Nodes are Entire System Server nuclei or Entire System Server/UNIX servers and refer to machines or CPUs on which requests to the operating system are executed. They are distinguished by numerical identifiers in the same way as database IDs distinguish between different Adabas databases.

If you are using Entire Operations in a multi-CPU environment, you must define node numbers for machines. Networks and jobs can thus be defined to run under Entire Operations control on different nodes.

Within Entire Operations, each UNIX and Windows server is assigned a node number. More than one operating system server node can reside in one physical machine. The machines identified by node IDs can run different target operating systems.

Entire Operations recognizes the operating system, thus allowing cross-operating-system job control. Communication paths between otherwise isolated nodes are provided by the Software AG products Entire Net-work and EntireX Broker, which allow a transparent connection of nodes, irrespective of how they are physically linked.

For an example scenario, see the section Entire Operations in Client/Server Environments in the Installation and Setup documentation.

This document covers the following topics:

• Listing all Nodes

• Displaying, Modifying and Adding a Node Definition

• UNIX and Windows Node Definitions

• Viewing Node Information

• Other Definitions for a Node (Mainframe)

• Other Definitions for a Node (UNIX and Windows)

• EntireX Broker Service Definition (UNIX and Windows)

• SAP Definitions (UNIX and Windows)

• Deleting a Node Definition

Related Topic:

• Logging on and off an Operating System Server Node in the User's Guide

---

Listing all Nodes

To list all nodes defined to Entire Operations

1. From the Main Menu, select the System Administrator Services option and press ENTER.

   The System Services Menu appears.

2. Select the Definition of Nodes option and press ENTER.

   An Operating System Server (Node) Table screen similar to the example below appears:

   08.03.16 ***** Entire Operations ***** 16:53:59 Owner EXAMPLE Operating System Server (Node) Table ------------------------------------------------------------------------------- Wait a. VSE Time Cmd Node Name Number Short AM Op.Sys. Error SSU SysId Diff. Valid _ Node 0001 1 N0001 N 4 U 3 -11.50 yes _ Node 0002 2 N0002 N BS2000 5 yes _ n4 4 N4 B 5 10.00 yes _ n5 5 N5 B 5 yes _ Adabas DB 9 9 N0009 N 5 yes _ TEST 12 HUGO N 5 yes _ hannes 21 21 N 5 yes _ BS2000 SIH2 31 N0031 N BS2000 1 U yes _ Broker 34 34 N0034 N rted 5 yes _ BS2 131 38 N0038 N BS2000 5 yes _ NPR 321 40 N0040 N MVS/ESA 5 yes _ Locl Nd DQA V134 42 N0042 N MVS/ESA 5 yes ------------------------------------------------------------------------------- B Broker D Delete I Info M Modify O Other S SAP Command => ____________________________________________________________ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Add End Save Up Down Menu

   The screen contains a list of nodes defined in Entire Operations (the list is empty if no nodes are defined).

This section covers the following topics:

• Columns: Operating System Server (Node) Table

• Line Commands: Operating System Server (Node) Table

Columns: Operating System Server (Node) Table

The columns on the Operating System Server (Node) Table screen are explained in the following table.

Column	Description
Cmd	Line command input field. For possible line commands, see Line Commands: Operating System Server (Node) Table.
Number	Entire System Server or UNIX node number.
Short	Short node name.
Node Name	User-defined (long) node name.
AM	Access mode:
	N	Use Entire Net-Work for Mainframe nodes.
	B	Use EntireX Broker for UNIX and Windows nodes.
	L	Local node (invoked directly on the machine where Entire Operations is running; for Entire Operations on UNIX and Windows only).
Op. Sys.	Operating system under which the node is running as received from the last SYSTEM-INFO call to Entire System Server or UNIX/Windows system information.
Wait a. Error	Wait after error. Time in minutes to wait until the next node access after a temporary error.
SSU	Submit Security User Type: see Fields: Monitor Defaults. If empty, the system-wide default is in effect for this node.
VSE SysID	The SYSID defined for a z/VSE node is added to the job cards of jobs submitted on this node.
Time Diff.	Time difference between local time and GMT in hours if the node is in a different time zone.
Valid	Possible values:
	yes	Node can be used.
	no	Node has been disabled.

Line Commands: Operating System Server (Node) Table

The following one-character line commands are available on the Operating System Server (Node) Table screen:

Command	Description
B	Applies to UNIX and Windows nodes only. Open the Node: Broker Service Definition window: see EntireX Broker Service Definitions.
D	Delete the selected node definition: see Deleting a Node Definition.
I	Open the Node Information window: see Viewing Node Information.
M	Open the Node Modification window: see Displaying, Modifying and Adding a Node Definition.
O	Open the Node: Other Definitions window: see Other Definitions for a Node (Mainframe) and Other Definitions for a Node (UNIX and Windows).
S	Open the Node: SAP Definitions window: see SAP Definitions (UNIX and Windows).

