ibm fileibm program directory for ibm tivoli advanced catalog management for z/os v2.1.0 program...

IBMProgram Directory for

IBM Tivoli Advanced Catalog Management for z/OS

V2.1.0

Program Number 5698-A50

for Use withz/OS

Document Date: October 2007

GI11-8085-00

Note!

Before using this information and the product it supports, be sure to read the general information under 7.0, “Notices” onpage 26.

Copyright International Business Machines Corporation 2007. All rights reserved.Note to U.S. Government Users — Documentation related to restricted rights — Use, duplication or disclosure is subject torestrictions set forth in GSA ADP Schedule Contract with IBM Corp.

Contents

1.0 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1 Advanced Catalog Management for z/OS Description . . . . . . . . . . . . . . . . . . . . . . . . . . 21.2 Advanced Catalog Management for z/OS FMIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2.0 Program Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42.1 Basic Machine-Readable Material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42.2 Optional Machine-Readable Material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42.3 Program Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2.3.1 Basic Program Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42.3.2 Optional Program Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2.4 Program Source Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52.5 Publications Useful During Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

3.0 Program Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63.1 Program Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63.2 Preventive Service Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63.3 Statement of Support Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

4.0 Program and Service Level Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84.1 Program Level Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84.2 Service Level Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

5.0 Installation Requirements and Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95.1 Driving System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

5.1.1 Machine Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95.1.2 Programming Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

5.2 Target System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105.2.1 Machine Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105.2.2 Programming Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

5.2.2.1 Installation Requisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105.2.2.2 Operational Requisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115.2.2.3 Toleration/Coexistence Requisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115.2.2.4 Incompatibility (Negative) Requisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

5.2.3 DASD Storage Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125.2.4 DASD Storage Requirements by FMID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

5.3 FMIDs Deleted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175.4 Special Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

6.0 Installation Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196.1 Installing Advanced Catalog Management for z/OS . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

6.1.1 SMP/E Considerations for Installing Advanced Catalog Management for z/OS . . . . . . . . . 196.1.2 SMP/E Options Subentry Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Copyright IBM Corp. 2007 iii

6.1.3 SMP/E CALLLIBS Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206.1.4 Sample Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206.1.5 Create New SMP/E Support Files - Optional . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226.1.6 Create New SMP/E CSI - Optional . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226.1.7 Allocate SMP/E Target and Distribution Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . 236.1.8 Create DDDEF Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236.1.9 Perform SMP/E RECEIVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236.1.10 Perform SMP/E APPLY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236.1.11 Perform SMP/E ACCEPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

6.2 Activating Advanced Catalog Management for z/OS . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

7.0 Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267.1 Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Contacting IBM Software Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Figures

1. Basic Material: Unlicensed Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52. Publications Useful During Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53. PSP Upgrade and Subset ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64. Component IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75. Driving System Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96. Mandatory Installation Requisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107. Mandatory Operational Requisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118. Conditional Operational Requisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119. Total DASD Space Required by Advanced Catalog Management for z/OS . . . . . . . . . . . . . 12

10. Storage Requirements for SMP/E Work Data Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . 1311. Storage Requirements for SMP/E Data Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1412. Storage Requirements for Advanced Catalog Management for z/OS Target Libraries . . . . . . . 1413. Storage Requirements for Advanced Catalog Management for z/OS Distribution Libraries . . . . 1514. Storage Requirements for HCKM210 Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1615. Storage Requirements for HKRN210 Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1616. SMP/E Options Subentry Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1917. Sample Installation Jobs for base function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2018. Sample Installation Jobs for base and monitoring agent functions . . . . . . . . . . . . . . . . . . 21

iv Advanced Catalog Management for z/OS Program Directory

1.0 Introduction

This Program Directory is intended for the system programmer responsible for program installation andmaintenance. It contains information concerning the material and procedures associated with theinstallation of IBM Tivoli Advanced Catalog Management for z/OS. This publication refers to IBM TivoliAdvanced Catalog Management for z/OS as Advanced Catalog Management for z/OS.

The Program Directory contains the following sections:

� 2.0, “Program Materials” on page 4 identifies the basic and optional program materials anddocumentation for Advanced Catalog Management for z/OS.

� 3.0, “Program Support” on page 6 describes the IBM support available for Advanced CatalogManagement for z/OS.

� 4.0, “Program and Service Level Information” on page 8 lists the APARs (program level) and PTFs(service level) incorporated into Advanced Catalog Management for z/OS.

� 5.0, “Installation Requirements and Considerations” on page 9 identifies the resources andconsiderations required for installing and using Advanced Catalog Management for z/OS.

� 6.0, “Installation Instructions” on page 19 provides detailed installation instructions for AdvancedCatalog Management for z/OS. It also describes the procedures for activating the functions ofAdvanced Catalog Management for z/OS, or refers to appropriate publications.

Before installing Advanced Catalog Management for z/OS, read the CBPDO Memo To Users and theCBPDO Memo To Users Extension that were supplied with this program in softcopy form as well as thisProgram Directory and then keep them for future reference. Section 3.2, “Preventive Service Planning” onpage 6 tells you how to find any updates to the information and procedures in this Program Directory.

Advanced Catalog Management for z/OS is 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 tothe hardcopy form provided with your order. All service and HOLDDATA for Advanced CatalogManagement for z/OS are included on the CBPDO tape.

Do not use this Program Directory if you are installing Advanced Catalog Management for z/OS with aSystemPac or ServerPac. When using these offerings, use the jobs and documentation supplied with theoffering. This documentation provides references to specific sections of the Program Directory asrequired.

Prior to installing Advanced Catalog Management for z/OS, read IBM Tivoli Advanced CatalogManagement for z/OS: Monitoring Agent Planning and Configuration Guide. This book focuses on thethings you will need to know for a successful installation and configuration of this product.

Copyright IBM Corp. 2007 1

1.1 Advanced Catalog Management for z/OS Description

