Program Directory for IBM OMEGAMON z/os Management Console

Transcription

1 IBM Program Directory for IBM OMGAMON z/os Management Console V1.1.1 Program Number 5698-A78 for Use with z/os Document Date: April 2006 GI

2 Note! Before using this information and the product it supports, be sure to read the general information under 7.0, Notices on page 26. Copyright International Business Machines Corporation All rights reserved. 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 Contract with IBM Corp.

3 Contents 1.0 Introduction OMGAMON z/os Management Console Description OMGAMON z/os Management Console FMIDs Program Materials Basic Machine-eadable Material Optional Machine-eadable Material Program Publications Basic Program Publications Optional Program Publications Program Source Materials Publications Useful During Installation Program Support Program Services Preventive Service Planning Statement of Support Procedures Program and Service Level Information Program Level Information Service Level Information Installation equirements and Considerations Driving System equirements Machine equirements Programming equirements Target System equirements Machine equirements Programming equirements Installation equisites Operational equisites Toleration/Coexistence equisites Incompatibility (Negative) equisites DASD Storage equirements DASD Storage equirements by FMID FMIDs Deleted Special Considerations Considerations for Installing V1.1.1 over V Installation Instructions Installing OMGAMON z/os Management Console Considerations for Using the SMP/ Web Download Package Copyright IBM Corp iii

4 6.1.2 SMP/ Considerations for Installing OMGAMON z/os Management Console SMP/ Options Subentry Values SMP/ CALLLIBS Processing Sample Jobs Perform SMP/ CIV Allocate SMP/ Target and Distribution Libraries Create DDDF ntries Perform SMP/ APPLY Perform SMP/ ACCPT Activating OMGAMON z/os Management Console Notices Trademarks Contacting IBM Software Support Figures 1. Basic Material: Unlicensed Publications Publications Useful During Installation PSP Upgrade and Subset ID Component IDs Driving System Software equirements Mandatory Installation equisites Mandatory Operational equisites Total DASD Space equired by OMGAMON z/os Management Console Storage equirements for OMGAMON z/os Management Console Target Libraries Storage equirements for OMGAMON z/os Management Console Distribution Libraries Storage equirements for HKHL110 Libraries Storage equirements for HKCI310 Libraries Storage equirements for HKDS610 Libraries Storage equirements for HKLV610 Libraries SMP/ Options Subentry Values Sample Installation Jobs SMP/ lements Not Selected iv OMGAMON z/os Management Console Program Directory

5 1.0 Introduction This program directory is intended for the system programmer responsible for program installation and maintenance. It contains information concerning the material and procedures associated with the installation of IBM OMGAMON z/os Management Console. This publication refers to IBM OMGAMON z/os Management Console as OMGAMON z/os Management Console. The program directory contains the following sections: 2.0, Program Materials on page 3 identifies the basic and optional program materials and documentation for OMGAMON z/os Management Console. 3.0, Program Support on page 6 describes the IBM support available for OMGAMON z/os Management Console. 4.0, Program and Service Level Information on page 8 lists the APAs (program level) and PTFs (service level) incorporated into OMGAMON z/os Management Console. 5.0, Installation equirements and Considerations on page 9 identifies the resources and considerations required for installing and using OMGAMON z/os Management Console. 6.0, Installation Instructions on page 19 provides detailed installation instructions for OMGAMON z/os Management Console. It also describes the procedures for activating the functions of OMGAMON z/os Management Console, or refers to appropriate publications. Before installing OMGAMON z/os Management Console, read Section 3.2, Preventive Service Planning on page 6. This tells you how to find any updates to the information and procedures in this program directory. OMGAMON z/os Management Console is a web deliverable as well as being available on physical media. If you have received physical media, read the CBPDO Memo To Users and the CBPDO Memo To Users xtension that were supplied with this program in softcopy form as well as this program directory and then keep them for future reference. OMGAMON z/os Management Console can be supplied in a Custom-Built Product Delivery Offering (CBPDO, 5751-CS3). The program directory is provided in softcopy form on the CBPDO tape which is identical to the hardcopy form provided with your order. All service and HOLDDATA for OMGAMON z/os Management Console are included on the CBPDO tape. Do not use this program directory if you are installing OMGAMON z/os Management Console with a SystemPac or ServerPac. When using these offerings, use the jobs and documentation supplied with the offering. This documentation may point you to specific sections of the program directory as required. Copyright IBM Corp

6 1.1 OMGAMON z/os Management Console Description The OMGAMON z/os Management Console product collects health check and availability information about z/os systems and sysplex resources, and reports the information in the Tivoli nterprise Portal graphical user interface. The product workspaces provide real-time health check information collected by the IBM Health Checker for z/os and configuration status information for z/os systems and sysplex resources. The user interface contains expert advice on alerts and corrective actions. 1.2 OMGAMON z/os Management Console FMIDs OMGAMON z/os Management Console consists of the following FMIDs (function modification identifiers): HKHL110 HKCI310 HKDS610 HKLV610 2 OMGAMON z/os Management Console Program Directory

