Job Scheduling

CDT uses a CA workload automation ESP edition to perform scheduled job submission and online tracking. CDT customers control their own jobs in order to efficiently manage their scheduled workload.

To efficiently utilize ESP’s features, customers must code the information listed below into ESP. Furthermore, customers may incorporate many optional parameters for more flexibility and control of batch scheduling needs.

1. Schedule criteria and time of event trigger.
2. Name of the dataset where ESP procedures are stored.
3. Job name(s).
4. Predecessor/Successor relationships.
5. Whom to notify of abends and failures.
6. Name of the dataset where production JCL is stored.
7. Acceptable condition codes for jobs.
8. ESP application name if part of an ESP application.

Make requests for job scheduling through your departmental scheduler. If your department does not have a designated scheduler, contact the CDT Scheduling Unit at (916) 228-6361. Only the CDT Processing Support Unit or your department scheduler can authorize customers to access ESP.

Customers control and maintain their own ESP events. You control your events by issuing one of the ESP Event commands listed below:

A – Alter event characteristics
B – Browse event
D – Delete event
E – Edit your event
H – Hold event
P – Release event from hold status
R – Resume event from suspend status
U – Suspend event
M – Simulate event
T – Trigger event

Through ESP ‘s Application Monitor screen, customers control their ESP application. By issuing one of the commands listed below:

AA – Release an Application from a hold state
AH – Select pre-defined jobs from an Application for ad-hoc scheduling
BE – Browse Event definition
CA – Complete the Application and all jobs within. Does not remove any Holds or Waits on the Application
CAA – Complete all active generations of the Application
CSA – Display active jobs in CSF for the Application
CSF – Display all jobs in CSF for the Application
HA – Hold the Application
LA – List Application summary
LAD – List Application details
NX – Display next 10 scheduled occurrences of the Event
PA – Purge completed Application
RM – Rerun jobs from the Application
SIM – Simulate the Application
TR – Trigger another occurrence of the Application
TA – Complete the Application and all jobs within, in addition to removing any Holds or Waits
UWA – Remove from APPLWAIT status

Through ESP ‘s Consolidated Status Facility screen, customers control their ESP jobs. By issuing one of the commands listed below:

JCL – displays the JESJCL output spool file
JES – displays the JESMSGLG, JESJCL and JESSYSMSG output spool
LJE – lists job details
LI – lists historic job index entries
LJ – displays step-level statistics
LJO – displays all the data sets in the output
LOG – displays the JESMSGLG
R – resubmits/restarts job
RD – Ready a job
RM- Rerun multiple jobs in an Application
RT – Reset time dependencies
RQ – request a job
C – force complete job and release successors
BC – browses COPYJCL
BE – browses event
BJ – browses last executed JCL
BP – browses procedure

• Customers create and maintain datasets that store their JCL.
• The CDT Processing Support Unit instituted the following naming convention. “XXXXXXX.ESP.CNTL(membername)”, where XXXXXXX is your TSO logon id.
• You can leave off the USER and PASSWORD keyword parameters. ESP checks RACF under the TSO id that defined or changed the ESP event.
• ESP requires the jobcard name to match the dataset’s member name.

Customers define and control their own events. Define schedule criteria in simple English sentences such as “Last Workday of the Month or 3rd Monday of Month”. Hard-coding specific dates is NOT RECOMMENDED because specific dates require updating after the event triggers.

Based on the schedule criteria, ESP can:

• “INVOKE” an ESP procedure (batch job(s)
• “Send” messages to one or more TSO users
• “Submit” JCL

Consult the ESP user guide for details about additional functions provided by an ESP event.

If used to submit batch jobs, we recommend using the “INVOKE” statement to allow more flexibility in controlling your jobs.

ESP procedures control your processing requirements. By specifying your requirements, ESP submits your batch jobs either all at once or in a specific order (predecessor/successor relationships). Additionally, you may further enhance ESP’s capabilities by combining other ESP parameters in your procedure.

• An ESP procedure definition is not compiled and therefore can be stored in a member of a partition dataset. Customers create and maintain these partition datasets.
• The CDT Scheduling unit instituted the following naming convention. “XXXXXXX.ESP.PROC(membername)”, where XXXXXXX is your TSO logon id.
• An ESP procedure allows an unlimited number of lines or statements; it can be as simple or as complex as your needs demand.
• You can set and/or test ESP’s symbolic variables in an ESP Procedure.
• Use IF-THEN-ELSE statements to increase versatility in submitting batch jobs.