af/operator user interface guide v340

User Interface GuideAF/OPERATOR®

Version 340

GC32-9141-00

September 2002

Candle Corporation201 North Douglas Street

El Segundo, California 90245-9796

2 AF/OPERATOR User Interface Guide V340

Registered trademarks and service marks of Candle Corporation: AF/OPERATOR, AF/PERFORMER, AF/REMOTE, Availability Command Center, Candle, Candle Command Center, Candle Direct logo, Candle Electronic Customer Support, Candle logo, Candle Management Server, Candle Management Workstation, CandleNet Portal, Candle Technologies, CL/CONFERENCE, CL/SUPERSESSION, CommandWatch, CandleNet Command Center, CT, CT/Data Server, CT/DS, DELTAMON, eBA, eBA*ServiceMonitor, eBA*ServiceNetwork, eBusiness Assurance, eBusiness Institute, ETEWatch, IntelliWatch, IntelliWatch Pinnacle, MQSecure, MQView, OMEGACENTER, OMEGAMON, OMEGAMON/e, OMEGAMON II, OMEGAMON Monitoring Agent, OMEGAVIEW, OMEGAVIEW II, PQEdit, Solutions for Networked Applications, Solutions for Networked Businesses, and Transplex.Trademarks and service marks of Candle Corporation: Alert Adapter, Alert Adapter Plus, Alert Emitter, AMS, Amsys, AutoBridge, AUTOMATED FACILITIES, Availability Management Systems, Candle Alert, Candle Business Partner Logo, Candle Command Center/SentinelManager, Candle CommandPro, Candle CIRCUIT, Candle eDelivery, CandleLight, CandleNet, CandleNet 2000, CandleNet eBP, CandleNet eBP Access, CandleNet eBP Administrator, CandleNet eBP Broker Access, CandleNet eBP Configuration, CandleNet eBP Connector, CandleNet eBP File Transfer, CandleNet eBP Host Connect, CandleNet eBP Object Access, CandleNet eBP Object Browser, CandleNet eBP Secure Access, CandleNet eBP Service Directory, CandleNet eBP Universal Connector, CandleNet eBP Workflow Access, CandleNet eBusiness Assurance, CandleNet eBusiness Exchange, CandleNet eBusiness Platform, CandleNet eBusiness Platform Administrator, CandleNet eBusiness Platform Connector, CandleNet eBusiness Platform Connectors, CandleNet eBusiness Platform Powered by Roma Technology, CandleNet eBusiness Platform Service Directory, CCC, CCP, CEBA, CECS, CICAT, CL/ENGINE, CL/GATEWAY, CL/TECHNOLOGY, CMS, CMW, Command & Control, Connect-Notes, 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 Logo, !DB/DASD, !DB/EXPLAIN, !DB/MIGRATOR, !DB/QUICKCHANGE, !DB/QUICKCOMPARE, !DB/SMU, !DB/Tools, !DB/WORKBENCH, Design Network, DEXAN, e2e, eBAA, eBAAuditor, eBAN, eBANetwork, eBAAPractice, eBP, eBusiness Assurance Network, eBusiness at the speed of light, eBusiness at the speed of light logo, eBusiness Exchange, eBusiness Institute, eBX, End-to-End, ENTERPRISE, Enterprise Candle Command Center, Enterprise Candle Management Workstation, Enterprise Reporter Plus, EPILOG, ER+, ERPNet, ESRA, ETEWatch Customizer, HostBridge, InterFlow, Candle InterFlow, Lava Console, MessageMate, Messaging Mastered, Millennium Management Blueprint, MMNA, MQADMIN, MQEdit, MQEXPERT, MQMON, NBX, NetGlue, NetGlue Extra, NetMirror, NetScheduler, OMA, OMC Gateway, OMC Status Manager, OMEGACENTER Bridge, OMEGACENTER Gateway, OMEGACENTER Status Manager, OMEGAMON Management Center, OSM, PC COMPANION, Performance Pac, PowerQ, PQConfiguration, PQScope, Response Time Network, Roma, Roma Application Manager, Roma Broker, Roma BSP, Roma Connector, Roma Developer, Roma FS/A, Roma FS/Access, RomaNet, Roma Network, Roma Object Access, Roma Secure, Roma WF/Access, Roma Workflow Access, RTA, RTN, SentinelManager, Somerset, Somerset Systems, Status Monitor, The Millennium Alliance, The Millennium Alliance logo, The Millennium Management Network Alliance, TMA2000, Tracer, Unified Directory Services, Volcano and ZCopy.Trademarks and registered trademarks of other companies: AIX, DB2, MQSeries and WebSphere 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.

Copyright © August 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

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Adobe Portable Document Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

What’s New in AF/OPERATOR Version 340 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Chapter 1. Introduction to AF/OPERATOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15What AF/OPERATOR Does. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16How Resource Management Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18How Console Management Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21Resource Control Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23What To Do Next . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

Chapter 2. Configuring AF/OPERATOR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27AF/OPERATOR Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28Set Up System Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30Define Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33Add and Authorize Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34Define Notification Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38Set Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40Optionally, Create Sysplex Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44Optionally, Create TCP/IP Communications Definitions . . . . . . . . . . . . . . . . . . . . . . . .45

Chapter 3. Resource Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Overview of Resource Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49Set up Calendars. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52Set Up Calendars—Task 1: Plan and Define the Calendar . . . . . . . . . . . . . . . . . . . . . . .53Set Up Calendars—Task 2: Specify Calendar Days . . . . . . . . . . . . . . . . . . . . . . . . . . . .55Procedure to Specify Calendar Days . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57Defining Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61Define Resources—Task 1: Define the Resource Classes . . . . . . . . . . . . . . . . . . . . . . . .62Define Resources—Task 2: Define the Individual Resources . . . . . . . . . . . . . . . . . . . . .65Specify Activities and Activity Qualifiers for a Resource . . . . . . . . . . . . . . . . . . . . . . . . .72Specify Activity Messages for a Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76Specify Predecessors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79Set up Resource Recovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82Set up Schedules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85Set Up Schedules—Task 1: Define schedules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86Set Up Schedules—Task 2: Specify Daytype Order . . . . . . . . . . . . . . . . . . . . . . . . . . . .90Example: Defining a Calendar for Use by the RSM . . . . . . . . . . . . . . . . . . . . . . . . . . . .94

Contents


Example: Creating RSM-Controlled Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99

Chapter 4. Resource Control Facility Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105About RCF Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107ACTIVATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109CHECK. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110DISABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112INACTIVATE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113INITIATE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114LIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117MONITOR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119NOMONITOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120PREDECESSOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121PURGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123RECOVERY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124REFRESH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126SCHEDULE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127SET. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128SHOW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .130START . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136STATUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .138STOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139SUCCESSOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .141TERMINATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .143TRAPGROUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .144

Chapter 5. Trap Group Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147About Traps -- Before you Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .148Working with Trap Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .150Adding Traps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .154Example: Defining a Spool Full WTO Trap to Flag Excessive Job Output . . . . . . . . . .158Example:Using a Trap to Start an Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163Example: Defining a Trap to Intercept Unauthorized Printer Commands . . . . . . . . . . .166

Chapter 6. Using the AF/OPERATOR Sysplex Console to Access Members of a Sysplex .169What is the Sysplex Console? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .170Set-up Requirements to Use Sysplex Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .171Examples of the Use of Sysplex Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173Issuing Commands—Some Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177

Chapter 7. Starting, Stopping, and Overseeing AF/OPERATOR. . . . . . . . . . . . . . . . . . . . 181Starting the AF/OPERATOR Resource State Manager . . . . . . . . . . . . . . . . . . . . . . . . .182Refreshing the Resource State Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .186Stopping Resource State Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .187

Contents 5

Resource Manager Scheduling Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188Managing Always Active Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .189Overseeing AF/OPERATOR and the Resource State Manager . . . . . . . . . . . . . . . . . . .190RSM Initialization, Termination, and Refresh Processes . . . . . . . . . . . . . . . . . . . . . . . .194Differences betweeen Cold and Warm Starts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .199

Chapter 8. Testing and Debugging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201Setting up a Test Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .202Simulating a Console with OG*TSO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .203

Appendix A. Writing Your Own Resource Management Routines. . . . . . . . . . . . . . . . . . . . .205Checking the State of a Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .206Recovery Failure Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .211Resource Manager Application Programming Interface . . . . . . . . . . . . . . . . . . . . . . . .212

Appendix B. Guide to Candle Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225Base Maintenance Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .226Enhanced Support Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .230Customer Support Contact Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .231

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

Preface 7

Preface

About This BookThis AF/OPERATOR® User Interface Guide gives instructions for setting up and using AF/OPERATOR to automate your data center. This document:

n explains how AF/OPERATOR works and what it does

n tells how to set up AF/OPERATOR to manage:

– data center resources

– console messages and commands

n gives guidelines for running AF/OPERATOR

n provides suggestions for testing and debugging your data center automation procedures

For information on customizing AF/OPERATOR, see the AF/OPERATOR Configuration and Customization Guide.

What to read nextThis table shows where you can find basic information to help you get started with AF/OPERATOR.

If... Turn to...

you used AF/OPERATOR Version 320 “What’s New in AF/OPERATOR Version 340” on page 11

you’ve never used AF/OPERATOR before “Introduction to AF/OPERATOR” on page 15

P

8 AF/OPERATOR User Interface Guide Version 340

Documentation set information

The documentation listed in the following bulleted list is available for AF/OPERATOR. To order additional product manuals, contact your Candle Support Services representative.

n AF/OPERATOR Configuration and Customization Guide

n AF/OPERATOR User’s Guide

n AF/OPERATOR Command Reference Manual

n Candle Product Messages Manual

n AF/OPERATOR User Interface Guide

n AF/OPERATOR OMEGAMON II for SMS Data Interface

n AF/OPERATOR Message Manager

n AF/OPERATOR Started Task Manager

n AF/OPERATOR: Using the Subsystem Logging Facility

n Connecting AF/OPERATOR and AF/REMOTE Using TCP/IP

Where to look for more informationFor more information related to this product, please see the

n technical documentation CD-ROM that came with your product

n technical documentation information available on the Candle Web site at www.candle.com

n online help provided with this product

Ordering additional documentationTo order additional product manuals, contact your Candle Customer Support representative.

We would like to hear from youCandle 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 the Candle Information Development department.

You can also send email to [email protected]. Please include "AF/OPERATOR User Interface Guide Version 340" in the subject line.

Preface 9

Adobe Portable Document Format


Printing this bookCandle supplies documentation in the Adobe Portable Document Format (PDF). The Adobe Acrobat Reader will print PDF documents with the fonts, formatting, and graphics in the original document. To print a Candle document, do the following:

1. Specify the print options for your system. From the Acrobat Reader Menu bar, select File > Page Setup… and make your selections. A setting of 300 dpi is highly recommended as is duplex printing if your printer supports this option.

2. To start printing, select File > Print... on the Acrobat Reader Menu bar.

3. On the Print pop-up, select one of the Print Range options forn Alln Current pagen Pages from: [ ] to: [ ]

4. (Optional). Select the Shrink to Fit option if you need to fit oversize pages to the paper size currently loaded on your printer.

Printing problems?The print quality of your output is ultimately determined by your printer. Sometimes printing problems can occur. If you experience printing problems, potential areas to check are:n settings for your printer and printer driver. (The dpi settings for both your driver and

printer should be the same. A setting of 300 dpi is recommended.)n the printer driver you are using. (You may need a different printer driver or the Universal

Printer driver from Adobe. This free printer driver is available at www.adobe.com.)n the halftone/graphics color adjustment for printing color on black and white printers (check

the printer properties under Start > Settings > Printer). For more information, see the online help for the Acrobat Reader.

