Dirmaint already uses the dirmap: Try "DIRM DIRMAP"
______________________________________________
Clovis Pereira
From: Edward M Martin <[email protected]>
To: [email protected]
Date: 04/10/2010 15:47
Subject: Re: How DIRMAINT Work ?
Sent by: The IBM z/VM Operating System <[email protected]>
Hello Kris,
DIRMAP part of the CMS Utilities Feature 1.1, along with FLIST, WAKEUP,
VMSIZE, USERID, SFPURGER, and the others.
Ed Martin
Aultman Health Foundation
330-363-5050
ext 35050
From: The IBM z/VM Operating System [mailto:[email protected]] On
Behalf Of Kris Buelens
Sent: Monday, October 04, 2010 2:29 PM
To: [email protected]
Subject: Re: How DIRMAINT Work ?
I tell over and over again: forget about DISKMAP, use DISKMAP instead.
DIRMAP used to be billable (part of IPF, later CUF), so the poor-man's
solution, DISKMAP EXEC, was created.
I've got a document describing differences in more details , and I give
some hints about how to manage the CP Directory (like a FULLPACK user with
an MDISK for every disk.
2010/10/4 Scott Rohling <[email protected]>
Because the DISKMAP utility is unaware of the size of the 'real' disk - so
END is meaningless to it.
I always encourage folks to not use END except under specific
circumstances. If there is a reason other than laziness to specify END --
then use it. Otherwise, list the number of cylinders specifically.
Oh - and it can pose a danger if you rely on DISKMAP to tell you what is
already allocated and these disks don't show up.
You might want to try DIRMAINT FREE and DIRMAINT USED commands instead of
DISKMAP. (The thread is about DIRMAINT after all ;-)
Scott Rohling
On Mon, Oct 4, 2010 at 10:10 AM, George Henke/NYLIC <
[email protected]> wrote:
Minidisks with the END option specified are not included in a DISKMAP when
the command, DISKMAP USER is entered.
What is the reason for this?
Does this pose a danger when updating the directory directly, no pun
intended? :-)
Ray Waters <[email protected]>
Sent by: The IBM z/VM Operating System <[email protected]>
Kris Buelens
