DIAG 84 can be used to change certain things, adding a new minidisk was not part of that, changing MDISK definition details is. You can see when Dirmaint has to use DIRECTXA in the messages it sends to you. Look for something like "updating the directory with DIAG84 failed; reverting to classic method" when you issue a DIRM CMDISK.
2010/5/27 Mike Walter <mike.wal...@hewitt.com> > Does DIRMAINT still call DIRECTXA for every directory update? I would > expect that by now it would perform directory update in place, > using DIAG X'84'. > > Mike Walter > Hewitt Associates > The opinions expressed herein are mine alone, not my employer's. > > > > "Kris Buelens" <kris.buel...@gmail.com> > > Sent by: "The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU> > 05/27/2010 02:55 PM > Please respond to > "The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU> > > > > To > IBMVM@LISTSERV.UARK.EDU > cc > > Subject > Re: DFSMS install > > > > > > > I'd be surprized thay must be 3380's: DFSMS overrides them dynamically to > match source and target MDISKs when it moves a CMS disk to a new place. > And, at that time it will get the device type, start, and size of the > source/target. > > DFSMS was the first to use this trick, it avoids several calls to > DIRECTXA, so improves performance on systems with large directories. > Dirmaint R5 later copied this technique. > > 2010/5/27 Alan Altmark <alan_altm...@us.ibm.com> > On Thursday, 05/27/2010 at 01:34 EDT, Mark Pace <mpac...@gmail.com> wrote: > > I'm confused. > > The DFSMS program directory has a note > > Critical Information > > The 500 & 5FF minidisk must be 3380 dasd. Emphasis IBM's. > > mdisk 0500 3380 001 001 $$$$$$ MR > > mdisk 0500 3380 001 001 $$$$$$ MR > > > > Yet the sample directory entries provided in VSM221B PLANINFO have 3390 > as the > > devtype. > > mdisk 0500 3390 001 001 $$$$$$ MR > > mdisk 0500 3390 001 001 $$$$$$ MR > > > > Is the program directory incorrect or is the provided sample incorrect? > Does > > it really matter? > > Yes, it matters. In order for CP to instantiate a minidisk, the vdev type > must match the rdev type. I suspect that the 'must be 3380' is really > 'must be modern ECKD that supports the stuff I need'. > > While not relevant in this particular case, the device type on the MDISK > tells DIRECTXA what the highest cylinder number is for that volume > (remembering that the volumes are not necessarily available to DIRECTXA > when it is being run). > > > Alan Altmark > z/VM Development > IBM Endicott > > > > -- > Kris Buelens, > IBM Belgium, VM customer support > > > > > The information contained in this e-mail and any accompanying documents may > contain information that is confidential or otherwise protected from > disclosure. If you are not the intended recipient of this message, or if > this message has been addressed to you in error, please immediately alert > the sender by reply e-mail and then delete this message, including any > attachments. Any dissemination, distribution or other use of the contents of > this message by anyone other than the intended recipient is strictly > prohibited. All messages sent to and from this e-mail address may be > monitored as permitted by applicable law and regulations to ensure > compliance with our internal policies and to protect our business. E-mails > are not secure and cannot be guaranteed to be error free as they can be > intercepted, amended, lost or destroyed, or contain viruses. You are deemed > to have accepted these risks if you communicate with us by e-mail. > -- Kris Buelens, IBM Belgium, VM customer support
