The Operator Interface

The Operator Interface enables you to issue Sterling Connect:Direct® for z/OS® commands from a z/OS console using a MODIFY command.

Access the Operator Interface after Sterling Connect:Direct initializes if you specify the initialization parameters MCS.CLIST and MCS.SIGNON.

Following is the syntax for the MCS.CLIST and MCS.SIGNON initialization parameters:

MCS.CLIST=console operator's CLIST library (dsn)
MCS.SIGNON=(SIGNON USERID=(userid,password)        		-
	    CASE=YES | NO	-
           NETMAP=network map file name)

An automatic signon is issued after the first Sterling Connect:Direct CLIST is invoked using the information in MCS.SIGNON. This session is active until you submit a CLIST that contains a Sterling Connect:Direct SIGNOFF command.

Note: The NETMAP used by the MCS.SIGNON must be the same as the NETDSN in the INITPARMs for this DTF. If a different NETMAP is used, LOCAL.NODE information from that NETMAP will be used for a SIGNON, and the commands to this DTF will be executed on the other DTF if it is running.

You can create easy to remember customized Sterling Connect:Direct commands with the Operator Interface through a CLIST-type facility. The software supports symbolic substitution and CLIST-type parameters allowing you to alter Sterling Connect:Direct commands without changing the CLIST.

In a Sterling Connect:Direct/Plex, if you issue a console operator command to a Sterling Connect:Direct/Server, the console interface actually signs on to the Sterling Connect:Direct/Manager. As a result, any commands issued to Sterling Connect:Direct/Server are actually issued to the Sterling Connect:Direct/Manager, which is the only Sterling Connect:Direct/Plex member that accepts operator commands.