At [VMNODE] cmd [command] [option]
Within the z/VM Cluster you're able to execute commands on the other SSI members. In this example the current node is 'pokdev62'. There's defined a linux guest named 'linux157' which we'd like to IPL on the SSI member 'pokdevtst62'. Query first the names. Then IPL the 'linux157' using the appropriate command.
LINUX122 - SSI , VMSERVP - SSI
FTPSERVE - DSC , TCPIP - DSC , LNXADMIN - DSC , DTCVSW2 - DSC
DTCVSW1 - DSC , VMSERVR - DSC , VMSERVU - DSC , VMSERVS - DSC
OPERSYMP - DSC , DISKACNT - DSC , EREP - DSC , OPERATOR - DSC
MAINT -L0004
VSM - TCPIP
Ready; T=0.01/0.01 10:01:35
==> at poktst62 cmd xautolog linux157 i 100
Command accepted
Ready; T=0.01/0.01 10:01:56
After querying the names again we could recognize that 'linux157' is running within the cluster -> LINUX157 - SSI.
LINUX157 - SSI , LINUX122 - SSI , VMSERVP - SSI
FTPSERVE - DSC , TCPIP - DSC , LNXADMIN - DSC , DTCVSW2 - DSC
DTCVSW1 - DSC , VMSERVR - DSC , VMSERVU - DSC , VMSERVS - DSC
OPERSYMP - DSC , DISKACNT - DSC , EREP - DSC , OPERATOR - DSC
MAINT -L0004
VSM - TCPIP
Ready; T=0.01/0.01 10:02:20
Just for demonstration a login to 'linux157' to check if it's running.
15:01:35 libtsocks(25205): IP (0.0.0.0) & 15:01:35 libtsocks(25205): SUBNET (210.127.0.0) != IP on line 6 in configuration file, ignored
Password:
Last login: Thu Mar 21 15:03:33 2013 from 10.78.1.10
root:10.199.10.106~ #
Fine, it's up and running. Of course we're also able to shutdown the linuxguest on another SSI-member using the similar command structure as before.
Ready; T=0.01/0.01 10:07:09
The post Execute commands on the other SSI members (z/VM 6.2/6.3) appeared first on Linux on the mainframe.