Advanced Catalog Management for z/OS offers powerful features to assist your organization with auditing,diagnosing, recovering, managing and maintaining access to your data assets, even in the event ofunforeseen problems ranging from human errors to natural disasters.

This solution offers the following functions to help manage your data:

� 24x7 data access

– Backup, recover and forward recover ICF catalogs and VVDS quickly, safely, andcomprehensively.

– Achieve significantly better VSAM performance and identify DASD space savings utilizing ourCA-by-CA MAP command for both VSAM and ICF catalogs.

– Clean hundreds of thousands of catalog entries in just a few minutes and save hours at therecovery site with our versatile CATSCRUB command.

– Audit your BCS, VVDS, and VTOC structures with "fix" commands automatically generated forcorrection of all identified error conditions.

– Backup and recover VSAM data sets; repair corrupted VSAM data sets.

– Effective day-to-day ICF catalog management

- Search using 90 data set attributes across catalogs, volumes, or system-wide

- Create data set reports from catalog and VTOC information, with greater ease and capabilitythan ever before

- SIMULATE major commands such as forward recovery or MERGECAT to documentprocedures and verify results before executing

- Ensure security of powerful catalog management commands utilizing the SAF security controls

- Utilize the Catalog Address Space (CAS) and the hardware coupling facility interfaces toguarantee ICF catalog integrity

- Utilize our familiar and easy-to-use ISPF interface to create commands and batch jobs

- Merge, split or clone catalogs at many times the speed of IDCAMS REPRO MERGECAT andrelax knowing you have full re-start or back-out capabilities

� Correlates entries in the tape management catalog with ICF catalogs. Identifies and resolves:

– Tape data not cataloged in tape management catalogs

– Tape data cataloged on tapes in scratch status

– Tape data cataloged in catalogs not connected to the master catalog

– Data in ICF catalogs not found in the tape management catalog

– Missing catalog records for tape data by building new entries

2 Advanced Catalog Management for z/OS Program Directory

1.2 Advanced Catalog Management for z/OS FMIDs

Advanced Catalog Management for z/OS consists of the following FMIDs (function modification identifiers):

HCKM210 HKRN210

Introduction 3

2.0 Program Materials

An IBM program is identified by a program number. The program number for Advanced CatalogManagement for z/OS is 5698-A50.

Basic Machine-Readable Materials are materials that are supplied under the base license and featurenumbers, and are required for the use of the product. Optional Machine-Readable Materials are orderableunder separate feature numbers, and are not required for the product to function.

The program announcement material describes the features supported by Advanced Catalog Managementfor z/OS. Ask your IBM representative for this information if you have not already received a copy.

2.1 Basic Machine-Readable Material

The distribution medium for this program is magnetic tape or downloadable files. It is installed usingSMP/E, and is in SMP/E RELFILE format. See 6.0, “Installation Instructions” on page 19 for moreinformation about how to install the program.

Information about the physical tape for the Basic Machine-Readable Materials for Advanced CatalogManagement for z/OS can be found in the CBPDO Memo To Users Extension.

2.2 Optional Machine-Readable Material

No optional machine-readable materials are provided for Advanced Catalog Management for z/OS.

2.3 Program Publications

The following sections identify the basic and optional publications for Advanced Catalog Management forz/OS.

2.3.1 Basic Program Publications

Figure 1 on page 5 identifies the basic unlicensed program publications for Advanced CatalogManagement for z/OS. One copy of each of these publications is included when you order the basicmaterials for Advanced Catalog Management for z/OS. You can print additional copies when electronicpublications are available using the softcopy url provided in the Product Announcement letter or from:

http://www.ibm.com/shop/publications/order

To install a monitoring server on z/OS, refer to the Program Directory for IBM Tivoli Monitoring Services(GI11-4105) for a complete list of publications and installation instructions for its product components.

4 Copyright IBM Corp. 2007

The Advanced Catalog Management for z/OS product manuals and other Tivoli product manuals can befound at the Tivoli Information Center url listed below:

http://publib.boulder.ibm.com/tividd/td/IBMTivolAdvancedCatalogManagementforzOS2.1.html

2.3.2 Optional Program Publications

No optional publications are provided for Advanced Catalog Management for z/OS.

2.4 Program Source Materials

No program source materials or viewable program listings are provided for Advanced CatalogManagement for z/OS.

2.5 Publications Useful During Installation

The publications listed in Figure 2 can be useful during the installation of Advanced Catalog Managementfor z/OS. To order copies, contact your IBM representative or visit the IBM Publications Center at thefollowing Web site:

http://www.ibm.com/shop/publications/order

Figure 1. Basic Material: Unlicensed Publications

Publication TitleForm

Number

IBM Tivoli Advanced Catalog Management for z/OS: User's Guide SC23-7973

IBM Tivoli Advanced Catalog Management for z/OS: Monitoring Agent User's Guide SC23-7974

IBM Tivoli Advanced Catalog Management for z/OS: Monitoring Agent Planning andConfiguration Guide

SC23-7975

Figure 2. Publications Useful During Installation

Publication TitleForm

Number

IBM SMP/E for z/OS and OS/390 User's Guide SA22-7773

IBM SMP/E for z/OS and OS/390 Commands SA22-7771

IBM SMP/E for z/OS and OS/390 Reference SA22-7772

IBM SMP/E for z/OS and OS/390 Messages, Codes, and Diagnosis GA22-7770

Program Materials 5

3.0 Program Support

This section describes the IBM support available for Advanced Catalog Management for z/OS.

3.1 Program Services

Contact your IBM representative for specific information about available program services. You can findinformation in the IBM Software Support Handbook at the following Web site:

http://techsupport.services.ibm.com/guides/handbook.html

The handbook provides information about how to contact IBM Software Support, depending on theseverity of your problem, and the following information:

