This may seem like an obvious solution, but have you tried to vary the unit offline and online again on the LPAR in error?
Richard Habres AVP; Enterprise Storage Technology Merrill Lynch -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Ed Finnell Sent: Thursday, June 09, 2005 10:35 AM To: [email protected] Subject: Re: Volume Problem - z/OS 1.4 In a message dated 6/9/2005 8:29:53 A.M. Central Standard Time, [EMAIL PROTECTED] writes: How could the volser get messed up on one LPAR like that? TTOP04 is the correct volser but the first LPAR doesn't indicate that. Anyone seen this before? Somethings overlaying it! Guess I'd start with EREP to see if there were any hardware or software hits in the window. Then check with DASD vendor on uCode levels or known problems relating to VOLSER with SHARED DASD. How current is your Maint? -------------------------------------------------------- If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -------------------------------------------------------- ---------------------------------------------------------------------- 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
