Lucy, Just to clarify for non-HDS customers, this is not the default behavior. By default a volume has no Security applied. It must be placed into a group before there is any security. This is one way for Storage Admin to mask spare capacity from tools like ISMF that can map unused space on offline devices.
The Storage Admin must have implemented Volume Security, which I mentioned last week. This was Volume masking doing exactly what was required. It is much more than managing what is on/offline at IPL - it makes sure offline stays offline as Lucy discovered :-( What if Lucy's mistake was that she was trying to INIT the wrong Device Number, or she was surreptitiously trying to get access to datasets on a production volume. Volume Security is doing exactly what it should by providing hardware mask that isolated this data from being accessed outside of the LPAR it is allocated to. For interested HDS customer, ask your sales rep for a copy of RD6283 Hitachi Volume Security User's Guide. Ron > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On > Behalf Of Lucy Arnold > Sent: Friday, November 14, 2008 3:24 PM > To: [email protected] > Subject: [IBM-MAIN] IODF/HITACHI HELP: SOLVED > > The problem was that the LPAR had to be registered in the Hitachi GUI. > > Thanks EVERYONE for their help!!!!!! > > > > Lucy Arnold > Storage Manager > U.C. Davis Medical Center > 916-734-5498 > > ---------------------------------------------------------------------- > 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 ---------------------------------------------------------------------- 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
