Providing an ID for the operating function

If the operating functionality is to be provided from physical consoles (if the operator logon is activated), $CONSOLE applications with dynamic authorization names and user tasks, the preparations described below must be made. For the existing system user ID SYSOPR to be used, only the creation and assignment of operator roles is necessary.

Under the TSOS ID

• Set up an ID:
/ADD-USER USER-ID=OPEROPER, LOGON-PASSWORD=C'12345678', ACCOUNT=account

• If the chargeable product SECOS is in use, for $CONSOLE applications with dynamic authorization names it may be possible to define extended access protection using the following command.

  /MODIFY-LOGON-PROTECTION USER-ID=OPEROPER, ...,
                           OPERATOR-ACCESS-TERM= ..., 
                           OPERATOR-ACCESS-PROG= ...
  

Under the SYSPRIV ID

• Assign the OPERATING privilege (not always necessary for $CONSOLE applications):
/SET-PRIVILEGE PRIVILEGE=OPERATING, USER-ID=OPEROPER

• Set up operator roles:
/CREATE-OPERATOR-ROLE OPERATOR-ROLE=OPERROLE, ROUTING-CODES=<list>

• Assign the operator roles to the ID:
/MODIFY-OPERATOR-ATTRIBUTES USER-ID=OPEROPER,ADD-OPERATOR-ROLE=OPERROLE

• If desired, additional assignment of operator roles to the system operator's user ID:
  

  /MODIFY-OPERATOR-ATTRIBUTES USER-ID=SYSOPR,ADD-OPERATOR-ROLE=OPERROLE

Following these preparations and the entry of the SET-LOGON-PARAMETERS command with user ID, account number and password, it is possible for an operator, taking account of any special conditions, to perform operation from a physical console, a $CONSOLE application with dynamic authorization name or a user task. The operator requests the routing code via the REQUEST-OPERATOR-ROLE command.