started task manager · started task manager is a component of the af/operator ® application...

Started Task ManagerAF/OPERATOR®

Version 340

GC32-9154-00

September 2002

Candle Corporation201 North Douglas Street

El Segundo, California 90245-9796

2 AF/OPERATOR Started Task Manager Version 340

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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Adobe Portable Document Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7Documentation Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

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

Chapter 1. What Is Started Task Manager?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Some Background. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16How Started Task Manager Works. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20The Recovery Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

Chapter 2. The ISPF Dialog Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Overview of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28Running the Started Task Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29Adding or Updating Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32Using the Startup Defaults Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37Using Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41

Chapter 3. Using the Service Subroutines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Starting the Service Subroutines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44Monitoring Started Task Manager Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45

Appendix A. Guide to Candle Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Base Maintenance Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48Enhanced Support Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52Customer Support Contact Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Contents

Preface 5

Preface

About This BookStarted Task Manager is a component of the AF/OPERATOR® Application Library that helps you manage long-running interdependent tasks on your MVS systems. This guide describes how to implement and customize Started Task Manager for your site. It assumes you have a working knowledge of data center operations and procedures and that AF/OPERATOR has been installed in your enterprise.

Documentation set informationThe following manuals comprise the AF/OPERATOR documentation set:

n AF/OPERATOR Configuration and Customization Guide

n AF/OPERATOR User’s Guide

n AF/OPERATOR Command Reference 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

n Candle Product Messages Manual

Where to look for more informationFor more information related to this product and other related products, 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 and the other related products.

P


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 Started Task Manager Version 340" in the subject line.

Preface 7

Adobe Portable Document Format

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



Documentation Conventions



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

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

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

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

LOGON APPLID (cccccccc)

In the above example, you type LOGON APPLID followed by an application identifier (represented by cccccccc) within parentheses.

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

Preface 9


SymbolsThe following symbols may appear in command syntax:

Table 1. Symbols in Command Syntax

Symbol Usage

| The “or” symbol is used to denote a choice. Either the argument on the left or the argument on the right may be used. Example:

YES | NOIn this example, YES or NO may be specified.

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

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

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

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

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

_ Default values are underscored. Example:

COPY infile outfile - [COMPRESS={YES | NO}]In this example, the COMPRESS keyword is optional. If specified, the only valid values are YES or NO. If omitted, the default is YES.

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.

What Is Started Task Manager? 15

What Is Started Task Manager?

OverviewThis chapter describes the Started Task Manager and its use.

Chapter ContentsSome Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

The Problem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16The Solution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

How Started Task Manager Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Components of Started Task Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Resource Management Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

The Recovery Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Events That Trigger Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23The Recovery Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23What’s Next? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

1

Some Background


Some BackgroundIn the early days of computing, all programs were run as batch jobs: the application took your input data, processed the data, gave the new data back in some form of output, and then terminated. As computers and operating systems became more sophisticated, an additional way to run programs came into existence. Called started tasks, they differed from batch jobs in that they did not terminate after giving back output; instead, they stayed active, waiting for another block of data to process. Once a started task was initiated, it would run until it abended or was manually shut down.

Started tasks made the data center much more efficient because they formed the basis for realtime online computing. In a different respect, however, they have grown to be a common source of problems for data center personnel. Today’s multiprocessing environments such as MVS offer the ability to run many started tasks concurrently. These tasks are often interdependent: the order in which they are started and shutdown is critical. To complicate matters further, started tasks may be brought up in the correct order by the MVS COMMND00 facility when the system is IPLed, but then a subset of those tasks must be shutdown at the end of a shift so that batch jobs can be run overnight. The next morning, those tasks must be restarted, and various factors must be manually checked by data center personnel to ensure the tasks will start properly.

The ProblemIt is easy for data center personnel to define when a started task should be running and to define what the status of other system programs and hardware must be for that task to run properly. Unfortunately, it can be difficult and time consuming to manually check the interdependencies before starting or stopping a task. Even worse is the case where a started task abends during a shift where the people on duty aren’t familiar with all the interdependencies.

The advent of sophisticated automation software such as AF/OPERATOR allowed data center personnel to write their own custom automation programs to manage resources such as started tasks. But this in itself didn’t completely solve the problem because many people don’t have the time or desire to write complex automation programs.

The SolutionStarted Task Manager is a component of AF/OPERATOR that writes the automation programs for you, making it easy to use the full power of AF/OPERATOR for managing a specific type of data center resource—started tasks. Figure 1 on page 17 illustrates the resources that can and cannot be controlled by the Started Task Manager.


Some Background

FIGURE 1. Resources that Started Task Manager Can and Cannot Control

As Figure 2 on page 17 shows, all you need to do is decide which started tasks (called resources in the rest of this guide) you want to manage with Started Task Manager, and then you define the desired parameters of each resource at Started Task Manager’s panel entry fields.

FIGURE 2. What You Must Tell Started Task Manager

Some Background


Started Task Manager uses this information to build several resource definition tables in ISPF table datasets and to generate AF/OPERATOR command files (automation programs executed by AF/OPERATOR) that automatically make sure your resources are active when they should be. These command files generated by Started Task Manager are known as resource command files.

FIGURE 3. What Started Task Manager Does

The command files generated by Started Task Manager perform many functions. They can:

n start and stop resources based on hour and day of week

n verify the existence of predecessors (other resources that must be active) before attempting to start a resource, and the non-existence of successors (other resources for which this one is a predecessor) before attempting to stop a resource


Some Background

n automatically attempt to restart abended resources, optionally executing several user-defined command files both before attempting recovery and after all recovery attempts fail

n issue messages that:

– verify successful starting of a resource

– warn operators before stopping a resource and allow them to delay the shutdown

– notify a list of users that recovery attempts have failed

