Anda di halaman 1dari 7

APPL Statement The APPL statement is used to identify the name of an Application, and to indicate certain processing options

for the Application. APPL applid [WAIT] [HOLD] [SAF_PROF_APPL|SAF_PROF_GROUP]

WAIT Indicates that concurrent processing of different generations of an Application is not permitted. HOLD Indicates that the Application is to be generated on hold. SAF_PROF_GROUP Indicates that jobs within the Application are to be protected by the GROUP.groupname and GROUPX.groupname resources. This is only applicable if SAF is used for ESP security. This is the default. SAF_PROF_APPL Indicates that jobs within the Application are to be protected by the APPL.applname.jobname and APPLX.applname.jobname resources. This is only applicable if SAF is being used for ESP security. SUBAPPL Statement SUBAPPL subapplid [WAIT|NOWAIT] The SUBAPPL statement is used to identify the logical name of a subApplication within an Application. WAIT : Indicates concurrent processing of different generations of the same subApplication is not permitted. ESP ensures that a subApplication waits for the previous generation of the same subApplication to complete. This can be specified at the Application or the subApplication level. NOWAIT Indicates concurrent processing of different generations of the same subApplication is permitted. This is the default. JOB Statement
JOB jobname [LINK[PROCESS|NOPROCESS]|NONLINK] [TASK |NOTASK] [INHERIT|NOINHERIT] [[EXTERNAL|NOEXTERNAL] [APPLID(applname: Indicates the name of the Application that submits the job.)] [SCHEDULED(criteria: Indicates a scheduled time or range for the scheduled time of the Event that submits the job or the trigger time issued for non-scheduled Events.]] [CRITICAL|NOTCRITICAL]

The JOB statement is used to identify the name of a job in an Application. The JOB statement must be used before identifying other job requirements such as predecessor and successor relationships and run frequencies. LINK: Indicates this is a task that does not require manual completion. ESP does not try to submit JCL for a LINK. y y PROCESS indicates you want to use a LINK to issue commands. NOPROCESS Indicates you do not want to use a LINK to issue commands. This is the default.

NONLINK: Indicates this is a task that does not require manual completion. ESP does not try to submit JCL for a LINK. TASK Indicates this is a task that requires manual completion. ESP does not try to submit JCL for a TASK. NOTASK Indicates this is not a task that requires manual completion. This is the default. NOINHERIT: Indicates job relationships should not be inherited. EXTERNAL Indicates a job is submitted by another ESP Application. The EXTERNAL parameter is used to build inter-Application dependencies. NOEXTERNAL Indicates a job is not submitted by another ESP Application. This is the default. CRITICAL Indicates this job represents a critical point in the Application. The longest path to this job, in terms of execution time (based on history) is identified as the critical path. NOTCRITICAL Indicates this job does not represent a critical point in the Application. This is the default. RUN Statement RUN criteria The RUN statement is used to identify a jobs schedule frequency. ESP allows multiple RUN statements for the same job. Eg: RUN WORKDAYS RUN DAILY RUN FRIDAY RUN 5TH DAY OF MONTH PLUS 0 WORKDAYS ENDJOB Statement ENDJOB The ENDJOB statement is used to indicate the end of a job definition.

AIX_JOB : Unix job beginning.

EARLYSUB Statement EARLYSUB criteria The EARLYSUB statement is used to specify a job for delayed (or early) submission relative to the scheduled time of the Event. If the Event is not scheduled, the delayed submission time is relative to the time the Application is generated. Eg: EARLYSUB 9PM

Delayed submission time of 9 pm relative to the job time. EARLYSUB 9PM IF TODAY(WEEKEND) THEN EARLYSUB 6PM A delayed submission time of: 9 pm on weekdays 6 pm on weekends. AGENT Command AGENT [name] The AGENT command is used to display the contents of the Agent Definition file (AGENTDEF), and controls the flow of messages to the Agent. % way to pass value from JOB AJ PAYJOB10 RESUB USER1(,RESTART=STEP20) APPL(CYBER1) The following is a sample jobcard and the corresponding jobcard used for resubmission: PAYJOB10 JOB...MSGCLASS=X%USER1 resolves to: PAYJOB10 JOB...MSGCLASS=X,RESTART=STEP20 SCRIPTNAME %sd/zrk@4302.drv %sd will contain path where UNIX script are stored.

RELEASE Statement The RELEASE statement is used to identify a successor to a job. The successor is released upon completion of this job. RELEASE {jobname}. TAG Statement The TAG statement is used to tag jobs in an Application with a character string up to 16 characters in length. The TAG statement can be job specific or can apply to all jobs in an Application. TAG string e.g. TAG CRITICAL JOB TAG %ESPSDAY(1:3)

NORUN Statement The NORUN statement is used to handle exceptions to a jobs regular schedule criteria. The NORUN statement tells ESP when not to select a job for submission.

NORUN criteria e.g. NORUN FIRST WORKDAY OF MONTH NORUN FIRST WORKDAY OF MONTH NORUN LAST WORKDAY OF MONTH NORUN WEDNESDAY

ESP Statement The ESP statement is used to issue any ESP command from within an ESP Procedure. ESP [Any valid ESP command]

e.g
ESP TRIGGER CYBER.ACCTJOB ADD Issues an ESP command to trigger an Event called CYBER.ACCTJOBS. ABANDON DEPENDENCIES Statement The ABANDON DEPENDENCIES statement is used to submit a job without its predecessor dependencies once it meets a specified time. This does not override a manual hold, a time dependency, or a resource dependency for a job. ABANDON DEPENDENCIES criteria e.g. JOB PAYJOB1 RUN DAILY RELEASE PAYJOB2 ENDJOB JOB PAYJOB2 RUN DAILY ABANDON DEPENDENCIES 9PM ENDJOB

In the above example, PAYJOB2 is submitted at 9 pm or when PAYJOB1completes, whichever comes first.
JCLLIB Statement The JCLLIB statement is used to identify the JCL library you want to use for all jobs following this statement. When ESP encounters a JOB statement, it uses the JCL member in the JCLLIB with the same name as the job. You can use the MEMBER statement to override this action. JCLLIB 'dsname'

TEMPLIB Statement

The TEMPLIB statement is used to identify the temporary or override JCL library you want to use as the default for all jobs following this statement. ESP uses JCL from this library for job submission if it exists. Otherwise it uses JCL from the most recent JCLLIB statement. TEMPLIB dsname COPYJCL Statement The COPYJCL statement is used to generate a copy of the JCL for every job ESP submits. When you use the COPYJCL statement you must specify the library that is to receive the copy, followed by either the JOBNAME or JOBID keyword. This working copy of the JCL can be used for job re-submission. ESP keeps track of where the job was submitted from and the JCL that was used. COPYJCL {datasetname|NONE} DOCLIB Statement The DOCLIB statement is used to identify the name of the job documentation library to be used throughout an ESP Procedure. Specifying a DOCLIB statement allows you to use control and user description information, which are components of ESPs job documentation feature. DOCLIB dsname OPTIONS Statement The OPTIONS statement is used to override the default processing options for jobs belonging to Applications. OPTIONS [INHERIT|NOINHERIT] [GENNET|NOGENNET] [MANUALSUBMIT|NOMANUALSUBMIT| [TRACKMANUAL|NOTRACKMANUAL] [AUTOVARS|NOAUTOVARS] [RESTARTSTEP|NORESTARTSTEP] INHERIT Indicates job relationships are inherited. This is the default. NOINHERIT Indicates job relationships are not inherited. GENNET Indicates DJC/JES3 NET control cards are generated for jobs in a DJCNET. This is not applicable to ESP Applications. This is the default. NOGENNET Indicates DJC/JES3 NET control cards are not generated for jobs in a network. This can be used if the jobs you are submitting already have NET control cards. MANUALSUBMIT Indicates jobs are manually submitted. NOMANUALSUBMIT Indicates jobs will not be manually submitted. This is the default. TRACKMANUAL Indicates jobs are tracked manually. NOTRACKMANUAL Indicates jobs are not tracked manually. AUTOVARS Indicates ESP allows the use of the automatic variable insertion feature. This is the default. NOAUTOVARS Indicates ESP does not allow the use of the automatic variable insertion feature.

RESTARTSTEP Indicates a restart step is added to each job in an Application as identified by the ERMSTEP initialization parameter. NORESTARTSTEP Indicates a restart step is not added to each job in an application. This is the default. EXITCODE EXITCODE 12-9999 FAILURE

EXITCODE0-5 SUCCESS
CCCHK Statement The CCCHK facility is designed to detect errors in condition codes. It offers the capability to immediately stop a failing job, without running any subsequent steps regardless of the COND parameters. Unless either the FAIL or STOP condition is seen on a matching CCCHK statement, ESP Workload Manager will not interrupt the flow of the job. CCCHK [RC(num1:num2)] [OK|FAIL] [CONTINUE|STOP] RC(num1:num2) Indicates a condition code between num1 and num2 inclusive. The value of num2 must not be smaller than num1. These values represent condition codes only, not user abend codes. OK Indicates that the job has not failed. OK is the default. FAIL Indicates that the job should be considered failed. When the job has failed, it may or may not continue, depending upon the value of CONTINUE/STOP. CONTINUE Indicates that the job should continue processing with the next step, whether or not the job was deemed to have failed. This is the default. STOP Indicates that the job should be stopped immediately. No other steps should be executed. Only one of CONTINUE or STOP may be specified. NOTIFY Statement The NOTIFY statement is used to notify users or consoles, or trigger an Event when one or more of the following conditions are met: SUBMIT, JOBSTART, RESUB, OVERDUE, ABEND, FAILURE and JOBEND. The NOTIFY statement is available only for jobs belonging to Applications. NOTIFY [SUBMIT] [JOBSTART] [RESUB] [OVERDUE] [ABEND] [FAILURE] [JOBEND] [ALERT(xxxx)] ALERT(xxxx) Indicates an Event associated with a logical alert identifier should be triggered. This logical identifier must have been previously specified using an ALERTDEF command. Alternatively, an asterisk (*) can be used to trigger the same Event which invoked this ESP Procedure.

ESPNOMSG Statement The ESPNOMSG statement is used to issue any ESP command from within an ESP Procedure and suppress responses from the command. Warnings and errors responses are not suppressed. ESPNOMSG command