PM63979: ABEND0C4 DSNUULCA -- UNLOAD FROM IMAGE COPY

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• While customer tried to unload from an imagecopy, unload utility
  floods the spool with DSNU1239I messages(VERSION X'0000' OBDREC
  WAS NOT FOUND IN OBID X'006A') and DSNU1219I(THE NUMBER OF
  RECORDS IN ERROR REACHED THE LIMIT 1).
  If add MAXERR integer(>=2) to limit the maximum number of
  records in error, utility would abend with 0C4 at
  DSNUTILA.DSNUULCA. It also may cause DB2 crash.
  

Local fix

• N.A.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users *
  *                 of UNLOAD with FROMCOPY/FROMCOPYDDN option.  *
  ****************************************************************
  * PROBLEM DESCRIPTION: Message spool flooded by MSGDSNU1239I   *
  *                      and MSGDSNU1219I messages during an     *
  *                      UNLOAD FROMCOPYDDN, and abended with    *
  *                      ABENDS0C4 RC00000038 at DSNUULCA        *
  *                      OFFSET7074 if MAXERR integer(>=2) was   *
  *                      specified, and then the DB2 subsystem   *
  *                      abended with ABEND04E RC00E20028 along  *
  *                      with the message DSNV086E - DB2         *
  *                      ABNORMAL TERMINATION REASON=00F30801.   *
  ****************************************************************
  * RECOMMENDATION: Apply corrective PTF when available.         *
  ****************************************************************
  User procedures caused DSNU1239I - VERSION version-number OBDREC
  WAS NOT FOUND IN OBID object-id during an UNLOAD FROMCOPYDDN.
  This message along with DSNU1219I - THE NUMBER OF RECORDS
  IN ERROR REACHED THE LIMIT nnnn were issued too many times and
  flooded the message spool if no MAXERR specified or MAXERR 1.
  If MAXERR integer(>=2), the UNLOAD abended with ABEND0C4 RC38
  at DSNUULCA + x'7074' on DB2 9 for z/OS and ABEND0C4 RC11 at
  DSNUULCA + x'3B4A' on DB2 10.  It may lead to the DB2 subsystem
  abnormally terminated with ABEND04E RC00E20028 and MSGDSNV086E
  - DB2 ABNORMAL TERMINATION REASON=00F30801.
  This problem occurred because UNLOAD was not handling the return
  code correctly and issuing messages for every single record,
  including beyond the MAXERR value.
  

Problem conclusion

• UNLOAD code has been modified to correct the reported problems.
  And if MAXERR is 0 or greater than 2000, UNLOAD will now stop
  issuing the DSNU1239I message once 2000 of them have been
  issued and issue MSGDSNU1140I stating this fact but will still
  continue processing until MAXERR has been reached.
  
  This APAR also introduces the following changes to the
  Messages publication:
  Description change for message DSNU1140I:
  DSNU1140I
  csect-name MESSAGE LIMIT OF max-messages HAS BEEN REACHED FOR
  message-number MESSAGES. NO MORE WILL BE ISSUED FOR THIS UTILITY
  
  Explanation
  The number of instances of the indicated message issued during a
  utility operation has exceeded the maximum number permitted.
  
  csect-name
  The name of the control section that issued the message.
  
  max-messages
  The maximum number of messages that are issued before this
  message is issued. This value is controlled by the utility that
  issues message DSNU1140I.
  
  message-number
  The message number that has reached the limit and is now
  suppressed.
  
  | Example 1: The LOAD utility issues message DSNU1140I after
    2000 instances of any of the following messages: DSNU313I,
    DSNU314I, DSNU1103I, or DSNU1104I. Any rows that would have
    triggered the suppressed message are still discarded.
  
  | Example 2: The UNLOAD FROMCOPY/FROMCOPYDDN issues message
  | DSNU1140I after 2000 instances of message DSNU1239I, when
  | MAXERR is specified to greater than 2000 or 0. Any rows that
  | would have triggered the suppressed message are still not
  | unloaded.
  
  System action
  Processing continues.
  
  No additional instances of message-number messages are issued.
  Only the issuance of the message is suppressed. Any action that
  is associated with the suppressed message number still occurs.
  
  User response
  No action is required.
  Severity
  0
  

Temporary fix

• *********
  * HIPER *
  *********
  

Comments

APAR Information

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

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

  UK79770 UK79771

Modules/Macros

• DSNUULCA DSNUULCB
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RA10 PSY UK79770

     UP12/07/14 P F207

• R910 PSY UK79771

     UP12/07/14 P F207

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.