PM70622: INCORRECT DDNAME IN DFS3257I AT /SWI WADS FAILURE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When WADS Open error happened during /SWI WADS in DUAL WADS
  environment, DDNAME in DFS3257I message had garbage.
  ---------------------------------------
  < Case-1; secondary WADS open error while switch >
   /DIS OLDS.
         WADS = *DFSWADS0 *DFSWADS1 DFSWADS2 DFSWADS3
   V D74E,OFFLINE,FORCE  (WADS3 volume offline)
   /SWI WADS.
   DFS3261I WRITE AHEAD DATA SET NOW ON DFSWADS2 IMP1
   IOS000I D74E,**,SIM,**,**06,,,I7OLDT,IMSVPA1
   IEC143I 213-04,IFG0194D,IMSVPA1,IMSVPA1,DFSWADS3,D74E,I7OLDT,
   IMS12VP.A0.WADS3
   DFS3256I OPEN/ALLOCATION FAILED ON DFSWADS3 IMP1
   DFS3262I NO DATA SET AVAILABLE FOR LOG WRITE AHEAD IMP1
   DFS3261I WRITE AHEAD DATA SET NOW ON DFSWADS0 IMP1
   DFS3261I WRITE AHEAD DATA SET NOW ON DFSWADS1 IMP1
   DFS3273I UNABLE TO PROCESS SWI COMMAND FOR DFSWADS0, REASON
   CODE 03                                    ========
   DFS3257I WADS DEALLOCATED ON DFSWADST IMP1
                                       =   ->  X'E3'
   DFS058I 10:35:36 SWITCH COMMAND COMPLETED IMP1
   /DIS OLDS.
         WADS = *DFSWADS0 *DFSWADS1 DFSWADS2
  ---------------------------------------------------------
  < Case-2; primary WADS open error while switch >
   /DIS OLDS.
         WADS = *DFSWADS2 *DFSWADS3 DFSWADS0 DFSWADS1
   V 5030,OFFLINE,FORCE  (WADS0 volume offline)
   /SWI WADS.
   IOS000I 5030,**,SIM,**,**06,,,I6TST1,IMSVPA1
   IEC143I 213-04,IFG0194D,IMSVPA1,IMSVPA1,DFSWADS0,5030,I6TST1,
   IMS12VP.A0.WADS0
   DFS3256I OPEN/ALLOCATION FAILED ON DFSWADS0 IMP1
   DFS3261I WRITE AHEAD DATA SET NOW ON DFSWADS1 IMP1
   DFS3262I NO DATA SET AVAILABLE FOR LOG WRITE AHEAD IMP1
   DFS3261I WRITE AHEAD DATA SET NOW ON DFSWADS1 IMP1
   DFS3261I WRITE AHEAD DATA SET NOW ON DFSWADS2 IMP1
   DFS3273I UNABLE TO PROCESS SWI COMMAND FOR DFSWADS1, REASON
   CODE 03                                    ========
   DFS3257I WADS DEALLOCATED ON DFSWADS  IMP1
                                       =  -> X'E0'
   DFS058I 10:44:13 SWITCH COMMAND COMPLETED IMP1
   /DIS OLDS.
         WADS = *DFSWADS1 *DFSWADS2 DFSWADS3
  ----------------------------------------------------------------
  There seems to be three problems in above cases.
  1. DDNAME in DFS3257I was wrong.
     The last byte of DDNAME was X'E3' for DFSWADS3, X'E0' for
     DFSWADS0.
  2. WADS switch behavior is not consistent.
    Case-1;  Tried to switch from WADS pair of 0 and 1 to 2 and 3,
     but got open failure of WADS3.
     Finally, WADS0 and 1 were assigned.
     This looks like as /SWI WADS was aborted ???
    Case-2;  Tried to switch from WADS pair of 2 and 3 to 0 and 1,
     but got open failure of WADS0.
     Finally, WADS1 and 2 were assigned.
     This case, /SWI WADS was not aborted...
  3. DDNAME in DFS3273I is not consistent ?
    Case-1; DFSWADS0 was issued.
    Case-2; DFSWADS1 was issued.   Why not WADS2 ?
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All IMS V11 users who use write-ahead data   *
  *                 sets (WADS)                                  *
  ****************************************************************
  * PROBLEM DESCRIPTION: Incorrect DD names in msgDFS3273I and   *
  *                      msgDFS3257I when a failure is           *
  *                      encountered at WADS-switch time.        *
  *                                                              *
  *                      Also,when using dual WADS and a         *
  *                      failure occurred on 1 of the new WADS,  *
  *                      the behavior was inconsistent as to     *
  *                      whether or not the entire switch was    *
  *                      aborted or if one of the old active     *
  *                      was also used as a new active.          *
  ****************************************************************
  * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
  ****************************************************************
  The code was changed to fix the incorrect DD names. Code was
  also added to make the behavior consistent when 1 WADS in a dual
  WADS environment encountered an error while switching. The
  behavior after applying this APAR is that if there aren't enough
  WADS to satisfy the complete switch (that is, the 2 new WADS are
  different than both of the 2 old WADS), then the switch process
  is aborted and the original 2 WADS remain the active WADS.
  

Problem conclusion

• GEN:
  KEYWORDS:
  
  *** END IMS KEYWORDS ***
  To correct the DD names in msgDFS3273, code was added to label
  SWTCHW60 in DFSFDLS0 to interrogate the WADS availability matrix
  (LBWADSX) before and after the call to WADSOPEN to see which
  WADS DDs are unavailable after the switch. Then, msgDFS3273 is
  issued for each of the WADS DDs for which there was a failure.
  
  On return from WADSOPEN, if the LFPWADS bit is turned off,
  indiciating a failure to find sufficient spare WADS, then
  the WADS switch is aborted, and the original WADS before the
  switch are re-opened and used.
  
  One line of code had to be added to the WADSOPEN routine in
  DFSFDLG0 to support this change. Previously, R8 was the same
  upon exiting DFSFDLG0 and coming back in. This wasn't the case
  after this change, so addressability for R8 had to be
  re-established.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

  PM61355

• APAR is sysrouted TO one or more of the following:

  UK81464

Modules/Macros

• DFSFDLG0 DFSFDLS0
  

Fix information

• Fixed component name

  IMS V11

• Fixed component ID

  5635A0200

Applicable component levels

• R100 PSY UK81464

     UP12/09/08 P F209

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.