� Registration and eligibility� Telephone numbers and e-mail 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 Advanced Catalog Management for z/OS, it is VERY IMPORTANT that you review thecurrent Preventive Service Planning (PSP) information. The PSP buckets maintain current lists (whichhave been identified since the package was created) of any recommended or required service for thispackage's installation. This includes software PSP information that contains HIPER, special attentionand/or required PTFs against the base release.

For program support, access the Software Support Web site at:

http://www.ibm.com/software/support/

PSP Buckets are identified by UPGRADEs, which specify product levels, and SUBSETs, which specify theFMIDs for a product level. The UPGRADE and SUBSET values for Advanced Catalog Management forz/OS are included in Figure 3.

Figure 3. PSP Upgrade and Subset ID

UPGRADE SUBSET Description

ACM4ZOS HCKM210 Advanced Catalog Management base

HKRN210 Advanced Catalog Management monitoring agent


3.3 Statement of Support Procedures

Report any difficulties you have using this program to IBM Software Support. If an APAR is required, theywill provide the address to which any needed documentation can be sent.

Figure 4 on page 7 identifies the component IDs (COMPID) for Advanced Catalog Management for z/OS.

Figure 4. Component IDs

FMID COMPID Component NameRETAINRelease

HCKM210 5698A9500 Advanced Catalog Management base 210

HKRN210 5698A9501 Advanced Catalog Management monitoring agent 210

Program Support 7

4.0 Program and Service Level Information

This section identifies the program and any relevant service levels of Advanced Catalog Management forz/OS. The program level refers to the APAR fixes incorporated into the program. The service level refersto the PTFs incorporated into the program.

4.1 Program Level Information

No APARs have been incorporated into Advanced Catalog Management for z/OS.

4.2 Service Level Information

No PTFs against this release of Advanced Catalog Management for z/OS have been incorporated into theproduct tape.


5.0 Installation Requirements and Considerations

The following sections identify the system requirements for installing and activating Advanced CatalogManagement for z/OS. The following terminology is used:

� Driving system: the system used to install the program.

� Target system: the system on which the program is intended to run.

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-ablecopy of the running system. The clone must include copies of all system libraries that SMP/E updates,copies of the SMP/E CSI data sets that describe the system libraries, and your PARMLIB and PROCLIB.

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 oldone. By installing onto a separate target system, you can test the new product while still keeping theold one in production.

� When installing a product that shares libraries or load modules with other products, the installation candisrupt the other products. Installing onto a test system or clone will allow you to assess theseimpacts without disrupting your production system.

5.1 Driving System Requirements

This section describes the environment of the driving system required to install Advanced CatalogManagement for z/OS.

5.1.1 Machine Requirements

The driving system can run in any hardware environment that supports the required software.

5.1.2 Programming Requirements

Figure 5. Driving System Software Requirements

ProgramNumber

Product Name andMinimum VRM/Service Level

Any one of the following:

5694-A01 z/OS V1.7 or later

5655-G44 IBM SMP/E for z/OS V3.3 or later


5.2 Target System Requirements

This section describes the environment of the target system required to install and use Advanced CatalogManagement for z/OS.

Advanced Catalog Management for z/OS installs in the z/OS (Z038) SREL.

5.2.1 Machine Requirements

The target system can run in any hardware environment that supports the required software.

5.2.2 Programming Requirements

5.2.2.1 Installation Requisites

An installation requisite is defined as a product that is required and must be present or one that is notrequired 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 productwill not install on your system. This includes products specified as PREs or REQs.

The installation of the Advanced Catalog Management monitoring agent, HKRN210 FMID, requires theTivoli Enterprise Monitoring Server on z/OS be present or installed in the CSI. Refer to the ProgramDirectory for IBM Tivoli Monitoring Services (GI11-4105) for a complete list of publications and installationinstructions for its product components.

A conditional installation requisite identifies products that are not required for successful install but mayresolve such things as certain warning messages at installation time. They include products that arespecified as IF REQs.

Advanced Catalog Management for z/OS has no conditional installation requisites.

Figure 6. Mandatory Installation Requisites

ProgramNumber



5698-A79 IBM Tivoli Monitoring Services V6.1 or later


5.2.2.2 Operational Requisites

An operational requisite is defined as a product that is required and must be present or a product that isnot 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 productwill not operate its basic function unless the requisite is met. This includes products specified as PREs orREQs.

A conditional operational requisite identifies products that are not required for the basic function but areneeded at run time for this product to utilize specific functions. They can include products specified as IFREQs.

The use of the Advanced Catalog Management monitoring agent component with a Tivoli EnterpriseMonitoring Server on z/OS requires the monitoring server be installed and operational.

5.2.2.3 Toleration/Coexistence Requisites

A toleration/coexistence requisite is defined as a product that must be present on a shared system. Thesesystems can be other systems in a multisystem environment (not necessarily sysplex), a shared DASDenvironment (such as test and production), or systems that reuse the same DASD at different timeintervals.

Advanced Catalog Management for z/OS has no toleration/coexistence requisites.

5.2.2.4 Incompatibility (Negative) Requisites

A negative requisite identifies products that must not be installed on the same system as this product.

Advanced Catalog Management for z/OS has no negative requisites.

Figure 7. Mandatory Operational Requisites

ProgramNumber



Figure 8. Conditional Operational Requisites

ProgramNumber

Product Name andMinimum VRM/Service Level Function

5698-A79 IBM Tivoli Monitoring Services V6.1 orlater

Monitoring services

Installation Requirements and Considerations 11

5.2.3 DASD Storage Requirements

Advanced Catalog Management for z/OS libraries can reside on all supported DASD types.

Figure 9 on page 12 lists the total space required for each type of library.

Notes:

1. If you are installing into an existing environment that has the data sets in Figure 12 on page 14 andFigure 13 on page 15 already allocated, ensure sufficient disk space and directory blocks areavailable to support the requirement listed. This might require you to reallocate some data sets toavoid x37 abends.