As you can see, the automation programs written with Started Task Manager have enough basic features to automate many operator tasks, such as the monitoring of resource activity. Additionally, due to the open-ended nature of the AF/OPERATOR language used by Started Task Manager, you can easily extend Started Task Manager’s functionality by linking the command files it generates to others that you have written using the AF/OPERATOR or REXX languages.

How Started Task Manager Works


How Started Task Manager WorksThe section “What Is Started Task Manager?” on page 15 showed in very broad terms how Started Task Manager operates. This section contains a more detailed overview that should prepare you to use Started Task Manager wisely and to its fullest extent.

Started Task Manager is an application that generates and executes AF/OPERATOR command files; it therefore requires AF/OPERATOR to run. This guide assumes that both AF/OPERATOR and the AF/OPERATOR Application Library have already been installed at your site.

Components of Started Task ManagerStarted Task Manager has three components: an ISPF dialog, resource command files, and service subroutines.

ISPF Dialog

The ISPF dialog presents you with a set of fill-in-the-blanks entry panels that you use to define each resource you want to manage with Started Task Manager. An example entry panel is shown in Figure 4.

FIGURE 4. Resource Definition Primary Options Panel

The chapter “The ISPF Dialog Component” on page 27 describes using the ISPF dialog in detail.

!Candle AF/OPERATOR - STARTED TASK MANAGER Version V340 COMMAND ===>_ RESOURCE DEFINITION ========================================================== More: + RESOURCE....... ________ SYSID.... ________ DEFINITION..... _________________________________________________ ==================================================================== PRIMARY OPTIONS Start time ... ________ Days...Mon Tue Wed Thu Fri Sat Sun End time ..... ________ Days...Mon Tue Wed Thu Fri Sat Sun Start Command. ____________________________________________ Verify msg..... ____________________________________________ Stop Command... __________________________________________ Stop warn time. ________ Extend. YES Predecessors... ________ ________ ________ Retries........ __ Wait time...... ________ PF1=Help PF3=Exit PF7=Bkwd PF8=Fwd



Resource Command Files

When you finish defining a resource with the ISPF dialog, Started Task Manager stores the information in a set of three ISPF tables and then generates an AF/OPERATOR command file, called a resource command file (prefix.RKANCMD), to manage the defined resource. Every time you add or update a resource, the ISPF dialog generates (or regenerates) a resource command file to manage that resource accordingly. The resource command files, in conjunction with the Started Task Manager service subroutines, will keep your resources active without any additional control or supervision on your part. These resource command files are just like any other AF/OPERATOR command file except:

n They can be controlled as a group by the Started Task Manager service subroutines. This is the recommended method, and is described in “Using the Service Subroutines” on page 43.

n Users familiar with the AF/OPERATOR command language and the Automation Facility automation language can, with some modifications, directly incorporate these resource command files into their own automation scenarios. This alternative is not recommended unless you are an accomplished automation programmer and you fully understand the interdependencies between resources.

The Service Subroutines

The third component is a special group of AF/OPERATOR command files called the service subroutines. These subroutines are used to start, stop, and perform other management functions on the resource command files created by Started Task Manager.

The service subroutines are divided into two categories: control subroutines and utility subroutines.

n The control subroutines start and stop resource command files, and also check for predecessors and successors. Because these subroutines must know about all the resource interdependencies, Started Task Manager regenerates them every time you add or update a resource.

n The utility subroutines perform various tasks such as issuing warning messages before a resource is stopped, calculating what time to issue a warning message, and so on. Since they do not need to know about resource interdependencies, Started Task Manager regenerates them only when you request it, as you would do after upgrading to a new release of Started Task Manager.

The chapter “Using the Service Subroutines” on page 43 describes using the service subroutines in detail.



ISPF Tables

The resource command files and service subroutines generated by Started Task Manager are all based on information stored in a set of ISPF tables. These tables are updated by Started Task Manager every time you add or update a resource. There are three tables:

The tables are stored in the output table library prefix.RKANISP with the ddname ALTABL that was allocated the first time you installed the Application Library

Resource Management LimitationsStarted Task Manager can manage only resources that have been specifically defined to it. Stated another way, it can only keep track of the resources that it starts and stops: it is not aware of resources started with any other job scheduler or with resources started manually at a system console.

For example, assume that for a given resource (Task A) defined to Started Task Manager, one attribute is that a different resource (Task B) must already be running. In this case Task B is known as a predecessor. If Task B had been started manually from a console, then when Started Task Manager attempts to start Task A, it will fail. This happens because Started Task Manager has no record of the predecessor (Task B) being started. When planning your implementation of Started Task Manager, you should make sure that all interdependent resources are defined to and controlled by Started Task Manager.

Resource Table Contains the resource definitions

Predecessor Table Contains a list of the resources that must be active before a given resource can be started

Successor Table Contains a list of the resources that can be started only after this resource.


The Recovery Process

The Recovery ProcessSo far, you’ve learned that Started Task Manager can be used to start and stop your resources, and you have been given a brief description of the components responsible for managing your resources. But all these things just amount to a task manager like any other——there doesn’t appear to be that much difference between Started Task Manager and the MVS COMMND00 command, for instance.

What really distinguishes Started Task Manager from any other task manager is that it utilizes a very flexible and powerful recovery process to restart resources. Unlike other task managers, Started Task Manager gives you broad control over task recovery.

In order for you to exploit the recovery process fully, you should read the following subsections carefully to understand how the process works.

Events That Trigger RecoveryThe recovery process comes into play only if a resource becomes inactive during a time period when it should be active. Started Task Manager determines whether such an event has occurred by constantly watching for three different MVS/JES messages. The first two messages are straightforward and apply to active resources that suddenly become inactive. The third is more flexible and can be used for a variety of situations. You specify the messages when defining the recovery options for a resource as described in “Recovery Options” on page 34. For the purposes of this discussion, however, you should know that the three messages are:

