II06122: A DATA SET NAME REFERBACK TO A DATA SET CREATED IN A BYPASSED STEP CAN RESULT IN MSGIEF212I.

APAR status

• Closed as canceled.

Error description

• A customer submitted the following JCL:
  {
  //JOB1 JOB MSGLEVEL=(1,1)
  //STEP1 EXEC PGM=PGM1
  //STEP2 EXEC PGM=PGM2,COND=(0,EQ,STEP1)
  //DD2 DD DSN=&&TEMP,DISP=(NEW,PASS),UNIT=SYSDA,SPACE=(TRK,1)
  //STEP3 EXEC PGM=PGM3,COND=(0,NE,STEP1)
  //DD3 DD DSN=&&TEMP,DISP=(NEW,PASS),UNIT=SYSDA,SPACE=(TRK,1)
  //STEP4 EXEC PGM=PGM4
  //DD4   DD   DSN=*.STEP2.DD2,DISP=(OLD,DELETE)
  {
  After MVS R420 this job will fail intermittenly with MSGIEF212I
  if PGM1 executes with a condition code of zero.  Before MVS
  R420 this job would always run successfully.
  {
  Note that when PGM1 executes with a condition code of zero
  STEP2 is bypassed.  Therefore, DD4 is attempting to receive
  the data set created in STEP3 (DD3) but DD4 refers to STEP2
  (DD2) in order to obtain the data set name.
  {
  Before MVS R420 the temporary data set name generated by the
  system for DD2 and DD3 would always match.  Therefore the data
  set name referback in DD4 would always work.  At MVS R420
  support was introduced for unique temporary data set names for
  APPC.  As a result the temporary data set name generated by the
  system for DD2 and DD3 may not always match.  The following
  restriction has always been documented in the JCL Reference
  where the COND parameter is described:
  {
  Backward References to Data Sets:  If a step is bypassed because
  of its COND parameter or if a step abnormally terminates, a
  data set that was to have been created or cataloged in the
  step may not exist, may not be cataloged, or may be incomplete.
  Thus, a job step should not refer to a data set being created
  or cataloged in a step that could be bypassed or abnormally
  terminated.
  {
  In order to resolve this problem it is suggested that the DSN
  name keyword in STEP4 (DD4) be changed to DSN=&&TEMP.
  {
  Also note that while this structure is not officially supported
  APAR OY55228 will be removing the allocation data set name
  function and therefore the invalid specification should work
  again as it did prior to R420.  In no way is this a guarantee
  that this JCL construct will always work as it did prior to
  R420.
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• Closing informational APAR.
  

APAR Information

• 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