PH68537: VARIOUS FIXES FOR LOG ANALYSIS TOOL V3.5

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Filter processing optimization when 'Include LOB/XML = Y'
  Fixed possible S0C4 on processing FLASH COPY of the LOB
  TABLESPACE
  Fixed possible incorrect data in the DELETE record in Details
  report when processing MASS DELETE.
  Fixed possible ISPP118 error on ALAAA5G panel.
  Fixed possible incorrect MODEFILE population after Profiles
  using.
  Added microseconds support for Continuous file report.
  Fixed quote usage for ALAZH030 panel.
  Fixed possible excessive JCL generation for Transaction report
  when 'Write reports to datasets = Y'
  Fixed possible invalid MODEFILE generation when generation from
  Profiles used.
  Fixed possible incorrect data when a dropped columns processing
  required for a tablespace with RELATIVE PAGING.
  Fixed possible hang when specific profile have populated
  DATABASE/TABLESPACE in source/target table list.
  Fixed possible incorrect target database/tablespace population
  into JSONIN DD.
  Fixed possible ALAA073E when processing partitioned FLASH COPY
  for a tablespace with RELATIVE PAGING.
  Fixed possible incorrect calculation of the SPACE parameters
  when dynamically allocating SPLIT LOAD FILES for a tablespace
  with RELATIVE PAGING.
  Fixed possible U0055 ABEND on XML decompression for a tablespace
  with RELATIVE PAGING.
  Fixed possible S0C4 on the LOAD step of the ALAJSON.
  Fixed S0C4 when processing UTILITY in HI-SPEED with a filter by
  PART.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of Db2 Log Analysis Tool for z/OS      *
  ****************************************************************
  * PROBLEM DESCRIPTION: This APAR fixes the following problems: *
  *                      1) Filter processing optimization when  *
  *                      'Include LOB/XML = Y'.                  *
  *                      2) Possible S0C4 on processing FLASH    *
  *                      COPY of the LOB TABLESPACE.             *
  *                      3) Possible incorrect data in the       *
  *                      DELETE record in Details report when    *
  *                      processing MASS DELETE.                 *
  *                      4) Possible ISPP118 error on ALAAA5G    *
  *                      panel.                                  *
  *                      5) Possible incorrect MODEFILE          *
  *                      population after using profiles.        *
  *                      6) Added microseconds support for       *
  *                      Continuous file report.                 *
  *                      7) Quote usage for ALAZH030 panel.      *
  *                      8) Possible excessive JCL generation    *
  *                      for Transaction report when 'Write      *
  *                      reports to datasets = Y'.               *
  *                      9) Possible invalid MODEFILE generation *
  *                      when generation from profiles used.     *
  *                      10) Possible incorrect data when a      *
  *                      dropped columns processing required for *
  *                      a tablespace with RELATIVE PAGING.      *
  *                      11) Possible hang when specific profile *
  *                      have populated DATABASE/TABLESPACE in   *
  *                      source/target table list.               *
  *                      12) Incorrect target                    *
  *                      database/tablespace population into     *
  *                      JSONIN DD.                              *
  *                      13) Possible ALAA073E when processing   *
  *                      partitioned FLASH COPY for a tablespace *
  *                      with RELATIVE PAGING.                   *
  *                      14) Possible incorrect calculation of   *
  *                      the SPACE parameters when dynamically   *
  *                      allocating SPLIT LOAD FILES for a       *
  *                      tablespace with RELATIVE PAGING.        *
  *                      15) Possible U0055 ABEND on XML         *
  *                      decompression for a tablespace with     *
  *                      RELATIVE PAGING.                        *
  *                      16) Possible S0C4 on the LOAD step of   *
  *                      the ALAJSON.                            *
  *                      17) S0C4 when processing UTILITY in     *
  *                      HI-SPEED with a filter by PART.         *
  ****************************************************************
  * RECOMMENDATION: Apply the PTF                                *
  ****************************************************************
  Various fixes for Log Analysis Tool V3.5
  

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:

  UO05441

Modules/Macros

• ALABSDS  ALACDC   ALACFREP ALACLDEL ALADATA  ALADTL3  ALAETV
  ALAFCP   ALAFMAIN ALAFRCA  ALAFRDTL ALAFRGNR ALAFRMFC ALAFRMTR
  ALAFRPMC ALAFRTSC ALAFRUT  ALAGFLT  ALAGNJCL ALALB1   ALALDCR
  ALALDPN  ALALF1   ALALFCPN ALALPD   ALAMFOPN ALAMPNL  ALAQGLPN
  ALAQGRPN ALAQGSPN ALARDR   ALARM64  ALARMW   ALARXML  ALASQL2B
  ALASQL3B ALATV    ALAVLXPN ALAZH030
  

Fix information

• Fixed component name

  DB2 LOG ANALYSI

• Fixed component ID

  5655E6601

Applicable component levels

• R350 PSY UO05441

     UP25/10/23 P F510

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.