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
