TYPERUN Parameter

TYPERUN Parameter

Note! TYPRUN parameter can be coded only at the job level.

TYPRUN is used to request special job processing like scanning jobs for syntax errors, library errors, etc. TYPRUN is used to scan the job without executing it. If a job is submitted with TYPRUN, the job fails. TYPRUN is a keyword parameter and is optional.

Syntax -

TYPRUN= {SCAN }
        {HOLD   }
        {JCLHOLD}
		{COPY   }
SCAN SCAN checks syntax errors without executing the job and allocating devices. SCAN used to check for -
  • The spelling of parameter keywords.
  • Invalid characters.
  • Unbalanced parentheses.
  • Misplaced positional parameters.
  • Invalid syntax on JCL statements in cataloged procedures.

While using SCAN, the system does not check the following -
  • Misplaced statements.
  • JCL sub-parameters syntax.
  • Inappropriate parameters or sub-parameters together.
COPY & JCLHOLD Options are available in JES2 only.
HOLD Requests the system to put the job on hold.
The operator should explicitly release the job to run.
To release the job, use "A" in front of the job in SPOOL, which brings the job to execution.

Examples -

Scenario1 - TYPRUN=SCAN.

//MTHEXMP1 JOB (META007),'PAWAN Y',TYPRUN=SCAN

Once the job is submitted, it first scans all the syntactical errors. If any errors are detected, the job fails with errors.

Scenario2 - TYPRUN=HOLD.

Job1 -

//MTHEXMP1 JOB (META007),'PAWAN Y' 
//STEP01   EXEC PRG=A
//DD01     DD   MTH.INPUT.DATA,DISP=SHR

Job2 -

//MTHEXMP2 JOB (META007),'PAWAN Y',TYPRUN=HOLD
//STEP01   EXEC PRG=B
//DD01     DD   MTH.INPUT.DATA,DISP=SHR

Job1 submitted directly without any TYPRUN parameter and job2 with TYPRUN=HOLD. So job1 starts running immediately, but job2 is on hold, and the operator should release it for execution.