IBM Program Directory for IBM Tivoli OMGAMON X for Messaging for z/os V7.3.0 Program Number 5698-B23 for Use with z/os Document Date: September 2014 GI13-2249-01
Note Before using this information and the product it supports, be sure to read the general information under 7.0, Notices on page 34. opyright International Business Machines orporation 2014. Note to U.S. Government Users Documentation related to restricted rights Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule ontract with IBM orp.
ontents 1.0 Introduction.................................................. 1 1.1 OMGAMON X for Messaging for z/os Description.......................... 2 1.2 OMGAMON X for Messaging for z/os FMIDs............................. 3 2.0 Program Materials.............................................. 4 2.1 Basic Machine-eadable Material..................................... 4 2.2 Optional Machine-eadable Material.................................... 4 2.3 Program Publications............................................. 4 2.4 Program Source Materials.......................................... 5 2.5 Publications Useful During Installation................................... 6 3.0 Program Support.............................................. 7 3.1 Program Services............................................... 7 3.2 Preventive Service Planning......................................... 7 3.3 Statement Support Procedures..................................... 8 4.0 Program and Service evel Information................................ 9 4.1 Program evel Information.......................................... 9 4.2 Service evel Information.......................................... 9 5.0 Installation equirements and onsiderations............................ 10 5.1 Driving System equirements........................................ 10 5.1.1 Machine equirements......................................... 10 5.1.2 Programming equirements...................................... 11 5.2 Target System equirements........................................ 11 5.2.1 Machine equirements......................................... 11 5.2.2 Programming equirements...................................... 11 5.2.2.1 Installation equisites....................................... 11 5.2.2.2 Operational equisites...................................... 12 5.2.2.3 Toleration/oexistence equisites................................ 13 5.2.2.4 Incompatibility (Negative) equisites.............................. 13 5.2.3 DASD Storage equirements..................................... 14 5.2.4 DASD Storage equirements by FMID................................ 18 5.3 FMIDs Deleted................................................ 22 5.4 Special onsiderations............................................ 22 6.0 Installation Instructions.......................................... 24 6.1 Installing OMGAMON X for Messaging for z/os........................... 24 6.1.1 SMP/ onsiderations for Installing OMGAMON X for Messaging for z/os......... 24 6.1.2 SMP/ Options Subentry Values................................... 24 6.1.3 SMP/ AIBS Processing..................................... 25 6.1.4 Installation Job Generator Utility.................................... 25 opyright IBM orp. 2014 iii
6.1.4.1 Introduction to the Job Generator................................ 26 6.1.4.2 Product Selection.......................................... 26 6.1.4.3 Installing into an existing SI................................... 26 6.1.4.4 Job Generator - Update ommand............................... 27 6.1.5 Sample Jobs............................................... 27 6.1.6 Allocate SMP/ Target and Distribution ibraries.......................... 28 6.1.7 reate DDDF ntries......................................... 29 6.1.8 Perform SMP/ IV....................................... 29 6.1.9 Perform SMP/ APPY......................................... 29 6.1.10 Perform SMP/ APT....................................... 32 6.2 Activating OMGAMON X for Messaging for z/os........................... 33 7.0 Notices..................................................... 34 7.1 Trademarks.................................................. 34 ontacting IBM Stware Support....................................... 35 Figures 1. Basic Material: Unlicensed Publications................................. 4 2. Publications Useful During Installation.................................. 6 3. PSP Upgrade and Subset ID........................................ 8 4. omponent IDs............................................... 8 5. Driving System Stware equirements................................. 11 6. Target System Mandatory Installation equisites............................ 12 7. Target System onditional Installation equisites............................ 12 8. Target System Mandatory Operational equisites........................... 13 9. Target System onditional Operational equisites........................... 13 10. Total DASD Space equired by OMGAMON X for Messaging for z/os............. 14 11. Storage equirements for SMP/ Work Data Sets........................... 15 12. Storage equirements for SMP/ Data Sets............................... 16 13. Storage equirements for OMGAMON X for Messaging for z/os Target ibraries....... 16 14. Storage equirements for OMGAMON X for Messaging for z/os Distribution ibraries.... 17 15. Storage equirements for HKQI730 ibraries.............................. 18 16. Storage equirements for HKMQ730 ibraries............................. 18 17. Storage equirements for HKM730 ibraries............................. 19 18. Storage equirements for HKF730 ibraries.............................. 20 19. Storage equirements for HKOB730 ibraries.............................. 20 20. SMP/ Options Subentry Values..................................... 24 21. Sample Installation Jobs.......................................... 27 iv OMGAMON X for Messaging for z/os Program Directory
1.0 Introduction This program directory is intended for system programmers who are responsible for program installation and maintenance. It contains information about the material and procedures associated with the installation IBM Tivoli OMGAMON X for Messaging for z/os. This publication refers to IBM Tivoli OMGAMON X for Messaging for z/os as OMGAMON X for Messaging for z/os. The Program Directory contains the following sections: 2.0, Program Materials on page 4 identifies the basic program materials and documentation for OMGAMON X for Messaging for z/os. 3.0, Program Support on page 7 describes the IBM support available for OMGAMON X for Messaging for z/os. 4.0, Program and Service evel Information on page 9 lists the APAs (program level) and PTFs (service level) that have been incorporated into OMGAMON X for Messaging for z/os. 5.0, Installation equirements and onsiderations on page 10 identifies the resources and considerations that are required for installing and using OMGAMON X for Messaging for z/os. 6.0, Installation Instructions on page 24 provides detailed installation instructions for OMGAMON X for Messaging for z/os. It also describes the procedures for activating the functions OMGAMON X for Messaging for z/os, or refers to appropriate publications. Before installing OMGAMON X for Messaging for z/os, read the BPDO Memo To Users and the BPDO Memo To Users xtension that are supplied with this program in stcopy format and this program directory; then keep them for future reference. Section 3.2, Preventive Service Planning on page 7 tells you how to find any updates to the information and procedures in this program directory. OMGAMON X for Messaging for z/os is supplied in a ustom-built Product Delivery Offering (BPDO, 5751-S3). The program directory that is provided in stcopy format on the BPDO tape is identical to the hardcopy format if one was included with your order. All service and HODDATA for OMGAMON X for Messaging for z/os are included on the BPDO tape. Do not use this program directory if you install OMGAMON X for Messaging for z/os with a SystemPac or ServerPac. When you use one those ferings, use the jobs and documentation supplied with the fering. The fering will point you to specific sections this program directory as needed. opyright IBM orp. 2014 1
1.1 OMGAMON X for Messaging for z/os Description IBM Tivoli introduces significant updates to IBM Tivoli OMGAMON Performance Monitors for key System z environments designed to run on IBM Tivoli Monitoring V6.3.0 Fix Pack 2 or higher and deliver enhanced capabilities designed to: Improve problem resolution efficiency by requiring fewer steps to isolate root cause performance impact in real time, therefore providing higher availability. Improve visibility, control, and automation with the more comprehensive 3270-based user interface capable viewing the entire enterprise-wide environment from a single 3270 screen. educe the time required for installation, configuration, and maintenance by utilizing enhanced IBM Tivoli Monitoring and PAMGN configuration tool functions. You must migrate your onfiguration Tool (IAT) setting to PAMGN at APA OA45024 level (HKI310 PTF UA73689) since the onfiguration Tool is no longer supported. OMGAMON X for Messaging for z/os is a product package consisting several components. The following can be configured and run on the mainframe. OMGAMON X for WebSphere Message Broker Monitoring is a monitoring and management tool that provides you with the means to verify, analyze, and tune message broker topologies. It helps ensure the reliability and performance your broker environment by detecting and correcting broker and message flow problems before they have an impact upon availability and service levels. It also reduces the amount time involved in the deployment broker applications by helping you debug message flows and providing statistics you can use to tune your environment. OMGAMON X for WebSphere MQ Monitoring lets you easily collect and analyze WebSphere MQ-specific data for all your remote and local queue managers from a single vantage point. It also provides many useful workspaces you can use to track trends and troubleshoot system problems. OMGAMON X for WebSphere MQ onfiguration helps you simplify the time-consuming and resource-intensive tasks defining and managing your WebSphere MQ configuration. New in OMGAMON X for Messaging for z/os V7.3.0: Tivoli ommon eporting 3.1, V2.1.1 reports are available on Service Management onnect. nhancements to further increase the usability and functionality the enhanced 3270 user interface (3270UI). Supports near term history for the enhanced 3270 user interface workspaces. Support for embedded data. Transaction file and database details. everages Tivoli Monitoring and the self-describing agent autonomic capability to remove the necessity for using application Ds to manually synchronize management servers and agents. 2 OMGAMON X for Messaging for z/os Program Directory
1.2 OMGAMON X for Messaging for z/os FMIDs OMGAMON X for Messaging for z/os consists the following FMIDs: HKQI730 HKMQ730 HKM730 HKF730 HKOB730 Introduction 3
2.0 Program Materials An IBM program is identified by a program number. The program number for OMGAMON X for Messaging for z/os is 5698-B23. Basic Machine-eadable Materials are materials that are supplied under the base license and feature numbers, and are required for the use the product. The program announcement material describes the features supported by OMGAMON X for Messaging for z/os. Ask your IBM representative for this information if you have not already received a copy. 2.1 Basic Machine-eadable Material The distribution medium for this program is physical media or downloadable files. This program is in SMP/ FI format and is installed by using SMP/. See 6.0, Installation Instructions on page 24 for more information about how to install the program. You can find information about the physical media for the basic machine-readable materials for OMGAMON X for Messaging for z/os in the BPDO Memo To Users xtension. 2.2 Optional Machine-eadable Material No optional machine-readable materials are provided for OMGAMON X for Messaging for z/os. 2.3 Program Publications The following sections identify the basic publications for OMGAMON X for Messaging for z/os. Figure 1 identifies the basic unlicensed publications for OMGAMON X for Messaging for z/os. The unlicensed documentation for OMGAMON X for Messaging for z/os can be found on the IBM Knowledge enter at http://www.ibm.com/support/knowledgecenter/ssaubv/welcome. Figure 1 (Page 1 2). Basic Material: Unlicensed Publications Publication Title Quick Start Guide Planning and onfiguration Guide Parameter eference Migration Guide 4 opyright IBM orp. 2014
Figure 1 (Page 2 2). Basic Material: Unlicensed Publications Publication Title WebSphere MQ Monitoring Agent User's Guide WebSphere MQ onfiguration Agent User's Guide WebSphere Message Broker Monitoring Agent User's Guide Troubleshooting Guide OMGAMON X and Tivoli Management Services on z/os shared documentation New in this elease Overview Guetting started Planning Installing Upgrading onfiguring Scenarios and how-tos eference The OMGAMON X and Tivoli Management Services on z/os shared documentation, and other Tivoli product documentation can be found at the IBM Knowledge enter url listed below: http://www.ibm.com/support/knowledgecenter/ssaubv/welcome Prior to installing OMGAMON X for Messaging for z/os, IBM recommends you review the Quick Start guide as well as the Planning and onfiguration guides if you have not already done so. This documentation focuses on the things you will need to know for a successful installation and configuration this product. efer to the Program Directory for IBM Tivoli Management Services on z/os (GI11-4105) for a complete documentation list and installation instructions for its product components. 2.4 Program Source Materials No program source materials or viewable program listings are provided for OMGAMON X for Messaging for z/os. Program Materials 5
2.5 Publications Useful During Installation You might want to use the publications listed in Figure 2 on page 6 during the installation OMGAMON X for Messaging for z/os. Figure 2. Publications Useful During Installation Publication Title IBM SMP/ for z/os User's Guide IBM SMP/ for z/os ommands IBM SMP/ for z/os eference IBM SMP/ for z/os Messages, odes, and Diagnosis Form Number SA22-7773 SA22-7771 SA22-7772 GA22-7770 These publications can be obtained from the IBM Publications enter website at http://www.ibm.com/shop/publications/order/. 6 OMGAMON X for Messaging for z/os Program Directory
3.0 Program Support This section describes the IBM support available for OMGAMON X for Messaging for z/os. 3.1 Program Services ontact your IBM representative for specific information about available program services. 3.2 Preventive Service Planning Before you install OMGAMON X for Messaging for z/os, make sure that you have reviewed the current Preventive Service Planning (PSP) information. eview the PSP Bucket for General Information, Installation Documentation, and the ross Product Dependencies sections. For the ecommended Service section, instead reviewing the PSP Bucket, it is recommended you use the IBM.ProductInstall-equiredService fix category in SMP/ to ensure you have all the recommended service installed. Use the FIXAT(IBM.ProductInstall-equiredService) operand on the APPY HK command. See 6.1.9, Perform SMP/ APPY on page 29 for a sample APPY command. If you obtained OMGAMON X for Messaging for z/os as part a BPDO, HODDATA is included. If the BPDO for OMGAMON X for Messaging for z/os is older than two weeks by the time you install the product materials, you can obtain the latest PSP Bucket information by going to the following website: http://www14.stware.ibm.com/webapp/set2/psearch/search?domain=psp You can also use S/390 StwareXcel or contact the IBM Support enter to obtain the latest PSP Bucket information. For program support, access the Stware Support Website at http://www-01.ibm.com/stware/support/. PSP Buckets are identified by UPGADs, which specify product levels; and SUBSTs, which specify the FMIDs for a product level. The UPGAD and SUBST values for OMGAMON X for Messaging for z/os are included in Figure 3. This product has an installation requirement for IBM Tivoli Management Services on z/os V6.3.0 or higher (5698-A79), so you should review the PSP buckets for it as well. efer to the Program Directory for IBM Tivoli Management Services on z/os (GI11-4105) for those UPGAD and SUBST values. opyright IBM orp. 2014 7
Figure 3. PSP Upgrade and Subset ID UPGAD SUBST Description OMXQI730 HKQI730 OMGAMON X for WebSphere Message Broker Monitoring HKMQ730 OMGAMON X for WebSphere MQ Monitoring HKM730 OMGAMON X for WebSphere MQ onfiguration HKF730 Generic onfiguration HKOB730 OMNIMON Base 3.3 Statement Support Procedures eport any problems which you feel might be an error in the product materials to your IBM Support enter. You may be asked to gather and submit additional diagnostics to assist the IBM Support enter in their analysis. Figure 4 identifies the component IDs (OMPID) for OMGAMON X for Messaging for z/os. Figure 4. omponent IDs FMID OMPID omponent Name HKQI730 5698A87MB OMGAMON X for WebSphere Message Broker Monitoring HKMQ730 5608A1100 OMGAMON X for WebSphere MQ Monitoring 730 HKM730 5608A3300 OMGAMON X for WebSphere MQ onfiguration 730 HKF730 5608A3301 Generic onfiguration 730 HKOB730 5608A41OB OMNIMON Base 730 TAIN elease 730 8 OMGAMON X for Messaging for z/os Program Directory
4.0 Program and Service evel Information This section identifies the program and relevant service levels OMGAMON X for Messaging for z/os. The program level refers to the APA fixes that have been incorporated into the program. The service level refers to the PTFs that have been incorporated into the program. 4.1 Program evel Information The following APA fixes against previous releases components included with OMGAMON X for Messaging for z/os have been incorporated into this release. They are listed by FMID. FMID HKQI730 OA41924 OA42 37 OA422 9 OA42382 OA42384 OA42385 OA43182 OA43582 FMID HKMQ730 OA41217 OA41287 OA41376 OA41378 OA41382 OA41395 OA41398 OA41899 OA42376 OA42383 OA42424 OA42482 OA42913 OA42915 OA42916 OA436 3 OA43646 OA43647 OA43713 FMID HKM730 OA41896 FMID HKF730 OA41895 OA4269 OA42695 OA42697 OA42698 OA42699 OA427 4 OA42722 FMID HKOB730 OA38724 OA38914 OA39194 OA39399 OA39622 OA39639 OA39649 OA39671 OA39889 OA4 88 OA4 373 OA4 429 OA4 8 OA4 853 OA4 973 OA41117 OA41153 OA41333 OA41451 OA41552 OA41669 OA41694 OA42127 OA42259 OA42748 OA42958 OA43 96 OA43163 OA43364 OA43638 4.2 Service evel Information No PTFs against this release OMGAMON X for Messaging for z/os have been incorporated into the product package. opyright IBM orp. 2014 9
5.0 Installation equirements and onsiderations The following sections identify the system requirements for installing and activating OMGAMON X for Messaging for z/os. The following terminology is used: Driving system: the system on which SMP/ is executed to install the program. Target system: the system on which the program is configured and run. In many cases, you can use a system as both a driving system and a target system. However, you can make a separate IP-able clone the running system to use as a target system. The clone must include copies all system libraries that SMP/ updates, copies the SMP/ SI data sets that describe the system libraries, and your PAMIB and POIB. Use separate driving and target systems in the following situations: When you install a new level a product that is already installed, the new level the product will replace the old one. By installing the new level onto a separate target system, you can test the new level and keep the old one in production at the same time. When you install a product that shares libraries or load modules with other products, the installation can disrupt the other products. By installing the product onto a separate target system, you can assess these impacts without disrupting your production system. 5.1 Driving System equirements This section describes the environment the driving system required to install OMGAMON X for Messaging for z/os. 5.1.1 Machine equirements The driving system can run in any hardware environment that supports the required stware. 10 opyright IBM orp. 2014
5.1.2 Programming equirements Figure 5. Driving System Stware equirements Program Number Any one the following: Product Name Minimum VM Minimum Service evel will satisfy these APAs 5694-A01 z/os V01.13.00 N/A No 5650-ZOS z/os V02.01.00 N/A No Included in the shipped product? Note: SMP/ is a requirement for Installation and is an element z/os but can also be ordered as a separate product, 5655-G44, minimally V03.05.00. Installation might require migration to new z/os releases to be service supported. See http://www-03.ibm.com/systems/z/os/zos/support/zos_eos_dates.html. 5.2 Target System equirements This section describes the environment the target system required to install and use OMGAMON X for Messaging for z/os. OMGAMON X for Messaging for z/os installs in the z/os (Z038) S. 5.2.1 Machine equirements The target system can run in any hardware environment that supports the required stware. 5.2.2 Programming equirements 5.2.2.1 Installation equisites Installation requisites identify products that are required and must be present on the system or products that are not required but should be present on the system for the successful installation this product. Mandatory installation requisites identify products that are required on the system for the successful installation this product. These products are specified as Ps or Qs. Installation equirements and onsiderations 11
Figure 6. Target System Mandatory Installation equisites Program Number Product Name Minimum VM Minimum Service evel will satisfy these APAs 5694-A01 z/os V01.13.00 N/A No 5650-ZOS z/os V02.01.00 N/A No 5698-A79 IBM Tivoli Management Services on z/os V06.03.00 N/A No Included in the shipped product? Note: Installation might require migration to new z/os releases to be service supported. See http://www-03.ibm.com/systems/z/os/zos/support/zos_eos_dates.html. onditional installation requisites identify products that are not required for successful installation this product but can resolve such things as certain warning messages at installation time. These products are specified as IF Qs. Figure 7. Target System onditional Installation equisites Program Number Product Name 5655-36 WebSphere MQ for z/os 5655-W97 WebSphere MQ for z/os Minimum VM V07.00.01 or higher V08.00.00 or higher Minimum Svc vl to satisfy these APAs Function for which this is a eq't N/A AIB No N/A AIB No Included in the shipped product? 5.2.2.2 Operational equisites Operational requisites are products that are required and must be present on the system or products that are not required but should be present on the system for this product to operate all or part its functions. Mandatory operational requisites identify products that are required for this product to operate its basic functions. These products are specified as Ps or Qs. 12 OMGAMON X for Messaging for z/os Program Directory
Figure 8. Target System Mandatory Operational equisites Program Number Product Name and Minimum VM/Service evel 5694-A01 z/os V01.13.00 5650-ZOS z/os V02.01.00 5698-A79 IBM Tivoli Management Services on z/os V06.03.00 or higher onditional operational requisites identify products that are not required for this product to operate its basic functions but are required at run time for this product to operate specific functions. These products are specified as IF Qs. Figure 9. Target System onditional Operational equisites Program Number One or more the following: Product Name and Minimum VM/Service evel 5655-36 WebSphere MQ for z/os V07.00.01 or higher 5655-W97 WebSphere MQ for z/os V08.00.00 or higher 5605-DB2 5615-DB2 IBM DB2 for z/os V10.01.00 or higher IBM DB2 for z/os V11.01.00 or higher 5697-P31 IBM DB2 Value Unit dition V10.01.00 or higher 5697-P43 IBM DB2 Value Unit dition V11.00.00 5655-V60 WebSphere Message Broker for z/os V07.00.00 or higher 5697-P44 WebSphere Message Broker for z/os V08.00.00 or higher 5655-IBB IBM Integration Bus for z/os V09.00.00 higher 5.2.2.3 Toleration/oexistence equisites Toleration/coexistence requisites identify products that must be present on sharing systems. These systems can be other systems in a multisystem environment (not necessarily sysplex), a shared DASD environment (such as test and production), or systems that reuse the same DASD environment at different time intervals. OMGAMON X for Messaging for z/os has no toleration/coexistence requisites. 5.2.2.4 Incompatibility (Negative) equisites Negative requisites identify products that must not be installed on the same system as this product. OMGAMON X for Messaging for z/os has no negative requisites. Installation equirements and onsiderations 13
5.2.3 DASD Storage equirements OMGAMON X for Messaging for z/os libraries can reside on all supported DASD types. Figure 10 on page 14 lists the total space that is required for each type library. Figure 10. Total DASD Space equired by OMGAMON X for Messaging for z/os ibrary Type Target 2801 Distribution 2508 Total Space equired in 3390 Trks Notes: 1. If you are installing into an existing environment that has the data sets in Figure 13 on page 16 and Figure 14 on page 17 already allocated, ensure sufficient disk space and directory blocks are available to support the requirement listed. This might require you to reallocate some data sets to avoid x37 abends. 2. Use system determined block sizes for efficient DASD utilization for all non-fm U data sets. For FM U data sets, a block size 32760 is recommended, which is the most efficient from a performance and DASD utilization perspective. 3. Abbreviations used for data set types are shown as follows. U S Unique data set, allocated by this product and used by only this product. This table provides all the required information to determine the correct storage for this data set. You do not need to refer to other tables or program directories for the data set size. Shared data set, allocated by this product and used by this product and other products. To determine the correct storage needed for this data set, add the storage size given in this table to those given in other tables (perhaps in other program directories). If the data set already exists, it must have enough free space to accommodate the storage size given in this table. xisting shared data set, used by this product and other products. This data set is not allocated by this product. To determine the correct storage for this data set, add the storage size given in this table to those given in other tables (perhaps in other program directories). If the data set already exists, it must have enough free space to accommodate the storage size given in this table. If you currently have a previous release this product installed in these libraries, the installation this release will delete the old release and reclaim the space that was used by the old release and any service that had been installed. You can determine whether these libraries have enough space by deleting the old release with a dummy function, compressing the libraries, and comparing the space requirements with the free space in the libraries. For more information about the names and sizes the required data sets, see 6.1.6, Allocate SMP/ Target and Distribution ibraries on page 28. 4. All target and distribution libraries listed have the following attributes: 14 OMGAMON X for Messaging for z/os Program Directory
The default name the data set can not be changed. The default block size the data set can be changed. The data set can not be merged with another data set that has equivalent characteristics. 5. All target libraries listed have the following attributes: These data sets can be SMS-managed, but they are not required to be SMS-managed. These data sets are not required to reside on the IP volume. The values in the "Member Type" column are not necessarily the actual SMP/ element types that are identified in the SMPMS. 6. All target libraries that are listed and contain load modules have the following attributes: These data sets can not be in the PA. These data sets can be in the NKST except for TKANMODS. If you are installing into an existing environment, ensure the values used for the SMP/ work datasets reflect the minimum values shown in Figure 11. heck the corresponding DDDF entries in all zones because use values lower than these can result in failures in the installation process. efer to the SMP/ manuals for instructions on updating DDDF entries. Figure 11. Storage equirements for SMP/ Work Data Sets ibrary DDNAM T Y P O G F M Prim 3390 Trks Sec 3390 Trks SMPWK1 PDS FB 80 150 150 220 SMPWK2 PDS FB 80 150 150 220 SMPWK3 PDS FB 80 300 600 1320 SMPWK4 PDS FB 80 150 150 220 SMPWK6 PDS FB 80 300 1500 660 SYSUT1 SQ -- -- 75 75 0 SYSUT2 SQ -- -- 75 75 0 SYSUT3 SQ -- -- 75 75 0 SYSUT4 SQ -- -- 75 75 0 DI Blks If you are installing into an existing environment, ensure the current SMP/ support dataset allocations reflect the minimum values shown in Figure 12. heck the space and directory block allocation and reallocate the data sets, if necessary. Installation equirements and onsiderations 15
Figure 12. Storage equirements for SMP/ Data Sets ibrary DDNAM T Y P O G F M Prim 3390 Trks Sec 3390 Trks SMPTS PDS U 0 15 150 N/A SMPMTS PDS FB 80 15 150 220 SMPPTS PDS FB 80 300 1500 N/A SMPSDS PDS FB 80 15 150 220 SMPSTS PDS FB 80 15 150 220 DI Blks Figure 13 and Figure 14 on page 17 describe the target and distribution libraries that will be allocated by this product's install jobs or that will be required for installation. The space requirements reflect what is specified in the allocation job or the space that this product will require in existing libraries. Additional tables are provided to show the specific space required for libraries that are used by each FMID. See 5.2.4, DASD Storage equirements by FMID on page 18 for more information. The storage requirements OMGAMON X for Messaging for z/os must be added to the storage required by other programs having data in the same library or path. Figure 13 (Page 1 2). Storage equirements for OMGAMON X for Messaging for z/os Target ibraries ibrary DDNAM Member Type Target Volume T Y P O G F M 3390 Trks TKANUS IST Any PDS FB 80 78 75 TKANDATV Data Any PDS VB 6160 376 15 TKANX X Any S PDS VB 255 13 44 TKANHNU Help Any PDS FB 80 138 188 TKANISP IST Any S PDS FB 80 2 44 TKANMA Macro Any PDS FB 80 8 3 TKANMOD MOD Any PDS U 0 200 26 TKANMOD MOD Any PDS U 0 902 23 TKANMODP MOD Any S PDS U 0 359 N/A TKANMODS MOD Any PDS U 0 74 56 TKANOS Data Any S PDS VB 255 3 44 TKANPA Parm Any PDS FB 80 9 10 DI Blks 16 OMGAMON X for Messaging for z/os Program Directory
Figure 13 (Page 2 2). Storage equirements for OMGAMON X for Messaging for z/os Target ibraries ibrary DDNAM Member Type Target Volume T Y P O G F M 3390 Trks TKANPNU Panel Any PDS FB 80 519 261 TKANPKGI Data Any PDS FB 80 36 10 TKANSAM Sample Any PDS FB 80 6 9 TKANWNU Panel Any S PDS FB 80 57 88 TKOBDATF Data Any S PDS FB 80 2 44 TKOBHP Help Any S PDS FB 80 19 132 DI Blks Figure 14. Storage equirements for OMGAMON X for Messaging for z/os Distribution ibraries ibrary DDNAM T Y P O G F M 3390 Trks DKANUS PDS FB 80 78 75 DKANDATV PDS VB 6160 376 15 DKANX S PDS VB 255 13 44 DKANHNU PDS FB 80 138 188 DKANISP S PDS FB 80 2 44 DKANMA PDS FB 80 8 3 DKANMOD PDS U 0 202 97 DKANMOD PDS U 0 900 23 DKANMODP S PDS U 0 79 N/A DKANMODS PDS U 0 61 3 DKANOS S PDS VB 255 3 44 DKANPA PDS FB 80 9 10 DKANPNU PDS FB 80 519 261 DKANPKGI PDS FB 80 36 10 DKANSAM PDS FB 80 6 9 DKANWNU S PDS FB 80 57 88 DKOBDATF S PDS FB 80 2 44 DKOBHP S PDS FB 80 19 132 DI Blks Installation equirements and onsiderations 17
5.2.4 DASD Storage equirements by FMID The tables in this section can help determine the specific space required for components not already installed in an existing environment. There is a table for each FMID included with the product. Figure 15. Storage equirements for HKQI730 ibraries ibrary DDNAM Member Type Target Volume T Y P O G F M 3390 Trks TKANUS IST Any PDS FB 80 21 18 TKANDATV Data Any PDS VB 6160 180 6 TKANMOD MOD Any PDS U 0 68 2 TKANMOD MOD Any PDS U 0 94 2 TKANPA Data Any PDS FB 80 3 2 TKANPKGI Data Any PDS FB 80 3 2 TKANSAM Sample Any PDS FB 80 1 2 DKANUS PDS FB 80 21 18 DKANDATV PDS VB 6160 180 6 DKANMOD PDS U 0 66 2 DKANMOD PDS U 0 93 2 DKANPA PDS FB 80 3 2 DKANPKGI PDS FB 80 3 2 DKANSAM PDS FB 80 1 2 DI Blks Figure 16 (Page 1 2). Storage equirements for HKMQ730 ibraries ibrary DDNAM Member Type Target Volume T Y P O G F M 3390 Trks TKANUS IST Any PDS FB 80 22 21 TKANDATV Data Any PDS VB 6160 183 3 TKANX X Any S PDS VB 255 3 7 TKANHNU HP Any PDS FB 80 135 184 TKANMOD MOD Any PDS U 0 4 3 TKANMOD MOD Any PDS U 0 445 15 DI Blks 18 OMGAMON X for Messaging for z/os Program Directory
Figure 16 (Page 2 2). Storage equirements for HKMQ730 ibraries ibrary DDNAM Member Type Target Volume T Y P O G F M 3390 Trks TKANPA Data Any PDS FB 80 3 2 TKANPNU Panel Any PDS FB 80 519 261 TKANPKGI Data Any PDS FB 80 17 2 TKANSAM Sample Any PDS FB 80 1 2 TKANWNU Panel Any S PDS FB 80 29 33 DKANUS PDS FB 80 22 21 DKANDATV PDS VB 6160 183 3 DKANX S PDS VB 255 3 7 DKANHNU PDS FB 80 135 184 DKANMOD PDS U 0 4 3 DKANMOD PDS U 0 444 15 DKANPA PDS FB 80 3 2 DKANPNU PDS FB 80 519 261 DKANPKGI PDS FB 80 17 2 DKANSAM PDS FB 80 1 2 DKANWNU S PDS FB 80 29 33 DI Blks Figure 17 (Page 1 2). Storage equirements for HKM730 ibraries ibrary DDNAM Member Type Target Volume T Y P O G F M 3390 Trks TKANUS IST Any PDS FB 80 22 21 TKANDATV Data Any PDS VB 6160 5 3 TKANMOD MOD Any PDS U 0 1 2 TKANMOD MOD Any PDS U 0 62 2 TKANPA Data Any PDS FB 80 1 2 TKANPKGI Data Any PDS FB 80 2 2 DKANUS PDS FB 80 22 21 DKANDATV PDS VB 6160 5 3 DI Blks Installation equirements and onsiderations 19
Figure 17 (Page 2 2). Storage equirements for HKM730 ibraries ibrary DDNAM Member Type Target Volume T Y P O G F M 3390 Trks DKANMOD PDS U 0 1 2 DKANMOD PDS U 0 62 2 DKANPA PDS FB 80 1 2 DKANPKGI PDS FB 80 2 2 DI Blks Figure 18. Storage equirements for HKF730 ibraries ibrary DDNAM Member Type Target Volume T Y P O G F M 3390 Trks TKANDATV Data Any PDS VB 6160 8 3 TKANMOD MOD Any PDS U 0 23 2 TKANMOD MOD Any PDS U 0 289 2 TKANPA Data Any PDS FB 80 1 2 TKANPKGI Data Any PDS FB 80 1 2 TKANSAM Sample Any PDS FB 80 1 2 DKANDATV PDS VB 6160 8 3 DKANMOD PDS U 0 23 2 DKANMOD PDS U 0 289 2 DKANPA PDS FB 80 1 2 DKANPKGI PDS FB 80 1 2 DKANSAM PDS FB 80 1 2 DI Blks Figure 19 (Page 1 3). Storage equirements for HKOB730 ibraries ibrary DDNAM Member Type Target Volume T Y P O G F M 3390 Trks TKANUS IST Any PDS FB 80 13 15 TKANX X Any S PDS VB 255 9 4 DI Blks 20 OMGAMON X for Messaging for z/os Program Directory
Figure 19 (Page 2 3). Storage equirements for HKOB730 ibraries ibrary DDNAM Member Type Target Volume T Y P O G F M 3390 Trks TKANHNU Help Any PDS FB 80 3 4 TKANISP IST Any S PDS FB 80 1 2 TKANMA Macro Any PDS FB 80 8 3 TKANMOD MOD Any PDS U 0 104 17 TKANMOD MOD Any PDS U 0 12 2 TKANMODP MOD Any S PDS U 0 313 N/A TKANMODS MOD Any PDS U 0 74 56 TKANOS Data Any S PDS VB 255 3 5 TKANPA Parm Any PDS FB 80 1 2 TKANPKGI Data Any PDS FB 80 13 2 TKANSAM Sample Any PDS FB 80 3 3 TKANWNU Panel Any S PDS FB 80 21 27 TKOBDATF Data Any S PDS FB 80 1 2 TKOBHP Help Any S PDS FB 80 17 66 DKANUS PDS FB 80 13 15 DKANX S PDS VB 255 9 4 DKANHNU PDS FB 80 3 4 DKANISP S PDS FB 80 1 2 DKANMA PDS FB 80 8 3 DKANMOD PDS U 0 108 88 DKANMOD PDS U 0 12 2 DKANMODP S PDS U 0 69 N/A DKANMODS PDS U 0 61 3 DKANOS S PDS VB 255 3 5 DKANPA PDS FB 80 1 2 DKANPKGI PDS FB 80 13 2 DKANSAM PDS FB 80 3 3 DKANWNU S PDS FB 80 21 27 DKOBDATF S PDS FB 80 1 2 DI Blks Installation equirements and onsiderations 21
Figure 19 (Page 3 3). Storage equirements for HKOB730 ibraries ibrary DDNAM Member Type Target Volume T Y P O G F M 3390 Trks DKOBHP S PDS FB 80 17 66 DI Blks 5.3 FMIDs Deleted Installing OMGAMON X for Messaging for z/os might result in the deletion other FMIDs. To see which FMIDs will be deleted, examine the ++V statement in the SMPMS the product. If you do not want to delete these FMIDs at this time, install OMGAMON X for Messaging for z/os into separate SMP/ target and distribution zones. Note: These FMIDs are not automatically deleted from the Global Zone. If you want to delete these FMIDs from the Global Zone, use the SMP/ JT NOFMID DTFMID command. See the SMP/ ommands book for details. 5.4 Special onsiderations To effectively manage a suite products with common components, you can install products into shared zones a consolidated stware inventory (SI). Space requirements are reduced by installing products into shared SI zones avoiding the duplication when different target zones, distribution zones, and data sets are used. Sharing a common set zones also allows SMP/ to automatically manage IFQ situations that exist across product components. If you intend to share a Tivoli nterprise Monitoring Server on z/os with other products, use shared SI zones so product configuration sets up the runtime environment correctly. The installation OMGAMON X for Messaging for z/os requires the Tivoli nterprise Monitoring Server on z/os be installed in the SI. efer to the Program Directory for IBM Tivoli Management Services on z/os (GI11-4105) for installation instructions its product components. The OMGAMON X and Tivoli Management Services on z/os shared documentation, and other Tivoli product documentation can be found at the IBM Knowledge enter url listed below: http://www.ibm.com/support/knowledgecenter/ssaubv/welcome 22 OMGAMON X for Messaging for z/os Program Directory
If you are installing into an existing SI zone that contains the listed FMIDs, ensure the maintenance has been installed previously or it must be installed with this product package. HKI31 - UA73688 UA73689 HKDS63 - UA69363 UA7 675 UA7 678 HKV63 - UA7 676 UA7 677 IBM Tivoli Monitoring V6.3.0 Fix Pack 3 is recommended for a number APA fixes, including Java 6 & 7 security support and Persistent Datastore APA OA44915: MUTIP ABNDS DU TO PSISTNT DATASTO FAIITY OVAY. onsider the following items when using shared SI zones. You must specify the same high-level qualifier for the target and distribution libraries as the other products in the same zones for the configuration tool to work correctly. If you install a product into an existing SI that contains a previous version the same product, SMP/ deletes the previous version during the installation process. To maintain multiple product versions concurrently, they must be installed into separate SI zones. If you install into an existing environment, you might need to remove data set references from the installation jobs to avoid errors because the data sets already exist. If you are installing into an existing environment that has the data sets already allocated, ensure sufficient space and directory blocks are available to support the requirement listed in the DASD tables. This might require you to reallocate some data sets to avoid x37 abends. When OMGAMON X for Messaging for z/os is used with the IBM Tivoli OMGAMON Dashboard dition on z/os product, they should both be installed in the same SI target and distribution zones. This ensures the maintenance level the ngine and Management Server components, which are used by both products, is at the same level. If they are installed in different SI zones, you should check to ensure the maintenance levels the ngine and Management Server components in both zones are the same or at a compatible level. This is also true for your runtime library environments (T). The PSP bucket will have the most current information and must be reviewed before installation. The OMGAVIW or OMGAMON Dashboard dition configuration document must also be reviewed for other operational considerations. Installation equirements and onsiderations 23
6.0 Installation Instructions This chapter describes the installation method and the step-by-step procedures to install and to activate the functions OMGAMON X for Messaging for z/os. Please note the following points: If you want to install OMGAMON X for Messaging for z/os into its own SMP/ environment, consult the SMP/ manuals for instructions on creating and initializing the SMPSI and the SMP/ control data sets. Additionally, to assist you in doing this, IBM has provided samples to help you create an SMP/ environment at the following url: http://www.ibm.com/support/docview.wss?rs=660&context=sszjdu&uid=swg21066230 You can use the sample jobs that are provided to perform part or all the installation tasks. The SMP/ jobs assume that all DDDF entries that are required for SMP/ execution have been defined in appropriate zones. 6.1 Installing OMGAMON X for Messaging for z/os 6.1.1 SMP/ onsiderations for Installing OMGAMON X for Messaging for z/os Use the SMP/ IV, APPY, and APT commands to install this release OMGAMON X for Messaging for z/os. 6.1.2 SMP/ Options Subentry Values The recommended values for certain SMP/ SI subentries are shown in Figure 20. Using values lower than the recommended values can result in failures in the installation. DSSPA is a subentry in the GOBA options entry. PMAX is a subentry the GNA entry in the GOBA options entry. See the SMP/ manuals for instructions on updating the global zone. Figure 20. SMP/ Options Subentry Values Subentry Value omment DSSPA 300,1200,1200 Use 1200 directory blocks PMAX SMP/ Default IBM recommends using the SMP/ default for PMAX. 24 opyright IBM orp. 2014
6.1.3 SMP/ AIBS Processing OMGAMON X for Messaging for z/os uses the AIBS function provided in SMP/ to resolve external references during installation. When OMGAMON X for Messaging for z/os is installed, ensure that DDDFs exist for the following libraries: SSIB SKD SSQOAD SZAMTX Note: AIBS uses the previous DDDFs only to resolve the link-edit for OMGAMON X for Messaging for z/os. These data sets are not updated during the installation OMGAMON X for Messaging for z/os. 6.1.4 Installation Job Generator Utility A utility is available to generate the necessary installation jobs for this product and others that might be included in the product package deliverable. Be aware that not all products are supported at this time and maintenance might have to be installed to get the latest updates for the product table. It is recommended you use this job generation utility to create a set jobs to install the product package when installing into an existing environment rather than using the sample jobs provided for each product. The job generation utility is delivered in the onfiguration Tool component the Tivoli Management Services on z/os product, which is a requisite this product. This utility is enhanced thru the maintenance stream so there could be an issue if it is invoked from an environment without the latest maintenance. nsure the latest maintenance is installed for the components this product to get the latest updates for the product table. If you are installing for the first time into a new environment and don't have an existing environment available to invoke this utility, you must use the sample jobs for the Tivoli Management Services on z/os product and install it first. This will install the FMID containing the job generation utility and the latest maintenance. Then you can invoke the utility from the target library TKANUS to install other products in the package. The job generation utility can be invoked from the SMP/ target library with the low-level qualifier TKANUS, launch the utility by using ISPF option 6 and entering the following command. ex 'hilev.tkanus' Select "SMP/-install z/os products with Install Job Generator (JOBGN)" from the Installation and onfiguration Tool main menu. You can use the online help available as a tutorial to become familiar with the utility and its processes. Installation Instructions 25
6.1.4.1 Introduction to the Job Generator The job generation utility creates a set jobs to define a SMP/ environment (SI and supporting data sets), allocate product libraries (target and distribution zone data sets and DDDFS), and install the products (IV APPY APT). You can use these jobs to create a totally new environment or to install the products into an existing SI. Processing Steps The jobs are generated from a series ISPF interactive panels and ISPF file tailoring. The initial step is selection the product mix. The set products will determine any additions to the basic set values needed to create the J. Process og One the members the generated job library is KIJGOG, which is the process log. This member shows the generating parameters and internal lists that were used to create the batch jobs. It also indicates which jobs were actually produced and need to be run. Note that the IV, APPY, and APT jobs are always generated even if the selected products are already in the target SI. In that case, the jobs install additional maintenance when available. 6.1.4.2 Product Selection You can select one or more products from a table that will determine the set FMIDs to install. You must select at least one product and you should always select the appropriate version the IBM Tivoli Management Services on z/os product (5698-A79) that is an installation requisite for this product fering. This will install the necessary FMIDs and maintenance for a new environment but also ensure any requisite maintenance will be processed when installing into an existing environment. The selection table contains information about all the supported products and might contain entries for products that you do not have or do not wish to install. Select only those products that are available in the package delivered and that you want to install. 6.1.4.3 Installing into an existing SI When the high-level qualifiers point to an existing environment, the job generation utility eliminates the jobs that allocate and initialize the SI. The job generation utility suppresses the creation libraries that already exist in the target environment. Instead, the generator creates a job to determine whether sufficient space is available for any additional data to be installed into the libraries. The member KIJGAN is generated to report on the available space for each the existing libraries that will have new data. However, KIJGAN cannot check for the maintenance stream requirements. 26 OMGAMON X for Messaging for z/os Program Directory
The space analyzer function is very helpful in identifying data set space issues that might cause X37 abends during APPY and APT processing. 6.1.4.4 Job Generator - Update ommand The job generation utility was enhanced to allow dynamic additions to the product table. The UPDAT routine is used to obtain additional data for products that are available but not yet included in the installation job generator table, KIDJG00. You must have the product FIs available on DASD in order to run this routine and all components the product must be available. After a successful run, the output this routine will replace the KIDJG00 member the work data set. If you make multiple changes to the data member be sure to save the original member as a backup. Note: Not all products qualify for inclusion in the job generator process at this time. efer to the online help for more information about this facility. 6.1.5 Sample Jobs If you choose not to use the installation job generator utility documented in the previous section, you can use the sample jobs that were created for OMGAMON X for Messaging for z/os. This will require you to research and tailor each the jobs accordingly. The sample jobs provided expect a SI to exist already. The sample installation jobs in Figure 21 are provided as part the product to help you install OMGAMON X for Messaging for z/os. Figure 21. Sample Installation Jobs Job Name Job Type Description FI KQIJ3AO AOAT Sample job to allocate target and distribution libraries IBM.HKQI730.F8 KQIJ4DDF DDDF Sample job to define SMP/ DDDFs IBM.HKQI730.F8 KQIJ5 IV Sample IV job IBM.HKQI730.F8 KQIJ6APP APPY Sample APPY job IBM.HKQI730.F8 KQIJ7A APT Sample APT job IBM.HKQI730.F8 The installation OMGAMON X for Messaging for z/os requires the Tivoli nterprise Monitoring Server on z/os be installed in the SI. efer to the Program Directory for IBM Tivoli Management Services on z/os (GI11-4105) for installation instructions its product components. You can access the sample installation jobs by performing an SMP/ IV (refer to 6.1.8, Perform SMP/ IV on page 29) then copy the jobs from the relfiles to a work data set for editing and submission. See Figure 21 to find the appropriate relfile data set. Installation Instructions 27
You can also copy the sample installation jobs from the tape or product files by submitting the following job. Depending on your distribution medium, use either the //TAPIN or the //FIIN DD statement and comment out or delete the other statement. Before you submit the job, add a job card and change the lowercase parameters to uppercase values to meet the requirements your site. //STP1 X PGM=IBOPY,GION=4M //SYSPINT DD SYSOUT= //TAPIN DD DSN=IBM.HKQI73.F8,UNIT=tunit, // VO=S=volser,AB=(x,S), // DISP=(OD,KP) //FIIN DD DSN=IBM.HKQI73.F8,UNIT=SYSADA,DISP=SH, // VO=S=filevol //OUT DD DSNAM=jcl-library-name, // DISP=(NW,ATG,DT), // VO=S=dasdvol,UNIT=SYSADA, // SPA=(TK,(1,2,5)) //SYSUT3 DD UNIT=SYSADA,SPA=(Y,(1,1)) //SYSIN DD OPY INDD=xxxxIN,OUTDD=OUT ST MMB=(KQIJ3AO,KQIJ4DDF,KQIJ5,KQIJ6APP,KQIJ7A) / See the following information to update the statements in the previous sample: TAPIN: tunit is the unit value that matches the product package. volser is the volume serial that matches the product package. x is the tape file number that indicates the location the data set name on the tape. See the documentation that is provided by BPDO for the location IBM.HKQI730.F8 on the tape. FIIN: filevol is the volume serial the DASD device where the downloaded files reside. OUT: jcl-library-name is the name the output data set where the sample jobs are stored. dasdvol is the volume serial the DASD device where the output data set resides. SYSIN: xxxxin is either TAPIN or FIIN depending on your input DD statement. 6.1.6 Allocate SMP/ Target and Distribution ibraries dit and submit the generated job KIJGAO to allocate the SMP/ target and distribution libraries for OMGAMON X for Messaging for z/os. If you are not using the generated allocation job, select the sample job KQIJ3AO. dit and submit it after making appropriate changes for your environment. onsult the instructions in the sample job for more information. onsider the following issues before submitting the job. If you are installing into an existing environment, you might have to remove lines for data sets that already exist. 28 OMGAMON X for Messaging for z/os Program Directory