PI89345: POSSIBLE S0C4 IN CSECT ALALB2 WHEN DATA RECORD IS NEAR END OF BUFFER

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• A S0C4 in ALALB2 is possible when a data record is found close
  to the end of the input buffer due to trying to access data
  beyond the end of the record.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of ALA 350                             *
  ****************************************************************
  * PROBLEM DESCRIPTION: ********PI89345************************ *
  *                       A S0C4 in ALALB2 is possible when a    *
  *                      data record is found close              *
  *                      to the end of the input buffer due to   *
  *                      trying to access data                   *
  *                      beyond the end of the record.           *
  *                                                              *
  *                      *********PI89773*********************** *
  *                      If a LOB column stored in an image copy *
  *                      is 32K in size, a S0C4                  *
  *                      abend can occur in module ALADTL1       *
  *                      (csect ALALB1) if the storage           *
  *                      obtained for internal processing was    *
  *                      not contiguous.                         *
  *                                                              *
  *                      *********PI89774*********************** *
  *                      If a Fixed Format or Delimited LOADFILE *
  *                      is generated and a LOAD                 *
  *                      specification is used to limit the type *
  *                      of records that are                     *
  *                      written to the LOADFILE, some of the    *
  *                      records were still be                   *
  *                      written to the LOADFILE because the     *
  *                      LOAD specification was not              *
  *                      being checked properly for Inserts      *
  *                      and Deletes.                            *
  *                                                              *
  *                      ***********PI89818********************* *
  *                      The Fixed External and Delimited        *
  *                      LOADFILEs are created from the          *
  *                      formatted data. The ISPF front end      *
  *                      correctly sets a flag so                *
  *                      that formatting will not be skipped.    *
  *                      However, when the MODEPARM              *
  *                      file is updated the product was not     *
  *                      processing the SKIP                     *
  *                      FORMATTING option properly. When the    *
  *                      SKIP FORMATTING is set and              *
  *                      the LOADFILEs need the data formatted,  *
  *                      various issues can be                   *
  *                      encountered such as U=50 ABEND,         *
  *                      U=88 ABEND,                             *
  *                      message ALAA041E,                       *
  *                      RC=2, and possibly other issues as well *
  *                                                              *
  *                      ************PI89917******************** *
  *                      During the processing of LOBS, if the   *
  *                      LOB cannot be found, an                 *
  *                      user abend is issued. This abend was    *
  *                      being issued due to an                  *
  *                      improper test of the LOB ids to the     *
  *                      object ids found in the LOG.            *
  *                                                              *
  *                      **************************************  *
  *                                                              *
  *                                                              *
  *                                                              *
  *                                                              *
  ****************************************************************
  * RECOMMENDATION: Apply the PTF                                *
  ****************************************************************
  

Problem conclusion

• Apply the PTF
  

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:

  UI51958

Modules/Macros

•    ALAEXTF  ALALB1   ALALB2   ALALB3   ALALDEL
  ALAMDTL
  

Fix information

• Fixed component name

  DB2 LOG ANALYSI

• Fixed component ID

  5655E6601

Applicable component levels

• R350 PSY UI51958

     UP17/11/29 P F711

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.