7 2.0 Program Materials An IBM program is identified by a program number. The program number for OMGAMON z/os Management Console is 5698-A78. Basic Machine-eadable Materials are materials that are supplied under the base license and feature numbers, and are required for the use of the product. Optional Machine-eadable Materials are orderable under separate feature numbers, and are not required for the product to function. The program announcement material describes the features supported by OMGAMON z/os Management Console. 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 magnetic tape or downloadable files. It is installed using SMP/, and is in SMP/ LFIL format. See 6.0, Installation Instructions on page 19 for more information about how to install the program. You can obtain the code deliverables and documentation required for installation from the Web site listed below: Information about the physical tape for the Basic Machine-eadable Materials for OMGAMON z/os Management Console can be found in the CBPDO Memo To Users xtension. 2.2 Optional Machine-eadable Material No optional machine-readable materials are provided for OMGAMON z/os Management Console. 2.3 Program Publications The following sections identify the basic and optional publications for OMGAMON z/os Management Console Basic Program Publications Figure 1 identifies the basic program publications for OMGAMON z/os Management Console. All of these publications are on CDs and included when you order the basic materials for OMGAMON z/os Management Console. For additional copies, contact your IBM representative. Copyright IBM Corp

8 Figure 1. Basic Material: Unlicensed Publications Publication Title IBM OMGAMON z/os Management Console Planning, Installation, and Configuration Guide IBM OMGAMON z/os Management Console User's Guide Introducing IBM Tivoli Monitoring xploring IBM Tivoli Monitoring IBM Tivoli Monitoring Installation and Setup Guide IBM Tivoli Monitoring Administrator's Guide IBM Tivoli Monitoring User's Guide IBM Tivoli Monitoring Problem Determination Guide Configuring IBM Tivoli nterprise Monitoring Server on z/os Note: The OMGAMON z/os Management Console publications are only available in softcopy on the OMGAMON z/os Management Console publications CD and in the Tivoli Information Center. Form Number GC SC GI SC GC SC SC GC SC The OMGAMON z/os Management Console product manuals and all other Tivoli product manuals can be found at the Tivoli Information Center Web site listed below: The OMGAMON z/os Management Console Program Directory, and other Tivoli program directories can be found by following links to the product from the support Web site listed below: Optional Program Publications No optional publications are provided for OMGAMON z/os Management Console. 2.4 Program Source Materials No program source materials or viewable program listings are provided for OMGAMON z/os Management Console. 4 OMGAMON z/os Management Console Program Directory

9 2.5 Publications Useful During Installation The publications listed in Figure 2 on page 5 can be useful during the installation of OMGAMON z/os Management Console. To order copies, contact your IBM representative or visit the IBM Publications Center at the following Web site: Figure 2. Publications Useful During Installation Publication Title IBM SMP/ for z/os and OS/390 User's Guide IBM SMP/ for z/os and OS/390 Commands IBM SMP/ for z/os and OS/390 eference IBM SMP/ for z/os and OS/390 Messages, Codes, and Diagnosis Form Number SA SA SA GA Program Materials 5

10 3.0 Program Support This section describes the IBM support available for OMGAMON z/os Management Console. 3.1 Program Services Contact your IBM or Tivoli representative for specific information about available program services. You can find information in the IBM Software Support Handbook at the following Web site: The handbook provides information about how to contact IBM Software Support, depending on the severity of your problem, and the following information: egistration and eligibility Telephone numbers and addresses, depending on the country in which you are located What information you need to gather before contacting support 3.2 Preventive Service Planning Before installing OMGAMON z/os Management Console, you should review the current Preventive Service Planning (PSP) information. You can contact IBM Software Support or use S/390 SoftwareXcel to obtain the current PSP Bucket. For program support, access the Software Support Web site at: 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 z/os Management Console are included in Figure 3. Figure 3. PSP Upgrade and Subset ID UPGAD SUBST Description OMXHL111 HKHL110 OMGAMON z/os Management Console HKCI310 Configuration Assistance Tool HKDS610 Tivoli nterprise Monitoring Server on z/os HKLV610 ITMS:ngine 6 Copyright IBM Corp. 2006

11 3.3 Statement of Support Procedures eport any difficulties you have using this program to IBM Software Support. If an APA is required, they will provide the address to which any needed documentation can be sent. Figure 4 on page 7 identifies the component IDs (COMPID) for OMGAMON z/os Management Console. Figure 4. Component IDs FMID COMPID Component Name HKHL A7800 OMGAMON z/os Management Console 110 HKCI A41CC Configuration Assistance Tool 310 HKDS A2800 Tivoli nterprise Monitoring Server on z/os 610 HKLV A41C ITMS:ngine 610 TAIN elease Program Support 7

