Data set header general section

This field may be set at execution time from either NJHGPRTN or NJHGPUNN.

AS/400 sets and uses this field as the destination address for the data set.

This field may be set at execution time from either NJHGPRTR or NJHGPUNR.

AS/400 sets and uses this field as a destination userid. If the received userid is blanks or zeros, this product substitutes ‘SYSTEM’ as the destination userid.

JES2 and JES3 also use this field for the TSO/E TRANSMIT and RECEIVE commands. If this field and the NDHGXWTR field are the same, this field is used as the TSO destination userid.

RSCS sets the field to the destination userid or printer (or X‘00’ when SYSTEM is the destination).

POWER uses the field to route the NJE job to a remote workstation, userid, or program.

RSCS sets the field from the information in FILENAME. RSCS does not use the field.

POWER defaults this field and does not use it.

For print files, AS/400 sets this field from the spooled file name and uses this field for the spooled file name.

For punch files, AS/400 sets this field to the database file name and uses this field as the database file name.

RSCS sets the field from the information in FILETYPE. RSCS does not use the field.

POWER defaults this field and does not use it.

AS/400 sets this field to the default value, but does not use it.

JES3 If blank or zero on input, JES3 uses the NJHGROOM value as a DDNAME. If NJHGROOM is blank this system uses a default DDNAME of ‘*NJEWKnn’, where ‘nn’ is an internal index value.

RSCS and POWER default the field and do not use it.

AS/400 sets this field to the default value, but does not use it.

There is no internal JES2 limit to this number. There is a storage limitation in the converter to 4096 datasets in one job.

JES3, RSCS, and POWER default the field and do not use it.

AS/400 sets this field from the CLASS parameter on the SNDNETF and SNDNETSPLF commands, but does not use it.

JES2 sets the SYSOUT class to A if the class specified in the job's JCL is not alphanumeric.

JES3 sets the field to the SYSOUT class. If receiving an NJE SYSOUT job, this field is used if the class and type (indicated by NDHGF2PR and NDHGF2PU) do not conflict with the local system's use of class/type.

If a conflict exists, a default class is used for the appropriate type.

RSCS uses the field for the VM output class and sets it from this class unless overridden by the SYSOUT keyword on the TAG.

POWER sets the SYSOUT class to the output class. POWER Version 4.1.2 supports numeric classes for output. For all versions prior to 4.1.2, only A-Z are valid (set to A if not in the range A-Z when received).

AS/400 sets this field, but does not use it.

JES2 uses the field as the line count of the data set. A spanned record counts as 1, regardless of the number of segments.

JES3 sets the number of records in the data set but does not use the information.

RSCS uses the information in a message to the user. RSCS sets the field from the record count in the spool file block.

POWER sets and uses the field as the line count.

AS/400 sets this bit off and does not use it.

JES2 sets the bit from information in the job's JCL. JES2 sometimes sets this bit for the TSO/E TRANSMIT and RECEIVE commands according to the data set disposition.

JES3 does not use this bit but sets it for spin data sets and data sets generated by the TSO/E TRANSMIT and RECEIVE commands.

RSCS uses the bit to separate data sets into individual spool files, but does not set this bit.

POWER sets the bit only if the data set is segmented and uses the bit to determine the job number. If the flag is on, the job number is set from the job header (NJHGJID), otherwise a new job number is assigned.

AS/400 sets and reads this bit to determine whether the print file should be held before printing.

JES2 sets the bit from information in the JCL and uses it to place the data set on the system output hold queue.

JES3 sets the bit and uses it to place the data set on the system output hold queue.

RSCS uses the bit to indicate to the destination node that it is to hold the data set. The bit is set when specified by the originator on the TAG command using the HOLD keyword.

POWER uses the bit and sets it if the data set disposition is ‘H’ or ‘L’.

AS/400, JES3, RSCS, and POWER do not use the bit but set it to the default value.

JES2 uses the bit to indicate that the data set is the JES2 job log.

AS/400 sets this bit on for print files, but does not use it.

JES2 and RSCS do not use this bit but set it with the default value.

JES3 sets the bit if OVFL=OFF is specified on the //*FORMAT statement in the job's JCL. JES3 uses the bit as described above.

POWER uses the field but does not set it.

AS/400, RSCS and POWER do not use this bit but set it to the default value.

JES2 and JES3 use the information from the job's JCL to set the bit.

AS/400 sets this bit on for print files, but does not use it.

JES2 sets and uses the bit if field NDHGF1LC is set on.

JES3, RSCS, and POWER set this bit to the default value, but do not use it.

AS/400 sets this bit off and does not use it.

JES2 uses the bit to avoid multiple instances of the job statistics in the job log.

JES3, RSCS, and POWER do not use this bit, but set it to the default value.

NDHGF1IN    0      1      0       1
NDHGF1DF    0      0      1       1

           |      |       |       |
            V      |      V       |
Meaning:   Use     |    Do not    |
         default   |   interpret  |
                   V              V
                Interpret      Interpret

AS/400 sets this bit to the default value, but does not use it.

