This was a topic back in the spring of 2003. I have an issue with this topic again, so I'm starting a new thread, with a slightly different twist.
Many shops utilize running their system as an MVS guest under VM at DR (Disaster Recovery) sites. Been doing that for years. We IPL our z/OS 1.4 system as an MVS Guest on the SG (SunGard) VM floor system in Philly. Done this before, but THIS time we are using "System Symbols", which were recently implemented on our PROD system at home. For some unknown and undetermined reason, z/OS is NOT looking for the correct member in SYS1.PARMLIB. **NOTE: I do NOT have the screen print with the error msg NOR do I have a copy of the actual error msg. Sorry. But z/OS is looking for member IEASYSCM in SYS1.PARMLIB, because we have: IEASYM (CM,RR) coded in the LOADxx member in SYS1.IPLPARM. We do NOT get: IEE252I MEMBER IEASYMCM FOUND IN SYS1.PARMLIB IEE252I MEMBER IEASYMRR FOUND IN SYS1.PARMLIB So, the upshot is that z/OS is not resolving the system symbols correctly. Our current work around is to bypass system symbols right now. My guess is that this is a problem within the VM definition in the VM directory. That VM and MVS are not handshaking and making nice, ay?! This first occurred in October 2006, without resolution. This April we were supposed to have the MVS console here remotely in our test center, so we could all see what the folks in Philly were seeing. Problems with our T-1 link and a bad card in a router prevented that from happening. Anyone ever experience such a situation? Or can anybody speak to the possible root cause, off the top of your head? THANX, Mark H. Young Sr. MVS SysProg Fairfax County Gov't of Virginia ---------------------------------------------------------------------- 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
