Tag: mainframe

The passing of job control information to the Job Entry Subsystem

The addressing of input resources

The performance of calculations

The sending of an email to the person who submitted the job

There is either a JCLLIB statement for the entire JOB, or a separate one for each EXEC

A JCLLIB statement can not have a statement name.

There can only be one JCLLIB statement per JOB.

A JCLLIB statement must be coded before the first EXEC statement.

Under no circumstances must a DD statement precede an EXEC statement

The OPERATION JOB can be coded in position 4.

An OPERATION can be coded beyond position 72, as long as it starts before position 72

A JCL OPERATION must be followed and preceded by at least one blank.

When TIME is added to a JOB statement, the entire job run time is limited to that amount

When REGION=0 is coded, the job will not execute due to the fact that no working storage

The COND parameter on JOB level will place the same condition on every EXEC statement,

TYPRUN=SCAN means that the entire JCL script will be checked for syntax and value

COND=(8,LE)

COND=(8,GE)

COND=(8,LT)

COND=(8,GT)

Step 1 can use 6 seconds of CPU time.

Step 2 has no time limitations.

Step 3 can use 15 seconds of CPU time.

Each step is limited to its specifically mentioned time, but the entire job can only use 10

A REGION parameter on an EXEC statement, overrides the REGION parameter on the JOB

A REGION parameter on an EXEC statement, limits the space available for that step, but

A REGION parameter on an EXEC statement, is only taken into consideration if there is no

The sum of all REGION parameters on EXEC statements, must be equal to the REGION

The COND parameter always indicates that if its condition is met, the step is NOT executed.

When adding the COND parameter to an EXEC statement that calls a procedure, this COND

With the COND parameter, we can only check return codes.

The COND parameter can check the return codes of multiple steps, but as soon as one of

&NAME&(TEMP)

&&TEMP(NAME)

&&NAME

&NAME

For both sequential and partitioned datasets to be extended or created.

Only for existing datasets to be extended

For all secured sequential datasets to be extended

Only for sequential datasets to be extended or created.