The Recovery FlowFigure 5 on page 24 illustrates the flow of events during the recovery process. As you read the diagram, be aware of the following notes:

n Some of the decision boxes check for true/false conditions, others for return codes from a command file, and others for operator replies entered at a console.

n The retry counter is a mechanism that measures the number of retries attempted during a given time period. It is reset to zero only once during the retry time period; it is not reset to zero every time the recovery process is initiated by one of the three messages described in “Events That Trigger Recovery” on page 23. For example, if your retry counter is set to fire no more than twice in one hour, and a given resource abends three times in one hour, Started Task Manager will not initiate recovery for the third abend message.

Abend Message This signals that a resource has abended.

End Message This signals that a resource has terminated. While this is not normally a problem in itself, it is a problem if it happens during a time span when the resource should be active.

User-Defined Message

This signals any event that should cause Started Task Manager to initiate the recovery process for a given resource. While the first two messages must be defined for every resource, this message is optional.



FIGURE 5. The Started Task Manager Recovery Process

n Started Task Manager attempts to initiate the recovery process every time it encounters one of the three messages described earlier (unless the retry counter has been exceeded). This can pose a problem when a resource abends, because MVS always issues two messages per abend: a job abend message followed by a job end message. Since Started Task Manager interprets each of these messages as a separate event, it would therefore



initiate the recovery process twice and increment the retry counter twice for a single abend. An automation programmer who understands your system structure can use the recovery exit command file to check for events like this and take the appropriate action. This command file is described below.

n The three command files that are executed at various points of the recovery process are all optional; if you do not define these as parameters for a given resource, Started Task Manager will still perform a basic restart of the resource. These command files allow you to augment the recovery process with special routines and tests of your own. While each command file can be practically any AF/OPERATOR command file, there are some special variables and return codes associated with each one that will shape the way you design and use them:

Problem Record Command File

Candle recommends you use this command file to interface with your site’s problem management system. To help you do this, the Started Task Manager service subroutines create three special AF/OPERATOR global variables available to this command file in addition to all the standard AF/OPERATOR global and system variables available to any command file. These variables are:

PMNAME Contains the name of the resource

PMABEND Contains the 8-character message ID that initiated the Started Task Manager recovery process

PMMSG Contains the 80-character text of the message that initiated the Started Task Manager recovery process

There are no return codes expected from this command file by the Started Task Manager recovery process. Note that this command file is executed every time you step through the recovery process. For example, if you had defined a resource to attempt three recovery retries, then the problem record command file may be executed as many as four times if all recovery efforts fail.

Note: Candle supplies a model problem record command file as one of the utility subroutines in your environment’s command file library. The Candle-supplied name for this model is @RPMSAMP.

Recovery Exit Command File

This command file gives you a chance to perform some action before Started Task Manager actually attempts to restart the resource. Depending on the nature of that action, you may not want Started Task Manager to subsequently attempt to restart the resource. To help you use this command file as a decision point in the recovery process, Started Task Manager expects a return code from this command file, which it will act upon as follows:



What’s Next?Now that you understand what Started Task Manager is and have been given an overview of its operation, you are ready to put it to work in your data center. The remaining two chapters will describe how to use the ISPF dialog and service subroutines.

0 Indicates that Started Task Manager should attempt to restart the resource

4 Indicates that Started Task Manager should do nothing further; no messages are issued.

Any Other RC Indicates that Started Task Manager should end the recovery process and issue a WTO notifying the operator that the resource has failed recovery

Notification Command File

Candle recommends you use this command file to augment the standard user notification list. To help you do this, the Started Task Mananger service subroutines create a special AF/OPERATOR global variable available in addition to all the standard global variables available to any command file. This variable is called RNAME, and it specifies the resource name.

The ISPF Dialog Component 27

The ISPF Dialog Component

OverviewIn this chapter you will learn how to use Started Task Manager’s ISPF dialog component to define resources and generate resource command files. If you find any aspect of this component confusing, you may find it helpful to review the chapter “What Is Started Task Manager?” on page 15, especially the section “How Started Task Manager Works” on page 20.

This chapter assumes that Started Task Manager is installed and available.

Chapter ContentsOverview of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Running the Started Task Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Adding or Updating Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Saving Resource Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Primary Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Recovery Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Additional Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Using the Startup Defaults Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Configuring the Started Task Manager Environment . . . . . . . . . . . . . . . . . . . . . . . . . . 38Refreshing Subroutines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Using Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

2

Overview of Operation


Overview of OperationThere are three parts to the ISPF dialog: a resource list, a group of resource definition panels, and a startup defaults panel. The resource list serves as an entry point; from there you navigate to either the resource definition or startup defaults panels depending on the operation you want to perform.

You use the resource definition panels every time you add or update a resource to Started Task Manager, which is the task you’ll perform most often. For instructions on using the resource definition panels, refer to the section “Task Resource List Options” on page 30.

You use the startup defaults panel:

n to specify configuration information the first time Started Task Manager is used at your site

n to refresh the utility subroutines when you upgrade to a new release of Started Task Manager

For instructions on using the startup defaults panel, refer to the section “Using the Startup Defaults Panel” on page 37.


Running the Started Task Manager

Running the Started Task ManagerUse the following procedure to run the Started Task Manager:

1. From the AO340 User Interface screen (shown in Figure 6 on page 29), select the Tools pull-down menu.

FIGURE 6. AO340 User Interface Panel

2. Key in 7.Note: If you are running Started Task Manager for the first time, the Task Manager Startup Defaults panel is displayed. For instructions on completing this panel, see “Using the Startup Defaults Panel” on page 37.

