APAR status
-
Closed as fixed if next.
Error description
-
Job that uses GDG data set fails with msgIEF211I DATA SET RESERVATION UNSUCCESSFUL. For example: While JOB1 was running, //stepname EXEC PGM=pgmname //ddname DD DSN='DSN.STL(0)',DISP=OLD (notice that the above DSN is in quotes) JOB2 got IEF211I. //stepname EXEC PGM=COD0220 //ddname DD DSN=DSN.STL(0),DISP=SHR (notice that the above DSN is NOT in quotes) ==> IEF211I JOB2 stepname ddname - DATA SET RESERVATION UNSUCCESSFUL. IEF272I JOB2 stepname - STEP WAS NOT EXECUTED. JOB1 issues ENQs for: DSN.STL(0) - because the DSN is in quotes and also for (e.g.) DSN.STL.G0001V00 JOB2 issues ENQs for: DSN.STL and also for (e.g.) DSN.STL.G0001V00 Both JOB1 and JOB2 will attempt to use (e.g.) DSN.STL.G0001V00, but JOB1 should REALLY attempt to use DSN.STL(0) -- which most likely does not exist. If a relative generation name is enclosed in apostrophes e.g. 'gdgname(0)' an ENQ is properly issued on that exact dataset name at job initiation time. But then at step allocation time the DSN is treated as if it were NOT in apostrophes, the relative GDG name is expanded to an absolute GDG name, and an ENQ is issued for that fully-qualified G0000V00 name. A relative GDG name in quotes should NOT be treated as a generation dataset (GDS) and an ENQ for the fully-qualified G0000V00 should NOT be issued. Additional Keywords: apostrophe quote enqueue
Local fix
Problem summary
-
**************************************************************** * USERS AFFECTED: All HBB7703 and above installations who * * use quoted Relative GDG names. * * * **************************************************************** * PROBLEM DESCRIPTION: Premature job ending with message * * IEF211I issued. * * * **************************************************************** * RECOMMENDATION: * **************************************************************** A job my end prematurely with message IEF211I issued when Allocation attempts to process a quoted GDG Releative Generation name.
Problem conclusion
Temporary fix
Comments
-
This APAR is being closed FIN with concurrence from the submitting customer. A solution to this problem will be delivered from IBM in a Release (if any) to be available within 18 months. The fix for the defect described in this APAR has been shipped in z/os V1R5. (Correction on 10/19/05: z/OS V1R6.)
APAR Information
-
APAR number
OA01622
-
Reported component name
5752 ALLOC/UNAL
-
Reported component ID
5752SC1B4
-
Reported release
608
-
Status
CLOSED FIN
-
PE
NoPE
-
HIPER
NoHIPER
-
Special Attention
NoSpecatt / Xsystem
-
Submitted date
2003-01-15
-
Closed date
2003-02-14
-
Last modified date
2005-10-19
-
APAR is sysrouted FROM one or more of the following:
-
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Platform":[{"code":"PF054","label":"z\/OS"}],"Version":"608"}]
Document Information
Modified date:
30 March 2021