A fix is available
APAR status
Closed as program error.
Error description
Customer running restore job and has failure when a PDSE dataset is being restored and the dataset is open. Job parameters for the restore include the keyword SHARE. With the SHARE keyword, there may be a problem being able to properly serialize the target PDSE dataset during the restore process if the target PDSE is open. Various symptoms can include an abend generated from PDSE with title similar to: COMPID=DF115, CSECT=IGWIRPAD+1CA4,DATE=04/26/16,MAINTID=UA81476, ABND=0F4,RC=00000024,RSN=1419A084 This can also lead to errors being reflected in DSS, including ADR717E SYSTEM SERVICES ERROR OCCURRED WHEN RESTORING DATASET xxxx.yyyy.zzzz RETURN INFORMATION IS 01-37-000012- 00518 AND MESSAGES FOLLOW IGW01518T RESTORE FAILED FOR xxxx.yyyy.zzzz BECAUSE THE DATASET IS CURRENTLY OPEN ADR799E AN UNEXPECTED HAS OCCURRED etc.... This can also then be followed by an abend0c4 in ADRZOUT at offset x'808' due to a invalid pointer within a bitmap. The above symptoms may occur if the SHARE keyword is used during the PDSE restore process, and there is a preallocated target PDSE that is open at the time of the restore. Additional Symptoms: IGW01469T DIRECTORY ACCESS REQUEST FOR DATA SET xxxx.yyyy.zzzz FAILED WITH RETURN CODE = X'00000024', REASON CODE = X'0703003D' COMPID=DF115,CSECT=IGWBCNL2+04E8,DATE=03/25/19,MAINTID=UA98488, ABND=0F4,RC=00000024,RSN=0703003D
Local fix
Remove SHARE keyword to bypass. After application of this ptf, as SHARE keyword will be no longer honored, the ADR412E message may be issued if the dataset in in use by another process. The use of the TOL(ENQF) 'may' be used as a bypass, or the user will need to be sure that any process or application that has the PDSE enqueued has released serialization.
Problem summary
**************************************************************** * USERS AFFECTED: * * All users of DFSMSdss using RESTORE or * * COPY to process a PDSE with the SHARE * * keyword specified. * **************************************************************** * PROBLEM DESCRIPTION: * * During DFSMSdss RESTORE to a * * pre-allocated PDSE with the SHARE * * keyword specified, ADR717E was * * issued when the target data set * * was being accessed by another * * application: * * * * ADR717E SYSTEM SERVICES ERROR OCCURRED * * WHEN RESTORING DATASET * * xxxx.yyyy.zzzz RETURN INFORMA- * * TION IS 01-37-000012- * * 00518 AND MESSAGES FOLLOW * * * * During RESTORE or COPY to a * * target PDSE with the SHARE keyword * * specified, it is possible for * * another application to be updating * * the same data set on a member level * * which may result in conflicts. * * Additional * * symptoms may include: * * * * COMPID=DF115, CSECT=IGWIRPAD+1CA4, * * DATE=mm/dd/yy, MAINTID=UA81476, * * ABND=0F4,RC=00000024,RSN=1419A08 * * * * Or * * * * ADR799E AN UNEXPECTED ERROR HAS * * OCCURRED * * * * OR * * * * ABEND0C4 in ADRZOUT at offset x 808 * **************************************************************** * RECOMMENDATION: * ****************************************************************
Problem conclusion
DFSMSdss will no longer honor the SHARE keyword for a target PDSE during COPY or RESTORE. EXCLUSIVE serialization will be requested for a target PDSE. Previous jobs that relied on DFSMSdss to serialize on the target PDSE name with a SHARE enqueue will now fail serialization with ADR412E if the data set name is already serialized by another application. Releasing serialization on the target PDSE should be considered to ensure data integrity during COPY and RESTORE. If releasing serialization is not possible, there are other documented methods to bypass serialization failures though integrity cannot be guaranteed. Note: Serialization is performed on the data set name. When renaming the target, serialization is performed on the target name. When not renaming, the source and target names are the same so EXCLUSIVE serialization will be performed on that name. This means that the source PDSE may receive an ADR412E error if the data set name is already serialized or allocated by another address space. The following updates will be reflected in a future revision of the z/OS DFSMSdss Storage Administration manual (SC23-6868): Under The explanation for the SHARE KEYWORD for the RESTORE command in Chapter 17. The following paragraph should be added. The SHARE keyword is not honored for PDSEs that are targets of a RESTORE operation. This guarantees that while DSS is writing to a target PDSE, no other application can be updating that PDSE or its members. Under The explanation for the SHARE KEYWORD for the COPY command in Chapter 17. The following paragraph should be added to the note section. The SHARE keyword is not honored for PDSEs that are targets of a COPY operation. The SHARE keyword will still be honored for source PDSEs of a COPY operation. Exclusive control is obtained for a target PDSE even if the SHARE keyword is specified. Neither read access nor write access by other programs is allowed while the PDSE is being copied to. Under Chapter 21 under the Enqueuing-ENQ section, the two bullets under "The SHARE option has unique properties when applied to the following commands" will be changed as followed: - For the RESTORE command, SHARE applies to all non-VSAM data sets except for PDSEs that are targets of a RESTORE operation. The SHARE keyword does not apply to VSAM data sets. - For the DUMP and COPY commands, SHARE applies to all non-VSAM data sets, excluding PDSEs that are targets of a COPY operation. SHARE also applies to VSAM data sets that are defined with share options other than (1,3) and(1,4). Under Chapter 21 under the Enqueuing-ENQ section, The table titled "Data Set Enqueue Options for Non-VSAM Data Sets Specified on DFSMSdss Commands" will be changed to "Data Set Enqueue Options for Non-VSAM Data Sets, except for PDSEs that are targets of a COPY or RETORE operation, Specified on DFSMSdss Commands"
Temporary fix
Comments
APAR Information
APAR number
OA56300
Reported component name
DFSMSDSS, ISMF
Reported component ID
5695DF175
Reported release
220
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-10-12
Closed date
2019-04-18
Last modified date
2020-01-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UA99095 UA99103 UA99104
Modules/Macros
ADRMRRFM ADRPCNVS ADRPPRNV ADRUTDAL ADRFRLBO ADRSBRTN ADRSERLZ
| SC23686800 |
Fix information
Fixed component name
DFSMSDSS, ISMF
Fixed component ID
5695DF175
Applicable component levels
R240 PSY UA99103
UP19/05/04 P F905
R230 PSY UA99095
UP19/05/04 P F905
R220 PSY UA99104
UP19/05/04 P F905
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":"220","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
03 January 2020