Configuration Automation Tools Help -------------------------- .-----------------------------. --------------- AF | _ 1. OG*TSO... | | 2. RETAIN*VIEW.......... | | 3. OG Statistics........ | Current Profile . . : KAO0 | 4. Display Status....... | Authorization Group : -DEF | 5. Match*Maker.......... | AAAAA OOOOO 33 | 6. Message Manager...... | AAAAAAA OOOOOOO 333 | 7. Started Task Manager. | AA AA OO OO 33 ‘-----------------------------’ AA AA OO OO 33 44 44 00 00 AA AA OO OO 33 44 44 00 00 Press F10 to AAAAAAAAA OO OO 333333 444444444 00 00 Select a Function AAAAAAAAA OO OO 333333 444444444 00 00 AA AA OO OO 33 44 00 00 AA AA OO OO 33 44 00 00 AA AA OO OO 33 44 0 00 AA AA OOOOOOO 33333333 44 0000000 AA AA OOOOO 333333 44 00000 COMMAND ===>------------------------------------------------------------------------------



FIGURE 7. Task Resource List Panel

Task Resource List Options

This panel is the entry point for all panels of the ISPF dialog. All functions of the ISPF dialog are available by choosing one of the following options. Online Help is available at any panel; see the section “Using Help” on page 41 for details on using Help.

Add To add a new resource to the list, type the letter A in the command field at the top of the panel and then press Enter. The section “Adding or Updating Resources” on page 32 describes how to fill out the resource definition panels. When the panels are saved, the control subroutines will be regenerated and a new resource command file will be generated. Note that you must subsequently restart the Started Task Manager service subroutines for the changes to take effect on your system.

Update To update a currently defined resource, type the letter S beside the resource whose definition you want to change and then press Enter. The section “Adding or Updating Resources” on page 32 describes how to fill out the resource definition panels. As when adding a new resource, changes do not take effect until you restart the service subroutines.

!Candle AF/OPERATOR - STARTED TASK MANAGER Row 4 from 8 TASK RESOURCE LIST Enter A for Add new task, P for Profile update on the Command Line above. Enter D for Delete, S for Update, or B for Browse below. RESOURCE SYSID START TIME END TIME START DAYS -------- -------- ---------- -------- -------------------------------- _ TASK1 * M T W T F S S _ TASK2 * M T W T F S S _ TASK3 * M T W T F S S _ TASK4 SYSG 07:00:00 16:00:00 M T W T F _ TASK5 SYSG 08:00:00 12:00:00 S S ******************************* Bottom of data ***************************** COMMAND ===>-----------------------------------------------------------------------------



To change the Started Task Manager startup defaults, type the letter P in the command field and press Enter. The section “Using the Startup Defaults Panel” on page 37 describes how to fill out the the Startup Defaults panel. You would use this option if you need to regenerate damaged utility subroutines or refresh them from a new version of Started Task Manager.

Changing your startup defaults has no effect on any currently running Started Task Manager service subroutines and resource command files

Delete To delete a resource, type the letter D beside the desired resource and then press Enter. To make sure you want to delete the chosen resource, Started Task Manager displays the name of the associated resource command file and gives you the option of cancelling the deletion by pressing PF3. If you instead press Enter, both the ISPF table definition and the resource command file will be deleted, and the control subroutines will be regenerated. Note that you must subsequently restart the Started Task Manager service subroutines for the changes to take effect on your system.

Browse To browse the defined attributes of a resource, type the letter B beside the desired resource and then press Enter. Use PF7 and PF8 to view the various panels. Note that you can only view the panels; you cannot edit them with this option.

Adding or Updating Resources


Adding or Updating ResourcesOn the Task Resource List Panel (Figure 7 on page 30), if you choose A to add or S to update a resource, the Resource Definition Primary Options panel is displayed.

FIGURE 8. Resource Definition Primary Options Panel

There are three resource definition options panels; this one and two others: Recovery Options and Additional Options. They are shown in Figure 9 on page 34 and Figure 10 on page 36. You scroll between the panels using PF7 and PF8. Fill out all three panels as described in the following pages to add or update the resource.

Saving Resource DefinitionsWhen you’ve completed all the panels as described in the next few pages, press Enter to save your entries, and then press PF3 to leave the resource definition panels. Started Task Manager displays the name of the resource command file that will be generated from your entries. Press Enter again to generate the command file, or press PF3 to exit the resource definition panels without generating any code.

Important

You must properly save your entries before exiting these panels. Otherwise, your definitions will be lost and no command files will be generated. Also, you must restart the service subroutines for your changes to take effect (see “Using the Service Subroutines” on page 43).

!Candle AF/OPERATOR - STARTED TASK MANAGER Version V340 COMMAND ===>_ RESOURCE DEFINITION ========================================================== More: + RESOURCE....... ________ SYSID.... ________ DEFINITION..... _________________________________________________ ==================================================================== PRIMARY OPTIONS Start time ... ________ Days...Mon Tue Wed Thu Fri Sat Sun End time ..... ________ Days...Mon Tue Wed Thu Fri Sat Sun Start Command. ____________________________________________ Verify msg..... ____________________________________________ Stop Command... __________________________________________ Stop warn time. ________ Extend. YES Predecessors... ________ ________ ________ Retries........ __ Wait time...... ________ PF1=Help PF3=Exit PF7=Bkwd PF8=Fwd



Primary OptionsTo fill out the Primary Options panel, enter the following information in the appropriate field. Note that each field is followed by a blank line; the length of this line determines the number of characters you can enter in that field. All fieldswith the exception of the Resource field are optional.

Resource The name of the started task to manage (Required field).

SYSID The SMF ID of the system the resource will run on.

Definition The description of the resource.

Start Time The time you want the resource to start, in the form hhh:mm:ss (24-hour military format). Use the space bar to blank out those days of the week that you do not want the resource to start.

Blank Start and End times indicate 24-hour operation; note that the resource will not actually start until you restart the Started Task Manager service subroutines.