2. Use system determined block sizes for efficient DASD utilization for all non-RECFM U data sets. ForRECFM U data sets, a block size of 32760 is recommended, which is the most efficient from aperformance and DASD utilization perspective.

3. The following abbreviations are used for the data set type:

U Unique data set, allocated by this product and used only by this product. To determine thecorrect storage needed for this data set, this table provides all required information; no othertables (or program directories) need to be referenced for the data set size.

S Shared data set, allocated by this product and used by this product and others. To determinethe correct storage needed for this data set, the storage size given in this table needs to beadded to other tables (perhaps in other program directories). If the data set already exists, itmust have enough free space to accommodate the storage size given in this table.

E Existing shared data set, used by this product and others. This data set is NOT allocated bythis product. To determine the correct storage needed for this data set, the storage size givenin this table needs to be added to other tables (perhaps in other program directories). Thisexisting data set must have enough free space to accommodate the storage size given in thistable.

If you currently have a previous release of this product installed in these libraries, the installation ofthis release will delete the old one and reclaim the space used by the old release and any service thathad been installed. You can determine whether or not these libraries have enough space by deletingthe old release with a dummy function, compressing the libraries, and comparing the spacerequirements 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, “AllocateSMP/E Target and Distribution Libraries” on page 23.

4. All target and distribution libraries listed have the following attributes:

Figure 9. Total DASD Space Required by Advanced Catalog Management for z/OS

LibraryType Total Space Required

Target 770 tracks of 3390

Distribution 758 tracks of 3390


� 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.

5. All target libraries listed have the following attributes:

� 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/E 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.

If you are installing into an existing environment, ensure the values used for the SMP/E work datasetsreflect the minimum values shown in Figure 10. Check the corresponding DDDEF entries in all zonesbecause use of values lower than these can result in failures in the installation process. Refer to theSMP/E manuals for instructions on updating DDDEF entries.

If you are installing into an existing environment, ensure the current SMP/E support dataset allocationsreflect the minimum values shown in Figure 11. Check the space and directory block allocation andreallocate the data sets, if necessary.

Figure 10. Storage Requirements for SMP/E Work Data Sets

LibraryDDNAME

TYPE

ORG

RECFM

LRECL

PrimNo.of

3390Trks

SecNo.of

3390Trks

No.of

DIRBlks

SMPWRK1 S PDS FB 80 150 150 220

SMPWRK2 S PDS FB 80 150 150 220

SMPWRK3 S PDS FB 80 300 600 1320

SMPWRK4 S PDS FB 80 150 150 220

SMPWRK6 S PDS FB 80 300 1500 660

SYSUT1 U SEQ -- -- 75 75 0

SYSUT2 U SEQ -- -- 75 75 0

SYSUT3 U SEQ -- -- 75 75 0

SYSUT4 U SEQ -- -- 75 75 0


Figure 12 and Figure 13 on page 15 describe the target and distribution libraries required to installAdvanced Catalog Management for z/OS in a standalone environment. The storage requirements ofAdvanced Catalog Management for z/OS must be added to the storage required by other programs havingdata in the same library or path when installing into an existing environment. Additional tables for eachFMID are provided to help determine the specific space required for a FMID if some common componentsare already installed. See 5.2.4, “DASD Storage Requirements by FMID” on page 15 for moreinformation.

Figure 11. Storage Requirements for SMP/E Data Sets

LibraryDDNAME

TYPE

ORG

RECFM

LRECL

PrimNo.of

3390Trks

SecNo.of

3390Trks

No.of

DIRBlks

SMPLTS E PDSE U 0 15 150 220

SMPMTS E PDS FB 80 15 150 220

SMPPTS E PDSE FB 80 300 1500 660

SMPSCDS E PDS FB 80 15 150 220

SMPSTS E PDS FB 80 15 150 220

Figure 12 (Page 1 of 2). Storage Requirements for Advanced Catalog Management for z/OS Target Libraries

LibraryDDNAME

MemberType

TargetVolume

TYPE

ORG

RECFM

LRECL

No.of

3390Trks

No.of

DIRBlks

SCKMCNTL DATA Any U PDS FB 80 19 44

SCKMLOAD LMOD Any U PDSE U 0 221 N/A

SCKMMENU MESSAGE Any U PDS FB 80 3 44

SCKMMSGS DATA Any U PDS FB 80 58 44

SCKMPARM DATA Any U PDS FB 80 14 44

SCKMPENU PANEL Any U PDS FB 80 95 220

SCKMPKGI DATA Any U PDS FB 80 11 44

TKANCUS CLIST Any E PDS FB 80 10 44

TKANDATV DATA Any E PDS VB 6160 2 44

TKANMOD LMOD Any E PDS U 0 14 44

TKANMODL LMOD Any E PDS U 0 287 44

TKANMODP LMOD Any S PDSE U 0 29 N/A

TKANPAR DATA Any E PDS FB 80 1 44


5.2.4 DASD Storage Requirements by FMID

The tables in this section can help determine the specific space required for components not alreadyinstalled in an existing environment. There is a table for each FMID included with the product.

Figure 12 (Page 2 of 2). Storage Requirements for Advanced Catalog Management for z/OS Target Libraries

LibraryDDNAME

MemberType

TargetVolume

TYPE

ORG

RECFM

LRECL

No.of

3390Trks

No.of

DIRBlks

TKANPKGI DATA Any E PDS FB 80 5 44

TKANUTIN UTIN Any S PDS FB 80 1 44

Figure 13. Storage Requirements for Advanced Catalog Management for z/OS Distribution Libraries

LibraryDDNAME

TYPE

ORG

RECFM

LRECL

No.of

3390Trks

No.of

DIRBlks

ACKMCNTL U PDS FB 80 19 44

ACKMLOAD U PDSE U 0 221 N/A

ACKMMENU U PDS FB 80 3 44

