operators 52

ESP Workload ManagerVersion 5.2

Operator’s GuideESP-OG-02

2

Second Edition (October 1999)

This edition applies to Version 5 Release 2 of ESP Workload Manager Documentation.

The software and related manuals are protected by copyright law.

ESP Workload Manager Documentation 1992-1998,1999 Cybermation Inc.All rights reserved.

No portion of this publication may be reproduced, stored in a retrieval system, or transmitted inany form or by any means without express written permission of Cybermation Inc.,80 Tiverton Court, Markham, Ontario, L3R 0G4, Canada, (905)-479-4611.www.cybermation.com

U.S. Government Users. RESTRICTED RIGHTS - Use, Duplication or Disclosure restricted byGSA ADP Schedule Contract with Cybermation Inc.

Trademark Notice:

ESP Workload Manager is a registered trademark of Cybermation Inc.

All other brand and product names are trademarks or registered trademarks of their respectivecompanies.

3

Table of Contents

About this Guide ................................................................................................................. 6Conventions Used in this Guide.......................................................................................... 7Summary of Changes .......................................................................................................... 8

Introduction to ESP .................................................................................................................. 9Overview ............................................................................................................................. 9Introducing ESP Workload Manager ................................................................................ 10ESP Concepts .................................................................................................................... 11The ESP ‘Big Picture’ ....................................................................................................... 14

Controlling ESP....................................................................................................................... 15Overview ........................................................................................................................... 15Starting ESP ...................................................................................................................... 16Stopping ESP .................................................................................................................... 21Quiescing ESP................................................................................................................... 22

Consolidated Status Facility................................................................................................... 23Overview ........................................................................................................................... 23How CSF Works ............................................................................................................... 24Understanding What You See ........................................................................................... 25CSF Commands ................................................................................................................ 27CSF Extensions ................................................................................................................. 31

Customizing CSF..................................................................................................................... 33Defining a View ................................................................................................................ 34View Characteristics ......................................................................................................... 35Changing Filter Information in a View ............................................................................. 36Changing Presentation Information in a View .................................................................. 39Defining Color Options in a View .................................................................................... 42Freeform Filtering ............................................................................................................. 43

ESP Applications..................................................................................................................... 52Overview ........................................................................................................................... 52An Example ESP Application........................................................................................... 53Application Generations.................................................................................................... 56Common ESP Application Statements.............................................................................. 57Resources .......................................................................................................................... 64Controlling Applications ................................................................................................... 66Controlling subApplications ............................................................................................. 67Controlling Jobs in an Application ................................................................................... 69

ESP Events ............................................................................................................................... 72Overview ........................................................................................................................... 72Functions of an Event........................................................................................................ 73Defining an Event.............................................................................................................. 75Data Set Triggering ........................................................................................................... 77Scheduling an Event.......................................................................................................... 78

4

Displaying the Schedule.................................................................................................... 79Displaying When an Event Will Execute.......................................................................... 80Postponing Event Execution ............................................................................................. 81Bypassing Event Execution............................................................................................... 83Triggering an Event Manually........................................................................................... 84Simulating an Event .......................................................................................................... 88Simulating the Next Occurrence ....................................................................................... 89Simulating a Specific Day................................................................................................. 92

Scheduling Workload.............................................................................................................. 94Schedule Criteria ............................................................................................................... 95Calendars........................................................................................................................... 97

Controlling the Work............................................................................................................ 100Overview ......................................................................................................................... 100Holding a Job .................................................................................................................. 101Completing a Job............................................................................................................. 103Bypassing a Job ............................................................................................................... 105Resubmitting a Job.......................................................................................................... 107Requesting a Job.............................................................................................................. 108Inserting a Job ................................................................................................................. 109Dropping Dependencies .................................................................................................. 111Resetting a Time Dependency......................................................................................... 114Holding an Application ................................................................................................... 115

Working with Delayed Events.............................................................................................. 116Overview ......................................................................................................................... 116System Outage................................................................................................................. 117Data Set Contention ........................................................................................................ 118Event Data Set Unavailability ......................................................................................... 119Extended Outages............................................................................................................ 120Restarting ESP in Phases................................................................................................. 122

Working with ESP Classes ................................................................................................... 124Overview ......................................................................................................................... 124Controlling Classes ......................................................................................................... 125Hold Queues.................................................................................................................... 126Masking........................................................................................................................... 127Multiple Class Restrictors ............................................................................................... 128

ESP Reports ........................................................................................................................... 130History Reporting ............................................................................................................ 131Scheduled Activity Report .............................................................................................. 132

ESP System Topology ........................................................................................................... 134Overview ......................................................................................................................... 134Multiple ESPs on a Single MVS Image .......................................................................... 135Multiple Copies of ESP in a Shared Spool Environment ............................................... 136Multiple Copies of ESP on Multiple JES Nodes ............................................................ 137

Frequently Used Commands ................................................................................................ 138APPLJOB (AJ) Command .............................................................................................. 139

5

List Application (LAP) Command .................................................................................. 140List Job (LJ) Command................................................................................................... 141List Tracked Job (LTJ) Command .................................................................................. 142

Using ESP Operator Commands ......................................................................................... 144Overview ......................................................................................................................... 144ESP Operator Commands................................................................................................ 145ESP Backup Commands.................................................................................................. 150Distributed Processing Commands ................................................................................. 151

Glossary of Terms ................................................................................................................. 152Glossary........................................................................................................................... 152

6

About this Guide

Overview Enterprise Systems Platform (ESP) is a very powerful and versatile system forscheduling jobs and managing workload. There are many different users ofESP. These users have specific and sometimes overlapping requirements.

Introduction This guide contains the information you require to do the following:

• Start and stop ESP Workload Manager• Define views in ESP’s Consolidated Status Facility• Define and control ESP Events• Create ESP Applications• Monitor and control workload managed by ESP Workload Manager• Enter ESP Operator commands.

7

Conventions Used in this Guide

Input ESP is not case sensitive. Even though we show commands in uppercase,when you type a command on the command line, you do not need to type thecommand in uppercase letters.

Syntaxconventions

The Syntax diagrams in this guide use the following conventions:

Notation MeaningApostrophes “ or ‘ Must be entered as shown.Comma , Must be entered as shown.Ellipsis … The parameter can be repeated. Do not enter ellipsis.Lower Case Italicsparameter

A parameter must be substituted. User supplied variableor character string.

Uppercase parameter The parameter must be spelled as shown. You can enterthe command and the parameter in either upper or lowercase.

OR-bar ( | ) Indicates an exclusive value on left or right of bar. Youmust enter one of the items. You cannot enter more thanone.

Underline ______ If you do not enter one of the parameters, the systemsupplies the underlined parameter, which is the default.

Parentheses ( ) andspecial characters

Parameter enclosed in parentheses is mandatory and mustbe entered as shown.

Single parameter insquare brackets [ ]

Optional parameter, do not type the brackets.

Stacked parameters inbraces { } { }

Mandatory, you must enter one of the parameters. Youcannot enter more than one.

Stacked parameters insquare brackets [ ] [ ]

Optional parameter, you can enter one value, or none.

Stacked parameterswith OR-bars ( | ) andsquare brackets[ ]|[ ]

Optional, mutually exclusive parameters. Enter one ornone.

Stacked parameters insquare brackets withinbraces {[ ]}

Mandatory, you must enter one of these parameters. Youcan enter more than one.

8

Summary of Changes

Introduction This guide contains information previously presented in ESP-OG-01, whichsupports ESP Workload Manager version 5 release 1.

ChangedInformation

This guide contains terminology, maintenance and editorial changes. Avertical line to the left of the text indicates technical changes or additions tothe text.

NewInformation

The following ESP START parameter has been added:

• CQFORMAT

9

Introduction to ESP

Overview

Introduction Enterprise Systems Platform (ESP) Workload Manager is a very powerful andversatile system for scheduling jobs and managing workload.

ESP allows users to automatically schedule workload on multiple systems,while maintaining a single point of control.

In this chapter This chapter contains the following topics:

Topic See PageIntroducing ESP Workload Manager 10ESP Concepts 11The ESP ‘Big Picture’ 14

10

Introducing ESP Workload Manager

Overview ESP Workload Manager is a very flexible and versatile job-scheduling andworkload-management system.

What ESP cando

ESP can be used to:

• Automate and manage workload• Schedule jobs and other workload objects• Manage dependencies• Track jobs and started tasks• Forecast future workload• Provide historical reporting.

11

ESP Concepts

Introduction This topic introduces you to basic ESP concepts and the ESP objects youencounter when using ESP.

ESPApplications

An ESP Application is a series of statements defining one or more (usuallyrelated) jobs that run under the control of an ESP Manager across yourenterprise on mainframes, mid-range, and small systems. For moreinformation on ESP Applications, see ESP Applications on page 52.

ESPProcedures

An ESP Procedure is a set of stored instructions invoked by ESP. Theseinstructions may define a group of jobs and tasks as an Application, but not allESP Procedures contain ESP Applications.

Procedures control processing requirements using:

• Job definition statements• CLANG (ESP’s Control Language)• IF/THEN/ELSE logic• ESP built-in functions• REXX processing• Use of symbolic variables.

ESP Events An ESP Event tells ESP when to run workload, and what actions to take toperform the work. For more information on Events, see ESP Events on page72.

ESP Jobs ESP allows you to define jobs with many characteristics:

• On request jobs that run only when requested manually• External jobs that exist in another Application• Manual jobs submitted outside of an ESP Application• Tasks that require manual intervention• Links – tasks that do not require manual completion• Data set trigger workload objects• Jobs that run on almost any platform in addition to MVS.

Continued on next page

12

ESP Concepts, Continued

ConsolidatedStatus Facility(CSF)

The ESP Consolidated Status Facility (CSF) is your scheduling focal point.Using CSF, you:

• Monitor workload• Control jobs• Edit JCL and ESP Procedures• Browse or edit documentation libraries• Rerun jobs• Restart jobs via ESP Encore.

For more information on CSF, see Consolidated Status Facility on page 23.

Resources A resource can be an item of hardware or software, or it can be an abstractcondition. Resources are used to ensure a job is not submitted until all of itsrequirements are met. For more information on resources, see Resources onpage 64.

Reporting ESP provides two types of reporting:

• History reporting• Scheduled Activity reporting.

History reporting allows you to look at the history of an individual job, todetermine such things as how long it runs, how many print lines it generates,and how much CPU time it requires.

Scheduled activity reporting allows you to look at schedule data for a timeperiod to see such things as how long work runs, how many print lines aregenerated, and how much CPU time is required.

For more information on reporting, see ESP Reports on page 130.


13

ESP Concepts, Continued

Masters andSlaves

You can run multiple copies of ESP in your installation and maintain a singlepoint of control using an ESP Master and ESP Slaves. The Master maintainsthe single point of control, while the Slaves perform the work under directionof the Master. For more information on Masters and Slaves, see ESP SystemTopology on page 134.

ESPWorkstation

ESP Workload Manager interfaces with many other products on MVS and onother platforms. ESP Workstation provides a Graphical User Interface (GUI)to ESP Workload Manager. You can use ESP Workstation to controlApplications and jobs in ESP.

14

The ESP ‘Big Picture’

Overview The following diagram illustrates how the objects used with ESP are defined,what they look like, and how they work together:

EVENT

ESPPROCEDURE

CSF

REPORTING

EVENT ID(CYBER.EXAMPLE)SCHEDULE 4PM WORKDAYSINVOKE 'CYB.ESP.PROCLIB(EXAMPLE)'ENDDEF

APPL EXAMPLEJCLLIB 'CYB.JCLLIB.CNTL'JOB A RUN WORKDAYS RELEASE BJOB B RUN WORKDAYS RELEASE CJOB C RUN LAST DAY OF MONTHENDJOB

ESP--CONSOLIDATED STATUS: VIEW PANEL --ESPCOMMAND ==>

JOBNAME JOBNO APPL APGEN STATUS

__ A 123 EXAMPLE 1 COMPLETE__ B 124 EXAMPLE 1 EXECUTING__ C 125 EXAMPLE 1 WAITING

REPORTFROM 8AM YESTERDAY UNTIL 8AM TODAYCRITERIA APPLSYS EQ EXAMPLEDISPLAY JOBNAME JOBNO EXECST ENDT CMPCENDR

JOBNAME JOBNO EXEC START EXEC END CMPC CODE A 123 16:05 16:10 0 B 124 16:11 16:15 S0C1 C 125 16:20 16:47 0

JOB A

JOB B

JOB C

The ESP Solution

15

Controlling ESP

Overview

Introduction This chapter tells you how to use the various options available to start andstop ESP.


Topic See PageStarting ESP 16Stopping ESP 21Quiescing ESP 22

16

Starting ESP

Overview ESP can be started from the operator’s console or by an automatic commandfrom SYS1.PARMLIB.

To start ESP from the operator’s console, issue the START command,specifying the name assigned to the ESP started task procedure – normallyESP. Refer to the following description of the START command. Once theESP499 message is issued, ESP is ready for communication.

You can start ESP in phases. Refer to Restarting ESP in Phases on page 122for more information.

STARTcommand

Several parameters can be specified on the START command or the PARMkeyword of the EXEC card. Note that any parameters specified on theSTART command override corresponding parameters on the EXEC cardPARM statement.

Syntax ofSTARTcommand