12 4.0 Program and Service Level Information This section identifies the program and any relevant service levels of OMGAMON z/os Management Console. The program level refers to the APA fixes incorporated into the program. The service level refers to the PTFs incorporated into the program. 4.1 Program Level Information The following APA fixes against previous releases of components included with OMGAMON z/os Management Console have been incorporated into this release. They are listed by FMID. FMID HKCI310 OA09405 OA09526 OA09527 OA09528 OA09529 OA09530 OA09531 OA09532 FMID HKDS610 OA09463 OA09988 OA10129 OA10230 OA10409 OA10521 OA10557 OA10573 OA10900 OA10914 OA11296 OA11840 OA12019 OA12020 OA12021 OA12022 OA12023 OA12024 OA12025 OA12026 OA12580 OA12698 OA12817 OA12883 FMID HKLV610 OA09477 OA09583 OA09762 OA09797 OA11225 OA11249 OA11649 OA11740 OA11846 OA12017 OA Service Level Information No PTFs against this release of OMGAMON z/os Management Console have been incorporated into the product tape. If you obtained OMGAMON z/os Management Console in a CBPDO deliverable, your order will include all available service and HOLDDATA based on your ordering options. If you obtained OMGAMON z/os Management Console as a web deliverable, service might be included with the package. If it is not included, you must obtain service through your regular service acquisition channel. 8 Copyright IBM Corp. 2006

13 5.0 Installation equirements and Considerations The following sections identify the system requirements for installing and activating OMGAMON z/os Management Console. The following terminology is used: Driving system: the system used to install the program. Target system: the system on which the program is installed. In many cases, the same system can be used as both a driving system and a target system. However, you may want to set up a clone of your system to use as a target system by making a separate IPL-able copy of the running system. The clone must include copies of all system libraries that SMP/ updates, copies of the SMP/ CSI data sets that describe the system libraries, and your PAMLIB and POCLIB. Some cases where two systems must be used include the following: When installing a new level of a product that is already installed, the new product will delete the old one. By installing onto a separate target system, you can test the new product while still keeping the old one in production. When installing a product that shares libraries or load modules with other products, the installation can disrupt the other products. Installing onto a test system or clone will allow you to assess these impacts without disrupting your production system. 5.1 Driving System equirements This section describes the environment of the driving system required to install OMGAMON z/os Management Console Machine equirements The driving system can run in any hardware environment that supports the required software Programming equirements Figure 5. Driving System Software equirements Program Number Any one of the following: Product Name and Minimum VM/Service Level 5694-A01 z/os V1.4 or later 5655-G44 IBM SMP/ for z/os and OS/390 V3.2.0 or later Copyright IBM Corp

14 5.2 Target System equirements This section describes the environment of the target system required to install and use OMGAMON z/os Management Console. OMGAMON z/os Management Console installs in the z/os (Z038) SL Machine equirements The target system can run in any hardware environment that supports the required software Programming equirements Installation equisites An installation requisite is defined as a product that is required and must be present or one that is not required but should be present on the system for the successful installation of this product. A mandatory installation requisite identifies products that are required, without exception, or this product will not install on your system. This includes products specified as Ps or Qs. Figure 6. Mandatory Installation equisites Program Number Product Name and Minimum VM/Service Level 5694-A01 z/os V1.4 or later A conditional installation requisite identifies products that are not required for successful install but may resolve such things as certain warning messages at installation time. They include products that are specified as IF Qs. OMGAMON z/os Management Console has no conditional installation requisites Operational equisites An operational requisite is defined as a product that is required and must be present or a product that is not required but should be present on the system for this product to operate all or some of its functions. A mandatory operational requisite identifies products that are required, without exception, or this product will not operate its basic function unless the requisite is met. This includes products specified as Ps or Qs. 10 OMGAMON z/os Management Console Program Directory

15 Figure 7. Mandatory Operational equisites Program Number Any one of the following: 5694-A01 z/os V A01 z/os V1.5 Product Name and Minimum VM/Service Level 5694-A01 z/os V1.6 with APAs OA09046 OA A01 z/os V1.7 with APA OA11901 A conditional operational requisite identifies products that are not required for the basic function but are needed at run time for this product to utilize specific functions. They can include products specified as IF Qs. OMGAMON z/os Management Console has no conditional operational requisites Toleration/Coexistence equisites A toleration/coexistence requisite is defined as a product that must be present on a shared system. 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 at different time intervals. OMGAMON z/os Management Console has no toleration/coexistence requisites Incompatibility (Negative) equisites A negative requisite identifies products that must not be installed on the same system as this product. OMGAMON z/os Management Console has no negative requisites DASD Storage equirements OMGAMON z/os Management Console libraries can reside on all supported DASD types. Figure 8 on page 12 lists the total space required for each type of library. Installation equirements and Considerations 11

