Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

ROBAR-CL as an authorized user program

ROBAR-CL is a BCAM/DCAM application which connects itself to $CONSOLE when it starts and then identifies itself to the operating system as an authorized user program. The application then executes operator functions in accordance with the routing codes assigned to it and thus functions as a logical console.
Further information on authorized user programs is provided in the “Introduction to System Administration” [2].

You can use static or dynamic authorization names for ROBAR-CL. Assign at least the routing codes *, T, E, N, G, U and A to the application.

Static authorization name

A static authorization name (e.g. CON1) is defined in the startup parameter service, parameter set OPR. Normally its routing codes are also assigned to it at the same time. The authorization name must be unique and cannot be used by any other application. The operating system must be restarted when a newly defined authorization name is to be used.

Supply the following parameters with values in the ROBAR-CL start file:

UCONID

Static authorization name (default value: CON1)

UCONPWD

Password for UCONID

The OPEROLE, OPERID and OPIDPWD parameters can contain any values. They are not evaluated.

Dynamic authorization name

You can use any operator identification (operator ID) and operator role for ROBAR-CL. The operator ID requires operator authorization. Assign at least the routing codes *, T, E, N, G, U and A to the operator role.

Supply the following parameters with values in the ROBAR-CL start file:

UCONID

*NONE

UCONPWD

*NONE (the parameter has no meaning in this case)

OPERID

Operator ID (default value: TSOS)

OPEROLE

Operator role which is requested for the operator ID (default value: SYSADM)

OPIDPWD

Password for the operator ID (default value: *NONE)


The dynamic authorization name (@001 through @192) is assigned and managed by the operating system when the application is started.

If ROBAR-CL is not assigned the operator role when the application starts (message NBR0984), it terminates and SYSOUT message ROB2226 is issued.

If an incorrect OPIDPWD password is entered when the application starts, ROBAR-CL terminates and SYSOUT message ROB2225 (NBR0717 on the console) is issued.

 

You are recommended to call the ROBAR-CL start procedure via a procedure which requires hidden entry of the OPIDPWD password, e.g.:

/DECLARE-PARAMETER NAME=PASS(INIT=*PROMPT  -
/(PROMPT-STRING='OPID-PASS:',DEFAULT-VALUE=*NONE,SECRET-INPUT=*YES))
...
/ENTER-PROC $SYSMAREN.SYSPRC.ROBAR-CL.<ver>, -
/PROC-PAR=(...,OPIDPWD=&PASS)