Configuration and Customization Guide - IBM Supportpublib.boulder.ibm.com/tividd/td/ITIntegRM/GC32-9221-00/...AUTOMATED FACILITIES, Availability Managers, Candle Business Partner Logo,

Configuration and Customization GuideIntegrated Resource Manager

Version 500

GC32-9221-00

September 2002

Candle Corporation201 North Douglas Street

El Segundo, California 90245

2 Integrated Resource Manager Configuration and Customization Guide Version 500

Registered trademarks and service marks of Candle Corporation: AF/OPERATOR, AF/PERFORMER, AF/REMOTE, Availability Command Center, Candle Command Center, Candle Electronic Customer Support, Candle logo, Candle Management Server, Candle Management Workstation, Candle Technologies, CL/CONFERENCE, CL/SUPERSESSION, CT, CT/Data Server, CT/DS, DB Logo, DB/QUICKCHANGE, DELTAMON, ETEWatch, IntelliWatch, MQSecure, MQView, OMEGACENTER, OMEGAMON, OMEGAMON/e, OMEGAMON II, OMEGAMON Monitoring Agent, OMEGAVIEW, OMEGAVIEW II, Solutions for Networked Businesses, and Transplex.Trademarks and service marks of Candle Corporation: Alert Adapter, Alert Adapter Plus, Alert Emitter, AMS, Amsys, AUTOMATED FACILITIES, Availability Managers, Candle Business Partner Logo, Candle Direct Logo, CandleLight, CandleNet, CandleNet 2000, CandleNet Portal, Candle CommandPro, CCC, CECS, CICAT, CL/ENGINE, CL/GATEWAY, CL/TECHNOLOGY, CMS, CMW, Command & Control, CommandWatch, Connect-Two, CSA ANALYZER, CT/ALS, CT/Application Logic Services, CT/DCS, CT/Distributed Computing Services, CT/Engine, CT/Implementation Services, CT/IX, CT/Workbench, CT/Workstation Server, CT/WS, DB/DASD, DB/EXPLAIN, DB/MIGRATOR, DB/QUICKCOMPARE, DB/SMU, DB/Tools, DB/WORKBENCH, Design Network, DEXAN, eBA*ServiceMonitor, End-to-End, Enterprise Candle Command Center, Enterprise Candle Management Workstation, EPILOG, ERPNet, ESRA, ETEWatch, HostBridge, IntelliWatch Pinnacle, Lava Console, Messaging Mastered, MQADMIN, MQEdit, MQEXPERT, MQMON, NBX, OMA, OMC Gateway, OMC Status Manager, OMEGACENTER Bridge, OMEGACENTER Gateway, OMEGACENTER Status Manager, OMEGAMON Management Center, OSM, PC COMPANION, Performance Pac, PowerQ, PQConfiguration, PQEdit, PQScope, Response Time Network, Roma, Roma Application Manager, Roma Broker, Roma BSP, Roma Connector, Roma Developer, Roma FS/A, Roma FS/Access, Roma Network, Roma Object Access, Roma Systems Manager, Roma WF/Access, Roma Workflow Access, RTA, RTN, SentinelManager, Solutions for Networked Applications, Status Monitor, Tracer, Unified Directory Services, and Volcano.Trademarks and registered trademarks of other companies: AIX, DB2, and MQSeries are registered trademarks of International Business Machines Corporation. SAP is a registered trademark and R/3 is a trademark of SAP AG. UNIX is a registered trademark in the U.S. and other countries, licensed exclusively through X/Open Company Ltd. HP-UX is a trademark of Hewlett-Packard Company. SunOS is a trademark of Sun Microsystems, Inc.

All other company and product names used herein are trademarks or registered trademarks of their respective companies.

ProtoView Development Corp. - May contain DataTable Version 3.0 Copyright 1989 - 1996 by ProtoView Development Corp. and distributed under license by Candle Corporation.

Copyright © September 2002, Candle Corporation, a California corporation. All rights reserved. International rights secured.

Threaded Environment for AS/400, Patent No. 5,504,898; Data Server with Data Probes Employing Predicate Tests in Rule Statements (Event Driven Sampling), Patent No. 5,615,359; MVS/ESA Message Transport System Using the XCF Coupling Facility, Patent No. 5,754,856; Intelligent Remote Agent for Computer Performance Monitoring, Patent No. 5,781,703; Data Server with Event Driven Sampling, Patent No. 5,809,238; Threaded Environment for Computer Systems Without Native Threading Support, Patent No. 5,835,763; Object Procedure Messaging Facility, Patent No. 5,848,234; End-to-End Response Time Measurement for Computer Programs, Patent No. 5,991,705; Communications on a Network, Patent Pending; Improved Message Queuing Based Network Computing Architecture, Patent Pending; User Interface for System Management Applications, Patent Pending.

NOTICE: This documentation is provided with RESTRICTED RIGHTS. Use, duplication, or disclosure by the Government is subject to restrictions set forth in the applicable license agreement and/or the applicable government rights clause.

This documentation contains confidential, proprietary information of Candle Corporation that is licensed for your internal use only. Any unauthorized use, duplication, or disclosure is unlawful.

Contents 3

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13About this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Adobe Portable Document Format . . . . . . . . . . . . . . . . . . . . . . . . . . 14Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Printing problems? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Documentation Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Panels and figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Revision bars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Variables and literals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Documentation Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Online Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Printed documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

What’s New . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21SYSPLEX Exploitation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22IRM "Active" function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22XCF, TCP/IP and APPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22New Managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Chapter 1. About the CICAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Migration Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26CICAT Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Using the CICAT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Software Requirements - IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

General Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28


Software Requirements - Candle . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29IRM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29IRM Function Package Zap (KAU$Z240). . . . . . . . . . . . . . . . . . . 29

Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30IRM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Chapter 2. CICAT Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Product Tapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Contents of the Tapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

SMP/E Format Product Tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Maintenance Tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Corrective Service Tapes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Installing the Product and Maintenance Tape. . . . . . . . . . . . . . . . . . . 34

Chapter 3. IRM Required Customization . . . . . . . . . . . . . . . . . . . . . . . . . . 35Dataset Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Installation Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Standard Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Run-time Libraries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Allocating Run-time Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Populating Run-time Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Support Datasets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Allocating Support Datasets . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Allocating Batch Status File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Allocating REXX Alternate Library . . . . . . . . . . . . . . . . . . . . . . . 43Allocating AF/OPERATOR Checkpoint Dataset . . . . . . . . . . . . . . 44Configuring AF/OPERATOR Message Logs . . . . . . . . . . . . . . . . 45

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Allocating Message Log Datasets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Allocating Message Log Archive GDG . . . . . . . . . . . . . . . . . . . . . . . . . 47Allocating AF/MSG Proclib Member - GDG Archive . . . . . . . . . . . . . . 47Allocating AF/MSG Proclib Member - Sysout Archive . . . . . . . . . . . . . 48

Configuring AF/OPERATOR Retain Logs . . . . . . . . . . . . . . . . . . 49

Contents 5

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Allocating Retain Log Datasets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Allocating Retain Log Archive GDG . . . . . . . . . . . . . . . . . . . . . . . . . . 51Allocating AF/RET Proclib Member - GDG Archive . . . . . . . . . . . . . . . 51Allocating AF/RET Proclib Member - Sysout Archive . . . . . . . . . . . . . . 52

ISPF Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Allocating ISPF Log Archive GDG . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Allocating AF/LGI Proclib Member - GDG Archive . . . . . . . . . . . . . . . 54Allocating AF/LGI Proclib Member - Sysout Archive . . . . . . . . . . . . . . 55

Updating Parmlib Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Link Library List (LNKLSTxx) . . . . . . . . . . . . . . . . . . . . . . . . . . 58Authorized Program List (IEAAPFxx) . . . . . . . . . . . . . . . . . . . . . 59TSO/E Commands and Programs (IKJTSOxx) . . . . . . . . . . . . . . 60Message Processing Facility List (MPFLSTxx) . . . . . . . . . . . . . . . 61Installation Control Specifications (IEAICSxx) . . . . . . . . . . . . . . . 62

Creating Proclib Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Creating AF/OPR Proclib Member . . . . . . . . . . . . . . . . . . . . . . . 64Creating AF/TCI Proclib Member . . . . . . . . . . . . . . . . . . . . . . . . 66Creating AF/RDR Proclib Member . . . . . . . . . . . . . . . . . . . . . . . 68Creating DEALLOC Proclib Member . . . . . . . . . . . . . . . . . . . . . 69

Creating Batch JCL Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Creating Cataloged Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . 71Creating Batch Interface JCL Members. . . . . . . . . . . . . . . . . . . . 72Creating REXX Table Maintenance Members . . . . . . . . . . . . . . . 73Creating REXX Table Batch Update Members. . . . . . . . . . . . . . . 75Creating Miscellaneous Batch Job Members . . . . . . . . . . . . . . . . 77

Installing ISPF Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Accessing the Load Libraries. . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Accessing the ISPF Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Invoking via Selection Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Invoking via TSO/E REXX Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Invoking the ISPF Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82


Updating Application Manager Definitions . . . . . . . . . . . . . . . . . . . . 84Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Updating Help Dataset Variable . . . . . . . . . . . . . . . . . . . . . . . . . 85Updating Company Name Variable. . . . . . . . . . . . . . . . . . . . . . . 86Updating Company Address1 Variable . . . . . . . . . . . . . . . . . . . . 87Updating Company Address2 Variable . . . . . . . . . . . . . . . . . . . . 88Allocating AF/OPERATOR Message Log MCF Resource Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Allocating AF/OPERATOR Retain Log MCF Resource Definition 90

Configuring AF/OPERATOR Environment . . . . . . . . . . . . . . . . . . . . 91Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Creating AF/OPERATOR Parmlib Members . . . . . . . . . . . . . . . . 92Creating IRM Parmlib Members . . . . . . . . . . . . . . . . . . . . . . . . . 94

Master Calendar Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Custom Calendar Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97System Variable Delete Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 101Table Manager Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102EMCS Consoles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106Started Task Manager Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

SYSPLEX Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Defining Coupling Facility List structure . . . . . . . . . . . . . . . . . . . . . . . 109XES List Structure Size Estimation . . . . . . . . . . . . . . . . . . . . . . . . . . . 110XES List Structure Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111Defining ARM Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Converting to IRM Version 500 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Formatting REXX Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Chapter 4. IRM Optional Customization. . . . . . . . . . . . . . . . . . . . . . . . . . 115Allocating Optional Datasets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116Installation Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116Allocating IMS/XRF Status File . . . . . . . . . . . . . . . . . . . . . . . . . 118Allocating AF/OPERATOR SLF Journals . . . . . . . . . . . . . . . . . 119Allocating POVI Parameter Dataset . . . . . . . . . . . . . . . . . . . . . . 121Allocating POVI NAM Database Dataset . . . . . . . . . . . . . . . . . . 122Allocating POVI Table Database Dataset . . . . . . . . . . . . . . . . . . 123Allocating POVI Viewlog Database Dataset . . . . . . . . . . . . . . . . 124Allocating AF/OPERATOR User Message Logs . . . . . . . . . . . . . 125Allocating User Message Log Archive GDG . . . . . . . . . . . . . . . 126

Contents 7

Alternate Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127Choosing a Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Additional Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

AF/OPERATOR IRM Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . 133Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133IRM Initialization Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134System Software Load Review . . . . . . . . . . . . . . . . . . . . . . . . . 135Updating SYSn.IPLPARM/SYS1.PARMLIB . . . . . . . . . . . . . . . 136

Creating IEASYSxx members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136Creating COMMNDxx members . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136Modifying IEFSSNxx members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Creating Proclib Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138Creating AF/OVI Proclib Member . . . . . . . . . . . . . . . . . . . . . . . 139Creating AF/OVI IRM Settings . . . . . . . . . . . . . . . . . . . . . . . . . 140Creating AF/USR Proclib Member - GDG Archive . . . . . . . . . . 141Creating AF/USR Proclib Member - Sysout Archive . . . . . . . . . 142

REXX Exec Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Appendix A. Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145Electronic support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145Telephone support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146Customer support locations and numbers . . . . . . . . . . . . . . . . . 146Incident documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148Ensuring your satisfaction with customer support . . . . . . . . . . . 148


9

List of Tables

Table 1. Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Table 2. Integrated Resource Manager Documentation . . . . . . . . . . . . . 19Table 3. Installing Product and Maintenance Tape . . . . . . . . . . . . . . . . . 34Table 4. Installation Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Table 5. Required Run-time Libraries - Standard Configuration . . . . . . . 38Table 6. Cataloged Procedure Members . . . . . . . . . . . . . . . . . . . . . . . . . 71Table 7. Batch Interface JCL Members. . . . . . . . . . . . . . . . . . . . . . . . . . 72Table 8. REXX Table Maintenance JCL Members. . . . . . . . . . . . . . . . . . 73Table 9. REXX Table Batch Updates JCL Members . . . . . . . . . . . . . . . . 75

Table 10. Miscellaneous Batch Jobs JCL Members. . . . . . . . . . . . . . . . . . 77Table 11. AF/OPERATOR Parmlib Members . . . . . . . . . . . . . . . . . . . . . . 92Table 12. Master Calendar Parmlib Members . . . . . . . . . . . . . . . . . . . . . . 96Table 13. Custom Calendar Parmlib Members . . . . . . . . . . . . . . . . . . . . . 97Table 14. System Variable Delete Parmlib Members . . . . . . . . . . . . . . . . 101Table 15. Table Manager Parmlib Members . . . . . . . . . . . . . . . . . . . . . . 102Table 16. Started Task Manager Parmlib Members . . . . . . . . . . . . . . . . . 108Table 17. Optional Run-time Libraries - Standard Configuration . . . . . . 116Table 18. Installing Optional Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . 116Table 19. Required Run-time Libraries - Alternate Configuration . . . . . . 127Table 20. Run-Time Dataset Configuration Chart . . . . . . . . . . . . . . . . . . 129Table 21. Customer Support Phone Numbers . . . . . . . . . . . . . . . . . . . . 147


11

List of Figures

FIGURE 1. IRM User Interface Main Selection Panel. . . . . . . . . . . . . . . . . . 83FIGURE 2. Custom Calendar Parameter Examples. . . . . . . . . . . . . . . . . . 100FIGURE 3. AF/OPERATOR Startup Procedure KAU$PARM DD. . . . . . . . 103


Preface 13

Preface

About this DocumentThis guide provides instructions on how to configure and customize the Integrated Resource Manager (IRM) Version 500 to your requirements.

This guide is directed to the systems programmer(s) responsible for configuring and customizing the Integrated Resource Manager. It assumes that you have some previous experience in customizing mainframe software and knowledge of MVS systems and SMP/E.

PrerequisitesThis guide assumes that AF/OPERATOR, or OMEGACENTER Gateway for MVS, and the Integrated Resource Manager has been SMP/E installed and that maintenance has been applied to bring them up to current levels of service. For information on installing AF/OPERATOR refer to Installing Candle Products on MVS (IC51-6057).

Refer to the AF/OPERATOR and the IRM Configuration and Customization Guides for additional information on installing and configuring AF/OPERATOR and IRM respectively.

P

Adobe Portable Document Format



IntroductionCandle supplies documentation in the Adobe Portable Documentation Format (PDF). The Adobe Acrobat Reader prints PDF documents with the fonts, formatting, and graphics as contained in the original document. To print a Candle document, perform the following:

1. Specify the print options for your system. From the Acrobat Reader Menubar, select File > Print Setup... and make your selections. Asetting of 300 dpi is highly recommended as is duplex printing if yourprinter supports it.

2. To start printing, select File > Print on the Acrobat Reader Menu bar.3. On the Print popup, select one of the Print Range options for:

– a single page

– a range of pages

– all of the document

(Optional)

4. To fit oversize pages to the paper size currently loaded on your printer,select the Shrink to Fit option.

Printing problems?Your printer usually determines the print quality of your output. Sometimes printing problems can occur. If you experience printing problems, potential areas to check are:

n settings for your printer and printer driver. (The 300 dpi settings for bothyour driver and printer should be the same. A setting of 300 dpi isrecommended.)

n the printer driver you are using. (You may need a different printer driveror the Universal Printer driver from Adobe. This free printer driver isavailable at www.adobe.com.)

Preface 15


n the halftone/graphics color adjustment for printing color on black andwhite printers. (Check the printer properties under Start > Settings> Printer. For more information, see the online help for the AcrobatReader.)

n the amount of available memory in your printer. (Insufficient memory cancause a document or graphics to fail to print.)

For additional information on printing problems, refer to the documentation for your printer or contact your printer manufacturer.

Documentation Conventions



IntroductionCandle documentation adheres to accepted typographical conventions for command syntax. Conventions specific to Candle documentation are discussed in the following sections.

Panels and figuresThe panels and figures in this document are representations. Actual product panels may differ.

Revision barsRevision bars (|) may appear in the left margin to identify new or updated material.

Variables and literalsIn examples of command syntax, uppercase letters are actual values (literals) that the user should type; lowercase letters are used for variables that represent data supplied by the user. Default values are underscored.

LOGON APPLID(cccccccc)

In the above example, you type LOGIN APPLID followed by an application identifier (represented by cccccccc) within parentheses. The number of characters indicates the maximum allowable length of the variable.

Note: In ordinary text, variable names appear in italics.

Preface 17


SymbolsThe following symbols may appear in command syntax.

Table 1. Symbols

Symbol Usage

| The ‘or’ symbol is used to denote a choice. Either the argument on the left or the argument on the right may be used. For example:

YES | NO

In this example, YES or NO may be specified.

[ ] Denotes optional arguments. Those arguments not enclosed in square brackets are required. For example:

APPLDEST DEST [ALTDEST]

In this example, DEST is a required argument and ALTDEST is optional.

{ } Some documents use braces to denote required arguments, or to group arguments for clarity. For example:

COMPARE {workload} - REPORT={SUMMARY | HISTOGRAM}

The workload variable is required. The REPORT keyword must be specified with a value of SUMMARY or HISTOGRAM.

