The following MVS JCL features are supported:
- Instream procedures
- Cataloged procedures
- Symbolic parameters
- EXEC statement overrides
- JOBLIB and STEPLIB DD statements
- DD statement overrides
- Conditional execution (specified by IF, THEN, ELSE, and ENDIF statements)
- Job restart after execution failure
- Concatenated data sets
- Instream data sets (preceded by a DD * or DD DATA statement)
- Partitioned data sets
- Generation data groups
- Temporary data sets
- Comments (indicated by //*)
- Normal mainframe nesting limits (that is, 15 levels of nested procedures and 15 levels of nested INCLUDE statements)
The following MVS JCL features are not supported:
- Multiple jobs in one jobstream
- Program control statements (enclosed by CNTL and ENDCNTL statements)
- Other special DD statements that are not relevant to the PC or that are implemented differently by
MSS. These statements have the following DD names:
- JOBCAT
- STEPCAT
- SYSABEND
- SYSMDUMP
- SYSUDUMP
- SYSCHK
- SYSCKEOV
More information about the MVS JCL statements supported by
MSS is given later in this section.
MSS supports the running of MVS JCL jobstreams either directly or via the TSO SUBMIT command and the Micro Focus extension ASUBMIT.
You can run these TSO commands with the IKJEFT01 utility.
Files containing MVS JCL jobstreams and cataloged procedures can be created on the PC or UNIX machine. Cataloged procedures
should be stored as members of partitioned data sets, known as procedure libraries. The procedure libraries are defined to
MSS in two different ways:
- The libraries defined in the JCLLIB statement, for a single job
- The libraries defined to
MSS, for all jobs.
MSS searches these libraries in the order specified above.
When the job is submitted
to an enterprise server for running , the effect depends on the setting of the TYPRUN parameter to the JOB statement as shown below:
| TYPRUN=SCAN
|
The syntax is scanned
|
| TYPRUN=COPY
|
The job stream is copied to a SYSOUT data set
|
| TYPRUN=HOLD
|
Holding of the job until explicitly released for execution
|
| No TYPRUN
|
The job is executed immediately, assuming resources are available
|
Exported JCL and system symbols:
- System symbols - it is possible to define system-wide symbols in the dataset
SYS1.PARMLIB(IEASYM00). This dataset is read when the system starts up and the defined values can then be used in JCL jobs. See the example job
INITSYS.JCL in the Samples Browser
jcl-symbols folder.
- JCL symbols may be exported and used in in-stream data and also passed with jobs submitted using the internal reader.