Displaying, Modifying and Adding a Node Definition

To display or modify a node definition

1. On the Operating System Server (Node) Table screen, enter the line command M next to the required node and press ENTER. 

   A Node Modification window similar to the example below opens:

   +------------------------------------------------------------+ | | | Node Modification | | | | Node Number ==> 1____ | | Short Name ==> N0001 | | Node Name ==> Node 0001_______________________ | | Access Mode ==> N | | Time Difference ==> ___________ | | Password Mode ==> _ | | z/VSE SysId ==> 3 | | Wait after Error ==> 4__ min. | | Submit Security User Type ==> U | | Valid ==> Y | | | | PF1 Help PF3 End PF5 Save | +------------------------------------------------------------+

   You can modify the definition by replacing the current values. The input fields are described in Fields: Node Definition.

2. Press ENTER to save the modifications.

3. Choose PF3 (End) to close the window and return to the Operating System Server (Node) Table screen.

To add a node definition

1. Choose PF2 (Add) on the Operating System Server (Node) Table screen.

   A Node Definition window opens. The input fields correspond to the fields contained in the Node Modification window. They are described in Fields: Node Definition.

2. Enter the required values.

   When finished, press ENTER to save the node definition.

3. Choose PF3 (End) to return to the list of nodes.

   The new node is added to the list.

This section covers the following topics:

• Fields: Node Definition

Fields: Node Definition

The fields in the Node Definition or Node Modification window are explained in the following table:

Field	Description
Node Number	Node number. Valid range: 1 to 99900.
Short Name	Mnemonic short name for the node. The mnemonic short name can be used instead of the node number in various locations. This can be set in the Representation options of the user profile.
Node Name	Unique, user-defined node name. For nodes with access mode N: Enter a short description to help the user select an appropriate node for a network or job run. For nodes with access mode B: Enter the name of a UNIX or Windows node (server) as it appears in System Automation Tools and EntireX Broker definitions in the SATSRV text object contained in the Natural SYSSATU library (see also the example of a node definition in the Installation and Setup documentation). This field is case-sensitive.
Access Mode	Possible values:
	N	Use Entire Net-Work for mainframe nodes.
	B	Use EntireX Broker.
	L	Use the local node (invoked directly on the machine where Entire Operations is running; for Entire Operations on UNIX and Windows only).
