Processing the PARM parameter
If you omit the PARM parameter from the EXEC PGM=DFHSIP statement, CICS assumes that there are no SIT overrides or other initialization parameters and tries to load an unsuffixed module named DFHSIT.
As a general rule, the PARM parameter must at least specify the suffix of your system initialization table, using the SIT keyword. Alternatively, you can code the special SYSIN keyword as the only PARM parameter, and supply the suffix of your SIT and the other system initialization parameters from the SYSIN data set.
- If CICS finds a SIT parameter but no SYSIN keyword, CICS tries to load the SIT as soon as it has finished scanning the PARM parameter. Processing any CICS system initialization parameters that are also present in the PARM parameter takes place only after the SIT has been loaded.
- If CICS finds a SIT parameter and also a SYSIN keyword,
CICS does not try to load the SIT until it has also finished scanning the
SYSIN data set. In this case, loading the SIT is deferred because there might
be other SIT parameters coded in the SYSIN data set that
override the one in the PARM parameter.
Processing any system initialization parameters that are also present in the PARM parameter takes place only after the SIT has been loaded.
Rules for coding the PARM parameter
The following rules apply when coding the PARM parameter:
- The maximum number of characters you can code is 100, excluding the opening and closing delimiters, which can be either apostrophes or parentheses.
- All CICS system initialization parameters must be separated by a comma, and the separating commas are included in the 100 character limit. Because of this limiting factor, you might prefer to limit the use of the PARM parameter to specify the SYSIN control keyword only.
The rules for coding the PARM parameter on an EXEC job control statement are described fully in z/OS MVS JCL Reference.