So I guess what you telling me, Tom, is that . . .
Though the XAUTOLOG's have no CMS synonyms and work in my AUTOLOG1 EXEC
without the ADDRESS COMMAND or even the CP prefix, it is not good form.
But the CP SET VSWITCH, being synonymous with the CMS SET command, does
not get recognized as a CP command even though it has the CP prefix.
The CP prefix is not enough.
It needs the ADDRESS COMMAND mode set in addition to the CP prefix.
Tom Huegel <tehue...@gmail.com>
Sent by: The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU>
11/02/2010 05:28 PM
Please respond to
The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU>
To
IBMVM@LISTSERV.UARK.EDU
cc
Subject
Re: No IPL VSWITCH Connectivity
ADDRESS COMMAND CP SET VSWITCH VSWITCH1 GRANT ZLINUX1
ADDRESS COMMAND CP SET VSWITCH VSWITCH1 GRANT ZLINUX2
ADDRESS COMMAND CP SET VSWITCH VSWITCH1 GRANT ZLINUX3
ADDRESS COMMAND CP SET VSWITCH VSWITCH1 GRANT ZLINXU4..
..
ADDRESS COMMAND CP XAUTOLOG DTCVSW1 SYNC < OK this does sort of wait..
ADDRESS COMMAND CP XAUTOLOG TCPIP
ADDRESS COMMAND CP XAUTOLOG ZLINUX1
ADDRESS COMMAND CP XAUTOLOG ZLINUX2
ADDRESS COMMAND CP XAUTOLOG ZLINUX3
ADDRESS COMMAND CP XAUTOLOG ZLINUX4
..
..
..
ADDRESS COMMAND CP XAUTOLOG VMRMSVM
ADDRESS COMMAND CP XAUTOLOG CMSRUN
ADDRESS COMMAND CP XAUTOLOG WAKEUP
On Tue, Nov 2, 2010 at 12:56 PM, George Henke/NYLIC <
george_he...@newyorklife.com> wrote:
Tom
Would you be so kind as to send me a copy of your AUTOLOG1 EXEC?
If I use it as a model, I should be ok.
Tom Huegel <tehue...@gmail.com>
Sent by: The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU>
11/02/2010 03:52 PM
Please respond to
The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU>
To
IBMVM@LISTSERV.UARK.EDU
cc
Subject
Re: No IPL VSWITCH Connectivity
I have my VSWITCHES defined in the SYSTEM CONFIG file and all of the
ADDRESS COMMAND CP SET VSWITCH VSWITCH1 GRANT vmuserid's in AUTOLOG1,
followed immediatly by XAUTOLOG LINUX1... LINUX2 ... LINUX etc.
SUSE 10 SP2 ..
I have no CP SLEEP commands and never had a problem.
For what it's worth I do not connect my TCPIP to a VSWITCH.
On Tue, Nov 2, 2010 at 11:02 AM, Martin, Terry R. (CMS/CTR) (CTR) <
terry.mar...@cms.hhs.gov> wrote:
Ok, my point was that you would not be able to connect the network and if
you can’t connect to the network having the VSWICTH defined does not mean
much at least not for me.
Thank You,
Terry Martin
Lockheed Martin - Citic
z/OS and z/VM Performance Tuning and Operating Systems Support
Office - 443 348-2102
Cell - 443 632-4191
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On
Behalf Of Miguel Delapaz
Sent: Tuesday, November 02, 2010 1:51 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: No IPL VSWITCH Connectivity
In that case, the guest should still be able to connect to the VSWITCH
without an issue. It just won't have access to the physical network. The
controller virtual machines have nothing to do with general VSWITCH
operation...they are simply there to manage the OSAs that may be attached
to the VSWITCH.
Regards,
Miguel Delapaz
z/VM Development
The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU> wrote on
11/02/2010 10:45:33 AM:
>
> Ok, they may be defined but try having a z/Linux guest connect to
> them before DTCVSW* is up!
>
> Thank You,
>
> Terry Martin
> Lockheed Martin - Citic
> z/OS and z/VM Performance Tuning and Operating Systems Support
> Office - 443 348-2102
> Cell - 443 632-4191
>
> From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu]
> On Behalf Of Riedel, Alexander
> Sent: Tuesday, November 02, 2010 1:33 PM
> To: IBMVM@LISTSERV.UARK.EDU
> Subject: AW: No IPL VSWITCH Connectivity
>
> Sorry Terry, but i think you are wrong. I define my 4 VSWITCHES all
> in the SYSTEM CONFIG and it works. At this time the TCPIP or DTCVSW*
> are definitely not started.
>
> Kind regards,
>
> Alexander Riedel