ACKMMSGS U PDS FB 80 58 44

ACKMPARM U PDS FB 80 11 44

ACKMPENU U PDS FB 80 95 220

ACKMPKGI U PDS FB 80 11 44

DKANCUS E PDS FB 80 10 44

DKANDATV E PDS VB 6160 2 44

DKANMOD E PDS U 0 19 44

DKANMODL E PDS U 0 287 44

DKANMODP S PDSE U 0 12 N/A

DKANPAR E PDS FB 80 1 44

DKANPKGI E PDS FB 80 5 44

DKANUTIN S PDS FB 80 1 44


Figure 14. Storage Requirements for HCKM210 Libraries

LibraryDDNAME

MemberType

TargetVolume

TYPE

ORG

RECFM

LRECL

No.of

3390Trks

No.of

DIRBlks

SCKMCNTL DATA Any U PDS FB 80 8 10

SCKMLOAD LMOD Any U PDSE U 0 196 N/A

SCKMMENU MESSAGE Any U PDS FB 80 2 4

SCKMMSGS DATA Any U PDS FB 80 51 25

SCKMPARM DATA Any U PDS FB 80 13 28

SCKMPENU PANEL Any U PDS FB 80 83 140

SCKMPKGI DATA Any U PDS FB 80 10 2

ACKMCNTL U PDS FB 80 8 10

ACKMLOAD U PDSE U 0 196 N/A

ACKMMENU U PDS FB 80 2 4

ACKMMSGS U PDS FB 80 51 25

ACKMPARM U PDS FB 80 13 28

ACKMPENU U PDS FB 80 83 140

ACKMPKGI U PDS FB 80 10 2

Figure 15 (Page 1 of 2). Storage Requirements for HKRN210 Libraries

LibraryDDNAME

MemberType

TargetVolume

TYPE

ORG

RECFM

LRECL

No.of

3390Trks

No.of

DIRBlks

TKANCUS CLIST Any E PDS FB 80 10 8

TKANDATV DATA Any E PDS VB 6160 2 2

TKANMOD LMOD Any E PDS U 0 14 12

TKANMODL LMOD Any E PDS U 0 287 2

TKANMODP LMOD Any S PDSE U 0 29 N/A

TKANPAR DATA Any E PDS FB 80 1 2

TKANPKGI DATA Any E PDS FB 80 5 2

TKANUTIN UTIN Any S PDS FB 80 1 2

DKANCUS E PDS FB 80 10 8

DKANDATV E PDS VB 6160 2 2


5.3 FMIDs Deleted

Installing Advanced Catalog Management for z/OS may result in the deletion of other FMIDs. To see whatFMIDs will be deleted, examine the ++VER statement in the product's SMPMCS.

If you do not want to delete these FMIDs at this time, you must install Advanced Catalog Management forz/OS into separate SMP/E target and distribution zones.

Note: These FMIDs will not automatically be deleted from the Global Zone. Consult the SMP/E manualsfor instructions on how to delete FMIDs from the Global Zone.

5.4 Special Considerations

To effectively manage a suite of products with common components, you can install products into ashared consolidated software inventory (CSI). Space requirements are reduced by installing products intoa shared CSI avoiding the duplication when different target zones, distribution zones, and data sets areused. Sharing a common set of zones also allows SMP/E to automatically manage IFREQ situations thatexist across product components.

If you intend to share a Tivoli Enterprise Monitoring Server on z/OS with other products, use a shared CSIso product configuration sets up the runtime environment correctly.

The installation of the Advanced Catalog Management monitoring Agent, HKRN210 FMID, requires theTivoli Enterprise Monitoring Server on z/OS be installed in the CSI. If it is already installed, ensure thelatest maintenance is installed as well because Advanced Catalog Management for z/OS requiresmaintenance for some of the components included with the monitoring server package. If it is not alreadyinstalled, the monitoring server components and maintenance should be installed first. Refer to theProgram Directory for IBM Tivoli Monitoring Services (GI11-4105) for installation instructions of its productcomponents.

Figure 15 (Page 2 of 2). Storage Requirements for HKRN210 Libraries

LibraryDDNAME

MemberType

TargetVolume

TYPE

ORG

RECFM

LRECL

No.of

3390Trks

No.of

DIRBlks

DKANMOD E PDS U 0 19 21

DKANMODL E PDS U 0 287 2

DKANMODP S PDSE U 0 12 N/A

DKANPAR E PDS FB 80 1 2

DKANPKGI E PDS FB 80 5 2

DKANUTIN S PDS FB 80 1 2


Consider the following issues, if you use a shared CSI.

� If you install a product into an existing CSI that contains a previous version of the same product,SMP/E deletes the previous version during the installation process. To maintain multiple productversions concurrently, they must be installed into separate CSI zones.

� If you install into an existing environment, you might need to remove data set references from theinstallation 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, ensuresufficient space and directory blocks are available to support the requirement listed in the DASDtables. This might require you to reallocate some data sets to avoid x37 abends.


6.0 Installation Instructions

This chapter describes the installation method and the step-by-step procedures to install and to activatethe functions of Advanced Catalog Management for z/OS.

Note the following information:

� If you want to install Advanced Catalog Management for z/OS into its own SMP/E environment,consult the SMP/E manuals for instructions on creating and initializing the SMPCSI and the SMP/Econtrol data sets. Additionally, to assist you in doing this, IBM has provided samples to help youcreate an SMP/E environment at the following Web site. A copy of these has also been included withthe other sample jobs.

http://www.ibm.com/support/docview.wss?rs=660&context=SSZJDU&uid=swg21066230

� Sample jobs have been provided to help perform some or all of the installation tasks. The SMP/E jobsassume that all DDDEF entries required for SMP/E execution have been defined in the appropriatezones.

� The SMP/E dialogs can be used instead of the sample jobs to accomplish the SMP/E installationsteps.

