I don't see any need/benefit to create another VTAM saved segment (guessing both VTAMs will use the same VTAM SW level). Having both VTAMs use the same segment even saves some real storage, so why do you say "to avoid any storage complaints"?
The VTAM segment can even fall inside the DEF STORAGE of the VTAM machine (as it does in the default setup): the name of the VTAM SEGMENT is listed in the GCS definitions, meaning GCS will load it soon after its IPL, and this for all members of thje GCS group, not only for user VTAM. If however you really insist: Q NSS NAME VTAM MAP to get the addresses it currently uses DEFSEG VTAM2 xxx-yyy SR where xxx-yyy is obtained from Q NSS run the VTAMSEG EXEC This is outside the VMSES environment, so if you'd apply service to VTAM, you'll have to repeat the above. 2010/10/19 Franz Josef Pohlen <[email protected]> > Hi listers, > > my customer uses VM-TN3270E, SCEXIT and Dial to VM-VTAM to connect to his > CICS-TS in zVSE. Now he is going to reach the 4096 devices limit in his > vm-vtam, because the Non-SNA resources support only 3-digit device numbers. > We want to create a 2nd GCS and VTAM with its own segments to avoid any > storage complaints. I know how to build a new GCS, but how can I build a new > VTAM NSS VTAM2 instead of VTAM. > -- > kind regards > Franz Josef Pohlen > -- Kris Buelens, IBM Belgium, VM customer support
