PK55380: ROLLUP APAR FOR LOG ANALYSIS V3.1

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• This rollup apar includes fixes for the following issues:
  1. Previously Log Analysis was generating SQL statements
     for columns defined as Character For Bit Data or
     Varchar For Bit Data in a format that may not always work.
     This PTF will convert SQL values for columns that are
     defined as Character For Bit Data and Varchar For Bit Data
     to a hexadecimal format (I.E. X'..'). This will make the
     SQL for these types of column definitions always valid.
  
  2. When the DB2 internal ids for objects can not be found
     in a stored file during the printing of the Details Report
     while in log backwards mode, an ABEND S0C4 will occur
     during error processing.
  
  3. Internally calculated space amounts for files sometimes
     exceed the maximum allowed value.
  
  4. RECORD ACCESS BIAS=SYSTEM causes VSAM ret code=x'58'
    (decimal 88).
  
  5. Code was not recognizing that the last record in an archive
     log was a spanned record and could cause errors in
     downstream processing.
     These errors include S0C4-11 in ALASBDF
  
     This occurs only in log-forward mode (pgm: ALASBDF),
     as its counterpart in log-backward mode (pgm:ALASBDB)
     did not have the missing one line of code.
  
  6. Performance enhancement to speed up the SQL generation
     process when thousands of SQL statements and many tables
     are involved.
  
     The information about each table is now being stored in
     memory for faster processing.
  
     This was also delivered in LAT v2.3 APAR PK59738.
  
  OTHER KEYWORDS:  ABENDS0C4 0C4 ABEND0C4
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of DB2 Log Analysis Tool.              *
  ****************************************************************
  * PROBLEM DESCRIPTION: This rollup apar includes fixes for     *
  *                      the following issues:                   *
  *                      1. Previously Log Analysis was          *
  *                      generating SQL statements for columns   *
  *                      defined as Character For Bit Data or    *
  *                      Varchar For Bit Data in a format that   *
  *                      may not always work. This PTF will      *
  *                      convert SQL values for columns that are *
  *                      defined as Character For Bit Data and   *
  *                      Varchar For Bit Data to a hexadecimal   *
  *                      format (I.E. X'..'). This will make the *
  *                      SQL for these types of column           *
  *                      definitions always valid.               *
  *                      2. When the DB2 internal ids for        *
  *                      objects can not be found in a stored    *
  *                      file during the printing of the Details *
  *                      Report while in log backwards mode, an  *
  *                      ABEND S0C4 will occur during error      *
  *                      processing.                             *
  *                      3. Internally calculated space amounts  *
  *                      for files sometimes exceed the maximum  *
  *                      allowed value.                          *
  *                      4. RECORD ACCESS BIAS=SYSTEM causes     *
  *                      VSAM ret code=x'58' (decimal 88).       *
  *                      5. Code was not recognizing that the    *
  *                      last record in an archive log was a     *
  *                      spanned record and could cause errors   *
  *                      in downstream processing. These errors  *
  *                      include S0C4-11 in ALASBDF. This occurs *
  *                      only in log-forward mode                *
  *                      (pgm: ALASBDF), as its counterpart in   *
  *                      log-backward mode (pgm:ALASBDB) did not *
  *                      have the missing one line of code.      *
  ****************************************************************
  * RECOMMENDATION: APPLY the PTF.                               *
  ****************************************************************
  Code has been changed to correct this condition.
  

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:

  UK33176

Modules/Macros

•    ALA#MREP ALABSQL  ALACATF  ALACREP  ALADTL1
  ALAFA    ALAFR6   ALALFP   ALALF2   ALAREC2  ALASBDF  ALASLX
  H237310J
  

Fix information

• Fixed component name

  DB2 LOG ANALYSI

• Fixed component ID

  5655E6601

Applicable component levels

• R310 PSY UK33176

     UP08/02/05 P F802

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.