End Time The time you want the resource to end, in the form hh:mm:ss. Use the space bar to blank out those days of the week that you do not want the resource to stop.

Note: You do not have to specify an end time for short-running or self-ending resources.

Start Command The appropriate start command for the resource you are defining. Type the command exactly as you would at a console. Only one command is allowed.

Verify Msg An IBM message you expect to receive that signifies the resource has started successfully. This message is used by Started Task Manager to determine whether the resource is active. This field is optional, but be aware that if you do not specify a message here, Started Task Manager will always assume that the resource is active.

Stop Command The appropriate stop command for the resource you are defining. Type the command exactly as you would at a console.

Stop Warn Time The amount of time, in the form hh:mm:ss, that the operator console should be notified before Started Task Manager stops a resource. This field is valid only if you specified an End Time. Leave this field blank if you do not want to warn the operator before stopping a resource.

Extend This field works in conjunction with the Stop Warn Time. Type YES (the default) if you want Started Task Manager to warn of an impending shutdown with a WTOR asking the operator if they would like to delay the shutdown. The WTOR will prompt the operator to reply N to proceed on schedule, or reply with a time in the format Hmm (where mm is minutes) by which to extend the shutdown.

Type NO in this field if you do not want to provide the operator with an opportunity to delay the shutdown.

Predecessors The names of all resources that must be active before this resource can be started.



Recovery OptionsYou scroll to the Recovery Options panel by pressing PF8 at the Primary Options panel.

FIGURE 9. Resource Definition Recovery Options Panel

Important

Started Task Manager assumes that the resources named here must also remain active until this resource is stopped.

Also, you should not name any resources here unless you have already defined them to Started Task Manager. Otherwise, Started Task Manager will not have the information needed to regenerate the control subroutines.

Retries The maximum number of times that you want Started Task Manager to check whether predecessors are active. Started Task Manager will wait for a time period (specified below) between each retry.

Wait Time The period of time which you want Started Task Manager to wait between predecessor checks. You should specify a fairly short length of time here, like 10 or 15 seconds. Use the format hh:mm:ss.

!Candle AF/OPERATOR - STARTED TASK MANAGER Version V340 COMMAND ===>_ RESOURCE DEFINITION ======================================================= More: - + RESOURCE...... ________ DEFINITION.... _________________________________________________ ================================================================== RECOVERY OPTIONS: Select recovery..... NO_ Number of retries... __ Retry time period... 00:00:00 Recovery exit cfile. _____________________________________ User notify list.... ________ ________ ________ ________ Notification cfile.. _____________________________________ Abend message ID ... ________ End message ID...... ________ User defined msg.... _____________________________________ Problem record cfile _____________________________________ PF1=Help PF3=Exit PF7=Bkwd PF8=Fwd



To fill out the Recovery Options panel, enter the following information in the appropriate field:

Select Recovery

This field determines whether the information on this panel is used by Started Task Manager. Type YES if you want Started Task Manager to initiate the recovery process for this resource if it receives one of the three messages defined below. Type NO (the default) if you do not want Started Task Manager to act on these messages.

Number of Retries

The number of times, within the retry time period specified below, that Started Task Manager will initiate the recovery process for a failed resource. There is no default. The range is from 01 to 99.

Retry Time The period of time within which you want Started Task Manager to attempt the number of retries specified above. Use the format hh:mm:ss.

Recovery Exit Cfile

The name of an AF/OPERATOR command file name to be executed during the recovery process. See the section “The Recovery Process” on page 23 for details. This field is optional.

User Notify List

The TSO user IDs of up to five users you want to notify when all recovery attempts have failed.

Notification Cfile

The name of an AF/OPERATOR command file name to be executed during the recovery process. See the section “The Recovery Process” on page 23 for details. This field is optional.

Abend Message ID

The message ID of the WTO that signifies an abend. This message will cause Started Task Manager to initiate recovery action. The default is the Job Abend Message specified in the profile definition panel described in the section “Using the Startup Defaults Panel” on page 37.

End Message ID

The message ID of the WTO that signifies a normal job end. This message will cause Started Task Manager to initiate recovery action. The default is the Job End Message specified in the profile definition panel described in the section “Using the Startup Defaults Panel” on page 37. Note that MVS always issues two messages per abend: a job abend message followed by a job end message. Since the Started Task Manager interprets each of these messages as a separate event, it will initiate the recovery process twice and increment the retry counter twice for a single abend. An automation programmer who understands your system structure can use the recovery exit command file to check for events like this and take the appropriate action.



Additional OptionsYou scroll to the Additional Options panel by pressing PF8 at the Recovery Options panel.

FIGURE 10. Resource Definition Additional Options Screen

To fill out the Additional Options panel, enter the following information in the appropriate field:

Note: If you have not entered a Start Time on the Resource Definition Primary Options screen, you cannot enter additional start or stop times on this screen.

User Defined Message

Any WTO that you want Started Task Manager to interpret as a signal to initiate recovery action. This field is optional.

Problem Record Cfile

The name of an AF/OPERATOR command file to be executed during the recovery process. See the section “The Recovery Process” on page 23 for details. This field is optional.

Start Time 2 A secondary time you want the resource to start, in the form hh:mm:ss. This field and the End time 2 field below allow you to augment your basic start and end times with split-shift or weekend run times. Use the space bar to blank out those days of the week that you do not want the resource to start.

End Time 2 A secondary time you want the resource to stop, in the form hh:mm:ss. Use the space bar to blank out those days of the week that you do not want the resource to stop.

