IBM Z Hardware and Operating Systems Ideas Portal
This is the public portal for all IBM Z Hardware and Operating System related offerings. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
Regarding the question on where it is documented. This change is documented in the z/VM 7.3 DirMaint manuals:
Tailoring and Admin Guide, DASD Management, :DEFAULTS Section, description…
When building the volume control structures within the DIRMAINT
machine, DirMaint will query each volume listed in the determine their actual size. In an SSI environment,
the queries are issued on each SSI member and the maximum size of the query responses is used. When
the volume is not attached, a default size defined for the device type is used.
Tailoring and Admin Guide, DASD Management, Volume Control File Section …
MAXBLK specifies the maximum allocatable block or cylinder. The value is obtained from the actual
size of the volume. A default size for the DASD model is used when the volume is not attached to
either the system where the DIRMAINT server is running or the SSI cluster member system where a
DirMaint satellite server is running.
Command Reference, AMDISK, Usage note 7….
When the volid used on the AMDISK command does not exist in the EXTENT CONTROL file the
volume will be allocated explicitly. The devtype value provided (3390, 3380) will be used as the
default device type. If the volume is attached to the system, DirMaint will query the device to
determine the maximum size. In an SSI environment, the queries are issued on each SSI member and
the maximum size of the query responses is used. When the volume is not attached, DirMaint will use
the default maximum size that is found in the DEFAULTS section of the EXTENT CONTROL file or the
DEFAULTS DATADVH file (for example, a 3390 device will default to a maximum allocatable cylinder
value of 1113).
Command Reference, CLONEDISK, Usage note 8…
When the volid used on the CLONEDISK command does not exist in the EXTENT CONTROL file
the volume will be allocated explicitly. The devtype value provided (3390, 3380) will be used as
the default device type. If the volume is attached to the system, DirMaint will query the device to
determine the maximum size. In an SSI environment, the queries are issued on each SSI member and
the maximum size of the query responses is used. When the volume is not attached, DirMaint will use
the default maximum size that is found in the DEFAULTS section of the EXTENT CONTROL file or the
DEFAULTS DATADVH file (for example, a 3390 device will default to a maximum allocatable cylinder
value of 1113).
Messages, message 3528W…
When building the volume control files, DirMaint issues QUERY DASD commands to obtain the size
of the volume. In an SSI environment, the queries are issued on each SSI member and the maximum
size of the volume responses is used. If the volume is not attached then the defaults for the specified
device type are used and this may be significantly less than the actual size of the device. If an entry
is specifically defined in the REGIONS section of the EXTENT CONTROL file the device characteristics
are determined by the device type in the entry.
DIRMAINT has made enhancements to obtain the size of a physical volume when it is added to a disk pool in the EXTENT CONTROL file.
DIRMAINT's process of reloading the EXTENT CONTROL file (RLDEXTN command) is enhanced to query each volume listed in the EXTENT CONTROL file or source directory to determine their actual size.
This ensures that DIRMAINT properly identifies the maximum size of the colume that is being used for minidisks as opposed to using the minimum default.
I will work with the developers to get this item added to the new function page.
How is this done? where is it documented?
It is my understanding this is in the base of z/VM 7.3.
From base or with a specific PTF ?