n the amount of available memory in your printer. (Insufficient memory can cause 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.

Contacting AdobeIf additional information is needed about Adobe Acrobat Reader or printing problems, see the Readme.pdf file that ships with Adobe Acrobat Reader or contact Adobe at www.adobe.com.

http://www.adobe.com



What’s New in AF/OPERATOR Version 340 11

What’s New in AF/OPERATORVersion 340

This section provides a description of the new features that have been incorporated into AF/OPERATOR Version 340.

TCP/IP connectivity enhancementsTCP/IP communications have been simplified by permitting you to optionally remove the AF packet header when communicating between AF/OPERATOR and systems or applications that are unable to comply with the Candle AF packet header protocol. You accomplish this by means of a new option on the LINK DEFINE and COMM START commands. In addition, new SEND and RECEIVE datatypes have been added to the COMSDRCV REXX function. You must use the SEND and RECEIVE datatypes when you want to transfer data over a link having the AF packet header turned off.

New keywords have been added to COMM START and COMM STOP commands. The CONNECT_EXEC keyword on the COMM START command identifies a named exec that runs whenever a connection to the server is established and is mandatory when you have specified AFPACKET(OFF). The CID keyword on the COMM STOP command identifies a particular connection to a server to be stopped.

A new COMADMIN REXX function provides GIVE and TAKE options that permit passing ownership of a connection from one match to another.

Passing larger amounts of data on a TCP/IP match

You can now pass more data to an individual match. AF/OPERATOR will permit passing a larger amount of parameter data to a REXX procedure. In addition, it will provide the capability to create a conversation between matches so that multiple 32K packets can be transferred. This is accomplished by permitting the DATARPLY datatype to code the replylength keyword on the COMSDRCV REXX function.

Automated peer-to-peer link managementBy predefining link attributes, it is now possible to automatically establish connections at AF/OPERATOR startup. The following product changes support this function:

n The optional RECOVERY keyword on the LINK DEFINE command indicates that an INACTIVE link having a desired state of ACTIVE is to be automatically started when the specified server becomes available.

W


n The new ACTIVATE keyword on the LINK DEFINE command indicates that a LINK START is to be automatically attempted for a particular linkid, assuming a successful link definition.

n The new SCOPE keyword on the LINK START command specifies those links that are to be selected for LINK START processing according to their activation state.

n Two new startup parameters, HOSTNAME and LINKDEFS are added. HOSTNAME(xxxxxxxx) overrides the default name of the trusted hostnames member in RKANPAR. The LINKDEFS(xxxxxxxx) parameter overrides the default name of the link definitions member in RKANPAR. During product startup, when TIMEOUT(nnn) is specified on the LINKDEFS keyword, it specifies the amount of time to wait for the LINK START command issued immediately after processing the LINKDEFS member to complete before startup is allowed to continue.

Changes to the OPER command when RESP is specifiedThe OPER command issues an MVS or subsystem command. On this command, the RESP parameter specifies that a set of line variables will receive the response text resulting from the command. Additional parameters have been added to the OPER command when specified with the RESP parameter:

n TIMEOUT(pp,ss): The new ss value specifies the number of seconds (from 1 through 3600) that AF/OPERATOR is to wait for each response message line from a multi-line write to operator before assuming the response is complete.

n MAXLINES(nnnn): This new parameter specifies that a response is to be deemed complete when the specified number of lines is received.

n ENDMSG(prefix): This new parameter specifies that the response is to be deemed complete when the specified prefix is encountered in one of the response lines.

The ss value is also added to the OPERRESP AF/OPERATOR startup parameter.

In addition, the CMDSDRCV function has been modified such that when it causes an OPER command with RESP specified to be executed on a remote system, it also causes an AOCASE variable to be built when the reply from the remote system is received.

Additional modificationsn New global variables have been added for COM matches.

n A DUB_AS_PROCESS command, having the same function as the AF/OPERATOR startup parameter of the same name, has been provided.

Storage Constraint ReliefThe amount of storage constraint relief realized will vary depending on AF/OPERATOR startup parameters and will be equal to (MAXMAT - MAXRUN) * 480 bytes.

What’s New in AF/OPERATOR Version 340 13

Online documentationWith Version 340, Candle Corporation has moved AF/OPERATOR manuals from IBM BookMaster to Adobe FrameMaker. This move was made to better enable us to address our customers’ needs by providing tools that enhance productivity.

One of the results of the move is that it is no longer possible to create BookManager versions of the AF/OPERATOR manuals. However, the manuals remain available online in the Adobe PDF version on CD-ROM and are also available on the Candle Corporation website at www.Candle.com.

The documentation CD being provided with this release has robust and easy-to-use search capabilities. You can search for information in multiple volumes, multiple versions, and across products. The CD also provides easy setup of search indexes with a single click of the mouse.

If you want to order printed copies of the documentation, please contact your Candle Support Services representative.

Enhancements to product documentationn Additional documentation about obtaining SMF data has been added to the

AF/OPERATOR User’s Guide.

n Additional documentation about using the Probe Directive, Probe Input, and Misc. Parms fields has been added to the OMEGACENTER Status Manager User’s Guide.

Introduction to AF/OPERATOR 15

Introduction to AF/OPERATOR

IntroductionAF/OPERATOR is Candle’s data center automation product. You can set it up to perform a variety of automated actions to keep your data center running smoothly and efficiently.

This chapter provides a basic orientation to AF/OPERATOR. It includes the following information:

n definitions of some key terms

n a description of product components

n a procedure sequence for setting up and using the product

Chapter ContentsWhat AF/OPERATOR Does . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16How Resource Management Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18How Console Management Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Resource Control Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23What To Do Next . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

1

What AF/OPERATOR Does



IntroductionAF/OPERATOR performs two basic types of automated actions:

n Resource management

Automated startup and shutdown, governed by your calendars and schedules, for all resources you define as AF/OPERATOR-controlled.

n Trap group management

MVS trap group management, console message- and command-handling, automated according to the rules of your choice.

Effective data center management involves the integration of resource management and trap group management.

Resource managementYou can set up AF/OPERATOR to control all types of data center resources, including:

n started tasks

n batch jobs

n initiators

n printers

n tape drives

n DASD volumes

n databases

n files and datasets

AF/OPERATOR can start and stop each resource at scheduled times and in response to specified events.

To manage some kinds of resources (such as started tasks and batch jobs), you need not write any code. To manage other kinds of resources (such as files and datasets), you will need to write REXX execs to supplement AF/OPERATOR’s resource management setup.



Trap group managementAF/OPERATOR monitors the operator consoles in your data center. It reads and can intercept every WTO and WTOR before MVS displays it at the console and every operator command before MVS takes the requested action.

You can set up AF/OPERATOR to:

n suppress screen display of routine messages

n emphasize messages by highlighting or freezing them on the screen

n reword or reroute messages

n respond to WTORs

n issue operator commands

n suppress or modify commands

How Resource Management Works



BasicsA resource is anything that can be started and stopped by console commands (MVS, VTAM, or JES) or by REXX code. The resource definitions you set up through the AF/OPERATOR user interface tell AF/OPERATOR which resources to manage and how to manage them.

For AF/OPERATOR, a resource can be in one of two states active (started) or inactive (stopped). process description AF/OPERATOR manages resources by starting and stopping them according to your calendars, schedules, and other specifications. At the scheduled time or in response to a specified system event, AF/OPERATOR initiates an activity (an attempt to start or stop a resource) by executing the specified process (usually a console command).

Some resources should not be started unless prerequisite resources are already active. Such a prerequisite resource is called a predecessor of the resource you are defining. A predecessor at startup can also be a successor at shutdown, if it must not be stopped until after the resource you are defining is stopped. (For example, in most data centers VTAM must be started before CICS and must not be stopped until after CICS is stopped. Therefore, VTAM is a predecessor to CICS at startup and a successor to CICS at shutdown.)

If a resource abends, AF/OPERATOR tries to restart it according to your specifications. This attempt to restart the resource is called recovery. If recovery fails, AF/OPERATOR begins notification of data center personnel.

Anytime you change resource definitions, calendars, schedules, or configuration, you can put your changes into effect immediately by issuing a REFRESH command from the user interface. Unless you specify otherwise, AF/OPERATOR allows all active internal processes to complete before refreshing the definitions and configuration.



Resource management componentsThis figure illustrates the relationship among AF/OPERATOR’s resource management facilities.



Runtime environmentThe definitions and instructions you specify from the user interface are executed by the Resource State Manager (referred to as the RSM in this document) runtime environment, which has three components.

For more informationSee “Resource Management” on page 47 for detailed information and instructions.

Component Purpose

Scheduler (SC) initiates resource activities at the times you specify

Event processor (EV) traps system events related to your resource activity specifications

Resource Control Facility (RCF) issues console commands to execute your resource management instructions


How Console Management Works

How Console Management Works

BasicsAF/OPERATOR provides two facilities to help you manage the console: traps and the Trap Group Manager.

A trap is a rule statement that determines how AF/OPERATOR responds to system events such as messages, commands, OMEGAMON exceptions, or date and time information.

Trap Group Manager allows you to create groups of traps and define actions for those traps.

For more informationSee “Resource Management” on page 47 for detailed information and instructions.

Resource Control Facility


Resource Control Facility

BasicsThe Resource Control Facility (RCF) is RSM’s console interface. It issues console commands based on your resource definitions, calendars, and schedules. You can also issue RCF commands directly from the console to:

n start, stop, and refresh RSM

n override scheduled resource management on an emergency basis

n produce resource management reports

For more information and instructions on using RCF to monitor and control AF/OPERATOR, see “Resource Control Facility Commands” on page 105 and “Starting, Stopping, and Overseeing AF/OPERATOR” on page 181.

How to get Help for RCFRCF provides a comprehensive Help facility, which you can invoke from the MVS console.

To get a list of RCF commands, issue this command from the MVS console:

rcf HELP

where rcf is the name of the currently running RCF. The name of RCF is set in the KAORSTRT command that starts RCF from each RSM.

To get Help on the use and syntax of an individual RCF command, issue this command from the MVS console:

rcf HELP command

where command is the RCF command you want information about.


User Interface

User Interface

IntroductionAF/OPERATOR provides a user interface based on the IBM Common User Access (CUA) standard. CUA panels are designed to facilitate product learning, navigation, and use.

Function keysAF/OPERATOR supports the ISPF function key definitions shown in the table below.

Function Key Use Description

F1 Help Displays a pop-up explaining the current panel or entry field. For field-level Help, the cursor must be on te entry field when F1 is pressed.

F3 Exit Exits from the current panel and returns one level in the display hierarchy

F4 Prompt Displays a list of valid entries for the field. A plus sign (+) beside an entry field indicates that you can press F4 to display a list of choices. The cursor must be on the entry field when F4 is pressed.

F7 Backword Scrolls backword if more lines exist than can be displayed on the current panel

F8 Forward Scrolls forward if more lines exist than can be displayed on the current panel.

F10 Actions Moves cursor to the action bar at the top of the panel, to allow selection of a pull-down menu. If the cursor is already on the action bar, the cursor is moved to its prior position in the display

F12 Cancel Cancels a panel , displaying the previous panel.

User Interface


Navigation in an entry panelTo navigate in an entry panel, use these keys:

Tips:

n To display a list of the active function keys on each user interface panel, enter this command at the Command ===> prompt:

PFSHOW

To remove the list, enter this command:

PFSHOW OFF

n To display the panel ID of each user interface panel, enter this command at the Command ===> prompt:

PANELID

To remove the panel ID, enter this command:

PANELID OFF

How to get Help from the user interfaceWhen you are using the AF/OPERATOR user interface, press F1 if you need help. If your cursor is on an entry field when you press F1, you will get Help for that field. Otherwise, you will get Help for the panel.

Key Description

Tab To move from field to field

F1 To display panel- or field-level Help

F4 To display a list of choices for fields followed by a plus ( + ) sign

F3 or F12 To close a panel without changes

Enter To update with the changes that you made


What To Do Next

What To Do Next

Recommended orderNow you are ready to set up and use AF/OPERATOR. Here is the order of the basic procedures you will perform.

Step Task See....

1 Configuration

You will set up:

1. resource management profiles and systems

2. user authorizations

3. recovery notification lists

4. desired overrides to certain Candle defaults

“Configuring AF/OPERATOR” on page 41

2 Calendar definition

You will define calendars for your data center and specify daytypes to be used in scheduling resources

“Set up Calendars” on page 68

3 Resource definition

You will define:

1. classes of resources to be managed by AF/OPERATOR

2. individual resources in each class

3. activities and activity messages for each resource

4. predecessors and successors for each resource

5. recovery procedures for each resource

6. a schedule for each resource

“Defining Resources” on page 78

4 Trap group management

You will set up trap groups and schedule them to control the flow of messages and commands to and from the console

“Trap Group Management” on page 183

5 Testing and debugging

You will check, test, and correct your AF/OPERATOR setup to make sure it works the way you want it to.

“Testing and Debugging” on page 241

What To Do Next


Configuring AF/OPERATOR 27

Configuring AF/OPERATOR

IntroductionBefore you can use AF/OPERATOR, you need to complete the configuration process described in this chapter. This chapter assumes:

n you have finished using the CICAT to install and customize AF/OPERATOR.

n you can access the AF/OPERATOR interface.

Chapter ContentsAF/OPERATOR Configuration Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Set Up System Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Define Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Add and Authorize Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Define Notification Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Set Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Optionally, Create Sysplex Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Optionally, Create TCP/IP Communications Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . 45

2

AF/OPERATOR Configuration Tasks


AF/OPERATOR Configuration TasksAll the configuration tasks explained in this chapter are options that appear on the AF/OPERATOR main panel, options 1-9, under the Configuration heading.

Order of tasksThe rest of this chapter guides you through the tasks of configuring AF/OPERATOR. We recommend that you perform the tasks in the order in which they appear in this chapter for maximum efficiency.

Note: As you navigate through the panels, online help is available. To receive specific help about any field, press F1 while the cursor is located in the field. Moving the cursor outside of a field and pressing F1 provides general help information.

Step Task

1 Set up system profiles

A profile is associated with the AF/OPERATOR application (or system) you are running. It contains settings that correspond to your system, so that the definitions you set in a profile determine the settings you want in effect during a system’s session.

You must first create and select a profile because the profile is associated with some of the other configuration tasks. For example, when adding users, you must provide a profile name. Also, all the resources you define are automatically associated with the currently selected profile.

Configuration Automation Control Tools Help ----------------------------------------------------------------------------- KAOIXMIN AF/OPERATOR - VERSION 340 Command ===> ________________________________________________________________ Select an option from the list below and press Enter, or make a selection from the Action-bar above. Current Profile . . : KAO001 Authorization Group : -DEFAULT- Configuration Automation 1. Profile 11. Calendars 2. Field Preferences 12. Resources 3. Global Preferences 13. Traps 4. Authorization Groups 14. Refresh 5. Notification Groups 6. Systems Control 7. Users 21. Sysplex Console 8. Sysplex 9. TCP Communications F1=Help F3=Exit F10=ActBar


AF/OPERATOR Configuration Tasks

2 Define systems

Defining a system tells AF/OPERATOR where a resource resides or identifies the target system for an AF/OPERATOR command.

3 Add and authorize users

There are two steps to authorizing users:n Define one or more authorization groups, where you establish authorization

settings that give users the ability to carry out different actions on different features of AF/OPERATOR.

n Add each user to an authorization group. When adding a user, you need to provide a system profile and an authorization group to associate with the user.

4 Define notification

You can define a notification group of users to receive a message when the recovery retry limit for a resource is exceeded.

5 Set preferencesn Field preferences provide the default values for some of the fields that appear in

AF/OPERATOR.n Global preferences are the options that the AF/OPERATOR task uses when

processing work.

6 Optionally, create Sysplex definitions

If the AF/OPERATOR task will coordinate automation tasks with other AF/OPERATORs in the Sysplex, identify the System IDs in a Sysplex definition.

7 Optionally, create Sysplex definitions

If you will communicate with an AF/OPERATOR directly from a TSO session, define the TCP/IP Automation Servers that are available for Sysplex Console support.

Set Up System Profiles



IntroductionThe settings you define in a system profile are active for the AF/OPERATOR session associated with or using that profile. When you log onto AF/OPERATOR, you are automatically associated with the last profile that was selected or with the default profile.

Note: To set up system profiles, you must have authority to add or edit profiles. If you cannot do so, see the person responsible for configuring AF/OPERATOR at your site.

For each profile, you must provide:

n a profile name having up to six characters, that identifies the profile. Each profile name must be unique.

n a profile description having up to 50 characters.

Setting up system profilesTo define or select a system profile, enter option 1 (Profile) on the command line of the AF/OPERATOR main panel.

AF/OPERATOR displays the Profiles panel that lists the name of the current profile followed by a list of all of the defined profiles. From this panel you can Add, Browse, Copy, Delete, or Modify a profile definition, or Select a profile that will become the current profile.

Actions Help ------------------------------------------------------------------------------ KAOIXP10 AF/OPERATOR - Profiles Row 1 to 3 of 3 Command ===> ________________________________________________________________ Select row(s) and press Enter. Valid selections are: (A)dd, (B)rowse, (C)opy,(D)elete, (M)odify, and (S)elect. Current Profile . . : KAO001 Profile Description __ KAO001 Sample Profile __ PROF0 Test Profile __ PROF1 Test Profile ******************************* Bottom of data ******************************** F1=Help F3=Exit F7=Backward F8=Forward F10=ActBar



Procedure to create a new profileTo create a new profile:

1. Define the profile using the Add or Copy actions available on this panel. n To base your new profile on an existing one, type C in the action entry field next to the

profile being copied and press the Enter key.

n To define a profile from scratch, type A in any action entry field and press the Enter key.

2. Select a profile by by typing S in the action entry field next to the profile name and press the Enter key. This makes the selected profile the current profile.AF/OPERATOR displays a message indicating that the current profile has been changed to the profile you selected.

3. Assign appropriate resources to the selected profile, including resource-related components (for example, schedules, activities, and activity messages, recovery, day order, predecessors, messages, and traps), using other AF/OPERATOR panels.

Modify AF/OPERATOR startup to include your default profileWhen the AF/OPERATOR application environment is initialized, use the Resource Control Facility (RCF) RCF INIT command to specify the name of a profile to associate with that AF/OPERATOR application. Otherwise, AF/OPERATOR uses a default profile. For detailed information on the RCF INIT command, see “Resource Control Facility Commands” on page 105 and “Starting, Stopping, and Overseeing AF/OPERATOR” on page 181.

You can create similar profiles to alter the automated use of resources for similar applications running in different AF/OPERATOR environments. For example, you can use similar profiles to simplify modifying the use of resources in either the development or the production versions of an automated application.

Note: Only one profile can run at a time with any one RCF. If you run two RCFs in separate AF/OPERATORs, each can use its own profile.

Once you have set up system profiles, you can modify the AF/OPERATOR startup command so that the profile you want to use as a default is automatically initialized whenever AF/OPERATOR is started.

When AF/OPERATOR is started, the EX KAORSTRT command in $$OGINIT (which resides in rhilev.RKANCMD) starts the Resource Control Facility (RCF). If the EX KAORSTRT command in $$OGINIT also specifies a system profile, the RSM is initialized with the definition and configuration of that profile.

Use the following command to modify the EX KAORSTRT command in $$OGINIT:

EX KAORSTR ‘runtime_table_library rcf profile initialization_type’



where:

n runtime_table_library is the name of the RSM library where the profile is located. The default library is rhilev.RKANISP.

n rcf is the name of RCF for this RSM. A command prefix is used to identify each AF/OPERATOR RSM. You can use the default, rcf, or you can choose your own command prefix.

n profile is the name of a system profile you set up from the Profile option of the AF/OPERATOR user interface. The default is KAO001.

n initialization_type is either COLD or WARM.

– COLD brings all resources defined in the given profile to their scheduled state.

– WARM brings all resources defined in the given profile to their desired state.

The desired state is the same as the scheduled state unless one of these conditions is true:

– An RCF command has been issued to start or stop a resource, and no RCF SCHEDULE command has been issued to return control of the resource to the scheduler.

– Recovery of a resource has failed and no RCF SCHEDULE command has been issued to return control of the resource to the scheduler.


Define Systems

Define Systems

IntroductionNow you will create the systems definitions that are referred to on the resource panels (identifying the system or group of systems where a resource resides or the target systems for an AF/OPERATOR command). Each system definition can refer to one or more physical systems, allowing you to create individual systems or groups of systems.

For each system definition, you need to provide:n The system ID, a unique name given to this definition and referenced by your resource

definitions.n A system description of up to 40 characters of freeform text entered as part of the system

definition.n From 1 to 8 System Management Facility (SMF) IDs, separated by blanks, that are to be

included in this definition.n The Subsystem ID that identifies the AF/OPERATOR address space associated with this

copy of AF/OPERATOR.n The name of the RCF command (rcf) on this subsystem.

Add or change a system definitionTo add a new system or change an existing system definition, enter option 6 (Systems) on the command line of the AF/OPERATOR main panel.

AF/OPERATOR displays the Systems list panel, showing all of the existing system definitions. From this panel you can Add, Browse, Copy, Delete, or Modify a system definition entry.

To create a new System Definition, use the Add or Copy actions available on this panel.

n To base your new system definition on an existing one, type C in the action entry field next to the system being copied, and press the Enter key.

n To define a system definition from scratch, type A in any action entry field and press the Enter key.

Actions Help ------------------------------------------------------------------------------ KAOIXSY0 AF/OPERATOR - Systems Row 1 to 1 of 1 Command ===> ________________________________________________________________ Select row(s) and press Enter. Valid selections are: (A)dd, (B)rowse, (C)opy,(D)elete, and (M)odify. System ID Description SMF ID Subsystem __ SYSTEST Test System SYSTST1 SYST ******************************* Bottom of data ******************************** F1=Help F3=Exit F7=Backward F8=Forward F10=ActBar

Add and Authorize Users



IntroductionTo use certain features in AF/OPERATOR, a user must be defined to AF/OPERATOR and assigned authority levels using an authorization group definition.

Each user is a member of only one authorization group. Each group member inherits the group’s authorization, including:

n the types of actions (for example, Add, Browse, Delete, Modify) that the group members can perform on AF/OPERATOR configuration panels (such as the Profiles, Field Preferences, Authorization Groups, Users, and Systems panels).

n whether members of the group can modify the group’s authorizations.

n whether members of the group can create and maintain trap definitions for use in automated procedures and manage automated traps.

n whether members of the group can create and maintain calendar and resource definitions as well as manage the following resource related components:

– Activities and activity messages

– Day order

– Messages

– Schedules

– Predecessors

– Recovery



Creating an Authorization GroupTo add a new Authorization Group or change an existing Authorization Group definition, enter option 4 (Authorization Groups) on the command line of the AF/OPERATOR main panel.

AF/OPERATOR displays the Authorization Groups list panel, listing all of the defined authorization group definitions. From this panel you can Add, Copy, Delete, or Modify an authorization group definition entry, or Edit authorization flags for a selected group.

About the DEFAULT authorization groupA user that is not in any other authorization group is a member of the default group. The default group cannot be deleted, but authorization flags can be modified. The default group gives all users the authority to complete any task. During configuration you may want to limit other users’ authority by creating new authorization groups.

Creating new authorization groupsTo create new authorization groups, complete the authorization group definition using the Add or Copy actions available on this panel.

n To base your new authorization group on an existing one, type C in the action entry field next to the group being copied, and press the Enter key.

n To define an authorization group from scratch, type A in any action entry field and press the Enter key.

Actions Help ------------------------------------------------------------------------------ KAOIXSX0 AF/OPERATOR - Authorization Groups Row 1 to 2 of 2 Command ===> ________________________________________________________________ Select row(s) and press Enter. Valid selections are: (A)dd, (C)opy, (D)elete,(E)dit Auth. Flags, and (M)odify. Group Name Description __ -DEFAULT- Default Authorization Group __ PERSONAL Personal Authorization Group ******************************* Bottom of data ******************************** F1=Help F3=Exit F7=Backward F8=Forward F10=ActBar



Changing authorization group flagsTo change the authorization flag settings for a group, type E in the action entry field next to the authorization group being changed, and press the Enter key.

AF/OPERATOR displays the Authorization Details list panel, listing all of the defined authorization items within an authorization group definition.

To toggle the Authorization Flag setting from Y to N or vice versa, type M next to the flag setting you want to change and press the Enter key.

Actions Help ------------------------------------------------------------------------------ KAOIXAU0 AF/OPERATOR - Authorization Details Row 1 from 140 Command ===> Select row(s) and press Enter. Valid selection is (M)odify. Group Name . . : -DEFAULT- __ Application Area Action Authorization Flag __ Authorization Groups (A)dd Y __ Authorization Groups (C)opy Y __ Authorization Groups (D)elete Y __ Authorization Groups (E)dit Auth. Flags Y __ Authorization Groups (M)odify Y __ AO Statistics AO Statistics Y __ Calendar (A)dd Y __ Calendar (B)rowse Y __ Calendar (C)opy Y __ Calendar (D)elete Y __ Calendar (E)dit Calendar Days Y __ Calendar (M)odify Y __ Display Status Display Status Y F1=Help F3=Exit F7=Backward F8=Forward F10=ActBar



Adding UsersTo add a new User or change an existing user definition, enter option 7 (Users) on the command line of the AF/OPERATOR main panel. The UserIDs for AF/OPERATOR are equivalent to TSO UserIDs.

AF/OPERATOR displays the User Details list panel, listing all of the defined User definitions. From this panel you can Add, Browse, Delete, or Modify a User definition entry.

n To add or modify a User definition, use the Add or Copy actions available on this panel.

n To define a new user, type A in any action entry field and press the Enter key.

n To modify a user definition, type M in the action entry field next to the user being changed and press the Enter key.

From the User Detail panel, select the Authorization Group that will be associated with this user.

Actions Help ------------------------------------------------------------------------------ KAOIXUS0 AF/OPERATOR - User Details Row 1 to 3 of 3 Command ===> ________________________________________________________________ Select row(s) and press Enter. Valid selections are: (A)dd, (B)rowse,(D)elete, and (M)odify. User ID User Name Group Profile __ USER1 Griff Halliwell -DEFAULT- KAO001 __ USER2 Pete Feyerherd -DEFAULT- KAO001 __ USER3 Rod Samuelson -DEFAULT- KAO001 ******************************* Bottom of data ******************************** F1=Help F3=Exit F7=Backward F8=Forward F10=ActBar

Define Notification Groups



IntroductionYou can define a group of TSO users to be notified when an AF/OPERATOR-controlled resource abends and automated recovery attempts fail. This notification occurs only if the link between a specific resource and a group of TSO users is established during resource definition. See “Resource Management” on page 47 for more information about defining resources.

When a resource recovery failure occurs for which notification processing has been established, either:

n a notification group that is tied to the resource receives (by TSO SEND) the following Candle-supplied resource recovery failure message:

RECOVERY RETRY LIMIT REACHED FOR resource

where resource is the name of the resource for which recovery was attempted.

n some other notification processing (for example, beeping, initiating notification chain processing, or corrective action) set up through your own notification routine is performed. For more information about writing your own notification routine, see “Recovery Failure Processing” on page 211.

Note: A user can belong to more than one notification group. All TSO users are eligible for membership in a notification group, whether they are defined as AF/OPERATOR users or not.



Defining users for notificationTo add or change a notification group and its users, enter option 5 (Notification Groups) on the command line of the AF/OPERATOR main panel.

AF/OPERATOR displays the Notification Groups panel, listing all of the defined Notification Group definitions. From this panel you can Add, Copy, Delete, or Modify a group definition, or Edit the members of a group.

To create a new Notification Group definition using the Add or Copy actions available on this panel.

n To base your new notification group on an existing one, type C in the action entry field next to the group being copied, and press the Enter key.

n To define a notification group from scratch, type A in any action entry field and press the Enter key.

n To edit the membership of a Notification Group, type E in the action entry field next to the notification group you want to edit and press the Enter key.

Actions Help ------------------------------------------------------------------------------ KAOIXNL0 AF/OPERATOR - Notification Groups Row 1 to 4 of 4 Command ===> Select row(s) and press Enter. Valid selections are: (A)dd, (C)opy, (D)elete,(E)dit UserIDs, and (M)odify. Group Name Description __ _STMGCNRS1 USER1 USER2 __ _STMGCNRS3 NOTIFY1 NOTIFY2 NOTIFY3 NOTIFY4 NOTIFY5 __ ANOTHER This can be lower case. __ JIMS GROUP An example of a notification group ******************************* Bottom of data ******************************** F1=Help F3=Exit F7=Backward F8=Forward F10=ActBar

Set Preferences


Set Preferences

IntroductionYou can set preferences that alter certain default values that are shipped with AF/OPERATOR. These preferences include:

n Field preferences, the default values for some of the fields that appear in AF/OPERATOR.

n Global preferences, the options that the AF/OPERATOR task uses when processing work.

Defining field preferencesTo view or modify the display of initial and default values that may appear on an Add panel, enter option 2 (Field Preferences) on the command line of the AF/OPERATOR main panel.

AF/OPERATOR displays the Field Preferences panel, listing all of the fields for which an initial or default value can be specified. From this panel you can Browse or Modify a field default value.

Actions Help ------------------------------------------------------------------------------ KAOIXP20 AF/OPERATOR - Field Preferences Row 1 to 15 of 198 Command ===> Select row(s) and press Enter. Valid selections are: (B)rowse, and (M)odify. __ Application Area Field Use __ Authorization Groups Authorization Group __ Authorization Groups Profile Name __ Authorization Groups Group Description __ Notification Groups Notification Group __ Notification Groups Group Description __ Notification Users User ID __ Calendar Calendar Name __ Calendar Calendar Description __ Calendar Sunday Business Day __ Calendar Monday Business Day I __ Calendar Tuesday Business Day I __ Calendar Wednesday Business Day I __ Calendar Thursday Business Day I __ Calendar Friday Business Day I F1=Help F3=Exit F7=Backward F8=Forward F10=ActBar


Set Preferences

Setting field preferencesWhen you perform an Add action on an AF/OPERATOR panel, AF/OPERATOR displays an Add panel. Fields on the Add panel can be blank or they can contain initial or default values. When AF/OPERATOR is installed, some fields are assigned initial values. Initial values are Candle-provided values that cannot be altered. Other fields have installation-assigned default values that you can change.

You can select one or more field entries from the Field Preferences panel and:

n display the field length and the initial and default values for the field.

n specify or change the default value.

n change the field’s use.

To Modify a field preference, type M in the action entry field next to the field preference you want to modify and press the Enter key.

To Browse a field preference, type B in the action entry field next to the field preference you want to browse and press the Enter key.

Defining global preferencesTo view or modify the global preference values, enter option 3 (Global Preferences) on the command line of the AF/OPERATOR main panel.

AF/OPERATOR displays the Global Preferences panel, listing the options that the AF/OPERATOR task uses when processing work. From this panel, you can change each preference value to customize AF/OPERATOR for your installation.

Actions Help ------------------------------------------------------------------------------ KAOIXGP0 AF/OPERATOR - Global Preferences Command ===> Enter the AF/Operator Global Preferences, then press Enter. WTOR Reply Timeout . . . . . . . . 5 (Seconds, 5..3600) Message Destination . . . . . . . . WTO (‘WTO’ or ‘LOG’) RCF START/STOP Command overrides Scheduler . . . . . . . YES (‘YES’ or ‘NO’) Message at Activity Failure . . . . NO (‘YES’ or ‘NO’) Responses TPUTed . . . . . . . . . NO (‘YES’ or ‘NO’) Confirm Resource Start/Stop at Initialization . . . . . . . . NO (‘NO’, ‘WARM’ or ‘BOTH’) Activate Scheduler at Startup . . . YES (‘YES’ or ‘NO’) F1=Help F3=Exit F10=ActBar

Set Preferences


Changing global preferencesFrom this panel, you can change a value by typing over the existing text. When you are finished, press the Enter key.

n WTOR Reply Timeout

Specifies the number of seconds to wait for a reply to a message sent to the operator’s console before deleting the message.

– 5 - Minimum numeric value

– 3600 - Maximum numeric value

n Message Destination

Specifies where messages are sent.

– WTO - Messages are sent to the operator’s console

– LOG - Messages are sent to the system log

n RCF START/STOP Command overrides Scheduler

Specifies whether issuing an RCF START or RCF STOP command causes Scheduling to be disabled for the resource(s).

– YES - Any RCF START/STOP command will disable scheduled activities for that resource. Once disabled, scheduled Start or Stop activites will not occur. However, the Scheduled Status is still updated, and you can later bring the resource to the Scheduled Status by issuing the RCF SCHEDULE command for the resource.

– NO - Any RCF START/STOP command will not affect any scheduled activities for that resource.

To check whether Scheduling is enabled for a resource, issue the RCF SHOW command for the resource.

n Message at Activity Failure

Specifies whether a message is issued if a Resource Start or Stop Activity fails to complete successfully. Lack of success could be due to the activity’s timing out or a failure message being trapped.

– YES - Issue the message after any retries have been performed

– NO - Do not issue any messages. The message is issued as a WTO or as a LOG message depending on the Message Destination Global Preference.

n Responses TPUTed

Specifies whether responses to RCF commands from a TSO user are issued as TPUTs

– YES - Responses to RCF commands are issued as TPUTs.

– NO - Responses to RCF commands are issued as either WTO or LOG messages, depending on the Message Destination Global Preference


Set Preferences

n Confirm Resource Start/Stop at Initialization

During Initialization and Refresh processing, the Resource Manager may Start or Stop Resources to bring them to the correct state (as determined by the Schedule or by previous RCF START or STOP commands).

– NO - No Confirmation WTORs are issued

– WARM - Confirmation WTORs are issued during a WARM Start (or Refresh) but not during a COLD Start

– BOTH - Confirmation WTORs are issued during both COLD and WARM initialization and during a Refresh

n Activate Scheduler at Startup

Specifies the Scheduler startup processing during profile initialization.

– YES - Start the resources based on the defined schedules.

– NO - None of the resources will be launched.

Optionally, Create Sysplex Definitions


Optionally, Create Sysplex Definitions

IntroductionThe Sysplex definition is a set of system IDs used by AF/OPERATOR in a Sysplex environment to control resources.

Creating Sysplex definitionsTo add a new Sysplex definition or change an existing definition, enter option 8 (Sysplex) on the command line of the AF/OPERATOR main panel.

AF/OPERATOR displays the Sysplex panel, listing all of the defined Sysplex definitions. From this panel you can Add, Browse, Copy, Delete, or Modify a Sysplex definition.

Create a new Sysplex definitionCreate the new Sysplex definition using the Add or Copy actions available on this panel.

n To base your new Sysplex definition on an existing one, type Cin the action entry field next to the Sysplex definition being copied and press the Enter key.

n To create a Sysplex definition from scratch, type A in any action entry field and press the Enter key.

Actions Help ------------------------------------------------------------------------------ KAOIXPL0 AF/OPERATOR - Sysplex Row 1 to 1 of 1 Command ===> Select row(s) and press Enter. Valid selections are: (A)dd, (B)rowse, (C)opy,(D)elete, and (M)odify. Sysplex Profile Description __ KAOPLEX KAO001 Sample SysPlex definition ******************************* Bottom of data ******************************** F1=Help F3=Exit F7=Backward F8=Forward F10=ActBar


Optionally, Create TCP/IP Communications Definitions


IntroductionIf an AF/OPERATOR has been defined as a TCP/IP Application Server, you can communicate with it directly from a TSO session. In the TCP/IP Automation Server, you can manage resources and traps on any AF/OPERATOR in the Sysplex. You can also issue MVS and AF/OPERATOR commands that are executed on the system running the selected AF/OPERATOR.

To access a TCP/IP Automation Server that has been defined, enter option 21 (Sysplex Console) on the command line of the AF/OPERATOR main panel.

Defining a TCP/IP Automation ServerTo create a new TCP/IP Automation Server definition or change an existing definition, enter option 9 (TCP/IP Communications) on the command line of the AF/OPERATOR main panel.

AF/OPERATOR displays the TCP Communications panel, listing all of the systems that have been defined as a TCP/IP Automation Server and are available for Sysplex Console support. From this panel, you can Add, Browse, Delete, or Modify a TCP/IP communication definition.

Creating a new TCP/IP Communication definitionCreate the TCP/IP Communication definition using the Add (A) action available on this panel. To define a TCP/IP definition from scratch, type A in any action entry field and press the Enter key.

Actions Help ------------------------------------------------------------------------------ KAOITTC0 AF/OPERATOR - TCP Communication Row 1 to 1 of 1 Command ===> Select row(s) and press Enter. Valid selections are: (A)dd, (B)rowse,(D)elete, and (M)odify. HostName Port# Description __ TCPTEST 00000 Sample TCP Connection Description ******************************* Bottom of data ******************************** F1=Help F3=Exit F7=Backward F8=Forward F10=ActBar

Resource Management 47

Resource Management

IntroductionThis chapter explains how to set up automated resource management. It includes instructions for:

n setting up calendars and schedules for your data center resources

n specifying which resources you want AF/OPERATOR to manage and how you want each of them to be managed

Before you beginIf you have not read “Introduction to AF/OPERATOR” on page 15, read it now for a basic explanation of resource management. In addition, make sure you have performed the configuration tasks described in “Configuring AF/OPERATOR” on page 27.

Check the current profile to be sure it is the one you want your calendar and resource definitions assigned to. The name of the current profile is shown on the AF/OPERATOR Primary menu. If the current profile is not the one you want to use, you can select a different one using the Profile option of the AF/OPERATOR Primary menu. For more information about profiles, see “Set Up System Profiles” on page 30.

Note: The first time you set up your resource management specifications, you may want to use the AF/OPERATOR user interface without the runtime environment. To do so, you should stop the AF/OPERATOR runtime environment if it is active. For instructions, see “Starting, Stopping, and Overseeing AF/OPERATOR” on page 181.

Chapter ContentsOverview of Resource Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Set up Calendars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Set Up Calendars—Task 1: Plan and Define the Calendar . . . . . . . . . . . . . . . . . . . . . . . . 53Set Up Calendars—Task 2: Specify Calendar Days . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Procedure to Specify Calendar Days. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Defining Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Define Resources—Task 1: Define the Resource Classes . . . . . . . . . . . . . . . . . . . . . . . . . . 62Define Resources—Task 2: Define the Individual Resources . . . . . . . . . . . . . . . . . . . . . . . 65Specify Activities and Activity Qualifiers for a Resource . . . . . . . . . . . . . . . . . . . . . . . . . . 72

3


Specify Activity Messages for a Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Specify Predecessors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Set up Resource Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Set up Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Set Up Schedules—Task 1: Define schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Set Up Schedules—Task 2: Specify Daytype Order. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Example: Defining a Calendar for Use by the RSM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Example: Creating RSM-Controlled Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99


Overview of Resource Management


Relating resources to systemsWhen you define each resource, you identify the system or systems on which the resource runs. A single resource can be defined to run on more than one system, and the wildcard asterisk character (*) can be used to assign a resource to all systems defined to AF/OPERATOR. To add system definitions so that more systems will be available for your resource definitions, use the Systems option on the AF/OPERATOR Primary menu. For system definition instructions, see “Define Systems” on page 33.

Note: Even though resources can be on any system defined to AF/OPERATOR, the task that issues success and failure messages for each resource must be on the same system as AF/OPERATOR.

Resource classes and groupsWhen you define resources, you can make your job easier by first defining a resource class (or template) and then defining individual resources as members of the class. The resources that are members of the class can inherit some of the attributes of the class, thus eliminating the need to reenter identical information each time you define a similar resource.

Notes:

1. To define a resource class, use the same name for Resource Name and Class Name in the resource definition.

2. To define an individual resource as a member of a class, use different names for resource and class. The class must be defined before its member resources.

3. To define an individual resource that is not a member of a class, do not specify a class name in the resource definition.You can also define resources as members of a group A group is a logical collection of resources that can be controlled by a single RCF command.



Planning resource managementBefore you set up resource management, spend some time planning the way you want your data center to run. You will save a great deal of time later if you answer these questions now:

1. Calendar and scheduleDo you want resources to run on the same schedule every day, or are there days when you want resources to run shorter hours than usual (for example, holidays) or longer hours than usual (for example, quarterly report production days)? Are there meaninful categories of days for your data center, for example, weekdays, weekends, holidays, and payroll processing days? See “Example: Defining a Calendar for Use by the RSM” on page 94 and “Example: Creating RSM-Controlled Resources” on page 99 for illustrations of a calendar that covers the year 2000, and a group of resources that make use of this calendar for scheduling.

2. Resource classes and groupsDo you want to define classes of resources that share important attributes (such as recovery procedures or scheduling)? Do you want to put resources into groups to be controlled as a unit?

3. ActivitiesWhat commands or other processes are used for starting and stopping each resource?

4. Predecessors and successorsWhat are the predecessors and successors of each resource? That is, what resources must be active before another resource can be started; or what resources must remain active and not stopped until another resource has been stopped?

5. Success and failureWhat WTOs indicate the success or failure of attempts to start or stop each resource? What processes should result from those successes and failures?

6. RecoveryWhat message indicates an abend for each resource? What recovery process do you want AF/OPERATOR to initiate for each resource? In case recovery fails, who should receive notification, and by what method (for example, WTOR or beeper)?



Order of tasksThe rest of this chapter guides you through the tasks of setting up resource management. For maximum efficiency, be sure to perform these tasks in the order recommended in the table that follows. If you need help on any panel or entry field, press F1.

Note: You can create calendar and resource definitions by using either the Copy option or the Add option. The rest of this chapter assumes that you will use the Copy option.

When you’ve finishedWhen you have completed all of your resource management definitions, you make your new definitions take effect by refreshing or restarting AF/OPERATOR. For instructions, see “Starting, Stopping, and Overseeing AF/OPERATOR” on page 181.

Order Task

1 Set up calendars

1. Plan for and define the calendars

2. Specify calendar days

2 Define resources

1. Define the resource classes

2. Define the individual resources

3 Specify activities and activity messages

4 Specify predecessors

5 Set up recovery

6 Set up schedules

1. Define the schedules

2. Specify day priority order

Set up Calendars


Set up Calendars

IntroductionAn AF/OPERATOR calendar is a set of definitions that assign specific attributes (called daytypes) to the days of the year.

Because each AF/OPERATOR calendar can apply to many resources, you need to set up the calendars before you define the resources. To set up a calendar, you specify:

1. which days of the week are normally business days, and which days are normally off days

2. what daytypes (for example, holidays or payroll processing days) require resource scheduling different from that provided by the normal distinction between business and off days

3. a priority order of daytypes, to be applied when a day is classified as more than one type


Set Up Calendars—Task 1: Plan and Define the Calendar


Planning the calendarBe sure you have answered the questions listed in “Planning resource management” on page 50. In addition, consider whether you need to define more than one calendar. For example, if you have offices, data centers, or other facilities in more than one country, you probably need to define separate calendars for resources assigned to each facility.

Defining a calendarTo define a calendar, enter option 11 (Calendars) on the command line of the AF/OPERATOR main panel. AF/OPERATOR displays the Calendars panel, shown below. This panel lists all of the defined calendars and allows you to create new calendars.

The first time you use AF/OPERATOR, the only calendar shown is the Candle-supplied EXAMPLE calendar.

Actions Help ------------------------------------------------------------------------------ KAOIXCL0 AF/OPERATOR - Calendars Row 1 to 1 of 1 Command ===> ________________________________________________________________ Select row(s) and press Enter. Valid selections are: (A)dd, (B)rowse, (C)opy,(D)elete, (E)dit Calendar Days, and (M)odify. Name Description __ EXAMPLE This is an example of a calendar def ******************************* Bottom of data ********************************



To define a new calendar based on EXAMPLE, type C (Copy) in the entry field to the left of EXAMPLE, and press the Enter key. This displays the Calendar Definition panel you use to define a new calendar based on an existing one.

The example calendar identifies Monday through Friday as business days. Saturday and Sunday are off days. Business day and off day are two predefined default daytypes that may be used for resource scheduling.

You are now ready to specify day definitions and daytypes for the new calendar.

KAOIXCL4 AF/OPERATOR - Calendar Definition KAOG010P - Row copied and ready for modification.Calendar Name . . . . . . EXAMPLECalendar Description . . This is an example of a calendar def ---------------------------------------------------------- Weekly Business Calendar Enter “X” for Business Days or blank for Off Days. Changes below will affect every Business Day Calculation.---------------------------------------------------------- Weekday Name Daytype Name Business Day Monday . . . . (MON) . . . . . X Tuesday. . . . (TUE) . . . . . X Wednesday. . . (WED) . . . . . X Thursday . . . (THU) . . . . . X Friday . . . . (FRI) . . . . . X Saturday . . . (SAT) . . . . . _ Sunday . . . . (SUN) . . . . . _ F1=Help F12=Cancel


Set Up Calendars—Task 2: Specify Calendar Days


Modifying the calendar called EXAMPLEOn the Calendar Definition panel, change the calendar name and description by typing over the existing text. The calendar name can be up to 12 characters long, and the first character cannot be a number. The description can be up to 45 characters long.

If your data center has different business and off days from those shown in the example, make any necessary changes. An X indicates that a day of the week is a business day, and a blank indicates that a day of the week is an off day.

When you have finished making changes, press Enter to save the new calendar definition. AF/OPERATOR redisplays the Calendar Definition panel showing a message indicating that your calendar definition has been added successfully.

Specifying day definitionsA day definition identifies a point in time or a collection of points in time. Each day definition has a daytype name that is used to identify the day definition.

User-defined daytypesThe daytype is useful only to indicate differences in the scheduling of a resource. A daytype designates a category of days on which you want the same resource scheduled. For example, you might define a daytype called HOLIDAY to be applied to several days on which resources run on the same holiday schedule.

AF/OPERATOR provides 9 predefined daytypes, called default daytypes: MON, TUE, WED, THU, FRI, SAT, SUN, BUS (business day), and OFF (off day). The default daytypes are reserved. Because the default daytypes can apply to all days of the year, you need to define your own daytypes only for resource scheduling that differs from the normal weekly schedule of business days and off days.

You can categorize the days of the year into as many daytypes as you find useful for scheduling purposes. A single calendar date can have more than one daytype assigned to it. For example, the first Tuesday in October may be classified as BUS, except that in election years, that day might be considered a holiday for your business and thus also be listed with a daytype of HOLIDAY.

When assigning daytypes to calendar days, you will list the calendar days in a specific order. The order in which calendar days and their associated daytypes are defined is used by AF/OPERATOR to resolve potential scheduling conflicts.

Once you have assigned any specialized daytypes to the appropriate calendar days, you can set up the schedule by daytype for each resource (see “Set up Schedules” on page 85).



Day calculation methodsYou can choose among 4 methods of calculating calendar days.

Method Description Example

Specific date (S) A single day June 30, 1995 (specified as 1995/06/30)

Day of month (D) One or more days occuring a spcified number of days after the beginning or before the end of all months selected

Sixth day before the end of every month except December

Weekday of month (W) One or more specified monthly occurrences of one or more specified days of the week

First and third Fridays from the beginning of every month

Business day of month One or more days occurring a specified number of business days after the beginning or before the end of all months

Third business day before the end of every month


Procedure to Specify Calendar Days


IntroductionTo illustrate the procedure, display the Calendars panel. Now, in addition to the Candle EXAMPLE, this panel contains the name of the calendar you just defined. Type E (for Edit) in the entry field to the left of the name of your calendar, and press Enter.

Selecting the day definition methodAF/OPERATOR displays the Calendar Day Definitions panel, listing all days defined for that calendar in rank order. The first time you access the Calendar Day Definitions panel, you will see four Candle-supplied examples of calendar days. Each example uses one of the four calculation methods described in the preceding table.

Type C (for Copy) in the entry field to the left of the day on which you want to base your first day definition and press Enter.

Actions Help ------------------------------------------------------------------------------ KAOIXCA0 AF/OPERATOR - Calendar Day Definitions Row 2 from 12 Command ===> ________________________________________________________________ Select row(s) and press Enter. Valid selections are: (A)dd, (C)opy, (D)elete,and (M)odify. Calendar Name : EXAMPLE Order Day Name Daytype Meth Ovrd Description __ 1 BUSINESSDAY 3BUSDAY B Example of a business day calcu __ 2 DAYOFMONTH 6DAYOFMONTH D Example of a day of month calcu __ 3 WEEKDAY TUES4 W Example of a weekday calculatio __ 4 SPECIFICDAY XMAS S Example of a specific day defin ******************************* Bottom of data ********************************



Modifying the day definitionAF/OPERATOR now displays the Calendar Day Definition panel with the day definition you selected. You can change the definition as needed. This example shows a named day definition using the daytype 3BUSDAY. It is based on the business day calculation method.

Change the day definition name, description, and daytype by typing over the existing text.

Notes:

n The day definition name must be unique. It can be up to 12 characters long, and the first character cannot be a number. The description can be up to 40 characters long. The daytype can be up to 12 characters long.

n Calendar day name and description fields are provided for your convenience in creating and reading calendars, but are not used in scheduling resources. Only the daytype, relative order, business/off override, and calculation method specifications affect resource scheduling.

n The default daytypes are predefined and reserved. You cannot specify a default daytype (MON-SUN, BUS, or OFF) in your day definitions. Use daytypes that reflect the calculation method specifications. For example, the daytype BUSDAY123 reflects the first three business days of the month.

n Many calendar days can share the same daytype. Make sure your daytypes are useful ones for your resource scheduling needs.

KAOIXCAE AF/OPERATOR - Calendar Day Definition KAOG010P - Row copied and ready for modification. Calendar Name . . . . . . : EXAMPLE Day Definition Name . . . . BUSINESSDAY Description . . . . . . . . Example of a business day calculation Daytype . . . . . . . . . . 3BUSDAY + Relative Order . . . . . . . 1 (1-999) Override . . . . . . . . . . _ (B)usiness Day, (O)ff Day, or blank Calculation Method . . . . . B + F1=Help F4=Prompt F12=Cancel



Assign a ranking order to the dayNow assign a relative order number between 1 and 999 to the day, where 1 is the highest priority rank. Relative order is used to resolve potential conflicts between business and off day specifications for an individual day. For example, the first Monday of every month is defined as a business day. However, U.S. Labor Day (which occurs on the first Monday of September) has the override set to offday. Candle recommends you place LABORDAY below 1STMONDAY on the list. This will ensure that 1STMONDAY retains its higher priority number and thus is not affected by the override.

If you want the day definition in this example to remain a business day, do not enter a business/off day override.

Note: For days calculated by any method other than business day of month, you can use the Override field to override the business/off day designation the day would normally have as determined by the rest of the calendar.

Select a day calculation methodYou are now ready modify your day definitions by providing a calculation method and performing the calculation for each day you are defining.

On the Calendar Daya Definition panel, for the field Calculation Method, enter one of these codes:

n B for business day of month

n W for weekday of month

n D for day of month

n S for specific day

For a description of each of these methods, see “Day calculation methods” on page 56.



AF/OPERATOR now displays the panel appropriate to the calculation method you selected. In the example below, the day is calculated as the third business day from the beginning of every month.

Save the day definitionChange the day calculation specifications as needed. When you have finished, press Enter to save the day definition. Result: The Calendar Day Definition panel reappears, with a message indicating that your day definition has been added successfully.

Note: Whether a given date is a business day or not is determined by:

n the business day specifications for the calendar as a whole

n the business day overrides for days in this calendar that rank higher than the day now being defined

Continue to define calendar days until you have all the day definitions you need for your calendar.

KAOIXCA4 AF/OPERATOR - Business Day of Month Method Entry Tab to choice. Press Enter when finished. Count days from Beginning or End B (“B” or “E”) Days of the Month (“X”=Selected, Blank=Not Selected)1st__ 2nd __ 3rd X 4th__ 5th__ 6th__ 7th__8th__ 9th__ 10th__ 11th__ 12th__ 13th__ 14th__15th__ 16th__ 17th__ 18th__ 19th__ 20th__ 21st__22nd__ 23rd__ 24th__ 25th__ 26th__ 27th__ 28th__29th__ 30th__ 31st__ Months of the Year (“X”=Selected, Blank=Not Selected)Jan X Feb X Mar X Apr X May X Jun XJul X Aug X Sep X Oct X Nov X Dec X F1=Help F12=Cancel


Defining Resources

Defining Resources

IntroductionIn this section, you will set up the resource definitions that give AF/OPERATOR basic resource management specifications. You first define classes of resources. Then you define the individual resources that share the characteristics of each class. Candle recommends that you define resource classes first because you can then define the individual resources more efficiently.

Relationship of a resource to a classWhen a resource is a member of a class, the resource definition can inherit any or all of the following rules from its class:

n activities

n activity messages

n schedule

n recovery specifications

n predecessor

For those resources that are members of a class, you can specify that:

n You want to use the rules defined for the resource, or

n You want the resource to inherit the rules from the class

If you want an individual resource to differ from its class for any of those rules, you can direct AF/OPERATOR accordingly. AF/OPERATOR will either:

n use the rule that is defined for the resource.

n use the rule that is defined for the class. In this case, the rules are copied from the class definition to the resource definition, and the resource definition rule is discarded.

Note: If you update an existing class definition (using the modify option), those changes are not copied to the existing members of that class.

You can define individual resources without defining a class. See “Define Resources—Task 2: Define the Individual Resources” on page 65.

Before you begin, make sure you have answered the questions listed in “Planning resource management” on page 50.

Define Resources—Task 1: Define the Resource Classes



IntroductionTo define a resource class, enter option 12 (Resources) on the command line of the AF/OPERATOR Primary Menu.

AF/OPERATOR displays the Resource Definitions panel listing all defined resources. Use this panel to define new resources. The first time you access the Resource Definitions panel, you will see three Candle-supplied example definitions. Two of those, EXAMPLE1 and EXAMPLE2, are examples of resource class definitions.

To base your first resource class definition on an existing one, type C (for Copy) in the entry field beside EXAMPLE2, and press the Enter key.

Actions Help ------------------------------------------------------------------------------ KAOIXRS0 AF/OPERATOR - Resource Definitions Row 1 from 5 Command ===> ________________________________________________________________ Select row(s) and press Enter.Valid selections are: (A)dd, (B)rowse, (C)opy,(D)elete, (M)odify, Copy to (N)ew Profile, and (R)ules. Current Profile . . : KAO001 Resource Group Name System-ID Calendar Description __ EXAMPLE * SAMPLE Example Resource __ EXAMPLE1 CICS * EXAMPLE Class definition for CICS re __ EXAMPLE2 VTAM * EXAMPLE Class definition for a VTAM ******************************* Bottom of data ********************************



AF/OPERATOR now displays the Resource Definition panel showing the resource definition for EXAMPLE2. You can change the definition as needed.

Notes:

n In a resource class definition, the resource name and the class name are the same. When the resource name and the class name in a definition are different, the resource being defined is a member of the named class, which must already have been defined. When no class name is specified, the resource is not a member of any class.

n Because VTAM generally should be started before CICS, the VTAM resource class definition example (EXAMPLE2) has been defined as a predecessor (prerequisite) to the CICS resource class.

Define predecessor resourcesPredecessor resources must be defined before the resources that require them. Therefore, the first resource classes you should define are those resource classes that are predecessors to other resource classes. The predecessor relationships are defined later, as described in “Specify Predecessors” on page 79.

Name the resource and classOn the Resource Definition panel, change the resource name and the class name by typing over the existing text. To make this a class definition, use the same name for resource and class. The resource and class names can be up to 12 characters long, and the first character cannot be a number.

Automation ------------------------------------------------------------------------- KAOIXRSD AF/OPERATOR - Resource Definition KAOG010P - Row copied and ready for modification. Resource Name . . . . EXAMPLE2 Calendar Name . . . . EXAMPLE + System ID . . . . . . *_______ + “*” is allowed Task Name . . . . . . ________ Class Name . . . . . EXAMPLE2 + Group Name . . . . . VTAM + Description . . . . . Class definition for a VTAM resource Warning Time . . . . __ (Minutes, 1..60) Check Exit . . . . . ________ Always Active . . . . Y (Y/N) Always Activity . . . START + Activity Qualifier ____________________ Recovery Retry Limit 2_ Within Period . . 00:10:00 (hh:mm:ss) Notification Group . ____________ + Notification Exit . . ________ (Blank for Default) F1=Help F4=Prompt F12=Cancel



Name the calendarIn the Calendar Name field, type the name of the calendar to be used for this resource. The calendar you specify must already be defined. For a list of defined calendars, place the cursor in the Calendar Name field and press F4. Select a calendar from the pop-up that appears. If you wish to define a new calendar for this resource, select Calendars from the AF/OPERATOR Primary menu. (For calendar definition instructions, see “Set up Calendars” on page 52.)

Provide the system ID and descriptionIn the System ID field, type the name of one of the system definitions created during configuration, or type the wildcard character (*) to associate the resource class with all defined systems.

Note: The System ID may refer to a single system or a group of systems. For a list of defined systems, place the cursor in the System ID field and press F4. Select a system from the pop-up that appears. (For more information about defining systems, see “Define Systems” on page 33).

In the Description field, type a resource class description up to 40 characters long. When you have finished, press the Enter key to save the resource definition. AF/OPERATOR now displays the Resource Rule Selection panel.

Complete the Resource Rule Selection panelFrom the Resource Rule Selection panel, select Activities to define activities. This is required. See “Specify Activities and Activity Qualifiers for a Resource” on page 72.

Continue to define predecessor resource classes until you have all the definitions your resource management setup requires.

Now, define the remaining resource classes (those that require the predecessors). You can copy resource definition EXAMPLE1 for these resource class definitions.

KAOIXRSR AF/OPERATOR - Resource Rule Selection (S)elect one or more Resource rules that you wish toprocess and press Enter. Resource Name : EXAMPLE2Resource Rule_ Activities_ Activity Messages_ Schedule_ Recovery_ Predecessors F1=Help F12=Cancel


Define Resources—Task 2: Define the Individual Resources


IntroductionTo define individual resources, enter option 12 (Resources) on the command line of the AF/OPERATOR Primary menu.

AF/OPERATOR displays the Resource Definitions panel listing all defined resources and allows you to define new resources. The first time you access the Resource Definitions panel, you will see three Candle-supplied example definitions. EXAMPLE is an example of an individual resource class definition.

To base your first resource class definition on an existing one, type C (for Copy) in the entry field beside EXAMPLE, and press the Enter key.

Actions Help ------------------------------------------------------------------------------ KAOIXRS0 AF/OPERATOR - Resource Definitions Row 1 from 5 Command ===> ________________________________________________________________ Select row(s) and press Enter. Valid selections are: (A)dd, (B)rowse, (C)opy,(D)elete, (M)odify, Copy to (N)ew Profile, and (R)ules. Current Profile . . : KAO001 Resource Group Name System-ID Calendar Description __ EXAMPLE * SAMPLE Example Resource __ EXAMPLE1 CICS * EXAMPLE Class definition for CICS re __ EXAMPLE2 VTAM * EXAMPLE Class definition for a VTAM ******************************* Bottom of data ********************************



AF/OPERATOR displays the Resource Definition panel showing the resource definition for EXAMPLE. Now you can change the definition as needed

Name the resource and classChange the resource name by typing over the existing text. To make this a class definition, use the same name for resource and class. The resource and class names can be up to 12 characters long, and the first character cannot be a number.

Name the calendarIn the Calendar Name field, type the name of the calendar to be used for this resource. The calendar you specify must already be defined. For a list of defined calendars, place the cursr on the Calendar Name field and press F4. Select a calendar from the pop-up that appears. If you wish to define a new calendar for this resource, select Calendars from the AF/OPERATOR Primary Menu. (For calendar definition instructions, see “Set up Calendars” on page 52.)

Provide the system IDIn the System ID field, type the name of one of the systems definitions created during configuration, or type the wildcard character (*) to associate the resource class with all defined systems.

Note: The System ID may refer to a single system or a group of systems. For a list of defined systems, place your cursor in the System ID field and press F4. Select a system from the pop-up that appears. (For more information about defining systems, see “Define Systems” on page 33).

Automation-------------------------------------------------------------------------KAOIXRSD AF/OPERATOR - Resource Definition KAOG010P - Row copied and ready for modification.Resource Name . . . . EXAMPLECalendar Name . . . . SAMPLE +System ID . . . . . . * + “*” is allowedTask Name . . . . . . PAYROLL1Class Name . . . . . ____________ +Group Name . . . . . ____________ +Description . . . . . Example ResourceWarning Time . . . . 5_ (Minutes, 1..60)Check Exit . . . . . ________Always Active . . . . N (Y/N)Always Activity . . . _____ + Activity Qualifier ____________________Recovery Retry Limit 3_ Within Period . . 00:15:00 (hh:mm:ss)Notification Group . ____________ +Notification Exit . . ________ (Blank for Default) F1=Help F4=Prompt F12=Cancel



Provide a task name and descriptionIn the Task Name field, type the name of the job or started task that will issue messages indicating the success or failure of attempts to start the resource or to recover the resource if it abends. The Candle-supplied default check exit also uses the task name you specify here to determine the state (active or inactive) of the resource. For information about the check exit, see page 110.

Optionally, you can specify a group name if you want RCF to treat this and other resources as a group, or a logical collection of resources that can be controlled by a single RCF command. For example, you could assign the group name CICS to all CICS resources.

In the Description field, type a resource class description up to 40 characters long.

Notes:

n Even though the resource can be on any system, the task that issues success and failure messages for the resource must be on the same system as this copy of AF/OPERATOR.

n Each resource or resource class can use only one task name. However, more than one resource or class can use the same task name if none of the resources are predecessors and none of the resources require predecessors.

Determine whether to issue a warning WTORIf you want AF/OPERATOR to issue a warning WTOR before starting or stopping the resource, type a value in the Warning time field. Completing this field is optional. The value indicates how many minutes in advance of the scheduled activity you want the warning to be issued. If you do not want a warning WTOR to be issued, leave the Warning time field blank.

When the warning WTOR (message KAO03900) is issued, the operator at the console can take any of these actions:

n Allow the activity to occur as scheduled by responding OK (the default reply).

n Request that the activity occur immediately by responding NOW.

n Postpone the activity for a specified number of minutes.

n Cancel the activity.

Notes:

n If you specify a warning time, AF/OPERATOR will never initiate a scheduled activity for the resource without first issuing the warning WTOR.

n If the operator does not respond to the warning WTOR within the time specified in the Warning time field, AF/OPERATOR initiates the activity.

n The warning time is defined for the resource, not for the schedule. Therefore, under some conditions, the resource activity may be postponed beyond the scheduled time as a result of the warning time.

n If you use an RCF command from the console to stop or start a resource, the warning WTOR is not issued and the warning time is not observed.



n If you issue an RCF REFRESH command (either from the user interface or from the console) while a warning WTOR is outstanding, either the operator must reply to the WTOR or the warning must time out before the REFRESH can take effect.

n If you issue an RCF REFRESH FORCE command from the console while a warning WTOR is outstanding, the WTOR will not time out and the scheduled activity will not take place.

n Delaying or canceling an activity for a predecessor resource will prevent activities scheduled for other resources (those that require the predecessor resource) from occurring.

Name the check exit to be usedIf you have written your own REXX exec to check on the state of the resource, type the name of that exec in the Check Exit field.

Providing your own check exit is optional. If you leave this field blank, the Candle-supplied default routine is used. The default check exit issues an ACTIVE function to check the state of the resource.

For more information about the Candle default check exit and instructions for writing your own exit, see “Checking the State of a Resource” on page 206.

Determine whether the resource will be controlled by the scheduleUse the Always Active field to determine whether the resource will be controlled by the resource management schedule. If you decide to remove a resource from control of the schedule by keeping the resource active at all times, you must also specify an Always Activity of START and optionally an Activity qualifier.

An activity describes an action to take on a resource. A process is a console command or an invocation of a REXX exec that performs the activity. An activity qualifier is a parameter that selects the exact process to be used for the activity.

n If you want the resource to be started and stopped at scheduled times, type N in the Always Active field and leave the Always Activity and Activity Qualifier fields blank.

n If you want the resource to be active at all times, type Y in the Always Active field and type START in the Always Activity field.

n If you typed Y in the Always Active field, you can also specify, in the Activity Qualifier field, a value to be used in selecting the process that performs the activity.

If you do not specify an activity qualifier, AF/OPERATOR considers the activity qualifier to be null. You can specify an activity qualifier when you set up recovery for the resource or when you issue an RCF command at the console to start or stop the resource. If you do so, AF/OPERATOR appends the activity qualifier to the end of the process as a character string. AF/OPERATOR does not validate the character string.



Specify recovery informationIf you want AF/OPERATOR to attempt to restart the resource when the resource abends, supply the following recovery information:

n In the Recovery Retry Limit field, specify how many times you want AF/OPERATOR to retry starting the resource. If you specify 0 (zero), AF/OPERATOR will not try to recover the resource when it abends.

n In the Within Period field, specify a time limit for the retries. The period specified cannot exceed 24 hours.

n In the Notification Group field, type the name of one of the notification groups defined for this profile. (You can press F4 for a list of the defined notification groups.) The users in this notification group will be notified if recovery fails.

If you do not specify a notification group, the notification group named DEFAULT is notified. If there is no DEFAULT notification group, no one is notified. For more information about defining notification groups, see “Define Notification Groups” on page 38.

n If you have written your own REXX exec to handle recovery notification, type the name of that exec in the Notification Exit field. If you leave this field blank, AF/OPERATOR uses the Candle-supplied default routine. The Candle routine issues a TSO SEND to every TSO user in the notification group. For information about the Candle default notification routine and instructions for writing your own routine, see “Recovery Failure Processing” on page 211.

When you have finished, press the Enter key.



Optionally, define the class specificationFollow this step only if you defined a resource using a class. If your resource does not include a class, continue with “Copy resources to a new profile” on page 71. If you defined resources using a class, AF/OPERATOR displays the Class Specification Entry pop-up. You can use this panel to determine the source of the resource’s attributes.

When you have finished, press the Enter key to save the resource definition. AF/OPERATOR now displays the Resource Rule Selection panel.

From the Resource Rule Selection panel, select Activities to define activities. This is required. See “Specify Activities and Activity Qualifiers for a Resource” on page 72.

Continue to define predecessor resources until you have all the definitions your resource management setup requires.

KAOIXRS4 AF/OPERATOR - Class Specification Entry Press Enter when finished. Valid Values are: C = Class or R = ResourcePredecessor Source . . . . . . RSchedule Source . . . . . . . RActivity Source . . . . . . . RActivity Message Source . . . RRecovery Source . . . . . . . R F1=Help F12=Cancel

KAOIXRSR AF/OPERATOR - Resource Rule Selection (S)elect one or more Resource rules that you wish toprocess and press Enter. Resource Name : EXAMPLE2Resource Rule_ Activities_ Activity Messages_ Schedule_ Recovery_ Predecessors F1=Help F12=Cancel



Copy resources to a new profileOnce you have defined a resource for one profile, you can reuse it in another profile. To do so, copy the resource from the current profile to a new profile.

To copy a resource to a new profile, enter option 12 (Resources) on the command line of the AF/OPERATOR Primary Menu. AF/OPERATOR displays the Resource Definitions panel. Type N in the entry field of the resource you want to copy, and press the Enter key.

AF/OPERATOR displays the Target Profiles panel. That panel shows a list of valid profiles.

Type S next to the profile to which you want to copy the selected resources, and press Enter. A panel appears indicating whether the copy is possible. Follow the instructions on the panel and press Enter.

Actions Help ------------------------------------------------------------------------------ KAOIXRSE AF/OPERATOR - Target Profiles Row 1 to 3 of 3 Command ===> ________________________________________________________________ (S)elect one, and only one, Target Profile. Current Profile...... KAO001 Selected Resource.... EXAMPLE Profile Description __ KAO001 Sample Profile __ PROF0 Test Profile Profile ******************************* Bottom of data ********************************

Actions Help ------------------------------------------------------------------------------ KAOIXRSE AF/OPERATOR - Target Profiles Row 1 to 3 of 3 Command ===> ________________________________________________________________ (S)elect one, and only one, Target Profile. Current Profile...... KAO001 Selected Resource.... EXAMPLE Profile Description __ KAO001 Sample Profile __ PROF0 Test Profile __ PROF1 Test Profile ******************************* Bottom of data ********************************

Specify Activities and Activity Qualifiers for a Resource



IntroductionAn activity describes an action to take on a resource. For each resource you defined, you will now:

1. specify activities2. define the messages that indicate the success or failure of each activity. This procedure is

discussed in the next unit.

Specify activities for a resourceUse the Resource Activities panel to specify activities for a resource. You can access the Resource Activities panel in one of the following two ways:

1. As a choice from the Resource Rule Selection panel that is displayed after you have defined a resource.

2. As a choice from the Resource Definitions panel by entering R (for Rules) in the entry field of the resource you want to change. AF/OPERATOR then displays the Resource Rule Selection panel, on which you select Activities.

This example shows the Resource Activities panel for EXAMPLE, a CICS resource. The Activity Qualifier column may contain a qualifier for the activity. An activity qualifier is a parameter that selects the exact process to be used for the activity. In the Process column for each activity is the MVS command that performs the activity. A process can be a console command or an invocation of a REXX exec that performs an activity.

Actions Help ------------------------------------------------------------------------------ KAOIXAC0 AF/OPERATOR - Resource Activities Row 3 from 13 Command ===> ________________________________________________________________ Select row(s) and press Enter. Valid selections are: (A)dd, (B)rowse, (C)opy,(D)elete, and (M)odify. Resource Name . : EXAMPLE Activity Qualifier Process (first 40 characters) __ START start payroll1,cold __ START WARM f payroll1,restart __ STOP p payroll1 ******************************* Bottom of data ********************************



Only two activities, START and STOP, can be specified. However, you can affect the way in which those activities behave by specifying different processes and activity qualifiers. On the Resource Activities panel above, the activities shown for EXAMPLE include two types of START activity:

1. The activity START with no activity qualifier executes the process START PAYROLL1,COLD.

2. The activity START with activity qualifier WARM executes the process F PAYROLL1,RESTART.

To base a new activity definition on an existing one, type C (for Copy) in the entry field beside the activity, and press Enter.

AF/OPERATOR displays the Resource Activity panel showing a START activity definition for resource EXAMPLE. Now you can change the definition as needed.

KAOIXAC4 AF/OPERATOR - Resource Activity KAOG010P - Row copied and ready for modification.Resource Name . . . . . : EXAMPLEActivity . . . . . . . . START (“START” or “STOP”)Activity Qualifier . . . ____________________Process (126 Characters) . . . . . start payroll1,cold ________________________________________________________________ _________________________________Success Process (126 Characters) se ‘payroll1 started’,u(fred) ________________________________________________________________ _________________________________Failure Process (126 Characters) se ‘payroll1 failed to start’,u(fred,jim)_________________________________Activity Timeout . . . . 10 (Minutes, 1 to 720)Maximum Retry Count . . . 3 (0 to 99) F1=Help F12=Cancel



Define the activity and activity qualifierOn the Resource Activity panel, change the activity and/or the activity qualifier by typing over the existing text. Defining an activity qualifier is optional. Candle recommends that you do not define an activity qualifier for a default message.

For the new activity definition to be unique, either the activity or the activity qualifier must differ from the specifications in the definition being copied. The activity qualifier can be up to 20 characters long.

If you do not specify an activity qualifier in one of the following places, AF/OPERATOR considers the activity qualifier to be null:

n The Activity Qualifier field of the activity definition (for a scheduled activity)

n The Activity Qualifier field of the resource definition (for a resource defined as always active)

If the activity qualifier is null, you can insert a process Qualifier as a qualifier to the process command itself, in one of the following places:

n in the Process field of the activity definition

n in the resource’s schedule definition

n in the resource’s recovery definition

n in an RCF command issued from the console to start or stop the resource

AF/OPERATOR then appends the activity qualifier to the process as a character string. AF/OPERATOR does not validate the character string.

Specify the processNow, specify the process (the console command or REXX exec invocation) to be executed for the activity.

Also, specify the processes to be executed as a result of activity messages indicating failure and success. For information about activity messages, see “Specify Activity Messages for a Resource” on page 76. If you want to complete an activity as the result of a failure, see “Using failure processing to complete an activity” on page 75, below.

Complete the Resource Activity panelIn the Activity Timeout field, type the maximum number of minutes that the activity will be given to complete before it is considered to have failed.

In the Maximum Retry Count field, type the number of times you want AF/OPERATOR to retry the activity if it times out. If AF/OPERATOR retries the activity the specified number of times without success, it invokes the activity failure process you specified.

When you have finished, press Enter to save the activity definition. AF/OPERATOR redisplays the Resource Activities panel (see page 72), with a message indicating that the new activity definition has been saved successfully.

Continue to define activities until you have all the activity definitions you need for all your resources.



Using failure processing to complete an activityIf you want to use failure processing to complete a START or STOP activity (instead of issuing a message, for example), complete these steps:

1. Create a new activity qualifier that contains the command to be issued to complete the activity.

2. Code ‘RCF START/STOP resource qualifier’ as the failure process on the Resource Activity panel. For example:

RESOURCE: CICS

START Activity: ‘S CICS1’

“ “ Failure Process: ‘RCF START CICS RETRY’

START Activity Qualifier RETRY: ‘S CICS1,PARM=xxx’

“ “ Failure Process: ‘ssid WTO ‘’Error’’ ‘

Specify Activity Messages for a Resource



IntroductionNow that you have defined resource activities, you need to specify the activity messages, WTOs that indicate success and failure for each activity. You must define at least one correct success message for each activity for a resource. A success message is required so that AF/OPERATOR can determine whether an activity is successful. If a success message has not been defined for a resource, the status of that resource can be incorrect. If you suspect that the resource’s status is not is not correct, issue the RCF CHECK command to force AF/OPERATOR to check the status again.

If you define an activity message for an activity without a qualifier (see Example A below), that activity message will also apply automatically to all other activities for that resource that have a qualifier (see Example B below). Therefore, it is not necessary to define an activity message for Example B, since AF/OPERATOR automatically adds a trap to the message, as shown below.

Example A: Success Message for IMS1 START (No Qualifier)

XXX123 IMS IS NOW ACTIVE

Example B: Success Message for IMS1 START (Qualifier WARM)

XXX123 IMS IS NOW ACTIVE

Specify an activity messageTo specify the activity messages, access the Resource Activity Messages panel. You can do so in one of two ways:

1. As a choice from the Resource Rule Selection panel that appears after you have defined a resource.

2. From the Resource Definitions panel by selecting R (for Rules) in the entry field next to the resource you want to change. From the Resource Rule Selection panel, select Activity Messages.



AF/OPERATOR displays the Resource Activity Messages panel.

In this example, the Resource Activity Messages panel shows the success and failure messages for the START activity for resource EXAMPLE. Each activity can have many failure messages.

Create a new acitivity messageTo base a new activity message on an existing one, type C (for Copy) in the entry field next to the START command you want to copy. AF/OPERATOR displays the Resource Activity Messages panel showing the success activity message specifications for START EXAMPLE.

Complete the Resource Activity Messages panelSpecify the activity and activity qualifier that result in execution of the process whose success or failure this message will indicate.

In the WTO Text field, type the text of the activity failure or success message. WTO Text does not automatically append an asterisk (*) to the end of the message.

Actions Help ------------------------------------------------------------------------------ KAOIXAM0 AF/OPERATOR - Resource Activity Messages Row 3 from 8 Command ===> ________________________________________________________________ Select row(s) and press Enter. Valid selections are: (A)dd, (B)rowse, (C)opy,(D)elete, and (M)odify. Resource Name . : EXAMPLE Activity Activity Qualifier Fail/Success Job Name WTO Text (First 60 Characters) __ START S $HASPaaa* __ START F $HASPxxx* __ START F * payroll data base is empty. check employee file, then rest __ START WARM F * payroll has run out of money and has stopped ******************************* Bottom of data ********************************

KAOIXAM4 AF/OPERATOR - Resource Activity Messages KAOG010P - Row copied and ready for modification.Resource Name . . . : EXAMPLEActivity . . . . . . START (“START” or “STOP”)Activity Qualifier . ____________________ +WTO Text (128 Characters) $HASPaaa* ________________________________________________________________ ____________________________Job Name . . . . . . ____________Fail or Success . . . S (“F” or “S”) F1=Help F4=Prompt F12=Cancel



In the Job Name field, type the name of the job or task you expect to issue this message.

If you do not specify a job name, the task name for this resource is used. Any characters allowed in the Job Name field of the AF/OPERATOR WTO TRAP command are valid here, including pattern characters. See the AF/OPERATOR Command Reference Manual for information on pattern characters.

In the Fail or Success field, type S if the message indicates activity success, or F if the message indicates activity failure.

When you have finished, press Enter to save the activity message. AF/OPERATOR displays the Resource Activity Messages panel with a message indicating that the new activity message has been saved successfully.

Continue to specify activity messages until you have success and failure messages for all resource activities.

You are now ready to specify the predecessors for each resource.


Specify Predecessors


IntroductionA predecessor is a resource that must be active before another resource can be started. A predecessor at startup can also be a successor at shutdown, if it must not be stopped until after the resource you are defining is stopped. (For example, in most data centers, VTAM must be started before CICS and must not be stopped until after CICS is stopped. Therefore, VTAM is a predecessor to CICS at startup and a successor to CICS at shutdown.) In this section, you will establish predecessor and successor relationships.

If you do not want to specify predecessors for any of your resources, you can skip to “Set up Resource Recovery” on page 82.

Procedure to specify predecessors and successorsSpecify predecessors and successors by accessing the Resource Predecessors panel. You can do so in one of two ways:

1. As a choice from the Resource Rule Selection panel that AF/OPERATOR displays after you have defined a resource.

2. From the Resource Definitions panel by selecting R (for Rules) in the entry field next to the resource you want to change. When AF/OPERATOR displays the Resource Rule Selection panel, select Predecessors.

AF/OPERATOR displays the Resource Predecessors panel.

Actions Help ------------------------------------------------------------------------------ KAOIXPR0 AF/OPERATOR - Resource Predecessors Row 1 from 1 Command ===> ________________________________________________________________ Select row(s) and press Enter. Valid selections are: (A)dd, (C)opy, (D)elete,and (M)odify. Resource . . . : EXAMPLE1 Predecessor SMFID Successor Flag __ EXAMPLE2 N ******************************* Bottom of data ********************************



In this example, the Resource Predecessors panel shows the predecessor definitions for resource class EXAMPLE1. EXAMPLE1 has only one predecessor, EXAMPLE2, which is not defined as a successor.

Notes:n SMFID is the SMFID of the predecessor.n During resource definition, a predecessor wait time of 10 minutes was established for

EXAMPLE1. This means that if EXAMPLE2 is not active by 10 minutes after AF/OPERATOR is scheduled to start EXAMPLE1, the success process for the scheduled START act

n To override a resource’s predecessor relationships and start the resource even though one or more predecessors are inactive, you can use this console command:RCF START resource FORCE

For more information about the RCF START command, see “Resource Control Facility Commands” on page 105.

Complete the Predecessor Definition panelTo base a new predecessor definition on an existing one, type C (for Copy) in the entry field beside EXAMPLE2.

The Copy Predecessor panel shows the EXAMPLE2 predecessor definition for resource EXAMPLE1.

To specify another predecessor for the resource, change the predecessor name by typing the name of another defined resource over the existing text.For a list of resources that are eligible to be predecessors, press F4 while the cursor is on the Predecessor Name field. If the resource you want to specify as a predecessor is not on the list, go back to the Resource Definitions panel and define that resource before you continue.In the Successor Flag field, type Y if you want the named predecessor also to be a successor at shutdown, or type N if you do not want the named predecessor to be a successor at shutdown.When you have finished, press Enter to save the predecessor definition. AF/OPERATOR redisplays the Resource Predecessors panel with a message indicating that the predecessor definition has been saved successfully.Continue to specify predecessors until you have all the predecessor definitions that your resource management setup requires.

Note: You must change the predecessor name to use add or copy. You may only modify the successor flag for existing resource predecessors.

KAOIXPR4 AF/OPERATOR - Predecessor Definition KAOG010P - Row copied and ready for modification.Resource Name . . . : EXAMPLE1Predecessor Name . . . EXAMPLE2 +SMFID of Predecessor . ________ +Successor Flag . . . . N (Y/N) F1=Help F4=Prompt F12=Cancel



You are now ready to set up resource recovery.

Set up Resource Recovery



IntroductionWhen a defined resource abends, AF/OPERATOR tries to restart it a specified number of times within a specified time period. These retries are attempts at recovery. If recovery fails, AF/OPERATOR begins notification of data center personnel.

If you do not want AF/OPERATOR to attempt recovery when resources abend, make sure that zero (0) is specified for the Recovery Retry Limit value in the resource definition. Then you can skip to “Set up Schedules” on page 85.

In each resource definition, you specified:

n the number of recovery retries

n the time limit for retries

n the list of TSO users to be notified if recovery fails

n the notification routine to be used

On the Resource Recovery panel, you will specify:

n the WTO that indicates the resource has abended

n the activity and activity qualifier that will execute the recovery process

The RSM uses the messages you define on the Recovery panels to monitor changes to resources. If you want the RSM always to report Resource Status correctly, then you must define a Recovery entry for the message that indicates a resource has terminated

If you do not define a Recovery entry for the resource termination message, the Resource may abend or be stopped by a process outside the control of the Resource Manager, and the RSM will not be able to detect it.

Notes:

n Recovery retries and activity retries are not the same. Recovery retries are the result of an abend. Activity retries are the result of unsuccessful attempts to start or stop a resource.

n AF/OPERATOR counts retries, not abends. Abends occurring during a recovery retry are ignored.

n If recovery is successful, AF/OPERATOR resumes monitoring the resource for abends.

n If the retry limit is reached, AF/OPERATOR initiates no further activities for a resource until you issue RCF commands to reset and restart the resource.



Procedure to set up recovery for a resourceTo set up recovery, access the Resource Recovery panel. You can do so in one of two ways:


2. From the Resource Definitions panel by entering R (for Rules) in the entry field next to the resource you want to change. When the Resource Rule Selection panel displays, select Recovery.

AF/OPERATOR displays the Resource Recovery panel.

This example shows a recovery specification for resource EXAMPLE. When task PAYROLL1 issues a WTO containing the pattern $OPERMSG*, resource EXAMPLE has abended. AF/OPERATOR then attempts the specified START activity.

Complete the Resource Recovery panelTo base a new recovery specification on an existing one, type C (for Copy) in the entry field beside PAYROLL1, and press the Enter key. AF/OPERATOR displays the Resource Recovery panel on which you can specify WTO text and Recovery Activity.

Actions Help ------------------------------------------------------------------------------ KAOIXRE0 AF/OPERATOR - Resource Recovery Row 1 from 3 Command ===> ________________________________________________________________ Select row(s) and press Enter. Valid selections are: (A)dd, (B)rowse, (C)opy,(D)elete, and (M)odify. Resource Name . : EXAMPLE Activity Activity Qualifier Job Name WTO Text (First 60 Characters) __ START WARM $OPERMSG* ******************************* Bottom of data ********************************

KAOIXRE4 AF/OPERATOR - Resource Recovery KAOG010P - Row copied and ready for modification.Resource Name . . . . . . . . . : EXAMPLEWTO Text (128 Characters) $OPERMSG* ________________________________________________________________ ____________________________Job Name . . . . . . . . . . . . ____________Recovery Activity . . . . . . . . START (“START” or “STOP”)Recovery Activity Qualifier . . . WARM + F1=Help F4=Prompt F12=Cancel



In the WTO Text field, specify the pattern used to trap abend messages from the resource. You must specify an entry in the WTO text field. Resource Name is a protected field and cannot be changed.

In the Job Name field, type the name of the job or task you expect to issue this message.

n If you do not specify a job name, the task name for this resource will be used.

n Any characters allowed in the Job Name field of the AF/OPERATOR WTO TRAP command are valid here, including pattern characters. See the AF/OPERATOR Command Reference Manual for information on pattern characters.

In the Recovery Activity and Recovery Activity Qualifier fields, specify the activity and activity qualifier that will execute the desired recovery process.

n In the example, the activity is START and the process Qualifier is WARM. The combination START WARM executes the process to be used for recovery retries: F PAYROLL1, RESTART (the process specified in the activity definition for START WARM).

n If the activity qualifier you specify here was not defined during resource definition or activity definition, it is appended as a character string at the end of the process. AF/OPERATOR does not validate the character string.

When you have finished, press Enter to save the recovery definition. AF/OPERATOR redisplays the Resource Recovery panel with a message indicating that the new recovery definition has been added successfully.

NotificationIf recovery does not succeed in the specified number of retries within the specified time period, a notification routine is invoked. In Candle’s default notification routine, this message goes (by TSO SEND) to TSO users in the notification group:

RECOVERY RETRY LIMIT REACHED FOR resource

You can also create your own notification routine if, for example, you want to establish an escalation chain or if you want members of the notification group to be beeped. For instructions on writing your own notification exec, see “Recovery Failure Processing” on page 211.


Set up Schedules

Set up Schedules

IntroductionAn AF/OPERATOR schedule is a set of specifications for starting and stopping a resource at certain times on certain days using designated daytypes. For each resource you defined, you will now:

1. Define schedules2. Specify the day priority order that resolves scheduling conflictsBefore you begin, make sure you have answered the questions listed in “Planning resource management” on page 50.

How resource definitions and schedules interactEach resource definition has three fields that affect the resource’s schedule.

Before you perform the task of defining schedules, make sure that the calendar and resource definitions are correct for the scheduling you want to set up.

When a resource is not under the schedule’s controlA resource is normally under the control of the schedule. That is, it is started and stopped according to the schedules you set up. However, under the following conditions, the resource is not under the control of the schedule:

n After an RCF START or RCF STOP command has been issued for a resource, the resource’s schedule is ignored until one of two things happens:

1. An RCF SCHEDULE command returns control of the resource to the schedule.2. An RCF INIT COLD command reinitializes AF/OPERATOR and brings all resources in

the current profile to their scheduled state.n If a resource abends and recovery fails, the resource’s schedule is ignored until an RCF

SCHEDULE command returns control of the resource to the schedule.

n If a resource is defined as Always Active, its schedule (if any) is ignored.

Field Effect on schedule

Calendar Name As a starting point for you to begin the scheduling proces, the calendar provides its daytypes associated with the all of the dates for each month.

Warning Time This value causes a warning WTOR to be issued at a point in time specified before the scheduled activity time.

Always Active If the value in this field is Y, the resource is always active and the schedule for the resource is ignored.

Set Up Schedules—Task 1: Define schedules



IntroductionTo define schedules for resources, access the Schedule panel. This can be done in one of two ways:


2. From the Resource Definitions panel, by selecting R (for Rules) in the entry field next to the resource you want to change. When the Resource Rule Selection panel is displayed, select Schedule.

AF/OPERATOR displays the Schedule panel. This Schedule panel shows a summary of the scheduled activities for resource class EXAMPLE1. EXAMPLE1 has seven defined daytypes, each one with different schedules. Each line of a resource’s schedule is called a schedule entry.

Actions Help ------------------------------------------------------------------------------ KAOIXSC0 AF/OPERATOR - Schedule Row 3 from 16 Command ===> ________________________________________________________________ Select row(s) and press Enter. Valid selections are: (A)dd, (B)rowse, (C)opy,(D)elete, and (M)odify. Resource Name : EXAMPLE1 Calendar Name : EXAMPLE Order Daytype Date Time Activity Qualifier __ 1 XMAS 11:99:99 START STARTCICS __ 1 XMAS 18:99:99 STOPT STOPCICS __ 2 BUS 99:99:99 START STARTCICS __ 2 BUS 99:29:99 START STARTDB2 __ 2 BUS 17:59:99 STOP STOPDB2 __ 2 BUS 18:99:99 STOP STOPCICS __ 3 MON 16:99:99 STOP STOPCICS __ 4 TUE4 17:99:99 STOP STOPCICS __ 5 FRI 98:99:99 START STARTCICS __ 5 FRI 18:99:99 STOP STOPCICS __ 6 3BUSDAY 15:99:99 START __ 7 6DAYOFMONTH 11:99:99 START __ 999 1995/12/31 95:99:99 STOP STOPCICS __ 999 1996/91/91 15:99:99 STOP STOPCICS __ 999 2929/92/29 95:99:99 STOP STOPCICS ******************************* Bottom of data ********************************



Notes:

n The Schedule panel for EXAMPLE1 shows one way in which schedules for different daytypes can overlap or conflict. The calendar for EXAMPLE1 defines Friday as a business day, but the resource is scheduled to start at 9 a.m. on business days and at 8 a.m. on Fridays. In addition, Christmas, the third business day of the month and the sixth day of the month, could fall on Friday. The daytype order, which you will set after defining the schedules, can help you resolve this kind of scheduling conflict.

n When you create a schedule for a resource class, the schedule applies to every resource for which these two conditions are true:

1. The resource is defined as a member of the class.

2. The specification for the Schedule field of the Class Specification Entry panel (see page 70) for the resource definition is C (for Class), indicating that the schedule for the resource should be inherited from the class.

Defining a new schedule entryTo base a new schedule entry on an existing one, type C (for Copy) in the entry field beside FRI. Result: The Schedule Entry panel shows the schedule entry for daytype FRI for resource EXAMPLE1.

KAOIXSC4 AF/OPERATOR - Schedule Entry KAOG010P - Row copied and ready for modification.Resource Name : EXAMPLE1Calendar Name : EXAMPLE Enter Schedule information below Daytype FRI + OR Specific Date __________ (yyyy/mm/dd)Order . . 2 (1-999)Time . . . 08:00:00 (hh:mm:ss) Late Time ________ (hh:mm:ss)Activity START (“START”, “STOP” or “TRAPG”)Qualifier STARTCICS____________ + F1=Help F4=Prompt F12=Cancel



In this example, the schedule entry for FRI provides for resource EXAMPLE1 to start at 8 a.m.

Notes:

n When you examine a schedule entry, keep in mind that other schedule entries may overlap or conflict with it. Although AF/OPERATOR does not check for schedule overlap, you can view the schedule panel for any conflicts that may appear after modifying your schedules and correct them by redoing the procedure.

n For schedules that use the same daytype, you must specify a unique combination of time and activity.

n You can specify a start activity using one daytype and a stop activity using a different daytype.

On the Schedule Entry panel, change the entries in either the Daytype or the Specific Date fields and in the Time field by typing over the existing text.

n You must specify either a daytype or a specific date, but you cannot specify both in the same schedule activity specification.

n Daytype must be one of the default daytypes or a daytype already defined in the calendar used by this resource.

n Specific Date is a single date, in the format yyyy/mm/dd. Specific dates are always given a daytype order of 999.

n To create a unique schedule entry, you must change the value in at least one of these fields:

– Daytype

– Specific Date

– Time

n The time format is hh:mm:ss. The range of acceptable times is 00:00:01 (1 second past midnight) to 24:00:00 (midnight).

Complete the order fieldAlthough you can complete the order field at this time, this is an optional field. Candle recommends that you wait until you are finished defining your schedules. It will then be easier for you to determine the appropriate order. See “Set Up Schedules—Task 2: Specify Daytype Order” on page 90 for more information.

Specify activity and activity qualifierSpecify the activity and activity qualifier for the time. The combination of activity and activity qualifier must already have been defined in this resource’s activity definition. If no activity qualifier was specified in the activity definition, the value you specify now is added to the process command as a qualifier. See “Specify Activities and Activity Qualifiers for a Resource” on page 72 for more information.



Optionally, complete the Late Time fieldIn the Late Time field, you can specify a clock time after which AF/OPERATOR will not initiate the activity. The Late Time is a timeout associated with the schedule, not with the resource or activity. Its purpose is to prevent resources impacted by batch jobs (such as data base reorganization) from being started or stopped during AF/OPERATOR reinitialization.

Do not use the Late Time to specify a time range for an online task.

If the Late Time specified is earlier than the Time value, the Late Time is assumed to be on the next day.

You can use a combination of these three time settings to control delays in scheduled activities:

n Predecessor Wait Time (set in the resource definition)

n Activity Timeout (set in the activity definition)

n Late Time (set in the schedule definition)

Complete the Schedule Entry panelContinue defining schedule entries for this and other resources until you have all the scheduling specifications you need. Be sure to specify a complete schedule for every daytype. Daytypes do not inherit scheduling information from each other, even if one daytype is a more specific example of another daytype. For example, if Christmas falls on Friday, daytype XMAS does not inherit the schedule of daytype FRI. You must provide a complete schedule for both daytypes.

Set Up Schedules—Task 2: Specify Daytype Order



IntroductionThis unit describes the procedure you use to specify daytype order.

Procedure for specifying daytype orderWhen specifying an initial daytype order for your schedules or modifying an existing order, start with the Resource Definitions panel.

On the Resource Definitions panel, type R in the entry field beside the resource for which you want to alter the daytype order, and press Enter. When the Resource Rule Selection panel is displayed, select Schedule.

Actions Help ------------------------------------------------------------------------------ KAOIXRS0 AF/OPERATOR - Resource Definitions Row 1 from 5 Command ===> ________________________________________________________________ Select row(s) and press Enter.Valid selections are: (A)dd, (B)rowse, (C)opy,(D)elete, (M)odify, Copy to (N)ew Profile, and (R)ules. Current Profile . . : KAO001 Resource Group Name System-ID Calendar Description __ EXAMPLE * SAMPLE Example Resource __ EXAMPLE1 CICS * EXAMPLE Class definition for CICS re __ EXAMPLE2 VTAM * EXAMPLE Class definition for a VTAM ******************************* Bottom of data ********************************



AF/OPERATOR displays the Schedule panel listing all of the schedules for a resource sorted into daytype order. When the schedule for a resource uses a daytype for the first time, it assigns 999, the lowest-priority entry on the list, as its order number.

In this example, BUS has a higher priority than FRI. Thus, as the panel illustrates, the schedule for BUS will take effect on the date sharing both BUS and FRI. To ensure that the schedule for Fridays is used on the business days that are Fridays, move BUS order 2 to order 7.

Notes:

n You can arrange priority specifications in any way you choose.

n The highest priority order number is 1, and the lowest is 999.

n The schedule for the less specific daytype (BUS) should appear after the schedule for the more specific one (FRI) that you want to take effect.

Actions Help ------------------------------------------------------------------------------ KAOIXSC0 AF/OPERATOR - Schedule Row 3 from 16 Command ===> ________________________________________________________________ Select row(s) and press Enter. Valid selections are: (A)dd, (B)rowse, (C)opy,(D)elete, and (M)odify. Resource Name : EXAMPLE1 Calendar Name : EXAMPLE Order Daytype Date Time Activity Qualifier __ 1 XMAS 11:99:99 START STARTCICS __ 1 XMAS 18:99:99 STOPT STOPCICS __ 2 BUS 99:99:99 START STARTCICS __ 2 BUS 99:29:99 START STARTDB2 __ 2 BUS 17:59:99 STOP STOPDB2 __ 2 BUS 18:99:99 STOP STOPCICS __ 3 MON 16:99:99 STOP STOPCICS __ 4 TUE4 17:99:99 STOP STOPCICS __ 5 FRI 98:99:99 START STARTCICS __ 5 FRI 18:99:99 STOP STOPCICS __ 6 3BUSDAY 15:99:99 START __ 7 6DAYOFMONTH 11:99:99 START __ 999 1995/12/31 95:99:99 STOP STOPCICS __ 999 1996/91/91 15:99:99 STOP STOPCICS __ 999 2929/92/29 95:99:99 STOP STOPCICS ******************************* Bottom of data ********************************



Modifying daytype orderTo modify the daytype order, type M (for Modify) in the entry field beside the schedule whose daytype order you want to change, and press Enter. AF/OPERATOR displays the Schedule Entry panel.

Enter the order number for the point at which you want this entry inserted. For example, if you wanted to move the less specific daytype BUS from order 2 to order 7 (thus lowering the day’s priority), you would enter 7 in the Order field for daytype BUS.

To give an entry the highest priority, enter 1 in the order field; to give it the lowest priority, enter 999.

When you have finished, press Enter to save the new daytype order.

KAOIXSC2 AF/OPERATOR - Schedule Entry KAOG010P - Row copied and ready for modification.Resource Name : EXAMPLE1Calendar Name : EXAMPLE Enter Schedule information below Daytype BUS + OR Specific Date __________ (yyyy/mm/dd)Order . . 7 (1-999)Time . . . 08:00:00 (hh&colon.mm&colon.ss) Late Time ________ (hh&colon.mm&colon.ss)Activity START (“START”, “STOP” or “TRAPG”)Qualifier STARTCICS____________ + F1=Help F4=Prompt F12=Cancel



AF/OPERATOR redisplays the Schedule Panel showing the change in the order of the schedules. Continue to modify the daytype order as needed.

Interpreting the result of your modificationThe result shows BUS as the lowest priority and FRI at a higher priority. Thus, the schedule for FRI will be used if both FRI and BUS appear on the same date.

You have now completed all of your resource management definitions. To make your new definitions take effect, refresh or restart AF/OPERATOR. For instructions, See “Starting, Stopping, and Overseeing AF/OPERATOR” on page 181

Actions Help ------------------------------------------------------------------------------ KAOIXSC9 AF/OPERATOR - Schedule Row 3 from 16 Command ===> ________________________________________________________________ Select row(s) and press Enter. Valid selections are: (A)dd, (B)rowse, (C)opy,(D)elete, and (M)odify. Resource Name : EXAMPLE1 Calendar Name : EXAMPLE Order Daytype Date Time Activity Qualifier __ 1 XMAS 11:99:99 START STARTCICS __ 1 XMAS 18:99:99 STOPT STOPCICS __ 2 MON 16:99:99 STOP STOPCICS __ 3 TUE4 17:99:99 STOP STOPCICS __ 4 FRI 98:99:99 START STARTCICS __ 4 FRI 18:99:99 STOP STOPCICS __ 5 3BUSDAY 15:99:99 START __ 6 6DAYOFMONTH 11:99:99 START __ 7 BUS 99:99:99 START STARTCICS __ 7 BUS 99:29:99 START STARTDB2 __ 7 BUS 17:59:99 STOP STOPDB2 __ 7 BUS 18:99:99 STOP STOPCICS __ 999 1995/12/31 95:99:99 STOP STOPCICS __ 999 1996/91/91 15:99:99 STOP STOPCICS __ 999 2929/92/29 95:99:99 STOP STOPCICS ******************************* Bottom of data ********************************

Example: Defining a Calendar for Use by the RSM



Background for the exampleBy following this example, you can define a calendar for use by the Resource State Manager (RSM). Create this complete calendar for the year 2000 by copying the SAMPLE calendar and giving it the name WEEK2000. The WEEK2000 calendar begins with the standard work week, Monday through Friday, with Saturday and Sunday as off days.

Calendar definition scenarioDefine the normal WEEK2000 calendar as follows:

n Monday through Friday are normal business (BUS) days.

n Saturday and Sunday are normal off (OFF) days.

n Annual holidays (President’s Day through Christmas) are defined as business day overrides.

n Payday is defined as overriding the 1st and 15th business days of each month.

n The last Friday of every month is defined as a special business day override.

n August 20, 2000, is defined as a special anniversary day.

Begin with the base day definitions of Monday through Friday as business (BUS) days and Saturday and Sunday as off (OFF) days.

Actions Help ------------------------------------------------------------------------------ KAOIXCL0 AF/OPERATOR - Calendars Row 1 to 3 of 3 Command ===> ________________________________________________________________ Select row(s) and press Enter. Valid selections are: (A)dd, (B)rowse, (C)opy,(D)elete, (E)dit Calendar Days, and (M)odify. Name Description __ EXAMPLE This is an example of a calendar def __ SAMPLE A Sample Calendar __ WEEK1999 COMPLETE 1999 CALENDAR __ WEEK2000 COMPLETE 2000 CALENDAR ******************************* Bottom of data ********************************



As shown in the next panel, entries 1 through 6 define the annual holidays that override normal business days during year 2000. All six entries use calculation method D to define a specific holiday.

The next example illustrates the definition for Christmas (entry number 6 in the panel above) in the year 2000. Calculation method D is used to define Christmas. Note that this overrides the normal business days (Monday and Tuesday) that fall on December 25th and 26th.

KAOIXCL2 AF/OPERATOR - Calendar Definition KAOG010Q - Row displayed and ready for modification. Calendar Name . . . . . : WEEK2000 Calendar Description . . COMPLETE 2000 CALENDAR ---------------------------------------------------------- Weekly Business Calendar Enter “X” for Business Days or blank for Off Days. Changes below will affect every Business Day Calculation. ---------------------------------------------------------- Weekday Name Daytype Name Business Day Monday . . . . (MON) . . . . . X Tuesday. . . . (TUE) . . . . . X Wednesday. . . (WED) . . . . . X Thursday . . . (THU) . . . . . X Friday . . . . (FRI) . . . . . X Saturday . . . (SAT) . . . . . Sunday . . . . (SUN) . . . . . F1=Help F12=Cancel

Actions Help ------------------------------------------------------------------------------ KAOIXCA0 AF/OPERATOR - Calendar Day Definitions Row 5 from 32 Command ===> ________________________________________________________________ Select row(s) and press Enter. Valid selections are: (A)dd, (C)opy, (D)elete,and (M)odify. Calendar Name : WEEK2000 Order Day Name Daytype Meth Ovrd Description __ 1 PRESDAY PRESDAY D B PRESIDENT’S DAY __ 2 MEMORIAL MEMORIAL D B MEMORIAL DAY __ 3 JULY4 JULY4 D B 4TH OF JULY __ 4 LABORDAY LABORDAY D B LABOR DAY __ 5 THANKSDAY THANKSDAY D B THANKSGIVING __ 6 CHRISTMAS CHRISTMAS D B CHRISTMAS __ 7 PAYDAY PAYDAY B PAYDAY __ 8 LASTFRI LASTFRI W B LAST FRIDAY OF EACH MONTH __ 9 ANNIV ANNIV S B D-DAY 2000 ******************************* Bottom of data ********************************



Specify the following for calculation method D:

n Count the days from the beginning (B) of the month.

n Select the 25th and 26th days of the month.

n Select the month of DEC.

With Relative Order specified as 7, use calculation method B to define the company’s paydays.

KAOIXCA2 AF/OPERATOR - Calendar Day Definition KAOG010Q - Row displayed and ready for modification.Calendar Name . . . . . . : WEEK2000Day Definition Name . . . : CHRISTMASDescription . . . . . . . . CHRISTMASDaytype . . . . . . . . . . CHRISTMAS +Relative Order . . . . . . . 6 (1-999)Override . . . . . . . . . . B (B)usiness Day, (O)ff Day, or blankCalculation Method . . . . . D + F1=Help F4=Prompt F12=Cancel

KAOIXCA5 AF/OPERATOR - Day of Month Method Entry Tab to choice. Press Enter when finished. Count Days From Beginning or End B (“B” or “E”) Days of the Month (“X”=Selected, Blank=Not Selected)1st _ 2nd _ 3rd _ 4th _ 5th _ 6th _ 7th _8th _ 9th _ 10th _ 11th _ 12th _ 13th _ 14th _15th _ 16th _ 17th _ 18th _ 19th _ 20th _ 21st _22nd _ 23rd _ 24th _ 25th x 26th x 27th _ 28th _29th _ 30th _ 31st _ Months of the Year (“X”=Selected, Blank=Not Selected)Jan _ Feb _ Mar _ Apr _ May _ Jun _Jul _ Aug _ Sep _ Oct _ Nov _ Dec x F1=Help F12=Cancel

KAOIXCA2 AF/OPERATOR - Calendar Day Definition KAOG010Q - Row displayed and ready for modification.Calendar Name . . . . . . : WEEK2000Day Definition Name . . . : PAYDAYDescription . . . . . . . . PAYDAYDaytype . . . . . . . . . . PAYDAY +Relative Order . . . . . . . 7 (1-999)Override . . . . . . . . . . (B)usiness Day, (O)ff Day, or blankCalculation Method . . . . . B + F1=Help F4=Prompt F12=Cancel



Specify the following for calculation method B:

n Count days from the beginning (B) of the month.

n Select the 1st and 15th business days of the month.

n Select every month of the year.

For entry number 8, calculation method W is used to define the last Friday of each month. This overrides the normal business day.

Specify the following for calculation method W:

n Count days from the end (E) of the month.

n Select the 1st week from the end of the month.

n Select Friday.

n Select every month of the year.

KAOIXCA5 AF/OPERATOR - Day of Month Method Entry Tab to choice. Press Enter when finished. Count Days From Beginning or End B (“B” or “E”) Days of the Month (“X”=Selected, Blank=Not Selected)1st x 2nd _ 3rd _ 4th _ 5th _ 6th _ 7th _8th _ 9th _ 10th _ 11th _ 12th _ 13th _ 14th _15th x 16th _ 17th _ 18th _ 19th _ 20th _ 21st _22nd _ 23rd _ 24th _ 25th _ 26th _ 27th _ 28th _29th _ 30th _ 31st _ Months of the Year (“X”=Selected, Blank=Not Selected)Jan x Feb x Mar x Apr x May x Jun xJul x Aug x Sep x Oct x Nov x Dec x F1=Help F12=Cancel

KAOIXCA2 AF/OPERATOR - Calendar Day Definition KAOG010Q - Row displayed and ready for modification.Calendar Name . . . . . . : WEEK2000Day Definition Name . . . : LASTFRIDescription . . . . . . . . LAST FRIDAY OF EACH MONTHDaytype . . . . . . . . . . LASTFRI +Relative Order . . . . . . . 8 (1-999)Override . . . . . . . . . . B (B)usiness Day, (O)ff Day, or blankCalculation Method . . . . . W + F1=Help F4=Prompt F12=Cancel



With entry number 9, calculation method S is used to define a single day in the year

Calculation method S requires that you specify a specific date, in this case, 08/20/2000, as an anniversary date.

KAOIXCA7 F/OPERATOR - Week Day of Month Method Entry Tab to choice. Press Enter when finished. Count weeks from Beginning or End E (“B” or “E”) Weeks of the Month (“X”=Selected, Blank=Not Selected)1st x 2nd _ 3rd _ 4th _ 5th _ Days of the Week (“X”=Selected, Blank=Not Selected)Sun _ Mon _ Tue _ Wed _ Thu _ Fri x Sat _ Months of the Year (“X”=Selected, Blank=Not Selected)Jan x Feb x Mar x Apr x May x Jun xJul x Aug x Sep x Oct x Nov x Dec x F1=Help F12=Cancel

KAOIXCA2 AF/OPERATOR - Calendar Day Definition KAOG010Q - Row displayed and ready for modification.Calendar Name . . . . . . : WEEK2000Day Definition Name . . . : ANNIVDescription . . . . . . . . D-DAY 2000Daytype . . . . . . . . . . ANNIV +Relative Order . . . . . . . 9 (1-999)Override . . . . . . . . . . B (B)usiness Day, (O)ff Day, or blankCalculation Method . . . . . S + F1=Help F4=Prompt F12=Cancel

KAOIXCA6 ERATOR - Specific Day Method Entry Press Enter when finished. Specific Date 2000/08/20 (YYYY/MM/DD) F1=Help F12=Cancel


Example: Creating RSM-Controlled Resources


Background for the exampleIn the example in this unit, you will create six resources that are defined as follows:

n AFOG140 is defined as Always Active.

n AFOG141 is scheduled to run on normal business days from 6AM to 3PM, and on the last Friday of every month from 7AM to 2PM.

n AFOG142 is scheduled to run the last Friday of every month.

n AFOG143 is scheduled to run the company’s anniversary date.

n AFOG144 is scheduled to run only on JAN 1, 2000.

n AFOG145 is scheduled to run on Saturdays and Sundays if they are OFF days.

Resource names AFOG141-AFOG145 refer to AFOG140 as a single predecessor resource.

Resource definition scenarioThe panels in this unit provide a scenario for defining resources.

Actions Help ------------------------------------------------------------------------------ KAOIXRS0 AF/OPERATOR - Resource Definitions Row 1 from 5 Command ===> ________________________________________________________________ Select row(s) and press Enter. Valid selections are: (A)dd, (B)rowse, (C)opy,(D)elete, (M)odify, Copy to (N)ew Profile, and (R)ules. Current Profile . . : KAO001 Resource Group Name System-ID Calendar Description __ AFOG140 SYS1 * WEEK2000 Always Active __ AFOG141 SYS2 * WEEK2000 Scheduled on BUS and PAYDAY __ AFOG142 SYS2 * WEEK2000 Scheduled on LASTFRI __ AFOG143 SYS2 * WEEK2000 Scheduled on ANNIV __ AFOG144 SYS2 * WEEK2000 Run on 01/01/2000 only __ AFOG145 SYS2 * WEEK2000 Run on SAT and SUN only ******************************* Bottom of data ********************************



Resource name AFOG140 is Always Active and is automatically started when the profile defined in the following panel is INITIATED. AFOG140 is the only one of the six resources that has no schedule associated with it.

Each of the six resources contain Activities (Start and Stop) that are defined in a similar manner. The next panel defines these activities for a resource named AFOG140.

Automation ------------------------------------------------------------------------------ KAOIXRS2 AF/OPERATOR - Resource Definition KAOG010Q - Row displayed and ready for modification. Resource Name . . . : AFOG140 Calendar Name . . . . WEEK2000 + System ID . . . . . . * + “*” is allowed Task Name . . . . . . AFOG140 Class Name . . . . . ____________ + Group Name . . . . . ____________ + Description . . . . . Pred=,Succ=N Warning Time . . . . __ (Minutes, 1..60) Check Exit . . . . . ________ Always Active . . . . Y (Y/N) Always Activity . . . _____ + Activity Qualifier ____________________ Recovery Retry Limit 9 (0..99) Within Period . . 00:10:00 (hh:mm:ss) Notification Group . ____________ + Notification Exit . . ________ (Blank for Default) F1=Help F4=Prompt F12=Cancel

Actions Help ------------------------------------------------------------------------------ KAOIXAC0 AF/OPERATOR - Resource Activities Row 1 from 13 Command ===> ________________________________________________________________ Select row(s) and press Enter. Valid selections are: (A)dd, (B)rowse, (C)opy,(D)elete, and (M)odify. Resource Name . : AFOG140 Activity Qualifier Process (first 40 characters) __ START S AFOG140 __ STOP P AFOG140 ******************************* Bottom of data ********************************



Each of the six resources have identical Activity Success Messages defined for them. The next panel shows success message definition for a resource name AFOG140.

Resource names AFOG141 through AFOG145 are defined in a similar manner. Note that these resources are not defined as Always Active. This implies that they are either started manually or they are started by the RSM by means of a schedule (see the following panel).

Actions Help ------------------------------------------------------------------------------ KAOIXAM0 AF/OPERATOR - Resource Activity Messages Row 1 from 8 Command ===> ________________________________________________________________ Select row(s) and press Enter. Valid selections are: (A)dd, (B)rowse, (C)opy,(D)elete, and (M)odify. Resource Name . : AFOG140 Activity Activity Qualifier Fail/Success Job Name WTO Text (First 60 Characters) __ START S IEF403I* __ STOP S IEF450I* ******************************* Bottom of data ********************************

Automation ------------------------------------------------------------------------------ KAOIXRS2 AF/OPERATOR - Resource Definition KAOG010Q - Row displayed and ready for modification. Resource Name . . . : AFOG141 Calendar Name . . . . WEEK2000 + System ID . . . . . . * + “*” is allowed Task Name . . . . . . AFOG141 Class Name . . . . . ____________ + Group Name . . . . . SYS2________ + Description . . . . . Pred=,Succ=N Warning Time . . . . __ (Minutes, 1..60) Check Exit . . . . . ________ Always Active . . . . N (Y/N) Always Activity . . . _____ + Activity Qualifier ____________________ Recovery Retry Limit 9 (0..99) Within Period . . 00:10:00 (hh:mm:ss) Notification Group . ____________ + Notification Exit . . ________ (Blank for Default) F1=Help F4=Prompt F12=Cancel



Resources AFOG141 through AFOG145 reference AFOG140 as a predecessor. This means that none of these can start until AFOG140 is active. The next panel defines AFOG141. Resources AFOG142 through AFOG145 are defined in a similar manner.

Resource Rule Selection (Schedules)The next set of panels illustrates defining schedules for the resources.

The following panel defines a schedule for resource AFOG141.

n AFOG141 is scheduled to run from 6AM to 3PM every business (BUS) day except payday (PAYDAY), when it runs from 8AM to 3PM.

n PAYDAY has been defined as the 1st and 15th business days of every month within the WEEK2000 calendar. To review the WEEK2000 calendar, See “Example: Defining a Calendar for Use by the RSM” on page 94.

Note: The order of definition is important. The RSM processes daytypes by order number (1 through 999) where 1 is the highest priority and 999 is the lowest. PAYDAY is specified with ORDER 1 to ensure it is processed ahead of the normal BUS day schedule.

Actions Help ------------------------------------------------------------------------------ KAOIXPR0 AF/OPERATOR - Resource Predecessors Command ===> ________________________________________________________________ Select row(s) and press Enter. Valid selections are: (A)dd, (C)opy, (D)elete,and (M)odify. Resource . . . : AFOG141 Predecessor SMFID Successor Flag __ AFOG140 * Y ******************************* Bottom of data ********************************

Actions Help ------------------------------------------------------------------------------ KAOIXSC9 AF/OPERATOR - Schedule Row 1 from 16 Command ===> ________________________________________________________________ Select row(s) and press Enter. Valid selections are: (A)dd, (B)rowse, (C)opy,(D)elete, and (M)odify. Resource Name : AFOG141 Calendar Name : WEEK2000 Order Daytype Date Time Activity Qualifier __ 1 PAYDAY 08:00:00 START __ 1 PAYDAY 15:00:00 STOP __ 2 BUS 06:00:00 START __ 2 BUS 15:00:00 STOP ******************************* Bottom of data ********************************



AFOG142 is scheduled to run from 8AM to 4PM on the last Friday of each month.

AFOG143 is scheduled to run from 5AM to 1PM on the company’s anniversary date.

AFOG144 is scheduled to run on a single date (JAN 1, 2000) from 9AM to 12 noon.

Actions Help ------------------------------------------------------------------------------ KAOIXSC9 AF/OPERATOR - Schedule Row 1 from 16 Command ===> ________________________________________________________________ Select row(s) and press Enter. Valid selections are: (A)dd, (B)rowse, (C)opy,(D)elete, and (M)odify. Resource Name : AFOG142 Calendar Name : WEEK2000 Order Daytype Date Time Activity Qualifier __ 1 LASTFRI 08:00:00 START __ 1 LASTFRI 16:00:00 STOP******************************* Bottom of data ********************************

Actions Help ------------------------------------------------------------------------------ KAOIXSC9 AF/OPERATOR - Schedule Row 1 from 16 Command ===> ________________________________________________________________ Select row(s) and press Enter. Valid selections are: (A)dd, (B)rowse, (C)opy,(D)elete, and (M)odify. Resource Name : AFOG143 Calendar Name : WEEK2000 Order Daytype Date Time Activity Qualifier __ 1 ANNIV 05:00:00 START __ 1 ANNIV 13:00:00 STOP******************************* Bottom of data ********************************

Actions Help ------------------------------------------------------------------------------ KAOIXSC9 AF/OPERATOR - Schedule Row 1 from 16 Command ===> ________________________________________________________________ Select row(s) and press Enter. Valid selections are: (A)dd, (B)rowse, (C)opy,(D)elete, and (M)odify. Resource Name : AFOG144 Calendar Name : WEEK2000 Order Daytype Date Time Activity Qualifier __ 1 2000/01/01 09:00:00 START __ 1 2000/01/01 12:00:00 STOP******************************* Bottom of data ********************************



AFOG145 is scheduled to run from 7AM to 3PM every OFF day. Note that OFF days are defined as Saturday and Sunday within the WEEK2000 calendar.

Actions Help ------------------------------------------------------------------------------ KAOIXSC9 AF/OPERATOR - Schedule Row 1 from 16 Command ===> ________________________________________________________________ Select row(s) and press Enter. Valid selections are: (A)dd, (B)rowse, (C)opy,(D)elete, and (M)odify. Resource Name : AFOG145 Calendar Name : WEEK2000 Order Daytype Date Time Activity Qualifier __ 1 OFF 07:00:00 START __ 1 OFF 15:00:00 STOP******************************* Bottom of data ********************************

Resource Control Facility Commands 105

Resource Control Facility Commands

ntroductionOnce you have defined your systems, schedules, profiles, and resources through the user interface, you can use AF/OPERATOR to initialize and control these resources. Although initialization can be a fully automated process that is invoked when the Resource State Manager (RSM) is started, you may want to control some of this activity manually. You use Resource Control Facility (RCF) commands for this purpose. Using RCF commands permits you to control resources or groups of resources running on various MVS systems from a single point of control.

The following sections of this manual discuss how to use RCF commands, how to start the RSM, and other topics you need to know in order to issue RCF commands. These topics are followed by descriptions of the commands and their syntax.

Chapter ContentsAbout RCF Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107ACTIVATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109CHECK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110DISABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112INACTIVATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113INITIATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114LIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117MONITOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119NOMONITOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120PREDECESSOR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121PURGE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123RECOVERY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124REFRESH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126SCHEDULE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127SET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128SHOW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130START . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

4


STATUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138STOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139SUCCESSOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141TERMINATE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143TRAPGROUP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144


About RCF Commands

About RCF Commands

Issuing RCF CommandsUse the following format when issuing RCF commands from the MVS console.

RCF command

where

n RCF is the command prefix you specified when starting the RSM.

n command is a valid RCF command

This chapter provides a description of the purpose and the syntax of the valid RCF commands. The following are examples of valid RCF commands.

RCF INIT PROF01 COLD

RCF START VTAM INCLUDE BELOW

Viewing online Help for RCF commandsRCF provides a comprehensive help facility which you can invoke for any RCF command by entering;

RCF HELP command

where command is the RCF command for which you want help.

Following are examples that will take you to the RCF commands’ online help:

RCF HELP INITIATE

RCF HELP START

RCF HELP REFRESH

RCF HELP SHOW SUMMARY

RCF HELP SHOW SCHEDULE

RCF HELP STATUS WAIT

Using a wild card mask to identify resourcesWhen an RCF command requires the entry of a resource name or group, you can specify like-named resources or groups using an asterisk (*) in a wild card mask. For example:

RCF START GROUP=DE*

starts all resources with group names that begin with DE

RCF STOP CIC* FORCE

forces a stop of all resources with names beginnng with CIC

About RCF Commands


Note: If you issue an RCF START or RCF STOP command followed only by an asterisk, for example, RCF START *, you will be prompted for verification of your request, since a request such as this will START or STOP all resources.

Organizing resources using group namesYou can organize resources with dissimilar names into groups by specifying a group name when you define a resource. For instance, you may choose to give resource names JES2, VTAM, and TCPIP the group name IPL. You can then refer to all of the individual resources by the group name as shown in these examples:

RCF START GROUP=IPL

RCF SHOW GROUP=IPL SUMMARY

RCF CHECK GROUP=IPL

RCF SHOW VT* SUMMARY

creates a SHOW SUMMARY report for all resources with names beginning with VT


ACTIVATE

ACTIVATE

DescriptionThe ACTIVATE command activates the selected resources. It can be abbreviated as A. It replaces the following two commands.

rcf RECOVERY resource YES

rcf SCHEDULE resource NEXT

Syntax

Examples

rcf RCF Command prefix

resource Name of a single resource or a name wildcard mask

groupname Name of a single resource group or a group name wildcard mask. The keyword GROUP= can be abbreviated as G=,GR=GRO=,GROU=,or GRP=.

smfid Name of a single SMF ID or an SMF ID wildcard mask. The keyword SMFID= can be abbreviated as S=,SM=,SMF=, or SMFI=. The default is SMFID=*.

RCF ACTIVATE VTAM

activates a single resource named VTAM

RCF ACTIVATE GROUP=IPL

activates all resources belonging to the IPL group

RCF ACTIVATE CICS

activates all resources with names beginning with CICS

RCF ACTIVATE TCPIP S=*

activates resource name TCPIP on all systems within the Sysplex

rcf ACTIVATE resource SMF=smfid ><

GROUP=groupname

CHECK


CHECK

DescriptionThe CHECK command executes the Check exit for the selected resources and sets their actual state based on the status found (START or STOP). Once the selected resources have been checked, RSM scans the active wait queue and launches any waiting START or STOP requests that are eligible to run. The command can be abbreviated as C.

Note: If the resource does not refer to an MVS task, then you must provide your own check exit to determine the actual state of the resource. A sample Check exit can be found later in this unit. If the default Check exit is used and the task cannot be located in an MVS address space, the actual state defaults to STOP.

Every time a CHECK command is issued, the RSM ensures that the current Scheduler and ARM traps are in effect by determining whether or not they are active and reestablishing them if they are not.

rcf RCF Command prefix resource

resource Name of a single resource or a resource name wildcard mask.

groupname Name of a single resource group or a group name wildcard mask. The keyword GROUP= can be abbreviated as G=,GR=,GRO=,GROU=, or GRP=.

RERUN Requests that the most recent RCF START or RCF STOP command be reissued after the named resources have been checked.

Note: If PURGE was not specified on the most recent RCF START or RCF STOP commmand, and start/stop requests are pending on the active wait queue, you must issue a PURGE command for the named resources to ensure that the RCF START or RCF STOP command can be reissued.


rcf CHECK resource SMF=smfid ><

GROUP=groupname


CHECK

Examples

Sample Check exitThe following is an example of the default Check exit used by the RSM, excluding error-checking and validation code for simplicity.

Note: For more information on the REXX function named ACTIVE, please refer to the AF/OPERATOR Command Reference in the section entitled “Candle-Supplied REXX Functions”.

RCF CHECK VTAM

checks a single resource named VTAM

RCF CHECK GROUP=IPL

checks all resources belonging to the IPL group

RCF CHECK CICS*

checks all resources with names beginning with CICS RCF

CHECK TCPIP S=*

checks resource named TCPIP on all systems within the Sysplex .

RCF CHECK CICS1 RERUN

checks resource name CICS1 and then reissues the last RCF START or RCF STOP command

/* REXX - Sample Default Check Exit (KAORRCHK) *//* *//* Input Parms: *//* Resource name *//* Task name *//* Return Value: *//* Actual state (START or STOP) *//*---------------------------------------------*/ PARSE UPPER ARG Resource ., Task .If ‘ACTIVE’(Task),then, Actual_state = “START”else Actual_state = “STOP”Return Actual_state

DISABLE


DISABLE

DescriptionThe DISABLE command is used to disable the named resources after taking the following actions on each of the specified resources:

n Purging any existing in-flight RCF START or STOP command from the active wait queue.

n Disabling the scheduler.

n Disabling recovery and deleting any outstanding recovery traps.

The command can be abbreviated as D To reenable the disabled resources, use the rcf RESET command.

Syntax

Examples





RCF DISABLE CICS1

disables a single resource named CICS1

RCF DIS GROUP=SA

disables all resources belonging to the SA group

RCF DIS CICS*

disables all resources with names beginning with CICS

RCF D AFREMOTE S=*

disables resource name AFREMOTE on all systems within the Sysplex.

rcf DISABLE resource SMF=smfid ><

GROUP=groupname


INACTIVATE

INACTIVATE

DescriptionThe INACTIVATE command inactivates the selected resources. The command can be abbreviated as INA. It replaces the following two commands.

rcf RECOVERY resource NO

rcf SCHEDULE resource NO

Syntax

Examples





RCF INACTIVATE VTAM

inactivates a single resource named VTAM

RCF INACTIVATE GROUP=IPL

inactivates all resources belonging to the IPL group

RCF INACTIVATE CICS*

inactivates all resources with names beginning with CICS

RCF INACTIVATE TCPIP S=*

inactivates resource name TCPIP on all systems within the Sysplex

rcf INACTIVATE resource SMF=smfid ><

GROUP=groupname

INITIATE


INITIATE

DescriptionThe INITIATE command initializes the AF/OPERATOR runtime environment using the predefined profile name on the current MVS system or the predefined plexname on a specific MVS system or multiple MVS systems. It can be abbreviated as INI.

Syntax


profile Name of the profile you want to initialize in the Sysplex. The profile is initialized on the current MVS system only and does not participate in the Sysplex.

plexname Name of the Sysplex definition you want to initialize on a specific MVS system or on all MVS systems specified in the Sysplex definition. Using the PLEX= keyword forces the RSM to consider the name as a plexname instead of a profile name and to include the associated profile in the Sysplex.

If you attempt to use the PLEX= keyword on an MVS system that does not support a Sysplex, you will receive a KAO09057 error message.

In order to initialize a profile that is global to all MVS systems defined to a Sysplex, you must use PLEX=plexname. Otherwise, the profile is initialized locally to the current MVS system only, and status information cannot be obtained by RSMs running on other MVSs in the Sysplex.

WARM (default) Requests that checkpoint information be considered during profile initialization by performing two checks to ensure that:

1. The last profile active in this AF/OPERATOR address space matches the current profile name

2. All required checkpoint information is available

If both checks are successful, the WARM start continues. If either of these checks fail, the profile is started COLD and error message KAO01018 is displayed.n If scheduling is disabled, the resource is brought back to its most recent

desired state.n An Always Active resource is started only if scheduling is enabled for that

resource.

COLD Requests a clean initialization of the profile that ignores checkpoint information. Always Active resources are started or stopped based on their defined Always Active specification.

COLD

rcf INITIATE ><profile

plex=plexname

WARM NOSCHED SMF=smfid


INITIATE

Examples

NOSCHED (optional) Indicates that the scheduler is to be disabled while initializing the profile. Whenever this option is used, scheduled resources are not acted on by the RSM during profile initialization.

Note: This option overrides checkpointed settings for resources to be scheduled. You can activate the schedule at any time after profile initialization by using the RCF ACTIVATE or RCF SCHEDULE command.

For more information on starting the scheduler, See “Starting the Scheduler” on page 116.

smfid Name of a single SMF ID or an SMF ID wildcard mask. The keyword SMFID= can be abbreviated as S=,SM=,SMF=, or SMFI=. The default is SMFID=*. smfid can be used only with PLEXNAME=. It does not apply to the resource parameter.

RCF INITIATE PROF01 WARM

initializes PROF01 on the current MVS system in WARM mode.

RCF INITIATE PLEX=PLEX01 COLD

initializes plexname PLEX01 on the current MVS system in COLD mode.

RCF INITIATE PLEX=PLEX01 S=SYSA

initializes plexname PLEX01 on the MVS system named SYSA in WARM mode.

RCF INITIATE PLEX=PLEX01 S=*

initializes plexname PLEX01 on all MVS systems specified in PLEX01 in WARM mode

RCF INIT PLEX=PLEX01 NOSCHED S=*

initializes plexname PLEX01 on all MVS systems specified in PLEX01, in WARM mode, with the scheduler disabled

INITIATE


Starting the SchedulerDuring a COLD or WARM initialization of a profile, the following Write-To-Operator-With-Reply (WTOR) message is displayed:

KAO08000 AF/OPERATOR Resource Manager Reply with Scheduler

Startup Option (NOW, OK, datetime, HELP)

The user response determines how the scheduler handles each resource during initialization:

n If the response is OK, the Resource Manager works out a schedule for each resource based on the most recent event for the resource according to the defined schedule. Note that if schedule definitions contain no scheduled START or STOP activities during the previous week, scheduled status cannot be determined.

n If the response is NOW, no scheduled status is determined for each resource since the schedule definitions are not be checked for any events that were scheduled to occur before the current time.

n If the response is datetime, the Resource Manager determines a current scheduled status for each resource based on the most recent START or STOP event in the schedule definitions that would have occurred since the datetime.


LIST

LIST

DescriptionThe LIST command allows you to display the current Global Preference values or an updated list of future scheduled events for today. It can be abbreviated as L.

Syntax


GLOBALS Lists the Global Preference values.

SCHEDULE Lists the START, STOP, and TRAPG events that are scheduled for a future time today. You can optionally specify a value nn. Specifying nn restricts the schedule display to nn hours into the future. This is illustrated in the third example below.


rcf LIST GLOBAL SMF=smfid ><

SCHEDULE

nn

LIST


ExamplesList Global Preference settings:

Entering RCF LIST GLOBALS results in the following display:

List all future scheduled events for today:

Entering RCF LIST SCHEDULE S=SYSG results in the following display:

List future events scheduled for the next 3 hours today:

Entering RCF LIST SCHEDULE 03 S=SYSG results in the following display:

====== CURRENT GLOBAL PREFERENCE SETTINGS ==V320 WTOR Timeout Value 5 Message Destination WTO RCF Override Sched NO Failure Messages YES TPUT NO Confirm Msgs at Init NO Scheduler Activated YES================================================

SYSG==== SCHEDULED EVENTS FOR THE CURRENT PERIOD ==== Date Time Resource Action Qualifier11/07/00 11:00:00 AFOG140 STOP AFOG141 STOP AFOG142 STOP11/07/00 12:00:00 AFOG143 STOP Next Scheduled Event: 11/07/00 11:00:00=====================================================

SYSG==== SCHEDULED EVENTS FOR THE NEXT 03 HOURS ===== Date Time Resource Action Qualifier11/07/00 11:00:00 AFOG140 STOP AFOG141 STOP AFOG142 STOP11/07/00 12:00:00 AFOG143 STOP Next Scheduled Event: 11/07/00 11:00:00=====================================================


MONITOR

MONITOR

DescriptionThe MONITOR command enables recovery processing as defined for the selected resources. The command can be abbreviated as MON. If the resources are already in a started state, that is, active, then recovery traps are added. The MONITOR command yields the same results as issuing:

rcf RECOVERY resource YES

Syntax

Examples





RCF MONITOR VTAM

enables recovery processing for a single resource named VTAM

RCF MONITOR GROUP=IPL

enables recovery processing for all resources belonging to the IPL group

RCF MONITOR CICS*

enables recovery processing for all resources with names beginning with CICS

RCF MONITOR TCPIP S=*

enables recovery processing for resource name TCPIP on all systems within the Sysplex.

rcf MONITOR resource SMF=smfid ><

GROUP=groupname

NOMONITOR


NOMONITOR

DescriptionThe NOMONITOR command disables recovery processing as defined for the selected resources. The command can be abbreviated as NOM. If the resources are already in a started state, that is, active, then recovery traps are deleted. Subsequent starts for the selected resources do not enable recovery traps.

The MONITOR command yields the same results as issuing:

rcf RECOVERY resource NO

Syntax

Examples





RCF NOMONITOR VTAM

enables recovery processing for a single resource named VTAM

RCF NOMONITOR GROUP=IPL

enables recovery processing for all resources belonging to the IPL group

RCF NOMONITOR CICS*

enables recovery processing for all resources with names beginning with CICS

RCF NOMONITOR TCPIP S=*

enables recovery processing for resource name TCPIP on all systems within the Sysplex.

rcf NOMONITOR resource SMF=smfid ><

GROUP=groupname


PREDECESSOR

PREDECESSOR

DescriptionThe PREDECESSOR command displays a report showing evrery predecessor for the selected resources. In the right-hand corner of the first heading line on each report is a value for either the SYSTEM or SYSPLEX to indicate how the profile was initiated.

Syntax

ExamplesEntering

RCF PREDECESSOR * displays the following report:





rcf PREDECESSOR resource SMF=smfid ><

GROUP=groupname

Profile:PROF02 PREDECESSOR LISTING SYSPLEXResource Group Smfid Predecessor Group Smfid------------ ------------ ----- ------------ ------------ -----JES2 IPL SYSAVTAM IPL SYSA JES2 IPL SYSATCPIP IPL SYSA VTAM IPL SYSANCP IPL SYSA VTAM IPL SYSA TCPIP IPL SYSA *** End of List ***

PREDECESSOR


The information in the fields on the report consists of:

Field Name Description

Resource Resource name

Group Defined group name

Smfid The smfid of the MVS system where the resource is running

Predecessor Name of a predecessor resource

Group Defined group name of the predecessor resource

Smfid The smfid of MVS system where the predecessor is to run


PURGE

PURGE

DescriptionThe PURGE command allows you to remove pending START and STOP commands from the active wait queue. The command can be abbreviated PU.

You should always issue a SHOW * WAIT command to display the contents of the active wait queue before issuing a PURGE command. This ensures that you are aware of pending START or STOP requests prior to purging them.

Syntax

Examples





RCF PURGE CICS* S=*

removes any pending START or STOP commands from the active wait queue for resources whose names begin with CICS and who are targeted for any MVS system.

RCF PURGE GROUP=DE

removes any pending START or STOP commands from the active wait queue for resources belonging to the DE group.

RCF PURGE CICS1

removes any pending START or STOP commands from the active wait queue for resource name CICS1

rcf PURGE resource SMF=smfid ><

GROUP=groupname

RECOVERY


RECOVERY

DescriptionThe RECOVERY command controls recovery processing for the selected resources. The command can be abbreviated REC.

Syntax

Examples




YES Enables recovery processing. If the actual state of the resource is START, recovery traps are added. YES is the default.

NO Disables recovery processing. If the actual state of the resource is START, recovery traps are deleted. If the resources are subsequently started, recovery traps will not be added.


RCF RECOVERY VTAM YES

activates recovery for a single resource named VTAM

RCF RECOVERY GROUP=IPL NO

deactivates recovery for all resources belonging to the IPL group

RCF RECOVERY CICS* YES

activates recovery for all resources with names beginning with CICS

NO

rcf RECOVERY ><resource

GROUP=groupname

YES SMF=smfid


REFRESH

REFRESH

DescriptionThe REFRESH command recycles the current active profile and picks up the most recent copy of the schedule from disk. The command can be abbreviated REF.

Syntax

Examples

rcf RCF Command Prefix

profile Name of the current active profile

FORCE (default) Initiates a refresh of the current profile immediately. In-flight activities are immediately cancelled.


RCF REFRESH *

refreshes the current profile immediately

RCF REFRESH PROF01

refreshes the current profile (PROF01).

RCF REFRESH * S=*

refreshes the current profile on all MVS systems within the Sysplex immediately.

rcf REFRESH ><profile FORCE SMF=smfid

RESET


RESET

DescriptionThe RESET command enables resources that were disabled by error recovery or by an RCF DISABLE command. The command can be abbreviated RES.

Syntax

Examples




YES Enables the resource and its schedule. Then sets the desired state of the resource to its current scheduled activity. YES is the default.

NO Enables the resource but disables its schedule. Leaves the resource in its current actual state and takes no further action.

NEXT Enables the resource and its schedule. Then sets the desired state of the resource to its next scheduled activity relative to the current date and time.

Note: You may want to issue the RCF LIST SCHEDULE command to determine the next scheduled activity.


RCF RESET VTAM YES

resets the single resource named VTAM

RCF RESET GROUP=IPL NO

resets all resources belonging to the IPL group

RCF RESET CICS* NEXT S=*

resets all resources with names beginning with CICS on every MVS system in the Sysplex.

NO

rcf RESET ><resource

GROUP=groupname

YES SMF=smfid

NEXT


SCHEDULE

SCHEDULE

DescriptionThe SCHEDULE command controls the scheduler for the named resources. The command can be abbreviated SC.

Syntax

Examples




YES Enables the scheduler and then sets the desired state of the resource to its current scheduled activity.

NO Disables the schedule. Leaves the resource in its current actual state and takes no further action.

NEXT Enables the scheduler and then sets the desired state of the resource to its next scheduled activity relative to the current date and time. NEXT is the default.

Note: You may want to issue the RCF LIST SCHEDULE command to determine the next scheduled activity.


RCF SCHEDULE VTAM YES

enables the schedule for the single resource named VTAM

RCF SCHEDULE GROUP=IPL NO

disables the schedule for all resources belonging to the IPL group

RCF SCHEDULE CICS* NEXT S=*

enables the schedule for all resources with names beginning with CICS on every MVS system in the Sysplex.

NO

rcf SCHEDULE ><resource

GROUP=groupname

YES SMF=smfid

NEXT

SET


SET

DescriptionThe SET command temporarily changes the settings of the Global Preferences for the current active profile. The command can be abbreviated SE.

Note:

n You can use the RCF LIST GLOBALS command to view the current Global Preeference settings.

n The temporary Global Preference settings remain in effect until a profile is initiated or refreshed. At this time the settings are refreshed from disk. Thus, if you are running in a Sysplex environment and you wish to initiate or refresh a profile on a single MVS system, force Global Preferences to be refreshed from disk for all MVS systems using the profile.

n Permanent changes to the Global Preferences must be made to the disk-resident copies of these values by means of the user interface.

Syntax


FAILMSG Indicates whether to send a message whenever a resource start or stop activity fails.

YES Issue a message

NO Do not issue a message

MSGDEST Indicates where to send messages.

WTO Send messages to the operator’s console

LOG Send messages to the system log

RCFOVER Indicates whether or not to disable the scheduler for resources that are started or stopped with an RCF command.

YES Disable the scheduler

NO Do not disable the scheduler

FAILMSG

MSGDEST

RCFOVER

TPUT

INITMSG

YES or NO

NO, WARM, or BOTH

YES or NO

YES or NO

WTO or LOG

>< rcf SET

SCHEDACT YES or NO


SET

Examples

TPUT Indicates the way in which responses to RCF commands are issued.

YES Responses are issued as TPUTs.

NO Responses are issued as either WTO or LOG messages depending on what has been specified for the Message Destiniation Global Preference.

INITMSG Determines whether confirmation messages are issued during profile initialization or refresh.

NO Confirmation messages are not issued during profile initialization or refresh.

WARM Confirmation messages are displayed during INITIATE WARM and REFRESH processing for a profile.

BOTH Confirmation messages are displayed during profile initialization, whether COLD, WARM, or REFRESH.

SCHEDACT Detemines whether the scheduler is activated at profile initialization

YES Sceduler is activated

NO Scheduler is diabled during profile initialization

RCF SET FAILMSG YES

issues a message whenever a resource activity fails

RCF SET MSGDEST LOG

sends messages to system log.

RCF SET RCFOVER NO

indicates that RCF commands will not disable the scheduler

RCF SET TPUT YES

issues messages as TPUTs

RCF SET INITMSG BOTH

issues messages during profile initialization (COLD, WARM, and REFRESH)

RCF SET SCHEDACT NO

disables the scheduler during profile initialization

SHOW


SHOW

DescriptionThe SHOW command is used to create a variety of resource status reports. The command can be abbreviated SH. Example reports can be found later in this unit under the heading “Examples”. In the right-hand corner of the first heading line on each report is a value for either the SYSTEM or SYSPLEX to indicate how the profile was initiated.

Syntax




SUMMARY (default) Can be abbreviated SU. Creates a selected resource summary report.

DESIRE Can be abbreviated D. Creates a desired state report for the selected resources.

SCHEDULE Can be abbreviated SC. Creates a report of selected resources scheduled to run today. (Only resources having schedules are displayed on this report.)

RCF Can be abbreviated RC. Creates a report showing the last RCF command issued against the selected resources.

RECOVERY Can be abbreviated RE. Creates a report of the recovery status for the selected resources.

WAIT Can be abbreviated W Displays the contents of the active wait queue for the selected resources.


DESIRE

rcf SHOW ><resource

GROUP=groupname

SUMMARY SMF=smfid

SCHEDULE

RCF

RECOVERY

WAIT


SHOW

Examples

Example of SUMMARY report:The command RCF SHOW * SUMMARY creates the report shown below.


Field name Description



Desired State The current desired state of the resource. The field may be blank or can contain the value START, STOP, or DISABLED. If the field is blank, it indicates that no action has been taken against this resource since the profile was initialized COLD.

Actual State The current actual state of the resource. (The value in this field may not reflect the actual state of the resource if the resource was started or stopped outside of the RSM. Use the RCF CHECK command to determine the actual state.)

Recovery Traps Displays whether recovery traps are (ON) or are not (OFF) in effect.

Recovery Enabled Displays whether recovery processing is enabled (YES) or disabled (NO).

Schedule Active Displays whether the schedule is active (YES) or inactive (NO).

Profile:PROF02 SUMMARY REPORT for Smfid: SYSA SYSPLEXResource Group Desired Actual --Recovery-- ScheduleName State State Traps Enable ActiveJES2 IPL START START OFF NO YESVTAM IPL START START OFF NO YESTCPIP IPL START START OFF NO YESNCP IPL START START OFF NO YES

SHOW


Example of DESIRE report:

The command RCF SHOW GRP=SA DESIRE creates the report shown below.


Example of SCHEDULE report:

The command RCF SHOW GRP=SA SCHEDULE creates the report shown below. Only resources with schedules appear on this report.




Desired State The current desired state of the resource. The field may be blank or can contain the value START, STOP, or DISABLED. If the field is blank, it indicates that no action has been taken against this resource since the profile was initialized COLD.

Action Source SCHED indicates that the most recent action came from the scheduler. RCF indicates that the most recent action came from an RCF command.

Date and Time Date and time that the most recent action was taken.

Flag W Value may be Y or Nn N indicates that no warning messages were defined for the resource.n Y indicates that warning messages were defined for the resource.

Flag F Value may be Y or Nn N indicates that the most recent START or STOP activity was not forced.n Y indicates that the most recent START or STOP activity was forced.

Profile:PROF02 DESIRE REPORT for Smfid: SYSA SYSPLEXResource Group Desired Action ---Date--- --Time-- FlagsName State Source W FCICS1 SA START SCHED 11/08/2000 05:00:00 N NCICS2 SA STOP RCF 11/08/2000 08:09:12 N YPAYROLL SA N NAFREMOTE SA STOP RCF 11/07/2000 20:09:14 N NDB2 SA DISABLED RCF 11/08/2000 10:22:00 N N

Profile:PROF02 SCHEDULE REPORT for Smfid: SYSA SYSPLEXResource Group Desired Action ---Date--- --Time-- FlagsName State Source W FCICS1 SA START SCHED 11/08/2000 05:00:00 N N SA STOP SCHED 11/08/2000 18:00:00 N NCICS2 SA START SCHED 11/08/2000 05:00:00 N N SA STOP SCHED 11/08/2000 18:00:00 N N


SHOW


Example of RCF report:

The command RCF SHOW GRP=SA RCF creates the report shown below.





Desired State Defined (desired) action to be taken on the resource. Values may be START, STOP, or TRAPG.

Action Source SCHED indicates that the action will be initiated by the Scheduler.

Date and Time Date and time that the most recent action was taken.

Flag W Value may be Y or Nn N indicates that no warning messages were defined for the resource.n Y indicates that warning messages were defined for the resource.

Flag F Value may be Y or Nn N indicates that the scheduled START or STOP activity will not be

forcedn Y indicates that the scheduled START or STOP activity will be forced.




Date and Time .Indicates the date and time of the most recent RCF command issued for the resource.

Command The most recent RCF action command to be issued for the resource. (The command shown on this report may not appear in its entirety due to space limitations on the report.)

Profile:PROF02 RCF REPORT for Smfid: SYSA SYSPLEXResource Group ---Date--- --Time-- Command-------------NameCICS1 SACICS2 SA 11/08/2000 08:09:12 STOP CICS2 FORCEPAYROLL SAAFREMOTE SA 11/07/2000 20:09:14 STOP AFREMOTE

SHOW


Example of RECOVERY report:

The command RCF SHOW GRP=SA RECOVERY creates the report shown below. In this example, resource name CICS1 went through recovery processing once at 07:15:23 after trapping message IEF450I.





Date and Time Indicates the date and time of the most recent recovery action for the resource.

Recovery Traps Status of the recovery traps:n ON indicates that recovery traps are active.n OFF indicates that recovery traps are not active.

Recovery Enabled

Indicates whether recovery processing is enabled.n YES indicates that recovery processing is enabled for this resource.n NO indicates that recovery processing is disabled for this resource.

Retry Count N is the number of times that the recovery process has been executed for this resource. When the defined recovery retry limit has been reached, the resource is DISABLED.

WTO TEXT --> The actual text of the message that triggered the most recent recovery process. (The text may appear truncated due to space limitations on the report.)

Profile:PROF02 RECOVERY REPORT for Smfid: SYSA SYSPLEXResource Group ----Last Retry---- --Recovery-- RetryName Date Time Traps Enable CountCICS1 SA 11/08/2000 07:15:23 ON YES 1 WTO TEXT --> IEF450I CICS1 CICS1 - ABEND=S222 U0000 REASON=CICS2 SA OFF NO 0PAYROLL SA OFF NO 0AFREMOTE SA OFF NO 0


SHOW

Example of WAIT report following an RCF start:

The command RCF START GRP=IPL starts resources belonging to group name IPL. The command RCF SHOW * WAIT displays the active wait queue status report.



Smfid The smfid where the resource is waiting

Resource Name of the resource that is waiting.

Activity Activity that is to be executed for this resource (START or STOP).

Waiting on Resources

The resource_name/owning_smfid pairs that represent the predecessors that the resource must wait on to START, or the successors that the resource must wait on to STOP.

Profile:PROF02 WAIT QUEUE STATUS SYSPLEXSmfid Resource Activity Waiting on Resources----- ------------ -------- --------------------SYSA VTAM START JES2\SYSASYSA TCPIP START VTAM\SYSASYSA NCP START TCPIP\SYSA *** End of List ***

START


START

DescriptionThe START command is used to start the selected resources. The command can be abbreviated STAR. If the Global Preference RCFOVER is specified as YES, the schedule is disabled for the selected resources.

Notes:

1. For more information about the RCFOVER Global Preference setting, please refer to the RCF SET command in this chapter. Alternatively, while in the RSM user interface, select Configuration Option 3 (Global Preferences) and display the online help for RCF START/STOP Command overrides Scheduler.

2. If recovery is enabled for the selected resources, then user-defined recovery traps are set automatically during success message processing.

Syntax




PURGE Purge the active wait queue of any queued requests before servicing the current start request. KAO04014 messages are issued for every request purged from the active wait queue. You can use the PURGE option with other options on this command. See the examples.

FORCE Ignore predecessor checking and launch the START request immediately.

INCLUDE Start resources following the successor chain beginning with the specified resource name. Note that you can specify only a single resource name when using this option.

FORCE

rcf START ><resource

GROUP=groupname

PURGE SMF=smfid

INCLUDE

qualifier

ABOVE or BELOW


START

Examples

ABOVE Must be used in conjunction with INCLUDE. Resources are started by following the defined predecessor chain beginning with the specified resource name.

BELOW Must be used in conjunction with INCLUDE. Resources are started by following the defined successor chain beginning with the specified resource name.

Qualifier May be either:

1. A user-defined activity qualifier, or

2. A parameter that must be appended to the start activity.

If this is a parameter, it must begin with a comma; (for example: ,PARM=GOTO).


RCF START PAYROLL

starts a single resource named PAYROLL

RCF START GRP=IPL

starts all resources in the IPL group, following the defined predecessor chain

RCF START VTAM INCLUDE BELOW

starts resource named VTAM and every resource linked to it on its successor chain

RCF START NCP INCLUDE ABOVE PURGE

purges any queued request; then starts resource on every MVS system defined in the Sysplex, the following defined predecessor chain

RCF START GRP=* S=* PURGE

purges the entire request queue; then starts every resource on every MVS system defined in the Sysplex, following defined predecessor chains

RCF START PAYROLL , PARM=1

starts the resource named PAYROLL and appends the parameter Parm=1 to the start activity

Defined activity: S PAYJOB

Launched activity: S PAYJOB,PARM=1

RCF START NCP NODATA S=SYSB

locates the activity qualifier named NODATA for resource name NCP; then launches the defined start activity on SYSB of the Sysplex

STATUS


STATUS

DescriptionThe STATUS command is used to create a variety of resource status reports. It is an alias for the SHOW command. The command can be abbreviated STAT.

Syntax

ExamplesFor example reports, See “Examples” on page 131.




SUMMARY (default) Can be abbreviated SU. Creates a selected resource summary report.

DESIRE Can be abbreviated D. Creates a desired state report for the selected resources.

SCHEDULE Can be abbreviated SC. Creates a report of selected resources scheduled to run today. (Only resources having schedules are displayed on this report.)

RCF Can be abbreviated RC. Creates a report showing the last RCF command issued against the selected resources.

RECOVERY Can be abbreviated RE. Creates a report of the recovery status for the selected resources.

WAIT Can be abbreviated W Displays the contents of the active wait queue for the selected resources.


DESIRE

rcf STATUS ><resource

GROUP=groupname

SUMMARY SMF=smfid

SCHEDULE

RCF

RECOVERY

WAIT


STOP

STOP

DescriptionThe STOP command is used to stop the selected resources. The command can be abbreviated STO. If the Global Preference RCFOVER is specified as YES, the schedule is disabled for the selected resources.

Note: For more information about the RCFOVER Global Preference setting, please refer to the RCF SET command in this chapter. Alternatively, while in the RSM user interface, select Configuration Option 3 (Global Preferences) and display the online help for RCF START/STOP Command overrides Scheduler.

Syntax




PURGE Purge the active wait queue of any queued requests before servicing the current stop request. KAO04014 messages are issued for every request purged from the active wait queue. You can use the PURGE option with other options on this command. See the examples.

FORCE Ignore predecessor checking and launch the STOP request immediately.

INCLUDE Stop resources following the successor chain beginning with the specified resource name. Note that you can specify only a single resource name when using this option.

FORCE

rcf START ><resource

GROUP=groupname

PURGE SMF=smfid

INCLUDE

qualifier

BELOW

FORCE

rcf STOP ><resource

GROUP=groupname

PURGE SMF=smfid

INCLUDE

qualifier

BELOW

STOP


Examples

BELOW Must be used in conjunction with INCLUDE. Resources are stopped by following the defined successor chain beginning with the specified resource name.

Qualifier May be either:

1. A user-defined activity qualifier, or

2. A parameter that must be appended to the stop activity.

If this is a parameter, it must begin with a comma; (for example: ,PARM=GOTO).


RCF STOP PAYROLL

stops a single resource named PAYROLL

RCF STOP GRP=IPL

stops all resources in the IPL group, following the defined successor chain

RCF STOP VTAM INCLUDE BELOW PURGE

purges the active wait queue; then stops the resource named VTAM and every resource linnked to it on its successor chain

RCF STOP GRP=* S=* PURGE

purges the entire request queue; then stops every resource on every MVS system defined in the Sysplex, following defined predecessor chains

RCF STOP PAYROLL ,PARM=2

stops the resource named PAYROLL and appends the parameter PARM=2 to the start activity

Defined activity: S PAYJOB

Launched activity: S PAYJOB,PARM=2

RCF STOP NCP QUICK S=SYSB

locates the activity qualifier named QUICK for resource name NCP; then launches the defined stop activity on SYSB of the Sysplex


SUCCESSOR

SUCCESSOR

DescriptionThe SUCCESSOR command displays a report showing evrery predecessor for the selected resources. The command can be abbreviated SU. In the right-hand corner of the first heading line on each report is a value for either the SYSTEM or SYSPLEX to indicate how the profile was initiated.

Syntax

ExamplesEntering RCF SUCCESSOR * displays the following report:





rcf SUCCESSOR resource SMF=smfid ><

GROUP=groupname

Profile:PROF02 SUCCESSOR LISTING SYSPLEXResource Group Smfid Successor Group Smfid------------ ------------ ----- ------------ ------------ -----JES2 IPL SYSA VTAM IPL SYSAVTAM IPL SYSA TCPIP IPL SYSA NCP IPL SYSATCPIP IPL SYSA NCP IPL SYSANCP IPL SYSG *** End of List ***

SUCCESSOR






Smfid The smfid of the MVS system where the resource is running

Successor Name of a successor resource

Group Defined group name of the successor resource

Smfid The smfid of MVS system where the successor is currently active.


TERMINATE

TERMINATE

DescriptionThe TERMINATE command terminates the current active profile. It can be abbreviated as TE.

Syntax

Examples


profile Name of the current active profile or an asterisk (*).


RCF TERMINATE *

terminates the current profile immediately

RCF TERMINATE * S=*

terminates the current profile on every MVS system in the Sysplex.

rcf TERMINATE profile SMF=smfid ><

TRAPGROUP


TRAPGROUP

DescriptionThe TRAPGROUP command permits you to request a trap action for all members of a defined trap group. Refer to “Defining Trap Groups” on page nnn for more information on how to define traps and trap groups.

You can define schedules in the user interface in such a way that trap group actions ADD, DEL, ENA, and DIS are performed automatically. The TRAPGROUP command terminates the current active profile. It can be abbreviated as TR.

Syntax


groupname Name of the trap group.

action Can be one of the following:

Add Performs a trap add

DEL Performs a trap delete

ENA Performs a trap enable

DIS Performs a trap disable

SHOW Performs a show trap.


rcf TRAPGROUP groupname action SMF=smfid ><


TRAPGROUP

Examples

RCF TRAPG TGROUP1 ADD

issues a trap add for each trap in the trap group named TGROUP1.

RCF TR TGROUP1 DEL

issues a trap delete for each trap in the trap group named TGROUP1.

RCF TR TGROUP1 SHOW

issues a show trap command for every trap in the trap group named TGROUP1.

:dt.RCF TR TGROUP2 ENA S=*

issues a trap enable for trap defined in trap group named TGROUP2, on every MVS system defined in the Sysplex.

TRAPGROUP


Trap Group Management 147

Trap Group Management

IntroductionThis chapter describes how to use AF/OPERATOR to automate console operations. It describes how to use the Trap Group Manager, and includes representative examples that show how to:

n define traps and extended actions through the AF/OPERATOR user interface

n trap, suppress, and reroute commands

n suppress, reroute, and reword messages

Chapter ContentsAbout Traps -- Before you Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148Working with Trap Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150Adding Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154Example: Defining a Spool Full WTO Trap to Flag Excessive Job Output . . . . . . . . . . . . 158Example:Using a Trap to Start an Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163Example: Defining a Trap to Intercept Unauthorized Printer Commands. . . . . . . . . . . . . 166

5

About Traps -- Before you Begin


About Traps -- Before you BeginBefore going through the scenarios in this chapter, you should be familiar with how traps work and the principles of message management.

A trap is a fundamental and essential element of AF/OPERATOR console management. It is a rule statement that defines how AF/OPERATOR responds to one or more system events, such as messages, commands, OMEGAMON exceptions, or date and time information. If you want actions to be taken based on the events you trap, you should also be familiar with the REXX programming language, since AF/OPERATOR extended action routines are written in REXX.

Trap Group Manager is an AF/OPERATOR tool that automates the process of trapping, suppressing, rerouting, and rewording traps. It allows you to manage groups of traps without having to write the automation programs from scratch.

Trap terminologyThe following terms are used in describing how traps work:

n Defining a trap means using the AF/OPERATOR user interface to write a trap statement and specifying the action you want AF/OPERATOR to take when the event (for example, a change in the environment) occurs. Defining a trap leaves the trap disabled but ready to enable.

n Enabling a trap makes it ready to respond to the event you want to trap.

n The occurrence of the event triggers or fires the trap if you have enabled it.

n A match occurs each time an event triggers a trap.

n Disabling a trap prevents the event from triggering it, but the trap remains defined in AF/OPERATOR.

n Deleting a trap disables it and removes its definition from AF/OPERATOR.

Trap typesThere are four types of traps.

Trap type Description

CMD (Command) Triggered by a command issued from an operator console or other user-defined source (defined using AOSIM). CMD traps respond to operator commands from:n MVS, VTAM, NetView®, JES2, and JES3n multiuser subsystems such as CICS, DB2®, and IMSn the OMEGAMONs for CICS, DB2, IMS, and MVS

TOD (Time of Day) Triggered by a date-time combination. TOD traps respond to time of day, day of week, date, or interval for scheduling and catch-up processing.


About Traps -- Before you Begin

here to find more informationThis chapter provides basic information about and examples of console management. However, it is not a comprehensive source of information on traps, trap group management, or the REXX programming language. For an in-depth treatment of traps, please refer to the following manuals:

n AF/OPERATOR User’s Guide

Explains how the different types of trap work.

n AF/OPERATOR Command Reference

Provides information on AF/OPERATOR variables and pattern matching, and a comprehensive reference of trap commands, parameters, and syntax.

The AF/OPERATOR online Help facility also contains detailed information on the various types of traps and their parameters. To get Help on any panel or entry field, press F1.

If you need to brush up on REXX, review the following IBM references:

n TSO/E REXX/MVS Reference

n TSO/E REXX/MVS User’s Guide

WTO (Write-To-Operator) Triggered by a WTO/WTOR, IMS, JES2, or JES3 message to an operator console, or other user-defined source (defined using AOSIM). WTO traps respond to MVS or subsystem messages issued as WTOs or WTORs, and IMS, JES2, or JES3 messages.

xtype (OMEGAMON exception)

Triggered by an exception from one of the following OMEGAMONs:n OMEGAMON for MVSn OMEGAMON for DB2n OMEGAMON for IMSn OMEGAMON for CICS

Trap type Description

Working with Trap Groups



IntroductionTo use the AF/OPERATOR Trap Group Manager, you must first define Trap Groups and assign traps to those groups. Once defined, you can create schedules for the groups, and if you want, copy trap groups to other profiles. AF/OPERATOR also provides default traps to which you can assign values that can be copied from one trap to the other. The following sections explain how to use the options available in the Trap Group Manager.

Considerations for working with trap groupsThe following lists some considerations you need to be aware of when working with Trap Groups:

n Refreshing the runtime environment updates the shared variables but does not affect the traps that reside in the AF/OPERATOR address space.

n Any changes you make to Trap Groups and traps do not affect the runtime until a refresh is accomplished. You must schedule a Trap Group Delete prior to the refresh so that the traps residing in the AF/OPERATOR address space will be deleted.

n When you define a trap group, AF/OPERATOR creates a resource that is a special type of resource. The activity is always set to TRAPG and you can select the activity qualifier from a list of actions for the trap group. The trap group is then controlled under the RSM using the RCF TRAPG command and can be scheduled using a calendar. For more information about TRAPG actions, See “Creating a schedule for a trap group” on page 152..



Adding trap groupsThis section explains how to add trap groups to AF/OPERATOR.From the Automation pull-down on the AF/OPERATOR Primary Menu, select Traps and press Enter to display the Trap Groups panel.

Note: For information on copying, deleting, or modifying an existing trap group, select the associated option on the Trap Groups panel and press F1 to receive help. For information on copying a trap group to a new profile or scheduling a trap group, see the appropriate sections below.

To add a new Trap Group, type A next to an existing group or select Add from the Actions pull-down and press Enter. AF/OPERATOR displays the Trap Group Add panel.

Complete the fields. Press F1 to receive help for any field. The value you assign to the Sysid field should be identical to the SMFID for the system where RSM resides.

Upon completing this panel, press enter to display the Traps panel.

Actions Help ------------------------------------------------------------------------------ KAOIXTG0 AF/OPERATOR - Trap Groups ROW 1 TO 1 OF 1 Select row(s) and press Enter. Valid selections are: (A)dd, (B)rowse,(D)elete, (E)dit, (M)odify, Copy to (N)ew Profile, (S)chedule. Profile :- KAO001 Trap Group Description Last updated _ TRPGROUP trap group 1997/01/31 09:00:00 _ TRPGROUP1 trap group 1 1997/01/31 10:00:00 _ TRPGROUP2 trap group 2 1997/02/03 10:00:00 ******************************* BOTTOM OF DATA ******************************* Command ===> __________________________________________________________________

.--------------------- Add Trap Groups -----------------------. | KAOIXTG1 AF/OPERATOR - Trap Group Add | | | | Fill in the information, then press Enter. | | | | Group Name TRPGROUP | | | | Description TRAP GROUP | | | | Sysid . . . SYSA + | | | | Calendar . SAMPLE + | | | | | ‘-------------------------------------------------------------’



Creating a schedule for a trap groupThe following procedure describes how to schedule how and when a trap group activity (TRAPG) is invoked.

When defining a schedule, AF/OPERATOR provides a set of four standard qualifiers for the TRAPG activity for Trap Groups. These are:

n ADD

n DELETE

n ENABLE

n DISABLE

On the Traps panel, type S next to the trap group you want to create a schedule for and press Enter to display the Schedule panel.

You can add a new schedule or copy from an existing schedule. See the chapter “Resource Management” on page 47 for more information on schedules. Complete the fields and press Enter. AF/OPERATOR displays the new schedule entries for the trap group on the Schedule panel.

Actions Help------------------------------------------------------------------------------- KAOIXSCO AF/OPERATOR - Schedule ROW 1 FROM 8 Select row(s) and press Enter. Valid selections are: (A)dd, (B)rowse, (C)opy,(D)elete, and (M)odify. TRPGROUP Name : A Calendar Name : SAMPLE Order Daytype Date Time Activity Qualifier _ 1 OFF 08:00:00 START DISABLE _ 2 BUS 08:00:00 START DELETE ******************************* BOTTOM OF DATA ******************************* Command ===> __________________________________________________________________



Copying a trap group to a new profileOnce you create a trap group for one profile, you can copy the trap group and its definitions, such as the current calendar and a list of the trap names defined to the group, to another profile.

You may want to copy the trap group if

n you developed a trap group definition in a test profile that now needs to be moved into the production profile

n you created and tested a trap group definition in one profile that you now want to propagate to other profiles

When you copy a trap group from one profile to another, you must ensure that the trap group (trpgroup) name of the trap group you want to copy does not exist in the target profile. If it does, you will receive a message indicating so and prompting you with several choices.

Follow these instructions to copy the trap group to a new profile.

From the Trap Group panel, type N next to the trap group you wish to copy to a new profile. Press Enter to display the Target Profiles panel. On the Target Profiles panel, type S next to the profile name to which you want to copy and press Enter.

Procedure to copy a trap group to a new profileWhen you have completed your entry on the Target Profiles panel and pressed Enter, AF/OPERATOR displays the Copy TrpGroup to New Profile panel. This panel displays a message indicating whether or not problems occurred during the copy procedure. If the copy was successful, enter Yes to complete the copy.

KAOIXTGH AF/OPERATOR - Copy TrpGroup to New Profile KAOG011V: No Validation errors found for the copy of TrpGroup TRPGRP to the target Profile KAO001 OK to continue the copy? Enter YES to continue copy of TrpGroup TRPGRP Enter ALL to continue copy of ALL selected TrpGroups (Only If No Error Enter NO_ to discontinue copy of TrpGroup TRPGRP Enter CAN to discontinue copy of ALL selected TrpGroups Option ___

Adding Traps


Adding Traps

IntroductionThis section provides the procedure you can use to add traps.

Copying a default trapWhen you initially create a Trap Group, a default trap entry is built for each trap type (WTO, CMD, TOD, xtype). These trap entries are named $$DFLTxxx, where xxx represents the trap type. You can delete, add, or modify these default entries at any time. When you define or modify a trap based on the default trap, any fields that have been filled in for the default trap will automatically be inherited by the trap being added or modified.

The system identifies these default values on each trap statement by placing the value in braces {}. Whenever default trap entries are added or modified, these default entries are changed automatically for every trap of that type within the group. Once you modify the default trap, you can inherit the values from that trap either by copying the default or by adding a new trap with the trap type defined to be the same as the default.

You can use the Preferences option on the Configuration pull-down to add values to the fields of new traps as they are being created. These values become a permanent part of the newly defined trap and are not automatically updated in the same way as the Trap Group defaults.

Modifying the default trapThe Traps panel shows the seven default traps supplied with AF/OPERATOR. You can modify a default trap, inserting the values you want to copy to other traps. To modify and copy a default trap, continue reading this section.

On the Traps panel, type M next to the default trap type you want to modify. For an expanded display of trap construction, type Y in the Expanded Display field on the Traps panel. To see more information about the expanded display information for a trap, press F1.


Adding Traps

When you have completed updating the Traps panel, press Enter to display the Modify Trap panel. Complete the fields, modifying the default trap as you wish and press Enter.

If you selected Y for Extended actions, AF/OPERATOR displays the Extended Actions panel. Complete the fields and press Enter.

If you selected N for Extended actions, or if you have completed the fields on the Extended Actions panel, pressing Enter causes AF/OPERATOR to display the panel for the trap type (CMD, WTO, TOD, or xtype) you modified.

Complete the appropriate fields on the panel for a specific trap type and press Enter. AF/OPERATOR redisplays the Traps panel, showing the default trap with its modified entries.

Note: AF/OPERATOR automatically provides a terminating asterisk (*) on the end of the message pattern. If you supply one yourself, then you will see two (**) asterisks at the

Actions Help ------------------------------------------------------------------------------ KAOIXEV0 AF/OPERATOR - Traps ROW 29 Select row(s) and press Enter. Valid selections are: (A)dd, (B)rowse, (C)opy,(D)elete, and (M)odify. Profile . . . : KAO001 Trap Group . : TRPGROUP1 Expanded Display? N (Y/N) Trap Name Type SysID Enable Description _ $$DFLTCMD CMD Default values for CMD* _ $$DFLTTOD TOD Default values for TOD* _ $$DFLTWTO WTO Default values for WTO* _ $$DFLTXOC XOC Default values for XOC* _ $$DFLTXOI XOI Default values for XOI* _ $$DFLTXOM XOM Default values for XOM* _ $$DFLTXO2 XO2 Default values for XO2* ******************************* BOTTOM OF DATA ******************************* Command ===> __________________________________________________________________

+-------------------------------Modify Trap ---------------------------+| KAOIXEV2 AF/OPERATOR - Version 250 - Traps || || Profile . . . : KAO001 Trap Group . : TRPGROUP1 || --------------------------------------------------------------------|| Trap Name . . . . . . . . ________________________ || Trap Type . . . . . . . . CMD + || Trap Description . . . . Default values for CMD’s || System Id/Pattern . . . . __________ + || Initialize Enabled . . . ___ (Y/N) || AOTRAP . . . . . . . . . ___ (Y/N) See warning about use of AOTRAP.|| Test Mode . . . . . . . . ___ (Y/N) || Extended Actions . . . . ___ (Y/N) || || Note: Any fields inclosed in braces “{}” are inherited Group defaults|| KAOG010P - Row copied and ready for modification. |+----------------------------------------------------------------------+

Adding Traps


end of the message. Two asterisks do not indicate any type of error on the message pattern.

Copying the modified default trapNow you can create new traps based on the modified default trap. On the Traps panel, type C next to the name of the default trap you want to copy and press Enter to display the Add Traps panel.

Type the new trap name in the the Trap Name field, select the trap type, and press Enter. Any field value enclosed in brackets {} indicates that the value is inherited from the default trap. You can accept the inherited values or assign specific values to other fields that you want to use for this trap. Accept or complete the fields on each panel and press Enter to redisplay the Traps panel.

+-------------------------------Add Traps -----------------------------+| KAOIXEV6 AF/OPERATOR - Version 250 - Traps || || Profile . . . : KAO001 Trap Group . : TRPGROUP1 || --------------------------------------------------------------------|| Trap Name . . . . . . . . DFLTCOPY________________ || Trap Type . . . . . . . . CMD + || Trap Description . . . . Default values for CMD’s || System Id/Pattern . . . . {CPU01}____ + || Initialize Enabled . . . {Y} (Y/N) || AOTRAP . . . . . . . . . ___ (Y/N) See warning about use of AOTRAP.|| Test Mode . . . . . . . . ___ (Y/N) || Extended Actions . . . . Y__ (Y/N) || || Note: Any fields inclosed in braces “{}” are inherited Group defaults|| KAOG010P - Row copied and ready for modification. |+----------------------------------------------------------------------+


Adding Traps

The Traps panel shows the copied trap, DFLTCOPY, on the list. Notice the brackets {} surrounding the values inherited from the default trap.

Actions Help ------------------------------------------------------------------------------ KAOIXEV0 AF/OPERATOR - Traps ROW 29 Select row(s) and press Enter. Valid selections are: (A)dd, (B)rowse, (C)opy,(D)elete, and (M)odify. Profile . . . : KAO001 Trap Group . : TRPGROUP1 Expanded Display? N (Y/N) Trap Name Type SysID Enable Description _ $$DFLTCMD CMD CPU01 Y Default values for CMD* _ $$DFLTTOD TOD Default values for TOD* _ $$DFLTWTO WTO Default values for WTO* _ $$DFLTXOC XOC Default values for XOC* _ $$DFLTXOI XOI Default values for XOI* _ $$DFLTXOM XOM Default values for XOM* _ $$DFLTXO2 XO2 Default values for XO2* _ DFLTCOPY CMD {CPU01} {Y} Default values for CMD* ******************************* BOTTOM OF DATA ******************************* Command ===>__________________________________________________________________

Example: Defining a Spool Full WTO Trap to Flag Excessive Job Output



IntroductionThis example is designed to familiarize you with the main features of the AF/OPERATOR trap facility. It shows you how to set up a trap that notifies an operator of a spool full condition (one in which the output of a job is excessive).

Solution stepsTo deal with this problem, you need to:

1. Access the AF/OPERATOR Trap Group Manager.

2. Build a WTO trap that fires when the JES2 spool full message appears.

3. Define the warning message you want sent to the console.

4. Specify the number of times you want the trap to fire before the warning message is transmitted.

5. Add the trap to the system and enable it.These steps are covered in the following scenario.

Adding a spool full WTO trapFrom the Trap Group Manager, access the Traps panel. On that panel, type A next to any trap and press Enter to display the Add Traps panel..

+------------------------------ Add Traps------------------------------+| KAOIXEV1 AF/Operator - Version 250 - Traps || || Profile . . . : KAO001 Trap Group . : TRPGROUP1 || --------------------------------------------------------------------|| Trap Name . . . . . . . . ________ || Trap Type . . . . . . . . ___ + || Trap Description . . . . ________________________________________ || System Id/Pattern . . . . * || Initialize Enabled . . . (Y/N) || AF/Operator Trap . . . . (Y/N) Use caution when selecting this || field. || Test Mode . . . . . . . . (Y/N) || Extended Actions . . . . (Y/N) || || Row initialized and ready for data entry. |+----------------------------------------------------------------------+



In the panel below, you have defined a spool full WTO trap named WSPOOL. The trap can be triggered only on system A. When it fires, an extended action will be taken (as indicated by the Y in the last field).

Specify any extended actionsTo accept the defaults, leave the field values as they are and press Enter. Because you specified Y in the Extended Action field, AF/OPERATOR displays the Trap Extended Actions panel. Use the Trap Extended Actions panel to specify the actions you want taken when the trap fires.

+-------------------------------Add Traps-------------------------------+| KAOIXEV1 AF/Operator - Version 250 - Traps || || Profile . . . : KAO001 Trap Group . : TRPGROUP1 || -------------------------------------------------------------------- || || Trap Name . . . . . . . . WSPOOL_ || Trap Type . . . . . . . . WTO + || Trap Description . . . . Traps spool full message________________ || System Id/Pattern . . . . A || Initialize Enabled . . . N (Y/N) || AOTRAP . . . . . . . . . N (Y/N) See warning about use of AOTRAP. || Test Mode . . . . . . . . N (Y/N) || Extended Actions . . . . Y (Y/N) || || Row initialized and ready for data entry. |+-----------------------------------------------------------------------+

+------------------------------ Add Traps-------------------------------+| KAOIXEV4 AF/Operator - Version 250 - Trap Extended Actions || || Action ... (128 Characters) . . . . . : || ________________________________________________________________ || ________________________________________________________________ || Alternate Action ... (128 Characters) : || ________________________________________________________________ || ________________________________________________________________ || Do Alternate Action every . . . . . . . ___ times. || || |+-----------------------------------------------------------------------+



Define the WTO messageTo send an operator warning message when the excessive output condition occurs 8 times in a row:

1. Type WTO ‘Spool full problem on System A’ in the Alternate Action field.

2. Type 8 in the Do Alternate Action every field.

3. Press enter.AF/OPERATOR displays the WTO Trap panel.

This panel allows you to qualify the trap’s operation. For example, you can selectively trap messages originating from certain job names or classes, or ones with certain descriptor or route codes. You can also suppress the trapped message from being passed on to another application or MVS.

Type the following message text in the Message Pattern field. You can use an asterisk (*) as a wildcard character in your message patterns.

$HASP375*

This pattern traps the JES2 excessive job output message.

In the WeekDays field, type X. By selecting this field, you are causing the excessive output trap to fire on Monday through Friday only.

+--------------------------------- Add Traps---------------------------------+| KAOIXEW1 AF/Operator - Version 250 - WTO Trap || || Message Pattern ... (128 Characters) . : || ________________________________________________________________ || ________________________________________________________________ || Suppress Message . . . . N (Y/N) || Job Name . . . ________ || Job Classes . . __________________________________________________ || (Separate by blanks or commas) || Descriptor || Codes . . . . . __________________________________________________ || (Separate by blanks or commas) || Route Codes . . __________________________________________________ || (Separate by blanks or commas, or n:n, or n-n) || || For the following fields enter a “X” or leave blank. || Job Types: IMS . _ Batch . . _ Tasks . . _ TSO Users _ || Run on: Mondays . . _ Tuesdays . _ Wednesdays _ || . . . Thursdays . . _ Fridays . . _ Saturdays . _ || . . . . Sundays . . _ WeekDays . _ WeekEnds . _ || || |+----------------------------------------------------------------------------+



The panel should appear as shown here. When you’re finished, press Enter.

Change route and descriptor codes for the WTO messagePressing enter causes AF/OPERATOR to display the next WTO Trap panel. This panel allows you to change route code (which console) or descriptor code (which combination of attributes) for the rerouted message. See the IBM Initialization and Tuning Guide for attribute definitions.

To accept the route and descriptor codes currently defined in the startup Message Processing Facility (MPF) list, leave the fields on this panel blank and press Enter to display the next WTO Trap panel.

+--------------------------------- Add Traps---------------------------------+| KAOIXEW1 AF/Operator - Version 250 - WTO Trap || || Message Pattern ... (128 Characters) . : || $HASP375*_______________________________________________________ || ________________________________________________________________ || Suppress Message . . . . N (Y/N) || Job Name . . . ________ || Job Classes . . __________________________________________________ || (Separate by blanks or commas) || Descriptor || Codes . . . . . __________________________________________________ || (Separate by blanks or commas) || Route Codes . . __________________________________________________ || (Separate by blanks or commas, or n:n, or n-n) || || For the following fields enter a “X” or leave blank. || Job Types: IMS . _ Batch . . _ Tasks . . _ TSO Users _ || Run on: Mondays . . _ Tuesdays . _ Wednesdays _ || . . . Thursdays . . _ Fridays . . _ Saturdays . _ || . . . . Sundays . . _ WeekDays . X WeekEnds . _ || || |+----------------------------------------------------------------------------+

+--------------------------------- Add Traps---------------------------------+| KAOIXEW2 AF/Operator - Version 250 - WTO Trap || || Append or Replace Descriptor Codes . . . _ (A/R) || New Descriptors . R2 || (Separate by blanks or commas) || Append or Replace Route Codes . . . . . _ (A/R) || Route Codes . . . __________________________________________________ || (Separate by blanks or commas, or n:n, or n-n) || Delete Descriptors __________________________________________________ || (Separate by blanks or commas) || Delete Route Codes __________________________________________________ || (Separate by blanks or commas, or n:n, or n-n) || || || |+----------------------------------------------------------------------------+



Complete additional trap optionsThis panel provides a number of trap options, including ones to log the firing of the trap, change specific attributes of the rerouted message, and specify the consoles to which you want the message sent.

When you have finished, press Enter. AF/OPERATOR now redisplays the Traps panel with your new trap, WSPOOL, included in the list.

+--------------------------------- Add Traps---------------------------------+| KAOIXEW3 AF/Operator - Version 250 - WTO Trap || || Log in Message Log . Y (Y/N) || Retain in RETAIN*VIEW N (Y/N) || New System . . . . . ________ (MSMF Required) || Address Space ID . . ____ || Trap Continue . . . . N (Y/N) || Hardcopy Log . . . . N (Y/N) || Message Color . . . . YELLOW (BLUE,RED,GREEN,PINK,YELLOW,TURQ,WHITE) || Message Highlighting _________ (NONE,BLINK,UNDERLINE,RVIDEO) || Message Intensity . . HIGH (NORMAL,HIGH) || Link Trigger . . . . ________ (Blank,’*’, or Link ID) || User ID Pattern . . . ____ || Issuing User . . . . ________ (RACF Systems Only) || New Console IDs __________________________________________________ || (Separate by blanks or commas) || || || |+----------------------------------------------------------------------------+


Example:Using a Trap to Start an Application


IntroductionYou can use an AF/OPERATOR time-of-day (TOD) trap to start, stop, affect the functioning of, or poll any application or ongoing system activity. A TOD trap executes whenever a predefined date-and-time combination and/or time interval occurs. TOD traps enable AF/OPERATOR to execute commands or REXX execs that affect any data center resource based on a specified time.

Once you have set up your resource management schedules, you can use TOD traps for one-time exceptions to the schedule. Here is one situation where such a combination of resource schedule and TOD trap might be extremely useful:

1. You have set up resource management schedules so that CICS will start every day at 6 a.m. and stop every day at 11 p.m.

2. One afternoon you receive a call from the manager in charge of the CICS application, requesting that you start CICS the next day at 4 a.m. for special processing.

3. Rather than leaving a note asking the night operator to start CICS early, you want to set up CICS now to start automatically at 4 a.m. tomorrow. That way no one will forget, CICS will start as requested, and the manager will be happy.You don’t want to have to change your resource schedule and refresh your entire configuration just for this one-time request. The solution is to set up a TOD trap that will fire at 4 a.m. the next morning. The trap can issue an RCF command to start CICS. A second trap can then return control of CICS to the resource management schedule. The following section explains how to define such a trap.



Defining a TOD trapTo define a new TOD trap, follow this scenario.

From the Trap Group Manager, access the Traps panel. Type A next to any trap, and press Enter to display the Add Traps panel.

Define your trap by completing the Add Traps panel. For the CICS startup trap, complete the fields in this panel so they appear as follows:

You have now defined a TOD trap named CICSSTRT. The trap can be triggered only on system A. When it fires, an extended action (an RCF command to start CICS) will be taken.

What happens when the trap fires?Use the Trap Extended Actions panel to specify the actions you want taken when the trap fires. In this example, the action is execution of an RCF command:

RCF START CICS

+------------------------------ Add Traps------------------------------+| KAOIXEV1 AF/Operator - Version 250 - Traps || || Profile . . . : KAO001 Trap Group . : TRPGROUP1 || --------------------------------------------------------------------|| || Trap Name . . . . . . . . CICSSTRT || Trap Type . . . . . . . . TOD + || Trap Description . . . . Starts CICSA at 4 a.m.__________________ || System Id/Pattern . . . . A || Initialize Enabled . . . N (Y/N) || AOTRAP . . . . . . . . . N (Y/N) See warning about use of AOTRAP. || Test Mode . . . . . . . . N (Y/N) || Extended Actions . . . . Y (Y/N) || || Row initialized and ready for data entry. |+----------------------------------------------------------------------+

+------------------------------- Add Traps------------------------------+| KAOIXEV4 AF/Operator - Version 250 - Trap Extended Actions || || Action ... (128 Characters) . . . . . : || RCF START CICS__________________________________________________ || ________________________________________________________________ || Alternate Action ... (128 Characters) : || ________________________________________________________________ || ________________________________________________________________ || Do Alternate Action every . . . . . . . ___ times. || || |+-----------------------------------------------------------------------+



After completing the Trap Extended Actions panel, press Enter to display the TOD Trap panel. Use this panel to set the key parameters for a TOD trap.

In the Trap Fire Time field, type the following value:

04:00:00

This sets the trap to fire at 4 a.m. Leave the remaining fields blank, so that the trap will fire only once.

When you have completed the Time of Day Trap panel, press Enter to return to the Traps panel. AF/OPERATOR redisplays the Traps panel with your new trap, CICSSTRT, included in the list.

+--------------------------------- Add Traps---------------------------------+| KAOIXET1 AF/OPERATOR - Version 250 - Time of Day Trap || || Trap Fire Time . . . . . * (hh:mm:ss or ‘*’) || Catch Up Limit . . . . . ___ (Blank, or 1 to 999) || Log in Message Log . . . Y (Y/N) || Checkpoint . . . . . . . N (Y/N) || Interval . . . . . . . . ________ (hh:mm:ss or seconds) || || For the following fields enter a “X” or leave blank. || Job Types: IMS . _ Batch . . _ Tasks . . _ TSO Users _ || Run on: Mondays . . _ Tuesdays . _ Wednesdays _ || . . . Thursdays . . _ Fridays . . _ Saturdays . _ || . . . . Sundays . . _ WeekDays . _ WeekEnds . _ || || |+----------------------------------------------------------------------------+

Example: Defining a Trap to Intercept Unauthorized Printer Commands



IntroductionAn important feature of AF/OPERATOR is its ability to trap unauthorized commands and prevent them from disrupting system operation. The following sections show an example of this feature. They illustrate how to set up a command trap that fires when unauthorized printer commands are issued.

The trap you will build invokes a REXX exec that allows printer commands to be issued only from a designated console. If some other console issues the command, a message is returned and the command is not executed.

Defining a command trapTo define a new command trap, follow this procedure.

From the Trap Group Manager, access the Traps panel. Type A next to any trap and press Enter to display the Add Traps panel.

Define your trap by completing the Copy Trap panel. For the printer authorization trap, complete the fields so they appear as follows:

You have defined a command trap named PRTAUTH, which can be triggered on any system (indicated by an asterisk in the System Id/Pattern field). When the trap fires, an extended action occurs: invocation of a REXX exec that determines the console from which the command was issued.

Because you have specified a Y in the Extended Actions field, AF/OPERATOR displays the Trap Extended Actions panel. In the Action field of the Trap Extended Actions panel, type:

EX PRTAUTH

+------------------------------- Add Traps------------------------------+| KAOIXEV1 AF/Operator - Version 250 - Traps || || Profile . . . : KAO001 Trap Group . : TRPGROUP1 || -------------------------------------------------------------------- || Trap Name . . . . . . . . PRTAUTH || Trap Type . . . . . . . . CMD + || Trap Description . . . . Printer authorization check_____________ || System Id/Pattern . . . . * || Initialize Enabled . . . N (Y/N) || AOTRAP . . . . . . . . . N (Y/N) See warning about use of AOTRAP. || Test Mode . . . . . . . . N (Y/N) || Extended Actions . . . . Y (Y/N) || || Row initialized and ready for data entry. |+-----------------------------------------------------------------------+



Specifying the commands to trapPress enter to display the Command Trap panel.

Use this panel to specify the command or group of commands to trap. The panel also contains options that allow you to qualify the operation of the trap, by:

n suppressing the command from being processed by MVS or other applications

n only trapping commands originating from certain address spaces, consoles, job names, or job classes

n specifying which days of the week you want the trap to be operational

Enter the following command text in the Command Pattern field to trap any JES2 printer commands:

$*PRT*

In the Suppress Command field, type Y to prevent additional processing of the command by other applications or by MVS.

Now press Enter to redisplay the Traps panel with your new trap, PRTAUTH, included in the list.

+-------------------------------- Add Traps---------------------------- -----+| KAOIXEC1 AF/OPERATOR - Version 250 - Command Trap || || Command Pattern ... (128 Characters) . : || ________________________________________________________________ || ________________________________________________________________ || Suppress Command . . . . N (Y/N) || Retain in RETAIN*VIEW . . N (Y/N) || Task Continues . . . . . N (Y/N) || Address Space ID . . . . ____ || Job Name . . . ________ || Job Classes . . __________________________________________________ || (Separate by blanks or commas) || Console IDs . . __________________________________________________ || (Separate by blanks or commas) || || For the following fields enter a “X” or leave blank. || Job Types: IMS . _ Batch . . _ Tasks . . _ TSO Users _ || Run on: Mondays . . _ Tuesdays . _ Wednesdays _ || . . . Thursdays . . _ Fridays . . _ Saturdays . _ || . . . . Sundays . . _ WeekDays . _ WeekEnds . _ || || |+----------------------------------------------------------------------------+



Building the PDS member PRTAUTHThe final step is to build a PDS member named PRTAUTH, containing the REXX exec invoked by the trap. The exec looks for the AF/OPERATOR variable AOCONS. If its value is 0, the printer command is allowed. If the value is anything else, the command is disallowed and a WTO is issued. One possible way of coding the exec is shown here.

For information on using AF/OPERATOR variables and commands to write REXX execs, see the AF/OPERATOR Command Reference Manual.

/* REXX PRTAUTH - Printer Command Authorization*/ r_c = GLBVGET(‘AOCONS’) If AOCONS = ‘0’ Then Do /* Allow command to be issued */ r_c = GLBVGET(‘AOTEXT’) “OPER ‘”AOTEXT”’” EndElse Do “WTO ‘Not authorized to issue this command.’ Console(“AOCONS”)” EndReturn

Using the AF/OPERATOR Sysplex Console to Access Members of a Sysplex 169

Using the AF/OPERATOR SysplexConsole to Access Members

of a Sysplex

IntroductionThis chapter describes the use of the Sysplex Console under AF/OPERATOR.

Chapter ContentsWhat is the Sysplex Console? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170Set-up Requirements to Use Sysplex Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171Examples of the Use of Sysplex Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173Issuing Commands—Some Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

6

What is the Sysplex Console?


What is the Sysplex Console?

IntroductionSelecting number 21 (Sysplex Console) on the AF/OPERATOR Primary Menu provides User Interface access, by means of TCP/IP, to MVS systems running in the Sysplex. In order to use the Sysplex Console, AF/OPERATOR must be running on all of the MVS systems defined to the Sysplex.

As a result of selecting option 21, AF/OPERATOR presents you with a list of defined RSM sessions that you can select from in order to establish communication with a member or members of a defined Sysplex.

Configuration Automation Control Tools Help ----------------------------------------------------------------------------- KAOIXMIN AF/OPERATOR - VERSION 320 Command ===> ________________________________________________________________ Select an option from the list below and press Enter, or make a selection from the Action-bar above. Current Profile . . : PROF01 Authorization Group : -DEFAULT- Configuration Automation 1. Profile 11. Calendars 2. Field Preferences 12. Resources 3. Global Preferences 13. Traps 4. Authorization Groups 14. Refresh 5. Notification Groups 6. Systems Control 7. Users 21. Sysplex Console 8. Sysplex 9. TCP Communications F1=Help F3=Exit F10=ActBar


Set-up Requirements to Use Sysplex Console


IntroductionBefore selecting Sysplex Console from the Primary Menu, you must ensure that you have correctly set up your environment by taking the following steps:

1. Add a COMM START command to your AF/OPERATOR startup REXX exec ($$OGINIT).

2. Create a HOSTNAME member in your &hilev.RKANPAR dataset that contains the IP address of the MVs system on which the User Interface is running.

3. Using the User Interface Primary Menu, create TCP/IP Communications Definitions by selecting option 9 (TCP/IP Communications).

Note: After making the changes outlined in steps 1 and 2 above, you must start AF/OPERATOR on the MVS systems participating in the Sysplex. (In the examples that follow in “Issuing Commands—Some Examples” on page 177, the participating systems are SYSA and SYSB.)

Add COMMSTART to &hilev.RKANCMD($$OGINIT)Select the TCP/IP port number of your choice and add a COMM START command to your $$OGINIT startup REXX exec in RKANCMD. (In the example below, the port number is 8889.)

/********************************************************//* AF/OPERATOR (RSM) STARTUP *//********************************************************/ “TRAP DEL(@RAO320)” “TRAP ADD(@RAO320) TOD(*) ENA ACT(‘EX KAORSTRT “, “‘’CANDLE.Q320.RKANISP RCF’’ ‘)” /********************************************************//* START TCP/IP CONNECTION FOR SYSA *//********************************************************/“COMM START PORT(8889)”



Create &hilev.RKANPAR(HOSTNAME)Create a member named HOSTNAME in your hilev.RKANPAR dataset. This dataset should contain the IP address of each MVS system that potentially will use the User Interface to communicate with AF/OPERATOR

Create TCP/IP definitionsFrom the User Interface Primary Menu, select option 9 to define your TCP/IP port numbers to AF/OPERATOR. The Sysplex Console function uses these definitions to communicate with AF/OPERATOR

Note: If you wish, you can use the same port number for multiple MVS systems.

[BEGIN]*SYSA MVS SYSTEMADDRESS=198.210.51.146[END][BEGIN]*SYSB MVS SYSTEMADDRESS=198.210.51.158[END]

Actions Help AF/OPERATOR - TCP Communication Row 1 to 4 of 4 Command ===> ________________________________________ Scroll ===> PAGE Select row(s) and press Enter. Valid selections are: (A)dd, (B)rowse,(D)elete, and (M)odify. HostName Port# Description ___SYSA 8889 TCP port for AF/OPERATOR on SYSA ___SYSB 8889 TCP port for AF/OPERATOR on SYSB


Examples of the Use of Sysplex Console


Selecting the target MVS systemSelecting option 21 (System Console) on the AF/OPERATOR Primary Menu causes AF/OPERATOR to display the Sysplex Automation panel. On that panel, you can select the host system with which you want to establish communication by placing an option such as R, T, or M in front of its name on the resource list.

Depending on which of the three options you selected, AF/OPERATOR connects you to the selected server, but displays a different set of AF/OPERATOR resources:

n R—Resource Manager displays all the resources (started tasks, batch jobs, initiators, printers, tape drives, DASD volumes, databases, files, and datasets) defined in the profile for that system.

n T—Trap Manager displays all the traps (CMD, TOD, WTO, xType) except suppression WTO traps.

n M—WTO Message Manager displays all of the WTO traps.

Automation-Server Help-------------------------------------------------------------------------------- AF/OPERATOR - Sysplex Automation Row 1 to 3 of 3 Command ===> ________________________________________________ Scroll ===> PAGE Select the Automation-Server from the list below, then press Enter. R -Resource Manager T -Trap Manager M -WTO Message Manager HostName Port# Description ___SYSB 8889 SYSB TCP/IP ___TCPTEST 00000 Sample TCP Connection Description ___SYSA 8889 SYSA TCP/IP ******************************* Bottom of data ********************************



Selecting Resource Manager actionsIf you selected a HostName from the list by entering R, AF/OPERATOR presents you with a list of resources that are currently initialized on the target MVS system. From this Resource Manager panel, you can select resource manager actions from the list provided. From the Command line, you can also submit various commands to MVS and AF/OPERATOR or submit various Resource Manager requests using RCF commands.

The next unit provides examples of RCF, MVS, and AF/OPERATOR commands and the results produced.

Resource-Manager Help AF/OPERATOR - Resource Manager Row 1 from 3 Command ===> ________________________________________________ Scroll ===> PAGE Select a Resource with an Action from the list below, then press Enter. S -Start P -Stop A -Activate I -Inactivate C -Check R -Recovery H -Schedule < -Predecessors > -Successors ? -Detail Hostname&colon. SYSA Port#&colon. 8889 Desired Actual --Recovery-- Schedule Resource State State Traps Enable Active * * * ___TASK01 START OFF N Y ___TASK03 START OFF N Y ___TASK05 STOP OFF N Y ******************************* Bottom of data ********************************



Selecting Trap Manager actionsBy selecting a HostName (such as SYSA) from the list using the letter T, AF/OPERATOR presents you with a list of traps that are currently started on the target MVS system. From this Trap Manager panel, you can select trap manager actions from the list provided. From the Command line, you can also submit various commands to MVS and AF/OPERATOR.

Trap-Manager Help------------------------------------------------------------------------------- AF/OPERATOR - Trap Manager Row 1 to 106 Command ===> ________________________________________________ Scroll == PAGE Select a Trap with an Action from the list below, then press Enter. E -Enable B -Disable D -Delete S -Show Hostname: SYSA Port#: 8889 Trap Name Type Status Count Text *_______________________ *___ *___ __ @CX1Q199093525548909 WTO ENA 0 IEF403I * __ @CX1Q199093525549484 TOD ENA 0 TIME=09:45:25 DATE=07/17/2000 __ @CX1Q199093525549484 TOD ENA 0 TIME=09:45:25 DATE=07/17/2000 __ @CX1Q199093529330715 TOD ENA 0 TIME=09:45:29 DATE=07/17/2000 __ @CX1Q199093532009665 WTO ENA 0 +STCSIM01 * __ @CX1Q199093532010111 TOD ENA 0 TIME=09:45:32 DATE=07/17/2000 __ @CX1R199093446361862 WTO ENA 0 IST105I APLOGVG NODE NOW INACTIV __ @CX1S199093508925505 TOD ENA 0 TIME=02:55:00 DATE=07/18/2000 __ MYTRAP WTO ENA 2 TRAP01 ** __ OGSUBSYS CMD ENA 7 O1NF *OGCMD __ RCF14 CMD ENA 1 RCF14 *PARM ******************************* Bottom of data ************************



Seledcting WTO Message Manager actionsBy selecting a HostName (such as SYSA) from the list using the letter M, AF/OPERATOR presents you with a list of WTO traps that are currently started on the target MVS system. From this Trap Manager panel, you can select trap manager actions from the list provided. From the Command line, you can also submit various commands to MVS and AF/OPERATOR.

Message-Manager Help------------------------------------------------------------------------------ AF/OPERATOR - Message Manager Row 1 OF 35 Command ===> ________________________________________________ Scroll == PAGE Select a Message with an Action from the list below, then press Enter. E -Enable B -Disable D -Delete S -Show Hostname: SYSA Port#: 8889 Status Count Message *___ *____________________________________________________________ __ ENA 0 $HASP395 * __ DIS 0 IKJ01234I ** __ ENA 0 IST105I APLOGVG NODE NOW INACTIV __ ENA 0 TIME=09:45:29 DATE=07/17/2000******************************* Bottom of data *************************


Issuing Commands—Some Examples


IntroductionThis unit illustrates the results of entering RCF, MVS, or AF/OPERATOR commands, transmitted using the TCP/IP, to an MVS system within the Sysplex. Note that, each time you enter a command through the Sysplex Console, you receive a pop-up menu requesting that you verify the command you entered before that command is transmitted to the target MVS system. On the pop-up, press Enter to submit the command, or press the Cancel key to return to the previous panel without submitting the command. Some commands may require the entry of additional parameters. You can enter them from this panel when required.

RCF Commands

Successor request

In the example that follows, you have placed the character > in front of TASK01 on the Resource Manager panel. This Resource Manager request asks that AF/OPERATOR display its successor resources. When you have pressed Enter, AF/OPERATOR first presents you with the command-verification pop-up menu:

Pressing Enter to submit the request causes AF/OPERATOR to return the following successor listing:

Resource-Manager Help -----------------------------------------------------------------------| SUCCESSOR TASK01 || AF/OPERATOR - Commands || || || Press Enter to submit the command. || || Command . . : SUCCESSOR TASK01 || || F1=Help F12=Cancel | ----------------------------------------------------------------------- * * * > TASK01 STOP OFF Y Y TASK02 STOP OFF Y Y TASK05 STOP OFF Y Y ******************************* Bottom of data ***********************



Resource Detail request

In this example, you have placed the Resource Manager request ? in front of TASK01 on the resource list of the Resource Manager panel. This requests DETAIL information about the resource. AF/OPERATOR returns the following list of control information used by the RSM to manage the resource.

SUCCESSOR TASK01 AF/OPERATOR - Reports Row 1 to 8 of 8 Command ===> ______________________________________________________________ Profile&colon.PROF01 SUCCESSOR LISTING SYSPLEX Resource Group Smfid Successor Group Smfid ------------ ------------ ----- ------------ ------------ ----- TASK01 FIRST SYSA TASK02 SECOND SYSB TASK05 FIRST SYSA *** End of List *** ***************************** Bottom of data ******************************

DETAIL TASK01 AF/OPERATOR - Reports Row 1 to 19 of 44 Command ===> ______________________________________________________________ !ACTUAL(STOP) !ARM(N) !CHKEXITFLAG(GOOD) !DESIRE(}SYSG}TASK01}STOP}}}}}SCHED}N}N}20001222130719}SYSA) !IGNORE(N) !JOBNAME(AFOG140) !LASTRETRYDATE(0) !LASTRETRYTEXT() !LASTRETRYTIME(0) !LOCK(N) !RCFUSER(}SCHEDULE AFOG140 YES}20001222130719}) !RECOVERY(OFF) !RECVENA(N) !RETRYCOUNT(0) !ROUTE(SYSG) !RSACTS(R) !RSALACT()