JES2, RSCS, and POWER default this bit and do not use it.

   11.. ....   undefined format
   10.. ....   fixed format
   01.. ....   variable format

AS/400:

For print files, this system sets either variable or fixed format (bits 1 and 1).

For punch files, AS/400 sets this field to X‘80’.

JES2 uses the RECFM in the DCB specified in the job's JCL to set the field. The DCB defines other settings that are not defined by this field. However, JES2 allows all flag settings and transmits them across the network.

JES3 uses the RECFM in the DCB specified in the job's JCL to set the field beginning with z/OS release 1.8.

RSCS sets this field to X‘42’ for print files, and X‘80’ for punch files.

For print files, it is used to decide what record length to use in determining whether to make an incoming file a virtual 1403 file or a 3211 file. (For further details, see the following field, NDHGLREC.)

For punch files, this field is used with NDHGLREC to determine the proper record length to use in detecting files containing punch records greater than 80 characters. It is also used in determining whether to forward punch records of a store-and-forward file with or without carriage control.

This field is modified for certain types of store-and-forward data when RSCS acts as an intermediate node.

POWER does not use this field, but sets it to C‘Cx’ (undefined) and supports all values of the field.

... .00. no carriage control
... .10. ASA control characteristics
... .01. machine control 
         characteristics
... .11. MODCA or AFPDS print files

AS/400:

For punch files, AS/400 sets this field to X‘80’.

JES2 uses the RECFM in the DCB specified in the job's JCL to set the field.

JES3 sets the carriage control to ASA, machine, or none (bits 5 and 6 off). Only carriage control bits are used on input.

RSCS sets this field to X‘42’ for print files, and X‘80’ for punch files.

For punch files, this field is used to determine whether to forward punch records of a store-and forward file with or without carriage control.

This field is modified for certain types of store-and-forward data when RSCS acts as an intermediate node.

For Version 3.1, this last restriction is removed.

POWER does not use this field, but sets it to X‘Cx’ (undefined). At store-and-forward nodes, files having ASA carriage control will not have the CC converted to machine carriage control.

JES2 obtains the LRECL from the DCB. It includes the carriage control character.

Print with CC   133  (132 without CC)
Punch with CC    81  (80 without CC)

RSCS uses this field as follows:

   Record Length       Device
      1 - 132           1403
    133 - 150           3211
    151 - 204           3800
205 - 32765VAFP (if supported 
on a VM system)

POWER uses the field and sets it to the maximum length of any record in the data set, up to a maximum record length of 32K-1.

JES2 sets the data set copy count to the number of copies for the data set.

JES3 sets and uses the data set copy count. If the value in the field is 0, one copy of the data set is produced.

RSCS sets the field from the copy count specified on the SPOOL command. RSCS uses the field to set the spool copy count.

POWER sets the field with the information supplied from the COPY parameter of the '* $$ LST' or '* $$ PUN' statement. It is used as the copy count (defaulted to 1).

AS/400 sets this field to the default value, but does not use it.

JES2 supports both right and left indexing.

JES3 and POWER do not use this byte but set the byte to the default value.

RSCS does not use the field. Set from the INDEX keyword on the TAG statement. (Only positive values may be specified.)

AS/400 sets this field to the default value, but does not use it.

JES2 obtains the value from the job's JCL. The special values X‘00’ and X‘FF’ are used as follows:

X‘00’ (default): Use the default value of the printing subsystem.

X‘FF’ : Do not force any page ejects. Let the skipping be solely determined by the carriage control (if present) in the SYSOUT data.

JES3, RSCS, and POWER do not use this field, but set it to the default value.

AS/400 sets this field to blanks if AS/400 formtype is *STD or greater than 8 characters. In all other cases, the field is set equal to AS/400 formtype.

JES2 and JES3 use only the first four bytes, followed by blanks. Forms are set to zero if not specified. If received, either zero or blanks indicate the standard (STD) forms are desired.

RSCS sets the field with the value supplied by CP FORM unless that value is overridden by the value supplied by TAG. The default is only set when the CP SPOOL command specifies NULL for the FORM name. This field is used for the CP FORM when not defaulted. When the header field contains the default (blanks), the CP FORM name is set to the installation's default.

POWER uses only the first four bytes because POWER has only four-character forms names. For a 3800 SYSOUT data set, a value of X‘00’ indicates that hardware defaults are to be used. A value of X‘40’ indicates that software defaults are to be used. When the job originated on a non-POWER system (POWER section was not present), X‘00’ is used as the software default.

AS/400 sets the field to blanks for print files, then reads the field to determine the printer filename to open when spooling the files.

   'FCB1'    1403
   'FCB2'    3211 and 3203-5
   'FCB3'    3800
   'FCB4'    4245 and 4248

JES3 sets and uses the field, but the default is zero.

RSCS uses this field as the FCB on spool file. It is set from FCB on the SPOOL command. Only the first four characters are used. The field may be overridden by the CP TAG command (up to eight characters).