6.1 Installing Advanced Catalog Management for z/OS

6.1.1 SMP/E Considerations for Installing Advanced CatalogManagement for z/OS

This release of Advanced Catalog Management for z/OS is installed using the SMP/E RECEIVE, APPLY,and ACCEPT commands. The SMP/E dialogs can be used to accomplish the SMP/E installation steps.

6.1.2 SMP/E Options Subentry Values

The suggested values for some SMP/E CSI subentries are shown in Figure 16. If you are installing intoan existing environment, check these values because use of values lower than these can result in failuresin the installation process. DSSPACE is a subentry in the GLOBAL options entry. PEMAX is a subentryof the GENERAL entry in the GLOBAL options entry. Refer to the SMP/E manuals for instructions onupdating the global zone.

Figure 16. SMP/E Options Subentry Values

SUB-ENTRY Value Comment

DSSPACE 300,600,1200 Use 1200 directory blocks

PEMAX SMP/E Default Use the SMP/E default for PEMAX.


6.1.3 SMP/E CALLLIBS Processing

Advanced Catalog Management for z/OS monitoring agent, HKRN210 FMID, uses the CALLLIBS functionprovided in SMP/E to resolve external references during installation. When Advanced CatalogManagement for z/OS monitoring agent is installed, ensure DDDEFs exist for the following libraries:

� SCEEBIND � SCEELIB � SCEELKED

Advanced Catalog Management for z/OS base, HCKM210 FMID, uses the CALLLIBS function provided inSMP/E to resolve external references during installation. When Advanced Catalog Management for z/OSbase is installed, ensure a DDDEF exists for the following library:

� CSSLIB

Note: The DDDEFs above are used only to resolve the link-edit for Advanced Catalog Management forz/OS using CALLLIBS. These data sets are not updated during the installation of Advanced CatalogManagement for z/OS.

6.1.4 Sample Jobs

There are two sets of sample installation jobs provided as part of the product. The sample installationjobs in Figure 17 are to help you install only the base function of Advanced Catalog Management forz/OS. To install both the base and monitoring agent functions, use the sample installation jobs inFigure 18 on page 21.

The installation of the Advanced Catalog Management monitoring agent, HKRN210 FMID, requires theTivoli Enterprise Monitoring Server on z/OS be installed in the CSI. If it is already installed, ensure thelatest maintenance is installed as well because Advanced Catalog Management for z/OS requiresmaintenance for some of the components included with the monitoring server package. If it is not alreadyinstalled, the monitoring server components and maintenance should be installed first. Refer to the

Figure 17. Sample Installation Jobs for base function

Job Name Job Type Description RELFILE

CKMJ0SMA Optional Sample job to create new SMP/E support files IBM.HCKM210.F8

CKMJ0SMI Optional Sample job to create and prime a new SMP/E CSI IBM.HCKM210.F8

CKMJ0ALO ALLOCATE Sample job to allocate target and distributionlibraries

IBM.HCKM210.F8

CKMJ0DDF DDDEF Sample job to define SMP/E DDDEFs IBM.HCKM210.F8

CKMJ0REC RECEIVE Sample RECEIVE job IBM.HCKM210.F8

CKMJ0APP APPLY Sample APPLY job IBM.HCKM210.F8

CKMJ0ACC ACCEPT Sample ACCEPT job IBM.HCKM210.F8


Program Directory for IBM Tivoli Monitoring Services (GI11-4105) for installation instructions of its productcomponents.

You can access the sample installation jobs by performing an SMP/E RECEIVE (refer to 6.1.9, “PerformSMP/E RECEIVE” on page 23), then copy the jobs from the relfiles to a work data set for editing andsubmission. See Figure 17 on page 20 or Figure 18 to find the appropriate relfile data set.

You may also choose to copy the jobs from the tape or product files by creating and submitting the jobbelow. Use one of the //TAPEIN or //FILEIN DD statements, depending on your distribution medium. Ifyou intend to install only the base function, uncomment the appropriate statement containingIBM.HCKM210.F8 for the input dataset. If you intend to install both base and monitoring agent functions,uncomment the appropriate statement containing IBM.HKRN210.F9 for the input dataset. Add a job cardand change the lowercase parameters to uppercase values to meet your site's requirements beforesubmitting.

//STEP1 EXEC PGM=IEBCOPY

//SYSPRINT DD SYSOUT=�

//�TAPEIN DD DSN=IBM.HCKM21�.F8,UNIT=tunit,//�TAPEIN DD DSN=IBM.HKRN21�.F9,UNIT=tunit,//� VOL=SER=volser,LABEL=(x,SL),//� DISP=(OLD,KEEP)

//�FILEIN DD DSN=IBM.HCKM21�.F8,UNIT=SYSALLDA,DISP=SHR,

//�FILEIN DD DSN=IBM.HKRN21�.F9,UNIT=SYSALLDA,DISP=SHR,

//� VOL=SER=filevol//OUT DD DSNAME=jcl-library-name,// DISP=(NEW,CATLG,DELETE),

// VOL=SER=dasdvol,UNIT=SYSALLDA,// SPACE=(TRK,(1�,2,5))

//SYSUT3 DD UNIT=SYSALLDA,SPACE=(CYL,(1,1))

//SYSIN DD �

COPY INDD=xxxxIN,OUTDD=OUT SELECT MEMBER=(CKMJ�ACC,CKMJ�ALO,CKMJ�APP,CKMJ�DDF,CKMJ�REC)

SELECT MEMBER=(CKMJ�SMA,CKMJ�SMI)

SELECT MEMBER=(KRNJ�ACC,KRNJ�ALO,KRNJ�APP,KRNJ�DDF,KRNJ�REC)

Figure 18. Sample Installation Jobs for base and monitoring agent functions

Job Name Job Type Description RELFILE