_ Default values are underscored. For example:

COPY infile outfile - [COMPRESS=YES | NO}]

In this example, the COMPRESS keyword is optional. If specified, the only valid values are YES or NO. If omitted, the default is YES.

b The symbol b indicates a blank space, when needed for clarity.

Documentation Set


Documentation Set

IntroductionCandle provides a complete set of documentation for the Integrated Resource Manager. Each manual in this documentation set contains a specific type of information to help you use the product.

Candle welcomes your comments and suggestions for changes or additions to the documentation set. A user comment form, located at the back of each manual, provides simple instructions for communicating with Candle's Information Development department. You can also send electronic mail to [email protected]. Please include the product name, version, and book title in the subject line. To order additional manuals, contact Candle Customer Support.

Online DocumentationAll documents in the Integrated Resource Manager documentation set are available online.

Preface 19

Documentation Set

Printed documentationThe documentation listed in the following table is availabe for the Integrated Resource Manager. To order additional product manuals, contact your Candle Support Services representative.

Table 2. Integrated Resource Manager Documentation

DocumentNumber Document Name Description

AU51-6292 Integrated Resource Manager Configuration and Customization Guide

Explains how to configure and customize the Integrated Resource Manager after it is installed.

AU54-6514 Integrated Resource Manager Primary Managers User’s Guide

Provides a task-oriented guide to using the Integrated Resource Manager. Explains basic features and navigation methods for the Primary Managers.

AU54-6515 Integrated Resource Manager Control Managers User’s Guide

Provides a task-oriented guide to using the Integrated Resource Manager. Explains basic features and navigation methods for the Control Managers.

AU54-6295 Integrated Resource Manager AF/OPERATOR and Subsystem Managers User’s Guide

Provides a task-oriented guide to using the Integrated Resource Manager. Explains basic features and navigation methods.

AU53-6591 Integrated Resource Manager Functions and Other Facilities Manual

Provides comprehensive reference information about the features of the Integrated Resource Manager.

AU52-6293 Integrated Resource Manager Messages Manual

Provides a reference summary of all Integrated Resource Manager messages.

AU99-6297 Integrated Resource Manager Command Quick Reference Guide

Quick Reference Handbook that explains the format and parameters for the Integrated Resource Manager console commands

Documentation Set


OMC99-4833 Candle Products Program Directory

Provides installation instructions and details all other installation consideration.

Table 2. Integrated Resource Manager Documentation

DocumentNumber Document Name Description

What’s New 21

What’s New

SummaryThis section details the new features and enhancements incorporated into the latest release of Integrated Resource Manager Configuration and Customization Guide Version 500. These changes reflect recent IRM enhancements. Version 500 contains additional description for the parameter file that must be completed in order to use EMCS consoles with the IRM.

W

SYSPLEX Exploitation



IntroductionThe IRM SYSPLEX implementation will introduce new List structures to the Coupling Facility. The IRM Version 400 currently has an internal, dynamically created table, to keep track of the automated tasks under its control. The new list structures will be a global status table for all IRM automated tasks in the SYSPLEX. The List structures will comprise of a total of 3 structures: the first will be a table with one row for each IRM in the SYSPLEX, the second will be a table with one row for each task registering with ARM and the 3rd will be the status table with one row for each task under IRM control in the SYSPLEX.

Enhancement of IRM recovery code to interface with ARM SYSPLEX recovery. The ARM recovery policy will be defined to issue the "IRM ARM" command to recover IRM resources in the SYSPLEX. This will ensure that all IRM automated tasks recovered by ARM will still be under IRM control but can be moved around in the SYSPLEX by workload manager.

With this enhancement, code was introduced to IRM to facilitate keeping track of tasks moved by ARM and keep the integrity of these tasks even if the failing LPAR where these tasks ran before were to be recovered.

IRM "Active" functionA new IRM "Active" function is introduced. This function will be used to determine if a task is active anywhere in the SYSPLEX. This will allow predecessor and successor logic to include a task running on a different LPAR in the SYSPLEX.

XCF, TCP/IP and APPC Up to this point Peer-to-Peer (P2P) connection supported by the IRM was the classic COM1 interface which was a LU6.2 protocol. The IRM is enhanced to include XCF for SYSPLEX related communication, APPC and TCP/IP for all other communication. This gives our customers a choice of protocols to use.

The basic procedure employed by IRM for secure and controlled delivery of messages between IRM residing through out the SYSPLEX is the phased commit protocol.

What’s New 23


New ManagersThis release of the IRM introduces and makes available to you, additional new SYSPLEX management tools. The following table identifies these optional tools.

MVS The MVS Manager is used for managing MVS and all of its related resources, such as tape and DASD devices, Character Reader Devices, Unit Record Devices, Display Devices, Communication Devices, CTC Devices, Miscellaneous Devices, JES Printer s, SNA/RJP Printers and Printer Schedules.

MQ The MQ Start Application is used to automate the start of MQSeries Queue Managers. This Manager has the ability to be customized to meet specific customer requirements.

DB2 The DB2 Start Application is used to automate the start of DB2. This Manager has the ability to be customized to meet specific customer requirements.

JES The JES Manager is used for managing JES3 and all of it's related resources, such as job classes, job groups, writers, printers, JES lines, and NJE nodes. The JES Manager can be used to automatically start and stop JES3 and any of its resources needed by Started Tasks or other JES applications running on the system.

IMS The IMS Start Application is used to control and automate the start of IMS. This manager controls MSDB Recovery options and Batch submittal parameters. The creation of APPC and XRF definitions managed via this interface as well. The Started Task Manager controls the application's initiation. IRM also provides a user interface to parameterize and control activities for the application.

XRF The XRF manager is used to automate the IMS/XRF takeover process. Its main purpose is to manage workload movement following an XRF takeover. After completion of the XRF takeover, the XRF Manager performs the tasks necessary to relocate the XRF workload from the failed system to the new active system.

CICS The CICS manager is used to automate the startup of CICS regions. It has a user interface to define logon parameters and region control parameters. Such as Purge Transactions, Console logon, CA7 region up posting as well as other CICS related functions. The Started Task Manager controls this application's initiation.



About the CICAT 25

About the CICAT

IntroductionThe CICAT supplied with AF/OPERATOR is an automated facility that you use to install and apply maintenance for the IRM.

1

Migration Considerations


Migration Considerations

OverviewThere are two versions of the IRM, version 400 and 500. When upgrading from version 400 to 500 you need to run the conversion procedure listed under Converting to IRM v500 beginning on page 113.

About the CICAT 27

CICAT Overview

CICAT Overview

Using the CICATTo perform the installation process, you must perform a combination of procedures, some using the CICAT and some performed manually. The first procedures in the process require you to use the CICAT.

If you have not previously installed the CICAT, during the installation of AF/OPERATOR or any other Candle product, you must do so now. For instructions on installing the CICAT, see the Program Directory.

ImportantYou must follow the Program Directory instructions provided under "Loading the CICAT" and under "Using the CICAT" before beginning the installation procedure.

If you want to use a CICAT from a previous installation, you must ensure that it is the most current version of the CICAT. The Program Directory will help you make this determination.

Software Requirements - IBM


Software Requirements - IBM

General RequirementsThe following table lists IBM software required by the IRM.

Product Versions Supported

IRM

MVS/ESA 4.3, 5.2.1, 5.2.2

OS/390 1.1, 1.3, 2.1, 2.4, 2.5, 2.6, 2.8, 2.9

JES2 and JES3 Any version compatible with the above

VTAM 3.4, 4.2, 4.3, CS390

CICS 2.1.2, 3.2.1, 3.3.0

IMS 3.1, 4.1, 5.1, 6.1, 7.1

DB2 5.1

TSO/E 2.5

ISPF 4.2, 4.3, 4.4

SMP/E 1.7 or later

REXX Run Time Libraries OR REXX Alternate Library

3.0

About the CICAT 29

Software Requirements - Candle

Software Requirements - Candle

OverviewThis section discusses the Candle software requirements.

IRMIRM Version 500 can be used with the following versions of Candle software.

IRM Function Package Zap (KAU$Z240)AF/OPERATOR Version 240 customers must use this zap. The zap defines the IRM function package to AF/OPERATOR.

Note: AF/OPERATOR Version 250 users should apply PTF QOG3539

To use this zap, copy the JCL to your -hilev-.RKAUSAMP dataset and include the value of DSNPFX on the SET statement. For example:

DSNPFX=HILEV

where HILEV is the high level qualifier for the AF/OPERATOR CSI.

Product Versions Supported

AF/OPERATOR 240, 250, 320

OMEGACENTER Gateway 120, 150

OMEGAVIEW 120

AF/REMOTE 270

Hardware Requirements


Hardware Requirements

OverviewThis section discusses the hardware requirements.

IRMIRM runs on all IBM and IBM-compatible processors capable of running the software listed in "Software Requirements - IBM" on page 23.

The IRM ISPF User Interface supports all 327x-family terminals. These include screen sizes of:

n 24 by 80

n 32 by 80

n 43 by 80

CICAT Customization 31

CICAT Customization

IntroductionThis chapter describes the CICAT customization process and provides instructions on how to install and configure CICAT for the IRM.

2

Product Tapes


Product Tapes

OverviewThis section describes the steps required to install the product and maintenance tapes.

For additional information on Candle tape products, please read Candle Document Number IC51-5812-3, Installing Candle Products and Candle Management Server on MVS, Version 300.

Contents of the TapesThis topic outlines the contents and purpose of the first five files on each type of tape and provides a description of the DOCFILE members.

Note: If your site has strict security requirements for registering all files on a tape before it can be processed, the dataset names for the first five files on Candle tapes are documented here. Dataset names for the additional files on product tapes are listed in the TAPEINFO member of the DOCFILE on the tape.

SMP/E Format Product Tape

The first five files on the SMP/E format product tape are listed below:

File Dataset Name Description1 CANDLE.PROD.CICAT CICAT install data.2 CANDLE.PROD.INSTLIB PDS containing installation data.3 CANDLE.PROD.RESERVE3 Reserved file.4 CANDLE.PROD.DOCFILE PDS containing installation information.5 CANDLE.PROD.SMPMCS SMP/E modification control statements.6 AKAU500.F1 Integrated Resource Manager7 AKAU500.F2 Integrated Resource Manager8 AKAU500.F3 Integrated Resource Manager9 AKAU500.F4 Integrated Resource Manager

10 AKAU500.F5 Integrated Resource Manager11 AKAU500.F6 Integrated Resource Manager12 AKAU500.F7 Integrated Resource Manager

CICAT Customization 33

Product Tapes

Maintenance Tape

The first five files on all types of maintenance tape are listed below:

Corrective Service TapesCorrective service tapes may have a special label attached that reads Customer Feedback Requested. This indicates that Candle has completed internal testing of the fixes on the tape. As part of our ongoing Customer Quality Program we are soliciting your feedback. Until we have received feedback from a number of customers and allowed time for any negative impact to be reported, we do not move the fixes to our repository of customer-approved maintenance. Candle cumulative and preventive maintenance tapes are only created from the customer approved repository.

13 AKAU500.F8 Integrated Resource Manager14 AKAU500.F9 Integrated Resource Manager15 AKAU500.F10 Integrated Resource Manager16 AKAU500.F11 Integrated Resource Manager17 AKAU500.F12 Integrated Resource Manager18 AKAU500.F13 Integrated Resource Manager19 AKAU500.F14 Integrated Resource Manager20 AKAU500.F15 Integrated Resource Manager21 AKAU500.F16 Integrated Resource Manager

File Dataset Name Description1 CANDLE.MAINT.CICAT PDS containing CICAT.2 CANDLE.MAINT.INSTLIB PDS containing installation data.3 CANDLE.MAINT.HOLDDATA SMP/E hold dataset.4 CANDLE.MAINT.DOCFILE PDS containing maintenance-related

information.5 CANDLE.MAINT.SMPCSI SMP/E SYSMODS.

File Dataset Name Description

Installing the Product and Maintenance Tape


Installing the Product and Maintenance TapeComplete the following steps at the command line prompt to install IRM from the product tape:

Table 3. Installing Product and Maintenance Tape

Step Action

1 Enter CICAT Services.

For example, TSO EX 'rhilev.IRM.INSTLIB'where rhilev is the high level for your AF/OPERATOR and SMP/E environment.

2 Select Option 2 “Load installation information”.

3 Select Option 1 to obtain product information from the tape.

4 Enter the tape volser and tape unit.

5 Check and submit load job.

6 Select Option 2 to obtain product maintenance from the tape.

7 Enter the tape volser and tape unit.

8 Check and submit load job.

9 Exit IRM Integrated Resource Manager.

10 Re-enter CICAT.

11 Select Option 3 “Install products”.

12 “S” Select the IRM Product tape volume.

13 Do Option 1, 2, 3, and 4 to SMP/E install the IRM.

14 Select Option 4 “Install maintenance” on the CICAT main panel.

15 Do option 1, 2, and 3 to SMP/E install the IRM maintenance.

IRM Required Customization 35

IRM Required Customization

IntroductionThe IRM is a Candle Automation Solution. The IRM is a toolkit that provides an integrated and comprehensive framework for managing MVS host resources.

The automation applications are based on, run under, and use the base facilities of the AF/OPERATOR, OMEGACENTER Gateway for MVS, and AF/REMOTE software platforms. Automation applications are used to provide an integrated, comprehensive, and easy to use automation solution for the MVS environment.

3

Dataset Configuration



OverviewThere are two dataset configurations available for the IRM run-time libraries, the standard configuration, and the alternate configuration. It is strongly recommended that the standard configuration be used for all initial installs of the IRM.

The IRM has been designed to allow for only one set of application and run-time libraries for your entire SYSPLEX. The IRM can also be replicated for instances where multiple IRM address spaces are needed per LPAR or where there is not any data sharing between LPARS. For these special situations please read the alternate configuration beginning on page 127.

Installation StepsThe following table contains the steps you perform to install the IRM system. These steps are listed in the sequence in which they must be performed.

Table 4. Installation Steps

Step Item Jobname(s)

RUN-TIME LIBRARIES

1 Allocating run-time libraries KAU$ARUN

2 Populating run-time libraries KAU$CRUN

SUPPORT DATASETS

3 Allocating support datasets KAU$ASYS

4 Allocating batch status file KAU$ARCF

5 Allocating REXX alternate library KAU$AEAG

AF/OPERATOR DATASETS

6 Allocating AF/OPERATOR checkpoint dataset KAU$ACHK



Standard ConfigurationThe standard configuration uses the same high level qualifier for the IRM application and user datasets; rhilev is the same as thilev. This is the most common and easiest way to set up the IRM run-time environment, as all of the datasets are named similarly. It also has the advantage that in a shared DASD environment there is a single REXX Table dataset which contains all of the automation definitions for all of the systems. Using a single REXX Table

MESSAGE LOGS

7 Allocating message log datasets KAU$AMSG

8 Allocating message log archive GDG KAU$GMSG

9 Add message log MCF resource definition N/A

10 Allocating AF/MSG proclib member GDG KAUAFMSG

11 Allocating AF/MSG proclib member SYSOUT KAUAFMS1

RETAIN LOGS

12 Allocating retain log datasets KAU$ARET

13 Allocating retain log archive GDG KAU$GRET

14 Add retain log MCF resource definition N/A

15 Allocating AF/RET proclib member GDG KAUAFRET

16 Allocating AF/RET proclib member SYSOUT KAUAFRE1

ISPF CHANGE LOG

17 Allocating ISP log archive GDG KAU$GLGI

18 Allocating AF/LGI proclib member GDG KAUAFLGI

19 Allocating AF/LGI proclib member SYSOUT KAUAFLG1

Table 4. Installation Steps




dataset eliminates the need to maintain redundant definitions for similar resources on different systems, thus reducing the effort required to maintain the automation data.

A third high-level qualifier, rhilev.@system## is needed for the IRM support datasets. Although the runtime libraries are shared between LPARs, the support datasets are a subset of runtime libraries that needs to be unique per LPAR. @system## will normally be the LPARs SMFID followed by the relative order of this IRM (“00” for the firm IRM on this LPAR).

Table 5. Required Run-time Libraries - Standard Configuration

Dataset Description

thilev.RKAURALT REXX Alternate Library

rhilev.RKAU@RCF Started Task Manager Batch Status File

rhilev.RKAUARCI ISPF Change Log Archive GDG

rhilev.RKAUCMDS Parameter Library

rhilev.RKAUEXEC REXX Exec Library

rhilev.RKAULOGI ISPF Change Log

rhilev.RKAUSAMP Batch JCL Library

rhilev.RKAUTBLI ISPF Table Library

rhilev.RKAUTBLR REXX Table Library

rhilev.@system##.RKAUPRFI AF/TCI ISPF Profile Dataset

rhilev.@system##.RKOGARCH AF/OPERATOR Historical Log Archive GDG

rhilev.@system##.RKOGARCM AF/OPERATOR Message Log Archive GDG

rhilev.@system##.RKOGCKP AF/OPERATOR Checkpoint Dataset

rhilev.@system##.RKOGLH01-02

AF/OPERATOR Historical Logs

rhilev.@system##.RKOGLM01-06

AF/OPERATOR Message Logs


Run-time Libraries

Run-time Libraries

OverviewIn the following steps you will be allocating and populating a set of run-time libraries for the IRM. The IRM run-time libraries are commonly referred to as user datasets in this manual. A distinction is made between the IRM application and user datasets, as the former are supplied with the product and maintained via SMP/E and the latter are meant to hold non-SMP/E user information such as data and code that is used by, but not supplied with, the IRM product.

Run-time Libraries


Allocating Run-time LibrariesThe KAU$ARUN member is used to allocate a set of IRM run-time libraries. The IRM run-time libraries will contain the user customized, and maintained, automation data and code used by the IRM.

Copy the KAU$ARUN member from the thilev.TKAUSAMP dataset to your personal JCL library. Edit the copy of KAU$ARUN in your personal JCL library and perform the following tasks:

1. Change the JOB card information to conform to your site's standards and/or requirements.

2. Fill in the JCL SET statements for the DSNPFX, DSVSER, and DSUNIT variables. The DSNPFX variable should be set to the high level qualifier for the IRM user datasets, rhilev. In most cases the high level qualifier for the IRM user datasets will be the same as the high level qualifier for the IRM application datasets, thilev.The DSVSER variable should be set to the volume serial number of the direct access device on which the rhilev datasets are to be located. The DSUNIT variable should be set to the unit type of the DASD volume specified by the DSVSER variable. If the rhilev datasets are to be part of an SMS-managed pool, generics may be used for the values of the DSVSER and DSUNIT variables, such as SYSDA and 3390 respectively.

The JCL SET statements should appear similar to the following example:

//*// SET DSNPFX=rhilev// SET DSVSER=DASD01// SET DSUNIT=3390//*

3. Submit the job and ensure that it completes with condition code 0.4. If you wish, you may now move the KAU$ARUN member into your

personal JCL library or the sample JCL library, rhilev.RKAUSAMP, which you have just created.


Run-time Libraries

Populating Run-time LibrariesThe KAU$CRUN member is used to populate the rhilev.RKAUSAMP dataset with JCL members and the rhilev.RKAUEXEC dataset with EXEC members that will be used in subsequent install steps.

Copy KAU$CRUN from TKAUSAMP to the RKAUSAMP library. Edit the copy of KAU$CRUN in the rhilev.RKAUSAMP dataset and perform the following tasks:


2. Fill in the JCL SET statements for the APLPFX and USRPFX variables. The APLPFX variable should be set to the high level qualifier for the IRM application datasets, thilev, and the USRPFX variable should be set to the high level qualifier for the IRM user datasets, rhilev, as in the following example:

//*// SET APLPFX=thilev// SET USRPFX=rhilev//*

3. Submit the job and ensure that it completes with condition code 0.

Support Datasets


Support Datasets

Allocating Support DatasetsThe KAU$ASYS member is used to allocate a set of support datasets for an IRM AF/OPERATOR run-time environment. The support datasets must be unique for each IRM AF/OPERATOR environment, relative order 0 through 9, on each system.

Edit the copy of KAU$ASYS in the rhilev.RKAUSAMP dataset and perform the following tasks:


2. Fill in the JCL SET statements for the DSNPFX, DSVSER, and DSUNIT variables. The DSNPFX variable should be set to the high level qualifier for the AF/OPERATOR support datasets, rhilev.@system##, the DSVSER variable should be set to the volume serial number of the direct access device on which the rhilev.@system## datasets are to be located, and the DSUNIT variable should be set to the unit type of the DASD volume specified by the DSVSER variable, as in the following example:

//*// SET DSNPFX=rhilev.@system##// SET DSVSER=DASD01// SET DSUNIT=3390//*


Allocating Batch Status FileThe KAU$ARCF member is used to allocate the rhilev.RKAU@RCF dataset. The rhilev.RKAU@RCF dataset, or Started Task Manager Batch Status File, is used to store resource related information for the Started Task Manager Batch Interface. The rhilev.RKAU@RCF dataset is also used as the repository for user-defined resource information: the @R####US members created by the @RCFWRIT() function and accessed by the @RCFREAD() function.


Support Datasets

Edit the copy of KAU$ARCF in the rhilev.RKAUSAMP dataset and perform the following tasks:


2. Fill in the JCL SET statements for the DSNPFX, DSVSER, and DSUNIT variables. The DSNPFX variable should be set to the high level qualifier for the IRM user datasets, rhilev, the DSVSER variable should be set to the volume serial number of the direct access device on which the rhilev datasets are to be located, and the DSUNIT variable should be set to the unit type of the DASD volume specified by the DSVSER variable, as in the following example:



Allocating REXX Alternate LibraryThe KAU$AEAG member is used to allocate and populate the thilev.RKAURALT dataset. The thilev.RKAURALT dataset is used for the REXX Alternate Library. A copy of Release 3 of the REXX Alternate Library is supplied with the IRM.

Note: If you have the REXX compiler run-time libraries, the REXX Alternate Library is not needed under normal circumstances, but may be requested by Candle support personnel in problem resolution situations. Therefore, if you have the REXX compiler run-time libraries, complete this step, but ignore all future references to the REXX Alternate Library.

Important:If you have installed the REXX Alternate Library supplied with AF/OPERATOR, ensure it is at least release 3.

Edit the copy of KAU$AEAG in the rhilev.RKAUSAMP dataset and perform the following tasks:


Support Datasets


2. Fill in the JCL SET statements for the DSNPFX, DSVSER, and DSUNIT variables. The DSNPFX variable should be set to the high level qualifier for the IRM application datasets, thilev, the DSVSER variable should be set to the volume serial number of the direct access device on which the thilev datasets are to be located, and the DSUNIT variable should be set to the unit type of the DASD volume specified by the DSVSER variable.

Fill in the JCL SET statements for the TAPEVSER and TAPEUNIT variables. The TAPEVSER variable should be set to the volume serial number of the IRM product tape and the TAPEUNIT variable should be set to the appropriate unit type for the tape drive, as in the following example:

//*// SET DSNPFX=thilev// SET DSVSER=DASD01// SET DSUNIT=3390// SET TAPEVSER=999999// SET TAPEUNIT=348//*


Allocating AF/OPERATOR Checkpoint DatasetThe KAU$ACHK member is used to allocate a checkpoint dataset for the AF/OPERATOR address space. The checkpoint dataset is used to store AF/OPERATOR system variables and TOD traps which use the CATCHUP option, across invocations of the AF/OPERATOR address space. The checkpointing facility is heavily used by the IRM and must be installed and enabled.

Note: If you have already defined a checkpoint dataset (RKOGCHK) as part of the AF/OPERATOR install process, you should skip this step and proceed to the next step of the process.

The dataset created in this step will be referenced in the AF/OPR cataloged procedure addressed in a subsequent step in the install process.

Edit the copy of KAU$ACHK in the rhilev.RKAUSAMP dataset and perform the following tasks:



Support Datasets



3. Change each occurrence of varialbe -HILEV- in the IDCAMS SYSIN DD to the high level qualifier for the AF/OPERATOR system specific datasets.

4. Change each occurrence of -SYSDA- in the IDCAMS SYSIN DD to the volume serial number of the direct access device on which the rhilev.@system## datasets are to be located.

5. If you are re-allocating a previously defined dataset, uncomment the DELETE statement in the IDCAMS SYSIN DD.


Configuring AF/OPERATOR Message Logs

Overview

The following sections describe how to configure the IRM automated message log archiving process. The steps to follow are:

n Allocate a set of DASD message log datasets.

n Define a message log archive GDG index.

n Create the required WTO traps to trigger the message log archive process.

n Create the AF/MSG started task JCL that will be used by IRM to archive the message log to either a DASD dataset or sysout file.

Once the above steps are completed and the WTO traps are initialized by IRM, the process that occurs is as follows; the WTO traps trigger on the AF/OPERATOR generated messages that indicate a message (RKOGLMxx) log switch has taken place, either as a result of the current message log filling

Support Datasets


up or an operator initiated the log switch. As a result IRM starts the AF/MSG started task to archive the current message log dataset.

Allocating Message Log Datasets

The KAU$AMSG member is used to allocate a set of six DASD message log datasets for the AF/OPERATOR address space. Using DASD message log datasets allows AF/OPERATOR to be started under the master subsystem (SUB=MSTR). Starting AF/OPERATOR under the master subsystem allows AF/OPERATOR and the automation environment to be independent of JES, and any JES failures, as well as allowing the IRM to automate other SUB=MSTR resources.

Note: If you have already defined a set of six DASD message log datasets (RKOGLM01-RKOGLM06) as part of the AF/OPERATOR install process, you should skip this step and proceed to the next step in the process.

The datasets created in this step will be referenced in the AF/OPR cataloged procedure that is addressed in a subsequent step in the install process.

Edit the copy of KAU$AMSG in the rhilev.RKAUSAMP dataset and perform the following tasks:






Support Datasets

Allocating Message Log Archive GDG

The KAU$GMSG member is used to allocate a generation data group (GDG) index for the DASD message log dataset archive process. The DASD message log dataset archive process will copy a DASD message log dataset to the +1 GDG member when the log dataset is closed. DASD message log datasets are closed automatically when the dataset is filled or closed on demand in response to an AO FREE(RKOGLOGM) command.

Note: If you will be using a sysout-based archive process for the DASD message log datasets, instead of the GDG-based archive process, you may skip this step.

The GDG index created in this step will be referenced in the AF/MSG cataloged procedure that is addressed in a subsequent step in the install process.

Edit the copy of KAU$GMSG in the rhilev.RKAUSAMP dataset and perform the following tasks:


2. Change each occurrence of -HILEV- in the IDCAMS SYSIN DD to the high level qualifier for the AF/OPERATOR support datasets, rhilev.@system##.



Allocating AF/MSG Proclib Member - GDG Archive

The KAUAFMSG member is a sample procedure for the AF/MSG started task. The AF/MSG started task is used by the AF/OPERATOR DASD message log dataset archive process to copy a DASD message log dataset to the +1 GDG member when the log dataset is closed.

Note: If you will be using a sysout-based archive process for the DASD message log datasets, instead of the GDG-based archive process, you may skip this step.

Copy the KAUAFMSG member from the thilev.TKAUSAMP dataset to the SYS1.PROCLIB dataset, choosing a new member name for the started task

Support Datasets


that is appropriate for your site, for example, AFMSG. Edit the copy of KAUAFMSG in SYS1.PROCLIB and perform the following tasks:

1. The SYS=system parameter may be filled in now or specified later on the MVS start command for the task. The value for system is the same as that used in rhilev.@system##.

2. The OUT='*' parameter should be set to a sysout class that conforms to your site's standards and/or requirements.


//*// SET DSNPFX=rhilev.@&SYS.00// SET DSVSER=DASD01// SET DSUNIT=3390//*

4. A pattern dataset may need to be added to the SYSUT2 DD DCB parameter if the GDG is located on a non-SMS managed volume. Add the name of a valid pattern dataset in your environment as the first subparameter of the SYSUT2 DD DCB parameter, as in the following example:

...// DCB=(SYS1.PTRN,DSORG=PS,...)...

5. Save the member and proceed to the next installation step.

Allocating AF/MSG Proclib Member - Sysout Archive

The KAUAFMS1 member is a sample procedure for the AF/MSG started task. The AF/MSG started task is used by the AF/OPERATOR DASD message log dataset archive process to copy a DASD message log dataset to sysout when the dataset is closed.

Note: If you will be using the GDG-based archive process for the DASD message log datasets, instead of a sysout-based archive process, you may skip this step.


Support Datasets

Copy the KAUAFMS1 member from the thilev.TKAUSAMP dataset to the SYS1.PROCLIB dataset, choosing a new member name for the started task that is appropriate for your site, for example, AFMSG. Edit the copy of KAUAFMS1 in SYS1.PROCLIB and perform the following tasks:




//*// SET DSNPFX=rhilev.@&SYS// SET DSVSER=DASD01// SET DSUNIT=3390//*


Configuring AF/OPERATOR Retain Logs

Overview

The following sections describe how to configure the IRM automated retain log archiving process. The steps to follow are:

n Allocate a set of DASD retain log datasets.

n Define a retain log archive GDG index.

n Create the required WTO traps to trigger the retain log archive process.

n Create the AF/RET started task JCL that will be used by IRM to archive the retain logs to either a DASD dataset or sysout file.

Support Datasets


Once the above steps are completed and the WTO trap is initialized by IRM the following process occurs:

n The WTO trap triggers on the AF/OPERATOR generated messages that indicate a retain (RKOGLHxx) log switch has taken place, either as a result of the current retain log file filling up or an operator initiated the log switch. As a result IRM starts the AF/RET started task to archive the current retain log dataset.

Allocating Retain Log Datasets

The KAU$ARET member is used to allocate a set of two retain log datasets for the AF/OPERATOR address space. The retain log datasets are used as part of the AF/OPERATOR TRAP command RETAIN option and the RETAIN*VIEW facility.

Note: If you have already defined a set of two retain log datasets (RKOGLH01-RKOGLH02) as part of the AF/OPERATOR install process, you should skip this step and proceed to the next step in the process.

The datasets created in this step will be referenced in the AF/OPR cataloged procedure that is addressed in a subsequent step in the install process.

Edit the copy of KAU$ARET in the rhilev.RKAUSAMP dataset and perform the following tasks:






Support Datasets

Allocating Retain Log Archive GDG

The KAU$GRET member is used to allocate a generation data group (GDG) index for the retain log dataset archive process. The retain log dataset archive process will copy a retain log dataset to the +1 GDG member when the log dataset is closed. Retain log datasets are closed automatically when the dataset is filled.

Note: If you will be using a sysout-based archive process for the historical log datasets, instead of the GDG-based archive process, you may skip this step.

The GDG index created in this step will be referenced in the AF/RET cataloged procedure that is addressed in a subsequent step in the install process.

Edit the copy of KAU$GRET in the rhilev.RKAUSAMP dataset and perform the following tasks:





Allocating AF/RET Proclib Member - GDG Archive

The KAUAFRET member is a sample procedure for the AF/RET started task. The AF/RET started task is used by the AF/OPERATOR historical log dataset archive process to copy a historical log dataset to the +1 GDG member when the log dataset is closed.

Note: If you will be using a sysout-based archive process for the historical log datasets, instead of the GDG-based archive process, you may skip this step.

Copy the KAUAFRET member from the thilev.TKAUSAMP dataset to the SYS1.PROCLIB dataset, choosing a new member name for the started task that is appropriate for your site, for example, AFRET. Edit the copy of KAUAFRET in SYS1.PROCLIB and perform the following tasks:

Support Datasets









Allocating AF/RET Proclib Member - Sysout Archive

The KAUAFRE1 member is a sample procedure for the AF/RET started task. The AF/RET started task is used by the AF/OPERATOR retain log dataset archive process to copy a retain log dataset to sysout when the dataset is closed.

Note: If you will be using the GDG-based archive process for the retain log datasets, instead of a sysout-based archive process, you may skip this step.

Copy the KAUAFRE1 member from the thilev.TKAUSAMP dataset to the SYS1.PROCLIB dataset, choosing a new member name for the started task


Support Datasets

that is appropriate for your site, for example, AFRET. Edit the copy of KAUAFRE1 in SYS1.PROCLIB and perform the following tasks:






ISPF Change Log

Overview

The following sections describe how to configure the IRM manual ISPF change log archiving process. The steps to follow are:

n define an change log archive GDG.

n create the AF/LGI started task JCL that will be used by the operator to archive the change log to either a DASD dataset or sysout file.

As this change log is internal to IRM there is no AF/OPERATOR messages associated when it runs out of space and wraps around. To prevent the potential loss of audit data it will be necessary to determine when the best time to archive this dataset. We recommend change log archiving should be included in your site's change control strategies.

Support Datasets


For example, immediately following any IRM changes to your production environment an operator can be instructed to start the AF/LGI procedure to archive and empty the change log dataset. Thus providing a change log archive dataset or sysout that contains all of changes for this particular production roll out.

Allocating ISPF Log Archive GDG

The KAU$GLGI member is used to allocate a generation data group (GDG) index for the ISPF change log dataset archive process. The ISPF change log dataset archive process will copy an ISPF change log dataset to the +1 GDG member when the KAU@LOGI batch job is run or the AF/LGI started task is started.

The GDG index created in this step will be referenced in the AF/LGI cataloged procedure and/or the KAU@LOGI batch job that is addressed in a subsequent step in the install process.

Edit the copy of KAU$GLGI in the rhilev.RKAUSAMP dataset and perform the following tasks:


2. Change each occurrence of -HILEV- in the IDCAMS SYSIN DD to the high level qualifier for the IRM user datasets, rhilev.



Allocating AF/LGI Proclib Member - GDG Archive

The KAUAFLGI member is a sample procedure for the AF/LGI started task. The AF/LGI started task is used by the IRM ISPF change log dataset archive process to copy a historical log dataset to the +1 GDG member when the task is started.

Note: If you will be using a sysout-based archive process for the ISPF change log datasets, instead of the GDG-based archive process, you may skip this step.

Copy the KAUAFLGI member from the thilev.TKAUSAMP dataset to the SYS1.PROCLIB dataset, choosing a new member name for the started task


Support Datasets

that is appropriate for your site, for example, AFLGI. Edit the copy of KAUAFLGI in SYS1.PROCLIB and perform the following tasks:


2. The OUT='*' parameter should be set to a sysout class conforming to your site's standards and/or requirements.






Allocating AF/LGI Proclib Member - Sysout Archive

The KAUAFLG1 member is a sample procedure for the AF/LGI started task. The AF/LGI started task is used by the IRM ISPF change log dataset archive process to copy a retain log dataset to the +1 GDG member when the task is started.

Note: If you will be using the GDG-based archive process for the ISPF change log datasets, instead of a sysout-based archive process, you may skip this step.

Support Datasets


Copy the KAUAFRE1 member from the thilev.TKAUSAMP dataset to the SYS1.PROCLIB dataset, choosing a new member name for the started task that is appropriate for your site, for example, AFLGI. Edit the copy of KAUAFRE1 in SYS1.PROCLIB and perform the following tasks:




//*// SET DSNPFX=rhilev.@&SYS.00// SET DSVSER=DASD01// SET DSUNIT=3390//*// SET DSNPFX=rhilev.@&SYS.00



Updating Parmlib Members


OverviewThe following sections describe the changes to the system initialization parameters which are required for AF/OPERATOR and the IRM. Each of the members referenced in the following sections are contained in the system initialization parameter dataset, SYS1.PARMLIB.