!Candle AF/OPERATOR - STARTED TASK MANAGER Version V340 COMMAND ===>_ RESOURCE DEFINITION ======================================================== More: - RESOURCE...... ________ DEFINITION.... _________________________________________________ =================================================================== ADDITIONAL OPTIONS: Start time 2... ________ Days.. Mon Tue Wed Thu Fri Sat Sun End time 2..... ________ Days.. Mon Tue Wed Thu Fri Sat Sun You MUST use primary Start/End times first PF1=Help PF3=Exit PF7=Bkwd PF8=Fwd


Using the Startup Defaults Panel

Using the Startup Defaults PanelThe system displays the Startup Defaults panel if

n you chose option P on the Task Resource List panel (Figure 7 on page 30).

n you are running Started Task Manager for the first time.

FIGURE 11. Startup Defaults Panel

The Startup Defaults panel performs several important functions:

n It allows you to specify configuration information that will be used by Started Task Manager when generating resource command files.

– It specifies where the skeleton and command file libraries are located and the names of the ISPF tables that store the resource definitions.

– It specifies the trap, variable, and command file name prefixes that are used to distinguish Started Task Manager resource command files from Message Manager entities and other AF/OPERATOR command files. This allows resource command files to be controlled as a group by the Started Task Manager service subroutines.

The section “Configuring the Started Task Manager Environment” on page 38 describes how to fill in the fields of the Startup Defaults panel.

n It generates the subgroup of Started Task Manager service subroutines known as utility subroutines. This must be done:

– every time you install a new version of Started Task Manager

– if any of the subroutines in your command file library become damaged

!Candle AF/OPERATOR - STARTED TASK MANAGER Version 340 TASK MANAGER STARTUP DEFAULTS Enter changes below. TRAP AND VARIABLE PREFIX ===> @R 2 char Prefix to trap/vars COMMAND FILE NAME PREFIX ===> @R 2 char Prefix to command files RESOURCE TABLE NAME ===> @RCFCTAB PREDECESSOR TABLE ===> @RCFCTA1 SUCCESSOR TABLE ===> @RCFCTA2 SKELETON LIBRARY DSN ===> CANDLE.V340.TKANISP COMMAND FILE DSN ===> CANDLE.V340.RKANCMD DEFAULT JOB ABEND MSG ===> IEF450I DEFAULT JOB ENDED MSG ===> $HASP395 COMMAND ===>



Procedures for refreshing the utility subroutines are described in the section “Refreshing Subroutines” on page 40.

Profile information is stored in your ISPF profile dataset. Started Task Manager uses the following members:

Configuring the Started Task Manager EnvironmentTo configure the Started Task Manager environment, you fill in the fields of the Startup Defaults panel and then press Enter. Started Task Manager takes a few moments to create a set of service subroutines and ISPF tables for the environment. Started Task Manager then displays the Resource Definition Primary Options panel (Figure 8 on page 32) so you can start defining resources to the new environment.

If you are merely changing the configuration of an existing environment, when you complete the Startup Defaults panel and press Enter, Started Task Manager displays a message asking if you wish to regenerate subroutines. You don’t need to do this unless you are refreshing subroutines or upgrading from a new release. (See “Refreshing Subroutines” on page 40 for details.)

To fill out the Startup Defaults panel, enter the following information in the appropriate field:

TMANEDIT Contains editing and terminal characteristics for your ISPF session.

TMANPROF

Contains session and profile characteristics for your ISPF session.

Trap and Variable Prefix

Command File Name Prefix

The prefix you want Started Task Manager to apply to all AF/OPERATOR traps, variables, and command file names associated with this environment. This prefix allows the Started Task Manager service subroutines to identify and manage this environment’s resources as a group distinct from other AF/OPERATOR entities or from Message Manager entities.

Important

n The default prefix is @R. If you change the prefix (for example, from @R to @P), you must change all occurrences of the prefix to the same value. As shown in Figure 11 on page 37, the same two-character prefix is used for the Trap and Variable Prefix, Command File Prefix, Resource Table Name, Predecessor Table, and Successor Table fields.

n You must be absolutely sure that you do not use any prefixes associated with Message Manager at your site. (The Candle default prefix for Message Manager entities is @M.) If you use the same prefix, all your command files and ISPF tables for both Started Task Manager and Message Manager may be corrupted.



Resource Table Name

Predecessor Table

Successor Table

The names of the ISPF tables in which you want to store this environment’s resource definitions. Candle recommends that you use the prefix defined in the previous fields as part of the table name. This is because Started Task Manager must have its own unique set of tables; using the prefix as part of its table names reduces the chance for confusion with Message Manager or other AF/OPERATOR entities.

Important

If any of these three tables should become damaged or lost, you must delete the remaining tables and then redefine the startup defaults. If any one of these tables exists, Started Task Manager will not rebuild the other two—it must build all three at the same time.

Skeleton Library Dsn

Command File Dsn

The skeleton library (default library name CANDLE.ALVnnn.ISPSLIB) contains model AF/OPERATOR command files that Started Task Manager uses to create the resource command files and service subroutines.

The command file dataset (default name CANDLE.ALVnnn.CMDLIB) is where Started Task Manager puts all its generated resource command files and service subroutines.

Important

The resource command files generated by Started Task Manager cannot be used in your production AF/OPERATOR system until you make them available to the command file dataset used by AF/OPERATOR. You can do this in two ways. One is to manually copy the resource command files to the AF/OPERATOR command file dataset. The second is to concatenate the command file dataset name specified here to the AOCMDLIB DD statement in your AF/OPERATOR startup PROC.

Default Job Abend Msg

Default Job Ended Msg

The message IDs that signify when a job abends or when a job ends normally. The default abend message ID is IEF4501. The default end message ID is $HASP395.



Refreshing SubroutinesThe Started Task Manager service subroutines and resource command files are all stored in the Started Task Manager command file library. (Refer to the section “Configuring the Started Task Manager Environment” on page 38 to determine the library name.) The control subroutines and resource command files are automatically regenerated every time you add, delete, or update a resource to the resource list.