KRNJ0SMA Optional Sample job to create new SMP/E support files IBM.HKRN210.F9

KRNJ0SMI Optional Sample job to create and prime a new SMP/E CSI IBM.HKRN210.F9

KRNJ0ALO ALLOCATE Sample job to allocate target and distributionlibraries

IBM.HKRN210.F9

KRNJ0DDF DDDEF Sample job to define SMP/E DDDEFs IBM.HKRN210.F9

KRNJ0REC RECEIVE Sample RECEIVE job IBM.HKRN210.F9

KRNJ0APP APPLY Sample APPLY job IBM.HKRN210.F9

KRNJ0ACC ACCEPT Sample ACCEPT job IBM.HKRN210.F9

Installation Instructions 21

SELECT MEMBER=(KRNJ�SMA,KRNJ�SMI)

/�

In the sample above, update the statements as noted below:

If using TAPEIN:tunit is the unit value matching the product tape.volser is the volume serial matching the product tape.x is the tape file number where the data set name is on the tape.Refer to the documentation provided by CBPDO to see where the file of your choice is on thetape.

If using FILEINfilevol is the volume serial of the DASD device where the downloaded files reside.

OUTjcl-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.

SYSINChange xxxxIN to either TAPEIN or FILEIN depending on which input DD statement you chose touncomment for use.If you chose to uncomment a statement containing IBM.HCKM210.F8 for the input dataset, keepthe Select statements for members starting with CKM and delete the others.If you chose to uncomment a statement containing IBM.HKRN210.F9 for the input dataset, keepthe Select statements for members starting with KRN and delete the others.

6.1.5 Create New SMP/E Support Files - Optional

If you do not want to install into an existing environment, you can create a new environment. To allocatenew SMP/E support data sets for Advanced Catalog Management for z/OS installation, edit and submitsample job CKMJ0SMA OR KRNJ0SMA. Consult the instructions in the sample job for more information.

Expected Return Codes and Messages: 0

6.1.6 Create New SMP/E CSI - Optional

If you do not want to install into an existing environment, you can create a new environment. To allocatea new SMP/E CSI and prime it for Advanced Catalog Management for z/OS installation, edit and submitsample job CKMJ0SMI OR KRNJ0SMI. Consult the instructions in the sample job for more information.



6.1.7 Allocate SMP/E Target and Distribution Libraries

If you are installing into an existing environment, you might have to remove lines for data sets that alreadyexist. Edit and submit sample job CKMJ0ALO OR KRNJ0ALO to allocate the SMP/E target anddistribution libraries for Advanced Catalog Management for z/OS. Consult the instructions in the samplejob for more information.

If you are installing into an existing environment that has the data sets already allocated, ensure sufficientspace and directory blocks are available to support the requirement listed in the DASD tables. This mightrequire you to reallocate some data sets to avoid x37 abends.


6.1.8 Create DDDEF Entries

If you are installing into an existing environment, you might have to remove lines for data sets that alreadyexist. Edit and submit sample job CKMJ0DDF or KRNJ0DDF to create DDDEF entries for the SMP/Etarget and distribution libraries for Advanced Catalog Management for z/OS. Consult the instructions inthe sample job for more information.


6.1.9 Perform SMP/E RECEIVE

Having obtained Advanced Catalog Management for z/OS as part of a CBPDO, you can use the RCVPDOjob found in the CBPDO RIMLIB data set to RECEIVE the Advanced Catalog Management for z/OSFMIDs as well as any service and HOLDDATA included on the CBPDO tape. For more information, referto the documentation included with the CBPDO.

You can also choose to edit and submit sample job CKMJ0REC or KRNJ0REC to perform the SMP/ERECEIVE for Advanced Catalog Management for z/OS. Consult the instructions in the sample job formore information.


6.1.10 Perform SMP/E APPLY

Edit and submit sample job CKMJ0APP or KRNJ0APP to perform an SMP/E APPLY CHECK forAdvanced Catalog Management for z/OS. Add a BYPASS(HOLDSYSTEM) operand to the SMP/E controlstatments in the APPLY job and uncomment the CHECK operand to see which PTFs will be processedbecause the ++HOLD is bypassed. Consult the instructions in the sample job for more information.

To receive the full benefit of the SMP/E Causer SYSMOD Summary Report, do not bypass the followingon the APPLY CHECK: PRE, ID, REQ, and IFREQ. This is because the SMP/E root cause analysis


identifies the cause only of ERRORS and not of WARNINGS (SYSMODs that are bypassed are treatedas warnings, not errors, by SMP/E).

