That is a welcome change from the former action. Having a new allocation
map wiped out at shutdown time was the source of a considerable amount
of head scratching. In my case, it was new PARM disk allocations that
got hammered. Thank you Bob or whoever wrote the code.
Regards,
Richard Schuh
________________________________
From: The IBM z/VM Operating System
[mailto:ib...@listserv.uark.edu] On Behalf Of Bob Bolch
Sent: Friday, February 27, 2009 7:39 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Changing DRCT size
>Oh yes: with DIRMAINT there is no problem as with VM:Secure.
It doesn't need to be brought down.
Starting with r2.8 Service Pack 1, VM:Secure provides a new
CPFMTXA command which allows you to change
the allocation map on a volume containing the DRCT area, without
taking VM:Secure down. It can be used to
add new directory cylinders or to modify any non-directory
cylinders. To remove directory cylinders, we suggest
taking VM:Secure down as in previous releases.
The VM:Secure CPFMTXA command works by locking out changes to
the directory area, running the IBM
CPFMTXA command, and then refreshing its own in-memory cache of
the allocation map.
Bob Bolch