Link Library List (LNKLSTxx)Adding the IRM load libraries to the link list is optional, but recommended. If you do not add the load libraries to the link list, you will need to update any TSO/E LOGON procedure that will be used to invoke the IRM ISPF User Interface and specify the thilev.TKAULOAD library, as well as the thilev.RKAURALT library if you will be using the REXX Alternate Library, in a STEPLIB DD.

Add the thilev.TKAULOAD library to the appropriate LNKLSTxx member in SYS1.PARMLIB. If the AF/OPERATOR load libraries have been added to the link list, place the entry for thilev.TKAULOAD before the AF/OPERATOR entries, as in the following example:

...thilev.TKAULOAD,thilev.TKANMOD,thilev.TKANMODL,thilev.TKANMOD1,...

If you will be using the REXX Alternate Library, you must also add the thilev.RKAURALT library to the LNKLSTxx member. Place this entry after thilev.TKAULOAD and before the AF/OPERATOR entries, as in the following example:

...thilev.TKAULOAD,thilev.RKAURALT,thilev.TKANMOD,thilev.TKANMODL,thilev.TKANMOD1,...



Authorized Program List (IEAAPFxx)Add the thilev.TKAULOAD library to the appropriate IEAAPFxx member in SYS1.PARMLIB. If you will be using the REXX Alternate Library, you must also add the thilev.RKAURALT library to the IEAAPFxx member.



TSO/E Commands and Programs (IKJTSOxx)Ensure that IEBCOPY has been defined as an authorized command in the AUTHCMD section of the appropriate IKJTSOxx member. A sample definition of the AUTHCMD NAMES statement is available in SYS1.SAMPLIB(IKJTSO00). This is part of the @E25D2HO IBM internal change to support DFP/DFSMS, which may not have been implemented.

AUTHCMD NAMES( /* AUTHORIZED COMMANDS */ +RECEIVE /* TSO COMMANDS */ +

...IEBCOPY /* */ +

/* DFP/DFSMS @E25D2HO */ +/* */ +

...SR SEARCH) /* */



Message Processing Facility List (MPFLSTxx)Check if the .NO_ENTRY statement in the appropriate MPFLSTxx member exists. If the .NO_ENTRY statement specifies SUP(YES), add the following two entries shown in BOLD font after the .NO_ENTRY statement:

.NO_ENTRY,AUTO(NO),RETAIN(YES),SUP(YES)ASO*,AUTO(NO),RETAIN(YES),SUP(NO)KAU*,AUTO(NO),RETAIN(YES),SUP(NO)

These entries ensure that IRM messages are not suppressed as a result of site-specific message suppression.



Installation Control Specifications (IEAICSxx)Define the AF/OPERATOR started task in the appropriate IEAICSxx member. The AF/OPERATOR started task should be given the highest priority in the system or, at a minimum, a higher priority than any resource that it is to manage.

Define the AF/TCI started task in the appropriate IEAICSxx member. The AF/TCI started task should be given a priority roughly equivalent to the TSO/E started task on that system.


Creating Proclib Members


OverviewThe following sections describe the start-up procedure members that need to be created for the required AF/OPERATOR and IRM started tasks. Each of the members created in the following sections should be placed in the SYS1.PROCLIB dataset or in an appropriate user proclib dataset.

Important: If the AF/OPERATOR started task is to be started under the master sub-system (SUB=MSTR), the start-up member for the task must be placed in the SYS1.PROCLIB dataset or in another proclib dataset that has been defined in the master JCL (refer to the SYS1.PARMLIB MSTJCLxx member for more information).



Creating AF/OPR Proclib MemberThe KAUAFOPR member is a sample procedure for the AF/OPERATOR started task.

Copy the KAUAFOPR member from the thilev.TKAUSAMP dataset to the SYS1.PROCLIB dataset, choosing a new member name for the started task that is appropriate for your site, for example, AFOPR. Edit the copy of KAUAFOPR in SYS1.PROCLIB and perform the following tasks:

1. If you are sharing REXX table data among multiple systems, or anticipate a large automation environment, increase the SIZE=64M parameter to 128M or 256M.


3. Fill in the JCL SET statements as follows://*// SET TKAUPFX=thilev// SET RKAUPFX=rhilev// SET TKANPFX=thilev// SET RKANPFX=rhilev// SET RKANSYS=rhilev.@&SYS.00// SET OGPARM1=KAU&RO.OG&TYPE// SET OGPARM2=KAU&RO.&SYS//*

where the JCL SET variables have the following meaning:

TKAUPFX Is the IRM target library high level qualifier, thilev.

RKAUPFX Is the IRM run-time library high level qualifier, rhilev.

TKANPFX Is the AF/OPERATOR target library high level qualifier, thilev.

RKANPFX Is the AF/OPERATOR run-time library high level qualifier, rhilev.

RKANSYS Is the support datasets high level qualifier, rhilev.@system##.

OGPARM1 Is the primary OGPARMS member which should be left as is.

OGPARM2 Is the system OGPARMS member which should be left as is.



4. If you will be using the REXX Alternate Library and you have not added the IRM load libraries to the link list, add the thilev.RKAURALT dataset to the STEPLIB DD as follows:

//STEPLIB DD DISP=SHR,DSN=&TKAUPFX..RKAURALT// DD DISP=SHR,DSN=&TKAUPFX..TKAULOAD...




Creating AF/TCI Proclib MemberThe KAUAFTCI member is a sample procedure for the AF/TSO Command Interface started task.

Copy the KAUAFTCI member from the thilev.TKAUSAMP dataset to the SYS1.PROCLIB dataset, choosing a new member name for the started task that is appropriate for your site, for example, AFTCI. Edit the copy of KAUAFTCI in SYS1.PROCLIB and perform the following tasks:


2. The OUT='SYSOUT=*' parameter should be set to a sysout class that conforms to your site's standards and/or requirements.

3. Fill in the JCL SET statements as follows://*// SET ISPFPFX=ihilev// SET TKAUPFX=thilev// SET RKAUPFX=rhilev// SET TKANPFX=thilev// SET RKANPFX=rhilev// SET RKAUSYS=rhilev.@&SYS.00//*







ISPFPFX Is the ISPF target library high level qualifier, ihilev. The ISPF libraries are supplied by IBM and are normally named SYS1.SISPxxxx, for example, SYS1.SISPCLIB. If this is the case, the value for ihilev would be SYS1.





RKAUSYS Is the support datasets high level qualifier, rhilev.@system##.



Creating AF/RDR Proclib MemberThe KAUAFRDR member is a sample procedure for the AF/RDR started task. The AF/RDR started task is used by the IRM @JOBEDIT() and @JOBSMIT() functions to submit batch jobs via the JES internal reader.

Copy the KAUAFRDR member from the thilev.TKAUSAMP dataset to the SYS1.PROCLIB dataset, choosing a new member name for the started task that is appropriate for your site, for example, AFRDR. Edit the copy of KAUAFRDR in SYS1.PROCLIB and perform the following tasks:



3. Fill in the JCL SET statements as follows://*// SET TKAUPFX=thilev// SET RKAUPFX=rhilev// SET CONFIRM='&MAT &SYS'//*





CONFIRM Is the confirmation parameter and should be left as is.



Creating DEALLOC Proclib MemberEnsure that the DEALLOC procedure has been installed in the SYS1.PROCLIB dataset or in another proclib dataset that has been defined in the master JCL (refer to the SYS1.PARMLIB MSTJCLxx member for more information). When needed, the DEALLOC procedure is started under the master subsystem (SUB=MSTR) by the IRM.

This is part of the OS/390 installation process which may not have been implemented. A copy of the DEALLOC procedure can be found in the SYS1.SAMPLIB dataset, or you may use the KAUAFDEA member in the thilev.TKAUSAMP dataset.

Note: For additional information, refer to IBM Corporation, 'OS/390 V2R10.0 MVS System Commands', GC28-1781-10 (Poughkeepsie, NY.:IBM, 1988, 2000), Placing an I/O Device or a Range of I/O Devices Online or Offline, section 4.55.9, for more information.

Creating Batch JCL Members



OverviewThe following sections describe creating the batch JCL members for the required IRM batch jobs and the Started Task Manager Batch Interface. Each of the members created in the following sections should reside in the rhilev.RKAUSAMP dataset.

Note: None of the members will be submitted at this point, just created.



Creating Cataloged ProceduresEdit each of the members listed in the following table in the rhilev.RKAUSAMP dataset and perform the following tasks:





Table 6. Cataloged Procedure Members

Member Description Checklist

KAUR@CA7 Issue RCF Command via CA7 Batch Procedure

KAUR@JOB Issue RCF Command via Batch Job Procedure

KAURBCMP Post STM Batch Complete Event Procedure

KAURBRDY Post STM Batch Ready Event Procedure

KAURBUSR Post STM Batch User Event Procedure

KAUZLGSN Invoke Syslog Scanning Utility Procedure



Creating Batch Interface JCL MembersEdit each of the members listed in the following table in the rhilev.RKAUSAMP dataset and perform the following tasks:




Table 7. Batch Interface JCL Members


KAU$@CA7 Issue RCF Command via CA7 Batch Sample

KAU$@JOB Issue RCF Command via Batch Job Sample

KAU$BCMP Post STM Batch Complete Event Sample

KAU$BRDY Post STM Batch Ready Event Sample

KAU$BUSR Post STM Batch User Event Sample



Creating REXX Table Maintenance MembersEdit each of the members listed in the following table in the rhilev.RKAUSAMP dataset and perform the following tasks:






Table 8. REXX Table Maintenance JCL Members


KAU@#AOC Re-format @APLAOCM Application Table

KAU@#APL Re-format APL Application Tables

KAU@#CCF Re-format CCF Application Tables

KAU@#CDS Re-format @CNSDESC Application Table

KAU@#CNS Re-format CNS Application Tables

KAU@#DEV Re-format DEV Application Tables

KAU@#IMS Re-format IMS Application Tables

KAU@#JCL Re-format @JESCLAS Application Table

KAU@#JGR Re-format @JESGRUP Application Table



KAU@#MCF Re-format MCF Application Tables

KAU@#OM2 Re-format OM2 Application Tables

KAU@#OVI Re-format OVI Application Tables

KAU@#P2P Re-format P2P Application Tables

KAU@#RCF Re-format RCF Application Tables

KAU@#RLS Re-format @RCFLIST Application Table

KAU@#RSC Re-format @RCFSCHD Application Table

KAU@#SCF Re-format SCF Application Tables

KAU@#SYS Re-format @SYSVARS Application Tables

KAU@#TBL Re-format TBL Application Tables

KAU@#USR Re-format @USRVARS Application Tables

KAU@#VTM Re-format VTM Application Tables

Table 8. REXX Table Maintenance JCL Members




Creating REXX Table Batch Update MembersEdit each of the members listed in the following table in the rhilev.RKAUSAMP dataset and perform the following tasks:






Table 9. REXX Table Batch Updates JCL Members


KAU$#AOC Update @APLAOCM Application Table

KAU$#APL Update APL Application Tables

KAU$#CCF Update CCF Application Tables

KAU$#CDS Update @CNSDESC Application Table

KAU$#CNS Update CNS Application Tables

KAU$#DEV Update DEV Application Tables

KAU$#IMS Update IMS Application Tables

KAU$#JCL Update @JESCLAS Application Table

KAU$#JGR Update @JESGRUP Application Table



KAU$#MCF Update MCF Application Tables

KAU$#OM2 Update OM2 Application Tables

KAU$#OVI Update OVI Application Tables

KAU$#P2P Update P2P Application Tables

KAU$#RCF Update RCF Application Tables

KAU$#RLS Update @RCFLIST Application Table

KAU$#RSC Update @RCFSCHD Application Table

KAU$#SCF Update SCF Application Tables

KAU$#SYS Update @SYSVARS Application Tables

KAU$#TBL Update TBL Application Tables

KAU$#USR Update @USRVARS Application Tables

KAU$#VTM Update VTM Application Tables

Table 9. REXX Table Batch Updates JCL Members




Creating Miscellaneous Batch Job MembersEdit each of the members listed in the following table in the rhilev.RKAUSAMP dataset and perform the following tasks:






Table 10. Miscellaneous Batch Jobs JCL Members


KAU$LSCN Syslog Scanning Utility Job Sample

KAU@LOGI Archive IRM Application Change Log

Installing ISPF Interface



OverviewThe following sections describe how to install and invoke the Integrated Resource Manager ISPF User Interface. The IRM ISPF User Interface is used to define and maintain definitions for the resources that will be managed (automated) by the IRM. Resource definitions are stored in REXX Table data format in the rhilev.RKAUTBLR dataset.



Accessing the Load Librariesn If you have installed the IRM load libraries in the link list, skip this step and

proceed to Accessing the ISPF Interface on page 81.

n If you will be using the REXX Alternate Library and you have not added the IRM load libraries to the link list, add the thilev.TKAULOAD and thilev.RKAURALT datasets to the STEPLIB DD in every TSO/E LOGON procedure that will be used to invoke the IRM ISPF User Interface, as in the following example:

//STEPLIB DD DISP=SHR,DSN=thilev.RKAURALT// DD DISP=SHR,DSN=thilev.TKAULOAD...

n If you will be using the REXX Run-time Libraries and you have not added the IRM load libraries to the link list, add the thilev.TKAULOAD dataset to the STEPLIB DD, or the ISPLLIB DD, in every TSO/E LOGON procedure that will be used to invoke the IRM ISPF User Interface, as in the following example:

// STEPLIB DD DISP=SHR,DSN=thilev.TKAULOAD...

OR

// ISPLLIB DD DISP=SHR,DSN=thilev.TKAULOAD...

n If you have installed the IRM load libraries into the LNKLSTxx member or added the IRM load libraries to the TSO Logon Procedure, skip this step and proceed to Accessing the ISPF Interface on page 81.



Otherwise the following sample REXX exec can be executed from the TSO ready prompt and used as a Installation Verification Procedure (IVP) to ensure that the IRM ISPF Interface has been installed correctly and is available for data entry.

/*--- REXX---------------------------------------------** Temporarily allocate RKAURALT and TKAULOAD ** libs to allow access to the IRM ISPF ** Interface **------------------------------------------------------*/parse source . typecall execfn execdd execds ., execadr execenv exectkn .parse upper arg .signal off failuresignal off error"ALLOCATE FILE(ALLOCIRM)","DATASET('-rhilev-.RKAURALT' '-thilev-.TKAULOAD') SHR”if rc = 0 thenPUSH "TSOLIB ACTIVATE FILE(ALLOCIRM)"call exit rc/*-- Exit ------------------------------------------------* * Universal exit. Retrieve RC and return to caller. * *----------------------------------------------------------*/exit:arg rc .exit rc

In the above example, change -RHILEV- to the high level qualifier for the AF/OPERATOR Support Datasets. Change -THILEV- to the high level qualifier for the IRM Application Datasets.



Accessing the ISPF Interface

Overview

There are two ways to invoke the IRM ISPF User Interface. The IRM ISPF User Interface can be invoked by adding an option to a selection panel in your ISPF menu system, or by calling a REXX exec from ISPF option 6 or the command line. Choose the option that best suits your needs and complete the installation section that corresponds to that choice which follows. If you wish, you may complete both of the installation sections that follow.

Invoking via Selection Panel

Add the IRM ISPF User Interface option to the appropriate ISPF selection panel and include the following line of code to the &ZSEL statement in the PROC section of the panel, specifying the IRM application dataset high level qualifier, thilev, via the PFX() parameter contained in the KAUISINT PARM() text:

&ZSEL = TRANS(TRUNC(&ZCMD,'.')...AU,'PGM(KAUISINT)PARM(&ZCMD PFX(thilev))NOCHECK'...*,'?')

AU,'PGM(KAUISINT)PARM(&ZCMD PFX(thilev) +NOCHECK'

You may now invoke the IRM ISPF User Interface by choosing the option you have defined from the selection panel you have modified.

Invoking via TSO/E REXX Exec

Edit the copy of KAUUISPF in the rhilev.RKAUEXEC dataset and change each occurrence of -HILEV- to the high level qualifier for the IRM application datasets, thilev:

pgm_parm ="'PFX(thilev)'"

You may now invoke the IRM ISPF User Interface by issuing the following command from ISPF option 6:

EXEC 'rhilev.RKAUEXEC(KAUUISPF)'



Note: If you wish, you may copy, or move, the KAUUISPF exec to an exec library in the TSO/E LOGON procedure SYSEXEC library concatenation, so that users may invoke the interface by simply entering KAUUISPF from any ISPF ommand line.

Invoking the ISPF Interface

When you invoke the IRM ISPF User Interface you will be presented with the main selection panel as illustrated in Figure 1 - IRM User Interface Main Selection Panel. The first time the interface is invoked it will automatically initialize the REXX Table dataset, rhilev.RKAUTBLR, and the IRM parameter dataset, rhilev.RKAUCMDS.

The REXX Table dataset will be populated with a complete set of starter REXX tables for the IRM applications. As you define your resources to the applications, the starter definitions, the ZZZZZZZZ records, may be deleted.

The IRM parameter dataset will be populated with a default set of parameter members for the applications. Customizing the IRM application parameter members will be addressed in subsequent install steps.



FIGURE 1. IRM User Interface Main Selection Panel

p

Actions GoTo Options Help PREFIX: TDAUAF.AF250

Integrated Resource Management System ISPF User Interface

__ 1 Started Task Manager - Resource Definitions__ 2 Started Task Manager - Resource Lists__ 3 Started Task Manager - Resource Schedules

__ 4 Message Manager - Resource Definitions__ 5 Command Manager - Resource Definitions__ 6 Schedule Manager - Resource Definitions

__ 7 VTAM Manager - Resource Definitions__ 8 Device Manager - Resource Definitions__ 9 Console Manager - Resource Definitions__ 10 Console Manager - Console Description

__ 11 Subsystem Resources - Selection Panel__ 12 AF/Operator Resources - Selection Panel

Command ===>Enter F1=Help F3=Exit F7=Bkwd F8=Fwd F10=Actions F12=Cancel

