PI33106: BACKUP SYSTEM DUMP FAILS WHEN BOTH DATA AND LOG COPYPOOL DUMPS ARE OUT OF SYNC

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Hardware changes resulted in copypools that had log
  and data out of sync.
  
  First BACKUP SYSTEM was successful. The HSM dump of the DATA
  copypool to tape was successful, the dump of the log copypool
  failed.
  
  A subsequent BACKUP SYSTEM reported success with the DATA
  copypool, but failed the log copypool because the DUMP status
  was PARTIAL instead of ALLCOMPLETE:
  
  DSNU1631I   005 14:04:52.23 DSNUVBBD - BACKUP SYSTEM UTILITY
  FAILED BECAUSE THE CALL TO DFSMSHSM FAILED WITH RC =
  X'00000006'     REASON = X'00000032'.
                         SEE THE HSM ACTIVITY LOG FOR HSM MESSAGES
  INDICATING THE  CAUSE OF THE ERROR.
  DSNU1611I   005 14:04:52.23 DSNUVBBD - A FAILURE HAS OCCURRED
  DURING BACKUP SYSTEM PROCESSING.  DFSMSHSM IS BEING
  CALLED TO DELETE THE
                         INCOMPLETE VERSION IN COPYPOOL =
  DSN$STLEC1$DB FOR TOKEN = x'tokenid'
  
  The DELETE indicated in MSGDSNU1611I does not happen when the
  DUMP option has been specified.  This lack of delete resulted
  in subsequent failures of BACKUP SYSTEM, including BACKUP
  SYSTEM...FORCE
  
  MSGDSNU1631I
  

Local fix

• manually delete the failed copypools with the FRDELETE command
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS      *
  *                 users of BACKUP SYSTEM utility               *
  ****************************************************************
  * PROBLEM DESCRIPTION: MSGDSNU1611I during BACKUP SYSTEM       *
  *                      after prior failure.  BACKUP SYSTEM     *
  *                      cannot be run successfully.             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
    User ran a series of BACKUP SYSTEM utility jobs while
  experiencing unexpected hardware problems with their tape
  devices.  Data supplied by the user suggested the following
  scenario took place (all BACKUP SYSTEM jobs specified DUMP
  and did NOT specify DATAONLY):
  
  BACKUP SYSTEM 1. (ended RC0)
    data copypool backup to disk: completed normally
    data copypool dump to tape:   completed normally
    log copypool backup to disk:  completed normally
    log copypool dump to tape:    unsuccessful due to h/w issue
  
  BACKUP SYSTEM 2. (ended RC8; MSGDSNU1611I)
    data copypool backup to disk: completed normally
    data copypool dump to tape:   unsuccessful due to h/w issue
    log copypool backup to disk:  failed due to incomplete dump
                                  to tape of BACKUP SYSTEM 1.
    log copypool dump to tape:    (aborted - job failure)
  
    At this point, the user reported that all subsequent attempts
  to run BACKUP SYSTEM utility failed with one or more of the
  following messages, including attempts using the FORCE keyword.
  
  MSGDSNU1610I - AN INCOMPLETE BACKUP SYSTEM HISTORY
                 ENTRY HAS BEEN FOUND IN THE BSDS, INDICATING
                 THERE MAY BE AN INVALID DATA AND
                 LOG VERSION IN COPYPOOL FOR TOKEN token.
                 DFSMSHSM WILL BE CALLED TO DELETE THE VERSION.
  
  MSGDSNU1611I - A FAILURE HAS OCCURRED DURING BACKUP
                 SYSTEM PROCESSING.  DFSMSHSM IS BEING CALLED
                 TO DELETE THE INCOMPLETE VERSION IN
                 COPYPOOL = copypool FOR TOKEN = token.
  
  MSGDSNU1631I - BACKUP SYSTEM UTILITY FAILED BECAUSE THE
                 CALL TO DFSMSHSM FAILED WITH RC = rc,
                 REASON = reason.  SEE THE HSM ACTIVITY LOG FOR
                 HSM MESSAGES INDICATING THE CAUSE OF THE ERROR.
  
    Investigation of the problem revealed that when BACKUP SYSTEM
  is run and fails with DSNU1611I for the log copypool, HSM is
  not called to delete the data copypool information as indicated
  by the message if DUMP is specified on the BACKUP SYSTEM
  statement.
    Depending on what other errors may have been previously
  encountered by BACKUP SYSTEM utility, it is possible this
  problem could leave BACKUP SYSTEM unable to run without
  first manually cleaning up errant entries via HSM.
  
  additional keywords:
  DSNU1611I DSNU1631I DSNU1610I
  

Problem conclusion

• BACKUP SYSTEM utility code was changed to invoke HSM as intended
  to clean up errant HSM entries when certain errors are
  encountered by BACKUP SYSTEM with DUMP.
  

Temporary fix

Comments

APAR Information

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

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

  UI27374 UI27375

Modules/Macros

•    DSNUVBBD
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RA10 PSY UI27374

     UP15/05/22 P F505

• RB10 PSY UI27375

     UP15/05/22 P F505

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.