Administration dialogs from privileged user tasks

Operating a VM in the administration dialog (ADMIN dialog) from a privileged user task involves the following steps:

>	Begin the BS2000 dialog under a user task with the appropriate privilege in the monitor system: /SET-LOGON-PARAMETERS ...
>	Open the ADMIN dialog using the VM2000 command /BEGIN-VM-DIALOG VM-IDENTIFICATION=...,PASSWORD=...,TYPE=*STD/*ADMIN(...) For the ADMIN dialog with the monitor VM, the VM2000-ADMINISTRATION privilege or the OPERATING privilege is required. If access to the VM is protected by a password, this must be specified when the dialog is opened. After a successful /BEGIN-VM-DIALOG, the VM2000 administrator is informed of the task sequence number (TSN) of this ADMIN dialog (message VMS1013). The exchange of messages in the ADMIN dialog is also logged with this TSN in the CONSLOG file of the monitor system.
>	Enter VM2000 commands to operate the VM (see "Operating a VM" and "VM2000 commands") or the VM2000 system as a whole (see "Operating the whole VM2000 system" and "VM2000 commands"). BS2000 commands can also be entered.
>	Terminate the ADMIN dialog with one of the VM2000 commands /END-VM-DIALOG VM-IDENTIFICATION=... /DELETE-VM VM-IDENTIFICATION=... If /DELETE-VM is specified, VM2000 terminates all ADMIN dialogs with the VM and all VC dialogs with the guest system on the VM.

For one user task, only one ADMIN dialog can be carried out at a time. For each VM up to 15 ADMIN dialogs from different user tasks can be conducted at the same time. Also, for each VM one ADMIN dialog can be conducted via $VMCONS.

Logging

The VM2000 commands, outputs and messages for operating VM2000 and the VMs are logged in the CONSLOG file of the monitor system (see the “Introduction to System Administration” [2]).
The command inputs and message outputs belonging to an ADMIN dialog via a user task can be determined from the TSN, which is stored in the sender/recipient field of the CONSLOG entry. The VM2000 administrator is informed of the TSN at /BEGIN-VM-DIALOG via the message VMS1013.

In addition, the progress of the user task can be logged in the usual way to SYSLST (/SET-LOGON-PARAMETERS ...,LOGGING=*PAR(LISTING=*YES)).

Using the event stream service (ESS)

The event stream of VM2000 is the system-dependent, asynchronous part of the data stream of a VM2000 or VM administrator dialog. It includes the periodic outputs of /SHOW-VM-STATUS and the asynchronous messages from VM2000, to which the administrator may have to respond.

The following asynchronous messages of VM2000 are normally received in the user event stream allocated to the privileged user task.

VMS0017   VMS0025   VMS0026   VMS0027   VMS1012   VMS1013   VMS1016   VMS1032
VMS1033   VMS1051   VMS1531   VMS1601   VMS1602   VMS2011   VMS2012   VMS2014
VMS2016   VMS2021   VMS2023   VMS2033   VMS2036   VMS2037   VMS2050   VMS2051
VMS2052   VMS2053   VMS2059   VMS2320   VMS2411 - VMS2422   VMS2424   VMS2425
VMS2430 - VMS2434   VMS2440   VMS2441   VMS2450 - VMS2452   VMS4910   VMS4912
VMS4005   VMS4009   VMS4065   VMS4066   VMS4094   VMS4095   VMS4191   VMS4192
VMS4224   VMS4227   VMS4244   VMS4245   VMS4342   VMS4344   VMS4510   VMS4511
VMS4514   VMS4551   VMS4552   VMS4553   VMS4554   VMS4555   VMS4556   VMS4557
VMS4558   VMS4559   VMS4560   VMS4561   VMS4562   VMS4563   VMS4564   VMS4620
VMS4621   VMS6002   VMS6003   VMS6018   VMS6020   VMS6021   VMS6023   VMS6094

With administration under a privileged user ID, you can receive the asynchronous messages for the relevant administrator with the help of the event stream service (ESS) and you can use the presentation functions of ESS.

The operating functions of ESS are also available if you have the OPERATING privilege. The ESS presentation functions are shown in the command description of /SHOW-SYSEVENT-LOG.

Recommendation

Use the event stream service to receive the event stream of VM2000. For examples of the structure, see the “Introduction to System Administration” [2], chapter “Operator functions”.

If you do not use the event stream service, the asynchronous messages will be output to SYSOUT at the next non-empty user input.

Even if you use the event stream service, (additional) output to SYSOUT is enabled (default). Output to SYSOUT can be suppressed by means of the task-specific command /MODIFY-MSG-OPTIONS SYSTEM-MSG=*NO.