Mark,

Until someone tells you differently, I'd assume (usually bad thing) that 
the doc never got updated when everything else was changed to 3390.
I'm guessing that it is really trying to imply that those MDISKs should 
not be moved to SFS directories.

Now, a 2-fer of questions for *you*...

1) Why not just open a PMR with IBM to get the correct info fro the 
horse's mouth?
2) Do you really WANT to use DFSMS/VM space management?  I don't hear of 
anyone else on the list actually using it.

Mike Walter
Hewitt Associates
The opinions expressed herein are mine alone, not my employer's.



"Mark Pace" <mpac...@gmail.com> 

Sent by: "The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU>
05/27/2010 12:32 PM
Please respond to
"The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU>



To
IBMVM@LISTSERV.UARK.EDU
cc

Subject
DFSMS install






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? 

-- 
Mark Pace
Mainline Information Systems
1700 Summit Lake Drive
Tallahassee, FL. 32317



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. 


Reply via email to