Mark, I ran into similar problems at a previous site when running as VM guests at the hot site. Ours turned out to be related to the way we had the LOADxx member coded. We had one LOADxx used by all systems at the site with HWNAME and LPARNAME filter statements coded so each system would find the proper parmlib concatenations, IEASYSxx and IEASYMxx members. For DR tests, I added VMUSERID statements that would cause the correct values to be used when running as a VM guest at the hot site, but the way the LOADxx member is processed, we didn't match any of the filter statements, so ended up not using the proper parmlibs etc. To circumvent this we created new LOADxx members for each system to force them to use the proper values.
What I learned from all this is that this mechanism is difficult to test, and there are no messages stating what parts of LOADxx member is used or not used. You can contact me off-list if you'd like any more details, but this may be contributing to your troubles HTH Dana Mitchell On Wed, 2 May 2007 10:04:01 -0500, Mark H. Young <[EMAIL PROTECTED]> wrote: > >Many shops utilize running their system as an MVS guest under VM at DR >(Disaster Recovery) sites. >For some unknown and undetermined reason, z/OS is NOT looking for the >correct member in SYS1.PARMLIB. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