16 Figure 8. Total DASD Space equired by OMGAMON z/os Management Console Library Type Total Space equired Target 3376 tracks of 3390 Distribution 3372 tracks of 3390 Notes: 1. If you are installing into an existing environment that has the data sets in Figure 9 on page 13 and Figure 10 on page 14 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-cfm U data sets. For CFM U data sets, a block size of is recommended, which is the most efficient from a performance and DASD utilization perspective. 3. The following abbreviations are used for the data set type: U S Unique data set, allocated by this product and used only by this product. To determine the correct storage needed for this data set, this table provides all required information; no other tables (or program directories) need to be referenced for the data set size. Shared data set, allocated by this product and used by this product and others. To determine the correct storage needed for this data set, the storage size given in this table needs to be added to 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 others. This data set is NOT allocated by this product. To determine the correct storage needed for this data set, the storage size given in this table needs to be added to other tables (perhaps in other program directories). This existing data set must have enough free space to accommodate the storage size given in this table. If you currently have a previous release of this product installed in these libraries, the installation of this release will delete the old one and reclaim the space used by the old release and any service that had been installed. You can determine whether or not 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 on the names and sizes of the required data sets, please refer to 6.1.7, Allocate SMP/ Target and Distribution Libraries on page All target and distribution libraries listed have the following attributes: The default name of the data set may not be changed. The default block size of the data set may be changed. The data set may not be merged with another data set that has equivalent characteristics. The data set may be either a PDS or a PDS. 5. All target libraries listed have the following attributes: 12 OMGAMON z/os Management Console Program Directory

17 The data set may be SMS-managed. It is not required for the data set to be SMS-managed. It is not required for the data set to reside on the IPL volume. The values in the "Member Type" column are not necessarily the actual SMP/ element types identified in the SMPMCS. 6. All target libraries listed that contain load modules have the following attributes: The data set may not be in the LPA. The data set may be in the LNKLST except for TKANMODS. Figure 9 and Figure 10 on page 14 describe the target and distribution libraries required to install OMGAMON z/os Management Console in a standalone environment. The storage requirements of OMGAMON z/os Management Console must be added to the storage required by other programs having data in the same library or path when installing into an existing environment. Additional tables for each FMID are provided to help determine the specific space required for a FMID if some common components are already installed. See 5.2.4, DASD Storage equirements by FMID on page 14 for more information. Figure 9. Storage equirements for OMGAMON z/os Management Console Target Libraries Library DDNAM Member Type Target Volume T Y P O G C F M L C L No. of 3390 Trks TKANCMD Data Any S PDS FB TKANCUS CLIST Any S PDS FB TKANDATV Data Any S PDS VB TKANHNU Help Any S PDS FB TKANMAC Macro Any S PDS FB TKANMOD LMOD Any S PDS U TKANMODL LMOD Any S PDS U TKANMODS LMOD Any S PDS U TKANPA Data Any S PDS FB TKANPNU Panel Any S PDS FB TKANPKGI Data Any S PDS FB TKANSAM Sample Any S PDS FB TKCIINST CLIST Any S PDS FB TKNSLOCL Data Any S PDS VB No. of DI Blks Installation equirements and Considerations 13

18 Figure 10. Storage equirements for OMGAMON z/os Management Console Distribution Libraries Library DDNAM T Y P O G C F M L C L No. of 3390 Trks DKANCMD S PDS FB DKANCUS S PDS FB DKANDATV S PDS VB DKANHNU S PDS FB DKANMAC S PDS FB DKANMOD S PDS U DKANMODL S PDS U DKANMODS S PDS U DKANPA S PDS FB DKANPNU S PDS FB DKANPKGI S PDS FB DKANSAM S PDS FB DKCIINST S PDS FB DKNSLOCL S PDS VB No. of DI Blks 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. 14 OMGAMON z/os Management Console Program Directory

19 Figure 11. Storage equirements for HKHL110 Libraries Library DDNAM Member Type Target Volume T Y P O G C F M L C L No. of 3390 Trks TKANCUS CLIST Any S PDS FB TKANDATV Data Any S PDS VB TKANMODL LMOD Any S PDS U TKANPA Data Any S PDS FB TKANPKGI Data Any S PDS FB TKANSAM Sample Any S PDS FB DKANCUS S PDS FB DKANDATV S PDS VB DKANMODL S PDS U DKANPA S PDS FB DKANPKGI S PDS FB DKANSAM S PDS FB No. of DI Blks Figure 12. Storage equirements for HKCI310 Libraries Library DDNAM Member Type Target Volume T Y P O G C F M L C L No. of 3390 Trks TKANCUS CLIST Any S PDS FB TKANPA Data Any S PDS FB TKANPKGI Data Any S PDS FB TKANSAM Sample Any S PDS FB TKCIINST Sample Any S PDS FB DKANCUS S PDS FB DKANPA S PDS FB DKANPKGI S PDS FB DKANSAM S PDS FB DKCIINST S PDS FB No. of DI Blks Installation equirements and Considerations 15

