This section provides instructions for logging on or off an Entire System Server node.

This document covers the following topics:

• Logon Function

• Fields: Node Logon

• Monitoring the Node Connection Status

• Logoff Function

---

Logon Function

To log on a node

1. Use the direct command LOGON or LOGIN as described in the Direct Commands documentation.

   Depending on the operating system of the specified node, a Node Logon window similar to the examples below opens:

   For a mainframe node:

   +---------------------------------------------+ ! ! ! ! ! Entire Operations ! ! Node Logon ! ! ! ! Node ===> 148 (N0148) ! ! XCEOR210 ! ! OpSys ===> MVS/ESA ! ! User ID ===> SAGTEST_____________ ! ! Password ===> ! ! upper case ! ! PF3 End ! +---------------------------------------------+

   For a UNIX node:

   +----------------------------------------+ | | | | | Entire Operations | | Node Logon | | | | Node ===> N0416 (416) | | vmesm01 | | OpSys ===> Linux | | User ID ===> SAGTEST_____________ | | Group ===> ____________________ | | Password ===> | | | | PF3 End | +----------------------------------------+

   For a Windows node:

   +----------------------------------------+ | | | | | Entire Operations | | Node Logon | | | | Node ===> N0401 (401) | | npr_pcsn01 | | OpSys ===> Windows7 | | User ID ===> SAGTEST_____________ | | Domain ===> SAG-HQ______________ | | Password ===> | | | | PF3 End | +----------------------------------------+

   In the input field(s), enter the required information. All fields are described in Fields: Node Logon.

2. Press ENTER.

   A Node Status screen similar to the example below appears:

   07.12.16 ***** Entire Operations ***** 17:40:34 Node Status at 17:40 ------------------------------------------------------------------------------ Node Server Name Op.Sys. Version L LogonUID Status Checked Usage N0123 NOP Test1 MVS/ESA 3.6.1 active 16:32 1 N0456 NOP Prod1 MVS/ESA 3.6.1 X SAG active 17:40 1 ******************************* Bottom of Data ******************************* Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help End Check Up Down

   You can press PF5 (Check) to refresh status display if last check was made some time ago.

   The screen columns are explained in Columns: Node Connection Status.

3. Press PF3 to return to the Main Menu.

Fields: Node Logon

The Node Logon window contains the following fields:

Field	Description
Node	Node number.
OpSys	Operating system on node.
User ID	Valid user ID. If you logon to a mainframe node, input text is converted to upper case letters. If you logon to a UNIX or Windows node, input text is not converted to upper case letters. Therefore, make sure an exact spelling in mixed case. See also Field Defaults.
Domain	Input field for Windows or UNIX nodes: Enter a Windows domain or UNIX group, respectively. Windows: If this field is left blank, the logon will be carried out without domain. Otherwise, this field must contain a valid domain. The default user ID and domain can be used (see the Administration documentation) for combinations of Entire Operations users and operating system servers (nodes). UNIX: If this field is left blank, the user's default UNIX group (from /etc/passwd) is used. Otherwise, this field must contain one of the UNIX groups, which is visible in the output of the UNIX groups command.
Group	Input field for UNIX nodes: Enter a UNIX group. If this field is empty, the user's default UNIX group (from /etc/passwd) is used. Otherwise, this field must contain one of the UNIX groups, which is visible in the output of the UNIX groups command. See also Field Defaults.
Password	Input field for the password of the user specified in the User ID field. If you logon to a BS2000 node, input text is converted to upper case letters. If you logon to a z/OS node, input text is converted to upper case letters depending on the setting of the password mode for the node (see the Administration documentation). The text below the Password Field indicates the password mode set: upper case or case-sensitive. You can set the password mode for a node in the Node Modification window described in Adding and Modifying a Node Definition in the Administration documentation.

Field Defaults

The default user ID - and perhaps also the group or domain - for logging on to a node can be defined for any combination of Entire Operations users and nodes (see User Definitions and Profile Settings in the Administration documentation). In this case, these values are displayed as defaults during the logon process.

They serve to simplify the logon process. If you want to logon with another user ID and/or group or domain, then these fields may simply be overwritten.

Monitoring the Node Connection Status

You can view a list with the current status of nodes defined in your environment.

To monitor the node connection status

• In the Command line, enter the following direct command:

  STATUS NODES

  (See also the STATUS command described in the Direct Commands documentation.)

  A Node Status screen appears.

  You can press PF5 (Check) to refresh status display if last check was made some time ago.

  The screen columns are explained in Columns: Node Connection Status.

For further information, see also the API NOPUST3N described under Inquire Network and Job Status, Symbol Table in the section API Routines.

Columns: Node Connection Status

The columns contained on the Node Status screen are described in the following table.

Column	Description
Status	Node status of last Entire System Server call, for example, active or not active.
Node	Node number or short node name.
Server Name	Logical (long) node name of the server.
Op.Sys.	Operating system on node.
Vers	Entire System Server version.
L	If marked: logon was made to the node. If no user ID is shown in the LogonUID column, AUTOLOG=YES is active on the node.
LogonUID	User ID used to log on to the node.
Checked	Time of last status check.
Usage	Usage access count for the node for the current user only.

Logoff Function

To log off a node

• Use the direct command LOGOFF as described in the Direct Commands documentation.