JCL Keyword parameters
The parameters apart from positional parameters used in JOB card called as Keyword parameters.
All Keyword parameters are optional.
Keyword parameters can be coded in any order.
Keyword parameters follow programmer name.
Each keyword parameter separated by comma (,).
Information passed in Keyword parameters used by the JOB.
Keyword parameters information applies to all steps in the JOB.
Keyword parameters can be specified at the JOB card or at step level.
Each keyword parameter is independent and not dependent on any other parameters.
Keyword parameters are more than 20. However the below parameters are mainly used.
Let’s discuss the parameters one by one.
CLASS parameters used to categorize the jobs. I.e. SHORT RUN or LONG RUN jobs.
CLASS always referred with one letter and allows alphabetic (A-Z characters), numeric (0-9) as well.
CLASS type predefined by system during system installation and every CLASS type has its own characteristics.
CLASS definition includes number of resource constraints, usage and CPU time etc,.
CLASS parameter can be explained in detail here .
MSGCLASS parameters used to describe where the JCL messages routed.
MSGCLASS always referred with one letter and allows alphabetic (A-Z characters), numeric (0-9) as well.
MSGCLASS type predefined by system during system installation and every MSGCLASS type has its own characteristics.
Each MSGCLASS is mapped to a device or location.
MSGCLASS parameter can be explained in detail here .
MSGLEVEL is used to print all the messages when the JOB terminates normally or abnormally.
MSGLEVEL used to control the volume of the messages from server as well.
It is mainly used to control the output messages which will be printed on the JOB log.
MSGLEVEL (0, 0) is default.
MSGLEVEL parameter can be explained in detail here .
PRTY controls the JOB execution by giving a priority to JOB.
PRTY determines the priority of JOBs within the same CLASS.
PRTY can be referred with Numeric number with the range of 0-15.
Higher number will have the higher priority during the execution.
PRTY parameter can be explained in detail here .
TIME specifies the maximum CPU usage time allowed for the JOB to execute.
TIME parameter can be coded at the JOB level and step level too.
If TIME parameter coded at both JOB and Step level, it will take the minimum to execute the particular step.
System will automatically cancel the JOB execution, if the execution time reaches to the time specified.
TIME parameter can be explained in detail here .
REGION parameter is used to specify the size of the virtual storage required to execute the JOB.
REGION parameter can be coded at JOB level and Step level.
If the REGION parameter coded at both JOB and Step level, JOB card overrides the Step level parameter.
REGION parameter can be explained in detail here .
TYPERUN is used for special job processing like to scan JOB for syntax errors etc.
TYPERUN used to specify for the JOBs which are not started.
If the TYPERUN submitted with TYPERUN, the JOB will fail.
TYPERUN parameter can be explained in detail here .
NOTIFY is used to send the notification of the job status when the job completed.
Identifies the user that the system to notify.
While running the JOB, system replaces &SYSUID with the user ID who submitted the JOB.
The system replaces &SYSUID from either the USER parameter from the JOB statement or the user ID from which the job was submitted.
NOTIFY parameter can be explained in detail here .
RESTART is used to restart the execution from a particular step.
Normally RESTART parameter will be used to start execution of a particular step from where it’s got abended.
RESTART parameter can be explained in detail here .
Condition parameter is used to decide execution of the JOB based on the other return code.
COND parameter can be coded at JOB level and Step level.
Maximum 8 conditions can be coded in single COND.
If COND parameter coded at both JOB level and STEP level, step level will override the job level COND parameter.
COND parameter can be explained in detail here .
If any questions on the above, post your queries on Jcl Discussion forum
Jobcard Positional Parameters JCL CLASS parameter