Add usercodes to the USERDATAFILE file on each MCP host system to enable the following activities:
Usercode-1: Used for automatic log-on (auto-logon) of Operations Sentinel Console terminal emulation sessions in remote ODT mode. See Section 3 for a description of the AUTO_LOGON_USERCODE parameter in the configuration file. Usercode-1 is the same usercode you use to set up ODT terminal emulation sessions during Operations Sentinel configuration. You must not use usercodes assigned for this purpose for any other purpose, because the log-on event causes the user terminal to go into remote ODT mode with the automatic display mode (ADM) active. SPOADM is the default usercode-1. If you use a different value, update AUTO_LOGON_USERCODE in the configuration file as described in Section 3. This usercode should have privileged status and system user status.
Usercode-2: Used for running the interface software program. This usercode should have privileged status and system user status. Usercode-2 must be the usercode that you specify during the installation of the interface software. See Section 3 for a description of how to install the software.
Usercode-3: User for security validation of the port connection with the Operations Sentinel server. This usercode should have privileged status and system user status. Usercode-3 is specified in the SP-AMS database on the Operations Sentinel server and is sent to the interface software after the initial connection. It is necessary to validate that the device connected to the interface port is an authorized Operations Sentinel server. The default value for usercode-3 is SPO. If you use a different value, update your SP-AMS databases accordingly.
For usercode-1: USER SPOADM; << Examined USER = SPOADM MAXPW = 1 MINPW = 1 PASSWORD = ?------------ PU SYSTEMUSER FAMILY DISK = DISK ONLY For usercode-2 and usercode-3: USER SPO; << Examined USER = SPO MAXPW = 1 MINPW = 1 PASSWORD = ?------------ PU SYSTEMUSER FAMILY DISK = DISK ONLY CANDEGETMSG
Notes:
Usercode-1 must be different from usercode-2 and usercode-3.
Usercode-2 and usercode-3 can be the same.
It is recommended that usercode-3 have privileged status and system user status so that the port connection is qualified to run with the same privileges as the interface software program. The default configuration file supplied with the interface software requires that usercode-3 have privileged status and system user status.
If, however, your site does not allow the utilization of privileged usercodes outside the MCP complex, a configuration option is available whereby usercode-3 need only be qualified as a valid usercode; no particular privileges are required. See Section 3.