Updating Application Manager Definitions



OverviewThe following updates to the Application Manager AO command definitions are site specific. They are required to declare IRM internal variables to be set to their proper values.



Updating Help Dataset VariableFrom the main IRM ISPF interface panel select option 12 AF/Operator Resources. On the AF/OPERATOR Resources panel select option 5 Application Manager - AO Cmds Definitions. Tab to line number: 1008, enter a U(pdate), and press ENTER. Change the -tkogpfx-.TKOGHELP to thilev.TKANHENU and press the PF3 key to save this entry.

Actions Goto View Options Help------------------------------------------------------------------------------ Application Manager Row 7 to 29 of 72

Name: Nmbr: Actions Goto Options Help ----- ----- ----------------------------------------------------------- _ !AO! 1007 Application Manager AO Cmds Definition: !AO! U !AO! 1008 _ !AO! 1009 Command Data: _ !AO! 1010 SMF ID......... !AO! _ !AO! 1011 Description.... Description for: OPER '&AOSUBSYS DCL____ _ !AO! 1012 _ !AO! 1013 Command Text... OPER '&AOSUBSYS DCL AOHLPDSN CHAR(44) SY _ !AO! 1014 STEM DUPOK INIT(''-tkogpfx-.TKOGHELP'')' _ !AO! 1015 ________________________________________ _ !AO! 1017 ________________________________________ _ !AO! 1018 _ !AO! 1020 _ !AO! 1021 Command ===> _ !AO! 1022 Enter F1=Help F3=Exit F4=Prompt F10=Actions F12=Cancel _ !AO! 1023 _ !SV! 1024 Description for: TRAP ADD(@AFOSLIP) TOD( 91/11/02 09:00:00 _ !SV! 1025 Description for: TRAP ADD(@AFOSLIP) TOD( 91/11/02 09:00:00 _ !ZZ! 1026 Description for: AO NOQUIET(MSG(0095)) 91/11/02 09:00:00 _ !ZZ! 1027 Description for: AO NOQUIET(MSG(0405)) 91/11/02 09:00:00 _ !ZZ! 1028 Description for: AO NOQUIET(MSG(0512)) 91/11/02 09:00:00 _ !ZZ! 1029 Description for: AO NOQUIET(MSG(0619)) 91/11/02 09:00:00 _ !ZZ! 1030 Description for: AO NOQUIET(MSG(3300)) 91/11/02 09:00:00 _ !ZZ! 1031 Description for: AO NOQUIET(MSG(3301)) 91/11/02 09:00:00

Command ===> Scroll ===> CSR F1=Help F3=Exit F7=Bkwd F8=Fwd F10=Actions F12=Cancel



Updating Company Name VariableTab down to Nmbr 1010 and enter a U(pdate) and press ENTER. Change the Company Name to your Company's name, and then press the PK3 key to save.

Actions Goto View Options Help

------------------------------------------------------------------------------

Application Manager Row 9 to 30 of 72

Name: Nmbr: Actions Goto Options Help

----- ----- -----------------------------------------------------------

_ !AO! 1009 Application Manager AO Cmds Definition: !AO!

U !AO! 1010

_ !AO! 1011 Command Data:

_ !AO! 1012 SMF ID......... !AO!

_ !AO! 1013 Description.... Description for: OPER '&AOSUBSYS DCL____

_ !AO! 1014

_ !AO! 1015 Command Text... OPER '&AOSUBSYS DCL COMPANY CHAR(25) SY

_ !AO! 1017 STEM DUPOK INIT(''Company Name'')'

_ !AO! 1018 ________________________________________

_ !AO! 1020 ________________________________________

_ !AO! 1021

_ !AO! 1022

_ !AO! 1023 Command ===>

_ !SV! 1024 Enter F1=Help F3=Exit F4=Prompt F10=Actions F12=Cancel

_ !SV! 1025

_ !ZZ! 1026 Description for: AO NOQUIET(MSG(0095)) 91/11/02 09:00:00






_ SP23 1005 Description for: OPER '&AOSUBSYS DCL 00/05/19 11:03:01

_ SP23 1016 Description for: OPER '&AOSUBSYS DCL 00/05/19 11:03:28

Command ===> Scroll ===> CSR

. . . . . . . . . . . . . . . . . . . . . . . . . . .



Updating Company Address1 VariableTab down to Nmbr 1011 and enter a U(pdate) and press ENTER. Change the Company Address to your Company's Address ensure that you only enter the street address and that your entry is not more than 25 chars. Press the PK3 key to save.

Actions Goto View Options Help ------------------------------------------------------------------------------ Application Manager Row 10 to 31 of 72

Name: Nmbr: Actions Goto Options Help ----- ----- ----------------------------------------------------------- _ !AO! 1010 Application Manager AO Cmds Definition: !AO! U !AO! 1011 _ !AO! 1012 Command Data: _ !AO! 1013 SMF ID......... !AO! _ !AO! 1014 Description.... Description for: OPER '&AOSUBSYS DCL____ _ !AO! 1015 _ !AO! 1017 Command Text... OPER '&AOSUBSYS DCL COADDR1 CHAR(25) SY _ !AO! 1018 STEM DUPOK INIT(''Company Address'')' _ !AO! 1020 ________________________________________ _ !AO! 1021 ________________________________________ _ !AO! 1022 _ !AO! 1023 _ !SV! 1024 Command ===> _ !SV! 1025 Enter F1=Help F3=Exit F4=Prompt F10=Actions F12=Cancel _ !ZZ! 1026 _ !ZZ! 1027 Description for: AO NOQUIET(MSG(0405)) 91/11/02 09:00:00 _ !ZZ! 1028 Description for: AO NOQUIET(MSG(0512)) 91/11/02 09:00:00 _ !ZZ! 1029 Description for: AO NOQUIET(MSG(0619)) 91/11/02 09:00:00 _ !ZZ! 1030 Description for: AO NOQUIET(MSG(3300)) 91/11/02 09:00:00 _ !ZZ! 1031 Description for: AO NOQUIET(MSG(3301)) 91/11/02 09:00:00 _ SP23 1005 Description for: OPER '&AOSUBSYS DCL 00/05/19 11:03:01 _ SP23 1016 Description for: OPER '&AOSUBSYS DCL 00/05/19 11:03:28 _ SP23 1019 Description for: OPER '&AOSUBSYS DCL 00/05/19 11:04:08

Command ===> Scroll ===> CSR . . . . . . . . . . . . . . . . . . . . . . . . . . .



Updating Company Address2 VariableTab down to Nmbr 1012 and enter a U(pdate) and press ENTER. Change Company City, State Zip to your Company's City, State Zip. Ensure your entry is not more than 25 chars and then press the PK3 key to save.

Actions Goto View Options Help ------------------------------------------------------------------------------ Application Manager Row 11 to 32 of 72

Name: Nmbr: Actions Goto Options Help ----- ----- ----------------------------------------------------------- _ !AO! 1011 Application Manager AO Cmds Definition: !AO! U !AO! 1012 _ !AO! 1013 Command Data: _ !AO! 1014 SMF ID......... !AO! _ !AO! 1015 Description.... Description for: OPER '&AOSUBSYS DCL____ _ !AO! 1017 _ !AO! 1018 Command Text... OPER '&AOSUBSYS DCL COADDR2 CHAR(25) SY _ !AO! 1020 STEM DUPOK INIT(''Company City, State Zi _ !AO! 1021 p'')' _ !AO! 1022 ________________________________________ _ !AO! 1023 _ !SV! 1024 _ !SV! 1025 Command ===> _ !ZZ! 1026 Enter F1=Help F3=Exit F4=Prompt F10=Actions F12=Cancel _ !ZZ! 1027 _ !ZZ! 1028 Description for: AO NOQUIET(MSG(0512)) 91/11/02 09:00:00 _ !ZZ! 1029 Description for: AO NOQUIET(MSG(0619)) 91/11/02 09:00:00 _ !ZZ! 1030 Description for: AO NOQUIET(MSG(3300)) 91/11/02 09:00:00 _ !ZZ! 1031 Description for: AO NOQUIET(MSG(3301)) 91/11/02 09:00:00 _ SP23 1005 Description for: OPER '&AOSUBSYS DCL 00/05/19 11:03:01 _ SP23 1016 Description for: OPER '&AOSUBSYS DCL 00/05/19 11:03:28 _ SP23 1019 Description for: OPER '&AOSUBSYS DCL 00/05/19 11:04:08 _ SP23 1032 Description for: OPER '&AOSUBSYS DCL 00/05/19 11:04:37

Command ===> Scroll ===> CSR . . . . . . . . . . . . . . . . . . . . . . . . . . .

Allocating AF/OPERATOR Message Log MCF Resource DefinitionsFrom the IRM ISPF interface main panel, select Option 4 - Message Manager and enter the following message traps.

The following four traps are required to enable the automatic archiving of the RKOGLM01 - 06 DASD message log datasets:

n Type ADD from the Command ===> line, press ENTER, type !AOP0651A for the message name and type the text !AOP0651 DASD MESSAGE LOG NOW RECORDING under description and then press ENTER. Locate the following fields and enter the indicated values:



Alias = !AOP0651Keyword = AUTOWTO Pattern = !AOP0651*Enable = 1AOTRAP = 1Suppress = 1

Press the PF3 key to save your entry.

n Type ADD from the Command ===> line, press ENTER, type !AOP0651B for the message name and type the text !AOP0651 DASD MESSAGE LOG NOW RECORDING under description and then press ENTER. Locate the following fields and enter the indicated values:

Alias = !AOP0651Keyword = AUTOWTO Pattern = !AOP0651 DASD MESSAGE LOG * - *LOGDSN *Enable = 1AOTRAP = 1Suppress = 1Action = LET ZMSGLOG = ''&&LOGDSN''


n Type ADD from the Command ===> line, press ENTER, type !AOP0652A for the message name and type the text !AOP0652A DASD MESSAGE LOG RECORDING END under description and then press ENTER. Locate the following fields and enter the indicated values:

Alias = !AOP652Keyword = AUTOWTO Pattern = !AOP0652 DASD MESSAGE LOG * - *LOGDSN *Enable = 1AOTRAP = 1Suppress = 1Action = OPER ''S AFMSG,LOGDSN=&&LOGDSN,SYS=&AOSMFID''


n Type ADD from the Command ===> line, press ENTER, type !AOP0652B for the message name and type the text !AOP0652B DASD MESSAGE LOG RECORDING END under description and then press ENTER. Locate the following fields and enter the indicated values:



Alias = !AOP652Keyword = AUTOWTO Pattern = !AOP0652 DASD MESSAGE LOG * - *LOGDSN *Enable = 1AOTRAP = 1Suppress = 1Action = LET ZMSGLST = ''&&LOGDSN''


Allocating AF/OPERATOR Retain Log MCF Resource Definition

Note: This step can only be performed only after the ISPF interface has been installed as discussed on page 84.

The following trap is required to enable automatic archiving of the RKOGLH01 - 02 retain DASD log datasets:

n Type ADD from the Command ===> line, press ENTER, type !AOP0743 for the message name and type the text !AOP0743 End of file reached on RKOGLHnn under description and then press ENTER. Locate the following fields and enter the indicated values:

Alias = !AOP0743Keyword = AUTOWTO Pattern = !AOP0743 End of file reached on *LOGDSN *Enable = 1AOTRAP = 1Suppress = 1Action = OPER ''S AFRET,LOGDSN=&&LOGDSN,SYS=&AOSMFID''



Configuring AF/OPERATOR Environment


OverviewThe following sections describe how to configure the AF/OPERATOR environment for the IRM and how to configure the IRM environment and the IRM applications to best suit your needs.

The AF/OPERATOR parmlib members will reside in the rhilev.RKANPAR dataset. The IRM parmlib members will reside in the rhilev.RKAUCMDS dataset.



Creating AF/OPERATOR Parmlib MembersCopy each of the AF/OPERATOR parmlib members listed in the following table from the rhilev.TKAUSAMP dataset to the rhilev.RKANPAR dataset.

After copying each of the above members perform the following edits to the KAU0OGAO, KAU0OGCK, and KAU0OGMN members changing the following statements in the rhilev.RKANPAR dataset:

n If your site uses JES3 comment out the JESTBL(KOGJ2TAB) statement by placing an * as the first character in the statement and remove the * from the *JESTBL(KOGJ3TB) statement.

n Create a new member for each system that will run under IRM using KAU0SMFD as a model. For example, if the SMFID is SYSA, then the new member will be KAU0SYSA.

This member will be concatenated to the RKANPAR DD statement within AF/OPERATOR started task JCL and contains the system specific AF/OPERATOR parameters.

Edit the newly created member (in this example it will be KAU0SYSA) and make the following changes:

n Change the CONSOLE statements PREFIX parameter value to the following recmmended value:

A = Automation,0 = the Relative Order of the AF/OPERATOR Started task.SA = last two chars of the SMFID.

n Change the SYSID to the SMFID.

Table 11. AF/OPERATOR Parmlib Members


KAU0OGAO Parameters for fully automated IPL, type AO

KAU0OGCK Parameters for checkpoint restart IPL, type CK

KAU0OGMN Parameters for manual/maintenance IPL, type MN

KAU0SMFD System parameters used with all start types



n Change the LINKID to match the value determined during the CICAT install of AF/OPERATOR.

Note: If you have determined that you wish to have a unique AF/OPERATOR SUBSYS id for each MVS image then you must perform the following additional steps.

n Remove the SUBSYS statement from each of the KAU0OGAO, KAU0OGCK, and KAU0OGMN members and insert a SUBSYS statement into each of the KAU0smfd members after the SYSID statement as shown below:

...SYSID(SYSA), SUBSYS(AOSA),...

The same naming convention used for the PREFIX parameter is recommended for use here as well.



Creating IRM Parmlib Members

Master Calendar Parameters

Overview

The master calendar parameters are stored in a parmlib member in the rhilev.RKAUCMDS dataset. If the KAUAMSTR member does not exist in the above mentioned dataset then copy the KAUAMSTR listed in the following table from the rhilev.TKAUCMDS dataset to the rhilev.RKAUCMDS dataset.

KAUAMSTR parmlib member is the US version; KAUAMDEU is the German master calendar parmlib member; and the KAUAMITA is the Italian master calendar parmlib member. More international calendar parmlib members will be added as the need arises.

Parameter Syntax

The syntax of the parameters and their use are:

WORKWEEK(abcdefg,smfid)

The WORKWEEK() parameter is used to define the business days for a normal week. abcdefg represents the 7 days of the week (Sun-Sat). Code a 1 if the day is normally a business day and 0 if not. The smfid is optional and is used to specify the default work week or a system specific override to the work week. Omit smfid or code the DEFAULT keyword to define the default work week.

For example:

WORKWEEK(0111110) The default work week is Mon-Fri.WORKWEEK(1111111) The default work week is Sun-Sat.WORKWEEK(0111110,DEFAULT) The default work week is Mon-Fri.WORKWEEK(1111111,DEFAULT) The default work week is Sun-Sat.



To create a system specific override to the work week, enter the WORKWEEK() parameter for the system after the default work week, and specify the system's SMF ID:

Note: If the WORKWEEK() parameter is omitted, Mon-Fri will be used for the default work week.

The HOLIDAYS() parameter is used to define holidays. Each record after the parameter must contain a holiday date and value in the form:

HOLIDAYS(smfid)

yyyy/mm/dd = 1 or 0 (code a 1 if the day is a holiday and 0 if not).

The smfid is optional and is used to specify the default holidays or a system specific override to the holidays. Omit smfid or code the DEFAULT keyword to define the default holidays.

To create a system specific override to the holidays, enter the HOLIDAYS() parameter for the system after the default holidays, and specify the system's SMFID.

WORKWEEK(0111110) The default work week is Mon-Fri, but on system SYSA the work week is Sun-Sat, and on SYSB the work week is Mon-Thu.

WORKWEEK(1111111,SYSA)

WORKWEEK(0111100,SYSB)



For example:

Note: If the HOLIDAYS() parameter is omitted, no holidays are used. The default HOLIDAYS() parameter supplied here includes the holidays observed by U.S. banks and the U.S. Federal Government for the years 1998-2027

HOLIDAYS(DEFAULT)1998/01/01 = 11998/01/19 = 11998/02/16 = 11998/05/25 = 11998/07/03 = 11998/09/07 = 11998/10/12 = 11998/11/11 = 11998/11/26 = 11998/12/25 = 1... etc ....

HOLIDAYS(SYSA) However, on SYSA Columbus day is not a holiday and the day after Thanksgiving Day is.

1998/10/12 = 01998/11/27 = 1

Table 12. Master Calendar Parmlib Members


KAUAMSTR Master Calendar Parameters

KAUAMDEU Master Calendar Parameters - Germany

KAUAMITA Master Calendar Parameters - Italy



Custom Calendar Parameters

Custom calendar parameters are stored in a parmlib member in the rhilev.RKAUCMDS dataset. Each system may have its own custom calendar parmlib member. The name of the parmlib member for a system is @CLNsmfd, where smfd is the SMFID of that system.

Custom calendar parameters can also be stored in the global RKAUCMDS parmlib member called KAUACPRM. The custom calendar definitions specified in the KAUACPRM member will be used for every system. If neither of the custom calendar parmlib members are found, no custom calendars will be defined.

Create a system specific custom calendar parmlib member in the rhilev.RKAUCMDS dataset by copying the KAUACSMF member to a new member whose name is @CLNsmfd, where smfd is the SMFID of that system. Edit the KAUACPRM and @CLNsmfd members in the rhilev.RKAUCMDS dataset and add the parameters described in the following section that are necessary or appropriate for your environment.

Table 13. Custom Calendar Parmlib Members


KAUACPRM Global Custom Calendar Parameters

@CLNsmfd System Custom Calendar Parameters



The valid custom calendar parameters and their meaning are as follows:

CALENDAR( ) The CALENDAR() keyword parameter indicates the beginning of a calendar definition. The CALENDAR() keyword parameter is required and must precede any date_value statements. As many date_value statements as are required may follow the CALENDAR() keyword parameter.

The varname value specifies the AF/OPERATOR system variable that represents the calendar. A valid AF/OPERATOR system variable name must be specified.

DEFAULT( ) The optional DEFAULT() parameter specifies the default value of the calendar variable. Valid values are 0 and 1 with 1 indicating that the calendar is enabled and 0 indicating that the calendar is disabled by default. If the DEFAULT() parameter is not specified, a default of 0 will be used.

date_value The date_value statement is used to specify the value of the calendar variable on a specific date. The first token of a date_value statement must be a date in Extended Ordered format, yyyy/mm/dd.

The token following the equal sign sets the value of the calendar variable on the specified date. Valid values are 0 and 1 with 1 indicating that the calendar is enabled and 0 indicating that the calendar is disabled on the specified date.

Note: For compatibility purposes, dates may be specified in USA format, mm/dd/yy, but this is not the recommended format.

VARIABLE( ) The VARIABLE() keyword parameter is used to specify an AF/OPERATOR system variable that is needed for IF() statement processing. A SYSVGET() is performed for the specified variable so that it is available to REXX when the IF() statement condition is evaluated. Each AF/OPERATOR system variable used in IF() statement processing must be identified by a VARIABLE() statement prior to its use.

The ifvarnm value specifies the name of the AF/OPERATOR system variable. A valid AF/OPERATOR system variable name must be specified.



IF( ) The IF() keyword parameter is used to specify the value of a calendar variable based on a mathematical formula, or equation, as expressed by the condition value. The input to the condition value is most commonly one or more of the calendar variables produced by the master calendaring routine.Specifically, the condition value is used to specify a valid REXX expression. If the REXX expression evaluates to true, the value of the calendar variable will be set to the converse of the DEFAULT() value.

Note: The IF() keyword parameter and a set of date_value statements can be used in combination to set the value of a calendar variable (see Figure 2 on page 107 for an example).



FIGURE 2. Custom Calendar Parameter Examples

CALENDAR(ZIMSXTRA) DEFAULT(0)1994/08/03 = 11994/08/08 = 11995/02/01 = 1

Creates the ZIMSXTRA calendar variable,which has a default value of 0 (disabled) & which has a value of 1 (enabled) on 1994/08/03, 1994/08/08, etc.

CALENDAR(HOLIDAY) DEFAULT(0)1994/12/25 = 1

Creates the HOLIDAY calendar variable,which has a default value of 0 (disabled) & which has a value of 1 (enabled) on 1994/12/25.

CALENDAR(ANOTRDAY) DEFAULT(1)1994/01/01 = 0

Creates the ANOTRDAY calendar variable,which has a default value of 1 (enabled) and which has a value of 0 (disabled) on 1/1/1994.