20 Figure 13. Storage equirements for HKDS610 Libraries Library DDNAM Member Type Target Volume T Y P O G C F M L C L No. of 3390 Trks TKANCUS CLIST Any S PDS FB TKANDATV Data Any S PDS VB TKANMAC Macro Any S PDS FB TKANMOD LMOD Any S PDS U TKANMODL LMOD Any S PDS U TKANMODS LMOD Any S PDS U TKANPA Data Any S PDS FB TKANPKGI Data Any S PDS FB TKANSAM Sample Any S PDS FB TKNSLOCL Data Any S PDS VB DKANCUS S PDS FB DKANDATV S PDS VB DKANMAC S PDS FB DKANMOD S PDS U DKANMODL S PDS U DKANMODS S PDS U DKANPA S PDS FB DKANPKGI S PDS FB DKANSAM S PDS FB DKNSLOCL S PDS VB No. of DI Blks Figure 14 (Page 1 of 2). Storage equirements for HKLV610 Libraries Library DDNAM Member Type Target Volume T Y P O G C F M L C L No. of 3390 Trks TKANCMD Data Any S PDS FB TKANHNU Help Any S PDS FB TKANMAC Macro Any S PDS FB TKANMODL LMOD Any S PDS U No. of DI Blks 16 OMGAMON z/os Management Console Program Directory

21 Figure 14 (Page 2 of 2). Storage equirements for HKLV610 Libraries Library DDNAM Member Type Target Volume T Y P O G C F M L C L No. of 3390 Trks TKANMODS LMOD Any S PDS U TKANPA Data Any S PDS FB TKANPNU Panel Any S PDS FB TKANPKGI Data Any S PDS FB TKANSAM Sample Any S PDS FB DKANCMD S PDS FB DKANHNU S PDS FB DKANMAC S PDS FB DKANMODL S PDS U DKANMODS S PDS U DKANPA S PDS FB DKANPNU S PDS FB DKANPKGI S PDS FB DKANSAM S PDS FB No. of DI Blks 5.3 FMIDs Deleted Installing OMGAMON z/os Management Console may result in the deletion of other FMIDs. To see what FMIDs will be deleted, examine the ++V statement in the product's SMPMCS. If you do not want to delete these FMIDs at this time, you must install OMGAMON z/os Management Console into separate SMP/ target and distribution zones. Note: These FMIDs will not automatically be deleted from the Global Zone. Consult the SMP/ manuals for instructions on how to delete FMIDs from the Global Zone. 5.4 Special Considerations OMGAMON z/os Management Console includes several components that are referred to as common components because they are also included in other OMGAMON products. If you install into an existing environment, you might need to delete the FMIDs for these components from the SMP/ installation jobs to avoid errors because they are already installed. Installation equirements and Considerations 17

22 These common components are: HKCI310 HKDS610 HKLV610 OMGAMON z/os Management Console was also designed to allow it to install into common target and distribution libraries with other OMGAMON products. If you install into an existing environment, you might need to delete libraries from the installation jobs to avoid errors because the libraries 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 Considerations for Installing V1.1.1 over V1.1.0 If you are installing OMGAMON z/os Management Console V1.1.1 into an existing environment that contains V1.1.0, read the following changes to the install process. 1. Do not run the ALLOCAT (KHLA0ALO) and DDDF (KHLA0DDF) jobs because the data sets are already allocated and defined. 2. The CIV (KHLA0C) job must be modified to exclude two FMIDs that are already installed. Use the following control statement to update the sample job. CIV SYSMODS XCLUD(HKCI31 HKHL11 ) 3. The APPLY (KHLA0APP) and ACCPT (KHLA0ACC) jobs must be updated to delete these two FMIDs (HKCI310 HKHL110) from the control statements because they are already installed. 18 OMGAMON z/os Management Console Program Directory

23 6.0 Installation Instructions This chapter describes the installation method and the step-by-step procedures to install and to activate the functions of OMGAMON z/os Management Console. Note the following information: If you want to install OMGAMON z/os Management Console into its own SMP/ environment, consult the SMP/ manuals for instructions on creating and initializing the SMPCSI 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 Web site: Sample jobs have been provided to help perform some or all of the installation tasks. The SMP/ jobs assume that all DDDF entries required for SMP/ execution have been defined in the appropriate zones. The SMP/ dialogs can be used instead of the sample jobs to accomplish the SMP/ installation steps. 6.1 Installing OMGAMON z/os Management Console Considerations for Using the SMP/ Web Download Package The Web download package for OMGAMON z/os Management Console uses the SMP/ GIMZIP function, which was introduced in SMP/ for z/os V31. Although GIMZIP and GIMUNZIP are used for the packaging, the full SMP/ CIV FOMNTWOK function is not available with this package. The SMP/ GIMUNZIP function is required to process the downloaded package. efer to the z/os SMP/ eference for information about using GIMUNZIP. You will need to perform the following tasks: 1. nsure that configuration requirements for using GIMUNZIP have been completed. For a description of the GIMZIP and GIMUNZIP function, refer to the SMP/ web page at: 2. Allocate a /W HFS directory on the z/os system where the package will be staged. This is the repository for the download package. efer to the eadme file for more details. 3. Download the OMGAMON z/os Management Console package which is available from the following Web site: There are two parts of the package: HL111.ADM.txt Copyright IBM Corp