The utility subroutines, on the other hand, are never automatically regenerated. There are two events, however, that require you to manually regenerate them

n if you are upgrading to a new release of Started Task Manager

n if any subroutine has been accidentally deleted

To regenerate the utility subroutines, use the following procedure:

1. Go to the Startup Defaults panel (Figure 11 on page 37).2. Make sure that the skeleton library containing the Started Task Manager command file

models is specified and then press Enter.3. Started Task Manager then asks if you want to refresh subroutines. Answer YES.4. Started Task Manager regenerates the utility subroutines, but leaves all control

subroutines and resource command files intact.


Using Help

Using HelpStarted Task Manager contains context-sensitive online Help information. To obtain Help about any panel, press PF1 while viewing the panel. To obtain Help for any field displayed on the panel, move the cursor into the field and press PF1. The Help provides a definition of the selected field and includes the input format and an example.

Application Library panels indicate that additional information is available (for instance, when a list is longer than can be shown on the screen) by placing a + or - in the More: field located on the upper right portion of the panel.

FIGURE 12. The More: Field

Use PF7 and PF8 to scroll forward (+) and backward (-) through these panels. Started Task Manager uses the following PF keys:

Table 1. Started Task Manager PF Keys

PF1

PF3

PF7

PF8

Displays context-sensitive help information

Exits the resource definition panels and returns to the Task Resource List panel. (If your definitions were previously saved with the Enter key, this PF key will also generate associated command files.) When pressed at the Task Resource List panel, this key exits the ISPF table editor.

Pages backward

Pages forward

Note: Other PF keys are not defined by Started Task Manager.

!Candle AF/OPERATOR - STARTED TASK MANAGER Version V340 COMMAND ===>_ RESOURCE DEFINITION=================================================== More: +RESOURCE....... ________DEFINITION..... _______________________________________________================================================================

Using Help


Using the Service Subroutines 43

Using the Service Subroutines

The ISPF dialog component of Started Task Manager only generates resource command files—it does not activate them. To initiate and control resource management for the environment, you must use the service subroutines.

Chapter ContentsStarting the Service Subroutines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Monitoring Started Task Manager Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

3

Starting the Service Subroutines


Starting the Service SubroutinesThe service subroutines and the resource command files they manage are all initiated by starting the control subroutine @RSTART (see “Configuring the Started Task Manager Environment” on page 38). This command file, in conjunction with other service subroutines, initializes the Started Task Manager environment and starts all resource command files that should be running at the current time and date; therefore, all started stasks scheduled to be running but are not currently active will be started. In addition, it sets up a special trap that allows you to manually override Started Task Manager operation with the command RCF (Resource Control Facility). (Traps are special AF/OPERATOR entities that watch for and react to particular events.)

Candle recommends that you include the @RSTART subroutine in your site’s initialization command file for AF/OPERATOR (Candle name: $$AOINIT). You do this by adding the line:

EX @RSTART

If AF/OPERATOR is already running, you can activate @RSTART before the next AF/OPERATOR recycle by issuing

EX @RSTART

from the MVS console.

Note: Remember, @R is the default command file name prefix. Use the prefix that you defined at the Startup Defaults panel as described in “Configuring the Started Task Manager Environment” on page 38.

Using the Service Subroutines 45

Monitoring Started Task Manager Resources

Monitoring Started Task Manager ResourcesThe RCF command provides an operator interface to give you additional control over resources defined to Started Task Manager. It communicates with AF/OPERATOR to display and control Started Task Manager resources from the MVS console. For example, from the MVS operator console you can type:

RCF START CICSPROD

at any time to start the resource command file associated with the resource definition you named as CICSPROD.

FIGURE 13. RCF Command Syntax

The resource name is the name you entered at the Resource Definition Primary Options panel (Figure 8 on page 32).

The asterisk (*) is treated as a wild card. For example, the command:

RCF START CICS*

will start all resources defined in Started Task Manager that begin with the letters CICS.

RCF commands are unique to the system at which they are entered; there is no inter-system communication.

The RCF keywords are:

START Starts a resource defined to the Started Task Manager immediately, rather than at the time specified in the resource definition. This keyword will not start a resource that is already active. No abbreviations of the START keyword are acceptable.

STOP Stops a resource defined to the Started Task Manager immediately, rather than at the time specified in the definition. STOP ALL stops all Started Task Manager resources in an orderly shutdown. No abbreviations of the STOP keyword are acceptable.

INIT

STATUS ALL

resource name pattern*

RCF ><START

STOP

resource name

INACTIVATE

ACTIVATE

NOMONITOR

MONITOR

Monitoring Started Task Manager Resources


STATUS Issues a WTO to the MVS console that indicates the status of the specified resource. Acceptable abbreviations are STAT or S.

The status types are:n ACTIVE–the resource is running.n INACTIVE–the resource is not running.n DEFINED–Started Task Manager knows about the resource but doesn’t know its

status.n DEACTIVATED–the resource is no longer controlled by Started Task Manager.n STARTING–Started Task Manager has issued a START command but hasn’t yet

seen a verify message.n STOPPING–Started Task Manager has issued a STOP command but hasn’t seen

an ended message.n IN-RECOVERY–Started Task Mananger has initiated recovery of the resource.

INIT Reinitializes a resource defined to the Started Task Manager so that changes to the resource’s definition will take effect immediately without affecting the status of other resources. The task will be started automatically if it should be running, and likewise stopped if it should not be up at the current time.

INACTIVATE

Changes a resource command file to INACTIVE status. This effectively undefines the resource; no further action will be taken on this resource until it is reactivated. Acceptable abbreviations are INACT or I.

ACTIVATE Changes a previously inactivated resource command file back to active status. Acceptable abbreviations are ACT or A.

NOMONITOR

