Re: CSE: It's the little things that'll get ya...
See what happens when you don't catch enough Zs? RPN01 [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@listserv.uark.edu 10/08/2007 09:01 AM Please respond to The IBM z/VM Operating System IBMVM@listserv.uark.edu To IBMVM@listserv.uark.edu cc Subject Re: CSE: It's the little things that'll get ya... Actually, John caught it almost immediately; Early on in the process, an arbitrary decision (the most dangerous kind :-\ ) was made to change the test machine's names from zvmtestp / g to vmtestp / g. The xspool statements contained the old names, so the systems with the new names did not have CSE available. Two little Zs were sinking the boat. All the other occurrences had been changed, so changing these two brought CSE right up. Thanks for the help though -- .~.Robert P. Nix Mayo Foundation /V\RO-OE-5-55200 First Street SW /( )\ 507-284-0844 Rochester, MN 55905 ^^-^^ - In theory, theory and practice are the same, but in practice, theory and practice are different. On 10/7/07 8:54 PM, Les Geer (607-429-3580) [EMAIL PROTECTED] wrote: I'm in the process of building our z/VM 5.3 systems, and I think I'm down to the last hurdle I can't get CSE to fire up across PVM. The message I'm getting in PVM is: DVMISG864E CSE is not authorized The description of the message says that CSE is not available or not set up, but, to the best that I can tell, it should be. My test systems are VMTESTP and VMTESTG. Is the PVM machine defined as class b? Best Regards, Les Geer IBM z/VM and Linux Development - This e-mail and any attachments are intended only for the individual or company to which it is addressed and may contain information which is privileged, confidential and prohibited from disclosure or unauthorized use under applicable law. If you are not the intended recipient of this e-mail, you are hereby notified that any use, dissemination, or copying of this e-mail or the information contained in this e-mail is strictly prohibited by the sender. If you have received this transmission in error, please return the material received to the sender and delete all copies from your system.
Re: CSE: It's the little things that'll get ya...
Actually, John caught it almost immediately; Early on in the process, an arbitrary decision (the most dangerous kind :-\ ) was made to change the test machine's names from zvmtestp / g to vmtestp / g. The xspool statements contained the old names, so the systems with the new names did not have CSE available. Two little Zs were sinking the boat. All the other occurrences had been changed, so changing these two brought CSE right up. Thanks for the help though -- .~.Robert P. Nix Mayo Foundation /V\RO-OE-5-55200 First Street SW /( )\ 507-284-0844 Rochester, MN 55905 ^^-^^ - In theory, theory and practice are the same, but in practice, theory and practice are different. On 10/7/07 8:54 PM, Les Geer (607-429-3580) [EMAIL PROTECTED] wrote: I'm in the process of building our z/VM 5.3 systems, and I think I'm down to the last hurdle I can't get CSE to fire up across PVM. The message I'm getting in PVM is: DVMISG864E CSE is not authorized The description of the message says that CSE is not available or not set up, but, to the best that I can tell, it should be. My test systems are VMTESTP and VMTESTG. Is the PVM machine defined as class b? Best Regards, Les Geer IBM z/VM and Linux Development
CSE: It's the little things that'll get ya...
I'm in the process of building our z/VM 5.3 systems, and I think I'm down to the last hurdle I can't get CSE to fire up across PVM. The message I'm getting in PVM is: DVMISG864E CSE is not authorized The description of the message says that CSE is not available or not set up, but, to the best that I can tell, it should be. My test systems are VMTESTP and VMTESTG. Is the PVM machine defined as class b? Best Regards, Les Geer IBM z/VM and Linux Development
CSE: It's the little things that'll get ya...
I¹m in the process of building our z/VM 5.3 systems, and I think I¹m down to the last hurdle I can¹t get CSE to fire up across PVM. The message I¹m getting in PVM is: DVMISG864E CSE is not authorized The description of the message says that CSE is not available or not set up, but, to the best that I can tell, it should be. My test systems are VMTESTP and VMTESTG. The system config file (w/o comments or other non-contributing entries) contains: System_Identifier * 025A7E GRIZZLY System_Identifier * 045A6E POLAR System_Identifier * 01 VMTESTP System_Identifier * 02 VMTESTG System_Identifier_Default ZVMV5R30 GRIZZLY: Say System Grizzly, LPAR PENG, starting up... POLAR:Say System Polar, LPAR GENT, starting up... VMTESTG: Say System Sandbox GRIZZLY, starting up... VMTESTP: Say System Sandbox POLAR, starting up... ZVMV5R30: Say UNKNOWN CPUID, PLEASE CHECK CONFIGURATION POLAR: VMTESTP: ZVMV5R30: System_Residence, Checkpoint Volid 530RES From CYL 21 For 9 , Warmstart Volid 530RES From CYL 30 For 9 GRIZZLY: VMTESTG: System_Residence, Checkpoint Volid 530RES From CYL 1 For 9 , Warmstart Volid 530RES From CYL 10 For 9 POLAR: GRIZZLY: XSPOOL_SYSTEM Slot 1 POLAR , Communications_Userid PVM Share_Spool yes POLAR: GRIZZLY: XSPOOL_SYSTEM Slot 2 GRIZZLY , Communications_Userid PVM Share_Spool YES POLAR: GRIZZLY: XSPOOL_SYSTEM Slot 3 RESERVED POLAR: GRIZZLY: XSPOOL_SYSTEM Slot 4 RESERVED VMTESTP: VMTESTG: XSPOOL_SYSTEM Slot 1 RESERVED VMTESTP: VMTESTG: XSPOOL_SYSTEM Slot 2 RESERVED VMTESTP: VMTESTG: XSPOOL_SYSTEM SLOT 3 ZVMTESTP , Communications_Userid PVM Share_Spool yes VMTESTP: VMTESTG: XSPOOL_SYSTEM Slot 4 ZVMTESTG , Communications_Userid PVM Share_Spool YES XSPOOL_XLIST_INPUT JANUS GCS PVM TCPIP RSCS OPERATOR FTPSERVE XSPOOL_XLIST_INPUT PERFSVM EREP DISKACNT OPERSYMP OPERATNS XSPOOL_XLIST_INPUT DTCVSW1 DTCVSW2 XSPOOL_XLIST_OUTPUT JANUS GCS PVM TCPIP RSCS OPERATOR FTPSERVE XSPOOL_XLIST_OUTPUT PERFSVM EREP DISKACNT OPERSYMP OPERATNS XSPOOL_XLIST_OUTPUT DTCVSW1 DTCVSW2 VMTESTP: CP_Owned Slot 2 530SPL own VMTESTP: CP_Owned Slot 3 530PAG VMTESTP: CP_Owned Slot 4 RESERVED VMTESTP: CP_Owned Slot 5 RESERVED VMTESTP: CP_Owned Slot 6 RESERVED VMTESTP: CP_Owned Slot 7 RESERVED VMTESTP: CP_Owned Slot 8 RESERVED VMTESTP: CP_Owned Slot 9 RESERVED VMTESTP: CP_Owned Slot 10 53GSPL shared VMTESTP: CP_Owned Slot 11 RESERVED VMTESTP: CP_Owned Slot 12 RESERVED VMTESTP: CP_Owned Slot 13 RESERVED VMTESTP: CP_Owned Slot 14 RESERVED VMTESTP: CP_Owned Slot 15 RESERVED VMTESTP: CP_Owned Slot 16 RESERVED VMTESTP: CP_Owned Slot 17 RESERVED VMTESTP: CP_Owned Slot 18 RESERVED VMTESTP: CP_Owned Slot 19 RESERVED VMTESTP: CP_Owned Slot 20 RESERVED VMTESTG: CP_Owned Slot 2 530SPL shared VMTESTG: CP_Owned Slot 3 RESERVED VMTESTG: CP_Owned Slot 4 RESERVED VMTESTG: CP_Owned Slot 5 RESERVED VMTESTG: CP_Owned Slot 6 RESERVED VMTESTG: CP_Owned Slot 7 RESERVED VMTESTG: CP_Owned Slot 8 RESERVED VMTESTG: CP_Owned Slot 9 RESERVED VMTESTG: CP_Owned Slot 10 53GSPL own VMTESTG: CP_Owned Slot 11 53GPAG VMTESTG: CP_Owned Slot 12 RESERVED VMTESTG: CP_Owned Slot 13 RESERVED VMTESTG: CP_Owned Slot 14 RESERVED VMTESTG: CP_Owned Slot 15 RESERVED VMTESTG: CP_Owned Slot 16 RESERVED VMTESTG: CP_Owned Slot 17 RESERVED VMTESTG: CP_Owned Slot 18 RESERVED VMTESTG: CP_Owned Slot 19 RESERVED VMTESTG: CP_Owned Slot 20 RESERVED - The only difference I see between the vmtest setup and the production setup is in the xspool_system list, where the test systems are in slots 3 and 4, reserving 1 and 2. Both RSCS and PVM are set up with the local and remote names matching the system names, VMTESTP and VMTESTG. Both RSCS and PVM link up w/o problem, other than the CSE message above. So for the brave among you... What am I overlooking? -- .~.Robert P. Nix Mayo Foundation /V\RO-OE-5-55 200 First Street SW / ( ) \ 507-284-0844 Rochester, MN 55905 ^^-^^ - In theory, theory and practice are the same, but ³Join the story... Ride Ural.² in practice, theory and practice are different.
