Configuration Best Practices › Common NJE Node Name

Common NJE Node Name

You can simplify NJE network configurations by operating an EMAS complex as one NJE node using a common NJE node name. A common VTAM Generic Resource name must have been previously defined to the EMAS complex so that VTAM sessions to any of the EMAS members are initiated by making a session to the VTAM Generic Resource name.

Business Value:

The management of your CA Spool system will be simplified because other external NJE nodes will only need one NJE connection to the CA Spool EMAS complex.

Additional Considerations:

If a VTAM Generic Resource name is defined and the NJENAME parameter is specified in the EMAS complex, the NJENAME parameter specifies a common NJE node name for the entire EMAS complex. Other external NJE nodes then just need one NJE connection to the EMAS complex. This NJE connection must specify the common NJENAME as the NJE node name and the common VTAM Generic Resource name as APPLID.

The members in an EMAS complex communicate using NJE connections. For these private NJE connections the individual Home Node NJE name and VTAM APPLID are being used.

The following rules decide which of the NJE definitions are considered to be the home node:

• When an EMAS member is started, it determines its member number by finding the Snn statement, which matches the specified SID parameter; the default is the actual SMF-provided system ID.
• The NJENAME sub-parameter of the matching Snn statement points to the NJE home node for the EMAS member.
• The APPL sub-parameter and NJE nodename of the NJE home node is used as the VTAM APPLID and local NJE node name by the EMAS member.