The OPERATING privilege is by default assigned to the SYSOPR user ID. The default allocation of privileges can only be changed with SECOS.
Operating is thus possible from both physical and virtual consoles and from user tasks with the OPERATING privilege.
The command authorization concept via authorization codes remains unchanged for consoles. For user tasks it is now irrelevant (exception: commands which are processed via the UCON task and to whom the authorization code $ is assigned see also "Command definition").
Certain commands that are usually always available to operators may be locked in the system syntax file by systems support (see also the “SDF-A” manual [44]).
A task with the OPERATING privilege offers most operator commands, including those that could previously only be entered via the console. Among the commands not offered are CONSOLE, ASR, RUN and AGOGO.
Each operator command entered at a console is managed by an OPR task that identifies itself to SDF and to the system as privileged when a command is executed. Before it is processed, each operator request (command passed by the OPR task to SDF for syntax and privilege verification) is checked to see whether the caller has the necessary OPERATING privilege.
The OPR task of a physical console (with NBCONOPI=NO) and a virtual console always has the OPERATING privilege.
The operator can enter commands via the console. The abbreviated form, if any, is given in the command syntax. For the structure of the command entries and messages, see chapter "Operator functions" and chapter "Automation of operator functions".
The commands are described in the “Commands” manual [27]. The BCAM commands for the operator (e.g. BCACT, DCSTART) are described in the “BCAM” manual [4].
Under certain conditions the operator may also use some system administration commands and user commands (see section "System administration functions performed by the operator").