Example of ADMIN and VC dialog via $VMCONS

This example shows the operation of the whole VM2000 system and the VM2 by the VM2000 administrator (ADMIN dialog with the monitor VM via $VMCONS) on an SU /390.

The guest system on the second VM is booted and started via a separate OMNIS connection in the VC dialog.

For an example of the ADMIN dialog via a privileged user task, see "Example of an ADMIN dialog from a user task".

Tracer listing

@: OMS0001 USER IS CONNECTED TO OMNIS (TERMINAL=(STATFD70/MCH9700D);
   TID=   474)
@: OMS0002 OMNIS VERSION <ver> READY ——————————————————————————————————  (1)
@:option logging=yes ——————————————————————————————————————————————————  (2)
@:option input-logging=send,output-logging=send
@:option pac=std ——————————————————————————————————————————————————————  (3)
@:option break-key=1,call-inf=yes,call-key=2 ——————————————————————————  (4)
@:opncon vm01,typ=dcam,ptnname=$vmcons,proname=d021ze01,appname=OMS111   (5)
@: OMS0012 'OPNCON' COMMAND ACCEPTED (PAC=VM01, PID=   477,
           APPNAME=(OMS111/D021ZE01))
@: OMS0014 'OPNCON' COMMAND EXECUTED SUCCESSFULLY
           (PARTNER=($VMCONS/D021ZE01), PAC=VM01) —————————————————————  (6)

vm01:/begin-vm-dialog vm-id=1,type=*admin(output-prefix=*no)  —————————  (7)
VM01: % VMS3000 VM2000 COMMAND /BEGIN-VM-DIALOG FOR
                VIRTUAL MACHINE (1,MONITOR) PROCESSED SUCCESSFULLY
VM01: % NBR0740 COMMAND COMPLETED 'BEGIN-VM-DIALOG';
                (RESULT: SC2=000, SC1=000, MC=CMD0001); DATE: <date> ——  (8)
/create-vm memory-size=512,vm-name=system2,
           cpu-quota=30,password=c'sys2' ——————————————————————————————  (9)
VM01: % VMS3050 VIRTUAL MACHINE (2,SYSTEM2) CREATED
VM01: % VMS4615 VIRTUAL MACHINE (2,SYSTEM2) ASSIGNED TO CPU POOL '*STDPOOL'
VM01: % VMS3000 VM2000 COMMAND /CREATE-VM FOR
                VIRTUAL MACHINE (2,SYSTEM2) PROCESSED SUCCESSFULLY
VM01: % NBR0740 COMMAND COMPLETED 'CREATE-VM';
                (RESULT: SC2=000, SC1=000, MC=CMD0001); DATE: <date>
/add-vm-devices vm-id=system2,
     units=*pubset-devices(pubset=*by-pubres-device(unit=fc1a)) ——————— (10)
VM01: % VMS4005 DEVICE 'FC1A' ASSIGNED TO VIRTUAL MACHINE (2,SYSTEM2)
VM01: % VMS4005 DEVICE 'FC1B' ASSIGNED TO VIRTUAL MACHINE (2,SYSTEM2)
VM01: % VMS4220 PUBSET '4IVK' WITH PUBRES DEVICE 'FC1A'
                ASSIGNED TO VM (2,SYSTEM2)
VM01: % VMS3000 VM2000 COMMAND /ADD-VM-DEVICES FOR
                VIRTUAL MACHINE (2,SYSTEM2) PROCESSED SUCCESSFULLY
VM01: % NBR0740 COMMAND COMPLETED 'ADD-VM-DEVICES';
                (RESULT: SC2=000, SC1=000, MC=CMD0001); DATE: <date>
/add-vm-devices units=(cc),type=*vc,vm-id=system2 ————————————————————— (11)
VM01: % VMS4005 DEVICE 'CC' ASSIGNED TO VIRTUAL MACHINE (2,SYSTEM2)
                 (TYPE=VC)
VM01: % VMS3000 VM2000 COMMAND /ADD-VM-DEVICES FOR
                VIRTUAL MACHINE (2,SYSTEM2) PROCESSED SUCCESSFULLY
