APAR status
Closed as program error.
Error description
OA35600 (sysroute of OA34306) was created to correct the following symptoms: IEC331I 050-012(041A041D,M9SN01),P27890R,RESTORE,VALO,IGG0CLE5 or ADR709E (001)-VDSS (01), AN ERROR OCCURRED IN THE STORAGE MANAGEMENT SUBSYSTEM WHILE ALLOCATING DATA SET P27890.SAMS0.SSS WITH NEWNAME P27890.SAMS0.T. SMS MESSAGES FOLLOW. IGD17102I CATALOG ERROR IN DEFINING NONVSAM DATA SET P27890.SAMS0.T RETURN CODE IS 50 REASON CODE IS 12 IGG0CLE5 IGD306I UNEXPECTED ERROR DURING IGG0CLE5 PROCESSING RETURN CODE 50 REASON CODE 12 THE MODULE THAT DETECTED THE ERROR IS IGDVTSCU SMS MODULE TRACE BACK - VTSCU VTSCT VTSCM VTSCR SSIRT SYMPTOM RECORD CREATED, PROBLEM ID IS IGD00012 This occurs when the data set being processed is larger than the volume its targeted to be created on and no VVDS exists on the volume. The window occurs when the dataset is large enough to fit on the volume but does not leave enough space for the VVDS. To compound the issue, IGG0325B will set the DS4VVDSA bit indicating there is a VVDS even though the allocation request for the VVDS failed with IEC331I 050-012. This setting of this bit when there is no VVDS will cause all future best-fit requests to fail with the same messages. This apar was created to close the window and ensure the DS4VVDSA bit is only set after a successful VVDS allocation. This APAR will need to be applied with OA39074.
Local fix
Ensure a VVDS is allocated to all volumes that had experienced the IEC331I error message.
Problem summary
**************************************************************** * USERS AFFECTED: The first allocation of a non-VSAM dataset * * that is big enough to fit a volume, but * * fail the subsequent creation of a default * * 10-track VVDS dataset on that same volume. * **************************************************************** * PROBLEM DESCRIPTION: For every VVDS dataset exists in a * * SMS-managed volume, there is an * * indicator for the VVDS dataset in the * * Format-4 DSCB. On an empty volume, if a * * creation of a single non-VSAM dataset * * fits the volume such that it does not * * leave enough space to fit a subsequent * * creation of a VVDS dataset, DADSM will * * fail the VVDS allocation and does not * * reset VVDS indicator. * * Unless SMS volume selection can find * * a volume with VVDS already exits, SMS * * selects a volume of different size, or * * SMS re-tries the allocation after the * * user has manually allocated a VVDS * * dataset on the failing volume, the * * subsequent VVDS allocation(s) will * * continue to fail. * * However, if the single non-VSAM dataset * * does not fit the volume at all, this * * will still result in successful best- * * fit allocation of the non-VSAM dataset * * and VVDS dataset. * **************************************************************** * RECOMMENDATION: * **************************************************************** N/A
Problem conclusion
In such a case as described above, when the FMT-4 indicator for VVDS dataset did not reset correctly, DADSM could no longer reserve the space for the default 10-track VVDS dataset on that volume when there is such unique allocation. The allocation would fail unless SMS can find a bigger empty volume or an empty volume with space less than the non-VSAM dataset to avoid such window described. The FMT-4 VVDS indicator will be corrected as long as there is a successful allocation on the volume. This APAR will resolve the unique allocation problem described above by correctly resetting VVDS indicator in the FMT-4 DSCB when the allocation for VVDS fails. During the test of DADSM fix for the recreate scenario, SMS has set a non-zero return code for a successful allocation of the dataset. As a result, DADSM fix,OA38691 will require SMS fix in OA39074 to resolve the allocation completely.
Temporary fix
Comments
APAR Information
APAR number
OA42814
Reported component name
DEVICE MGMT SER
Reported component ID
5695DF133
Reported release
A10
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-07-11
Closed date
2013-10-21
Last modified date
2013-11-18
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UA71165
Modules/Macros
IGG0325B IGG0325H
Fix information
Fixed component name
DEVICE MGMT SER
Fixed component ID
5695DF133
Applicable component levels
RA10 PSY
UP
[{"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":"A10","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
18 November 2013