S ESP[,PARM=[WARM|COLD] [NOTRACK] [PROMPT] [QFORM] [RELOAD] [NOQUIESCE|QUIESCE] [SYSID(sysid)] [SUBSYSTEM(subsysid)] [RESFORM] [TPFORM] [SKIP] [CQFORMAT]

Parameter DescriptionWARM Requests a warm start. On a warm start, the main ESP

Initialization Parameter member and the ESPWARMmember are read. This is the default.

COLD Requests a cold start. Do only under direction ofCybermation Technical Support. On a cold start, themain ESP Initialization Parameter member and theESPCOLD member are read.


17

Starting ESP, Continued

Syntax of START command (continued)

Parameter DescriptionNOTRACK Indicates that ESP is not to collect job-tracking data.

This option should be used if you are starting an ESPsubsystem on a CPU that already has an active ESPsubsystem sharing the same tracking data sets. Itprevents duplicate updates to the tracking files.

PROMPT Requests that ESP prompt the operator for additionalInitialization Parameter input after reading ESPPARM.

QFORM Requests that the QUEUE data set be reformatted. Doonly under direction of Cybermation Technical Support.When using this parameter, ensure that no ESPsubsystem is currently using the QUEUE data set onanother processor.

QUIESCE Requests that ESP initialize in the quiesced state, whichdefers Event execution. Use the RESTART command totake ESP out of the quiesced state.

NOQUIESCE Requests that ESP initialize in the non-quiesced state.Event executions are not deferred. This is the default.

RELOAD Requests that all ESP modules residing in CSA arereloaded (that is, control blocks re-initialized). Use thisafter a change is made to CYBSS010, CYBJS031 orCYBSS016 or if your system has experienced any SMFproblems.

SYSID(sysid) Specifies the system identifier to be used. This overridesthe corresponding parameter in the ESPPARM data set.It can consist of up to eight alphanumeric characters.

SUBSYSTEM(subsystemid)

Specifies the subsystem name that ESP is to use. Itshould be up to four characters long. The defaultsubsystem name is the started task procedure name.


18


Syntax of START command (continued)

Parameter DescriptionRESFORM Requests a format of the RESFILE, used for ESP’s

resource feature. Do only under direction ofCybermation Technical Support.

TPFORM Requests that the TP server checkpoint data set, used forLU6.2 communication, be reformatted. Do only underdirection of Cybermation Technical Support.

SKIP Skips the first time-driven request in ESP’s queue. Useonly on the advice of Cybermation Technical Support.

CQFORMAT Requests a reformat of the COMMQ data set. TheCOMMQ data set is the ESPCOM checkpoint data set.

Specifyingmultipleparameters

You can specify multiple parameters by separating them with commas:

S ESP,PARM=(parm1,…,parmn)

Cold startingESP

A COLD start re-initializes the Checkpoint data set, and destroys the schedulequeues. ESP automatically does the following:

• Re-specifies the Event data sets. As each data set is opened, if it containsdata, an immediate scan is performed and the schedule is rebuilt.

• Executes any commands contained in the cold parameters.• CLASS hold queues are lost, as are the overdue and deferred queues.

For more information, see COLD start on page 20.

Starting ESPwith theRELOADoption

Starting ESP with the RELOAD option causes ESP’s primary control blocksin CSA to be re-initialized. If you experience problems with SMF, you needto use this option to resolve the SMF problem. You also use this option whenupgrading to a new release of ESP.


19


Starting ESPwith theRELOADoption con’t

Before you issue a START with the RELOAD option, the auxiliary addressspace and any Workstation server tasks must be shut down. Batch interface orTSO users that are active at the time of a RELOAD must restart, or they seethe subsystem as inactive.

Example –Cold start ESPwith reformatof Queue file

S ESP,PARM=(COLD,QFORM)

Example –Starting ESP ina quiesced state

S ESP,PARM=(QUIESCE)

Starting ESPwith QFORMoption

Starting ESP with the QFORM option formats the QUEUE file, whichcontains tracking information in transit from ESP Slaves to the ESP Master.After starting ESP with the QFORM option:

• The ESP Master system may miss notification of job or data set activityfrom a Slave.

• The DAB command is out of date – use CSF.• Locally defined P-Nodes are deleted. They are automatically created

again when new job tracking information is received.• If this is the first ESP start following an IPL, ESP rebuilds via the

QUPDATE function. The completion status of some jobs may beindeterminate.

• If there is no intervening IPL, data is rebuilt with the receipt of bufferedTCELL information.

• Inbound or outbound tracking or triggering information may be lost.


20


COLD startprocess

An ESP COLD START reformats the Checkpoint file, and initializes all ESPcomponents, with the exception of:

• The ESP QUEUE file, which is formatted the first time ESP is started, orwhen ESP is started with the QFORM option.

• ESP CSA-loaded modules. These modules are loaded into CSA the firsttime ESP starts after an IPL, or when ESP is started with the RELOADoption.

An ESP COLD START rebuilds its ‘to-do list’ by scanning all Event data setsand extracting the next scheduled times to execute. If an Event data set wasadded dynamically to ESP, and is not recorded in the Initialization Parametersor cold start member, it is not found and examined during a cold start.

Once the ‘to-do list’ is rebuilt, ESP starts triggering Events unless QUIESCEwas specified at start time. When ESP is quiesced, no new workload issubmitted.

Provided ESP data sets (INDEX, JOBINDEX, APPLFILE and so on) areintact, ESP retains status over a COLD START. For example, Applicationstatus or data set trigger activity is retained.

• ESP internally issues a QUPDATE command during a COLD START.This command compares ESP’s view on a job-by-job basis. If ESPrecorded that job PAYROLL was in execution and JES shows that jobPAYROLL is on the output queue, ESP updates its status.

Items lost in aCOLD start

The following items are lost in a COLD START:

• Event Class Actions – Any CLASS actions entered, like hold, ignore, orsuspend are lost.

• Trigger-added Events – If an Event was added to the schedule via aTRIGGER ADD command, it is lost over a COLD START.

• Pending Application Manager actions – Application actions that arepending are lost in a COLD START. These are entries that may show as‘queued for submission’ in CSF. Resubmit these jobs. (Items displayedwith a leading + in the output from the LISTSCH command are pendingApplication actions.

21

Stopping ESP

Overview ESP can be stopped from the operator’s console or by an automatic commandfrom SYS1.PARMLIB.

To stop ESP from the operator’s console, issue the STOP command,specifying the name assigned to the ESP started task procedure – normallyESP.

STOPcommand

The syntax of the STOP command is as follows:

P started_task_name

where started_task_name is the name of the ESP started task. For example:

P ESP

Where the name of the started task is ESP.

22

Quiescing ESP

Overview If you want to stop further processing on ESP, without shutting it down, youcan use the Quiesce option. Any active jobs continue to process tocompletion. No further workload is submitted.

QUIESCEcommand

To quiesce ESP, issue the following command from the system console:

F ESP,QUIESCE

or from ESP page mode, using OPER authority, option G from the ESP mainmenu:

OPER QUIESCE

23

Consolidated Status Facility

Overview

Introduction ESP’s Consolidated Status Facility (CSF) provides a focal point formonitoring and controlling ESP workload. It allows you to see a list of thejobs running under the control of ESP, and control those jobs easily.


Topic See PageHow CSF Works 24Understanding What You See 25CSF Commands 27CSF Extensions 31

24

How CSF Works

Overview ESP maintains a ‘scoreboard’ containing details about every workload objectin its control. This scoreboard is updated constantly as workload is processed.

Customizable What you see on CSF is customizable to suit you. You can filter and sort thedata displayed as required.

SCHDFILEdata set

The ‘scoreboard’ that ESP maintains is contained in a data set calledSCHDFILE. Information is contained in this data set in rows that representthe workload objects, and columns that represent attributes of the workloadobject. It is this data set that provides the data for CSF. By default, all activeApplications are displayed on CSF.

PURGSCHFcommand

The PURGSCHF command is used to delete data from the SCHDFILE dataset. When PURGSCHF is issued, all completed jobs from completedApplications, which completed prior to the schedule criteria specified in thecommand, are deleted from CSF.

OPER authority is required to issue this command.

The following is an example of the PURGSCHF command:

OPER PURGSCHF NOW LESS 1 HOUR

You can also set filter options to not display completed jobs without purgingthe Schedule file.

25

Understanding What You See

Overview ESP’s CSF can display many types of information regarding the workloadrunning under ESP’s control. CSF is commonly used to display the followingtypes of information about workload:

• P-Node fields• Status fields

A job can be in only one P-Node at a time, but may have more than onestatus. For example, if a job is waiting until 5 pm, and is also on hold, the P-Node shows MANHOLD, and the status shows MANHOLD and Waitinguntil 5 pm.

For more information on customizing what displays on CSF, see CustomizingCSF on page 33.

P-Node fields A Processing node (P-Node) identifies a processing stage through which a jobmay pass during its time on the system. The following is a list of the possibleP-Nodes you may see on CSF, and their meanings:

P-Node DescriptionMANHOLD Manual holdAPPLHOLD Application holdPREDWAIT Predecessor waitWAITING Delayed submission timeJANCWAIT Job ancestor waitSANCWAIT SubApplication ancestor waitRESWAIT Resource waitEXTERNAL External job submitted by another ApplicationTASK Task required completionMANSUB Manual submissionREADY EligibleSUBERROR Submission errorSUBDELAY Submission delayedINPUT Input queue – JES number assignedEXEC ExecutingCOMPLETE Completed successfullyFAIL Completed unsuccessfully


26

Understanding What You See, Continued

Status fields You can display the following status fields on CSF:

Status DescriptionUser status Displays information set by the user.System status Displays the system state of a workload object. This is

the system state that ESP continues to change during jobprocessing. You cannot change the values in this field.

Status Displays the user status, if set. If the user status is set tonull, it displays the system status.

User Statusfield

The User Status field contains more information than what is contained in theP-Node field. The User Status field is set by either of the following:

• HR command – holds a job with a reason• SUS command – resets User Status for a job.

For example, if you bypass a job you can use the User Status field to notifyothers of the reason for this action. The User Status field for a job might looklike this:

JOBNAME PNODE USER STATUSTAPEJOB BYPASSED NO INPUT TODAY

ESP does not reset the User Status field. To reset the User Status field to null,issue the SUS command and enter a period (.) in the field.

27

CSF Commands

Overview Several line commands are available to control the following workloadobjects:

• Applications• SubApplications• Events• ESP Procedures• Jobs.

Commandavailability

You can issue the following commands from CSF in the field next to theobject. (Many of these commands have an equivalent APPLJOB (AJ)command, which can be issued in Page mode, batch, an ESP Procedure, orfrom the system console.)

For controllingApplications

Command DescriptionAA Release an Application from ESP hold statusCA Complete an entire ApplicationHA Place an Application into ESP hold statusLA List an Application

UWA Remove an Application from wait status


28

CSF Commands, Continued

For controllingsubApplications

Command DescriptionAS Release a subApplication from ESP hold status

BYS Bypass a subApplicationCS Complete an entire subApplicationHS Place a subApplication into ESP hold statusLS Display a subApplication

RQS Request a subApplicationUBS Un-bypass a subApplicationURS Un-request a subApplicationUWS Remove a subApplication from wait status

For controllingEvents andProcedures

Command DescriptionBE Browse an EventEE Edit an EventBP Browse a ProcedureEP Edit a Procedure


29


For controllingjobs

Command DescriptionA Release a job

BC Browse COPYJCLBJ Browse last executed JCLBY Bypass a jobC Complete a job

DD Drop all predecessor dependenciesDIN Display an Info recordDR Drop all resource dependenciesEC Edit COPYJCLEJ Edit last executed JCLH Place a job into ESP hold status

HR Place a job into ESP hold status with a reasonIJ Insert a job

IJA Insert a job after a selected jobIJB Insert a job before a selected jobL Display all dependencies

L, then D Drop individual dependenciesLI Display index entriesLJ Display step-level statisticsLR Display job resource waitsR Resubmit or restart a job


30


For controlling jobs (continued)

Command DescriptionRD Ready a job, removing all predecessor and submit time

dependenciesRP Replies to an AS/400 messageRQ Request a jobRR View ESP Encore panelsRT Reset a time dependency

SUS Reset User Status field for a jobUB Un-bypass a bypassed jobUIN Update an Info recordUR Un-request a requested jobUW Un-wait a job from job-ancestor wait (JANCWAIT)

31

CSF Extensions

Overview CSF Extensions allow an installation to customize CSF to meet its needs.Frequently performed functions can be reduced to a single command. CSFExtensions can be used to access other ISPF applications, such as outputdistribution products, spool viewers and so on from within the CSF display.

What you needto know

As an ESP operator, you should be aware of any installation-definedcommands. Check with your System Programmer.

For detailed information about CSF Extensions, refer to the ESP WorkloadManager Installation Guide.

33

Customizing CSF

Overview You can customize what you see on CSF by defining a CSF view. A CSFview limits the workload objects displayed on CSF to match criteria youspecify. You can have an unlimited number of views per user.


Topic See PageDefining a View 34View Characteristics 35Changing Filter Information in a View 36Changing Presentation Information in a View 39Defining Color Options in a View 42Freeform Filtering 43

34

Defining a View

Overview You define a view by replicating an existing view and changing thecharacteristics of the view.

Replicating aview

To define a view, replicate an existing view and customize the new view tomeet your requirements:

Step Action1 From the ESP Main Menu, choose Option C to access CSF.2 Type V in the command line to list the current views.3 To define a view, type R to replicate an existing view and

customize the new view to meet your requirements:

Press Enter. The Replicate a View panel appears.4 Type the name, a description and optionally the message you want

displayed when no workload objects match your filter criteria:

Press Enter. The view you defined is now displayed in the list ofviews

35

View Characteristics

Possible views Once you select an existing view, or create a new view, you can customize theinformation presented. For example, you can create:

• Application-specific views• Exception monitoring views that display:

• Overdue jobs• Abended jobs

• Waiting job views• Incomplete job views.

Customizing aview

You can change the characteristics of a view, to specify what workloadobjects you want included, how you want the view presented, the sort order ofthe fields, and any color options you desire.

Select the view you want to customize, and use the following commands onCSF to change the characteristics of the view:

Command DescriptionFI Select Filter informationPR Specify Presentation fieldsPL Alter the default Presentation field lengthPT Alter the default Presentation titlesSO Specify the sort order of the information presentedCO Define color options based on job status

36

Changing Filter Information in a View

Overview When you filter information, you are describing the criteria for selecting a jobas part of a view. This information defines the rows or workload objects inyour display.

Steps tochanging thefilter criteria

Step Action1 From the ESP Main Menu, choose Option C to access CSF.2 Type V in the command line to list the current views. Type S next

to the view you want to customize, as shown below:

Press Enter.


37

Changing Filter Information in a View, Continued

Steps to changing the filter criteria (continued)

Step Action3 The CSF display appears, displaying workload based on its current

attributes. Type FI to change the filter information:

Press Enter.


38

Changing Filter Information in a View, Continued

Steps to changing the filter criteria (continued)

Step Action4 The Filter Specification panel appears. Specify the desired filter

criteria:

(All filter criteria is tested with Boolean ‘OR’ logic.)Press Enter. The CSF display reappears, displaying only thespecified workload objects:

The changes to the view are saved automatically.

39

Changing Presentation Information in a View

Overview You can change the way your view of CSF looks by changing the presentationfields of the view. You can change the order in which the fields appear, theorder they are sorted on, the length of the fields, and the title of each column.

Changing thefields

To change what fields are displayed and how they are displayed in your view,do the following:


to the view you want to customize. Press Enter.3 The CSF display appears, displaying workload based on its current

attributes. Type PR to change the Presentation fields displayed.4 The Presentation Fields for View panel appears. Specify the

presentation order, new titles, sort order and so on. Specifypresentation order first, because it determines what is displayed:

Press Enter. The Presentation information is changed.

Presentationorder(Pres order)

Presentation order determines what is presented (the columns) and whatorder it appears in, from left to right on your display. Specify the workloadobject fields to be presented for display and the order in which you want themshown, from left to right. Identify a field to be displayed by typing a one ortwo-character string for each field. The strings you specify can contain anycharacter and are sorted in normal collating sequence.

The jobname field is always displayed first.


40

Changing Presentation Information in a View, Continued

Presentationfields

In addition to the jobname, a series of user level or system level fields can bedisplayed:

User Level Entries System Level EntriesAccount Number Job Status FlagAppl Generation Job Attr FlagAppl Def Seq Job Status ByteDJC Jobnet Appl Status FlagSubapplication SAD FlagsQualifier ApplFile nameStatus ApplFile Slot#User Status TrakFile Slot#System Status EXH File Slot#Tag NS Cart MountsScheduled Time NS Reel MountsEvent Name HW Cart MountsJob Number HW Reel MountsHold Count Color IndexJob Start Time SCB Entry#Job End Time SCB TokenCompletion Code SCB CycleAuth String

Presentationlength(Pres Len)

Specify the width of each column of data selected for display if the defaultdisplay widths are not what you want. If the specified width is too short forthe data, the data is truncated. If the column is wider than the data, the data isleft justified and padded to the right with blanks.

Presentationtitle(Pres Title)

If you do not specify a heading for any column, a default heading is used. Ifthe field is not selected for display via the Presentation order, the field isignored.


41

Changing Presentation Information in a View, Continued

Sort order Specify the order in which the columns are to be sorted. (The rows of thedisplay.) Type a one or two-character string next to the field. Strings aresorted in normal collating sequence to determine the sort order of thedisplayed data. You can specify more than one Sort order field. Specify A orD to request an Ascending (the default) or descending sort order. Forexample, you may want to sort by Application generation number.

What isdisplayed

User level fields are always displayed. System level fields can be requestedvia the ESP DEFAULTS panel (option O from the ESP Main Menu).

42

Defining Color Options in a View

Overview You can use different colors to represent certain job conditions to highlightthose conditions and make them easier to see. For example, you might wantto highlight all failed jobs in red.

Steps tochanging coloroptions


to the view you want to customize. Press Enter.3 The CSF display appears, displaying workload based on its current

attributes. Type CO to change the color options.4 The Highlight Attributes panel appears. Select from the available

color, highlighting and intensity options:

Press Enter. The color options of the view are changed.

43

Freeform Filtering

Introduction Freeform filtering is an extension to the CSF filtering capabilities that allowsyou a more versatile and customizable method of filtering your ESPApplications. You have the option to filter your Applications using thestandard filter panel or to use the Freeform filter panel for scenarios thatcannot be handled using the standard panels.

Somesuggestions

For example, you may choose to filter based on the following criteria:

• Jobs that have started and ended between specific times• Jobs on a critical path• Completion codes for jobs within a subApplication• Jobs within an Application that have restart steps.

Filter criteria A filter consists of a filter string. A filter string consists of the following:

keyword logical_operator value|condition [Boolean_operator]

Operand Descriptionkeyword Identifies the kind of workload objects on which you want

to filter, such as Applications or workload object names.logical operator Specifies the operation, such as filter on Application

name, when it is equal to some specified character string.value orcondition

What you want the Application name to be equal to, suchas PAYROLL. If you want to see all Applications that areincomplete, filter on the condition INCOMPLETE.

Booleanoperator

Boolean operators are used to AND or OR one or morekeyword and value sets.

Example The following is an example of freeform filtering that limits what is displayedto incomplete jobs in Applications called PAYROLL:

APPL=PAYROLL AND INCOMPLETE


44

Freeform Filtering, Continued

Entering afreeform filter

Step Action1 Type FI on the CSF command line. This displays the Filter

Specification panel.2 Type Y in the Freeform filter ===> field. This places you in ISPF

Edit, where you can enter a Freeform filter. Replace the followingtext shown with your freeform filter.

(COMPLETE OR INCOMPLETE)


45


FilteringKeywords

Keyword Description Keyword DescriptionJob status byte:ACCOUNT Account number JSBYTEC-completedD-dependencyE-executingF-failedI-input

P-post-processR-resourcesS-scheduledT-timeW-wait

AGENT Agent name JSFLAG Job status flagAPPL Application

nameNETID DJC/JES3 network id

APPLFILE Application file NSCM Non-specific cart mountsAPPLGEN Application

generationNSRM Non-specific reel mounts

APPLSEQ Applicationdefinitionsequence

PNODE Processing node

APSLOT Application fileslot #

QUAL Qualifier

ASFLAG Applicationstatus flag

SADFLAG SAD flags

AUTH Authorizationstring

SCBCYCLE Scoreboard cycle

CMPC Completion code SCBENTRY Scoreboard entry #DMANAGER Distributed

manager nameSCBTOKEN Scoreboard token

ETIME Job end time SCHED Scheduled timeEVENT Event name STATUS StatusHC Hold count STIME Job start timeHWCM High water cart

mountsSUBAPPL SubApplication name

HWRM High water reelmounts

TAG Tag

JAFLAG Job attribute flag TRSLOT Trakfile slot #JOBNAME Job name USTATUS User statusJOBNO Job number WOBTYPE 2-character workload object

type for non-MVS


46


TIME functionas comparison

For any of the time fields, (i.e. ETIME, SCHED, and STIME), you need touse the TIME function in a comparison. For example:

STIME > TIME(11AM TODAY)

You can compare against any time in a format that ESP recognizes.

Specifyingrelationaloperators

Relational operators include the following standard operators:

>= GE greater than or equal<= LE less than or equal> GT greater than< LT less than= EQ equal¬= NE not equal to

SpecifyingValues

You may need to refer to portions of a value, rather than its full contents. Thefilter string uses substring notation to allow you to specify which characters ofa value you need. Substring notation consists of specifying 1 or 2 numbers inparentheses immediately following the value name, as follows:

VALUE(v1[,v2])

where:

• v1 and v2 are whole numbers• v1 refers to the starting position, the first character position is 1.• If v1 is negative, the starting position is relative to the last non-blank

character of the variable. For example, -1 refers to the last character.• If v2 is omitted, it defaults to the remaining length of the variable.• If v2 is positive, it specifies a number of characters required.• If v2 is negative, it represents the remaining length less v2.


47


Example For example, assume that JOBNAME contains the string PRODJOB. Thefollowing table demonstrates the outcome that results when you specifycertain substring notations:

Specification Result

JOBNAME ‘PRODJOB’

JOBNAME(1,4) ‘PROD’

JOBNAME(5) ‘JOB’

JOBNAME(5,1) ‘J’

JOBNAME(-1,1) ‘B’

JOBNAME(1,7) ‘PRODJOB’

JOBNAME(1,-3) ‘PROD’

Conditions forfilter string

Condition DescriptionALL All objectsAPPL_COMPLETE Application execution is completeBYPASSED Object execution has been bypassedCOMPLETE Object execution is completeCRITICAL_PATH Object is on a critical pathEXTERNAL Object is External to an ApplicationINCOMPLETE Object execution is not completeINTERVENTION_REQUIRED Object execution requires manual

interventionINTVRQ Object execution requires manual

interventionLINK Object is a LINKMANUAL_TASK Object is a manual taskNOT_APPL_COMPLETE Application execution is not completeNOT_BYPASSED Object execution has not been

bypassedNOT_CRITICAL_PATH Object is not on a critical pathNOT_EXTERNAL Object is not an External


48


Conditions for filter string (continued)

Condition DescriptionNOT_INTERVENTION_REQUIRED Object execution does not require

manual interventionNOT_INTVRQ Object execution does not require

manual interventionNOT_LINK Object is not a LINKNOT_ON_REQUEST Object is not defined as REQUESTNOT_OVERDUE_END Object execution end time has not

been exceededNOT_OVERDUE_START Object execution start time has not

been exceededNOT_REQUESTED Object has not been specifically

requestedNOT_RESTART_STEP_PRESENT Object does not have a restart stepNOT_TASK Object is not a TASKON_REQUEST Object is defined as REQUESTOVERDUE_END Object execution end time has been

exceededOVERDUE_START Object execution start time has been

exceededREQUESTED Object has been specifically

requestedRESTART_STEP_PRESENT Object has a restart stepTASK Object is a TASK

Note:Common conditions are available on the Filter Specifications panel and maynot require a freeform filter.

Example FilterStrings

The following table lists example filter strings and what they reveal:

Enter the following filter To see...

CRITICAL_PATH Critical path jobs


49


Example Filter Strings (continued)

Enter the following filter To see ...

ON_REQUEST AND REQUESTED On-request jobs that have beenrequested

APPL EQ 'PAYROLL' ANDRESTART_STEP_PRESENT

Jobs in the PAYROLL Applicationthat have a restart step

JOBNAME(1,1) EQ 'P' AND JSBYTEEQ 'F'

Failed objects that start with ’P’

CMPC EQ 'S222' AND SUBAPPL EQ'PAYJOBS'

Jobs with a completion code of’S222’ in the PAYJOBSsubApplication

JOBNAME(1,3) EQ 'PAY' ORJOBNAME(1,3) EQ 'ACC'AND APPLEQ 'FINANCE'

Objects that start with ’PAY’ or’ACC’ and belong to an Applicationcalled FINANCE

JOBNAME(1,4) EQ 'TEST' OR APPLEQ 'TESTAPPL' AND INCOMPLETE

Objects in Application TESTAPPLthat start with TEST and are notcomplete

APPL EQ 'CYBER' ANDOVERDUE_START AND REQUEST

Objects in Application CYBERwhose execution start time is overdue

JOBNAME(1,3) EQ 'CYB' ANDSTIME> TIME(11AM TODAY)

Objects whose names start with’CYB’ that started later than 11 a.m.today

WOBTYPE EQ 'HP' AND APPL EQ'BILLING'

All HP jobs in the BILLINGApplication

JOBNAME(1,1) EQ 'X' AND APPLEQ 'MYAPPL' AND NOT_REQUESTED

Objects that start with X inApplication MYAPPL that have notbeen requested

(JOBNAME EQ 'TESTJOB' ORJOBNAME(1,2) EQ 'A' ORJOBNAME(1,2) EQ 'BC') AND(APPL EQ 'MYAPPL' OR APPL(1,2) EQ 'PA') ANDOVERDUE_START

Objects called TESTJOB and whosenames start with the characters ‘A’ or‘BC’ and are contained withinApplication MYAPPL or anyApplication whose name starts withPA and whose execution start time isoverdue

52

ESP Applications

Overview

Introduction An ESP Application is a group of related jobs where dependencies arecontrolled at the submission level. A job in an Application is submitted to JESwhen all its dependencies (e.g. time, job and resource dependencies) are met.


Topic See PageAn Example ESP Application 53Application Generations 56Common ESP Application Statements 57Resources 64Controlling Applications 66Controlling subApplications 67Controlling Jobs in an Application 69

53

An Example ESP Application

Overview An ESP Application is made up of a series of statements to:

• Identify the Application• Tells ESP where the JCL is located• Identify the jobs to run• Describe job relationships• Describe when ESP should select the jobs to run• Tell ESP where to copy the JCL• Identify the documentation library• Describe other dependencies, such as time and resources.

APPL1 Consider the following example. In ESP Application APPL1, the flow chartdepicts the relationship between the jobs:

A

C

E

D

Daily

Daily

Daily

Friday

B

F

LastWorkday of

Month

The flow chart shows the following job dependencies: Job B and C depend onJob A to finish before they can start. Similarly, Job E depends on Job D,which depends on Jobs B and C. Job F depends on Job E.


54

An Example ESP Application, Continued

TheApplication

This is what the Application looks like:

APPL PAYROLLJCLLIB ‘CYBER.JCL.CNTL’

JOB A RUN DAILY RELEASE (B,C)JOB B RUN DAILY RELEASE DJOB C RUN DAILY RELEASE DJOB D RUN DAILY RELEASE EJOB E RUN FRIDAY RELEASE FJOB F RUN LAST WORKDAY OF MONTHENDJOB

Applicationduration

An Application does not have to complete within a 24 –hour period – it mayspan days or weeks. It is also possible to schedule an Application many timesdaily.


55

An Example ESP Application, Continued

Inheriting jobrelationships

Jobs in an Application may not require the same run frequency. ESPautomatically checks for relationships among jobs in the Application.

A

B

C

DAILY

DAILY

FRIDAY

For example, Job B runs only on Fridays. On the other days of the week,when Job B is not selected to run, Job C inherits B’s relationships, and isreleased by Job A.

You can choose not to inherit relationships with the NOINHERIT option onthe JOB statement, Job C is eligible for submission at the same time as Job A.

56

Application Generations

Overview Each time an Application is generated, a new generation of the Applicationexists. The generation number increments with each new generation.Multiple generations of an Application may process at the same time.

Generation numbers allow ESP to identify the particular generation of anApplication to which a job belongs.

Contents of ageneration

The specific contents of a generation of an Application depend upon thecircumstances at the time the Application is generated. For example, if Job Ein Application PAYROLL runs only on Fridays, the generations of APPL1created Monday through Thursday do not contain Job E.

57

Common ESP Application Statements

Overview As an operator monitoring workload as it processes on ESP, you may berequired to understand some Application statements. Some of those you maysee are:

DELAYSUB DSTRIG DUEOUTEXTERNAL LINK MANUALON REQUEST RESOURCE SUBAPPLTAG

DELAYSUB The DELAYSUB statement is used to delay the submission of a job until aspecific time or date. The DELAYSUB statement looks like the following:

JOB BILL99 DELAYSUB 11PM RUN WORKDAYS AFTER (BILL01,BILL02)ENDJOB

On CSF, BILL99 appears as follows:

Jobname Qual Jobno Appl Gen CCode Status___BILL99 1895 BILLING 12 - WAITING UNTIL 11:00___BILLUPDT - BILLING 12 - WAITING, HC=1___PAYBKUP5 1855 PAY1 73 - EXECUTING S1

DUEOUT The DUEOUT statement is used to identify a due-out time for a job from oneor more processing nodes (P-Nodes), such as INPUT, EXEC and OUTPUT.The DUEOUT statement looks like the following:

JOB PAYBKUP5 RUN LAST FRI OF MONTH DUEOUT INPUT 3AM DUEOUT EXEC 6AMENDJOB

DUEOUT statements provide a vehicle to flag overdue jobs on CSF. OnCSF, PAYBKUP5 appears as follows if it is late finishing execution:

Jobname Qual Jobno Appl Gen CCode Status___BILL99 1895 BILLING 12 - WAITING UNTIL 11:00___BILLUPDT - BILLING 12 - WAITING, HC=1___PAYBKUP5 1855 PAY1 73 - EXECUTING S1, OVERDUE


58

Common ESP Application Statements, Continued

TAG The TAG statement is used to “tag” jobs in an Application with a characterstring. The TAG statement looks like the following:

JOB PAYCHQ05 RUN FIRST MONDAY MONTHLY RELEASE TESTJOB9 TAG ‘HIGH-PRIORITY’ENDJOB

JOB PAYCHQ10 RUN FIRST MONDAY MONTHLY RELEASE TESTJOB9 TAG ‘HIGH-PRIORITY’ENDJOB

JOB PAYREPRT RUN FIRST MONDAY MONTHLYENDJOB

On CSF, PAYCHQ05 and PAYCHQ10 appear as follows:

Jobname TAG Jobno Appl Gen CCode Status___PAYCHQ05 HIGH-PRIORITY 2007 CHQS 12 16 ENDED,CCFAIL___PAYCHQ10 HIGH-PRIORITY - CHQS 12 - WAITING, HC=1

Identifying ajob as ON-REQUEST

Certain jobs can be specified to run only when requested by a user. This isaccomplished with the use of the REQUEST parameter on the JOB statement.An ON-REQUEST job is considered part of the schedule when it is selected.If the job is not selected for submission, it is bypassed, and ESP responds as ifit completed normally. For information on requesting a job, see Requesting aJob on page 108.


59


EXTERNAL An External job is a job that is actually part of another Application, called its‘home’ Application. The EXTERNAL keyword on the JOB statementidentifies a job as External to this, the ‘distant’ Application.

A

B

C

A

Y

Z

Distant - APPL2Home - APPL1

JOB A EXTERNALRELEASE Y

ENDJOB

JOB ARELEASE B

ENDJOB

In the above example, Job A exists in APPL1 but is referred to in APPL2 asan External job. APPL1 is the home Application and APPL2 is the distantApplication.

Displaying anExternal job

You can use the LAX command to display External jobs in an activeApplication. For example:

lax

WKLYPAYS.9: PAYJOB1,BILL010 REPORTS.1: JOB99 PGMS.7: PGM424 --- 3 APPLS DISPLAYED


60


MANUAL A manual job is a job that is submitted outside an ESP Application. Amanual job is identified by the MANUAL keyword on the JOB statement.ESP does not look for JCL or try to submit the job. Manual jobs can be usedas predecessors or successors to ESP jobs, but cannot have job qualifiers.

The following is an example of an Application that contains a manual job:

APPL ABCJCLLIB .....

JOB PAYXMIT MANUAL RELEASE PAY001 RUN DAILY

JOB PAY001 SEND ‘PAYJOBS NOW STARTING’ U(*)

RELEASE PAY002 RUN DAILY

JOB PAY002 RUN DAILYENDJOB

TASK A task is a manual job, defined within the Application, but still requiringmanual completion. A task may be used to represent a manual or automatedprocess, such as:• Balancing reports• Input tapes• Data set triggering at the job level• Any other special handling jobs.

A task is identified by the TASK keyword on the JOB statement. ESP doesnot try to submit JCL for a task, and the task must be marked complete usingthe AJ command or CSF.


61


LINK A link is a task that does not require manual completion. A link is identifiedby the LINK PROCESS keyword on the JOB statement. ESP does not try tosubmit JCL, and automatically marks a link complete as its dependencies aremet. You can use a link when you need to take an action, such as issue acommand or send a message.

You use a link in an Application to simplify complex dependencies. Forexample, in the following diagram, LINKJOB is used to simplify thesuccessor relationships for jobs A, B and C:

A B C

D E F

A B C

D E F

A B C

D E F

LINKJOB


62


Example Links You can use a link to issue a command. For example:

JOB OPEN.INITS LINK PROCESS VS ‘$SI1-10’ RUN DAILYENDJOB

You can use a link to keep an Application active. For example:

JOB KEEPOPEN LINK PROCESS DELAYSUB 23:59 RUN DAILYENDJOB

SUBAPPL An Application can consist of one or more subApplications. AsubApplication is used to break up large Applications into smaller, moremanageable groups of jobs. You can display, manipulate and report onsubApplications.

A subApplication is identified by the SUBAPPL statement in an ESPProcedure. The subApplication name must be unique – it cannot be the sameas any job name in the Application.

You can use the WAIT keyword to prevent processing of concurrentgenerations of the subApplication, if the WAIT keyword is not used on theAPPL statement.


63


DSTRIG You can define a data set trigger workload object as part of an ESPApplication. This allows you to set up data set dependencies at the job level.A data set trigger workload object can be completed by the successfulcreation, closure or renaming of a data set by another job, started task, or TSOuser.

A data set trigger workload object is identified by the DSTRIG statement,instead of a job statement. For example:

DSTRIG BIGFILE DSNAME PROD.FILE.CICS1602 RUN DAILY RELEASE ABCJOBENDJOB

RESOURCE You use the RESOURCE statement to identify real or abstract resourcesrequired by a job. For information on the RESOURCE statement, seeResources on page 64.

64

Resources

Overview A resource can be an item of hardware or software, or it can be an abstractcondition. Common examples of resources include:

• Scratch tapes• Execution time• An entity to control mutually exclusive jobs• On-line system availability• Time periods• Tape drives• CPU absorption.

A RESOURCE statement is used to specify that a job has a requirement for agiven number of units of a specific resource before job submission.

RESOURCEstatement

The following is an example of a job definition containing RESOURCEstatements:

JOB BILL010 RUN MON WED FRI RESOURCE (1,IMS)ENDJOB

JOB BILL020 RUN MON WED FRI RESOURCE (1,IMS)ENDJOB

In the above example, BILL010 and BILL020 each require 1 unit of IMS inorder to be submitted.


65

Resources, Continued

What it lookslike on CSF

The following example shows what CSF looks like when a job is waiting forresources:

Jobname Tag Jobno Appl Gen Pnode Status

___ BILL010 BILLING 2007 BILL 32 EXEC EXECUTING, S1 LR BILL020 BILLING - BILL 32 RESWAIT WAITING FOR RESOURCES

To see what resource a job is waiting for, type LR beside the job name, andpress Enter. The Extended Resource List panel appears:

ESP Consolidated Status: Extended Resource List ---- Row 1 of 1,

You may enter an L in front of any resource to display more information onthat specific resource, or enter an X in front of any resource to getadditional information on all the resources.

X 1 IMS

Type X beside a resource to see additional information about the resource:

---------------------------------- TOP OF DATA----------

Resource IMS Global Renewable 1 needed by BILL020, Appl BILLING.8 TORONTO * Max=1 Avail=0 1 used by BILL010, Appl BILLING.8

66

Controlling Applications

Overview As an operator, you may be required to display an Application. You candisplay an Application after it is generated. You can display all instances(generations) of the Application, or specific generations of the Application.Normally, you use CSF or ESP Workstation to control Applications.

Displaying anApplication –usingLISTAPPLcommand

Once an Application is generated, you can display it. You can display itthrough CSF, ESP Workstation, or using the LISTAPPL command. The shortform of the command is LAP. You can use the command with the ALLkeyword to give a structured view of an active Application (i.e. one withincomplete jobs) or with other keywords, to give a summary of active orcompleted Applications. The display can be limited to specific generations ifrequired. For more information on displaying an Application, see ListApplication (LAP) Command on page 140.

67

Controlling subApplications

Overview An ESP subApplication is a grouping of jobs within an Application. LargeApplications may be broken into smaller, easier to manage groups of jobs.An Application may contain multiple subApplications.

You can display, control and report on subApplications.

Defining asubApplication

You define an ESP subApplication using a SUBAPPL statement in an ESPProcedure. Choose a name that is unique – it cannot be the same as any jobname within the Application.

Controlling asubApplication

You can control a subApplication using CSF commands, or the APPLJOB(AJ) command.

You control a subApplication similar to the way you control jobs. You can:• Bypass or unbypass a subApplication• Request or unrequest a subApplication• Hold or release a subApplication• Complete a subApplication• Un-wait a subApplication.


68

Controlling subApplications, Continued

Example of asubApplicationdefinition

The following is an example of an ESP Application that containssubApplications:

APPL ACCOUNTSJCLLIB .....

JOB ACCTG1SUBAPPL ACCTSRECRUN DAILYRELEASE ACCTG2

ENDJOBJOB ACCTG2

SUBAPPL ACCTSRECRUN DAILYRELEASE ACCTG3

ENDJOBJOB ACCTG3

SUBAPPL ACCTPAYRUN DAILY

ENDJOBJOB ACCTG5 RUN WORKDAYSENDJOBJOB ACCTG6

RUN WORKDAYSENDJOB

Example2 of asubApplicationdefinition

The following example shows another method of coding subApplications:

APPL ACCOUNTSJCLLIB .....

SUBAPPL ACT1JOB JOB1 RUN DAILY RELEASE JOB2ENDJOBJOB JOB2 RUN DAILY RELEASE JOB3ENDJOBSUBAPPL ACT2JOB JOB3 RUN DAILYENDJOB

69

Controlling Jobs in an Application

Overview As an operator, you may be required to:

• Hold or release a job in an active Application• Bypass or unbypass a job in an active Application• Mark a job or manual task complete in an active Application• Request a job• Reset a time dependency• Resubmit a job in an Application• Remove predecessor relationships from a job.

You can control jobs using CSF, ESP Workstation, or using the APPLJOBcommand.

Using CSF You control jobs from CSF by typing a command next to the jobname on theCSF display:

When you control jobs on CSF, it is the APPLJOB command you areinvoking in the background. For more information on controlling workload,see Controlling the Work on page 100.


70

Controlling Jobs in an Application, Continued

UsingAPPLJOBcommand

You can control the jobs in an Application using the APPLJOB command.The short form of this command name is AJ. A jobname or job number is allyou need to identify the job if it is submitted and has a JES number assigned.The Application is located via the tracking files.

If the job is not yet submitted, augment the job name with the Applicationname. If more than one generation of the Application is active, you must alsospecify the relative or absolute generation of the Application.

For more information on the APPLJOB command, see APPLJOB (AJ)Command on page 139. For the syntax of the APPLJOB command, see theESP Command Reference or the ESP Command Quick Reference.

72

ESP Events

Overview

Introduction If you want to run an ESP Application at a certain time every day, you need away to tell that to ESP. The object you use is called an Event. An Eventdefines:

• When ESP must perform the work• What actions ESP must take to perform the work.


Topic See PageFunctions of an Event 73Defining an Event 75Data Set Triggering 77Scheduling an Event 78Displaying the Schedule 79Displaying When an Event Will Execute 80Postponing Event Execution 81Bypassing Event Execution 83Triggering an Event Manually 84Simulating an Event 88Simulating the Next Occurrence 89Simulating a Specific Day 92

73

Functions of an Event

Overview An Event can be used to:

• Invoke an ESP Application:• Scheduled or data set triggered

• Submit a job or group of jobs• Send a message• Issue an MVS operator command.

Sending amessage

You can use an Event to send a message. The following example sends a‘good morning’ message to user USER01:

EVENT ID(CYBER.MESSAGE) SYSTEM(ES51)SCHEDULE 8AM DAILYSEND ‘GOOD MORNING’ U(USER01)ENDDEF

SubmittingJCL

You can use an Event to submit JCL. The following example submitsmember PROD001 from the JCL library CYBER.ESP.CNTL:

EVENT ID(CYBER.SUBMIT) SYSTEM(ES51)SCHEDULE 8AM DAILYSUBMIT ‘CYBER.ESP.CNTL(PROD001)’ENDDEF

Invoking anESP Procedure

You can use an Event to invoke an ESP Procedure. The following exampleinvokes the TESTPROC procedure in CYBER.ESP.PROC:

EVENT ID(CYBER.PROC) SYSTEM(ES51)SCHEDULE 8AM DAILYINVOKE ‘CYBER.ESP.PROC(TESTPROC)’ENDDEF

Issuing an MVScommand

You can use an Event to issue an MVS command. The following exampleissues the VS command:

EVENT ID(CYBER.COMMAND) SYSTEM(ES51)SCHEDULE 8AM DAILYVS ‘$TI1-15,C=A’ENDDEF


74

Functions of an Event, Continued

Data settriggering

You can trigger an Event based on data set activity. For more information,see Data Set Triggering on page 77.

Triggerdiagram

The following diagram illustrates what happens when an Event is triggered:

Trigger

Event

Send aMessage

Submit JCLOperator

CommandInvoke ESPProcedure

- Scheduled date and time- Data set trigger- Manual trigger- Job monitor trigger- Alert trigger

75

Defining an Event

Overview When you define an Event, you define what you want ESP to do, where andwhen you want it done. Use one of the following methods to create an Event:

• ESP panels• Edit an existing Event and give it a new Event name• ESP Page mode commands• The LOAD command to copy an Event from a data set.

Creating anEvent using theESP panels

Step Action1 Name the Event.

An Event name has two parts:• Prefix – name of a user or group, up to 8 characters in length• Descriptive name – up to 16 characters in length including

national characters and underscore.ESP verifies security requirements when the Event is triggered.

2 Specify when the Event will execute.The trigger for the Event can be:• A scheduled date and time• A data set trigger• A manual trigger (the default)• A job monitor or Alert trigger.

Schedule criteria looks like:• SCHEDULE 8PM THIRD FRIDAY OF MONTH• SCHEDULE 22.00 LAST DAY OF MONTH LESS 1 WORKDAY• SCHEDULE 3PM DAILY

NOSCHED 3PM FRIDAY


76

Defining an Event, Continued

Eventdefinition

An Event definition is made up of the following:

• EVENT command• ID field, which identifies the name of the Event• SYSTEM field, which identifies the ESP subsystem on which the Event

executes• SCHEDULE command, which tells ESP when to trigger the Event• What ESP is to do – INVOKE a Procedure, SEND a message, and so on• ENDDEF command, which indicates the end of the definition.

Eventdefinitionexample

The following is an example of an Event definition:

EVENT ID(CYBER.PAYROLL) SYSTEM(ES51)SCHEDULE 5PM MONDAYINVOKE ‘CYBER.PROD.PROC(PAYROLL)’ENDDEF

Eventset Events are stored in a VSAM data set called an Eventset.

77

Data Set Triggering

Overview You can use a data set trigger to trigger an Event automatically on data setactivity. A data set trigger can be used on:

• The creation of a data set (this is the default)• The closure of a data set after an update• The renaming of a data set.

ESP supports data set triggering with multiple data sets and multiple closures.Data set triggering can be restricted to data sets created by a specific job orgroup of jobs.

Example ofdata settriggering oncreation

In the following example, the Event triggers on the creation of the data setPROD.ACCT.BKUP99:

EVENT ID(CYBER.BKUP99) SYSTEM ES51DSTRIG PROD.ACCT.BKUP99INVOKE ‘ACCT.MONTHLY.PAYROLL(PAY1)’ENDDEF

Example ofdata settriggering onupdate orcreation

In the following example, the Event triggers on the update or creation of thedata set PROD.ACCT.BKUP99:

EVENT ID(CYBER.BKUP99) SYSTEM ES51DSTRIG PROD.ACCT.BKUP99 ANYCLOSEINVOKE ‘ACCT.MONTHLY.PAYROLL(PAY1)’ENDDEF

78

Scheduling an Event

Overview An Event can be triggered manually, or automatically, by telling ESP when todo so (for example, 6 pm daily). An Event can also be triggered by data setactivity.

Scheduling anEvent once

To schedule an Event to execute only once followed by the deletion of theEvent, use the ONCE keyword with the SCHEDULE command. This isuseful for one-time Events. If you do not specify ONCE, ESP assumes theEvent runs daily. The following example schedules an Event only once:

EVENT ID(CYBER.TEST) SYSTEM(ES51)SCHEDULE 8AM SATURDAY ONCESUBMIT ‘CYBER.JCLLIB.CNTL(ONETIME)’ENDDEF

Event data set At regular intervals (e.g. 6 a.m. each day), ESP scans the Event data set(EVENTSET) and builds a schedule of work to be executed during thatschedule cycle. A schedule cycle is the time between successive scans of anEvent data set. The schedule cycle can be set according to the requirements ofyour installation when ESP is installed. A message is issued at the start andend of each scan through the data set. As ESP scans the data set, it also takes abackup copy.

Displaying theschedule

Once the schedule is built, it can be displayed using the LISTSCH (listschedule) command. This command allows the display to be limited to:

• A certain time range, or• A generic Event name specification.

If an Event is to execute more than once during the current schedule cycle,only the first scheduled execution is displayed. This is because ESP stores anEvent entry only once in the schedule. When the scheduled time arrives, ESPthen calculates and stores the next execution time.

79

Displaying the Schedule

Overview You can display the schedule using the LISTSCH command. It displays thenames of the Events and their scheduled execution times. The names of anyjobs to be submitted are not displayed; one Event can submit several jobs.Job names are displayed by generating a scheduled activity report. Forinformation on the Scheduled Activity Report, see Scheduled Activity Reporton page 132.

The LISTSCHcommand

The following LISTSCH command lists the entire current schedule betweenone schedule scan and the next:

LISTSCH

The following example displays all Events with names beginning ‘GR’ thatare scheduled between 11 pm and 1:30 am:

LISTSCH LEVEL(GR-.-) FROM(23.00) TO(01.30)

In many cases, the LISTSCH command may not provide an operator withsufficient information to be of use. If you want a forecast of the schedule atthe job level, you need to produce a scheduled activity report. For moreinformaton see Scheduled Activity Report on page 132.

80

Displaying When an Event Will Execute

Overview You can display when an Event will execute using option 5 (NEXT) from theEvent Management panel (E.5 option). The Display Next Execution Timespanel appears:

You can enter a number (up to a maximum of 99) of next scheduled executiontimes for the Event in question. The Event must contain at least oneSCHEDULE or EXPECT command.

81

Postponing Event Execution

Overview You can postpone Event execution by placing an Event on hold until suchtime as you want it to execute. You use the HOLD and RELEASE commandsrespectively to hold and release an Event.

If an Event is in the hold state, it is placed in an overdue condition. When theEvent is finally released, the overdue count is checked to see whetherexecution should proceed. The Event is checked immediately for everyoccurrence missed while in the held state, up to the overdue limit countspecified when the Event was defined.

If an Event is in both a suspended and held state when due for scheduling, thehold state is ignored, and the Event is considered suspended.

HOLDcommand

The HOLD command postpones execution of an Event until you RELEASEit. Specify the name of the Event to be held and the Event has its hold countincremented immediately. While the hold count of an Event is greater thanzero, it does not execute. Missed executions of the Event while in the heldstate are processed up to the overdue count of the Event.

The following is an example of the HOLD command:

HOLD PROD.BIGEVENT

The above example increments the hold count of the EventPROD.BIGEVENT by 1.

RELEASEcommand

The RELEASE command is used in conjunction with the HOLD commandand decrements the hold count of an Event. When the hold count reacheszero, the Event is eligible for execution.


82

Postponing Event Execution, Continued

OverdueEvents

An Event can miss its scheduled execution time for many reasons. Some ofthese are:

• System trouble• Event was held• Event’s class was held• ESP was quiesced• No Event initiators were available• Eventset (Event data set) was suspended.

OVERDUEcount

An Event is marked OVERDUE if it is held at its scheduled execution time.

You use the OVERDUE count with the SCHEDULE command to tell ESPhow many times the Event can execute if it misses more than one scheduledexecution.

When it is RELEASED, an Event executes once for every missed occurrence,up to the overdue count. The default is 1.

The following is an example where the Event is not allowed to execute if itmisses its scheduled execution time:

SCHEDULE 10AM WORKDAY OVERDUE(0)

83

Bypassing Event Execution

Overview You can bypass Event execution by suspending the Event until such time asyou want it to execute. You use the SUSPEND and RESUME commandsrespectively to suspend and resume an Event.

If the scheduled time for an Event arrives while it is in the suspended state,the Event execution is bypassed, and it is not considered overdue.

If an Event is in both a suspended and held state when due for scheduling, thehold state is ignored, and the Event is considered suspended.

SUSPENDcommand

The SUSPEND command bypasses execution of an Event until youRESUME it. Specify the name of the Event to be suspended and the Eventhas its suspend count incremented immediately. While the suspend count ofan Event is greater than zero, it does not execute.

The following is an example of the SUSPEND command:

SUSPEND PROD.BIGEVENT

The above example increments the suspend count of the EventPROD.BIGEVENT by 1.

RESUMEcommand

The RESUME command is used in conjunction with the SUSPENDcommand and decrements the suspend count of an Event. When the suspendcount reaches zero, the Event is eligible for execution at its next scheduledtime.

84

Triggering an Event Manually

Overview An Event can be triggered manually in the following ways:

• From the ESP panels• Using the TRIGGER command.

From the ESPpanels

To trigger an Event using the ESP panels, start at the ESP Main Menu and dothe following:

Step Action1 Choose to work with Events.

At the Main Menu, choose option E (Events):

Press Enter. ESP displays the Event Management Menu.

At the Event Management Menu, select option 3, Control an existingEvent. Press Enter.


85

Triggering an Event Manually, Continued

From the ESP panels (continued)

Step Action2 Control an Event.

The next panel is the Event Control Menu:

Press Enter. The List Events panel appears.3 Choose the Event from the list and trigger it.

The List Events panel lists the Events belonging to your user id. Itlooks like this:

Type t next to the Event you want to trigger and press ENTER.ESP displays the Trigger An Event panel.


86


From the ESP panels (continued)

Step Action4 Add the Event to the schedule.

On the Trigger An Event panel, type ADD in the REPLACE/ADDfield. ADD results in an additional execution of the Event. Leaveall other fields blank:

Press Enter. You return to the List Events panel. Note the ESPmessage ‘Event Triggered’ in the top right corner of the panel.


87


ADD option The ADD option executes the Event in addition to the Event’s normalscheduled execution date and time.

REPLACEoption

The REPLACE option executes the Event in place of the Event’s normalexecution date and time. This is the default.

TRIGGERcommand

You can trigger an Event manually using the TRIGGER command. Specifythe name of the Event and either the ADD option or the REPLACE option.

If you specify ADD, the Event is scheduled for execution as if a SCHEDULEstatement was processed and consequently adds an extra execution to thenormal schedule for the Event. A TRIGGER ADD always causes theexecution of an Event.

The REPLACE option merely brings forward the next scheduled executionfor that Event. If the next statement in the Event is a HOLD statement, thatstatement is processed by the TRIGGER, rather than an execution of theEvent. Before issuing a TRIGGER REPLACE, you should be aware of thenext action to be processed for that Event.

The AT keyword allows you to specify a future time and date for the trigger tooccur, overriding the default of NOW. If you specify REPLACE, the triggerreplaces the next scheduled execution on or after the specified time.

To change the default used when an Event is triggered manually, use theTRDFLT command. The option you specify applies until the next time ESPis initialized.

Example 1 The following example creates an additional execution of FIRST_EVENT:

F ESP,TRIGGER FIRST_EVENT AT(’19:00’) ADD

Example 2 The following example replaces the next scheduled execution ofLAST_EVENT:

F ESP,TRIGGER LAST_EVENT AT(‘NOW PLUS 10 MINUTES’)

88

Simulating an Event

Overview You can simulate the execution of an Event to see:

• What would happen if an Event was triggered on a certain day• If any syntax errors or successor loops occur• Which workload objects ESP submits.

You can simulate the next occurrence of an Event, or the actions of the Eventat a specific date or time.

Refer to the examples on the following pages to simulate the next occurrenceof an Event, or to simulate a specific date and time.

89

Simulating the Next Occurrence

Overview The following example steps you through the simulation of an Event using theEvent panels.

Procedure To simulate the next occurrence of an Event, begin at the Main Menu, andfollow these steps:

Step Action1 Choose to work with Events.

At the Main Menu, select option E (Events). Press Enter.Selecting this option takes you to the Event Management Menu.

2 Control an existing Event.At the Event Management Menu, select option 3 (Control anexisting Event). Press Enter. ESP takes you to the Event ControlMenu.

3 Leave the option blank and press Enter.At the Event Control Menu, leave the option blank and pressEnter to see a list of Events.


90

Simulating the Next Occurrence, Continued

Procedure (continued)

Step Action4 Simulate the Event.

Type M next to payroll:

Press Enter. The Simulate Event Execution panel appears:

Press Enter. ESP starts the Event simulation and presents theresults.


91

Simulating the Next Occurrence, Continued

The simulationresults

The following panel shows the results of the simulation:

The following line indicates the name of the simulated Event(USER01.PAYROLL) and the time and date:

SIMULATION OF Event USER01.PAYROLL AT hh.mm.ss ON dddddd...

The next two lines name the jobs and give the total number of jobs simulatedto run. The remaining lines list each simulated job, its hold count, and the jobit was simulated to release. The hold count associated with a job indicates thenumber of immediate predecessors. For details on hold count, refer to theESP User’s Guide.

Scroll through the results and check for any errors.

Press End twice to return to the Event Control Menu and continue to the nextsimulation. (If you want to return to the Main Menu, press End twice more.)

92

Simulating a Specific Day

Overview In this example, you simulate triggering the Event on the next Friday. Youcan assume both of the following:

• The next Friday is not the last workday of the month• You are at the Event Control Menu. Refer to steps 1 and 2 of the previous

topic if you are at the Main Menu.

The simulation Follow these steps:

Step Action1 Leave the option blank and press ENTER.

At the Event Control Menu, leave the option blank and pressENTER to see a list of Events.

2 Simulate the EventType M next to payroll, and press ENTER. The Simulate EventExecution panel appears.


93

Simulating a Specific Day, Continued

The simulation (continued)

Step Action3 Enter the day to be simulated.

Type the schedule criteria:

SCHEDULE TIME ==> friday

The panel looks like this:

Press Enter. ESP starts the Event simulation and presents theresults in a panel like this:

Press End twice to return to the Event Control Menu and tocontinue to the next simulation. (If you want to return to the MainMenu, press End twice more.)

94

Scheduling Workload

Overview You can schedule workload in a variety of ways using ESP. This chapterdiscusses scheduling criteria and ESP calendars.


Topic See PageSchedule Criteria 95Calendars 97

95

Schedule Criteria

Overview ESP recognizes scheduling criteria specified in plain English. Schedulecriteria can be used in:

• Events• ESP Procedures and Applications• Symbolic variables• ESP Built-in functions• Calendar definition panels• Various ESP commands• Reporting criteria.

Specifyingschedulecriteria

Schedule criteria can consist of:

• Days of the week• Month names• Time zones• Time of day• Days of months• Julian dates

Examples ofschedulecriteria

The following are examples of schedule criteria:

• 6AM DAILY• MON WED FRI• DAILY EXCEPT HOLIDAYS• 19.00 WEEKENDS• EVERY 2 WORKDAYS STARTING FRIDAY• LAST WORKDAY OF WEEK• 7PM FIRST WORKDAY OF MONTH• 8:00 LAST SAT OF MONTH STARTING OCT 1995• 15TH DAY OF MARCH JUNE AUGUST• LAST DAY OF MONTH LESS 1 WORKDAY


96

Schedule Criteria, Continued

Testingschedulecriteria

Use the TEST command (option E.4 of the ESP panels) to test schedulecriteria. This tests any date or schedule specification. ESP responds to thetest with the actual date and times the criteria resolves to. For example:

TEST (5) LAST WORKDAY OF MONTH!

00.00.00 TUESDAY JANUARY 31ST, 1995, DAY 031 00.00.00 TUESDAY FEBRUARY 28TH, 1995, DAY 059 00.00.00 FRIDAY MARCH 31ST, 1995, DAY 090 00.00.00 FRIDAY APRIL 28TH, 1995, DAY 118 00.00.00 WEDNESDAY MAY 31ST, 1995, DAY 151

97

Calendars

Overview ESP uses one or more calendars to store definitions of scheduling elements –some general and some unique to your installation. Your ESP Administratordefines any calendars to meet your installation’s requirements, and controlsthe access to those calendars.

What theyidentify

Calendars identify workdays, the first day of the week, the start time for a day,special days, holidays and so on.

You do not need to define calendar terms to ESP in order to use them.

Holidays Holidays are defined in your calendar, and you refer to them as you would anyother scheduling term:

• 16:00 HOLIDAY• 10PM CHRISTMAS• BANK_HOLIDAY LESS 1 WORKDAY

Special days Special days are defined similarly to holidays and referenced in the samemanner:

• 5PM BALANCE_DAY• 3PM BALANCE_DAY LESS 2 WORKDAYS• 16:00 BALANCE_DAY PLUS 1 WEEK

Special periods A Special period is the time between two like-name Special days:

• LAST DAY OF PAYROLL_PERIOD• FIRST WORKDAY OF PAYROLL_PERIOD


98

Calendars, Continued

Examplecalendar

The following is a display of calendars:

ESP ------------------------------ CALENDARS ---------------------------COMMAND ===> Enter D against holidays or special days to delete, then press ENTER

NAME START DATE END DATE CALENDAR

QUARTER 00.00 FRI 1 JAN 1995 SYSTEM QUARTER 00.00 SAT 1 APR 1995 SYSTEM GOOD_FRIDAY 00.00 FRI 14 APR 1995 00.00 SAT 15 APR SYSTEM MONTH_END 00.00 FRI 7 MAY 1995 SYSTEM VICTORIA_DAY 00.00 MON 24 MAY 1995 00.00 TUE 25 MAY SYSTEM QUARTER 00.00 SAT 1 JUL 1995 SYSTEM PAYDAY 00.00 FRI 30 JUL 1995 PAY1 MONTH_END 00.00 FRI 4 AUG 1995 SYSTEM PAYDAY 00.00 THU 31 AUG 1995 PAY1 PAYDAY 00.00 FRI 29 SEP 1995 PAY1 QUARTER 00.00 SUN 1 OCT 1995 SYSTEM PAYDAY 00.00 TUE 31 OCT 1995 PAY1 PAYDAY 00.00 THU 30 NOV 1995 PAY1 CHRISTMAS_HOL 00.00 MON 25 DEC 1995 00.00 WED 27 DEC SYSTEM PAYDAY 00.00 FRI 29 DEC 1995 PAY1 FISCAL_YEAR 00.00 THU 1 AUG 1996 BILLING FISCAL_YEAR 00.00 FRI 1 AUG 1997 BILLING FISCAL_YEAR 00.00 SAT 1 AUG 1998 BILLING

100

Controlling the Work

Overview

Introduction This chapter discusses some of the typical operator tasks you may be requiredto perform.

Most commonly, you control workload using the Consolidated Status Facility(CSF), or ESP Workstation.

CSF commands Many CSF commands exist that allow you to control workload objects on theCSF display. For more information on these commands, refer to CSFCommands on page 27.


Topic See PageHolding a Job 101Completing a Job 103Bypassing a Job 105Resubmitting a Job 107Requesting a Job 108Inserting a Job 109Dropping Dependencies 111Resetting a Time Dependency 114Holding an Application 115

101

Holding a Job

Overview You can place a job on hold until such time as you want it to run. TheConsolidated Status Facility (CSF) is one method used to hold a job.

Example The following illustrates holding a job from CSF:

Step Action1 At the Main Menu, select option C (CSF). Press Enter. Selecting

this option takes you to the Consolidated Status Facility display:

2 Place the job on Hold.Type H next to the job you want to place on hold. Press Enter.The status of the job is updated to show the job is waiting, and itshold count is increased by one:


102

Holding a Job, Continued

Holding a jobwith a reason

You can specify a reason when you place a job on hold. The reason you typeappears in the CSF User Status field, and can be used for a variety ofpurposes. For example, you can use it to indicate the job is waiting until aprogrammer makes a last-minute change.

If you want to specify a reason when you place the job on hold, begin at theMain Menu and do the following:


this option takes you to the Consolidated Status Facility display.2 Place the job on Hold with a reason.

Type HR next to the job you want to place on hold. Press Enter.The status of the job is updated to show the job is waiting, anddisplays the reason you entered. The hold count is increased byone.

103

Completing a Job

Overview You can complete a job from CSF. You may want to do this if a job iswaiting for a dependency to be met, and its successor job can no longer waitbefore running. If you force the job complete, its successor can run.

Example The following illustrates how to force a job complete from CSF:



2 Force the job complete.Type C next to the job you want to complete. Press Enter. Thestatus of the job is updated to show the job Completed (F):

Completing ajob in Pagemode

To complete a job from Page mode, you issue the AJ command. Forexample:

AJ JOB3 APPL(PAYROLL.12) COMPLETE

In the above example, JOB3 in generation 12 of the PAYROLL Application isforced complete.


104

Completing a Job, Continued

Completingexternal jobs

If you complete a job in the distant Application, it affects only thatApplication. It has no effect on the home Application.

If you complete a job in its home Application, it posts it complete in thedistant Application. (Your installation may override this behavior by settingUSERMOD 30 on.)

Complete orbypass?

If you are uncertain if you want to force a job complete or bypass it, refer toDifference between bypassing and completing on page 106.

105

Bypassing a Job

Overview You can bypass a job from CSF. You do this when you do not require thisjob to run. If you bypass a job, its successor can run.

Example The following illustrates how to bypass a job from CSF:



2 Bypass the job.Type BY next to the job you want to bypass. Press Enter. Thestatus of the job is updated to show the job Bypassed:


106

Bypassing a Job, Continued

Differencebetweenbypassing andcompleting

When you complete a job, ESP decreases the hold count of its successors by1. In the following diagram, if you complete B, C runs, even if A is stillrunning. There is no way to reverse this action.

A

B

C

However, if you bypass B, you are indicating you are not going to run B – it isthe same as canceling the job off the schedule.

ESP does not bypass the job until it would normally be submitted. You canunbypass the job up to its normal submission time.

107

Resubmitting a Job

Overview You can resubmit a job, if it fails to complete successfully. The job is rerunfrom its first job step, unless you specify otherwise. You can resubmit a jobfrom a different library, such as the COPYJCL library.

Example The following illustrates how to resubmit a job from CSF:



2 Resubmit the job.Type R next to the job you want to resubmit. Press Enter. TheResubmit an Object display appears:

Enter a library name if you want to resubmit the job from adifferent library, specify the start and end steps, and any othervalues. Press Enter. The job is eligible for submission again.

External jobs You must resubmit a job in its home Application.

108

Requesting a Job

Overview Certain jobs are defined as REQUEST jobs. These are jobs that must berequested manually before they can run. A typical request job might be onethat must be ready to run if requested, but a user may not require it every day.Building it into an Application ensures that any predecessor or successordependencies are met in case the job is run.

A REQUEST job is considered part of the schedule when selected, but is onlyselected on request. If the job is not requested prior to its scheduledsubmission time, it is bypassed, and treated as a normal completion.

Example The following illustrates how to request a job from CSF:



2 Request the job.Type RQ to request the job. The status is updated to indicate thejob is requested.

109

Inserting a Job

Overview You can use the INSERT JOB (IJ) command to insert a job into an activeApplication. The inserted job runs immediately unless you define apredecessor or insert the job on hold.

Inserting a job When an Application is displayed on CSF, you can insert a job into thatApplication. To insert a job, do the following:

Step Action1 Type IJ next to the Application. The Insert an Object panel

appears. Type the name of the job you want to insert, and if thereare any predecessors or successors to the job. Specify any otherconditions, such as if this is a conditional or request job, or if youwant the job inserted on hold:


110

Inserting a Job, Continued

Inserting a job (continued)

Step Action2 Press Enter. If you specified Y to predecessors, the Define

Predecessors panel appears. Define the predecessors to the job:

Press Enter. The job is inserted.

111

Dropping Dependencies

Overview You can drop one or more dependencies when you want a job to run in spiteof an unfulfilled dependency. You can drop one or more predecessors, or youcan drop all resource dependencies of a job.

Droppingresources

Before you drop a job’s resources, you may want to display the job’s resourcedependencies. To display and then drop the job’s resource dependencies,begin at the Main Menu and follow these steps:



2 Display the job’s resource dependencies.Type LR next to the job whose resources you want to display, andpress Enter. The Extended Resource List display appears:

The Extended Resource List display lists the resourcedependencies for a job, and allows you to obtain more informationabout the resource dependencies.


112

Dropping Dependencies, Continued

Dropping resources (continued)

Step Action3 Typing L displays more information about a specific resource:

Press End to return to CSF.4 Drop the resource dependencies.

Type DR to drop all of the resource dependencies, and pressEnter. All resource dependencies for the job are dropped.

Drop allpredecessors

The following illustrates how to drop all of a job’s predecessors:



2 Drop all predecessors.Type DD next to the job whose predecessors you want to drop, andpress Enter. The job becomes eligible for submission.


113

Dropping Dependencies, Continued

Drop one ormorepredecessors

The following illustrates how to drop one or more of a job’s predecessors:



2 Display the job.Type L next to the job for which you want to drop a predecessor,and press Enter. The Extended Job List display appears.

3 Delete the predecessor(s).Type D next to the predecessor(s) you want to delete, and pressEnter.

114

Resetting a Time Dependency

Overview You can reset a time dependency if a job is waiting until a particular time torun, and you want to run it sooner, or if you want the job to wait until a latertime to run.

Example The following illustrates how to reset a time dependency:



2 Reset the time.Type RT next to the job whose time dependency you want to reset,and press Enter. The Reset Object Times display appears:

Enter the new values or simply edit existing values and pressEnter. The time is reset.

115

Holding an Application

Overview You can place an entire Application on hold by issuing a command next toany job in that Application.

Example The following illustrates how to hold an Application:



2 Hold the Application.Type HA next to any job in the Application you want to hold, andpress Enter. The Application is placed on hold – APPLHOLD isdisplayed:

116

Working with Delayed Events

Overview

Introduction Several circumstances can cause the execution of an Event to be delayed. Themore common ones are:

• System outage• Data set contention• Event data set unavailability.


Topic See PageSystem Outage 117Data Set Contention 118Event Data Set Unavailability 119Extended Outages 120Restarting ESP in Phases 122

117

System Outage

Overview If the system is down because of software or hardware outages, some Eventscannot execute at the scheduled time. When ESP is restarted, it processes alloverdue Events.

Overdue count When an Event is considered overdue, an attribute in the Event definition isexamined to determine how to process it. This attribute is called the overduecount, which is specified in a schedule statement in an Event definition.

The overdue count specifies how many overdue occurrences of the Event areto be executed once the system is re-instated. For example, if an Event isscheduled to execute once an hour, and the system is down for three hours,the Event misses three scheduled executions.

Overdue countof zero

An overdue count of zero (0) indicates that the Event should only execute atits scheduled time. If the system is down at that time, the Event does notexecute.

118

Data Set Contention

Overview If one or more data sets required for a job are allocated exclusively to anotheruser or job, a message is issued and the Event is delayed for up to fiveminutes. This process is repeated until all the data sets are available for sharedallocation.

119

Event Data Set Unavailability

Overview An Event data set may become unavailable for several reasons:

• If a severe I/O error occurred on the data set, an error message is issuedand the data set may be placed in the suspended state.

• It might be necessary to suspend the data set manually for other reasons,such as problems with the catalog, disk recovery, etc.

Data set issuspended

If the data set where an Event resides is in the suspended state, a warningmessage is issued and the Event is placed on the deferred queue.

Displaying thedeferred queue

You can display the deferred queue by using the LISTSCH command with theDEFERRED option, and specifying the identifier of the Event data set. Forexample:

LISTSCH DEFERRED(EVENT1)

where EVENT1 is the Event data set id.

When data setis availableagain . . .

Once the data set is made available again, take the data set out of thesuspended state by issuing the EVENTSET command and specifying theOPEN option:

EVENTSET EVENT1 OPEN

As a result of the above command, all the deferred Events in EVENT1 areplaced on the OVERDUE queue. Once in the OVERDUE queue, the Eventsare processed as if they were overdue because of a system outage. TheOVERDUE COUNT determines how they are to be processed.

Displaying theoverdue queue

You can display the OVERDUE queue, by using the LISTSCH command, andspecifying the OVERDUE keyword:

LISTSCH OVERDUE

In most situations, the OVERDUE queue is empty, because any Events in itare eligible for immediate execution. However, when ESP is quiesced, Eventsremain on the OVERDUE queue.

120

Extended Outages

Overview In the case of an extended outage, the actions to be performed by the Eventsmay already be done manually. In this case, you must prevent the deferredexecutions from taking place again when the data set is reinstated. You cando this in several ways:

• FLUSH the entire deferred queue• HOLD or SUSPEND the Events by CLASS• Open the affected Event data set and SUSPEND individual Events.

Flushing thedeferred queue

You can flush the deferred queue without opening the Event data set. Toflush the deferred queue, use the EVENTSET command, and specify FLUSH:

EVENTSET EVENT1 FLUSH

Where EVENT1 is the Event data set ID. The above command flushes theentire deferred queue for the EVENT1 data set.

Holding orsuspendingEvents

If you do not want to flush all the Events in the queue for a data set, you canuse the CLASS command to HOLD or SUSPEND Events. The EVENTSETOPEN command can then be used to take the data set out of the suspendedstate.

Classes ofEvents

When an Event is defined, it can be associated with a particular class. A classis a user-defined string of up to eight characters, which can be used to groupEvents logically together. If a class name is omitted, the prefix of the Eventname is used by default in place of a class.

CLASScommand

The CLASS command operates on classes of Events. You can use the CLASScommand to SUSPEND one or more classes. When an Event is scheduled andits class is in the suspended state, the Event execution is bypassed. As soon asyou remove the required Events from the deferred or overdue queue, theclasses that were previously suspended can be resumed.


121

Extended Outages, Continued

SuspendingindividualEvents

During an extended system outage, if only a few Events were manuallyscheduled, and you do not want to flush the entire Event data set queue or tosuspend entire classes, you can quiesce ESP. This temporarily stops all Eventexecutions. Open the affected Event data set, and suspend specific Events,using the SUSPEND command.

Resumingnormalscheduling

You can resume normal scheduling with the RESTART command. You canresume specific Events that were previously suspended.

122

Restarting ESP in Phases

Overview At startup time, ESP can detect that a system outage occurred. An installationcan define a system outage as any period that ESP or the operating system isinactive. The default is 60 minutes. When an outage is detected, ESPprompts the operator indicating the current time and last time of execution.

On notificationof systemoutage . . .

When ESP notifies you of a system outage condition, you can use thefollowing manual procedure to restart ESP in phases, or you can define aCLIST to automate a phased restart.

Manual, phasedrestart

The following table shows how to manually restart ESP in phases:

Step Action1 Start ESP in a quiesced state. Issue the following command:

S ESP,PARM=(QUIESCE)

Because you started ESP in a quiesced state, no new work issubmitted. ESP continues to track jobs and respond to operatorsand users.

2 Issue CLASS commands to hold or suspend low and mediumpriority Events, and to exempt high priority groups of Events byusing explicit names or wildcard characters for genericspecification.

3 Remove ESP from its quiesced state using the RESTARTcommand:

F ESP,RESTART or OPER RESTART

Processing of high-priority Events begins.4 As priority work completes, release medium and then low-priority

classes in a staged manner as required.


123

Restarting ESP in Phases, Continued

Automating aphased restart

The following table shows how to automate a phased restart:

Step Action1 After startup, define the commands like the following in a CLIST:

CLASS S- HOLDCLASS W- HOLDCLASS S027 EXEMPTRESTART

where class S027 defines the high priority Events.2 After the high priority work is complete, specify the following:

CLASS S- RELEASE

where class S defines the medium priority Events.3 After the medium priority work is complete, specify the following:

CLASS W- RELEASE

where class W defines the low priority Events.

124

Working with ESP Classes

Overview

Introduction ESP Events can be grouped into classes. A class name can be assigned to anEvent when it is defined. If a class name is omitted from an Event definition,the Event name prefix (the part before the period - either a userid or a groupname) is used as the class name.


Topic See PageControlling Classes 125Hold Queues 126Masking 127Multiple Class Restrictors 128

125

Controlling Classes

Overview As an ESP operator, you can control multiple ESP Events by controlling theEvent classes. To control Event classes, you use the CLASS command. TheCLASS command places restrictions on the execution of an individual class,or a group of classes. The CLASS command can be used to perform thefollowing actions on a class of Events:

• Suspend a class of Events• Hold a class of Events• Make a class of Events exempt from a particular action.

Before anEvent isexecuted

Before an Event is executed, its class restrictors are examined to see if theclass the Event belongs to is restricted. If the class is restricted, the actionspecified by the restriction for that Event is taken.

Suspendrestrictor

The SUSPEND restrictor bypasses all Events in a specified class during thetime the SUSPEND restrictor is in effect. A warning message is issued at thetime the Event is scheduled to execute.

Hold restrictor The HOLD restrictor places Event on hold as soon as they are scheduled toexecute. The Events are held in queues by class name.

Exemptrestrictor

The Exempt restrictor prevents the Events in a specified class from being heldor suspended.

126

Hold Queues

Overview Events that are on hold are held in queues by their class name.

Name of thehold queue

If the class name for an Event is GROUP1 and the hold restrictor is placed onthe class ‘GR-’, a hold queue is formed for the class GROUP1. The Event,and any other Events with the same two characters (GR) at the beginning oftheir group name, is placed on the hold queue.

CLASScommand

You can use the CLASS command to display the Events in a hold queue, asfollows:

CLASS W LIST

The above example displays the hold queues for class W.

Releasing holdqueues

You can release the Events in a class hold queue using the CLASS commandas follows:

CLASS W RELEASE

In the above example, any Events in class W hold queue are released.

127

Masking

Overview When you are specifying a class string, you can use asterisks or a hyphen formasking when you want to use a generic class name. An asterisk signifiesthat any character in that position is considered a match. A hyphen ‘-’,signifies that any character in that or subsequent character positions isconsidered a match.

Example -Asterisks

The string **PR affects all classes with names consisting of four characters,which end with PR e.g. TAPR, A1PR, and so on.

Example –hyphens

The string ACC1- affects all classes whose names begin with the stringACC1. The class name can have any number of characters.

Example – holdall classesexcept thosewith PR

The following example holds all Event classes except for those whose namesbegin with the characters PR:

CLASS PR- EXEMPT /*THIS EXEMPTS ALL CLASSES */ /* BEGINNING WITH PR */CLASS – HOLD /*THIS HOLDS ALL CLASSES */

Displaying allrestrictors andhold queues

The following example displays all current class restrictors, and the names ofany hold queues in existence:

CLASSESP0001 CLASS LISTFOLLOWING CLASSES EXEMPT(E), HELD(H), SUSPENDED(s)PR-(E), -(H)NO EVENTS CURRENTLY HELD

128

Multiple Class Restrictors

Overview When multiple class restrictors exist, they are queued in ascending alphabeticsequence, with the more specific ones queued first.

When an Event is executed, the restrictor queue is searched, and the firstrestrictor that applies takes effect.

Example In the following example, imagine you use nine group names, all of whichstart with GR. You issue the following commands:

CLASS GROUP1- EXEMPTCLASS GR- HOLD

In the above example:• You specified to exempt class names beginning with GROUP1• You also specified to hold class names beginning with GRBecause GROUP1- is a more specific string than GR-, GROUP1 is queuedfirst.

The following illustration shows the nine group names, and the results of theabove commands:

HOLD

GR-GROUP10GRAMGROUP19GROUP1GROUP20GROUP45GREGORY

Group names

GROUP10GROUP19GROUP1

GRAMGROUP20GROUP45GREGORY

EXEMPT

GROUP1-

130

ESP Reports

Overview Two types of reports are available for your use with ESP. These are:

• History reports• Scheduled Activity Reports.

You use these reports to summarize historical statistics about a job andinformation about the workload objects in the schedule, respectively.


Topic See PageHistory Reporting 131Scheduled Activity Report 132

131

History Reporting

Overview You can use a History Report to see certain statistics about a job as it ran inthe past. History data is retained in the History file (HISTFILE) data set for aperiod of time. ESP uses this data to produce History Reports and to calculateaverage run times for a job.

The History Report contains detailed historical data about each job. You caninclude many kinds of data in a History report. For information about thefields available, and creating the report, see the ESP Workload ManagerUser’s Guide.

Obtaining aHistory Report

To obtain a History Report, enter the report commands in Page mode or inbatch.

For detailed information about the ESP reporting commands, see the ESPWorkload Manager Command Reference. If you know what command youwant to use, but simply want a syntax description, refer to the ESP WorkloadManager Command Quick Reference. For detailed information onconstructing a History report, see the ESP Workload Manager User’s Guide.

ExampleHistory Report

The following is an example of the commands to generate a History Report(in bold) and the resulting report:

REPORTFROM 7AM YESTERDAY TO NOWCRITERIA JOBNAME EQ SW-DISPLAY JOBNAME JOBNO APPLSYS CMPC EXECST LINES CPUTIMESORT APPLSYS JOBNAMEENDR

JOBNAME JOB APPLSYS COMP EXEC PRINT CPU TIME NO CODE START LINES

SWJOB1 1750 DB2JOBS 0 15.19 74 0:20SWJOB2 1753 DB2JOBS 0 15.20 74 0:00SWJOB3 1755 DB2JOBS S913 15.21 32 0:30SWJOB5 1622 OVERDU 0 11.05 48 0:22SWJOB5 1620 OVERDU 16 11.01 48 0:00

TOTAL (5) (276) (1:12)

132

Scheduled Activity Report

Overview In many cases, the LISTSCH command may not provide an operator withsufficient information to be of use. If you want a forecast of the schedule atthe job level, you need to produce a Scheduled Activity Report.

Generating thereport

To produce a snapshot of the activity expected on the system in any specifiedfuture time frame, use one of the following methods:

• Issue the LSAR (List Scheduled Activity Report) command in batch. TheLSAR command extracts data from the scheduled activity data set, andgenerates a standard format scheduled activity report.

• Choose option S from the ESP Main Menu. This runs the LSARcommand for you. This is the method normally used.

In order to create this report, you need to know the name of the scheduledactivity data set. Contact your ESP Administrator.

Data generatedby LSAR

The LSAR command generates a standard scheduled activity report thatincludes the following useful data:

• Jobname• Fully qualified Event identifier• Scheduled submit time• Job net ID• Number of samples used for averages• Averages of specific and non-specific tape mounts• Tape drives required• CPU time• Number of print lines• Elapsed execution time.


133

Scheduled Activity Report, Continued

The report The following shows the kind of output you can expect to generate using theLSAR command:

JOBNAME SUBMISSION SAM- ------------------- AVERAGE ----------------- TIME DATE PLES EXEC TIME CPU TIME PRINT TAPE MOUNTS TAPE USED (MINS) (MINS) LINES SPEC NON-SP DRIVESPAYJOB1 19.00 8FEB 9 22.2 1:01 300 0.0 0.0 0.0PAYJOB2 19.00 8FEB 0 0.0 0:00 00 0.0 0.0 0.0PAYJOB3 19.30 8FEB 10 0.5 0:00 1056 0.0 0.0 0.0DB2UPDT 20.30 8FEB 10 10.0 0:50 32 2.0 10.0 3.0IMSRPT 23.30 8FEB 10 0.1 0:01 80 0.0 0.0 0.0BILLNG1 01.30 9FEB 10 0.1 0:00 92 0.0 0.0 0.0BILLNG2 01.30 9FEB 10 0.5 0:00 91 0.0 0.0 0.0BILLNG3 02.00 9FEB 10 120.0 9:00 21040 3.0 15.0 6.0HISTRPT 05.30 9FEB 5 1.0 0:00 100 0.0 0.0 0.0BACKUP1 06.00 9FEB 1 90.0 5:00 78 1.0 1.0 2.0

TOTALS:

10 JOBS, 3 DID NOT HAVE STATISTICS AVAILABLE 4.07 TOTAL INITIATOR TIME (HOURS:MINS) 0:25 TOTAL CPU (HOURS:MINS) 22869 PRINT LINES 6 SPECIFIC TAPE MOUNTS 26 NON-SPECIFIC (SCRATCH) TAPE MOUNTS

134

ESP System Topology

Overview

Introduction Because ESP Workload Manager is so versatile, there are as many ways toconfigure ESP systems, as there are installations to do so. This chaptersummarizes the possible configurations for multiple ESP systems.


Topic See PageMultiple ESPs on a Single MVS Image 135Multiple Copies of ESP in a Shared Spool Environment 136Multiple Copies of ESP on Multiple JES Nodes 137

135

Multiple ESPs on a Single MVS Image

Overview You can run multiple copies of ESP on a single MVS image in two scenarios:

• Production and test copies• Master and Slave copies.

Production andtest ESPs

Your installation may require that you install new releases of ESP in a testenvironment prior to running ESP in production. If so, you need two copiesof ESP on the same MVS image – one for production and one for test. Eachof these copies of ESP is a Master.

Master andSlave ESPs

If you run copies of ESP on multiple MVS images in a Master/Slaveconfiguration, one copy of ESP is defined as the Master. It is very beneficialto also run a Slave copy of ESP on the same MVS image as the Master – ifyou need to take the system down for an extended period of time, it is verysimple to move the Master to another system.

For more information on Masters and Slaves, refer to the ESP WorkloadManager Installation Guide.

136

Multiple Copies of ESP in a Shared Spool Environment

Overview If your installation runs multiple copies of ESP in a shared spool environment,you are using a Master ESP, and multiple Slaves.

Master andmultiple Slaves

The copy of ESP that is defined as the Master is the ESP where you controlworkload. The Master is the only copy of ESP that has a CSF. If you requireaccess to CSF from a Slave, you use a product called ESP CommServer.


In a Master/Slave configuration, the Master ESP performs the tracking ofworkload. Each Slave passes its tracking data to the Master via the sharedQUEUE data set, as shown:

MASTER ESP

SLAVE ESP SLAVE ESP

QUEUEFILE

137

Multiple Copies of ESP on Multiple JES Nodes

Overview If your installation runs multiple copies of ESP across multiple JES nodes,you are using multiple Master copies of ESP. Each JES node requires an ESPMaster. If you want tracking data managed at a single point of control,tracking data is transmitted between Masters via NJE or LU 6.2.


MultipleMasters andSlaves

The following diagram illustrates the multiple JES node configuration:

MASTER ESP MASTER ESP

SLAVE ESP SLAVE ESP SLAVE ESP SLAVE ESP

LU 6.2

QUEUEFILE

QUEUEFILE

138

Frequently Used Commands

Overview This chapter discusses some of the more commonly used ESP Operatorcommands. These are the commands you likely use on a day-to-day basis.


Topic See PageAPPLJOB (AJ) Command 139List Application (LAP) Command 140List Job (LJ) Command 141List Tracked Job (LTJ) Command 142

139

APPLJOB (AJ) Command

Overview The APPLJOB command is used to control Applications, subApplicationsand jobs defined within Applications. The short form of this command is AJ.

AJ command Using the APPLJOB (AJ) command, you can:

• Resubmit a job using the original data set using the RESUB keyword.• Resubmit a job using an alternate JCL data set (COPYJCL library for

instance) using the DATASET keyword.• Bypass a job that is no longer required using the BYPASS keyword. As

soon as its dependencies are met, the job is marked complete. Successorjobs are posted as in a normal job completion.

• Unbypass a job that is bypassed at any time up to the normal point ofsubmission.

• Simulate normal completion of a job using the COMPLETE keyword.This immediately posts successor jobs. It can be used in a situation wherethe job failed, but a rerun is not necessary. The command can also beused prior to job execution.

• Remove predecessor relationships from a job using the DROPDEPkeyword. This marks all the predecessor links as satisfied.

• Hold or release a job using the HOLD or RELEASE keywordsrespectively.

Examples of AJcommand

The following example shows the use of the AJ command with the HOLD,COMPLETE, BYPASS and RESUB keywords:

AJ 1234 HOLDAJ REPORT.CHECK COMPLETE APPL(AP1)AJ XYZJOB BYPASS APPL(ACJOBS)AJ BADJOB RESUB DATASET(‘PROD.COPY.JCL’) APPL(NIGHTLY.-1)

140

List Application (LAP) Command

Overview The LAP command is used to list the information about an Application.

Issuing LAP To issue the LAP command, type the following in Page mode:

LAP TEST1 ALL

The above command requests a display of the Application TEST1.

Output of LAP The following example shows sample output from a LAP command1:

LAP TEST1 ALLAPPL TEST1 GEN 2CREATED AT 09:04 ON THURSDAY MARCH 19TH, 1998JOB1, HC=0 PREDECESSORS: (NONE) SUCCESSORS: JOB2

JOB2, HC=1 PREDECESSORS: JOB1 SUCCESSORS: JOB6

JOB6, HC=1 PREDECESSORS: JOB2 SUCCESSORS: JOB11, JOB9



JOB12, HC=2 PREDECESSORS: JOB9, JOB11 SUCCESSORS: (NONE)

1 HC indicates the number of immediate predecessors to a job.

141

List Job (LJ) Command

Overview The LJ command is used to display the information about a job.

Issuing LJ To issue the LJ command, type the following in Page mode:

LJ TESTJOB

The above command requests a display of the job TESTJOB.

Output of LJ The following example shows the output of the command

LJ PAYD002A:

142

List Tracked Job (LTJ) Command

Overview The LTJ command, on its own, displays the tracked job definition. If youwant more information, issue the LTJ command with the Index option. Itincludes more information, such as the JES job number, Reader on time, date,status, execution time and CPU time.

If you want more details about a job, generate a History Report.

Issuing LTJ To issue the LTJ command, type the following:

LTJ jobname

Output of LTJ The following example shows an LTJ command and the resulting output:

LTJ A


143

List Tracked Job (LTJ) Command, Continued

Issuing LTJIndex

To issue the LTJ command with the Index option, type the following:

LTJ jobname I

Output of LTJIndex

The following example shows an LTJ command with the Index option, andthe resulting output:

LTJ A I

144

Using ESP Operator Commands

Overview

Introduction ESP Workload Manager provides many operator commands for your use.This chapter contains a brief description of each command.


Topic See PageESP Operator Commands 145ESP Backup Commands 150Distributed Processing Commands 151

145

ESP Operator Commands

Overview ESP Workload Manager provides many operator commands for your use.These commands are documented fully in the ESP Workload ManagerCommand Reference. However, they are listed here with a brief descriptionof their purpose and when you might use them. You can also refer to the ESPWorkload Manager Command Quick Reference for the syntax of thecommands.

Authorityrequired

OPER authority is required to issue any of the operator commands listed inthis chapter.

Entering acommand

To enter an ESP modify command, specify:

F ESP,command text

where ESP is the name of the started task procedure.

Issuingcommand fromTSO

To issue a command from an authorized TSO userid, prefix all ESP operatorcommands with OPER. For example, from Page mode:

OPER LISTQ


146

ESP Operator Commands, Continued

The commands The commands listed here are those you probably use in your day to daywork:

Command DescriptionABENDLIM Displays or sets Abend queue sizeALERTDEF Displays or controls Alert definitionsAPPLJOB (AJ) Controls jobs, subApplications or ApplicationsBACKOUT Backs out this release of ESP to a specified earlier

release (4.4 and up)BUILDDTE Causes ESP to rebuild its list of data sets scanned for

data set triggeringCALLRTN Calls an external utility routineCLASS Displays and controls class queuesCELLTRC Traces storage cell usageCKPTRACE Traces all storage acquisitions and releases in checkpoint

spaceCLRSYSMS Clears all system messages interceptionCMDPRFX Allows you to substitute a single character for the string

‘F ESP’CONSOLE Displays or sets the primary consoleCPU Displays the CPU definitionCRITPATH Enables or disables Critical path analysisDAB Displays all or selected jobs from the abend queueDATEFORM Sets the date format in schedule statementsDELAYINT Sets the interval for re-triggering an Event when required

data sets are not availableDFPNODE Displays or sets the default P-NodeDN Displays the names of jobs on the P-Node queuesDQ Displays the names of all or selected P-Node queuesDSTRDLY Used to delay data set triggered Events or data set trigger

objects when data set activity occursDSTREXCL Flags an entry in the Data Set Trigger Exclude list as

invalidDSTRST Controls data set triggering activityEICLASS Controls Event initiator class definition and

manipulationESPCTR Displays ESP internal activities relating to Events,

Applications and jobs.


147


The commands (continued)

Command DescriptionEVENT Starts Event definition modeEVENTSET Defines or alters the definition of an Event data setHISTFILE Specifies the identifiers of the History files to scan to

generate a reportINET Displays and controls TCP/IP attributesJESCOMCH Specifies the JES command prefixJOBINFO (JI) Displays all or selected information from a job

documentation entry for a jobJTPEXCL Provides a means to exclude a named program from

affecting job tracking completion statusLAX Displays Application external linkagesLCMDPRFX Displays the default command prefixLDFLTU Displays the default user idLDSN Displays system data sets allocated to ESPLDTREL Displays the entries from the Data set Trigger Exclude

listLISTAPTF Displays information on the current status of the

Application data setLISTCKPT Displays statistics about the Checkpoint data setLISTEVS Displays the status of any or all Event databasesLISTHIST Displays the status of the History data setLISTJTML Displays internal tracking model dataLISTQ Displays information about the Queue data setLISTSADL Displays the current SADLINKsLISTSCH Displays the current scheduleLISTTRAK Displays the status of the Trackfile data setLISTXMEZ Displays cross-memory tracking elementsLJ Displays job statusLOADJTDT Loads the job tracking definition tableLOADSCHF Copies schedule information from a sequential work file

to a VSAM file that can be viewed from CSFLOADUPDT Loads the User Profile Definition TableLSYS Displays system information


148



Command DescriptionLSYSMSGS Displays system message informationMSG Modifies the routing or descriptor codes of a message or

range of messages. The error level of a message can alsobe modified.

MSGLIMIT Allows you to limit the number of console messagesgenerated by an Event

MSGPRFX Alters the message ID prefix for all messages generatedby the subsystem

MSGTYPE Modifies the routing or descriptor codes of an entireclass of messages. A class of messages is a group withthe same error level i.e. information, warning, error andsevere error.

NODE Together with CPU, defines the resource topology ofyour network

NTRCLASS Specifies a job execution class to exclude from trackingPOST Posts a job as having completed processing at a P-NodePREALLOC Controls the use of pre-allocated data setsPURGSCHF Purges the SCHDFILEQUIESCE Requests that ESP enter the quiesced state. Event

execution is deferred.QUPDATE Forces ESP to do a JES status and update P-Node queue

informationRACROUTE Specifies whether ESP should issue a SAF RACINIT

before Event executionRESTART Requests that ESP leave the quiesced state. Event

execution can restart.RESDEF Used to define, display, delete or update resourcesRESDFLT Identifies default resourcesRESREFR Used in conjunction with real resources to refresh the

device list if resources are added or deleted dynamicallySAFOPTS Controls processing options for the SAF interfaceSHUTDOWN Requests termination of ESP


149



Command DescriptionSPINLOG Used to spin ESP’s audit log to a sysout classSPUSER Defines the name of a user who is to perform the initial

definitions in the user definition data setSTATUS Used to display the current ESP processing statusSYSMSGS Intercepts messages that are routed to the system

message data setTRACE Activates the trace facility and allows trace options to be

setTRACEDEF Defines the data set(s) to be used for recording trace dataTRACKING Used to enable or disable the ESP tracking facilityTRACKOPT Sets tracking optionsTRDFLT Specifies an installation default to be used when an

Event is triggered manuallyTRIGGER Requests the immediate execution of an EventUNALLOC Used to unallocate a data set from ESPUSERMOD Used to define the ESP user modificationXMITMDL Tells ESP which tracking models are to be transmitted,

and to which node

150

ESP Backup Commands

Overview The commands listed here are those you use to back up ESP data sets:

Command Backs up the . . .BKUPUDEF User Definition data setBKUPEVS Event data setBKUPINDEX Index data setBKUPJNDX Job Index data setBKUPHIST History data set

151

Distributed Processing Commands

Overview The commands listed here are those you use when running off-MVSworkload:

Command DescriptionAGENT Displays the contents of the Agent definition file

(AGENTDEF) and controls the flow of messages to theAgent

AGENTRCV Defines the Manager’s receiver function forcommunication with non-MVS Agents

LOADAGDF Loads the Agent Definition fileWOBDEF Identifies the program modules ESP uses to support non-

MVS job types

152

Glossary of Terms

Glossary

Term ExplanationAlert A mechanism you define to ESP to trigger

ESP activity when specific actions take placein your Application. For example, you can useESP to trigger an Event when a job fails.

Application See ESP Application.Application Wait A status in which the execution of an

Application has to wait until a previousgeneration of the Application completes.

Audit log An audit trail of ESP activity. It storesinformation on administration activities,operator commands, and Application andEvent processing.

Authorization string One of four job related fields that is used toidentify the ownership of a job.

Calendar A collection of definitions of holidays, specialdays and special periods that are unique toyour installation.

CCFAIL Abbreviation for “condition code fail”.CCFAIL statements define conditions, which,if met, should cause the job to fail.

CLANG Control language. This is a high levelprogramming language developed for ESP.


153

Glossary, Continued

Term ExplanationCondition code A code indicating the results of processing a

job step.COPYJCL Location of a copy of the submitted JCL.Consolidated Status Facility An ESP facility for displaying and

manipulating the workload.Descriptor code A one or more digit code used to describe the

characteristics of a message to an MVSconsole.

ESP Application A group of related jobs and tasks.ESP Procedure A collection of stored instructions to be

executed by ESP when invoked by an Event.External job A job defined in an ESP Procedure that ESP

submits from another Procedure.Event A basic unit of work to ESP. An Event starts

an active function such as sending a messageor invoking an ESP Procedure.

Event data set A VSAM data set where ESP stores Eventdefinitions.

Event group Group of ESP Events with the same Eventprefix (first name).

EVENTSET Event data set.Group A high-level index, to which specific users

are allowed access. Normally a group is acollection of users with common accessrequirements.

HISTFILE History file.


154

Glossary, Continued

Term ExplanationHistory file A VSAM data set used to store historical

information.Job index data set A VSAM data set used to store an index to

the most recent executions of a job.Job monitor An ESP facility for monitoring a job’s

progress at any stage of processing and fortaking action at significant points.

Job tracking An ESP facility to track job data in real timeas jobs are processed.

Job tracking definition table A table used to specify the characteristics ofjobs, STCs and TSUs you want to track.

Link A task in an Application that does not requiremanual completion.

Manual job A job that ESP does not submit as part ofeither an ESP Application or a DJC/JES3 jobnetwork.

Model A definition of your environment (e.g. CPUs,initiators, resources).

Page mode A method to communicate with ESP usingISPF, producing scrollable output from ESP.

P-Node Processing node. A processing stage throughwhich a job must pass during its time on thesystem.

Post To mark complete. For example, you can posta job complete.

Predecessor job Any job that must complete before anotherjob can be released.

Qualifier An addition to the job’s name, used touniquely identify similar jobs.

Resource An item of hardware, a software resource oran abstract condition.


155

Glossary, Continued

Term ExplanationREXX Restructured eXtended eXecutor. This is a

high level, procedural language developed byIBM. You can invoke the REXX languageinterpreter from ESP to extend ESP’scapabilities.

Route code A one or more digit code used to route amessage to an MVS console.

SAD file Scheduled activity data set file; a sequentialdata set ESP uses to store scheduled activityinformation on jobs.

SAF System Authorization Facility; a generic setof operating system interfaces that allows asecurity product to implement access controlagainst the components of the operatingsystem. Also used to refer to the use of theinterface.

Schedule A list of Events to execute, sorted in timesequence.

Signal A manual or automated task used forscheduling.

Special day A day with special significance for schedulingat your installation.

Special period A period of processing with specialsignificance for scheduling at yourinstallation. An example is a fiscal month.

SubApplication A group of jobs within an Application.Subsystem An MVS facility that ESP uses to manage and

control requests among its components.Successor job Any job that depends on the completion of

another job before it can be released.


156

Glossary, Continued

Term ExplanationSymbolic variable An integer or character string whose value

ESP substitutes at processing time.SYMLIB Symbolic variable library: data set(s) or data

set members used to store symbolic variables.System message interception A facility used to intercept system messages

as they are written to the system message dataset.

System security product A product installed to implement systemsecurity. Also known as the host securitysystem or product.

Task An element of an Application that requirescompletion. For example, a task mayrepresent the checking of a report.

Tracking model A centralized definition of the attributes andprocessing phases of a group of jobs.

TRAKFILE Tracking file; a non-VSAM data set used tostore job-tracking data.

userid A short (8 bytes or less) field used to identifya system user. It can represent an actualperson or an active program, job or routine.

158

A

AA........................................................................... 27Agent commands................................................... 150AJ command ......................................................... 138altering default presentation field length................. 35altering default presentation titles ........................... 35APPLHOLD............................................................ 25Application statements ............................................ 56Applications

completing.......................................................... 27description.......................................................... 11displaying ..................................................... 27, 65generations ......................................................... 55holding................................................................ 27overview............................................................. 52releasing from hold............................................. 27removing from wait ............................................ 27statements ........................................................... 56

APPLJOB command ....................................... 69, 138AS ........................................................................... 28Asterisks

for masking....................................................... 126

B

backup commands................................................. 149BE ........................................................................... 28BP ........................................................................... 28browsing an Event................................................... 28browsing COPYJCL................................................ 29browsing last executed JCL..................................... 29BY........................................................................... 29bypassing a job................................................ 29, 104BYS......................................................................... 28

C

CA........................................................................... 27calendars ................................................................. 96Checkpoint data set,cold start ................................. 18CLASS command.................................................. 119class name,assigning ............................................. 123class restrictors,examples ...................................... 127class,Event prefix as.............................................. 119COLD START ........................................................ 20color options,specifying in a view........................... 35commands

AJ138APPLJOB................................................... 69, 138backup .............................................................. 149distributed processing....................................... 150for Agents......................................................... 150LAP .................................................................. 139LJ 140

LSAR................................................................ 131LTJ ................................................................... 141non-MVS.......................................................... 150operator ............................................................ 144TRIGGER .......................................................... 86

COMPLETE ........................................................... 25completing a job.............................................. 29, 102completing an entire Application ............................ 27Consolidated Status Facility,description ................. 12contention, data sets .............................................. 117controlling multiple Events ................................... 124CQFORMAT .......................................................... 18CS............................................................................ 28CSF

changing colors .................................................. 42defining a view ................................................... 34deleting completed jobs...................................... 24description.......................................................... 12Extensions .......................................................... 31filter criteria........................................................ 36

CSF commandsAA...................................................................... 27CA ...................................................................... 27HA...................................................................... 27HR ...................................................................... 29IJ 29IJA...................................................................... 29IJB ...................................................................... 29L 29LA ...................................................................... 27LI 29LJ 29LR....................................................................... 29R 29UWA .................................................................. 27

D

data set contention................................................. 117data set triggering.................................................... 76DD........................................................................... 29deferred

Events,overdue queue....................................... 118queue,flushing .................................................. 119

defining an Event .................................................... 74delayed Events ..................................................... 115DELAYSUB statement ........................................... 56deleting completed jobs .......................................... 24dependencies,dropping.......................................... 110displaying

Applications ................................................. 27, 65dependencies ...................................................... 29index entries ....................................................... 29Info records ........................................................ 29

159

job resource waits............................................... 29schedules ............................................................ 78step-level statistics.............................................. 29

distributed,commands ........................................... 150dropping

all predecessors .................................................. 29all resource dependencies................................... 29dependencies .................................................... 110individual dependencies ..................................... 29resources........................................................... 110

DUEOUT statement ................................................ 56

E

EE ........................................................................... 28EP28Event class,manipulating....................................... 123Event data sets

deferred queue.................................................. 118respecifying after cold start ................................ 18suspended ......................................................... 118

Eventsassigning class .................................................. 123browsing............................................................. 28bypassing execution............................................ 82class.................................................................. 119controlling multiple .......................................... 124delayed ............................................................. 115description.......................................................... 11editing................................................................. 28hold................................................................... 119overdue............................................................. 116OVERDUE......................................................... 81overdue count ................................................... 116postponing execution.......................................... 80RESUME............................................................ 82sending a message .............................................. 72simulating ........................................................... 87stopping execution temporarily ........................ 120suspend............................................................. 119SUSPEND.......................................................... 82suspending individual....................................... 119to invoke an ESP Procedure ............................... 72to issue an MVS command................................. 72to submit JCL ..................................................... 72triggering manually............................................. 83

EVENTSET ............................................................ 77EVENTSET command,OPEN option ................... 118Eventset suspension,reversing............................... 118EXEC...................................................................... 25EXTERNAL ........................................................... 25External job............................................................. 58

F

FAIL........................................................................ 25specifying freeform ............................................ 43

flush deferred queue.............................................. 119freeform filtering..................................................... 43

examples............................................................. 48keywords ............................................................ 45

G

generation number................................................... 55

H

HA........................................................................... 27History Reports ..................................................... 130Hold restrictor ....................................................... 125hold with a reason ................................................. 101holding

Application................................................. 27, 114job .................................................................... 100jobs with a reason............................................... 29

holidays, defining.................................................... 96HS ........................................................................... 28

I

I/O error,Event data set ......................................... 118INPUT..................................................................... 25inserting a job.................................................. 29, 108inserting a job after a selected job........................... 29inserting a job before a selected job........................ 29

J

JANCWAIT ............................................................ 25JES nodes,multiple Masters .................................. 136jobs

bypassing.......................................................... 104completing........................................................ 102External .............................................................. 58holding with a reason.......................................... 29inserting...................................................... 29, 108manual ................................................................ 59ON-REQUEST................................................... 57requesting ......................................................... 107resubmitting...................................................... 106

K

keywords,freeform filtering..................................... 45

L

LA ........................................................................... 27LAP command ...................................................... 139links......................................................................... 60listing Application.................................................. 27LJ command.......................................................... 140LS28LSAR command.................................................... 131LTJ command ....................................................... 141

160

M

MANHOLD ............................................................ 25MANSUB ............................................................... 25manual job............................................................... 59Master and Slave................................................... 134multiple class restrictors........................................ 127

O

ON-REQUEST job ................................................. 57operator commands ............................................... 144overdue

count................................................................. 118Events............................................................... 116keyword............................................................ 118queue ................................................................ 118

OVERDUE ............................................................. 81

P

P-NodesAPPLHOLD....................................................... 25COMPLETE....................................................... 25EXTERNAL....................................................... 25FAIL................................................................... 25INPUT................................................................ 25JANCWAIT ....................................................... 25MANHOLD ....................................................... 25PREDWAIT ....................................................... 25READY.............................................................. 25RESWAIT .......................................................... 25SANCWAIT....................................................... 25SUBDELAY....................................................... 25SUBERROR....................................................... 25TASK ................................................................. 25WAITING .......................................................... 25

postponing Event execution .................................... 80PREDWAIT............................................................ 25presentation fields ................................................... 40presentation length .................................................. 40presentation order.................................................... 39presentation titles .................................................... 40Procedures

browsing............................................................. 28description.......................................................... 11editing................................................................. 28

PURGSCHF command ........................................... 24

Q

QFORM option ....................................................... 19quiesced state,ESP ................................................ 120quiescing ESP ......................................................... 17

R

READY................................................................... 25readying a job.......................................................... 30

releasing a job ......................................................... 29releasing an Application from hold ......................... 27RELOAD option ..................................................... 18removing Application from wait status ................... 27replying to an AS/400 message ............................... 30reports

History.............................................................. 130History, description ............................................ 12Scheduled Activity, description.......................... 12

requesting a job ............................................... 30, 107resetting a time dependency .................................... 30resetting time dependency..................................... 113resetting User Status field ....................................... 30RESOURCE statement............................................ 63resources ................................................................. 63resources,description............................................... 12restart options

QFORM.............................................................. 19RELOAD............................................................ 18

restarting a job......................................................... 29restarting after SMF problems................................. 18restrictors

examples........................................................... 127searching queue ................................................ 127

resubmitting a job............................................ 29, 106RESUME ................................................................ 82RESWAIT............................................................... 25RQS......................................................................... 28running off-MVS workload................................... 150

S

SANCWAIT ........................................................... 25SCHDFILE ............................................................. 24schedule criteria ...................................................... 94Scheduled Activity Report .................................... 131schedules

Checkpoint data set ............................................ 18displaying ........................................................... 77rebuilding ........................................................... 18reinitializing checkpoint ..................................... 18scanning.............................................................. 18system outages.................................................. 116

scheduling Event to execute once ........................... 77selecting Filter information ..................................... 35shared spool, Master and multiple Slaves ............. 135simulating

an Event.............................................................. 87description of...................................................... 90next occurrence .................................................. 88

SMF problems, restarting after................................ 18sort order ................................................................. 41sort order of presentation fields............................... 35special days, defining .............................................. 96special periods, defining.......................................... 96specifying presentation fields.................................. 35

161

START command ................................................... 16statements

DELAYSUB....................................................... 56DUEOUT ........................................................... 56RESOURCE....................................................... 63TAG ................................................................... 57

status fieldsstatus................................................................... 26system................................................................. 26user ..................................................................... 26

STOP command ...................................................... 21subApplications....................................................... 66

defining .............................................................. 66bypassing............................................................ 28completing.......................................................... 28displaying ........................................................... 28holding................................................................ 28releasing from hold............................................. 28removing from wait ............................................ 28requesting ........................................................... 28un-bypassing....................................................... 28un-requesting...................................................... 28

SUBDELAY ........................................................... 25SUBERROR ........................................................... 25SUSPEND............................................................... 82suspended Eventset ............................................... 118suspending Events................................................. 119

T

TAG statement ........................................................ 57TASK...................................................................... 25tasks ........................................................................ 59time dependency, resetting.................................... 113trigger an Event automatically on data set activity.. 76TRIGGER command............................................... 86

U

UBS......................................................................... 28un-bypassing a bypassed job ................................... 30un-requesting a requested job.................................. 30un-waiting a job from job-ancestor wait.................. 30updating an Info record ........................................... 30URS......................................................................... 28User status field....................................................... 26UWA....................................................................... 27UWS........................................................................ 28

V

view,defining in CSF............................................... 34viewing Encore panels ............................................ 30

W

WAITING............................................................... 25Workstation............................................................. 13

162

Reader’s Comment FormESP v.5.2 OG-02

We want tohear from you!

Please use this form to communicate your comments about this publication,its organization or subject matter with the understanding that Cybermationmay use or distribute whatever information you supply in any way itbelieves appropriate without incurring any obligation to you.

If your comment does not need a reply (for example, pointing out a typingerror), check this box and do not include your name and address below. Ifyour comment is applicable, we will include it in the next revision of themanual.

If you would like a reply, check this box. Be sure to print your name andaddress below.

Page Number(s) Comment(s)

Name _______________________________________________Company _____________________________________________Address ______________________________________________Fax: _________________________

163

Mail this form to:Cybermation Inc.80 Tiverton CourtMarkham, OntarioL3R 0G4Attn: Documentation Dept.

or Fax it to:Documentation Dept.(905) 479-4614

164

Reader’s Comment FormESP v.5.2 OG-02

We want tohear from you!

Please use this form to communicate your comments about this publication,its organization or subject matter with the understanding that Cybermationmay use or distribute whatever information you supply in any way itbelieves appropriate without incurring any obligation to you.

If your comment does not need a reply (for example, pointing out a typingerror), check this box and do not include your name and address below. Ifyour comment is applicable, we will include it in the next revision of themanual.

If you would like a reply, check this box. Be sure to print your name andaddress below.

Page Number(s) Comment(s)

Name _______________________________________________Company _____________________________________________Address ______________________________________________Fax: _________________________

165

Mail this form to:Cybermation Inc.80 Tiverton CourtMarkham, OntarioL3R 0G4Attn: Documentation Dept.

or Fax it to:Documentation Dept.(905) 479-4614

operators 52

Documents