Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Output processing section Network Job Entry (NJE) Formats and Protocols SA32-0988-00 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
The Output Processing Section is used for transmitting output processing parameters and is identified by an identifier field of X‘89’ and a modifier field of X‘00’. This section's length is variable and depends on the type and number of output processing parameters being transmitted. The individual output processing parameters are represented by self defining data structures contained within the Output Processing Text Block (OPTB) which follows a fixed length portion of the section. The parameter representations are termed Output Processing Text Units (OPTUs or TUs) and their structure is defined in Output Processing Text Block. The set of NJE defined OPTUs are defined in OPTU Key Definitions. The 3800 section of the data set header is still built if the user specifies any 3800 attributes. Some fields are duplicated in the OPTB. However, if any of the 3800 fields are changed by operator command, those changes need only be reflected in the 3800 section, not in the OPTB. The 3800 section fields override the OPTB at the SYSOUT destination. Table 1 describes the format of the output processing section of the data set header. The output processing section includes several fields that describe the length of parts of the output processing section. All length fields include the length of their own field. For example, field NDHSLEN is the length of the entire output processing section including the length of field NDHSLEN. Note: JES2 and JES3 call this section the “data stream” section in
their control block references.
|
Copyright IBM Corporation 1990, 2014
|