🚀 go-pugleaf

>I am just about finished with the base installation of VM/ESA 2.1.0 and I
>need to merge the directory file on the new system with the VM:Secure
>directory entries on my existing system.

For us, we only really worried about MAINT. To move it over we created a flat
file "MAINT210 VMXSYSAD" with just the MAINT directory entry. Fire it over to
VMSECURE and received it then brought up VMSECURE and it did a source start.

Then you IPL off MAINT210's 190 if you're testing CMS. When you're ready to
switch to the new CMS bring VM:Secure down, rename MAINT to MAINT122 (or
something similar) and MAINT210 to MAINT (don't forget to edit them and adjust
the "USER" record. Then bring up VM:Secure, it'll do a source start. Bring it
down again and IPL CP so everyone has the new 190, including VM:Secure.

If you have a lot of entries to do this too, use "vmxgnr" to create the userid
files from the USER DIRECT file.  You can do this to a t-disk and just take
the id's you need over to the production VM:Secure.

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
*   From: Adrian Clark              Phone  : (416) 510-6161
*   D/704-54, Valleybrook,          User ID: TORINFO(ACLARK)
*   Sears Canada, VM Technical Development   IBMMAIL(CASRSAJC)