POWER uses the field as the FCB name. The field is set from the FCB name if one was specified. The last four characters may be set to ‘$$$$’ for device-independence. For a 3800 data set, a value of X‘00’ indicates that hardware defaults are to be used; a value of X‘40’ indicates that software defaults are to be used. When the job originates from a non-POWER system (POWER section was not present), X‘00’ is used as the software default.

AS/400 sets the field to blanks for print files and does not use it.

   'UCS1'    1403
   'UCS2'    3211
   'UCS3'    3203-5
   'UCS5'    4245
   'UCS6'    3262-5 and 4248

RSCS does not use the field. RSCS sets the field with the value specified on the UCS keyword in the TAG.

POWER sets the field with the UCS name specified on the * $$ LST statement.

AS/400 sets the field equal to NDHGRMT, but does not use it.

JES2 and JES3 set the field to the name of the external writer. A default of zero is set; either zero or blanks are accepted as defaults for input.

RSCS does not use this field but sets it to the value specified of the EXTWTR keyword if specified on TAG statement.

POWER does not use the field but sets it to the external writer name as specified on the DEST parameter.

AS/400 sets this field to the default value, but does not use it.

JES2 and JES3 set from the DSNAME= keyword on the DD JCL statement, or default it to a single question mark '?'. It is used to construct a resource name associated with this data set for purposes of resource access authorization.

RSCS does not use the field and sets it to the default.

POWER does not use the field and sets it to the default.

AS/400 sets and uses this bit for print files.

JES2 does not use the bit, but sets it if the output class is a print class at the output execution node.

JES3 uses this bit to denote print output. If there is print output, JES3 sets this bit.

RSCS uses the bit to cause the data set to be spooled to a printer. RSCS sets the bit if the input file is a print file.

POWER uses the bit to denote print output. It is set if the input file is a print file.

AS/400 sets and uses this bit for punch files.

JES2 does not use the bit, but sets it if the output class is a punch class at the output execution node.

JES3 uses this bit to denote punch output. If there is punch output, JES3 sets this bit.

RSCS uses the bit to cause output to be spooled to a punch device. RSCS sets the bit if the input file is a punch file.

POWER uses the bit to denote punch output. If there is punch output, POWER sets this bit.

AS/400 sets this bit, but does not use it.

JES2 and JES3 do not use the bit and set it to the default.

RSCS uses the bit to take the FILENAME and FILETYPE from the NDHGPROC and the NDHGSTEP fields respectively.

POWER does not use the bit and sets it to the default.

AS/400 sets this field to the default value, but does not use it.

JES2 sets this bit whenever the output disposition is either HOLD or LEAVE.

JES3 sets this bit whenever the output disposition of a data set is either HOLD or LEAVE. When this bit is set on, JES3 also sets bit NDHGF1HD to hold the data set at nodes not supporting output dispositions. JES3 uses this bit and bit NDHGF2HA to determine the output disposition of an incoming data set.

RSCS, and POWER do not use or set this field.

AS/400 sets this field to the default value, but does not use it.

JES2 sets this bit whenever the output disposition is either KEEP or LEAVE. When this bit is set on, JES2 also sets flag NDHGF1HD to hold the data set at nodes not supporting output dispositions.

JES3 sets this bit whenever the output disposition of a data set is either KEEP or LEAVE. When this bit is set on, JES3 also sets bit NDHGF1HD to hold the data set at nodes not supporting output dispositions. JES3 uses this bit and bit NDHGF2HB to determine the output disposition of an incoming data set.

RSCS, and POWER do not use or set this field.

AS/400, JES2, RSCS, and POWER do not use or set this field.

JES3 sets this bit to indicate the data had its blanks truncated when it was created and should have them truncated when the data set is received at the targeted JES3 node.

AS/400, JES2, RSCS, and POWER do not test or set this bit.

JES2 uses this bit for its JCL images and step completion codes data sets (EVENTLOG).

AS400, JES3, RSCS, and POWER do not test or set this bit.

AS/400, JES2, and RSCS do not use this bit but set it to the default value. (JES2 always blocks data checks.)

AS/400 sets this bit to the default value, but does not use it.

JES2, JES3, and RSCS do not use this bit but set it to the default value. JES2 loads the FOLD option on a character set if bit X‘40’ of the first byte (byte 0) is on in the UCS image.

• LINE
• PAGE
• SOSI1
• SOSI2

AS/400 sets this field to the appropriate process mode depending on AS/400 devtype, igcdta, and igcosi. If none of these settings are appropriate, the field is set to blanks. See OPTB for PRMODE, see key 0018 for other values when these are not appropriate.

JES2 and JES3 set the field from the PRMODE keyword on the OUTPUT JCL statement. If PRMODE is not specified, then the data itself is examined to determine the process mode.

RSCS moves this field into an XAB and sets it from an XAB (if existing) for VM/PSF.

For Version 3.1, RSCS sets this field from the PRMODE= tag parameter.

POWER sets this field from the PRMODE operand on a JECL statement, but does not use this field.

AS/400 does not read or set this field.

JES2 sets this field if the segment number is less than or equal to 99999, and uses this number on the default separator page.

JES3 and POWER do not read or set this field.