Re[2]: FW: 2 VTAM segments

[Carey Tyler Schug]

Method 3: Like method 2, but use DCSSBKUP to store an image of each
version of the VTAM NSSes in a disk file, then use DCSSRSAV to recreate
which ever NSS you want. I use this method to enable AUTOLOG1 to recreate
the NSSes for VSAM, which my ACF2 external security manager requires.
AUTOLOG1 also restores the auxiliary CMS segments, our CMS IPLer, and
finishes with resaving CMS, so all the critical segments are available
after a very cold start, such occurs during a disaster recovery. This way,
I never have to IPL without ACF2 and manually load an NSS tape.

This allows testing from home or from your office remote from the computer
center, without having to worry about mounting tapes.

------------------------------------------------------------------------------

METHOD 1:
If VTAM 4.2.0 is serviced in the SNA-products fashion there's a mdisk
(3xx something-or-other) on which VTAM's service parameter file is stored
(it specifies mdisk addr's of BASE, MERGE, DELTA, ZAP disks) but
for your purpose it also specifies the *name* of VTAM's DCSS. Specify it as
VTAM420 and re-gen GCS to load VTAM420... but now you need 2 GCS's? no?

METHOD 2:
Use CP SPXTAPE command to backup your production VTAM 3.4.1 VTAM segment.
Save your VTAM 4.2.0 segment under the name VTAM. This will mark your
3.4.1 VTAM segment as pending-purge (are you on VM/ESA?) so restore a
fresh copy from the SPXTAPE copy.
From then on you can restore and run either VTAM version, always using
segment name VTAM.