Re: Virtual Lock File
Another way would be to define a VDISK in the PROFILE EXEC of the VDISKS machine (instead of VM directory definition) and check the return code of CP DEFINE (if it's 0, initialise it). I forgot to say that in this case you would have to add 'CP LINK VDISKS 222 vaddr MW' a second or two after 'CP XAUTOLOG VDISKS' in VSE machines' PROFILE EXECs. Also, you may choose to add COMMAND XAUTOLOG VDISKS directory control statement for all VSE machines, which would work even if you IPL VSE straight from directory by using IPL sysres_addr directory control statement, and then you don't even have to worry about VSE machines' privilege class to be able to run XAUTOLOG CP command. Ivica Brodaric BNZ
Re: Virtual Lock File
Thank you to all who responded. Many different and interesting solutions to choose from. I decided to LINK to the VDISKS virtual disk from two Service Machines that are always running. Thank you, Scott From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Kris Buelens Sent: Tuesday, March 08, 2011 2:39 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Virtual Lock File Each of our VM systems had a minidisk on a shared pack (with CSE) that we used to test of the target VM system was still up. To assure there was always some LINK to this minidisk, we had it linked by quite a few service machines (VMUTIL, RSCS, Operator, etc). The chance that all of these service machines would be logged off at the same time were pretty small. You could do something similar. 2011/3/8 Frank M. Ramaekers framaek...@ailife.com I simply use this (at the end of the PROFILE EXEC for the user that owns the VDISKS): Do forever Say Staying alive, staying alive(99 hours)... CP SLEEP 99 HRS End Frank M. Ramaekers Jr. -Original Message- From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Wandschneider, Scott Sent: Tuesday, March 08, 2011 11:58 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Virtual Lock File I have a SVM called VDISKS the creates and initializes a virtual lock file for four VSE guest to use. After a short time, VDISKS is logged off by the system. All is fine if at least one VSE remains logged on, however if all are logged off the virtual lock file goes away also. How can I keep VDISKS from being logged off by the system? * * * Top of File * * * USER VDISKS $SECRET$ 4M 4M BG 90 *NAME: VIRTUAL_DISKS ACCOUNT SYSTEMS SUPPORT COMMAND SET RUN ON IPL CMS MACH ESA XAUTOLOG AUTOLOG1 MAINT CONSOLE 0009 3215 T OPERATOR SPOOL 000C 2540 READER * SPOOL 000D 2540 PUNCH A SPOOL 000E 1403 A LINK MAINT 0190 0190 RR LINK MAINT 019D 019D RR LINK MAINT 019E 019E RR MDISK 0191 3390 499 001 PKSCMS MR ALL WRITE MULTIPLE MDISK 0222 FB-512 V-DISK 6208 MWV ALL *DVHOPT LNK0 LOG1 RCM1 SMS0 NPW1 LNGAMENG PWC20101121 CRCc PROFILE EXEC Z1 V 130 Trunc=130 Size=14 |...+1+2+3+4.. 0 * * * Top of File * * * 1 /* */ 2 'CP SPOOL CONSOLE START MAINT CLASS M' 3 Trace I 4 'EXECIO * CP (STRING Q' USERID() 5 PULL @RESPONSE 6 PARSE VAR @RESPONSE @USERID . @TERMID 7 IF @TERMID = 'DSC' THEN DO 8EXEC INITVDSK 9SLEEP 05 SEC 00010'CP SPOOL CONSOLE CLOSE' 00011EXIT 00012 END 00013 SET PF12 RETRIEVE 00014 EXIT 00015 * * * End of File * * * INITVDSK EXEC Z1 V 130 Trunc=130 Size=8 |...+1+2+3+4 0 * * * Top of File * * * 1 /* EXEC TO INITIALIZE ALL VDISKS*/ 2 Trace I 3 ERASE DSFOUT OUTPUT A 4 PUSH 'DSFOUT' 5 PUSH 'INITV222' 6 ICKDSF 7 'CP LINK * 222 222 RR' 8 EXIT 9 * * * End of File * * * INITV222 INPUTZ1 F 80 Trunc=80 Size=1 Line=0 Col=1 Alt=0 |...+1+2+3+4+5+6 0 * * * Top of File * * * 1 INIT UNIT(222) NVFY NOMAP PURGE VOLID(VSELOK) FBAVTOC(6200,8) 2 * * * End of File * * * Thank you, Scott R Wandschneider Systems Programmer 3|| Infocrossing, a Wipro Company || 11707 Miracle Hills Drive, Omaha, NE, 68154-4457|| ': 402.963.8905 || Ë:847.849.7223 || : scott.wandschnei...@infocrossing.com **Think Green - Please print responsibly** Confidentiality Note: This e-mail, including any attachment to it, may contain material that is confidential, proprietary, privileged and/or Protected Health Information, within the meaning of the regulations under the Health Insurance Portability Accountability Act as amended. If it is not clear that you are the intended recipient, you are hereby notified that you have received this transmittal in error, and any review, dissemination, distribution or copying of this e-mail, including any attachment to it, is strictly prohibited. If you have received this e-mail in error, please immediately return it to the sender and delete it from your system. Thank you. _ This message contains information which is privileged and confidential and is solely for the use of the intended recipient. If you are not the intended recipient, be aware that any review, disclosure, copying, distribution, or use of the contents of this message is strictly prohibited. If you have received this in error, please destroy it immediately and notify us at privacy...@ailife.com. -- Kris Buelens, IBM Belgium, VM customer support Confidentiality Note: This e-mail, including any attachment to it, may contain material that is confidential, proprietary, privileged and/or Protected Health Information, within the meaning of the regulations under the Health Insurance Portability Accountability Act
Re: Virtual Lock File
If your VSE machines are being IPLed by first IPL-ing CMS and then IPLing VSE from their PROFILE EXEC, then you may do the following: 1. Include 'CP XAUTOLOG VDISKS' in all VSE machines' PROFILE EXECs anywhere before IPL command. (Make sure all your VSE machines are properly authorised to XAUTOLOG VDISKS machine.) 2. Modify PROFILE EXEC in your VDISKS machine to include the check wether the virtual disk is already initialised (check the label or try ACCESSing it) and then don't initialise it if it is. Another way would be to define a VDISK in the PROFILE EXEC of the VDISKS machine (instead of VM directory definition) and check the return code of CP DEFINE (if it's 0, initialise it). If you want to keep a VDISK alive for reasons other than having to manually autolog VDISKS before you IPL the first VSE machine, then take one of the other good suggestions. Ivica Brodaric BNZ
Virtual Lock File
I have a SVM called VDISKS the creates and initializes a virtual lock file for four VSE guest to use. After a short time, VDISKS is logged off by the system. All is fine if at least one VSE remains logged on, however if all are logged off the virtual lock file goes away also. How can I keep VDISKS from being logged off by the system? * * * Top of File * * * USER VDISKS $SECRET$ 4M 4M BG 90 *NAME: VIRTUAL_DISKS ACCOUNT SYSTEMS SUPPORT COMMAND SET RUN ON IPL CMS MACH ESA XAUTOLOG AUTOLOG1 MAINT CONSOLE 0009 3215 T OPERATOR SPOOL 000C 2540 READER * SPOOL 000D 2540 PUNCH A SPOOL 000E 1403 A LINK MAINT 0190 0190 RR LINK MAINT 019D 019D RR LINK MAINT 019E 019E RR MDISK 0191 3390 499 001 PKSCMS MR ALL WRITE MULTIPLE MDISK 0222 FB-512 V-DISK 6208 MWV ALL *DVHOPT LNK0 LOG1 RCM1 SMS0 NPW1 LNGAMENG PWC20101121 CRCc PROFILE EXEC Z1 V 130 Trunc=130 Size=14 |...+1+2+3+4.. 0 * * * Top of File * * * 1 /* */ 2 'CP SPOOL CONSOLE START MAINT CLASS M' 3 Trace I 4 'EXECIO * CP (STRING Q' USERID() 5 PULL @RESPONSE 6 PARSE VAR @RESPONSE @USERID . @TERMID 7 IF @TERMID = 'DSC' THEN DO 8EXEC INITVDSK 9SLEEP 05 SEC 00010'CP SPOOL CONSOLE CLOSE' 00011EXIT 00012 END 00013 SET PF12 RETRIEVE 00014 EXIT 00015 * * * End of File * * * INITVDSK EXEC Z1 V 130 Trunc=130 Size=8 |...+1+2+3+4 0 * * * Top of File * * * 1 /* EXEC TO INITIALIZE ALL VDISKS*/ 2 Trace I 3 ERASE DSFOUT OUTPUT A 4 PUSH 'DSFOUT' 5 PUSH 'INITV222' 6 ICKDSF 7 'CP LINK * 222 222 RR' 8 EXIT 9 * * * End of File * * * INITV222 INPUTZ1 F 80 Trunc=80 Size=1 Line=0 Col=1 Alt=0 |...+1+2+3+4+5+6 0 * * * Top of File * * * 1 INIT UNIT(222) NVFY NOMAP PURGE VOLID(VSELOK) FBAVTOC(6200,8) 2 * * * End of File * * * Thank you, Scott R Wandschneider Systems Programmer 3|| Infocrossing, a Wipro Company || 11707 Miracle Hills Drive, Omaha, NE, 68154-4457|| : 402.963.8905 || :847.849.7223 || : scott.wandschnei...@infocrossing.com **Think Green - Please print responsibly** Confidentiality Note: This e-mail, including any attachment to it, may contain material that is confidential, proprietary, privileged and/or Protected Health Information, within the meaning of the regulations under the Health Insurance Portability Accountability Act as amended. If it is not clear that you are the intended recipient, you are hereby notified that you have received this transmittal in error, and any review, dissemination, distribution or copying of this e-mail, including any attachment to it, is strictly prohibited. If you have received this e-mail in error, please immediately return it to the sender and delete it from your system. Thank you.
Re: Virtual Lock File
Scott, Try adding the following two (2) commands to your PROFILE EXEC -- CP SET RUN ON SET AUTOREAD OFF John P. Baker Chief Software Architect HFD Technologies -Original Message- From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Wandschneider, Scott Sent: Tuesday, March 08, 2011 12:58 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Virtual Lock File I have a SVM called VDISKS the creates and initializes a virtual lock file for four VSE guest to use. After a short time, VDISKS is logged off by the system. All is fine if at least one VSE remains logged on, however if all are logged off the virtual lock file goes away also. How can I keep VDISKS from being logged off by the system? * * * Top of File * * * USER VDISKS $SECRET$ 4M 4M BG 90 *NAME: VIRTUAL_DISKS ACCOUNT SYSTEMS SUPPORT COMMAND SET RUN ON IPL CMS MACH ESA XAUTOLOG AUTOLOG1 MAINT CONSOLE 0009 3215 T OPERATOR SPOOL 000C 2540 READER * SPOOL 000D 2540 PUNCH A SPOOL 000E 1403 A LINK MAINT 0190 0190 RR LINK MAINT 019D 019D RR LINK MAINT 019E 019E RR MDISK 0191 3390 499 001 PKSCMS MR ALL WRITE MULTIPLE MDISK 0222 FB-512 V-DISK 6208 MWV ALL *DVHOPT LNK0 LOG1 RCM1 SMS0 NPW1 LNGAMENG PWC20101121 CRCc PROFILE EXEC Z1 V 130 Trunc=130 Size=14 |...+1+2+3+4.. 0 * * * Top of File * * * 1 /* */ 2 'CP SPOOL CONSOLE START MAINT CLASS M' 3 Trace I 4 'EXECIO * CP (STRING Q' USERID() 5 PULL @RESPONSE 6 PARSE VAR @RESPONSE @USERID . @TERMID 7 IF @TERMID = 'DSC' THEN DO 8EXEC INITVDSK 9SLEEP 05 SEC 00010'CP SPOOL CONSOLE CLOSE' 00011EXIT 00012 END 00013 SET PF12 RETRIEVE 00014 EXIT 00015 * * * End of File * * * INITVDSK EXEC Z1 V 130 Trunc=130 Size=8 |...+1+2+3+4 0 * * * Top of File * * * 1 /* EXEC TO INITIALIZE ALL VDISKS*/ 2 Trace I 3 ERASE DSFOUT OUTPUT A 4 PUSH 'DSFOUT' 5 PUSH 'INITV222' 6 ICKDSF 7 'CP LINK * 222 222 RR' 8 EXIT 9 * * * End of File * * * INITV222 INPUTZ1 F 80 Trunc=80 Size=1 Line=0 Col=1 Alt=0 |...+1+2+3+4+5+6 0 * * * Top of File * * * 1 INIT UNIT(222) NVFY NOMAP PURGE VOLID(VSELOK) FBAVTOC(6200,8) 2 * * * End of File * * * Thank you, Scott R Wandschneider Systems Programmer 3|| Infocrossing, a Wipro Company || 11707 Miracle Hills Drive, Omaha, NE, 68154-4457|| : 402.963.8905 || :847.849.7223 || : scott.wandschnei...@infocrossing.com **Think Green - Please print responsibly**
Re: Virtual Lock File
On 3/8/11 12:57 PM, Wandschneider, Scott scott.wandschnei...@infocrossing.com wrote: I have a SVM called VDISKS the creates and initializes a virtual lock file for four VSE guest to use. After a short time, VDISKS is logged off by the system. All is fine if at least one VSE remains logged on, however if all are logged off the virtual lock file goes away also. How can I keep VDISKS from being logged off by the system? Simplest answer: have the VDISKS userid run PROP in it's PROFILE EXEC (see Running Guest Operating Systems Under VM manual for PROP setup). If you never send it any commands or anything to act on, the VDISKS users will take up almost no resources, and PROP's always there on the basic system. The theory here is that a creator of a VDISK has to stay logged in if you want the VDISK to survive the last user of the VDISK logging off. As you've observed, the userid creates the vdisk and then other users link it. If the creator logs off, but another user has the VDISK linked, then the VDISK survives until the last user linked to it logs off, then CP destroys it. In this case PROP is a simple way to keep the VDISKS userid logged in (thus protecting the VDISK from destruction because the creator is still logged on), but PROP is well behaved enough to pretty much take no resources at all if it's not being actively used.
Re: Virtual Lock File
Our VSE lock file mdisk belongs to OPERATOR, which runs PROP and is disconnected shortly after IPL. All VSE guests tests the lock file in their PROFILE EXEC and if it needs to be initialized, does it. So any guest can come up first and set up the lock file. All OPERATOR does is have the mdisk entry in the DIRECT. On Tue, Mar 8, 2011 at 12:05 PM, David Boyes dbo...@sinenomine.net wrote: On 3/8/11 12:57 PM, Wandschneider, Scott scott.wandschnei...@infocrossing.com wrote: I have a SVM called VDISKS the creates and initializes a virtual lock file for four VSE guest to use. After a short time, VDISKS is logged off by the system. All is fine if at least one VSE remains logged on, however if all are logged off the virtual lock file goes away also. How can I keep VDISKS from being logged off by the system? Simplest answer: have the VDISKS userid run PROP in it's PROFILE EXEC (see Running Guest Operating Systems Under VM manual for PROP setup). If you never send it any commands or anything to act on, the VDISKS users will take up almost no resources, and PROP's always there on the basic system. The theory here is that a creator of a VDISK has to stay logged in if you want the VDISK to survive the last user of the VDISK logging off. As you've observed, the userid creates the vdisk and then other users link it. If the creator logs off, but another user has the VDISK linked, then the VDISK survives until the last user linked to it logs off, then CP destroys it. In this case PROP is a simple way to keep the VDISKS userid logged in (thus protecting the VDISK from destruction because the creator is still logged on), but PROP is well behaved enough to pretty much take no resources at all if it's not being actively used.
Re: Virtual Lock File
I simply use this (at the end of the PROFILE EXEC for the user that owns the VDISKS): Do forever Say Staying alive, staying alive(99 hours)... CP SLEEP 99 HRS End Frank M. Ramaekers Jr. -Original Message- From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Wandschneider, Scott Sent: Tuesday, March 08, 2011 11:58 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Virtual Lock File I have a SVM called VDISKS the creates and initializes a virtual lock file for four VSE guest to use. After a short time, VDISKS is logged off by the system. All is fine if at least one VSE remains logged on, however if all are logged off the virtual lock file goes away also. How can I keep VDISKS from being logged off by the system? * * * Top of File * * * USER VDISKS $SECRET$ 4M 4M BG 90 *NAME: VIRTUAL_DISKS ACCOUNT SYSTEMS SUPPORT COMMAND SET RUN ON IPL CMS MACH ESA XAUTOLOG AUTOLOG1 MAINT CONSOLE 0009 3215 T OPERATOR SPOOL 000C 2540 READER * SPOOL 000D 2540 PUNCH A SPOOL 000E 1403 A LINK MAINT 0190 0190 RR LINK MAINT 019D 019D RR LINK MAINT 019E 019E RR MDISK 0191 3390 499 001 PKSCMS MR ALL WRITE MULTIPLE MDISK 0222 FB-512 V-DISK 6208 MWV ALL *DVHOPT LNK0 LOG1 RCM1 SMS0 NPW1 LNGAMENG PWC20101121 CRCc PROFILE EXEC Z1 V 130 Trunc=130 Size=14 |...+1+2+3+4.. 0 * * * Top of File * * * 1 /* */ 2 'CP SPOOL CONSOLE START MAINT CLASS M' 3 Trace I 4 'EXECIO * CP (STRING Q' USERID() 5 PULL @RESPONSE 6 PARSE VAR @RESPONSE @USERID . @TERMID 7 IF @TERMID = 'DSC' THEN DO 8EXEC INITVDSK 9SLEEP 05 SEC 00010'CP SPOOL CONSOLE CLOSE' 00011EXIT 00012 END 00013 SET PF12 RETRIEVE 00014 EXIT 00015 * * * End of File * * * INITVDSK EXEC Z1 V 130 Trunc=130 Size=8 |...+1+2+3+4 0 * * * Top of File * * * 1 /* EXEC TO INITIALIZE ALL VDISKS*/ 2 Trace I 3 ERASE DSFOUT OUTPUT A 4 PUSH 'DSFOUT' 5 PUSH 'INITV222' 6 ICKDSF 7 'CP LINK * 222 222 RR' 8 EXIT 9 * * * End of File * * * INITV222 INPUTZ1 F 80 Trunc=80 Size=1 Line=0 Col=1 Alt=0 |...+1+2+3+4+5+6 0 * * * Top of File * * * 1 INIT UNIT(222) NVFY NOMAP PURGE VOLID(VSELOK) FBAVTOC(6200,8) 2 * * * End of File * * * Thank you, Scott R Wandschneider Systems Programmer 3|| Infocrossing, a Wipro Company || 11707 Miracle Hills Drive, Omaha, NE, 68154-4457|| : 402.963.8905 || :847.849.7223 || : scott.wandschnei...@infocrossing.com **Think Green - Please print responsibly** Confidentiality Note: This e-mail, including any attachment to it, may contain material that is confidential, proprietary, privileged and/or Protected Health Information, within the meaning of the regulations under the Health Insurance Portability Accountability Act as amended. If it is not clear that you are the intended recipient, you are hereby notified that you have received this transmittal in error, and any review, dissemination, distribution or copying of this e-mail, including any attachment to it, is strictly prohibited. If you have received this e-mail in error, please immediately return it to the sender and delete it from your system. Thank you. _ This message contains information which is privileged and confidential and is solely
Re: Virtual Lock File
Each of our VM systems had a minidisk on a shared pack (with CSE) that we used to test of the target VM system was still up. To assure there was always some LINK to this minidisk, we had it linked by quite a few service machines (VMUTIL, RSCS, Operator, etc). The chance that all of these service machines would be logged off at the same time were pretty small. You could do something similar. 2011/3/8 Frank M. Ramaekers framaek...@ailife.com I simply use this (at the end of the PROFILE EXEC for the user that owns the VDISKS): Do forever Say Staying alive, staying alive(99 hours)... CP SLEEP 99 HRS End Frank M. Ramaekers Jr. -Original Message- From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Wandschneider, Scott Sent: Tuesday, March 08, 2011 11:58 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Virtual Lock File I have a SVM called VDISKS the creates and initializes a virtual lock file for four VSE guest to use. After a short time, VDISKS is logged off by the system. All is fine if at least one VSE remains logged on, however if all are logged off the virtual lock file goes away also. How can I keep VDISKS from being logged off by the system? * * * Top of File * * * USER VDISKS $SECRET$ 4M 4M BG 90 *NAME: VIRTUAL_DISKS ACCOUNT SYSTEMS SUPPORT COMMAND SET RUN ON IPL CMS MACH ESA XAUTOLOG AUTOLOG1 MAINT CONSOLE 0009 3215 T OPERATOR SPOOL 000C 2540 READER * SPOOL 000D 2540 PUNCH A SPOOL 000E 1403 A LINK MAINT 0190 0190 RR LINK MAINT 019D 019D RR LINK MAINT 019E 019E RR MDISK 0191 3390 499 001 PKSCMS MR ALL WRITE MULTIPLE MDISK 0222 FB-512 V-DISK 6208 MWV ALL *DVHOPT LNK0 LOG1 RCM1 SMS0 NPW1 LNGAMENG PWC20101121 CRCc PROFILE EXEC Z1 V 130 Trunc=130 Size=14 |...+1+2+3+4.. 0 * * * Top of File * * * 1 /* */ 2 'CP SPOOL CONSOLE START MAINT CLASS M' 3 Trace I 4 'EXECIO * CP (STRING Q' USERID() 5 PULL @RESPONSE 6 PARSE VAR @RESPONSE @USERID . @TERMID 7 IF @TERMID = 'DSC' THEN DO 8EXEC INITVDSK 9SLEEP 05 SEC 00010'CP SPOOL CONSOLE CLOSE' 00011EXIT 00012 END 00013 SET PF12 RETRIEVE 00014 EXIT 00015 * * * End of File * * * INITVDSK EXEC Z1 V 130 Trunc=130 Size=8 |...+1+2+3+4 0 * * * Top of File * * * 1 /* EXEC TO INITIALIZE ALL VDISKS*/ 2 Trace I 3 ERASE DSFOUT OUTPUT A 4 PUSH 'DSFOUT' 5 PUSH 'INITV222' 6 ICKDSF 7 'CP LINK * 222 222 RR' 8 EXIT 9 * * * End of File * * * INITV222 INPUTZ1 F 80 Trunc=80 Size=1 Line=0 Col=1 Alt=0 |...+1+2+3+4+5+6 0 * * * Top of File * * * 1 INIT UNIT(222) NVFY NOMAP PURGE VOLID(VSELOK) FBAVTOC(6200,8) 2 * * * End of File * * * Thank you, Scott R Wandschneider Systems Programmer 3|| Infocrossing, a Wipro Company || 11707 Miracle Hills Drive, Omaha, NE, 68154-4457|| : 402.963.8905 || :847.849.7223 || : scott.wandschnei...@infocrossing.com **Think Green - Please print responsibly** Confidentiality Note: This e-mail, including any attachment to it, may contain material that is confidential, proprietary, privileged and/or Protected Health Information, within the meaning of the regulations under the Health Insurance Portability Accountability Act as amended. If it is not clear that you are the intended recipient, you are hereby notified that you have received this transmittal in error, and any review, dissemination, distribution or copying of this e-mail, including any attachment to it, is strictly prohibited. If you have received this e-mail in error, please immediately return it to the sender and delete it from your system. Thank you. _ This message contains information which is privileged and confidential and is solely for the use of the intended recipient. If you are not the intended recipient, be aware that any review, disclosure, copying, distribution, or use of the contents of this message is strictly prohibited. If you have received this in error, please destroy it immediately and notify us at privacy...@ailife.com. -- Kris Buelens, IBM Belgium, VM customer support