CALENDAR(SUNDAY#3) DEFAULT(1)VARIABLE(@APLCL02)VARIABLE(@APLCL03)IF(@APLCL02=1 & @APLCL03=3)

Creates the SUNDAY#3 calendar variable, which has a default value of 1 (enabled) and which has a value of 0 (disabled) on the 3rd Sunday of the month.

CALENDAR(S3ANDFRI) DEFAULT(1)VARIABLE(@APLCL02)VARIABLE(@APLCL03)IF(@APLCL02=1 & @APLCL03=3)IF(@APLCL02=6)

Creates the S3ANDFRI calendar variable,which has a default value of 1 (enabled) and which has a value of 0 (disabled) on the 3rd Sunday of the month & Fridays.

CALENDAR(BUSDAY#3) DEFAULT(0)VARIABLE(@APLCL05)IF(@APLCL05=3)

Creates the BUSDAY#3 calendar variable,which has a default value of 0 (disabled) & which has a value of 1 (enabled) on the third business day of the month.

CALENDAR(NOTBDY#3) DEFAULT(1)VARIABLE(@APLCL05)IF(@APLCL05=3)

Creates the NOTBDY#3 calendar variable, which has a default value of 1 (enabled) and which has a value of 0 (disabled) on the third business day of the month.

CALENDAR(NOTBDY#3) DEFAULT(1)VARIABLE(@APLCL05)IF(@APLCL05=3 | @APLCL05=0)

Creates the NOTBDY#3 calendar variable,which has a default value of 1 (enabled) and which has a value of 0 (disabled) on the third business day of the month and any non-business day.

CALENDAR(NOTBDY#3) DEFAULT(1)VARIABLE(@APLCL05)IF(@APLCL05=3 | @APLCL05=0)2000/08/07 = 02000/08/08 = 0

Creates the NOTBDY#3 calendar variable,which has a default value of 1 (enabled) and which has a value of 0 (disabled) on the third business day of the month, any non-business day, & 2000/08/07, 2000/08/08, etc.



System Variable Delete Parameters

System variable delete parameters are stored in a parmlib member in the rhilev.RKAUCMDS dataset. Each system may have its own system variable delete parmlib member. The name of the parmlib member for a system is @SYSsmfd, where smfd is the SMFID of that system.

System variable delete parameters can also be stored in the global RKAUCMDS parmlib member called KAUASPRM. The parameters specified in the KAUASPRM member will be used for every system. If neither of the system variable delete parmlib members are found, no variables will be deleted.

Create a system specific system variable delete parmlib member in the rhilev.RKAUCMDS dataset by copying the KAUASSMF member to a new member whose name is @SYSsmfd, where smfd is the SMFID of that system. Edit the KAUASPRM and @SYSsmfd members in the rhilev.RKAUCMDS dataset and add the parameters described in the following section that are necessary or appropriate for your environment.

The valid system variable delete parameters and their meaning:

Table 14. System Variable Delete Parmlib Members


KAUASPRM Global System Variable Delete Parameters

@SYSsmfd System System Variable Delete Parameters

VARNAME() The VARNAME() keyword parameter is used to specify the name of an AF/OPERATOR system variable to delete. The value specified for varname must be a valid AF/OPERATOR system variable name. For example, the following entry will delete the AF/OPERATOR system variable named SYSVAR00 if the variable exists:

VARNAME(SYSVAR00)



Table Manager Parameters

Table Manager initialization parameters are stored in a parmlib member in the rhilev.RKAUCMDS dataset. Each system may have its own Table Manager initialization parmlib member. The name of the parmlib member for a system is @TBLsmfd, where smfd is the SMFID of that system.

Table Manager initialization parameters can also be stored in the global RKAUCMDS parmlib member called KAU$PARM. The parameters specified in the KAU$PARM member will be used for every system. If a parameter is specified in both parmlib members, the value specified in the local parmlib member will override the value in the global member.

PATTERN() The PATTERN() keyword parameter is used to specify a valid pattern for a set of AF/OPERATOR system variables to delete. The value specified for pattern must be a valid AF/OPERATOR pattern. For example, the following entry will delete all AF/OPERATOR system variables whose name begins with SYSVAR and ends with two numbers:

PATTERN(SYSVAR##)

Table 15. Table Manager Parmlib Members


KAU$PARM Global Table Manager Parameters

@TBLsmfd System Table Manager Parameters



The KAU$PARM DD may be specified in the AF/OPERATOR startup procedure to identify the Table Manager initialization parmlib member or members (see Figure 3 for an example of the KAU$PARM DD). If the KAU$PARM DD is specified via the AF/OPERATOR startup procedure, those members will be used by the Table Manager initialization routine. If the KAU$PARM DD is not specified, the initialization routine will dynamically allocate the Table Manager parmlib members in the cataloged version of the rhilev.RKAUCMDS dataset.

If neither of the Table Manager parmlib members are found, the default parameter values will be used to initialize the Table Manager.

FIGURE 3. AF/OPERATOR Startup Procedure KAU$PARM DD

Create a system specific Table Manager parmlib member in the rhilev.RKAUCMDS dataset by copying the KAU$PSMF member to a new member whose name is @TBLsmfd, where smfd is the SMFID of that system. Edit the KAU$PARM and @TBLsmfd members in the rhilev.RKAUCMDS dataset and add the parameters described in the following section that are necessary or appropriate for your environment

//KAU$PARM DD DISP=SHR,DSN=&RKAUPFX..RKAUCMDS(KAU$PARM),// VOL=SER=DASD01,UNIT=3390...

OR

//KAU$PARM DD DISP=SHR,DSN=&RKAUPFX..RKAUCMDS(KAU$PARM),// VOL=SER=DASD01,UNIT=3390// DD DISP=SHR,DSN=&RKAUPFX..RKAUCMDS(KAU$&SYS),// VOL=SER=DASD01,UNIT=3390...



The valid Table Manager initialization parameters and their meaning are as follows:

ALLOC() The ALLOC() keyword parameter is used to specify a storage allocation option for the REXX Table Manager. The allocation option will be passed to the REXX Table Manager when it is started. Valid values are: TSO and NONTSO. The default is NONTSO.

For all but the largest IRM implementations, the TSO allocation should be adequate and is recommended.

VOLSER() The VOLSER() keyword parameter is used to specify the volume serial number of the direct access device on which all of the IRM application and user datasets are located.

The default option for any IRM dataset allocation is to use the cataloged version of the dataset. This parameter is used to override the default option and allocate the datasets on the specified volume.

UNIT() The UNIT() keyword parameter is used to specify the unit type of the direct access device on which the IRM datasets are located. The UNIT() parameter is used in conjunction with the VOLSER() parameter. If UNIT() is specified, a VOLSER() is required.

FREE() The FREE() keyword parameter is used to specify whether or not the table dataset allocations should be freed once the tables have been loaded. Freeing allocations will reduce below-the-line storage use. Valid values are: YES and NO. The default is YES.

PREFIX() The PREFIX() keyword parameter is used to specify the high level qualifier for the IRM application datasets. This parameter is optional; by default the high level qualifier for the IRM application datasets, thilev, is set to the high level qualifier for the IRM user datasets, rhilev. This parameter is needed only if the high level qualifier for the IRM application datasets and the high level qualifier for IRM user datasets are not the same.



TABLE() The TABLE() keyword parameter is used to specify the name and location of a user-defined table. Multiple TABLE() parameters may be specified. The TABLE() parameter must be specified in the following format:

TABLE(tbname,dsname)

The tbname value specifies the name of the table, as well as the DD name that will be used to allocate the table for loading. The dsname value is used to specify the name of the dataset which contains the table. The dsname value can specify a sequential dataset, DATA.SET, or a member of a PDS, DATA.SET(MBR).The volser and unit values for the table dataset may be specified in the following format:

TABLE(tbname,dsname,volser,unit)

If a volser is specified, a unit must be specified.CMDEXIT() The CMDEXIT() keyword parameter is used to specify the name

of a user-defined exit for the TBL command. The CMDEXIT() parameter is optional.



EMCS Consoles

In order to use the EMCS Consoles you must complete the following parameter file (KAUAEPRM). In order to use EMCS consoles, copy member KAUAEPRM from thilev.TKAUCMDS to rhilev.RKAUCMS. To activate the EMCS consoles, edit member rhilev.RKAUCMDS(TKAUAEPRM) in the following format:

CONSOLE(LIMIT(LMT_OPT),PREFIX(PRE_OPT))

The valid EMCS Console initialization parameters and their meaning are as follows:

Examples

CONSOLE(PREFIX(A223),LIMIT(1))

creates 1 console name with the prefix A223. Console name available for IRM will be A223001.

CONSOLE(PREFIX(A223))

creates 4 console names with the prefix A223. Console names available for IRM will be A223001 through A223004.

CONSOLE(LIMIT(2),PREFIX(A223))

creates 2 console names with the prefix A223. Console names available for IRM will be A223001 and A223002.

CONSOLE() Specifies EMCS console definition for IRM. A CONSOLE() statement is required that encompasses LIMIT and PREFIX options. Multiple CONSOLE() statements may be specified.

LIMIT() Indicates the number of EMCS console names to be created with the given prefix. If the limit is not specified, a default value of 4 will be used.

lmt_opt Represents limit scope value for the EMCS console creation. A valid 4-digit length non-zero numeric value must be specified.

PREFIX() Indicates prefix for the EMCS console names to be used for IRM.pre_opt Represents prefix scope value for the EMCS console creation. A

valid IRM console prefix must be specified. It must not be same as AF/OPERATOR console name prefix.



Started Task Manager Parameters

Overview

Initialization parameters are stored in a member in the RKAUCMDS dataset. Each system may have its own initialization parmlib member. The name of the parmlib member for a system is @RCFsmfd where smfd is the SMFID of that system.

Initialization parameters can also be stored in the global RKAUCMDS parmlib member called KAURPARM. The parameters specified in the KAURPARM member will be used for every system. If a parameter is specified in both parmlib members, the value specified in the local parmlib member overrides the value in the global member.

If neither of the application's parmlib members are found, the default parameter values will be used to initialize the application.

Parameter Syntax

The syntax of the parameters and their use are as follows:

NOBATCH(day,start,end)

Specifies a global no-submit batch window for the Started Task Manager.

The day parameter must specify a valid three character day-of-week (Sun - Sat).

The start and end parameters specify the start and end times of the window in twenty-four hour (military time) format. The default start time is 00:00:00 and the default end time is 24:00:00.

Multiple NOBATCH statements may be specified. For example:

NOBATCH(SUN,02:00:00,06:00:00)

NOBATCH(SUN,08:00:00,12:00:00)

NOBATCH(SUN,14:00:00,16:00:00)

NOBATCH(SAT,02:00:00,06:00:00)

NOBATCH(SUN,,06:00:00) /* WINDOW = 00:00:00 to 00:06:00 */

NOBATCH(SUN,06:00:00) /* WINDOW = 06:00:00 to 24:00:00 */



Table 16. Started Task Manager Parmlib Members


KAURPARM Global Started Task Manager Parameters

@RCFsmfd System Started Task Manager Parameters



SYSPLEX ConfigurationThis section provides you with information for configuring your SYSPLEX as well as recommendations for default configurations.

Defining Coupling Facility List structure

For IRM v500 to be able to exploit SYSPLEX and to make SYSPLEX related functions available to the IRM, a new List Structure must be defined to the Coupling Facility as described in the following section.

CFRM Policy

STRUCTURE NAME(KAU_IRM_L01) INITSIZE(1000) SIZE(4000) PREFLIST(CF02)

Additional recommendations for defining your structure include:

1. INITSIZE - 90% of Structure size calculated above.

2. MINSIZE - 90% of Structure size calculated above.

3. ALLOWAUTOALT(YES/NO) YES recommended. FULLTHRESHOLD(Value) 90 Recommended.

Allowing ALLOWAUTOALT as YES and FULLTHRESHOLD as 90 allows XCF to automatically initiate an ALTER to increase structure size. IRM v500 supports dynamic altering of the structure size (both manual and system initiated).

4. PREFLIST(cfname1,cfname2,...,cfname8), EXCLLIST(strname1,strname2,...,strname8) & ENFORCEORDER(NO/YES).

You should select the above parameters depending on the CFLEVEL, failure independence. Refer "CFRM Parameters" in "MVS Setting Up a Sysplex".

5. REBUILDPERCENT(value) - This parameter must be chosen with respect to the current SFM policy for the SYSPLEX.

6. DUPLEX(DISABLED/ALLOWED/ENABLED) - DISABLED recommended.



XES List Structure Size Estimation

The amount of space required for the allocation of the XES List Structure used by IRM for the SYSPLEX support depends upon:

n the number of participating IRMs,

n the number of entries stored in XES List structure,

n the level of coupling facility, and

n the version of the operating system.

When an XES Structure is defined to the Coupling Facility, certain lower level attributes are not specified. These lower level attributes are only supplied when the first connection is made and the structure is first allocated. However, the actual structure size attribute must be specified in the definition. This section assists in determining the size of the structure required for the automation.

Currently IRM v500 supports a maximum of 48 IRM participants. This is the maximum number of users irrespective of it being currently connected. For example, once a structure is allocated, then it will accept a maximum of 48 new IRM connections throughout its life. Each new connection is identified by maintaining a unique key (IRMID = SMFID+AOSUBSYS). Once connected, each user is allocated a specific Sub-list and is reused for the life of the structure even if the IRM region is restarted as long as the IRMID remains unchanged.

Note: If an IRM with AOSUBSYS SUBA is started from SYSA and is subsequently brought down and then restarted in SYSB then it is referred to as a new connector since the IRMID changes with the restart.

To calculate the IRM structure size, perform the following:

1. Determine the total number of entry counts:

– TI = Total IRMs participating in the SYSPLEX. One or more can be participating from within an image including all active and inactive IRMs. The total number cannot exceed 48.

– TT = (TI x N) = Total IRM tasks within the SYSPLEX where N is the number of tasks per IRM.



– TA = Total number of ARM tasks in the SYSPLEX.

– TC = Total number of COM Manager servers in the sysplex.

This makes total entries within the SYSPLEX:

TE = TT + TA + TC

2. To determine the structure size:

– Each IRM List entry requires 192 bytes. This includes the following:

– Each structure requires approximately 350k for structure information. This includes MVS and IRM control information.

– The total structure size (in k): (TE x 192 / 1024) + 350

– Allow a factor of 10% for future growth and round to the next higher 256K boundary.

3. The formula for structure size calculation (including 10% for future growth) is:

– Structure size (in k) = (Total Entries in SYSPLEX) * 0.21 + 385

4. For example:Assume a SYSPLEX consists of 8 MVS images and a total of 20 IRMs participate in the SYSPLEX. Also assume that 500 tasks are defined to each IRM, 30 ARM tasks are defined to the entire SYSPLEX, and 72 COM Manager servers are defined to the entire SYSPLEX. This means that:

– Total Entry counts: TE = (500 x 20) + 30 + 72 = 10102

– Structure size (in k): (10102 x 0.21) + 385 = 2506k

– Rounding to the next 256k boundary yields a total of 2560k

XES List Structure Usage

IRM supports Planned User Managed Rebuild Processing. For XES List Structures, Duplex rebuild is not permitted. During the rebuild progress, the structure is temporarily unavailable. IRM does not allow new connections to the List Structure when a rebuild is in progress. A new connect request will automatically be rejected during the rebuild.



The structure is persistent, so that data is retained even when there are no active IRM systems connected to it. In case of structure failure or loss of connection to the structure event, the afflicted IRM users should be restarted.

Note: For Top Secret, the IRM needs “ALL” access to the Coupling Facility List structure.

Defining ARM Resources

When defining ARM resources to your SYSPLEX, the following policy should be used:

RESTART_GROUP(ARMGROUP1) TARGET_SYSTEM(SYSG) ELEMENT(SYSCICS_CICS2353) RESTART_METHOD(BOTH,S, 'RCF ARM CICS2353')

Note: The command to start the resource is an IRM RCF command.


Converting to IRM Version 500

Converting to IRM Version 500This section describes the process for converting REXX Tables to V500 from V400 format.

Formatting REXX TablesThe KAU@#500 is used to reformat V400 IRM user REXX Tables to V500 IRM user REXX Tables.

Copy the KAU@#500 member from thilev.TKAUSAMP dataset to the rhilev.RKAUSAMP. Edit the copy of KAU@#500 in the rhilev.RKAUSAMP dataset and perform the following tasks:


2. Fill in the JCL SET statements for the APLPFX, USRPFX and OLDPFX variables. The APLPFX variable should be set to the high level qualifier for the IRM application datasets, thilev, the USRPFX variable should be set to the high level qualifier for the new (V500) IRM user datasets, rhilev, and the OLDPFX variable should be set to the high level qualifier for the old (V400) IRM user datasets, rhilevo as in the following example:

//*

// SET APLPFX=thilev

// SET USRPFX=rhilev

// SET OLDPFX=rhilevo

//*

Note: If you are using the alternate configuration for the IRM run-time libraries, use rhilev.@system## for the value of the USRPFX variable and use rhilevo.@system## for the value of the OLDPFX variable.

// SET USRPFX=rhilev.@system###

// SET OLDPFX=rhilevo.@system##

Converting to IRM Version 500



//STEPLIB DD DISP=SHR,DSN=&APLPFX..RKAURALT

// DD DISP=SHR,DSN=&APLPFX..TKAULOAD

...

Notes: While reformatting the IRM user datasets, the old version of the IRM user datasets should not be edited. If they are being edited during job execution, results will be unpredictable.

After reformatting, any changes made to the old version (V400) of the IRM user datasets will not be reflected in V500 and will need to be made in V500 also.

IRM Optional Customization 115

IRM Optional Customization

IntroductionThis chapter describes the Integrated Resource Manager optional customization and provides instructions on how to install and configure the chosen options.

3

Allocating Optional Datasets



OverviewThe following table identifies the standard configuration for the optional run-time libraries.I

Installation StepsThe following table contains the steps you must perform to install optional datasets.

Table 17. Optional Run-time Libraries - Standard Configuration

Dataset Description

rhilev.RKAU@XRF IMS/XRF Control Region Status File

rhilev.@system##.RKOGARCU AF/OPERATOR User Message Log Archive

rhilev.@system##.RKOGLU01-06 AF/OPERATOR User Message Logs

rhilev.@system##.RKOGSLF0-1 AF/OPERATOR SLF Journal Files

rhilev.@system##.RKANPAR POVI Parm Dataset

rhilev.@system##.RKOGNAM POVI NAM Database

rhilev.@system##.RKOGTDB POVI Table Database

rhilev.@system##.RKOGVLG POVI Viewlog Database

Table 18. Installing Optional Libraries


OPTIONAL LIBRARIES

1 Allocating IMS/XRF status file KAU$AXRF

2 Allocating POVI parameter dataset KAU$APAR

3 Allocating POVI NAM database dataset KAU$ANAM

4 Allocating POVI table database dataset KAU$ATDB

5 Allocating POVI viewlog database dataset KAU$AVLG



6 Allocating AF/OPERATOR user message logs KAU$AUSR

7 Allocating AF/OPERATOR user messages logs GDG KAU$GCHK

8 Allocating AF/OPERATOR SLF journals KAU$ASLF

Table 18. Installing Optional Libraries




Allocating IMS/XRF Status FileThe KAU$AXRF member is used to allocate the rhilev.RKAU@XRF dataset. The rhilev.RKAU@XRF dataset, or IMS/XRF Control Region Status File, is used to store the IMS control region status information created by the @XRFWRIT() function and accessed by the @XRFREAD() function.

Edit the copy of KAU$AXRF in the rhilev.RKAUSAMP dataset and perform the following tasks:







Allocating AF/OPERATOR SLF JournalsThe KAU$ASLF member is used to allocate a set of two SLF (Subsystem Logging Facility) journal datasets for the AF/OPERATOR address space.

Note: If you have already defined a set of two SLF journal datasets (RKOGSLF0 andRKOGSLF1) as part of the AF/OPERATOR install process, you may skip this step.

The datasets created in this step are referenced in the AF/OPR cataloged procedure addressed in a previous step in the install process.

Edit the copy of KAU$ASLF in the rhilev.RKAUSAMP dataset and perform the following tasks:










7. Edit the copy of the AF/OPR procedure in SYS1.PROCLIB and uncomment the RKOGSLF0 and RKOGSLF1 DD statements and cycle the AF/OPERATOR started task.



Allocating POVI Parameter DatasetThe KAU$APAR member is used to allocate a parameter dataset for the POVI, Programmerless Open VTAM Interface, address space.

Note: If you have already defined a POVI parameter dataset (RKANPAR) as part of the AF/OPERATOR install process, you should skip this step and proceed to the next step in the process.

The dataset created in this step will be referenced in the AF/OVI cataloged procedure that is addressed in a subsequent step in the install process.

Edit the copy of KAU$APAR in the rhilev.RKAUSAMP dataset and perform the following tasks:



//*//SET DSNPFX=rhilev.@system##//SET DSVSER=DASD01//SET DSUNIT=3390//*




Allocating POVI NAM Database DatasetThe KAU$ANAM member is used to allocate a NAM, Network Access Manager, database dataset for the POVI, Programmerless Open VTAM Interface, address space.

Note: If you have already defined a POVI NAM database (RKOGNAM) as part of the AF/OPERATOR install process, you may skip this step.


Edit the copy of KAU$ANAM in the rhilev.RKAUSAMP dataset and perform the following tasks:










Allocating POVI Table Database DatasetThe KAU$ATDB member is used to allocate a Table database dataset for the POVI, Programmerless Open VTAM Interface, address space.

Note: If you have already defined a POVI Table database (RKOGTDB) as part of the AF/OPERATOR install process, you may skip this step.


Edit the copy of KAU$ATDB in the rhilev.RKAUSAMP dataset and perform the following tasks:










Allocating POVI Viewlog Database DatasetThe KAU$AVLG member is used to allocate a Viewlog database dataset for the POVI, Programmerless Open VTAM Interface, address space.

Note: If you have already defined a POVI Viewlog database (RKOGVLG) as part of the AF/OPERATOR install process, you may skip this step.


Edit the copy of KAU$AVLG in the rhilev.RKAUSAMP dataset and perform the following tasks:



//*//SET DSNPFX=rhilev.@system##//SET DSVSER=DASD01//SET DSUNIT=3390//*







Allocating AF/OPERATOR User Message LogsThe KAU$AUSR member is used to allocate a set of six user DASD message log datasets for the AF/OPERATOR address space.

Note: If you have already defined a set of six user DASD message log datasets (RKOGLU01-RKOGLU06) as part of the AF/OPERATOR install process, you may skip this step.

The datasets created in this step are referenced in the AF/OPR cataloged procedure addressed in a previous step in the install process.

Edit the copy of KAU$AUSR in the rhilev.RKAUSAMP dataset and perform the following tasks:





4. Edit the copy of the AF/OPR procedure in SYS1.PROCLIB and uncomment the USERLG01 through USERLG06 DD statements and cycle the AF/OPERATOR started task.



Allocating User Message Log Archive GDGThe KAU$GUSR member is used to allocate a generation data group (GDG) index for the user DASD message log dataset archive process. The user DASD message log dataset archive process will copy a user DASD message log dataset to the +1 GDG member when the log dataset is closed. User DASD message log datasets are closed automatically when the dataset is filled or closed on demand in response to an AO FREE(USERLG) command.

The GDG index created in this step will be referenced in the AF/USR cataloged procedure that is addressed in a subsequent step in the install process.

Note: If you will be using a sysout-based archive process for the user DASD message log datasets, instead of the GDG-based archive process, you may skip this step.

Edit the copy of KAU$GUSR in the rhilev.RKAUSAMP dataset and perform the following tasks:






Alternate Configuration

Alternate ConfigurationA further distinction between the IRM application and user datasets is that the application datasets and user datasets need not have the same high level dataset name qualifier. All IRM application datasets must have the same high level qualifier, thilev, and all IRM user datasets must have the high level qualifier, rhilev, but thilev and rhilev do not have to be the same.

The alternate dataset configuration uses a system specific, as well as address space specific, high level qualifier for the IRM user datasets, rhilev.@system##. This is useful in situations where there must be separation of data between systems, where there is no commonality in the automation data between systems, or if you intend to run multiple AF/OPERATOR address spaces on a single OS/390 image.

Table 19. Required Run-time Libraries - Alternate Configuration

Dataset Description

thilev.RKAURALT REXX Alternate Library

rhilev.@system##.RKAU@RCF Started Task Manager Batch Status File

rhilev.@system##.RKAUARCI ISPF Change Log Archive GDG

rhilev.@system##.RKAUCMDS Parameter Library

rhilev.@system##.RKAUEXEC REXX Exec Library

rhilev.@system##.RKAULOGI ISPF Change Log

rhilev.@system##.RKAUSAMP Batch JCL Library

rhilev.@system##.RKAUTBLI ISPF Table Library

rhilev.@system##.RKAUTBLR REXX Table Library

rhilev.@system##.RKAUPRFI AF/TCI ISPF Profile Dataset

rhilev.@system##.RKOGARCH AF/OPERATOR Historical Log Archive GDG

rhilev.@system##.RKOGARCM AF/OPERATOR Message Log Archive GDG

rhilev.@system##.RKOGCKP AF/OPERATOR Checkpoint Dataset

rhilev.@system##.RKOGLH01-02 AF/OPERATOR Historical Logs

rhilev.@system##.RKOGLH01-06 AF/OPERATOR Message Logs



Choosing a ConfigurationThe configuration you choose will depend on your site's OS/390 environment, the maintenance strategy used to maintain the systems and program products within that environment, the number of systems within that environment, and the automation requirements for that environment. More specifically, the configuration you choose will depend on:

1. Whether you use a stand-alone or shared SMP/E environment to maintain AF/OPERATOR and the IRM. In a stand-alone SMP/E environment, the SMP/E maintained datasets are not physically or logically shared with another OS/390 system. In a shared SMP/E environment, the SMP/E maintained datasets are physically shared with another system by means of shared DASD or logically shared with another system by copying the datasets from one system to the other.

2. Whether you have multiple OS/390 systems.

3. Whether you wish to use multiple AF/OPERATOR address spaces.

4. Whether you share SMP/E environments logically or physically.

5. Whether you wish to share REXX Table data between systems.

6. AF/OPERATOR, OMEGACENTER Gateway, and IRM can not currently share a common SMP/E environment with other Candle Products.

To determine which IRM run-time dataset configuration best suits your needs, use the following chart as a decision tree. Start at the far left column and choose the option that is in use in your environment, or best describes your environment. Proceed to the next column to the right, and of the two choices available, choose the option that is in use in your environment. Continue this process across the chart. The value in the resulting far-right column will be the suggested dataset configuration that best suits your needs.

If you choose the standard configuration, follow the installation instructions as provided. If you choose the alternate configuration, in the installation steps that follow, use rhilev.@system## instead of rhilev for the dataset prefix in the KAU$ARUN, KAU$ARCF, and KAU$AXRF jobs.



Table 20. Run-Time Dataset Configuration Chart

SMP/EEnvironment

OS/390Systems

AF/OPERATORAddressSpaces

SMP/ESharingMethod

REXXTableData

SuggestDatasetConfig

Stand Alone Single Single n/a n/a Standard

Multiple n/a n/a Alternate1

Multiple Single n/a n/a Standard

Multiple n/a n/a Alternate1

Shared Multiple Single Physical

(DASD)

Shared Standard

Unique Alternate

Logical

(Copied)

Shared Standard

Unique Standard2

Multiple Physical

(DASD)

Shared Standard3

Unique Alternate

Logical

(Copied)

Shared Standard3

Unique Alternate

Notes:

1. If you wish, you may use the standard configuration for the IRM run-time libraries for the relative order 0 AF/OPERATOR address space. The alternate configuration must be used for relative order 1 through 9 AF/OPERATOR address spaces.

2. You may use the standard configuration in this situation assuming that you exclude the IRM run-time libraries from the copy process, otherwise you will need to use the alternate configuration.

3. A unique high level qualifier must be chosen for each set of run-time libraries for the relative order 1 through 9 AF/OPERATOR address spaces. For example, if ‘rhilev.AO’ is used as the high level qualifier for the relative order 0 AF/OPERATOR address spaces, ‘rhilev.AO.IMS’ might be used as the high level qualifier for relative order 1 AF/OPERATOR adress spaces.



Additional Requirements

In addition to the previous actions required to perform an alterate configuration, you must also rerun the following batch jobs as shown:

1. KAU$ARUN

Follow all the steps outlined for running KAU$ARUN but use rhilev.@system## for the value of the DSNPFX variable:

// SET DSNPFX=rhilev.@system##

2. KAU$CRUN

Follow all the steps outlined for running KAU$CRUN but use rhilev.@system## for the value of the DSNPFX variable:


3. KAU$ARCF

Follow all the steps outlined for running KAU$ARCF but use rhilev.@system## for the value of the DSNPFX variable:


4. KAU$GLGI

Follow all the steps outlined for "Allocating ISPF Log Archive GDG" member KAU$GLGI but change each occurrence of -HILEV- to rhilev.@system## instead of rhilev.

5. KAUAFLGI

Follow all the steps outlined for "Allocating AF/LGI Proclib Member - GDG Archive" member KAUAFLGI but use rhilev.@system## for the value of the DSNPFX variable:

// SET DSNPFX=rhilev.@&SYS.

6. KAUAFRE1

Follow all the steps outlined for "Allocating AF/LGI Proclib Member - Sysout Archive" member KAUAFRE1 but use rhilev.@system## for the value of the DSNPFX variable:




7. KAUAFOPR

Follow all the steps outlined for "Creating AF/OPR Proclib Member" member KAUAFOPR but use rhilev.@system## for the value of the RKAUPFX variable:

// SET RKAUPFX=rhilev.@&SYS.00

8. KAUAFTCI

Follow all the steps outlined for "Creating AF/TCI Proclib Member" member KAUAFTCI but use rhilev.@system## for the value of the RKAUPFX variable:


9. KAUAFRDR

Follow all the steps outlined for "Creating AF/RDR Proclib Member" member KAUAFRDR but use rhilev.@system## for the value of the RKAUPFX variable:


10. Creating Cataloged Procedures

Follow all the steps outlined for "Creating Cataloged Procedures" for each member listed in the table and use rhilev.@system## for the value of the USRPFX variable:

// SET USRPFX=rhilev.@system##

11. Creating Batch Interface JCL Members

Follow all the steps outlined for "Creating Batch Interface JCL Members" for each member listed in the table and use rhilev.@system## for the value of the USRPFX variable:


12. Creating REXX Table Maintenance Members

Follow all the steps outlined for "Creating REXX Table Maintenance Members" for each member listed in the table and use rhilev.@system## for the value of the USRPFX variable:




13. Creating REXX Table Batch Update Members

Follow all the steps outlined for "Creating REXX Table Batch Update Members" for each member listed in the table and use rhilev.@system## for the value of the USRPFX variable:


14. Creating Miscellaneous Batch Job Members

Follow all the steps outlined for "Creating Miscellaneous Batch Job Members" for each member listed in the table and use rhilev.@system## for the value of the USRPFX and DSNPFX variable:



15. KAU$AXRF

Follow all the steps outlined for "Allocating IMS/XRF Status File" member KAU$AXRF but use rhilev.@system## for the value of the DSNPFX variable:


16. KAUAFOVI

Follow all the steps outlined for "Creating AF/OVI Proclib Member" member KAUAFOVI but use rhilev.@system## for the value of the RKAUPFX variable:



AF/OPERATOR IRM Initialization


Overview In order for IRM to have complete control of the operating system and manage all of the resources defined to it, you must make the following changes to SYS1.PARMLIB and/or SYSn.IPLPARM datasets as shown in the following sections.

Note: You will need the assistance of a MVS Systems Programmer to make these changes.



IRM Initialization TypesThe following identifies the types of IRM initializations that are permitted:

n (AO) AUTOIndicates this is an automated mode IPL. An automated IPL will bring up all resources defined to the system.

n (CK) CHKPIndicates this is a checkpoint restart of AF/OPERATOR. A checkpoint restart is used to restart the Automation Applications where they left off; all check-pointed Automation Application control information will be restored and the applications will respect any previously entered dynamic control information. The checkpoint option, CHKP, is used to establish a system in the exact configuration it was in before AF/OPERATOR or the system was brought down or failed. All dynamic control information is reestablished from check-pointed AF/OPERATOR system variables and the system is placed in a comparable state to that which it was in the last time the Automation Applications were active.

n (MN) MANUALIndicates this is a maintenance mode IPL. During a manual IPL, the IRM will bring up only those resources that have been defined with the AUTO keyword. The manual IPL option is used to bring up a system in maintenance mode; only those tasks, messages or other controlled resources that are necessary are activated. For example, in the case of started tasks, LLA, VLF and JES, could be defined as the only tasks that will be activated by the Started Task Manager during a maintenance mode IPL. This allows you to perform whatever system maintenance is necessary before an entire system is established. The intent of the AUTO keyword is to allow you to specifically designate those resources, controlled by automation, which are necessary for a skeleton maintenance system. Any resource defined with the AUTO keyword will be automatically started regardless of the application-processing mode.



System Software Load ReviewThis section provides a review of the system software load process. Once the system hardware is ready, you use the system console to load the system software. Load the system as follows, using the following fields on the system control (SYSCTL) frame. The example at the end of this section uses the IBM 3090 for illustration):

1. T = TARGET CPSpecifies the target processor for initialization.

2. A = INITIALIZE SYSTEM CONTROL PROGRAM, A1Specifies the device number that contains the system residence volume (IPL volume).

3. A = INITIALIZE SYSTEM CONTROL PROGRAM, A2Specifies the LOAD parameter.

The following shows the format of the LOAD parameter:

The two characters (characters 5 and 6 in the above example) specify the suffix of the LOADxx parmlib member that the system is to use. The LOADxx member contains information about the name of the IODF data set, the master catalog to use, and which IEASYSxx members of SYS1.PARMLIB to use and, in turn, which COMMNDxx members of SYS1.PARMLIB to use.

1 4 5 6 7 8IODF DASD LOADxx PROMPT FEAT ALT NUCx

IODF LOADxx prompt nucleusdevice suffix feature suffixnumber



Updating SYSn.IPLPARM/SYS1.PARMLIBCreate three separate LOADxx members named LOADAO, LOADCK, LOADMN in either of the datasets discussed in the previous section, depending on your site's requirements. Within each newly created LOADxx member add or modify a SYSPARM statement as follows:

n LOADAO statement:

*---+----1----+----2----+----3----+----4----+----5----+----6----+---- . . .SYSPARM (00,AO,L). . .

n LOADCK statement:

*---+----1----+----2----+----3----+----4----+----5----+----6----+---- . . .SYSPARM (00,CK,L). . .

n LOADMN statement:

*---+----1----+----2----+----3----+----4----+----5----+----6----+---- . . .SYSPARM (00,MN,L). . .

Creating IEASYSxx members

From the thilev.TKAUSAMP dataset use the supplied KAUSYSAO, KAUSYSCK, KAUSYSMN members as models and create three separate IEASYSxx members named IEASYSAO, IEASYSCK, IEASYSMN in SYS1.PARMLIB.

Creating COMMNDxx members

From the thilev.TKAUSAMP dataset use the supplied KAUCMDAO, KAUCMDCK, KAUCMDMN members as models and create three separate COMMNDxx members named COMMNDAO, COMMNDCK, COMMNDMN in SYS1.PARMLIB.



Modifying IEFSSNxx members

Locate the appropriate IEFSSNxx member that is used to start the Job Entry Subsystem and ensure that JES start statement contains a START(NO) parameter. This ensures that IRM will handle the starting of the JES at the appropriate time.




OverviewThe following sections describe the start-up procedure members that need to be created for the optional AF/OPERATOR and IRM started tasks. Each of the members created in the following sections should be placed in the SYS1.PROCLIB dataset or in an appropriate user proclib dataset.



Creating AF/OVI Proclib MemberThe KAUAFOVI member is a sample procedure for the Programmerless Open VTAM Interface started task.

Copy the KAUAFOVI member from the thilev.TKAUSAMP dataset to the SYS1.PROCLIB dataset, choosing a new member name for the started task that is appropriate for your site, for example, AFOVI. Edit the copy of KAUAFOVI in SYS1.PROCLIB and perform the following tasks:



3. Fill in the JCL SET statements as follows:

//*//SET TKAUPFX=thilev//SET RKAUPFX=rhilev//SET TKANPFX=thilev//SET RKANPFX=rhilev//SET RKANSYS=rhilev.@&SYS.00//*







RKANSYS Is the support datasets high level qualifier, rhilev.@system##.



Creating AF/OVI IRM SettingsTo prevent the logon's managed by IRM, such as CICS, from timing out and being dropped by AF/OVI, the following changes need to be made to the AF/OVI Recording manager after you have completed the installation of AF/OVI started task.

Issue a start of the AF/OVI started task that you either defined during the AF/OPERATOR CICAT installation procedures or as part of this optional manual customization procedure. Once it has become active, logon to the AF/OVI recording manager by entering the following logon command from any VTAM terminal.

LOGON APPLID(applid)

This logon APPLID must match the recording manager APPLID statement within the rhilev.@system##..RKANPAR(KOGPSTRT) member.

From the POVI Session Selection panel, perform the following:

Cycle the AF/OVI started task to pick up your changes.

Step Action

1 Tab to the ADMIN field and press ENTER.

2 Select Option 4 - Timeout and press ENTER.

3 Select Option 2 - OMEGACENTER Gateway Timeout and press ENTER.

4 In the Physical Session Read Timeout field enter a value of 0 in the seconds field.

5 Press ENTER to save your changes.



Creating AF/USR Proclib Member - GDG ArchiveThe KAUAFUSR member is a sample procedure for the AF/USR started task. The AF/USR started task is used by the AF/OPERATOR user DASD message log dataset archive process to copy a user DASD message log dataset to the +1 GDG member when the log dataset is closed.

Note: If you will be using a sysout-based archive process for the user DASD message log datasets, instead of the GDG-based archive process, you may skip this step.

Copy the KAUAFUSR member from the thilev.TKAUSAMP dataset to the SYS1.PROCLIB dataset, choosing a new member name for the started task that is appropriate for your site, for example, AFUSR. Edit the copy of KAUAFUSR in SYS1.PROCLIB and perform the following tasks:










Creating AF/USR Proclib Member - Sysout ArchiveThe KAUAFUS1 member is a sample procedure for the AF/USR started task. The AF/USR started task is used by the AF/OPERATOR user DASD message log dataset archive process to copy a user DASD message log dataset to sysout when the dataset is closed.

Note: If you will be using the GDG-based archive process for the user DASD message log datasets, instead of a sysout-based archive process, you may skip this step.

Copy the KAUAFUS1 member from the thilev.TKAUSAMP dataset to the SYS1.PROCLIB dataset, choosing a new member name for the started task that is appropriate for your site, for example, AFUSR. Edit the copy of KAUAFUS1 in SYS1.PROCLIB and perform the following tasks:







REXX Exec Template

REXX Exec TemplateCopy the member KAUAEXEC from TKAUSAMP to RKAUEXEC to a member name conforming to your site-specific standard naming convention. This REXX exec should be used as a template for any user written REXX exec's. Make any alterations to the header portion to conform to your site's standards for REXX execs.

This REXX exec contains a set of IRM specific error routines to trap on the most common REXX errors and to aid in debugging by providing more meaningful error messages.

REXX Exec Template


Customer Support 145

Customer Support

IntroductionCandle Corporation offers a comprehensive maintenance and support plan to ensure you realize the greatest value possible from your Candle software investments. We have more than 200 technicians worldwide, committed to providing you with prompt resolutions to your support requests.

Customer Support hours of operation are from 5:30 A.M. – 5:00 P.M., Pacific Time. In the event of an after-hours or weekend emergency, Candle's computerized call management system ensures that a technician will return your call within one hour. For customers located outside of North America, after-hours and weekend support is provided by Candle Customer Support locations in the United States.

Electronic supportCandle provides information and support services through

n Candle's home page at www.candle.com. You can use the Candle Worldwide Web Site to– open problem records– access maintenance information – order products or maintenance– access IBM compatibility information– download fix packs for distributed products– read news and alerts– scan a list of scheduled Candle education classes

C


n Candle Electronic Customer Support (CECS), an electronic customer support facility. You can access this facility using the IBM Global Network. You can use CECS to:– open problem records– search our database for solutions to known problems– look for answers to commonly asked questions– read news and alerts– scan a list of scheduled Candle education classes

Both CECS and the Candle Worldwide Web Site are available 24 hours a day, 7 days per week.

Telephone supportOur support network consists of product specialists who work with you to solve your problem.

Candle uses an on-line problem management system to log and track all support requests. Your support request is immediately routed to the appropriate technical resource.

When you call to report a problem, please have the following information:

n your Candle personal ID (PID) numbern the release level of the Candle product n the release level of IBM or other vendor software n identifying information and dates of recently applied maintenance to your

Candle product or IBM productn a detailed description of the problem (including the error message) and

the events preceding the problemn a description of any unusual events that occurred before the problem

Customer support locations and numbersTo contact a Customer Support representative, refer to the following list. While these phone numbers were accurate at the time this document was published, the current numbers can be found on the Candle Web site, www.candle.com, under Customer Support.

http://www.candle.com

Customer Support 147

Table 21. Customer Support Phone Numbers

Office Telephone FAX

North America (800) 328-1811 (310) 535-3636

(310) 727-4204

Europe

Belgium/Luxembourg +32 (0) 3 270 95 60 +32 (0) 3 270 95 41

France +33 (0) 1 53 61 60 60 +33 (0) 1 53 61 06 16

Germany/Switzerland/Austria

+49 (0) 89 54 554 333 +49 (0) 89 54 554 170

Italy – Freephone 800 780992

Netherlands +31 (0) 30 600 35 50 +31 (0) 30 600 35 10

Scandinavia +46 (0)8 444 5940 +46 (0)8 623 1855

United Kingdom +44 (0)161 437 5224 +44 (0)161 437 5225

(Southern Europe, Middle East and South Africa Agents call United Kingdom)

Asia Pacific – English Hub +61 2 9954 1818

Australia +61 2 8912 9898

Hong Kong 800 908 457

India +61 2 8912 9898

Indonesia 0018 03061 2061

Malaysia 1800 803 459

New Zealand 0800 449 596

Philippines 1800 1612 0096

Singapore 800 616 2075

Thailand 0018 00612 1045

Asia Pacific – Japanese Hub +81 3 3595 7150 +81 3 3595 7110

Asia Pacific – Korean Hub +82 2 552 8744 +82 2 552 8746

Asia Pacific – Mandarin Hub +88 62 2739 3223 +88 62 2378 5993

Asia Pacific – e-mail address: [email protected]


When your local support office is unavailable, you can contact Candle's North America support center. If USADirect® service is available in your country, use the 800 telephone number. If USADirect® service is not available, ask your international operator for assistance in calling Candle's local (310) number.

Incident documentationYou may be asked to send incident documentation to the Candle Customer Support Center. On the outside of all packages you send, please write the incident number given to you by the Customer Support representative.

Send tapes containing the incident information to the following address, unless directed otherwise by your Customer Support representative:

Candle Customer SupportCandle Support Center, Incident number201 North Douglas StreetEl Segundo, California 90245

Send all other relevant documentation, such as diskettes or paper documentation, to the address provided by your Customer Support representative.

Ensuring your satisfaction with customer supportCandle Customer Support is committed to achieving high customer satisfaction ratings in all areas. These include

n connecting you to a support representative promptlyn providing you with the appropriate fixesn answering support questionsn filling your shipping ordersn supplying documentation

If you have a concern that has not been resolved to your satisfaction, you can open a complaint ticket. All tickets are logged and tracked to ensure responsiveness and closure. Using the ticket information, a manager will contact you promptly to resolve your problem.

Index 149

Index

AAccessing the ISPF Interface 81Accessing the Load Libraries 79AF/OPERATOR

Version 240 Special Requirement 29AF/OPERATOR Environment

configuring 91creating AF/OPERATOR Parmlib

members 92creating IRM Parmlib members 94custom caldendar parameters 97master caldendar parameters 94started task manager parameters 107system variable delete parameters 101

AF/OPERATOR IRM Initialization 133initialization types 134updating

SYSn.IPLPARM/SYS1.PARMLIB 136Allocating AF/LGI Proclib Member - GDG

Archive 54Allocating AF/LGI Proclib Member - Sysout

Archive 55Allocating AF/MSG Proclib Member - Sysout

Archive 48Allocating AF/OPERATOR Checkpoint

Dataset 44Allocating AF/OPERATOR Retain Log MCF

Resource Definition 90Allocating AF/OPERATOR SLF

Journals 119Allocating AF/OPERATOR User Message

Logs 125Allocating AF/RET Proclib Member - GDG

Archive 51Allocating AF/RET Proclib Member - Sysout

Archive 52Allocating IMS/XRF Status File 118Allocating ISPF Log Archive GDG 54

Allocating Message Log Datasets 46Allocating Optional Datasets 116Allocating POVI NAM Database

Dataset 122Allocating POVI Parameter Dataset 121Allocating POVI Table Database

Dataset 123Allocating POVI Viewlog Database

Dataset 124Allocating Retain Log Archive GDG 51Allocating Retain Log Datasets 50Allocating REXX Alternate Library 43Allocating Support Datasets 42Allocating User Message Log Archive

GDG 126Application Manager Definitions

updating company address1 variable 87updating company address2 variable 88updating company name variable 86updating help dataset variable 85

Authorized Program List 59

BBatch JCL Members

creating 72creating miscellaneous batch job

members 77creating REXX table batch update

members 75creating REXX table maintenance

members 73Batch Status File 42

CCandle Electronic Customer Support

(CECS) 146Candle home page 145


Candle Internet site 145Candle Tape Products 32Candle Worldwide Web site 145Cataloged Procedures

creating 71Change Logs

allocating AF/LGI Proclib member GDG archive 54

allocating AF/LGI Proclib member sysout archive 55

allocating ISPF log archive GDG 54ISPF 53

CICATusing 27

CICAT Customization 31Company Address1 Variable 87Company Address2 Variable 88Company Name Variable 86Configuring AF/OPERATOR

Environment 91Configuring AF/OPERATOR Message

Logs 45Configuring AF/OPERATOR Retain Logs 49Configuring the IMS/APPC Interface 116Converting

Formatting REXX Tables 113Creating AF/OPERATOR Parmlib

Members 92Creating AF/OPR Proclib Member 64Creating AF/OVI IRM Settings 140Creating AF/OVI Proclib Member 139Creating AF/RDR Proclib Member 68Creating AF/TCI Proclib Member 66Creating AF/USR Proclib Member - GDG

Archive 141Creating AF/USR Proclib Member - Sysout

Archive 142Creating Batch Interface JCL Members 72Creating Batch JCL Members 70Creating Cataloged Procedures 71Creating DEALLOC Proclib Member 69Creating IRM Parmlib Members 94Creating Miscellaneous Batch Job

Members 77Creating Proclib Members 63, 138Creating REXX Table Batch Updates

Members 75Creating REXX Table Maintenance

Members 73Custom Calendar Parameters 97customer support

electronic support 145Internet 145locations 146numbers 146telephone support 146

DDASD

message log datasets 125Dataset Configuration

standard configuration 36Defining

Coupling Facility List structure 109

EEstimating

XES List Structure Size 110

HHelp Dataset Variable 85home page

Candle 145

IIBM

software requirements 28Installation Control Specifications 62Installing ISPF Interface 78Installing ISPF interface 78Installing product tape 34Internet site

Candle 145Invoking the ISPF Interface 81IRM

Index 151

AF/OPERATOR initialization 133Choosing a Configuration 128Converting to V500 113creating IRM Parmlib members 94hardware requirements 30Required Customization 35

IRM Initialization Types 134IRM Optional Customization 115ISPF Change Log 53ISPF Interface

accessing load libraries 79accessing the ISPF interface 81installing 78invoking 82

LLink Library List 58

MMaster Caldendar Parameters

parameters syntax 94Master Calendar Parameters 94Message Processing Facility List 61Migration Considerations 26

OS/390 26

OOptional Datasets

allocating 116allocating AF/OPERATOR SLF

journals 119allocating AF/OPERATOR user message

logs 125allocating IMS/XRF status file 118allocating POVI NAM database

dataset 122allocating POVI parameter dataset 121allocating POVI table database

dataset 123allocating POVI viewlog database

dataset 124Installation Steps 116

system software load review 135user message log archive GDG 126

Optional Datasets allocating 116

PParmlib Member

authorized program list 59installation control specifications 62link library list 58message processing facility 61TSO/E comands and programs 60

Populating Run-time Libraries 41Proclib Member

creating 62, 63creating AF/OPR 64creating AF/RDR 68creating AF/TCI 66creating DEALLOC 69

Proclib Memberscreating 138creating AF/OVI IRM settings 140creating AF/OVI Proclib member 139creating AF/USR Proclib member GDG

archive 141creating AF/USR Proclib member sysout

archive 142Product Tapes

corrective service tapes 33maintenance tape 33SMP/E format product tape 32tape contents 32

RRetain Logs

allocating AF/OPERATOR retain log MCF resource definition 90

allocating AF/RET Proclib member GDG archive 51

allocating AF/RET Proclib member sysout archive 52

allocating retain log archive GDG 51allocating retain log datasets 50


configuring 49REXX Exec Template 143Run-time Libraries

allocating 40populating 41

SSoftware Requirements

Candle 29Software versions supported

IRM 29Special Characters

@JOBEDIT() 68@JOBSMIT() 68@RCFREAD() 42@RCFWRIT() 42

Started Task Managerparameter syntax 107

Started Task Manager Parameters 107Support Datasets

allocating 41Supported screen sizes 30SYSPLEX Configuration 109SYSPLEX Exploitation 22System Software Load Review 135System Variable Delete Parameters 101

TTSO/E Commands and Programs 60

UUpdating Application Manager

Definitions 84Updating Parmlib Members 57Updating

SYSn.IPLPARM/SYS1.PARMLIB 136

creating COMMNDxx members 136creating IEASYSxx members 136creating IEFSSNxx members 137

Using the CICAT 27

VVersion Requirements 28

WWorldwide Web site

Candle 145

Documents

Configuration and Customization Guide - IBM Supportpublib.boulder.ibm.com/tividd/td/ITIntegRM/GC32-9221-00/...AUTOMATED FACILITIES, Availability Managers, Candle Business Partner Logo,