MVS CommandsFrom any of the Sysplex Console panels, you can submit commands to the MVS system on which the selected AF/OPERATOR is running. All MVS commands must start with a slash (/).

In the following example, you have just submitted the MVS command /D A,L from the command line. AF/OPERATOR first displays the Command Verification pop-up (not shown) and then displays the following reply data:

AF/OPERATOR CommandsYou can submit AF/OPERATOR commands to the selected AF/OPERATOR system from any of the Sysplex Console panels.

In the next example, you enter the AF/OPERATOR command SHOW TRAPS on the command line. AF/OPERATOR first returns the Command Verification Pop-Up (not shown), then the following reply data:

MVS Operator Command AF/OPERATOR - Reports Row 1 to 19 of 112 Command ===> ______________________________________________________________ D A,L IEE114I 13.38.10 2000.357 ACTIVITY 790 JOBS M/S TS USERS SYSAS INITS ACTIVE/MAX VTAM OAS 00027 00173 00030 00028 00053 00030/00500 00075 VLF VLF VLF NSW S LLA LLA LLA NSW S ASCH ASCH ASCH NSW S LOGROUTE LOGROUTE LOGROUTE NSW S JES2 JES2 IEFPROC NSW S $AFOPG AFOPER OGEXEC NSW S RMFG RMF IEFPROC NSW S ATRRRS ATRRRS RRS NSW S OAM OAM IEFPROC NSW S KCNDL KCNDL CNDL NSW S NET25 NET NET25 NSW SO $SUPGATG SUPGATEG IEFPROC NSW S $OG120G OG120 OGEXEC NSW S RMFGAT RMFGAT IEFPROC NSW SO TSOG TSO STEP1 IN S SDSFG SDSF SDSF NSW S $DFRMMG DFRM IEFPROC NSW S TCPIPG TCPIPG TCPIP NSW SO INETD4 STEP1 BPXOINIT OWT AO CRON5 STEP1 BPXOINIT IN AO $PORTG $PORTG PMAPG OWT SO $SMTPG $SMTPG SMTP NSW S



