A fix is available
APAR status
Closed as program error.
Error description
One has the following MDISK definition : USER $FILLER$ NOLOG * fill excess space, known by DIRMAP, not available on LUN MDISK A000 FB-512 14680064 4280287224 TSTRES DIRMAP doesn't complain about this definition while DIRECTXA execution results in message :HCPDIR1762E INVALID BLOCK SPECIFICATION CODE = 12 FOLLOWING USER $FILLER$ The z/VM CP Planning and Administration version 6 release 3 Chapter 17. Creating and Updating a User Directory page 543 mentions the following maximum minidisk sizes : Device Type Models Format 9336 020 2147483640 blocks FB-512 (vdisk in storage) (not applicable) 4194296 blocks The HCPDIR1762E error when running DIRECTXA with his definition is as expected as 4280287224 > 2147483640. But apparently DIRMAP doesn't use the same value as it runs without any error.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Anyone using the DIRMAP command to map off * * the end of a minidisk defined on a FB-512 * * type device in a CP user directory is * * affected by this change. * **************************************************************** * PROBLEM DESCRIPTION: * **************************************************************** * RECOMMENDATION: APPLY PTF * **************************************************************** DIRMAP had several deficiencies when dealing with minidisks on FB-512 and 9336 devices. 1. DIRMAP used a different maximum disk size for FB-512 and 9336 minidisks than DIRECTXA used 2. The END option was not honored for minidisks on FB-512 and 9336 devices 3. The option FULLPACK and the FULLPACK DEFINES file was not honored for FB-512 and 9336 minidisks
Problem conclusion
The DIRMAP command has been updated such that 1. the maximum disk size for FB-512 minidisks matches the maximum size used by the CP DIRECTXA command 2. added support for the END option on FB-512 and 9336 devices 3. the FULLPACK option and the use of the FULLPACK DEFINES file is now extended to minidisks of type FB-512 and 9336. THE FOLLOWING CHANGES HAVE BEEN MADE TO THE SYSTEM REFERENCE LIBRARIES: ***START PUBLICATION CHANGE************************************* PUBLICATION TITLE: CMS Commands and Utilities Reference RELEASE: z/VM 6.3.0 ORDER NUMBER: SC24-6166-03 ------------------------------------------- CHAPTER: 3 PAGE: 1398 ABSTRACT: Update FULLPACK option to add FB-512 and 9336 disks BODY: FULLPACK specifies fullpack minidisk definitions are found in FULLPACK DEFINES. If the input file is not found, a message is issued and the default fullpack minidisk sizes are used. If the file is found, it can list new fullpack minidisk sizes for device types 3380, 3390, 9336, and FB-512 DASD. These new sizes are added to the existing fullpack minidisk sizes. Only numerics are valid for the size. ------------------------------------------- CHAPTER: 3 PAGE: 1400 ABSTRACT: Update FULLPACK option to add FB-512 and 9336 disks BODY: FULLPACK DEFINES is used by DIRMAP to list new fullpack minidisk definitions for device types 3380, 3390, 9336, and FB-512 DASD. The first word is either 3380, 3390, 9336, or FB-512. The second word is the ending minidisk cylinder or block number. The ending minidisk cylinder or block number cannot be more than 10 numeric characters. All other words on the record are ignored. Therefore, if you wanted to define a fullpack of 1000 cylinders and one of 1500 cylinders on your device type 3380, a fullpack of 2000 cylinders and one of 2500 cylinders on your device type 3390, and a fullpack of 4280287224 blocks on both your device types FB-512 and 9336, your FULLPACK DEFINES looks similar to the following: 3380 999 3380 1499 3390 1999 3390 2499 9336 4280287224 FB-512 4280287224 Your corresponding directory statements looks similar to the following: MDISK 123 3380 000000 1000 VMSRES RR MDISK 124 3380 000000 1500 VMSPKK RR MDISK 125 3390 000000 2000 MYPACK RR MDISK 126 3390 000000 1500 YOURPK RR MDISK A00 9336 14680064 4280287224 MYTEST MDISK A01 FB-512 14680064 4280287224 YOURTS ------------------------------------------- CHAPTER: 3 PAGE: 1402 ABSTRACT: Update FULLPACK options to add FB-512 and 9336 disks BODY: Add a line to Table 61: "Fullpack Minidisk Values" after the 9336 entry which reads: +-----------------------------------------------------+ | DASD Type Beginning Total Blocks or Cylinders | | and Model Block or | | Cylinder | +-----------------------------------------------------+ | FB-512 000 2147483640 See note 2 below | +-----------------------------------------------------+ ***END PUBLICATION CHANGE*************************************** ***START PUBLICATION CHANGE************************************* PUBLICATION TITLE: CMS Commands and Utilities Reference RELEASE: z/VM 6.4.0 ORDER NUMBER: SC24-6166-04 ------------------------------------------- CHAPTER: 3 PAGE: 1390 ABSTRACT: Update FULLPACK options to add FB-512 and 9336 disks BODY: FULLPACK specifies fullpack minidisk definitions are found in FULLPACK DEFINES. If the input file is not found, a message is issued and the default fullpack minidisk sizes are used. If the file is found, it can list new fullpack minidisk sizes for device types 3380, 3390, 9336, and FB-512 DASD. These new sizes are added to the existing fullpack minidisk sizes. Only numerics are valid for the size. ------------------------------------------- CHAPTER: 3 PAGE: 1392 ABSTRACT: Update FULLPACK options to add FB-512 and 9336 disks BODY: FULLPACK DEFINES is used by DIRMAP to list new fullpack minidisk definitions for device types 3380, 3390, 9336, and FB-512 DASD. The first word is either 3380, 3390, 9336, or FB-512. The second word is the ending minidisk cylinder number. The ending minidisk cylinder cannot be more than 8 numeric characters. All other words on the record are ignored. Therefore, if you wanted to define a fullpack of 1000 cylinders and one of 1500 cylinders on your device type 3380, a fullpack of 2000 cylinders and one of 2500 cylinders on your device type 3390, and a fullpack of 4280287224 blocks on both your device types FB-512 and 9336, your FULLPACK DEFINES looks similar to the following: 3380 999 3380 1499 3390 1999 3390 2499 9336 4280287224 FB-512 4280287224 Your corresponding directory statements looks similar to the following: MDISK 123 3380 000000 1000 VMSRES RR MDISK 124 3380 000000 1500 VMSPKK RR MDISK 125 3390 000000 2000 MYPACK RR MDISK 126 3390 000000 1500 YOURPK RR MDISK A00 9336 14680064 4280287224 MYTEST MDISK A01 FB-512 14680064 4280287224 YOURTS ------------------------------------------- CHAPTER: 3 PAGE: 1394 ABSTRACT: Update FULLPACK options to add FB-512 and 9336 disks BODY: Add a line to Table 62: "Fullpack Minidisk Values" after the 9336 entry which reads: +-----------------------------------------------------+ | DASD Type Beginning Total Blocks or Cylinders | | and Model Block or | | Cylinder | +-----------------------------------------------------+ | FB-512 000 2147483640 See note 2 below | +-----------------------------------------------------+ ***END PUBLICATION CHANGE***************************************
Temporary fix
Comments
APAR Information
APAR number
VM65491
Reported component name
VM CMS
Reported component ID
568411201
Reported release
630
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2014-01-24
Closed date
2016-12-19
Last modified date
2018-12-14
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
306PC1Ÿ UM34990 306PC1Ÿ 306PC1Ÿ
Modules/Macros
DEVICE DIRMAP DTRYDIR
| SC24616603 | SC24616604 |
Fix information
Fixed component name
VM CMS
Fixed component ID
568411201
Applicable component levels
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG27M","label":"APARs - z\/VM environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"630","Edition":"","Line of Business":{"code":"LOB16","label":"Mainframe HW"}}]
Document Information
Modified date:
14 December 2018