Time Difference	Difference between local time and GMT in hours if the node is in a different time zone. Input format: xn, where: x is a plus or minus sign (+ or -), and n is any number from 0 to 12.
Password Mode	This setting is evaluated for nodes on z/OS only. Conversion mode to be used for password entries. Possible values:
	U	Passwords are converted to upper case (default for mainframe nodes).
	M	Passwords in lower or mixed case are not converted to upper case (default for UNIX and Windows nodes).
	The password mode currently set is indicated in the Node Logon window (see the section Logon Function in the User's Guide).
z/VSE SysID	ID added to the job cards of jobs submitted on a z/VSE node. Valid range: 1 to 9.
Wait after Error	Time in minutes to wait until the next node access after a temporary error. Default: 5 minutes.
Submit Security User Type	Submit security user type can be set individually for each node. If this field is blank, the global default applies to this node: see the Submit Security User Type field described in Monitor Defaults for possible values of this field.
Valid	Allow or disallow use of the node. Possible values:
	Y	Allow use.
	N	Disallow use.

UNIX and Windows Node Definitions

UNIX and Windows nodes (i.e. on Entire System Server) must be defined in the following locations as well:

• SATSRV/SYSSATU (see the section Definitions for Entire System Server in the Installation documentation of System Automation Tools.)

• EntireX Broker parameters. You can omit these definitions for the Monitor node if this node is accessed in local mode.

• Entire System Server/UNIX or Windows initialization file npr.ini (see Customize the NPR Server in the section Completing the Installation in the Entire System Server documentation).

  Note:
  For each combination of UNIX or Windows node and user ID, at least one successful login (by LOGON NODE) must have been made, before this combination can be used within the Entire Operations Monitor. These LOGON NODE commands must be repeated after a password modification on a UNIX or Windows system.

Viewing Node Information

The Node Information window displays general information on the node. In addition to the Node Modification window, it also provides product-specific information.

To view additional information on a selected node

1. On the Operating System Server (Node) Table screen, enter the line command I next to the required node.

2. Press ENTER

   A Node Information window similar to the example below opens:

   +---------------------------------------------------------------------------+ | | | Node Information | | | | Node Number ==> N0077 (77) MVS/ESA | | Node Name ==> Test Node 77 | | | | NPR Version ==> 3.5.4 | | OS Release ==> z/OS 02.01.00 | | | | | | PF1 Help PF3 End | +---------------------------------------------------------------------------+

   The following fields (read-only) are provided in the window:

   Field	Description
   Node Number	Short name and number of the node.
   Node Name	Long name of the node.
   NPR Version	Version of the Entire System Server (NPR) installed at your site.
   OS Release	Information (where available) on the operating system that hosts the server node at your site.

Other Definitions for a Node (Mainframe)

To add or modify other definitions for a mainframe node

• On the Operating System Server (Node) Table screen, enter the line command O next to the required mainframe node and press ENTER.

  A Node: Other Definitions window similar to the example below opens:

  +---------------------------------------------------------------------------+ | | | Node: Other Definitions | | | | Node Number ==> N0042 (42) MVS/ESA | | Node Name ==> Locl Nd DQA V134 | | | | Default User ID ==> SAG_____ Spool Class to be set ==> ________ | | E-Mail Code Page ==> ________ | | E-Mail SYSOUT Class ==> _ | | E-Mail Sender ==> John.Test@softwareag.com_____________________ | | E-Mail Reply-To ==> Martha.Test@softwareag.com___________________ | | | | PF1 Help PF3 End PF5 Save | +---------------------------------------------------------------------------+

  The fields in the window are explained in the following section.

Fields: Node Definition (Mainframe)

Field	Meaning
Default User ID	User ID used by the Monitor for actions for which no specific user ID is available on the job or network level.
Spool Class to be set	Spool class to be set after job completion. You can enter any valid z/OS or z/VSE spool class to which the job spool class will be set after job completion. Usage precedence: Spool class defined for an Entire Operations job. Spool class defined here in this field (Spool Class to be set). Spool class defined in the Entire Operations defaults for z/OS or z/VSE. Note: If you enter a minus sign (-) here, the global default will not be applied.
E-Mail Code Page	E-mail host code page (z/OS and BS2000). The host code page to be used for e-mail sending. Refer to the description of the field HOST-CODE-PAGE of the Entire System Server view SEND-EMAIL.
E-Mail SYSOUT Class	(z/OS and older Entire System Server versions only.) SYSOUT class to be used for e-mail messages, which are sent from z/OS via SMTP.
E-Mail Sender	Default sender name for e-mails which are sent via this node. The commercial at sign (@) can also be coded as (a).
E-Mail Reply-To	Return address for e-mails which are sent via this node. The commercial at sign (@) can also be coded as (a). The name specified in E-Mail Sender is used by default.

Other Definitions for a Node (UNIX and Windows)

To add or modify other definitions for a UNIX or Windows node

• On the Operating System Server (Node) Table screen, enter the line command S next to the required UNIX or Windows node and press ENTER.

  A Node: Other Definitions window similar to the example below opens:

  +--------------------------------------------------------------------------+ | | | Node: Other Definitions | | | | Node Number ==> N0409 (409) Win 10 | | Node Name ==> npr_pcsn02_win | | | | Default User ID ==> SAGTEST_____________ | | Default Group ==> EUR_________________ | | Print Command ==> type :f: >lpt3___________________________________ | | E-Mail Sender ==> John.Test@softwareag.com_________________________ | | E-Mail Reply-To ==> Martha.Test@softwareag.com_______________________ | | Message Command | | blat ":f:" -s ":u:" -i ":s:" -t ":r:"________________________________ | | OPO Block Name ==> MFX___ | | Cygwin Dir. ==> c:/cygwin64______________________________________ | | | | PF1 Help PF3 End PF5 Save | +--------------------------------------------------------------------------+

  The fields contained in the window are explained in the following section.

Fields: Node Definition (UNIX and Windows)

Field	Meaning
Default User ID	UNIX or Windows user ID used by the Monitor for actions which do not depend on a specific network or job.
Default Group	UNIX: If this field is empty, the default group name as defined in /etc/passwd is used. Otherwise, this field contains the name displayed when you issue the UNIX command groups. Windows: The domain name used to log on to the server. Note: You can replace symbols in network and job definitions.
Print Command	Print command (UNIX or Windows) for SYSOUT files on this node. :f: will be replaced by the file name. Example: lp -dxxxx :f:
Message Command	Message send command (Windows only). This command is used to send a user message out of Entire Operations. blat can be specified without parameters. Replacements: :s: sender name (optional) :u: subject (title of the message, optional) :r: recipient :f: name of the file containing the message Entire Operations automatically makes these replacements. Examples: blat blat ":f:" -s ":u:" -i ":s:" -t ":r:" (Parameters must be enclosed in quotes if they contain blanks.)
E-Mail Sender	Default sender name for e-mails which are sent via this node. The commercial at sign (@) can be coded as (a).
E-Mail Reply-To	Return address for e-mails which are sent via this node. The commercial at sign (@) can also be coded as (a). The name specified in E-Mail Sender is used by default.
OPO Block Name	Applies to UNIX and Windows nodes only. You must specify a block name in this field if you want to send files or SYSOUT from this node to Entire Output Management (NOM) by using the Open Print Option (OPO). The OPO Block Name determines the configuration block in the nomrptConf.xml file to be used by OPO.
Cygwin Dir.	Applies to Windows only. Base directory of a Cygwin installation. This field is only required if jobs of the type WCB (Windows Cygwin Bash) are used on a Windows node. The directory name can contain a slash (/) instead of a backslash (\). Example: c:/cygwin64

EntireX Broker Service Definition (UNIX and Windows)

This function displays the EntireX Broker service definition if specified for the selected node.

To view the EntireX Broker service definition for a selected node

• On the Operating System Server (Node) Table screen, enter the line command B next to the required UNIX or Windows node and press ENTER.

  A Node: Broker Service Definition window similar to the example below opens:

  +----------------------------------------------------------------+ | | | Node: Broker Service Definition | | | | Node Number ==> N0401 (401) Windows7 | | Node Name ==> npr_pcsn01 | | | | Broker ID | | BKR034 | | Server Class ==> NPR | | Server Name ==> PCSN01 | | Service ==> npr_pcsn01 | | Locale String ==> | | User ID ==> IBM1 | | Wait Time ==> 30S | | | | PF1 Help PF3 End PF5 Save PF6 Refresh PF9 Del. | +----------------------------------------------------------------+

  The fields (read-only) contain the current attributes of the EntireX Broker service definition specified for the node.

  The EntireX Broker service definition for the node can only be modified in the SATSRV text object in the Natural SYSSATU system library on the server. If you change the service definition, use PF6 (see below) for an update.

  The window provides the following special PF keys:

  PF Key	Name	Function
  PF6	Refresh	With this function you can force a re-read of the service definition from SATSRV/SYSSATU into Entire Operations.
  PF9	Delete	With this function you can delete all fields of an EntireX Broker service definition in Entire Operations at once. Note: This does not delete any entries in SATSRV/SYSSATU.

SAP Definitions (UNIX and Windows)

Jobs of the type SAP require SAP-specific default values to set environment variables using jexa4S. All definitions are mandatory to run jobs of the type SAP.

To add or modify SAP definitions for a UNIX or Windows node

• On the Operating System Server (Node) Table screen, enter the line command S next to the required UNIX or Windows node and press ENTER.

  A Node: SAP Definitions window similar to the example below opens:

  +-----------------------------------------------------------------------------+ ! ! ! Node: SAP Definitions ! ! ! ! Node Number ==> N0517 (517) Linux ! ! Node Name ==> npr_pcsn ! ! ! ! JEXA4S_EXE ==> /opt/softwareag/nop/jexa4s/bin_x86_64/jexa4s_______________ ! ! JEXA4S ==> /opt/softwareag/nop/jexa4s/ini_____________________________ ! ! RFC_INI ==> /opt/softwareag/nop/jexa4s/ini/saprfc.ini__________________ ! ! ! ! ! ! ! ! PF1 Help PF3 End PF5 Save ! +-----------------------------------------------------------------------------+

  The SAP-specific fields contained in the window are explained in the following section.

Fields: Node - SAP Definitions

Field	Description
JEXA4S_EXE	Full path name of the jexa4s executable. Example: /opt/softwareag/nop/jexa4s/bin_x86_64/jexa4S
JEXA4S	This path will be set as the JEXA4S environment variable prior to the invocation of jexa4s. Example: /opt/softwareag/nop/jexa4S/ini
RFC_INI	This path will be set as the RFC_INI environment variable prior to the invocation of jexa4s. Example: /opt/softwareag/nop/jexa4S/ini/saprfc.ini

Deleting a Node Definition

Before you delete a node, consider the impact on master or active objects using this node:

• When a node definition is deleted, this node is no longer available for new objects like network or job definitions.

• A deleted node is not invalidated in existing objects.

• A node status list can still show a deleted node as active.

• Various node access errors can occur if a deleted node is still referenced, for example, during network activation or job submission.

To delete a node definition

1. On the Operating System Server (Node) Table screen, enter the line command D next to the required node and press ENTER.

   A confirmation window opens.

2. Enter the node number and press ENTER to confirm the deletion and close the window.