Your Browser is not longer supported

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

{{viewport.spaceProperty.prod}}

Connections with generated authorization names

&pagelevel(4)&pagelevel

A static authorization name can be generated in the startup parameter service, OPR parameter set, using the SET-CODE or ADD-CMD-ENTRY statements, see section "Configuration and suppressing the output of messages at consoles (OPR)". The SET-CODE statement defines the assignment of routing codes to a $CONSOLE application with this authorization name. The assignment can be changed with the ASR commands.

The connection to an authorization name thus created is realized by specifying the following parameters in the connection message:

[NAME=]<name 4..4> 
[,[PASSWORD=]C'password 1..8'] 
[,[PROTVERS=]Vn] 
[,[DISCON=]{YES/NO}]

NAME=<name 4..4>
The specified name must correspond to one of the authorization names set up in the setup parameter service with the SET-CODE or ADD-CMD-ENTRY statements.
In addition, an identically named user ID must exist in the user catalog of the home pubset. The ID should be password protected. It may also be locked (LOCK-USER command). It does not require SECOS access authorizations. Access takes place in the UCON access class.

PASSWORD=<password 1..8>
A password protects the access to $CONSOLE with this authorization name. The password entered for the authorization name in the user catalog must be specified.
A hexadecimal password is not permitted. The password may be a maximum of 8 characters in length.

PROTVERS und DISCON
See the description on "Format of the connection message for dynamic authorization names" in section "Connections with dynamic authorization names".