Enhanced HOLDDATA introduced ERROR HOLDs against FMIDs for HIPER APARs. Prior to installing,ensure you have the latest Enhanced HOLDDATA (available athttp://service.software.ibm.com/holdata/390holddata.html). The FMIDs can be installed regardless of thestatus of unresolved HIPERs, however, the software must not be deployed until the unresolved HIPERshave been analyzed to determine applicability.

There are two methods to complete an FMID installation where ++HOLDs for HIPERs exist for the FMIDsbeing installed:

1. To ensure that all recommended and critical service is installed with the FMIDs, add the SOURCEIDsof PRP, HIPER, and RSU* to the APPLY command. There may be PE or HIPER APARs that do nothave resolving PTFs available yet. You need to analyze the symptom flags to determine if you wantto BYPASS the specific ERROR HOLDs and continue the FMID installation.

APPLY S(fmid,fmid,...)

FORFMID(fmid,fmid,...)

SOURCEID(PRP,HIPER,RSU�,...)

GROUPEXTEND .

This method requires more initial research, but will provide resolution for all HIPERs that have fixesavailable and are not in a PE chain. There may still be unresolved PEs or HIPERs that require theuse of BYPASS.

2. To install an FMID as it was installed prior to Enhanced HOLDDATA, you can add aBYPASS(HOLDCLASS(HIPER)) operand to the APPLY command. This allows the FMID to beinstalled even though there are HIPER ERROR HOLDs against it. Note that not all ERROR HOLDswere bypassed, only the HIPER ERROR HOLDs. After the FMIDs are installed, you must run theSMP/E REPORT ERRSYSMODS command to identify any missing HIPER maintenance.

APPLY S(fmid,fmid,...)

FORFMID(fmid,fmid,...)

SOURCEID(RSU�)

GROUPEXTEND

BYPASS(HOLDCLASS(HIPER))

other parameters documented in the program directory...

This method is the quicker of the two, but requires subsequent review of the REPORT ERRSYSMODSto investigate any HIPERs.

If you bypass any HOLDs during the installation of the FMIDs because fixing PTFs were not yet available,you can use the APAR Status Tracking (AST) function of ServiceLink or the APAR Tracking function ofResourceLink to be notified when the fixing PTF is available.

After you have taken any actions indicated by the APPLY CHECK, remove the CHECK operand and runthe job again to perform the APPLY.

Note: The GROUPEXTEND operand indicates that SMP/E apply all requisite SYSMODs. The requisiteSYSMODS might be applicable to other functions.


Expected Return Codes and Messages from APPLY CHECK: 0

Expected Return Codes and Messages from APPLY: 0

6.1.11 Perform SMP/E ACCEPT

Edit and submit sample job CKMJ0ACC or KRNJ0ACC to perform an SMP/E ACCEPT CHECK forAdvanced Catalog Management for z/OS. Add a BYPASS(HOLDSYSTEM) operand to the SMP/E controlstatments in the ACCEPT job and uncomment the CHECK operand to see which PTFs will be processedbecause the ++HOLD is bypassed. Consult the instructions in the sample job for more information.

To receive the full benefit of the SMP/E Causer SYSMOD Summary Report, do not bypass the followingon the ACCEPT CHECK: PRE, ID, REQ, and IFREQ. This is because the SMP/E root cause analysisidentifies the cause only of ERRORS and not of WARNINGS (SYSMODs that are bypassed are treatedas warnings, not errors, by SMP/E).

Before using SMP/E 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 SYSMODcontaining inline JCLIN is accepted. For more information on the ACCJCLIN indicator, see the descriptionof inline JCLIN in the SMP/E manuals.

After you have taken any actions indicated by the ACCEPT CHECK, remove the CHECK operand and runthe job again to perform the ACCEPT.

Note: The GROUPEXTEND operand indicates that SMP/E accept all requisite SYSMODs. The requisiteSYSMODS might be applicable to other functions.

Expected Return Codes and Messages from ACCEPT CHECK: 0

If PTFs containing replacement modules are being accepted, SMP/E ACCEPT processing linkedit/bindsthe modules into the distribution libraries. During this processing, the Linkage Editor or Binder can issuemessages documenting unresolved external references, resulting in a return code of 4 from the ACCEPTstep. These messages can be ignored, because the distribution libraries are not executable and theunresolved external references will not affect the executable system libraries.

Expected Return Codes and Messages from ACCEPT:0

6.2 Activating Advanced Catalog Management for z/OS

The publication IBM Tivoli Advanced Catalog Management for z/OS: Monitoring Agent Planning andConfiguration Guide, SC23-7975 contains the step-by-step procedures to activate the functions ofAdvanced Catalog Management for z/OS. This publication can be found online at:

http://publib.boulder.ibm.com/tividd/td/IBMTivolAdvancedCatalogManagementforzOS2.1.html


7.0 Notices

References in this document to IBM products, programs, or services do not imply that IBM intends tomake 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. Anyfunctionally equivalent product, program, or service that does not infringe on any of IBM's intellectualproperty rights may be used instead of the IBM product, program, or service. Evaluation and verificationof operation in conjunction with other products, except those expressly designated by IBM, is the user'sresponsibility.

APAR numbers are provided in this document to assist in locating PTFs that may be required. Ongoingproblem reporting may result in additional APARs being created. Therefore, the APAR lists in thisdocument may not be complete. To obtain current service recommendations and to identify currentproduct service requirements, always contact the IBM Customer Support Center or use S/390SoftwareXcel to obtain the current "PSP Bucket".

IBM may have patents or pending patent applications covering subject matter in this document. Thefurnishing of this document does not give you any license to these patents. You can send licenseinquiries, in writing, to the

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, New York 10504-1785USA

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 oneach 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 atransfer). 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 thisauthorization.

THERE ARE NO WARRANTIES, EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OFMERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

Some jurisdictions do not allow the exclusion of implied warranties, so the above exclusion may not applyto you.


Your failure to comply with the terms above terminates this authorization. Upon termination, you mustdestroy 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:

CBPDOIBMOS/390Redbooks

RETAINSystemPacS/390z/OS

TivoliTivoli Enterprise

The following terms are trademarks of other companies as follows:

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in theUnited States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Notices 27

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 (PMR) electronically at IBMSERV/IBMLINK.

Submit a problem management record (PMR) electronically from the support Web site at:

http://www.ibm.com/software/sysmgmt/products/support/

You can also review the IBM Software Support Handbook, which is available on the Web site listed above. An End ofSupport Matrix is provided that tells you when products you are using are nearing the end of support date for aparticular version or release.

When you contact IBM Software Support, be prepared to provide identification information for your company so thatsupport personnel can readily assist you. Company identification information might also be needed to access variousonline services available on the Web site.

The support Web site offers extensive information, including a guide to support services (the IBM Software SupportHandbook); frequently asked questions (FAQs); and documentation for all Tivoli products, including Release Notes,Redbooks, and white papers. The documentation for some product releases is available in both PDF and HTMLformats. Translated documents are also available for some product releases.


IBM

Printed in U.S.A.

GI11-8�85-��

ibm fileibm program directory for ibm tivoli advanced catalog management for z/os v2.1.0 program...

Documents