24 This file contains a sample job that performs the following tasks. It must be updated to reflect your environment. xecutes the z/os UNIX System Services pax command to extract the GIMZIP archives from the downloaded package. xecutes the GIMUNZIP program to expand the GIMZIP archives and place their contents in data sets that can be processed by SMP/. xecutes the SMP/ CIV from DASD function to receive the FMIDs in the package. HL111.pax.Z This pax archive file consists of the base function. The file contains the SMP/ MCS and the associated LFILs. This must be downloaded to a node that has connectivity to the target z/os system. Transfer the file to the host using binary format. 4. un the sample job in HL111.ADM.txt This job will perform the required tasks up to and including the SMP/ CIV from DASD step. 5. Complete the installation using the instructions in this Program Directory, beginning with 6.1.7, Allocate SMP/ Target and Distribution Libraries on page SMP/ Considerations for Installing OMGAMON z/os Management Console This release of OMGAMON z/os Management Console is installed using the SMP/ CIV, APPLY, and ACCPT commands. The SMP/ dialogs can be used to accomplish the SMP/ installation steps SMP/ Options Subentry Values The suggested values for some SMP/ CSI subentries are shown in Figure 15. Use of values lower than these can result in failures in the installation process. DSSPAC is a subentry in the GLOBAL options entry. PMAX is a subentry of the GNAL entry in the GLOBAL options entry. efer to the SMP/ manuals for instructions on updating the global zone. Figure 15. SMP/ Options Subentry Values SUB-NTY Value Comment DSSPAC 300,300,1200 Use 1200 directory blocks PMAX SMP/ Default Use the SMP/ default for PMAX SMP/ CALLLIBS Processing OMGAMON z/os Management Console does not use the CALLLIBS function. 20 OMGAMON z/os Management Console Program Directory

25 6.1.5 Sample Jobs The sample jobs provided expect a CSI to exist already. If one does not exist, see the information at the beginning of the installation section for creating one. The following sample installation jobs are provided as part of the product to help you install OMGAMON z/os Management Console: Figure 16. Sample Installation Jobs Job Name Job Type Description LFIL KHLA0C CIV Sample CIV job IBM.HKHL110.F7 KHLA0ALO ALLOCAT Sample job to allocate target and distribution libraries IBM.HKHL110.F7 KHLA0DDF DDDF Sample job to define SMP/ DDDFs IBM.HKHL110.F7 KHLA0APP APPLY Sample APPLY job IBM.HKHL110.F7 KHLA0ACC ACCPT Sample ACCPT job IBM.HKHL110.F7 You can access the sample installation jobs by performing an SMP/ CIV and then copying the jobs from the relfiles to a work data set for editing and submission. See Figure 16 to find the appropriate relfile data set. You may also choose to copy the jobs from the tape or product files by submitting the job below. Use either the //TAPIN or the //FILIN DD statement, depending on your distribution medium, and comment out or delete the other statement. Add a job card and change the lowercase parameters to uppercase values to meet your site's requirements before submitting. //STP1 XC PGM=IBCOPY //SYSPINT DD SYSOUT= //TAPIN DD DSN=IBM.HKHL11.F7,UNIT=tunit, // VOL=S=volser,LABL=(x,SL), // DISP=(OLD,KP) //FILIN DD DSN=IBM.HKHL11.F7,UNIT=SYSALLDA,DISP=SH, // VOL=S=filevol //OUT DD DSNAM=jcl-library-name, // DISP=(NW,CATLG,DLT), // VOL=S=dasdvol,UNIT=SYSALLDA, // SPAC=(TK,(1,2,5)) //SYSUT3 DD UNIT=SYSALLDA,SPAC=(CYL,(1,1)) //SYSIN DD COPY INDD=xxxxIN,OUTDD=OUT SLCT MMB=(KHLA ACC,KHLA ALO,KHLA APP,KHLA DDF,KHLA C) / In the sample above, update the statements as noted below: If using TAPIN: tunit is the unit value matching the product tape. volser is the volume serial matching the product tape. Installation Instructions 21

26 x is the tape file number where the data set name is on the tape. efer to the documentation provided by CBPDO to see where IBM.HKHL110.F7 is on the tape. If using FILIN filevol is the volume serial of the DASD device where the downloaded files reside. OUT jcl-library-name is the name of the output data set where the sample jobs will be stored. dasdvol is the volume serial of the DASD device where the output data set will reside. SYSIN xxxxin is either TAPIN or FILIN depending on your input DD statement Perform SMP/ CIV Having obtained OMGAMON z/os Management Console as part of a CBPDO, use the CVPDO job found in the CBPDO IMLIB data set to CIV the OMGAMON z/os Management Console FMIDs as well as any service and HOLDDATA included on the CBPDO tape. For more information, refer to the documentation included with the CBPDO. You can also choose to edit and submit sample job KHLA0C to perform the SMP/ CIV for OMGAMON z/os Management Console. Consult the instructions in the sample job for more information. xpected eturn Codes and Messages: Allocate SMP/ Target and Distribution Libraries dit and submit sample job KHLA0ALO to allocate the SMP/ target and distribution libraries for OMGAMON z/os Management Console. Consult the instructions in the sample job for more information. 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. xpected eturn Codes and Messages: Create DDDF ntries dit and submit sample job KHLA0DDF to create DDDF entries for the SMP/ target and distribution libraries for OMGAMON z/os Management Console. Consult the instructions in the sample job for more information. xpected eturn Codes and Messages: 0 22 OMGAMON z/os Management Console Program Directory