VM01: % NBR0740 COMMAND COMPLETED 'ADD-VM-DEVICES';
                (RESULT: SC2=000, SC1=000, MC=CMD0001); DATE: <date>
@:/opncon gs02,typ=ucon,ptnname=$vmcons,proname=D021ZE01,appname=OMS112 (12)
@: OMS0012 'OPNCON' COMMAND ACCEPTED (PAC=GS02, PID=   487,
           APPNAME=(OMS112/D021ZE01))
@: OMS0014 'OPNCON' COMMAND EXECUTED SUCCESSFULLY
           (PARTNER=($VMCONS/D021ZE01), PAC=GS02)




gs02:/begin-vm-dialog vm-id=system2,password=c'sys2',
                      type=*vc(output-prefix=*no)  ———————————————————— (13)
VM01: % VMS1033 PARTNER 'OMS112   D016ZE04' HAS STARTED A VC DIALOG WITH
                            VIRTUAL MACHINE (2,SYSTEM2) ——————————————— (14)
      % VMS3000 VM2000 COMMAND /BEGIN-VM-DIALOG FOR 
                VIRTUAL MACHINE (2,SYSTEM2) PROCESSED SUCCESSFULLY
      % NBR0740 COMMAND COMPLETED 'BEGIN-VM-DIALOG';
                (RESULT: SC2=000, SC1=000, MC=CMD0001); DATE: <date>
vm01:/start-vm ipl-unit=fc1a,vm-id=system2,information-byte=*dialog ——— (15)
VM01: % VMS2023 CPU 00 OF VIRTUAL MACHINE (2,SYSTEM2) STARTED
VM01: % VMS3000 VM2000 COMMAND /START-VM FOR
                VIRTUAL MACHINE (2,SYSTEM2) PROCESSED SUCCESSFULLY
VM01: % NBR0740 COMMAND COMPLETED 'START-VM';
                (RESULT: SC2=000, SC1=000, MC=CMD0001); DATE: <date>
GS02: %P.NSI00E3 IPL-REPS READ: 2; EXECUTED: 2
GS02: %P.NSI1100 IPL DEVICE = 4IVK.0; IPL PATH = FC1A (MN=FC1A)
GS02: %P.NSI1106 *** BS2000 DIALOGUE STARTUP *** —————————————————————— (16)
GS02: ?P.NSI1110 ENTER OPTIONS OR EOT.
         REPLY (UNLOCK,TEST,ALLDISK,DRV-SELECT,CREATE-DRV,IPL-CONF)
gs02:p. ——————————————————————————————————————————————————————————————— (17)
GS02: %P.NSI3135 IPL DISK-SETUP READ FROM IPL-CONF PREPARED <date> <time>
GS02: %P.NSI1143 002 PUBVOLS OF HOME-PVS 4IVK WITH SYSID 186 ONLINE
GS02: %P.NSI1145 4IVK.0 <date> <time> ON FC1A
GS02: %P.NSI1145 4IVK.1 <date> <time> ON FC1B
GS02: %P.NSI1153 STATE OF PROCESSORS ONLINE:
GS02: %P.NSI1155 CPU 00 ONLINE, ATTACHED (IPL CPU)
GS02: %P.NSI1163 LOCAL DATE = <date>, TIME = <time> FROM SVP
GS02: %P.NSI1180 LOAD ADDRESS OF SYSPRG.STRT.<ver> = 0076A000
GS02: %P.NSI00E6 FILE SYSREP.STRT.<ver> IS USED AS REP FILENAME
GS02: ?P.NSI0050 SPECIFY PARAM FILE OR DEVICE.
         REPLY ( EOT (USE STANDARD FILE);FN=FILENAME,(VOL=VSN);CONS;END )
