Re: Updating PROFILE GCS Nondisruptively
We have all of our coding on the 192 disk. The only thing VTAM does is run the VTAMPROF GCS from the 192 disk. The same is true for almost any other service machine (GCS, RSCS, OPERATOR, SFS). They all link the same minidisk as 192, obviously RO, and run customized EXEC or GCS. Afterwards we let the machine reaccess that disk to get the new content available. In case of VTAM: Update file. SEND VTAM ACCESS 192 D Regards, Berry. Op 08-11-10 23:49, George Henke/NYLIC schreef: What is the best way to update PROFILE GCS without corrupting VTAM? VTAM has R/W access to it and yet I must update GCS through an LU? Will I not bring down VTAM or corrupt VTAM's 191 if I update it while VTAM is up?.
Re: Updating PROFILE GCS Nondisruptively
ty, Berry, do you need to be a SECUSER to issue the SEND VTAM command? Berry van Sleeuwen berry.vansleeu...@xs4all.nl Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 11/09/2010 11:25 AM Please respond to IBMVM IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: Updating PROFILE GCS Nondisruptively We have all of our coding on the 192 disk. The only thing VTAM does is run the VTAMPROF GCS from the 192 disk. The same is true for almost any other service machine (GCS, RSCS, OPERATOR, SFS). They all link the same minidisk as 192, obviously RO, and run customized EXEC or GCS. Afterwards we let the machine reaccess that disk to get the new content available. In case of VTAM: Update file. SEND VTAM ACCESS 192 D Regards, Berry. Op 08-11-10 23:49, George Henke/NYLIC schreef: What is the best way to update PROFILE GCS without corrupting VTAM? VTAM has R/W access to it and yet I must update GCS through an LU? Will I not bring down VTAM or corrupt VTAM's 191 if I update it while VTAM is up?.
Re: Updating PROFILE GCS Nondisruptively
As opposed to CMS, the PROFILE GCS doesn't need to be on the A-disk. Any disk accessed at IPL is good. - in the good old days, GCS accessed 595 S; 59E Y/S; 191 A; and 191 A - now only 191 A and 192 are left. In these good old days, I stored all customzed execs (including the common PROFILE GCS) on MAINT 59E, linked by all GCS users. Whne GCS no longer had an S- nor Y-disk, I simply made our GCS users LINK MAINT 59E 192 and the common PROFILE GCS still worked. GCS, AVSVM, and some less common ones, didn't even have a 191 A-disk. 2010/11/9 Berry van Sleeuwen berry.vansleeu...@xs4all.nl We have all of our coding on the 192 disk. The only thing VTAM does is run the VTAMPROF GCS from the 192 disk. The same is true for almost any other service machine (GCS, RSCS, OPERATOR, SFS). They all link the same minidisk as 192, obviously RO, and run customized EXEC or GCS. Afterwards we let the machine reaccess that disk to get the new content available. In case of VTAM: Update file. SEND VTAM ACCESS 192 D Regards, Berry. Op 08-11-10 23:49, George Henke/NYLIC schreef: What is the best way to update PROFILE GCS without corrupting VTAM? VTAM has R/W access to it and yet I must update GCS through an LU? Will I not bring down VTAM or corrupt VTAM's 191 if I update it while VTAM is up?. -- Kris Buelens, IBM Belgium, VM customer support
Re: Updating PROFILE GCS Nondisruptively
I didn't now this. So we even do not need the PROFILE GCS on the 191 disk and store the PROFILE GCS on the 192 disk. Or perhaps even only link the RO disk as 191 instead of keeping the local 191 minidisk. Nice. Op 09-11-10 18:34, Kris Buelens schreef: As opposed to CMS, the PROFILE GCS doesn't need to be on the A-disk. Any disk accessed at IPL is good. - in the good old days, GCS accessed 595 S; 59E Y/S; 191 A; and 191 A - now only 191 A and 192 are left. In these good old days, I stored all customzed execs (including the common PROFILE GCS) on MAINT 59E, linked by all GCS users. Whne GCS no longer had an S- nor Y-disk, I simply made our GCS users LINK MAINT 59E 192 and the common PROFILE GCS still worked. GCS, AVSVM, and some less common ones, didn't even have a 191 A-disk. 2010/11/9 Berry van Sleeuwen berry.vansleeu...@xs4all.nl mailto:berry.vansleeu...@xs4all.nl We have all of our coding on the 192 disk. The only thing VTAM does is run the VTAMPROF GCS from the 192 disk. The same is true for almost any other service machine (GCS, RSCS, OPERATOR, SFS). They all link the same minidisk as 192, obviously RO, and run customized EXEC or GCS. Afterwards we let the machine reaccess that disk to get the new content available. In case of VTAM: Update file. SEND VTAM ACCESS 192 D Regards, Berry. Op 08-11-10 23:49, George Henke/NYLIC schreef: What is the best way to update PROFILE GCS without corrupting VTAM? VTAM has R/W access to it and yet I must update GCS through an LU? Will I not bring down VTAM or corrupt VTAM's 191 if I update it while VTAM is up?. -- Kris Buelens, IBM Belgium, VM customer support
Re: Updating PROFILE GCS Nondisruptively
We have class c on our own users and/or use user OPERATOR (who is secuser) to send the commands. Since our profiles and such are maintained and distributed automatically by a sevicemachine, usually OPERATOR is used to issue the commands. And also because we can have PROP control the authorisation as well as storing the commands and output into the operator log. Regards, Berry. Op 09-11-10 17:27, George Henke/NYLIC schreef: ty, Berry, do you need to be a SECUSER to issue the SEND VTAM command? *Berry van Sleeuwen berry.vansleeu...@xs4all.nl* Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 11/09/2010 11:25 AM Please respond to IBMVM IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: Updating PROFILE GCS Nondisruptively We have all of our coding on the 192 disk. The only thing VTAM does is run the VTAMPROF GCS from the 192 disk. The same is true for almost any other service machine (GCS, RSCS, OPERATOR, SFS). They all link the same minidisk as 192, obviously RO, and run customized EXEC or GCS. Afterwards we let the machine reaccess that disk to get the new content available. In case of VTAM: Update file. SEND VTAM ACCESS 192 D Regards, Berry. Op 08-11-10 23:49, George Henke/NYLIC schreef: What is the best way to update PROFILE GCS without corrupting VTAM? VTAM has R/W access to it and yet I must update GCS through an LU? Will I not bring down VTAM or corrupt VTAM's 191 if I update it while VTAM is up?.
Re: Updating PROFILE GCS Nondisruptively
On Monday, 11/08/2010 at 05:50 EST, George Henke/NYLIC george_he...@newyorklife.com wrote: What is the best way to update PROFILE GCS without corrupting VTAM? VTAM has R/W access to it and yet I must update GCS through an LU? Will I not bring down VTAM or corrupt VTAM's 191 if I update it while VTAM is up?. Logon to MAINT SET SECUSER VTAM * SEND VTAM CP DETACH 191 Link and access VTAM 191 .MR update PROFILE GCS release and DETACH VTAM's 191 from MAINT SEND VTAM CP LINK * 191 191 MR SEND VTAM ACCESS 191 A SET SECUSER VTAM RESET Alan Altmark z/VM and Linux on System z Consultant IBM System Lab Services and Training ibm.com/systems/services/labservices office: 607.429.3323 alan_altm...@us.ibm.com IBM Endicott
Re: Updating PROFILE GCS Nondisruptively
tyvm, Alan, once again. Alan Altmark alan_altm...@us.ibm.com Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 11/08/2010 05:56 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: Updating PROFILE GCS Nondisruptively On Monday, 11/08/2010 at 05:50 EST, George Henke/NYLIC george_he...@newyorklife.com wrote: What is the best way to update PROFILE GCS without corrupting VTAM? VTAM has R/W access to it and yet I must update GCS through an LU? Will I not bring down VTAM or corrupt VTAM's 191 if I update it while VTAM is up?. Logon to MAINT SET SECUSER VTAM * SEND VTAM CP DETACH 191 Link and access VTAM 191 .MR update PROFILE GCS release and DETACH VTAM's 191 from MAINT SEND VTAM CP LINK * 191 191 MR SEND VTAM ACCESS 191 A SET SECUSER VTAM RESET Alan Altmark z/VM and Linux on System z Consultant IBM System Lab Services and Training ibm.com/systems/services/labservices office: 607.429.3323 alan_altm...@us.ibm.com IBM Endicott