AF/Operator Command AF/OPERATOR - Reports Row 1 to 19 of 38 Command ===> ______________________________________________________________ R320 SHOW TRAPS !AOP0210 --- LIST OF ALL WTO CMD TOD XOM XOC XOI XO2 DOM TRAPS --- !AOP0201 ENABLED AO320ARMTRAP WTO(‘!AOP3940*’) COUNT(75) !AOP0201 -------- JOBTYPE(*) JOBNAME(*) JOBCLASS(‘*’) SYSID(SYSG) LINKID( !AOP0201 -------- DESC(*) ROUT(*) CON(*) ASID(*) USR(*) CONNAME() NEWCONS !AOP0201 -------- CONTINUE ALLOW LOG NOTEST NORETAIN AOTRAP !AOP0201 -------- NEWDESC() NEWROUT() !AOP0201 -------- ADDDESC() ADDROUT() !AOP0201 -------- ACTION(‘EX KAORRARM’) !AOP0201 -------- MATCHLIM(0) ALTACT(‘’) !AOP0201 -------- USERID(*) DAYS() !AOP0201 -------- DELDESC() DELROUT() !AOP0201 -------- ATTRIBUTES(COLOR(),HIGHLIGHT(),INTENSITY()) !AOP0201 -------- DOM ACTION(‘*NONE*’) !AOP0201 -------- JOURATTR(COLOR(),HIGHLIGHT(),INTENSITY()) JOURHELP() !AOP0201 ENABLED RRR CMD(‘RRR *PARM’) COUNT(9) !AOP0201 -------- JOBTYPE(*) JOBNAME(*) JOBCLASS(‘*’) SYSID(SYSG) LINKID(

Starting, Stopping, and Overseeing AF/OPERATOR 181

Starting, Stopping, andOverseeing AF/OPERATOR

IntroductionThis chapter tells you how to start and stop AF/OPERATOR by activating and deactivating facilities, runtime environments, and other products that make AF/OPERATOR function properly. It also describes how to Refresh AF/OPERATOR, that is, how to make your configuration and resource definitions take effect immediately.

In addition, the chapter explains how to generate reports and logs that give you information about AF/OPERATOR.

Chapter ContentsStarting the AF/OPERATOR Resource State Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . 182Refreshing the Resource State Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186Stopping Resource State Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187Resource Manager Scheduling Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188Overseeing AF/OPERATOR and the Resource State Manager . . . . . . . . . . . . . . . . . . . . 190RSM Initialization, Termination, and Refresh Processes. . . . . . . . . . . . . . . . . . . . . . . . . . 194Differences betweeen Cold and Warm Starts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

7

Starting the AF/OPERATOR Resource State Manager



IntroductionOnce you have set up your configuration, calendars, and resource definitions, you are ready to start the RSM. However, before you can start the RSM, you must ensure that:

n AF/OPERATOR is active

n the Resource Control Facility (RCF) has been started

For information on the RSM, see “Introduction to AF/OPERATOR” on page 15.

Running the AF/OPERATOR user interface aloneIt is possible to run the AF/OPERATOR user interface without starting RCF and the RSM. This is particularly useful when you want to define configuration specifications, set up calendars, and create resource definitions. Once you have set up those definitions, you can start RCF and the RSM to test what you have defined.

Procedure for starting the Resource State ManagerTo start RSM, use the following procedure.

Make sure the AF/OPERATOR. environment is set up correctly. Edit $$OGINIT in rhilev. RKANCMD where rhilev. is the prefix your site uses for AF/OPERATOR runtime datasets and add the following statements:

“AF NOAUTOREF QUIET”

“AF MATINFO”

Note: $$OGINIT should be a REXX EXEC.

NOAUTOREF and QUIET settings help to ensure that the RSM runs efficiently and suppresses unnecessary AF/OPERATOR console traffic. MATINFO adds important information to the Message Log (MSGLOG).

If you do not have a copy of $$OGINIT in rhilev. RKANCMD, you can use the copy in rhilev.RKANSAM as a model. However, remember to delete the verification test statements.

Now, restart AF/OPERATOR to incorporate the above changes and to check that the commands were executed.



Set up AF/OPERATOR to start RCF automaticallyIn $$OGINIT, add the following statement after the two commands listed in “Procedure for starting the Resource State Manager” on page 182 above.

call KAORSTRT ‘rhilev.RKANISP’

For example:

/* REXX */

call KAORSTRT ‘CANDLE.AO250.RKANISP’

where the resource and calendar definitions you created in the user interface are stored in the rhilev.RKANISP dataset.

The statement above starts RCF with the specified Table Library and with the default RCF command prefix of “RCF”. If you want to start RCF with a different command prefix, for example when you already have a copy of the RSM running in a different address space, then issue this command:

call KAORSTRT ‘rhilev.RKANISP’, ‘rcf’

where rcf is your desired RCF command prefix.

For example:

/* REXX */

call KAORSTRT ‘CANDLE.AO250.RKANISP’, ‘RCF1’

Restart AF/OPERATOR to incorporate changes.

Initialize the RSM with the desired profileTo initialize the RSM, issue the console command

rcf INIT profile

where:

n rcf is your chosen RCF command prefix.

n profile is the profile that you want to initialize.

Note: This is the only permitted RCF command at this point.

The first time you initialize a profile, the RSM automatically performs a cold start. On subsequent initializations, the RSM normally defaults to a warm start. To avoid reissuing the RCF INIT command in the future, modify the command used to start RCF as follows:

call KAORSTRT ‘rhilev.RKANISP’, ‘rcf’, ‘profile’

where

n rcf is your desired RCF command prefix.

n profile is the profile you want to initialize.



For example:

/* REXX */

call KAORSTRT ‘CANDLE.AO250.RKANISP’, ‘rcf1’, ‘myprof’

For a description of the RCF INIT command, see “Resource Control Facility Commands” on page 105. For a detailed description of cold and warm starts and their results, see “Differences betweeen Cold and Warm Starts” on page 199.

Note: Only one profile can be active, or initialized, at a time. Before initializing a different profile, you must first terminate the current profile. For a description of RCF TERMINATE, see “Resource Control Facility Commands” on page 105.

If this is a cold start...If this is a cold start, reply to WTOR KAO08000, which controls Scheduler Initialization. The normal reply should be “OK”, but for a list of additional replies to the KAO08000 message, see “Differences betweeen Cold and Warm Starts” on page 199.

Determine the state of the initializationCheck the system log for the following KAO01000 message:

KAO01000 AF/OPERATOR V250200source Manager

successfully initialized COLD/WARM

This message indicates that the RSM is now active and controlling resources. You can now issue any RCF command.

Check the MSGLOG for message KAO08102. This message indicates whether the RSM started or stopped any resources during Initialization to bring them to their correct status.

Check the MSGLOG for message KAO08200. This message lists all scheduled Start or Stop events for the current period. Request this display at any time by issuing this command:

rcf LIST SCHEDULE

OK Instructs the RSM to calculate current “Desired” status for each resource based on the most recently defined scheduled Start or Stop for that resource.

If you do not reply to the KAO08000 message within the timeout period (normally 2 minutes), then “OK” will automatically be assumed.



Check Global Preferences and change if requiredTo check current Global Preference settings, issue this command:

rcf LIST GLOBAL

To temporarily change a Global Preference setting, issue this command:

rcf SET option value

For example:

rcf SET MSGDEST WTO

To permanently change the setting, update Global Preferences in the user interface.

Two Global Preference settings control how RSM messages and replies are issued:

Restart AF/OPERATOR to incorporate these changes.

Optionally, display status information for resourcesTo display status information for all resources, issue the command:

rcf STATUS *

MSGDEST WTOs (WTO) or AF/OPERATOR LOGMSGs (LOG). During testing, you may want to set MSGDEST to LOG.

TPUT Controls whether replies to RCF commands from a TSO user are TPUTed Yes or No.

Refreshing the Resource State Manager


Refreshing the Resource State Manager

IntroductionIf you have changed resource definitions in the user interface, you must refresh the RSM to incorporate those changes. There are two ways to refresh the RSM:

n Issue the RCF REFRESH command from the MVS console (For a description of this command, see “Resource Control Facility Commands” on page 105.)

n Use the AF/OPERATOR user interface

If you want to switch to a different profile, you must issue terminate and reinitialize commands, since REFRESH applies only to the current profile.

When you refresh the RSM, it performs processing similar to that done during a warm start. This includes checking to determine whether resources are currently in the correct state as specified by previous RCF START or STOP commands or by a previously scheduled action. It can also include starting or stopping resources, if required, to bring them to the correct status.

After a REFRESH, it is always a good idea to check the MSGLOG to confirm reasons a resource may have been started or stopped.

Procedure for refreshing the RSMTo refresh AF/OPERATOR from the MVS console, issue this RCF command:

rcf REFRESH profile

The RCF REFRESH command allows all current resource activities to complete processing (or DRAIN) before updating your resource definitions, calendars, schedules, and configuration.

To interrupt processing and refresh AF/OPERATOR immediately, issue this RCF command from the MVS console:

rcf REFRESH profile FORCE

Warning: Use the REFRESH FORCE command with caution. It destroys all events currently processing. If you issue this command before you have responded to a warning WTOR, the resource activity associated with the WTOR will not take place. Therefore, be sure to respond to all WTORs before issuing the REFRESH FORCE command.


Stopping Resource State Manager

Stopping Resource State Manager

IntroductionWhen you stop or “terminate” a Resource State Manager profile, the RSM stops controlling the resources in that profile and deletes all variables associated with those resources. The resources themselves are not stopped; they remain in their current state. If you want to stop all resources, such as for an IPL, you should issue RCF STOP resource commands before you terminate the RSM. For examples of stopping several resources simultaneously, see the RCF STOP command in “Resource Control Facility Commands” on page 105.

After the RSM has been terminated, you can issue the RCF INIT command to initialize the RSM with the same or with a different profile; or you can stop the AF/OPERATOR address space. The system accepts only RCF INIT commands at this time.

Note that status information about the resources in an RSM profile is always checkpointed and saved, even if you stop the AF/OPERATOR address space without terminating the current profile.

Procedure for stopping Resource State ManagerTo stop the RSM from processing, issue this RCF command:

rcf TERMINATE profile

Verifying that AF/OPERATOR has stoppedTo verify that the RSM has stopped processing, check to see that the following KAO01999 message appears in the system log.

AF/OPERATOR Version 320 Resource Manager has terminated successfully.

Resource Manager Scheduling Considerations


Resource Manager Scheduling Considerations

How scheduling is affected when RSM stopsBefore you stop RSM, you should consider the resources you have scheduled to start or stop during the time RSM will be down.

For example, you might schedule CICS to stop at 17:00, with a warning WTOR to be sent out 30 minutes in advance, notifying the operator that CICS will go down and allowing the operator to cancel the activity, extend the delay, or request that the activity occur immediately. However, if the RSM terminates at 16:25 and reinitializes cold at 16:50, then the CICS WTOR is issued when AF/OPERATOR starts, and the CICS activity scheduled for 17:00 will not take place until 17:20.

In this example, if you want CICS to stop sooner or later than 17:20, you can respond to the WTOR as follows: You can choose among:

n stopping CICS immediately

n extending the delay up to an hour

n canceling the stop completely

Delaying or canceling an activity for a predecessor resource will prevent activities scheduled for other resources (those that require the predecessor resource) from occurring.


Managing Always Active Resources

Managing Always Active Resources

IntroductionResources defined as Always Active generally behave as if they were scheduled to be permanently started. This means that the normal rules about scheduled resources and warm and cold starts also apply to Always Active resources. For more details about warm and cold starts, see “Differences betweeen Cold and Warm Starts” on page 199.

Determining when Always Aactive resources are automatically startedUse the following table to determine when Always Active resources are automatically started (if not already active) during warm and cold starts.

Note that Always Active resources are not automatically started during a warm start if the RSM determines that scheduling is currently disabled for that resource. Thus, to prevent some Always Active resources from being automatically started during a warm start, disable scheduling for those resources.

If Scheduling remains enabled for an Always Active resource, you can issue an RCF STOP command. This command stops the Always Active task while still permitting it to be started automatically at the next warm start.

For a description of the commands and Global Preference settings that affect how and when scheduling is enabled or disabled, see the RCF SCHEDULE command in “Resource Control Facility Commands” on page 105.

Start typeScheduling enable for

resource?“Always Active” resources started if

required?

COLD n/a YES

WARM NO NO

WARM YES YES

Overseeing AF/OPERATOR and the Resource State Manager



IntroductionYou can view reports and logs to help you monitor and verify the actions of AF/OPERATOR and of the Resource State Manager. From RSM, you can view the following:

n RCF SHOW command reports

n RCF LIST command reports

n Message logs

Using the message logYou can log commands and messages from AF/OPERATOR and store them in RKOGLOGM. You can use the messages in the message log to diagnose problems and debug your system.

The message log location is set up during OG*TSO configuration. See the AF/OPERATOR User’s Guide for more information on setting up and viewing logged messages.

Using the historical logYou can useAF/OPERATOR’s RETAIN*VIEW facility to display a historical record of messages, commands, and OMEGAMON exceptions that have triggered traps.

To record trap activity in the AF/OPERATOR historical log, specify the RETAIN option on the WTO, CMD, or xtype TRAP ADD or TRAP CHANGE command. Each time the trap is triggered, the triggering event is written to a special log dataset. You can view detailed information about the trapped events in that dataset, to help you develop and debug traps more efficiently.

You can group commands or messages for easier viewing. For example, you can display all VTAM messages from all VTAM nodes that were trapped during a certain time period.

RETAIN*VIEW can also provide a consolidated log of message activity from various sources. For example, you can merge IMS messages issued to the MTO with IMS messages issued to the MVS operator console.

Historical log datasetsWhen AF/OPERATOR is installed, a series of datasets (up to 99) are allocated for the historical log. When one dataset is full, AF/OPERATOR closes it and switches to the next. When the last dataset is full, AF/OPERATOR starts again with the first dataset. This feature lets you retain a great number of events in the historical log.

AF/OPERATOR issues message number AOP0745 when it switches to a new dataset. You can use this message to trigger a match that archives the newly filled dataset.



Viewing messages and commands using RETAIN*VIEWTo use RETAIN*VIEW to show information about messages and commands, follow the procedure described here.

Select RETAIN*VIEW from the Tools pull-down on the AF/OPERATOR Primary Menu and preess Enter to display the Defined Systems panel.

On the Defined Systems panel, select the system for which you want to show information and press Enter to display the Retain Log Text Selector panel for that system.

Note: On the Retain Log Text Selector panel, you must specify WTO ===> Y to use the WTO filter—MSGID, JOBNAME, JOBTYPE, CONS, and ROUT. You can use only those filters appearing in the list under WTO ===>. Similarly, you must specify CMD ===> Y: to use the CMD filters—CONS, JOBNAME, and JOBTYPE.

In the Dataset field, type the name of a previously retained dataset. In the Subsystem field, type the name of the AF/OPERATOR subsystem on which this copy of AF/OPERATOR is running.

Note: You cannot display log datasets (RKOGLHNn) contained on other copies of AF/OPERATOR.

Defined Systems ROW 1 TO 7 (S)elect a System and press Enter. System ID Description SMF Id Sub Sys _ GCNO gcno SYSG GCNO _ SYSA Candle Development System A SYSA OMC _ SYSA1 Test Install for AF/OPERATOR V247.9 SYSA AO47 _ SYSB Candle Test System B SYSB AOB _ SYSG Candle Test System G SYSG G _ SYS1 A non-existant system for conversio SYS1 XXXX _ X x X X **************************** BOTTOM OF DATA ************************ Command ===> _______________________________________________________---------------------------------------------------------------------



When you have completed the panel, press Enter. This causes the RETAIN*VIEW panel to display the messages or commands trapped with the RETAIN option.

To find out additional information about a message or command listed on the report, enter S (for Show variables) next to any line to display the AF/OPERATOR Variables panel.

!Candle RETAIN LOG TEXT SELECTOR ENTER DATASET NAME OR SUBSET NAME DATASET ===> SUBSYSTEM ===> START DATE/TIME ===> _______ ________ (mm/dd/yy hh:mm:ss) END DATE/TIME ===> _______ ________ (mm/dd/yy hh:mm:ss) WTO ===> _ (Y or N) CMDS ===> _ (Y or N) MSGID ===> _________ (1-9 chars) CONS ===> ___ (1-3 digits) JOBNAME ===> ________ (1-8 chars) JOBNAME ===> ________ (1-8 chars) JOBTYPE ===> ____ (JOB,STC,TSU) JOBTYPE ===> ____ (JOB,STC,TSU) CONS ===> ________ ROUT ===> ________ MVS Exceptions ===> _ (Y or N) CICS Exceptions ===> _ (Y or N) IMS Exceptions ===> _ (Y or N) DB2 Exceptions ===> _ (Y or N) COMMAND ===>

!Candle RETAIN*VIEW COMMAND ===> LINE OPTIONS: S=Show variables, T=Trap add OPT MESSAGE TEXT _ 88192 08:59:04.16 STC 4641 IEFTMS10 --HOOKS IN ERROR--_ 88192 08:59:04.16 STC 4641 IEFTMS10 --HOOKS IN ERROR--_ 88192 08:59:03.28 STC 4641 IEFUCC01 UCC OS WTO INTERCEPT ACTIVATED_ 88192 08:59:03.34 STC 4641 IEFUCC05 UCC OS WTO - UCC 001 INTERCEPTS ACTIVATED_ 88192 08:59:08.84 STC 4641 $HASP395 TMSINIT ENDED_ 88192 08:59:08.11 STC 4641 +IEFTMS1 UCC-ONE(TMS) IS ACTIVE_ 88192 08:59:09.51 IEA989I SLIP TRAP ID=X33E MATCHED_ 88192 08:59:10.66 STC 4641 $HASP250 TMSINIT IS PURGED_ 88192 08:59:19.58 STC 4640 F VPS,ACTI,R110A31_ 88192 08:59:19.88 STC 4657 VPS600N-R110A31 PRINTER SUCCESSFULLY ACTIVATED_ 88192 08:59:35.77 ISG011I SYSTEM SYSC - QUIESCING GLOBAL RESOURC



The value of ROUT or DESC may be the wildcard asterisk character (*). This means that the trap is triggered no matter what the message route or descriptor code is.

AF/OPERATOR Variables fieldsThe match variables shown on the AF/OPERATOR Variables panel correspond to the AF/OPERATOR-supplied match variables listed in the following table. For further information on AF/OPERATOR-supplied match variables, refer to the AF/OPERATOR Command Reference Manual.

Field name Variable Description

ASID AOASID Address space ID

CONSOLE AOCONS ID of console to which trapped message is routed

DESC AODESC Descriptor code(s) of trapped message

JOBCLASS AOJCLAS Job class of trapped message or command (same as JES2 variable if JES2 is running)

JOBNAME AOJNAME Job name, task name, or TSO user ID

JOBTYPE AOJTYPE Job type (IMS, JOB, STC, TSU, O2, OC, OI, OM)

ROUT AOROUT Message route code

SYSID AOSID SMF system ID (IMS region if jobtype is IMS)

!Candle AF/OPERATOR Variables COMMAND ===> Text: IST093I CDRM01 ACTIVE Match variablesASID 9 JOBTYPE STC JOBCLASSCONSOLE JOBNAME NET SYSID SYSAROUT 1,2,3DESC 7 Environmental dataJOBID STC 1234 MESSAGE PREFIX 0000 hh&colon.mm&colon.ss STC 1234TSO NOTIFY TSOUSER PROGRAMMER NAME I. M. PROGRAMMERACCOUNT NUMBER 1234 ROOM NUMBER 1234INPUT DEVICE STCINRDR ORIGINATING NODE NODE1MSGCLASS X

RSM Initialization, Termination, and Refresh Processes



IntroductionInitially, it is not particularly important whether the Resource State Manager (RSM) performs a warm or a cold start, except that in a warm start the RSM recalls previous RCF START or STOP commands. In most cases, you should allow the RSM to select the appropriate default Start Type (according to the rules described in “Processing for warm starts” on page 195. For cold starts, reply to the KAO08000 message with the default, OK.

Once you begin to define schedules or to allow the RSM to automatically manage resources for you, however, the type of initialization you perform when starting the RSM becomes more important. Selecting an inappropriate type of initialization, such as overriding the defaults, may result in missed resource starts or stops.

Understanding warm and cold starts and the refresh process also helps to explain actions that the RSM may take at this time, and may enable you to use available techniques to achieve specific results.

This section describes the Scheduling process, the different types of initialization, and the consequences of selecting each type.

Overview of the scheduling processThe RSM maintains an internal list of the start and stop events that are scheduled to occur during the current period (normally 24 hours). It builds this list using information from resource schedule definitions (and their respective daytypes and their order), together with the appropriate calendar definitions. The RCF LIST SCHEDULE command displays these events. (For information about the RCF LIST command, see “Resource Control Facility Commands” on page 105).

When the last start or stop in the current period has been processed, the RSM automatically rebuilds the list to include all starts and stops for the next period, and logs a copy of the list in MSGLOG.

The RSM uses a special TOD trap to :q.wake up:eq. the Scheduler at the time of the next event in the scheduled event list. The Scheduler then finds all resources that are scheduled to be started or stopped at this time. It logs each start or stop event in the MSGLOG and updates the current “Scheduled” for the resource to reflect the scheduled event.

The Scheduler also checks to determine whether scheduling is enabled. For those resources having schedulig enabled, AF/OPERATOR performs the scheduled start or stop and updates their Desired status. For a description of which commands and Global Preference settings affect how and when Scheduling is enabled or disabled, see RCF SCHEDULE in “Resource Control Facility Commands” on page 105.



Initialization processingWhenever the RSM is started or restarted, it attempts to determine the correct status (started or Stoped) for each managed resource. If are source is not already in the correct state, the RSM starts or stops that resource as required. Depending on the kind of start, this feature can either:

n for a warm start or refresh, restore all resources to their previous requested state, allowing for start or stop events that were scheduled to occur during the period that the RSM was not active, or

n for a cold start, determine a status for each resource based mainly on user interface definitions.

A warm start is the recommended type of initialization for normal processing using a single profile. Use a cold start only if you want to perform a “clean” start. You can specify the start type (cold or warm) on the RCF INIT command or on the KOARSTRT call. If start type is not specified, the RSM chooses the most appropriate start type as follows:

n If this is the first time that this profile has been initialized or this profile is different from the one that was last active, then a cold start is performed.

n If any of the information required for a warm start is not available, then a cold start takes place. Otherwise, a warm start is performed.

After the refresh or warm or cold start completes, Scheduler processing resumes normally as described above in “Overview of the scheduling process” on page 194. The Scheduler TOD trap is initially set for the time of the first scheduled event. You can check the time of this event by issuing the RCF LIST SCHEDULE command.

Processing for warm startsA warm start allows the RSM to continue smoothly after a restart, recalling previous resource status as well as any scheduled events that should have occurred. A warm start is the fastest way to restart, since it requires no additional information (and no message to which you must reply), and since schedules must be checked only for the period during which the RSM was not active.

If you do not want the RSM to automatically start or stop resources during a warm start to bring them to the correct status, you can so specify by correctly setting the Global Preference Init Msg in the user interface. Init Msg lets you specify that AF/OPERATOR is to issue a confirmation WTOR before any resource is started or stopped, either for warm starts only or for both warm and cold starts.

Note: A warm start will not be available if the checkpointing feature of AF/OPERATOR is not turned on.



During a warm start, the following processing occurs:

1. Information about Scheduled status, Desired status, and the last requested action for each resource is restored from values saved (checkpointed) when the RSM was last active. The last action may have been an RCF START or STOP request, or it may have been a scheduled start or stop event. The previous setting for scheduling (enabled or disabled) for each resource is also restored.

2. The time and date of the last scheduled start or stop event to occur before the RSM terminated is restored from the checkpointed value.

3. The Scheduler checks for any starts or stops scheduled to occur from the time of the last scheduled event until the current time. For each event that it finds, the Scheduler updates the Scheduled status for that resource to reflect the scheduled start or stop.

4. Each resource is then processed as follows:n If the resource has scheduling enabled, then the Scheduled status as determined above is

the correct setting for the resource, and the RSM starts or stops the resource if necessary to bring it to that status. Desired status is also updated with the same information at this point.

n If the resource has scheduling disabled, then the Scheduled status is ignored. Instead, the RSM checks for a previous RCF START or STOP command, and uses that as the correct setting for the resource. It then starts or stops the resource if necessary to bring it to that status.

5. At the end of this process, a short report containing the following information is logged to the MSGLOG:n the status of each resource after the restart and before the RSM took any action

n whether scheduling is enabled or disabled for the resource

n the action (start or stop) required to bring resources to the correct status

n the reason for the required action (For example, Previous RCF START or scheduled START at...)

Note: Always Active resources are handled as if they were permanently scheduled in a “Start” state. If scheduling is enabled, then they are started if required, but if scheduling is disabled, then a previous RCF START or STOP command, if there was one, is honored.



Processing for cold startsIn a cold start, the RSM ignores any previous information about resource status, scheduled events, and RCF START or STOP commands. The only information that may be used to decide correct status of resources at Initialization is resource schedule information that is defined in the user interface. A WTOR (KAO08000) message is issued during a cold start so that you can specify how you want to use this schedule information.

You can make one of three possible replies to the KAO08000 message:

The default reply to KAO08000 message is OK.

Note that a reply of OK does not guarantee that the RSM can determine a current “Scheduled status” for each scheduled resource. If resource schedules do not contain any definitions for start or stop events during the week before the restart, then no Scheduled status can be determined for that resource, and therefore no action is taken. However, for most resources and most situations, this process is sufficient to determine a current Scheduled status and most resources are started or stopped correctly.

At the end of this process, a short report is logged to MSGLOG, that shows the following:

n the status of each resource after the restart and before the RSM took any action

n the action (start or stop) required to bring resource to the correct status

n the reason for the required action (For example, Scheduled START at...)

Always Active resources are always started if required during a cold start.

For a description of how to request a confirmation WTOR before any resource is started or stopped, see “Processing for warm starts” on page 195.

OK The RSM attempts to determine a correct status for each resource based on schedules defined in the user interface. It does this by calculating the most recent scheduled start or stop for each resource before the current time and up to a maximum of one week in the past. The RSM then starts or stops the resources if required to bring them to this status. This is the recommended type of cold start.

yyyymmddhhmmss The RSM attempts to determine a correct status for each resource based on resource schedules defined in the user interface. However, it only takes into account start or stop events scheduled to occur between yyyymmddhhmmss and the current time. The RSM then starts or stops resources to bring them to this status.

Depending on the date and time, this can be a quicker method than the use of OK, but the RSM may not be able to determine the correct state for a resource if its most recently scheduled start or stop preceded the date and time specified

NOW The RSM does not check for recently scheduled events and therefore cannot determine a correct status for each resource. It takes no action to start or stop resources.



RefreshA refresh is similar to a warm start. It is important to understand that the RSM checks resource status during a Refresh in the same way as it does during a Warm start, and that it may start or stop resources to bring them to the correct status. A report showing any actions taken during a refresh is logged to MSGLOG.


Differences betweeen Cold and Warm Starts


IntroductionWhen AF/OPERATOR is initialized, the resulting KAO01000 message indicates whether the start type was cold or warm. A cold start brings all resources defined in the given profile to their scheduled state. A cold start is the default unless the given profile was the last active profile.

Select a cold start when you want to perform a “clean” start. Include one of the following cold start WTOR options:

A warm start brings all resources defined in the given profile to their Desired state. The Desired state is the same as the Scheduled state unless one of these conditions is true:

n An RCF command has been issued to start or stop a resource, and no RCF SCHEDULE command has been issued to return control of the resource to the Scheduler.

n Recovery of a resource has failed and no RCF SCHEDULE command has been issued to return control of the resource to the Scheduler.

A warm start is the default if the profile was the last one active. The warm start preserves the integrity of the schedules. If a warm start does not include all required information, the RSM issues a cold start. If scheduling is disabled, the warm start uses the previous RCF START/STOP commands.

OK Scheduled status is determined from the defined schedules.

NOW No resources are started or stopped during initialization. Schedule starts from now.

yyyymmddhhmmss Scheduled status is the most recent scheduled start or stop since the specified time.

Testing and Debugging 201

Testing and Debugging

IntroductionWhen you want to test your traps and commands, you can set up a testing environment and use facilities provided by AF/OPERATOR to verify that your traps and commands are working correctly.

This chapter shows you how to:

n set up a test profile

n simulate and test WTOs and commands

n simulate AF/OPERATOR

You many want to set up a separate AF/OPERATOR address space for your test system. That way you can have a production AF/OPERATOR and a test AF/OPERATOR running separately but simultaneously. This can also be useful in the event one AF/OPERATOR goes down. You can use another AF/OPERATOR to take over until all address spaces are functioning properly.

Chapter ContentsSetting up a Test Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202Simulating a Console with OG*TSO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

8

Setting up a Test Profile


Setting up a Test Profile

IntroductionIn this unit you will:

n Create a profile to use as a testing environment for AF/OPERATOR

n Associate it with a system, and

n Copy a resource to use as a model

Create the test profileTo copy a profile to use in your test environment, follow this procedure. To get help about any panel or field, press F1.

From the Configuration pull-down on the AF/OPERATOR main panel, select Profile. When AF/OPERATOR displays the Profiles panel, type C (for Copy) next to the profile you want to copy, and press Enter.

AF/OPERATOR displays the Copy Profile panel. On the Copy Profile panel, change the profile name and press Enter to add the new profile to the profile list.

Now, make the new profile the current profile by typing S (for Select) next to the profile name. Press Enter, and then press F3 to return to the AF/OPERATOR main panel.

For more information on working with profiles, see “Setting up system profiles” on page 30.

Associate the profile with a systemFrom the Configuration pull-down on the AF/OPERATOR main panel, select Systems and press Enter. AF/OPERATOR displays the Systems panel listing all the systems already defined to AF/OPERATOR.

If the system you want is already on the list, you can skip to “Copy a resource definition” on page 202. To add a system to the list, type A(for Add) in the action column and press Enter.

When AF/OPERATOR displays the Add System panel, fill in the information requested. Press Enter, then press F3 to return to the AF/OPERATOR main panel. This causes the new system to be added to the list and defined to AF/OPERATOR.

Copy a resource definitionFrom the Automation pull-down, select Resources and press Enter to see a list of all of the defined resources. Enter C(for Copy) next to the resource you want to use as a model, and press Enter.

AF/OPERATOR displays the Copy Resource panel. Change the resource name and system ID on that panel, press Enter, then press F3 to return to the AF/OPERATOR main panel. The causes the new resource to be defined to AF/OPERATOR.

You can now use the new profile, system, and resource to test resource management.

Testing and Debugging 203

Simulating a Console with OG*TSO


IntroductionOG*TSO is a simulated version of an AF/OPERATOR console that runs under TSO. It is a safe environment, separate from your production system, in which to learn about AF/OPERATOR. It is useful for developing and testing traps. You can create traps, watch the results display on the screen, and test your solutions before putting them into your production system.

Some commands under OG*TSO are simulated, while others work just as they do with your AF/OPERATOR started task.

Important: Within an OG*TSO environment, any session issued with the LOGON command is a fully-functional session and all subsequent procedures will behave in a normal fashion; that is, even though OG*TSO is a “simulation” of AF/OPERATOR, the sessions which it initiates with the LOGON are real.

Accessing OG*TSO from ISPFTo access OG*TSO:

1 Select OG*TSO from the Tools pull-down on the AF/OPERATOR main panel.

Result: The OG*TSO Startup Parameters panel appears.

To exit OG*TSO:

1 F3

For more informationFor instructions on simulating a console, see the AF/OPERATOR User’s Guide.

Writing Your Own Resource Management Routines 205

Writing Your Own ResourceManagement Routines

IntroductionEach AF/OPERATOR resource definition includes two routines to external REXX routines:

n A check routine that determines the state of the resource

n A notification routine invoked if a resource abends and recovery fails

Candle supplies default routines, but you can write your own routines and specify their names on the Resource Definition panel. Each resource can have its own routines if desired. If you omit the routine names in the resource definition, AF/OPERATOR uses the Candle default routines.

This section gives specifications for both routines.

ContentsChecking the State of a Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206Recovery Failure Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211Resource Manager Application Programming Interface. . . . . . . . . . . . . . . . . . . . . . . . . . 212

A

Checking the State of a Resource



IntroductionThe check routine is a REXX exec called by AF/OPERATOR whenever it needs to determine the state of a resource. This section provides specifications for writing a check routine.

When the routine is calledThe check routine is called at these points in AF/OPERATOR processing:

n During AF/OPERATOR initialization

All check routines defined for resources in the profile specified in the RCF INIT command are preloaded during initialization.

If the check routine fails or is not available during initialization, the routine is marked as bad and is never called again until the routine is fixed and the product is either refreshed or restarted.

n When a resource activity is being initiated

If the activity completes successfully, the resource’s state is changed to reflect the activity. For example, if a START activity completes successfully, the state becomes START (active).

If the activity completes unsuccessfully, the state is not updated.

n During recovery retries

The check routine can be called repeatedly during recovery. because AF/OPERATOR needs to determine that the resource is still inactive so further retrys can be attempted.

n When the RCF Check subcommand is issued

Parameters passed to the routineTwo parameters are passed to the check routine:

n Resource name

n Task name

Because the check routine is called directly from AF/OPERATOR, the parameters are passed in the same way as for any other REXX routine and can also be accessed in the usual way.

What the routine must returnThe check routine must return one of two strings to indicate the state of the resource: ’START’ (active) or ’STOP’(inactive).

If some value other than ’START’ or ’STOP’ is returned, the current activity fails. If that activity is a recovery retry, the resource is considered unrecoverable.



Default check routineThe default routine is KAORRCHK. Candle supplies source code for sample routine KAORRCH1 in hilev.TKANEXEC. The sample routine KAORRCH1 shown below functions similarly to the KAORRCHK routine.

Sample Routine KAORRCH1

====================================================================== Candle Corporation Copyright (c) 1985-2002 U.S.A All Rights Reserved. Use permissible by license only.====================================================================== Function Example resource check exit. Issues an AF ACTIVE function on the resource name and returns either START or STOP based on the resource status. This is called by AF/OPERATOR when it needs to determine the state of the resource being managed. Operation Issue ACTIVE If ACTIVE then return ‘START’ If not ACTIVE then return ‘STOP’ Parameters Resource name Task name Returns START if the resource is active STOP if the resource is inactive ======================================================================*/Do/*%EDULCNI KAOR$CH0 - Set up exception handling. *//* +--------------------------------------------------------------- + Start of imbed KAOR$CH0. +---------------------------------------------------------------*/ Signal on error name _CHK_handle_exception Signal on halt name _CHK_handle_exception Signal on novalue name _CHK_handle_exception Signal on syntax name _CHK_handle_exception/* +--------------------------------------------------------------- + End of imbed KAOR$CH0. +---------------------------------------------------------------*//*%EDULCNI KAOR$CHK - Include main body. *//*



+--------------------------------------------------------------- + Start of imbed KAOR$CHK. +---------------------------------------------------------------*/ True = (1 == 1) /* Evaluate Boolean control variables. */ False = \True Process = True /* False - Terminate processing in this function */ /* True - Continue processing in this function */ /* +------------------------------------------------------------- + Validate program arguments. +------------------------------------------------------------- */If arg() \= 2, then, Do Parse source . . ModN . Say ModN || “: Number of parameters invalid.” Process = False /* Terminate processing. */ Resource_state = “STOP” /* Default state. */ EndIf Process, then, Do /* +--------------------------------------------------------- + Retrieve the resource and task name from program + arguments. +--------------------------------------------------------- */ Parse upper arg Resource ., Task . Alpha = “ABCDEFGHIJKLMNOPQRSTUVWXYZ” Number = “0123456789” National = “@#$” If verify(Task, Alpha || Number || National) \= 0, | verify(left(Task,1), Alpha || National) \= 0, | length(Task) > 8, | task = ““, then, Do Parse source . . ModN . Say ModN || “: Task name ‘” || Task || “‘ is invalid.” Process = False /* Terminate processing */ Resource_state = “STOP” /* Default state */ End Drop Alpha Number National End

If Process, /* If processing is to continue...*/ then, Do /*



+--------------------------------------------------------- + Use AF’s ‘ACTIVE’ function to get the task state. + If the task is up then set resource state to START, + otherwise set state to STOP. +--------------------------------------------------------- */ If ‘ACTIVE’(Task), then, Resource_state = “START” else Resource_state = “STOP” End/* +--------------------------------------------------------------- + End of imbed KAOR$CHK. +---------------------------------------------------------------*/ Return Resource_stateEnd /*%Page *//*%EDULCNI KAOR$CH1 - Exception handling routine. *//* +--------------------------------------------------------------- + Start of imbed KAOR$CH1. +---------------------------------------------------------------*//* ------------------------------------------------------------------ */_CHK_handle_exception:Do Parse source . . ModN . ModN = ModN || “:” Drop Type Description Location Source Condition. = ““ Condition.Type = condition(“c”) Condition.Description = condition(“d”) Condition.Location = SIGL Condition.Source = strip(sourceline(SIGL),”t”) pad = 16 /* Pad size */ pc = “.” /* Pad character */ Say ModN left(“Check method”,pad,pc) “Exception condition detected.” Say ModN left(“Exception type”,pad,pc) Condition.Type Say ModN left(“Source line #”,pad,pc) Condition.Location Say ModN left(“Source”,pad,pc) Condition.Source Select When Condition.Type = “ERROR”, | Condition.type = “FAILURE”, then, Do Say ModN left(“Failed cmd”,pad,pc) Condition.Description Say ModN left(“Return Code”,pad,pc) RC End



When Condition.Type = “HALT”, then, Do Say ModN left(“Halt reqst”,pad,pc) Condition.Description End When Condition.Type = “SYNTAX”, then, Do Say ModN left(“Error text”,pad,pc) Condition.Description Say ModN left(“REXX error”,pad,pc) RC || “,” errortext(RC) End When Condition.Type = “NOVALUE”, then, Do Say ModN left(“Variable”,pad,pc) Condition.Description EndOtherwise, Do Say ModN left(“Description”,pad,pc) Condition.Description If symbol(“RC”) = “VAR”, then, Say ModN left(“Return Code”,pad,pc) RC End End /* select */ Return “STOP” /* Return default value. */End


Recovery Failure Processing

Recovery Failure Processing

IntroductionThe notification routine is invoked when the recovery retry limit, within the specified period, is reached. The routine is invoked by an AF/OPERATOR EXEC command and therefore is not a called routine. The AF/OPERATOR thread is a TOD(*) trap with an ACTION field that executes the named routine.

The Candle default routine, KAORRNFY, issues a SEND message to every TSO user ID in the notification group. The notification group is set up during configuration, and the group name is specified in the resource definition.

Although the default routine performs notification, you can write your routine to respond to recovery failure in any number of ways, including:

n using the AF/OPERATOR BEEP function to beep someone, and then using a timed WTOR on the console to trigger beeping the next person on the list if the first person does not respond.

n trapping the text of the abend WTO and trying to fix the problem it indicates. For example, if the WTO is an out-of-space message, the routine can execute a job to delete space and then issue RCF commands to reset and restart the resource.

What the routine must returnBecause the routine is under the control of AF/OPERATOR, it must return an AF/OPERATOR return code (0, 4, 8, etc.). For more information, see the AF/OPERATOR Language Reference Manual.

Data available to the routineThe routine has access to all of the variables available to any REXX running in the AFHOST environment. Additionally, it also has access to table data supplied via the User Interface by using the services of the application programming interface KAORRAPI.

Resource Manager Application Programming Interface



IntroductionThe REXX module KAORRAPI provides a data interface between the resource manager and other AFHOST REXX modules. The default recovery notification uses this API to determine which users to send messages to. As the data returned from the API can be text strings, the following conventions have been adopted. The first or only string returned is a numeric value representing a status code. Any other data returned through the interface will be contained in a single string. If needed, substrings within this string will be delimited by a special delimiter character. This character will be the first character of the return string. Thus, a return string can be broken into its component parts by using the REXX PARSE instruction.

Example:

Parse value KAORRAPI (SomeService) with Status ReturnString

If Status = 0,

then,

Parse var ReturnString delimiter 2 ,

0 (delimiter) value1 ,

(delimiter) value2 ,

...

(delimiter) valuen ,

(delimiter) ,

The API provides services to accomplish the following:

1. Extract the parameters from the trap

2. Retrieve data from Resource Manager tables

Service GetParms

Services Table, Open, Close, Read



TablesThis interface supports the following resource manager tables:

n Users Table

n NotificationGroups table

n NotificationUsers table

The Users Table contains the following information:

The NotificationGroups table contains the following information:

The NotificationUsers table contains the following information:

Processing Recovery Trap ParametersTrap parameters are not actually specified in the trap command and thus can be obtained only through this function. The call to this service must occur under the trap AF/OPERATOR used to invoke the notification routine. If the routine sets off another trap, the trap parameters will not be available to that trap. For this reason, you will need to issue a ‘GETPARMS’ at the very beginning of the notification routine.

GETPARMS Service

where

GETPARMS is a literal string

UserID The TSO user ID

GroupName The authorization group of this user

Name User’s name

Phone User’s telephone number

Extension Telephone extension

Profile User’s current resource manager profile

GroupName The notification group name

Description Identification text

GroupName The notification group name

UserID A TSO user ID

Function Access recovery trap parameters

Parameter GetParms

Returns Status TrapParameters



where

status is one of the following:

TrapParameters is a delimited string containing the following information:

Example:

Parse value KAORRAPI(“GetParms”),

with API_rc Parameters

If API_rc = 0, /* Trap parameters are available. */

then,

Do

parse var parameters delim 2, /* Extract the delimiter */

0 (delim) Profile, /* Use it to parse the data */

(delim) Resource,

(delim) Group,

(delim) WTO_text,

(delim) User_Parm,

(delim) .

Drop parameters /* Done with this var. Delete it. */

End

0 successful completion

8 trap parameters unavailable

Profile The profile in which the recovery failure occured

Resource The failing resource

Group The user specified notification group name

WTO_Text The text of the message indicating an abend

User_parm The parameter(s) specified in the notification Exit field during resource definition



Processing tables

Table Service

where

where


Function Access table data

Parameters TABLE, Profile, TableID [OutputOption[,stem.]]

TABLE is a literal string

Profile is the profile which is controlling this process

TableID is one of the following literal strings:n Usersn NotificationGroupsn NotificationUsers

OutputOption is one of the following:

STEM Output will be loaded into AF/OPERATOR REXX shared variables. If this option is chosen, stem must contain the name of a valid REXX stem.

LIFO The output is pushed down onto the program stack.

FIFO The output is queued onto the program stack.

Returns Status

0 successful completion

4 Invalid call parameters

8 table is not open

16 attempted to read past end of table

20 unable to stow results in RSVs



Example:

Parse value KAORRAPI(“Table”,,

Profile,,

“Users”,,

“Stem”,,

“Userdata.”,,

“System”,

with API_rc .

If API_rc = 0,

then,

Do

...

End

Open Service

where

where


Function open a table for read

Parameters OPEN, Profile, TableID

OPEN is a literal string

Profile the profile which is controlling this process

TableID one of the following literal strings:n Usersn NotificationGroupsn NotificationUsers

Returns status #_of_rows

0 successful open

8 table could not be opened

#_of_rows is the number of rows in the table



Example:

Parse value KAORRAPI(“Open”, profile, tableID),

with API_rc row_count

Read Service

where

where

Status is one of the following:

Example:Do i = 1 to row_count

Parse value KAORRAPI(“Read”, profile, tableID),

with API_rc row_data.i

If API_rc = 0,

then,

Do

Parse var row_data delim 2,

0 (delim) word1.i,

...

End

End i

Function reads a row from an open table

Parameters READ, Profile, TableID

READ is a literal string



Returns Status Row_data

0 successful open

8 table is not open

16 attempted to read past end of table

Row_data a delimited string containing the row data



Close Service

where

where


Example:

API_rc = KAORRAPI(“Close”, profile, tableID)

Example of notification routine KAORRNF1The following example, REXX exec KAORRNF1, shows how KAORRAPI is used with the table service to extract data. The KAORRNF1 routine functions similarly to the default routine KAORRNFY.

Function close a table

Parameters CLOSE, Profile, TableID

CLOSE is a literal string



Returns Status

0 Successful close

8 table failed to close



====================================================================== Candle Corporation Copyright (c) 1985-1995 U.S.A All Rights Reserved. Use permissible by license only.====================================================================== Function Example notification exit routine. Operation Get the parameters from the invoking trap. Use the API “table” service to read each row from the table. If the user ID is for our group (parm specified) then send a TSO message. Parameters None Parameters are supplied via a KAORRAPI ‘GetParms’ call. Calls KAORRAPI Returns 0 - Successful completion >0 - Return code from KAORRAPI ======================================================================*/Do /*%EDULCNI KAOR$NFY *//* +--------------------------------------------------------------- + Start of imbed KAOR$NFY. +---------------------------------------------------------------*/ True = (1 == 1) False = \True Group_Default = “-DEFAULT-” /* Set up a default group name */ Notify_Table = “NotificationUsers” /* Notification Table */ Notify_Stem = “NotifyUser.” /* Stem name to collect results */ /* Select the appropriate RSV pool. */ Parse value KAORHSHV(“API”) with Status Reason Notify_Pool If \Status, then, Notify_Pool = “SYSTEM” /*



------------------------------------------------------------ Extract the trap parameters passed to us. ------------------------------------------------------------ We must “unwrap” the parameters returned to us. The first character in the parameter string is a unique delimeter. ------------------------------------------------------------ */ Parse value KAORRAPI(“GetParms”), with API_rc ParametersIf API_rc = 0, /* Trap parameters are available. */ then, Do Parse var Parameters delim 2, /* Extract the delimiter char */ 0 (delim) Profile, /* Use it to parse the data */ (delim) Resource, (delim) Group, (delim) WTO_Text, (delim) User_Parm, (delim) . Drop Parameters /* Done with this var. Delete it. */ /* ------------------------------------------------------- See if we need to use the default group. ------------------------------------------------------- */ If Group = ““, then, Do Group = Group_Default /* Set the default group name */ End /* ------------------------------------------------------- Call the API to extract the notification user table. Save the data in Rexx Shared Variables. -------------------------------------------------------*/ Parse value KAORRAPI(“Table”,, Profile,, Notify_Table,, “Stem”,, Notify_Stem,, Notify_Pool), with API_rc . If API_rc = 0, /* Table processing was successful. */ then, Do /*--------------------------------------------------- Copy the RSVs into local stem variables. Clean up the RSVs. We don’t need them any more.--------------------------------------------------- */ Call SHARVGET Notify_Pool, Notify_Stem Call SHARVDEL Notify_Pool, Notify_Stem /*



--------------------------------------------------- Check each notification row and if it is for our group notify that user. ---------------------------------------------------*/ Do Row = 1 to NotifyUser.0 Parse var NotifyUser.Row delim 2, 0 (delim) GroupName, (delim) UserID, (delim) . If Group = GroupName, then, Do /* Notify the user via “SEND”. */ “OPER”, “‘SEND ‘’” ||, “RECOVERY RETRY LIMIT REACHED FOR” Resource ||, “‘’,USER=(“UserID”)’” /* Log the operation */ Say “--Notifying” UserID “in group” Group Say “--for recovery error:” WTO_Text Say “--User parms:” User_Parm End End Row Drop Row End End /* GetParms */ Return_value = API_rc /* Set the result */ /* +--------------------------------------------------------------- + End of imbed KAOR$NFY. +---------------------------------------------------------------*/ Return Return_valueEnd/*.*********************************



Example of notification routine KAORRNF2The following example, REXX exec KAORRNF2, shows how KAORRAPI is used with the OPEN, READ, and CLOSE functions of the table services.

====================================================================== Candle Corporation Copyright (c) 1985-1995 U.S.A All Rights Reserved. Use permissible by license only.====================================================================== Function Example notification exit routine. Operation Get the parameters from the invoking trap. Open the user notification table. Read each row from the table. If the user ID is for our group (parm specified) then send a TSO message. Close the user notification table. Parameters None Parameters are supplied via a KAORRAPI ‘GetParms’ call. Calls KAORRAPI Returns 0 - Successful completion >0 - Error code from KAORRAPI ======================================================================*/Do True = (1 == 1) False = \True

Group_Default = “-DEFAULT-” /* Set up a default group name */ Notify_Table = “NotificationUsers” /* Notification Table */ /*------------------------------------------------------------ Extract the trap parameters passed to us. ------------------------------------------------------------ We must “unwrap” the parameters returned to us. The first character in the parameter string is a unique delimeter. ------------------------------------------------------------ */



Parse value KAORRAPI(“GetParms”), with API_rc Parameters If API_rc = 0, /* Trap parameters are available. */ then, Do Parse var Parameters delim 2, /* Extract the delimiter char */ 0 (delim) Profile, /* Use it to parse the data */ (delim) Resource, (delim) Group, (delim) WTO_Text, (delim) User_Parm, (delim) .

Drop Parameters /* Done with this var. Delete it. */

/*

------------------------------------------------------- See if we need to use the default group. -------------------------------------------------------*/ If Group = ““, then, Do Group = Group_Default /* Set the default group name */ End /* ------------------------------------------------------- Open the TSO user ID table for this profile. Save the number of rows in table. ------------------------------------------------------- */ Parse value KAORRAPI(“Open”, Profile, Notify_Table), with API_rc Rows . If API_rc = 0, /* Table open was successful. */ then, Do /* --------------------------------------------------- Read each notification row and if it is for our group notify that user. --------------------------------------------------- */ Do Rows Parse value KAORRAPI(“Read”, Profile, Notify_Table), with API_rc RowData If API_rc \= 0, /* Bad read. Bail out. */ then, Leave /* Rows */

Parse var RowData delim 2, 0 (delim) GroupName, (delim) UserID, (delim) .



Drop RowData /* Done with this var. Delete it. */ If Group = GroupName, then, Do /* Notify the user via “SEND”. */ “OPER”, “‘SEND ‘’” ||, “RECOVERY RETRY LIMIT REACHED FOR” Resource ||, “‘’,USER=(“UserID”)’”

/* Log the operation */ Say “--Notifying” UserID “in group” Group Say “--for recovery error” WTO_Text Say “--User parms:” User_Parm End End /* Rows */

/* --------------------------------------------------- Close the TSO user ID table. --------------------------------------------------- */ Call KAORRAPI “Close”, Profile, Notify_Table End /* Open */ End /* GetParms */ Return API_rcEnd/*

Guide to Candle Customer Support 225

Guide to CandleCustomer Support

IntroductionCandle Corporation is committed to producing top-quality software products and services. To assist you with making effective use of our products in your business environment, Candle is also committed to providing easy-to-use, responsive customer support.

Precision, speed, availability, predictability—these terms describe our products and Customer Support services.

Included in this Guide to Candle Customer Support is information about the following:

Base Maintenance Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226– Telephone Support

– eSupport

– Description of Severity Levels

– Service-level objectives

– Recording and monitoring calls for quality purposes

– Customer Support Escalations

– Above and Beyond

Enhanced Support Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230– Assigned Support Center Representative (ASCR)

– Maintenance Assessment Services (MAS)

– Multi-Services Manager (MSM)

Customer Support Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231– Link to Worldwide Support Telephone and E-mail information

D

Base Maintenance Plan



OverviewCandle offers a comprehensive Base Maintenance Plan to ensure that you realize the greatest value possible from your Candle software investments. We have more than 200 technicians providing support worldwide, committed to being responsive and to providing expedient resolutions to support requests. Technicians are available worldwide at all times during the local business day. In the event of an after-hours or weekend emergency, our computerized call management and forwarding system will ensure that a technician responds to Severity One situations within one hour. For customers outside of North America, after-hours and weekend support is provided in English language only by Candle Customer Support technicians located in the United States.

Telephone supportCandle provides consistently reliable levels of service—thanks to our worldwide support network of dedicated experts trained for specific products and operating systems. You will always work with a professional who truly understands your problem.

We use an online interactive problem management system to log and track all customer-reported support requests. We give your support request immediate attention by routing the issue to the appropriate technical resource, regardless of geographic location.

Level 0 Support is where your call to Candle Customer Support is first handled. Your support request is recorded in our problem management system, then transferred to the appropriate Level 1 support team. We provide Level 0 manual interaction with our customers because we support more than 170 products. We feel our customers would prefer personal interaction to a complex VRU or IVR selection menu.

Level 1 Support is the service provided for initial support requests. Our Level 1 team offers problem determination assistance, problem analysis, problem resolutions, installation assistance, and preventative and corrective service information. They also provide product usage assistance.

Level 2 Support is engaged if Level 1 cannot provide a resolution to your problem. Our Level 2 technicians are equipped to analyze and reproduce errors or to determine that an error is not reproducible. Problems that cannot be resolved by Level 2 are escalated to Candle’s Level 3 R&D support team.

Level 3 Support is engaged if a problem is identified in Candle product code. At Level 3, efforts are made to provide error correction, circumvention or notification that a correction or circumvention is not available. Level 3 support provides available maintenance modifications and maintenance delivery to correct appropriate documentation or product code errors.



eSupportIn order to facilitate the support process, Candle also provides eSupport, an electronic full-service information and customer support facility, using the World Wide Web at www.candle.com/support/. eSupport allows you to open a new service request and update existing service requests, as well as update information in your customer profile. New and updated service requests are queued to a support technician for immediate action. And we can respond to your request electronically or by telephone—it is your choice.

eSupport also contains a continually expanding knowledge base that customers can tap into at any time for self-service access to product and maintenance information.

The Candle Web Site and eSupport can be accessed 24 hours a day, 7 days a week by using your authorized Candle user ID and password.

Description of Candle severity levelsResponses to customer-reported product issues and usage questions are prioritized within Candle according to Severity Code assignment. Customers set their own Severity Levels when contacting a support center. This ensures that we respond according to your individual business requirements.

Severity 1 Crisis

A crisis affects your ability to conduct business, and no procedural workaround exists. The system or application may be down.

Severity 2High

A high-impact problem indicates significant business effect to you. The program is usable but severely limited.

Severity 3Moderate

A moderate-impact problem involves partial, non-critical functionality loss or a reasonable workaround to the problem. A “fix” may be provided in a future release.

Severity 4Low

A low-impact problem is a “how-to” or an advisory question.

Severity 5Enhancement Request

This is a request for software or documentation enhancement. Our business units review all requests for possible incorporation into a future release of the product.

http://www.candle.com/support/



Candle has established the following service-level objectives:

Recording and Monitoring Calls for Quality PurposesCandle is committed to customer satisfaction. To ensure that our customers receive high levels of service, quality and professionalism, we’ll monitor and possibly record incoming and outgoing Customer Support calls. The information gleaned from these calls will help us serve you better. If you prefer that your telephone call with Candle Customer Support in North America not be monitored or recorded, please advise the representative when you call us at (800) 328-1811 or (310) 535-3636.

Customer Support EscalationsCandle Customer Support is committed to achieving high satisfaction ratings from our customers. However, we realize that you may occasionally have support issues that need to be escalated to Candle management. In those instances, we offer the following simple escalation procedure:

If you experience dissatisfaction with Candle Customer Support at any time, please escalate your concern by calling the Candle support location closest to you. Ask to speak to a Customer Support manager. During standard business hours, a Customer Support manager will be available to talk with you or will return your call. If you elect to hold for a manager, you will be connected with someone as soon as possible. If you wish a return call, please tell the Candle representative coordinating your call when you will be available. After contacting you, the Customer Support manager will develop an action plan to resolve your issue. All escalations or complaints received about support issues are logged and tracked to ensure responsiveness and closure.

Call Status Severity 1 Goal

Severity 2 Goal

Severity 3 Goal

Severity 4 Goal

Severity 5Goal

First Call Time to Answer

90% within one minute

Level 1 Response

(Normal Business Hours)

90% within 5 minutes

90% within one hour

Level 2 Response

(Normal Business Hours)

Warm Transfer

90% within two hours

90% within eight hours

Scheduled follow-up (status update)

Hourly or as agreed

Daily or as agreed

Weekly or as agreed Notification is made when an enhancement is incorporated into a generally available product.

Notification is made when a fix is incorporated into a generally available product.

The above information is for guideline purposes only. Candle does not guarantee or warrant the above service levels. This information is valid as of October 1999 and is subject to change without prior notice.



Above and BeyondWhat differentiates Candle’s support services from our competitors? We go the extra mile by offering the following as part of our Base Maintenance Plan:

n Unlimited multi-language defect, installation and operations support

n eSupport using the World Wide Web

n Regularly scheduled product updates and maintenance provided at no additional charge

n Over 200 specialized technicians providing expert support for your Candle products

Enhanced Support Services


Enhanced Support Services

OverviewOur Base Maintenance Plan provides a high level of software support in a packaged offering. However, in addition to this plan, we have additional fee-based support services to meet unique customer needs.

The following are some examples of our added-value support services:

n Assigned Support Center Representative Services (ASCR)

– An assigned focal point for managing support escalation needs

– Proactive notification of available software fixes

– Proactive notification of product version updates

– Weekly conference calls with your ASCR to review active problem records

– Monthly performance reviews of Candle Customer Support service levels

– Optional on-site visits (extra charges may apply)

n Maintenance Assessment Service (MAS)

– On-site assessment services

– Advice about product maintenance and implementation

– Training your staff to develop efficient and focused procedures to reduce overall cost of ownership of your Candle software products

– Analysis of your Candle product environment: versions, updates, code correction history, incident history and product configurations

– Reviews to ensure that purchased Candle products and solutions are used effectively

n Multi-Services Manager (MSM)

Multi-Services Manager provides highly valued services to customers requiring on-site full time expertise to complement their technical resources.

– Dedicated on-site Candle resource (6 months or one year) at your site to help ensure maximum use and effectiveness of your Candle products

– Liaison for all Candle product support activities, coordination and assistance with implementation of all product updates and maintenance releases

– Works with your staff to understand business needs and systems requirements

– Possesses technical and systems management skills to enhance your staff ’s knowledge and expertise

– Other projects as defined in Statement of Work for MSM services


Customer Support Contact Information


Link to Worldwide Support Telephone and E-mail informationTo contact Customer Support, the current list of telephone numbers and e-mail addresses can be found on the Candle Web site, www.candle.com/support/.

Select Support Contacts from the list on the left of the page.

http://www.candle.com/support/

Index 233

AACTIVATE command 109Add Traps panel 158Adobe portable document format 9AF 15AF/OPERATOR Variables panel 192Always Active resources

managing 189application programming interface

described 211tables supported with 211

ASCRassigned support center representative 230

assigned support center representativeASCR 230

automationAF/OPERATOR defined 15function keys 23resource management for, defined 16Trap group management for, defined 16

CCHECK command 110check routine

KAORRCHK, Candle default example 207overview

writing 206CMD trap

defined 148defining 166

cold and warm startsdifferences between 199

commandREFRESH 198

commands 201RCF 105

Configuration and Customization Guidemultiple address spaces 201simulating 201

console management 21list of console actions AF/OPERATOR manages 17overview 21trap, defined 21

controlling sysplex membersusing Sysplex Console 169

CUA standards 23customer support

base maintenance plan 226contact information 231enhanced support services 230eSupport 227severity levels 227telephone support 226

Ddebugging AF/OPERATOR 201DISABLE command 112duling is affected when RSM stops 188

EeSupport

customer support 227

Ffields, match variables 193function keys, use of 23

HHelp

RCF 22using 24

historical logSee RETAIN*VIEW

IINACTIVATE command 113INITIATE command 114ISPF

running under OG*TSO 203

KKAOIXEV1 panel 158KAORRAPI, described 211KAORRCHK default check routine 207KAORRNFY default notification routine 211

LLIST command 117log

historicalusing RETAIN*VIEW

message log 190

Index


Mmaintenance assessment service

MAS 230MAS

maintenance assessment service 230match variables 193message log, using 190MONITOR command 119monitoring AF/OPERATOR 190MSM

multi-services manager 230multi-services manager

MSM 230

NNOMONITOR command 120notification

routine 211notification routine

KAORRAPI, described 211KAORRNF1, example of 218KAORRNF2, example of 222KAORRNFY, described 211overview 211

OOG*TSO

accessing 203exiting 203under TSO 203using

simulated Configuration and Customization Guide 203

OMEGAMON exception trap 149online help, using 24overseeing AF/OPERATOR 190

Ppanel 192

add TrapsKAOIXEV1 158

AF/OPERATOR Variables 192Defined Systems, for RETAIN*VIEW 191RETAIN*VIEW 192

PREDECESSOR command 121printing problems 9profile

test 202PURGE command 123

RRCF 105

RCF commandsACTIVATE 109CHECK 110DISABLE 112e 125INACTIVATE 113INITIATE 114LIST 117MONITOR 119NOMONITOR 120PREDECESSOR 121PURGE 123RECOVERY 124RESET 126SCHEDULE 127SET 128SHOW 130START 136STATUS 138STOP 139SUCCESSOR 141TERMINATE 143TRAPGROUP 144

RECOVERY command 124REFRESH command 125Refresh command 198refreshing RSM

from the MVS consolefrom the user interface 186

refreshing the RSMRCF REFRESH

REFRESH FORCE 186RESET command 126resource

definition, defined 18writing a check routine 206writing a notification routine 211

Resource Control Facility (RCF) 105overview 22using help for 22

resource management 19active state 18inactive state 18list of resources AF/OPERATOR controls 16managing resources, 18resource definition, defined 18resource, definition of 18started state 18stopped state 18

resource manager 211resources

Always Active 189managing 189

Index 235

RETAIN*VIEW 190historical log datasets 190message or command information 191purpose of

RETAIN*VIEW panel 192REXX exec

check routine 206notification routine

recovery failure processing 211routines

check 206notification

recovery 211RSM

stopping 187RSM considerations 188RSM, defined 20running AF/OPERATOR UI alone 182runtime environment

components 20event processor (EV), defined 20Resource Control Facility (RCF), defined

Resource State Manager (RSM), defined 20scheduler (SC), defined 20

SSCHEDULE command 127schedules

stopping RSM and 188SEND message 211SET command 128severity levels

customer support 227SHOW command 130simulated environment, OG*TSO 203simulating

commands 201Configuration and Customization Guide 201WTOs 201

spool full condition, setting trap for 158spool full WTO trap, defining 158START command 136starting AF/OPERATOR 182starting the RSM

procedure for 182STATUS command 138STOP command 139stopping AF/OPERATOR

verifying AF/OPERATOR has stopped 187stopping RSM

and scheduling 188procedure for 187

stopping the RSM 187

SUCCESSOR command 141Sysplex Console

using to control sysplex members 169

Ttelephone support

customer support 226TERMINATE command 143test profile 202testing

AF/OPERATOR 201traps in OG*TSO

REXX execs in OG*TSO 203Time of Day (TOD) trap

defined 148TOD trap 163

defined 148trap group management

defined 16Trap Group Manager

defined 148TRAPGROUP command 144traps

CMD 148defined 148defining a CMD trap 166defining a TOD trap 164spool full WTO trap, defining 158terminology

how traps work 148testing in OG*TSO 203TOD 148types 148WTO 149xtype

OMEGAMON exception 149TSO

running under OG*TSO 203user ID, for notification

users 211

Uuser interface overview 23users

TSO 211

Vverifying

command function 201trap function 201


WWrite-To-Operator (WTO) trap 149WTO

simulating 201trap 149, 158

Xxtype trap 149

af/operator user interface guide v340

Documents