... ——————————————————————————————————————————————————————————————————— (18)
gs02:vm00:/end-vm-dialog vm-id=system2  ——————————————————————————————— (19)
VM01: % VMS1032 PARTNER HAS TERMINATED A VC DIALOG WITH
                VIRTUAL MACHINE (2,SYSTEM2)———————————————————————————— (20)
      % VMS3000 VM2000 COMMAND /END-VM-DIALOG FOR
                VIRTUAL MACHINE (2,SYSTEM2) PROCESSED SUCCESSFULLY
      % NBR0740 COMMAND COMPLETED 'END-VM-DIALOG';
                (RESULT: SC2=000, SC1=000, MC=CMD0001); DATE: <date>
@: OMS0006 CONNECTION TO PARTNER ($VMCONS/D021ZE01) LOST
           (PAC=GS02; CODE=00000000) —————————————————————————————————— (21)
vm01:/end-vm-dialog  —————————————————————————————————————————————————— (22)
VM01: % VMS3000 VM2000 COMMAND /END-VM-DIALOG FOR
                VIRTUAL MACHINE (1,MONITOR) PROCESSED SUCCESSFULLY
VM01: % NBR0740 COMMAND COMPLETED 'END-VM-DIALOG';
                (RESULT: SC2=000, SC1=000, MC=CMD0001); DATE: <date>
@: OMS0006 CONNECTION TO PARTNER ($VMCONS/D021ZE01) LOST
           (PAC=VM01;CODE=00000000)

------------------------------------------------------------------------------------------------------------------

(1)	Via a terminal emulation the connection is established to OMNIS.
(2)	The OMNIS logging is activated.
(3)	The standard output of the OMNIS connection name (<pac>:) is chosen.
(4)	The “K2 function“ is set up in OMNIS.
(5)	The connection to $VMCONS is established via OMNIS with the connection name VM01. The password for access to $VMCONS is not set up.
(6)	The connection was established successfully. $VMCONS sends the welcome screen.
(7)	The VM2000 administrator opens the ADMIN dialog with the monitor VM. The OMNIS connection name VM01 must be specified here for assignment of the input to the OMNIS connection. The slash (/) to introduce a command must always be specified. Output of the VM prefix is suppressed since in this example a separate connection to $VMCONS with an OMNIS connection of the same name is set up for every dialog under OMNIS.
(8)	The standardized command termination message is output.
(9)	A mono-VM is initialized by the VM2000 administrator. The VM receives the VM name SYSTEM2. The password SYS2 is defined for dialog access. The OMNIS connection name need no longer be specified, as it was set with the last input.
(10)	The VM2000 administrator assigns VM2 the disk device(s) of the home pubset by specifying the pubres device. The pubset is detected by VM2000.
(11)	The VM2000 administrator assigns a virtual console to VM2.
(12)	A further connection to $VMCONS is established via OMNIS with TYP=UCON and connection name GS02. This connection could also be established from a separate terminal to separate the operating levels. The prefix @ must be specified, as the statement is directed to OMNIS.
(13)	Only the VC dialog is opened. Output of the GS prefix is suppressed. The OMNIS connection name GS02 must be specified here for assignment of the input to the OMNIS connection.
(14)	The VM2000 administrator is informed that the connection has been established.
(15)	The VM2000 administrator starts the guest system on VM2 (change of the OMNIS connection name). The pubres device of the home pubset is selected as the IPL unit. A dialog startup is to be performed. Operation of the guest system is done in the VC dialog.
(16)	Outputs of the guest system appear in the VC dialog (OMNIS connection name GS02).
(17)	Inputs to the guest system (change of the OMNIS connection name).
(18)	The guest system continues to run.
(19)	The VC dialog is terminated. The OMNIS connection name GS02 would only have to be specified if the OMNIS connection were changed. Specification of VM00 as a replacement prefix is necessary, as only a VC dialog (TYPE=*VC) is carried out via the OMNIS connection GS02 and so no VM prefix is defined. If an ADMIN dialog (also) were conducted via this connection, its VM prefix would have to be specified.
(20)	The VM2000 administrator is informed that the connection has been lost.
(21)	OMNIS reports the lost connection to $VMCONS.
(22)	The VM2000 administrator terminates the ADMIN dialog with the monitor VM.