27 6.1.9 Perform SMP/ APPLY dit and submit sample job KHLA0APP to perform an SMP/ APPLY CHCK for OMGAMON z/os Management Console. Consult the instructions in the sample job for more information. To receive the full benefit of the SMP/ Causer SYSMOD Summary eport, do not bypass the following on the APPLY CHCK: P, ID, Q, and IFQ. This is because the SMP/ root cause analysis identifies the cause only of OS and not of WANINGS (SYSMODs that are bypassed are treated as warnings, not errors, by SMP/). nhanced HOLDDATA introduced O HOLDs against FMIDs for HIP APAs. Prior to installing, ensure you have the latest nhanced HOLDDATA (available at The FMIDs can be installed regardless of the status of unresolved HIPs, however, the software must not be deployed until the unresolved HIPs have been analyzed to determine applicability. There are two methods to complete an FMID installation where ++HOLDs for HIPs exist for the FMIDs being installed: 1. To ensure that all critical service is installed with the FMIDs, add the SOUCIDs of PP, and HIP to the APPLY command. There may be P or HIP APAs that do not have resolving PTFs available yet. You need to analyze the symptom flags to determine if you want to BYPASS the specific O HOLDs and continue the FMID installation. APPLY S(fmid,fmid,...) FOFMID(fmid,fmid,...) SOUCID(PP,HIP,...) GOUPXTND. This method requires more initial research, but will provide resolution for all HIPs that have fixes available and are not in a P chain. There may still be unresolved Ps or HIPs that require the use of BYPASS. 2. To install an FMID as it was installed prior to nhanced HOLDDATA, you can add a BYPASS(HOLDCLASS(HIP)) operand to the APPLY command. This allows the FMID to be installed even though there are HIP O HOLDs against it. Note that not all O HOLDs were bypassed, only the HIP O HOLDs. After the FMIDs are installed, you must run the SMP/ POT SYSMODS command to identify any missing HIP maintenance. APPLY S(fmid,fmid,...) BYPASS(HOLDCLASS(HIP)) other parameters documented in the program directory... This method is the quicker of the two, but requires subsequent review of the POT SYSMODS to investigate any HIPs. If you bypass any HOLDs during the installation of the FMIDs because PTFs were not yet available, you can use the APA Status Tracking (AST) function of ServiceLink or the APA Tracking function of esourcelink to be notified when the PTF is available. Installation Instructions 23

28 After you have taken any actions indicated by the APPLY CHCK, remove the CHCK operand and run the job again to perform the APPLY. Note: The GOUPXTND operand indicates that SMP/ apply all requisite SYSMODs. The requisite SYSMODS might be applicable to other functions. xpected eturn Codes and Messages from APPLY CHCK: 0 xpected eturn Codes and Messages from APPLY: 4 You can receive many of the following messages depending on your environment. GIM23903W LINK-DIT POCSSING FO SYSMOD aaaaaaaa WAS SUCCSSFUL FO MODUL bbbbbbbb IN LMOD cccccccc IN TH ddddddd LIBAY. TH TUN COD WAS ee. DAT yy.ddd - TIM hh:mm:ss - SQUNC NUMB nnnnnn. GIM23913W LINK-DIT POCSSING FO SYSMOD aaaaaaa WAS SUCCSSFUL FO MODUL bbbbbbbb IN LMOD cccccccc IN TH dddddddd LIBAY. TH TUN COD WAS ee. DAT yy.ddd -- TIM hh:mm:ss -- SQUNC NUMB nnnnnn -- SYSPINT FIL ffffffff. IW2454W SYMBOL symbol UNSOLVD. NO AUTOCALL (NCAL) SPCIFID. The following table contains a list of elements that might be marked as not selected during the APPLY and ACCPT processes. This occurs because a VSION parameter was supplied in an FMID indicating that it contained a higher level version of the same element provided by another FMID being processed at the same time. The higher version element is selected for processing and the lower version is not selected for processing. Figure 17. SMP/ lements Not Selected KAGCDSV KAGCXIT KAGCVCFG KAGSASTC KAGSDCFM KAGSSVU2 KAGSSYSV KDSBHLP KDSCBLD KDSCDSV KDSCXIT KDSCMGVS KDSCSLV KDSCTBX KDSDDICT KDSDINFO KDSHSLV KDSHSLW KDSHWN1 KDSHWN2 KDSLLIST KDSPSLV KDSPWN1 KDSSBATO KDSSDM KDSSUNF KDSSSVA0 KDSSSVU2 KDSSSYSV KDSZ00 KDSZ01 KDSZ02 KDSZ03 KDSZ04 KPDZ10 KALLIST 24 OMGAMON z/os Management Console Program Directory

29 Perform SMP/ ACCPT dit and submit sample job KHLA0ACC to perform an SMP/ ACCPT CHCK for OMGAMON z/os Management Console. Consult the instructions in the sample job for more information. To receive the full benefit of the SMP/ Causer SYSMOD Summary eport, do not bypass the following on the ACCPT CHCK: P, ID, Q, and IFQ. This is because the SMP/ root cause analysis identifies the cause only of OS and not of WANINGS (SYSMODs that are bypassed are treated as warnings, not errors, by SMP/). Before using SMP/ to load new distribution libraries, set the ACCJCLIN indicator in the distribution zone. This causes entries produced from JCLIN to be saved in the distribution zone whenever a SYSMOD containing inline JCLIN is accepted. For more information on the ACCJCLIN indicator, see the description of inline JCLIN in the SMP/ manuals. After you have taken any actions indicated by the ACCPT CHCK, remove the CHCK operand and run the job again to perform the ACCPT. Note: The GOUPXTND operand indicates that SMP/ accept all requisite SYSMODs. The requisite SYSMODS might be applicable to other functions. xpected eturn Codes and Messages from ACCPT CHCK: 0 If PTFs containing replacement modules are being accepted, SMP/ ACCPT processing linkedit/binds the modules into the distribution libraries. During this processing, the Linkage ditor or Binder can issue messages documenting unresolved external references, resulting in a return code of 4 from the ACCPT step. These messages can be ignored, because the distribution libraries are not executable and the unresolved external references will not affect the executable system libraries. xpected eturn Codes and Messages from ACCPT if no PTFs are being installed: 0 Figure 17 on page 24 contains a list of elements that might be marked as not selected during the APPLY and ACCPT processes. This occurs because a VSION parameter was supplied in an FMID indicating that it contained a higher level version of the same element provided by another FMID being processed at the same time. The higher version element is selected for processing and the lower version is not selected for processing. 6.2 Activating OMGAMON z/os Management Console The publication IBM OMGAMON z/os Management Console Planning, Installation, and Configuration Guide, GC contains the step-by-step procedures to activate the functions of OMGAMON z/os Management Console. This publication can be found online at: Installation Instructions 25

30 7.0 Notices eferences in this document to IBM products, programs, or services do not imply that IBM intends to make these available in all countries in which IBM operates. Any reference to an IBM product, program, or service is not intended to state or imply that only IBM's product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe on any of IBM's intellectual property rights may be used instead of the IBM product, program, or service. valuation and verification of operation in conjunction with other products, except those expressly designated by IBM, is the user's responsibility. APA numbers are provided in this document to assist in locating PTFs that may be required. Ongoing problem reporting may result in additional APAs being created. Therefore, the APA lists in this document may not be complete. To obtain current service recommendations and to identify current product service requirements, always contact the IBM Customer Support Center or use S/390 SoftwareXcel to obtain the current "PSP Bucket". IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to the IBM Director of Licensing IBM Corporation North Castle Drive Armonk, New York USA For online versions of this book, we authorize you to: Copy, modify, and print the documentation contained on the media, for use within your enterprise, provided you reproduce the copyright notice, all warning statements, and other required statements on each copy or partial copy. Transfer the original unaltered copy of the documentation when you transfer the related IBM product (which may be either machines you own, or programs, if the program's license terms permit a transfer). You must, at the same time, destroy all other copies of the documentation. You are responsible for payment of any taxes, including personal property taxes, resulting from this authorization. TH A NO WAANTIS, XPSS O IMPLID, INCLUDING TH WAANTIS OF MCHANTABILITY AND FITNSS FO A PATICULA PUPOS. Some jurisdictions do not allow the exclusion of implied warranties, so the above exclusion may not apply to you. 26 Copyright IBM Corp. 2006

