A fix is available
APAR status
Closed as program error.
Error description
VSAM non-indexed data set is allocated using 2 storage groups. The second storage group is defined as an overflow storage group. The primary storage group has 20 volumes all with sufficient space. All volumes in the primary storage group are EAV. There are 8 volumes in the overflow storage group, none of these are EAV. The primary storage group volumes cyl-managed space is full, however there is sufficient space in track managed space to satisfy the request. The allocation receives: MSGIGD17223I data set was allocated to an overflow storage group. ANALYSIS: The data class definition in IGDDCD shows DCDSFLG is x'00'which says EATTR is not specified. For VSAM the default is EATTR=OPT so SMS should be considering the primary storage group volumes as there is space in cyclinder-managed space to satisfy the request
Local fix
Ensure the cylinder-managed space is sufficient to satisfy the request.
Problem summary
**************************************************************** * USERS AFFECTED: * * HDZ2220 and above users * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * **************************************************************** When the EAV volumes did not have sufficient cylinder managed space to satisfy the request but had sufficient track managed space, SMS rejected those volumes and incorrectly selected a volume from an OVERFLOW storage group.
Problem conclusion
When the requested disk space is greater than or equal to the value for BreakPointValue, the system prefers to use the cylinder-managed space for that extent. . For all data set types, if not enough cylinder-managed space is available, the system uses track-managed space or both cylinder-managed space and track-managed space. - For non-VSAM data sets and VSAM data sets (excluding KSDS), when volumes in the volume list do not have enough cylinder-managed space and the primary storage groups have sufficient track-managed space, volumes that are enabled will be marked as primary. This will prevent a data set from being allocated in an overflow storage group. When the requested disk space is less than the value for BreakPointValue, the system prefers to use track-managed space for that extent. . For all data set types, if not enough track-managed space is available, the system uses cylinder-managed space or both track-managed space and cylinder-managed space. - For non-VSAM data sets and VSAM data sets (excluding KSDS), when volumes in the volume list do not have enough track-managed space and the primary storage groups have sufficient cylinder-managed space, volumes that are enabled will be marked as primary. This will prevent a data set from being allocated in an overflow storage group. The following 3 publications related to BreakPointValue need to be updated: 1- SA23-1380-09 z/OS MVS Initialization and Tuning Reference At Chapter 62. IGDSMSxx (storage management subsystem Definition) for BREAKPOINTVALUE(0-65520), add the following note at the end: Note: For more details, please reference z/OS DFSMSdfp Storage Administration. 2- SA38-0666-07 z/OS MVS System Commands At SETSMS command section for BreakPointValue(nnnn), add the following note at the end: Note: For more details, please reference z/OS DFSMSdfp Storage Administration. 3- SC23-6860-02 z/OS DFSMSdfp Storage Administration At Chapter 4. Defining storage groups for BreakPointValue, replace the third paragraph. The third paragraph is like the following: "When a disk space request is equal to or ... cylinder-managed space." to be replaced by the following: When the requested disk space is greater than or equal to the value for BreakPointValue, the system prefers to use the cylinder-managed space for that extent. . For all data set types, if not enough cylinder-managed space is available, the system uses track-managed space or both cylinder-managed space and track-managed space. - For non-VSAM data sets and VSAM data sets (excluding KSDS), when volumes in the volume list do not have enough cylinder-managed space and the primary storage groups have sufficient track-managed space, volumes that are enabled will be marked as primary. This will prevent a data set from being allocated in an overflow storage group. When the requested disk space is less than the value for BreakPointValue, the system prefers to use track-managed space for that extent. . For all data set types, if not enough track-managed space is available, the system uses cylinder-managed space or both track-managed space and cylinder-managed space. - For non-VSAM data sets and VSAM data sets (excluding KSDS), when volumes in the volume list do not have enough track-managed space and the primary storage groups have sufficient cylinder-managed space, volumes that are enabled will be marked as primary. This will prevent a data set from being allocated in an overflow storage group.
Temporary fix
Comments
APAR Information
APAR number
OA58596
Reported component name
STORAGE MGMT SU
Reported component ID
5695DF101
Reported release
230
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2019-10-31
Closed date
2020-02-26
Last modified date
2020-04-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UJ02226 UJ02227 UJ02228
Modules/Macros
IGDVTSSS IGDVTSV2
| SA23138009 | SA38066607 | SC23686002 |
Fix information
Fixed component name
STORAGE MGMT SU
Fixed component ID
5695DF101
Applicable component levels
R240 PSY UJ02227
UP20/04/01 P F003
R230 PSY UJ02226
UP20/04/01 P F003
R220 PSY UJ02228
UP20/04/01 P F003
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":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"230","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
27 March 2020