Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Text Format for JDT-defined JCL z/OS MVS Installation Exits SA23-1381-00 |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Long Parameters: The length of some parameters, such as a pathname for an hierarchical file, can be up to 255 bytes. Any parameter with a maximum length that is over 127 bytes is represented in the key entry format as a subparameter list within the key for the parameter. Each subparameter has a maximum length of 127 bytes. The PATH parameter is used to specify the pathname:
Example 1: In the following example, the PATH parameter
has 6 characters:
Even though the pathname parameter is only 6 bytes, it must be represented as a subparameter list because the maximum length of the pathname can be 255 bytes.
Example 2: In this example, the PATH parameter has
130 characters:
It would be represented
as shown in Table 2.
Because only 127 characters can fit in a single subparameter field,
the parameter must be represented as two subparameters. Therefore,
the Num of Subparameters field is 82.
Pre-MVS/ESA SP 4.1: For JCL converted on a pre-MVS/ESA SP 4.1 system, the JDT-defined keyword is the first parameter on the JDT key (X'1A').
MVS/ESA SP 4.1: For JCL converted on an MVS/ESA SP 4.1 system, the JDT-defined key for the specified JDT keyword is the first parameter on the JDT key (X'1A'). For JDT-defined keywords on the DD statement, refer to the macro IEFSJKEY. For JDT-defined keywords on the OUTPUT statement, refer to the macro IEFDOKEY.
|
Copyright IBM Corporation 1990, 2014
|