31 Your failure to comply with the terms above terminates this authorization. Upon termination, you must destroy your machine readable documentation. 7.1 Trademarks The following terms are trademarks of the IBM Corporation in the United States or other countries or both: CBPDO IBM OS/390 edbooks TAIN SystemPac S/390 z/os OMGAMON Tivoli Tivoli nterprise The following terms are trademarks of other companies as follows: Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Notices 27

32 Contacting IBM Software Support For support for this or any Tivoli product, you can contact IBM Software Support in one of the following ways: Submit a problem management record (PM) electronically at IBMSV/IBMLINK. Submit a problem management record (PM) electronically from the support Web site at: You can also review the IBM Software Support Handbook, which is available on the Web site listed above. An nd of Support Matrix is provided that tells you when products you are using are nearing the end of support date for a particular version or release. When you contact IBM Software Support, be prepared to provide identification information for your company so that support personnel can readily assist you. Company identification information might also be needed to access various online services available on the Web site. The support Web site offers extensive information, including a guide to support services (the IBM Software Support Handbook); frequently asked questions (FAQs); and documentation for all Tivoli products, including elease Notes, edbooks, and white papers. The documentation for some product releases is available in both PDF and HTML formats. Translated documents are also available for some product releases. 28 OMGAMON z/os Management Console Program Directory