Defining the Home Node

The first step in defining the home node is to name it and to specify it as the home node. To name the node, code the NAME= parameter. To specify the node as the home node, code HOME=YES.

If this node is to be part of a TCP/IP network, a NETSERV statement must be coded or dynamically added later.

If this node is to be part of an NJE network that uses the SNA protocol, you can also code the BDTID parameter. This parameter identifies which MVS/BDT subsystem in your JES3 complex is processing SNA networking transactions. The name specified on this parameter must match the name specified on the MVS/BDT SYSID statement.

If the node uses the BSC protocol, you can also specify the number of logical printers or punches associated with this node. You can specify from 1-99 logical printers, from 1-99 logical punches, or both. The number of logical printers determines how many jobs can concurrently spool network print data to a networking writer. The number of logical punches determines how many jobs can concurrently spool network punch data to a networking writer.

To request logical printers, code the NJEPR parameter; for logical punches, code the NJEPU parameter. If you omit the NJEPR parameter, JES3 assumes 3 logical printers. If you omit the NJEPU parameter, JES3 assumes 3 logical punches.

When defining the home node, you can also specify default SYSOUT classes for print and punch output received from other nodes. If the characteristics of the SYSOUT class associated with received output does not match the characteristics of the SYSOUT class defined for the home node, the default class that you specify is used. For example, if SYSOUT class C is defined as a print class at the home node, and punched output, designated as SYSOUT class C, is received from a remote node, the value that you specified in the PUNDEF parameter is used.

To assign a default print class, code the PRTDEF parameter; to assign a default punch class, code the PUNDEF parameter. If you omit the PRTDEF or PUNDEF parameter, JES3 assumes SYSOUT class A for print output and SYSOUT class B for punch output.

To influence how the home node handles NETDATA, you code the NETHOLD= keyword parameter to indicated whether NETDATA is held at the node or released to JES3 writers.

To influence how the home node handles incoming SYSOUT whose characteristics, as specified by the sending node, do not match the characteristics of the SYSOUT class, you code the DEFCLASS or XNAMEREQ parameter. "Characteristics" includes whether the SYSOUT is print or punch output, and whether it is held for TSO, held for external writer, or not held.

DEFCLASS determines whether default SYSOUT classes may be assigned. PRTDEF, PUNDEF, PRTTSO, and PRTXWTR define the default classes. If default SYSOUT classes may be assigned, then XNAMEREQ determines how SYSOUT, that is defined as held for external writer, should be handled if no external writer name is present.