Turns off the automatic recovery (monitoring) of a resource originally defined to Started Task Manager as having recovery ON. Acceptable abbreviations are NOMON or N.

MONITOR Turns back on the automatic recovery (monitoring) of a resource that had previously been set to NOMONITOR status. Acceptable abbreviations are MON or M. The command

RCF MONITOR resourcewill not turn on automatic recovery for a resource that was originally defined to Started Task Manager as having recovery OFF.

Guide to Candle Customer Support 47

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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48– 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52– Assigned Support Center Representative (ASCR)

– Maintenance Assessment Services (MAS)

– Multi-Services Manager (MSM)

Customer Support Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53– Link to Worldwide Support Telephone and E-mail information

A

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 55

Symbols$HASP395 23@RCFTA1 22, 39@RCFTA2 22, 39@RCFTAB 22, 39@RPMSAMP 25@RSTART subroutine 44

Aabend message 23, 24, 39abend recovery

See recoveryactivating command files 43adding resources 32additional options panel 36Adobe portable document format 7AF/OPERATOR language 19ALTABL 22Application Library installation 5ASCR

assigned support center representative 52assigned support center representative

ASCR 52automatic recovery

See recoveryautomation language 19

Bbatch job, defined 16browsing resources 31

Ccfile

See command filechanging resource definitions 32command file

activating 43dataset 39defined 18features 18model problem record 25name prefix 38notification 26problem record 25recovery exit 25regenerating 40

resource command filecreating 21defined 21difference from standard command files 21managing 21

command, RCFSee RCF command

COMMND00 command 16components

ISPF dialog 20resource command file 21service subroutines 21

concepts of operation 20configuring startup defaults 37control subroutines

See service subroutinescreating resources 32customer support

base maintenance plan 48contact information 53enhanced support services 52eSupport 49severity levels 49telephone support 48

Ddefaults

See startup defaultsdefined terms

batch job 16command file 18concepts of operation 20control subroutine 21ISPF dialog 20operational overview 16predecessordefined terms

successor 18resource command file 21service subroutinesstarted task 16trap 44utility subroutine 21who should use this guide 5, 20

deleting resources 30

Eend message 23, 24, 39

Index


end timeprimary 33secondary 36

error recoverySee recovery

eSupportcustomer support 49

extend WTOR 33

Gglobal variables

See variables

HHASP395 39help panels, using 41

IIEF450I 23, 39implementation planning 22initializing startup defaults 37installation 5ISPF dialog component

navigation 28overview 28

ISPF dialog, defined 20ISPF tables

ALTABL 22ISPTLIB 22predecessor table (@RCFTA1) 22, 39resource table (@RCFTAB) 22, 39successor table (@RCFTA2) 22, 39

ISPPROF 38ISPTLIB 22

Llanguage

REXXlanguageAF/OPERATOR 19

Mmaintenance assessment service

MAS 52MAS

maintenance assessment service 52messages

abend 23, 39end 23, 39user-defined 23

model problem record command file 25modifying resources 32MSM

multi-services manager 52multi-services manager

MSM 52MVS COMMND00 command 16

Nnavigation, ISPF dialog component 28notification command file 26

See command file

Ooperational overview 16

Pplanning Started Task Manager implementation 22PMABEND variable 25PMMSG variable 25PMNAME variablePMNAMEvariable 25predecessor

defined 18table name 39

predecessor tableSee ISPF tables

prefixcommand file name 38trap and variable 38

prerequisitesSee dependencies

primary options panel 33printing problems 7problem record command file 25

See command fileprofile definition

See startup defaults

RRCF command

ACTIVATE keyword 46INACTIVATE keyword 46INIT keyword 46MONITOR keyword 46NOMONITOR keyword 46START keyword 45STATUS keyword 45STOP keyword 45

recoveryabend message 23, 24, 39end message 23, 24, 39flow of events 23messages that trigger 23modifying the process 25

Index 57

notification command file 26overview 23problem record command file 25recovery exit command file 25retry counter 23, 24user notify list 35user-defined message 23

recovery exit command file 25See command file

recovery options panel 34resource

adding 32browsing 31defined 17deleting 30end time 33extend WTOR 33manually starting 22predecessors 33profile 37recoverysaving definitions 32secondary end time 36secondary start time 36start command 33start time 33stop command 33stop warn time 33table name 39updating 32verify message 33what Started Task Manager can and cannot

manage 22resource command file

See command fileresource list

functions 30panel options 30

resource tableSee ISPF tables

resources, monitoring 45retry counter 23, 24REXX language 19RNAME variable 26

Ssample problem record command file 25saving resource definitions 32service subroutines

control subroutinesdefined 21regenerating 21

defined 21

refreshing 40starting 44using 43utility subroutines

defined 21regenerating 21

severity levelscustomer support 49

skeleton library dataset 39software dependencies

See dependenciesstart command 33start time

primary 33secondary 36

started taskSee resource

started task, defined 16startup defaults

command file dataset 39command file name prefix 38configuring 37functions 37predecessor table name 39resource table name 39skeleton library dataset 39successor table name 39trap and variable prefix 38where stored 38

stop command 33stop warn time 33subroutines

See service subroutinessuccessor

defined 18table name 39

successor tableSee ISPF tables

Ttable names

predecessor 39resource 39successor 39

taskSee resource

telephone supportcustomer support 48

TMANEDIT member 38TMANPROF member 38trap and variable prefix 38trap, defined 44tutorial 20


Uupdating resources 32user notify list 35user prerequisites 5user-defined message 23utility subroutines

See service subroutines

Vvariables

global 25, 26PMABEND 25PMMSG 25PMNAME 25RNAME 26

verify message 33viewing resource definitions 31

Wwho should use this guide 5, 20

started task manager · started task manager is a component of the af/operator ® application...

Documents