A fix is available
APAR status
Closed as program error.
Error description
This APAR addresses the following issues: 1. Possible 0C4 in ALADTL1 when the Log Analysis tool is using SYSLGRNX in Detail report for large amount of objects. 2. Possible -181 SQL error, when Db2 Catalog tables contain timestamps of invalid '0000-00-00-00.00.00.000000' values and these values are used by the tool in next queries. 3. Possible excessive fallback to IC when processing utility log records. 4. Incorrect values displayed for SGSZ on IDMAP report 5. Incorrect values displayed for DSNUM, LDSNUM, HDSNUM on SYSCOPY report 6. Possible SOC4 in ALASUBG/ALASUBGC when generating Quiet Time report 7. Possible missing data in between continuous mode runs, when transaction is not finished by the end of the first JOB.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of Db2 Log Analysis Tool for z/OS * **************************************************************** * PROBLEM DESCRIPTION: 1) Possible 0C4 in ALADTL1 when * * the Log Analysis tool is using * * SYSLGRNX in Detail report for large * * amount of objects. * * * * 2) Possible -181 SQL error, when * * Db2 Catalog tables contain * * timestamps of invalid * * '0000-00-00-00.00.00.000000' values * * and these values are used by * * the tool in next queries. * * * * 3) Possible excessive fallback * * to IC when processing utility * * log records. * * * * 4) Incorrect values displayed * * for SGSZ on IDMAP report * * * * 5) Incorrect values displayed * * for DSNUM, LDSNUM, HDSNUM * * on SYSCOPY report * * * * 6) Possible SOC4 in ALASUBG/ALASUBGC * * when generating Quiet Time report * * * * 7) Possible missing data in between * * continuous mode runs, * * when transaction is not finished * * by the end of the first JOB. * **************************************************************** * RECOMMENDATION: Apply the PTF * **************************************************************** Various fixes for Log Analysis Tool V3.5.0
Problem conclusion
Apply the PTF
Temporary fix
Comments
APAR Information
APAR number
PH42570
Reported component name
DB2 LOG ANALYSI
Reported component ID
5655E6601
Reported release
350
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2021-12-06
Closed date
2022-01-25
Last modified date
2022-02-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI79052
Modules/Macros
ALA#ERRM ALA#LCLF ALA#LDSN ALA#STOR ALA#WTO ALACLDEL ALACTAU ALADB2SP ALADTL3 ALAFMAIN ALAGEN1 ALAHRC ALAIDRP ALAJSON ALALF1 ALAMODEM ALAQT ALASETUP ALASLX ALASQ1CA ALASQ1CB ALASQ9CA ALASQL0 ALASQL0A ALASQL0B ALASQL1 ALASQL1A ALASQL1B ALASQL1C ALASQL2 ALASQL2A ALASQL2B ALASQL9 ALASQL9A ALASQL9B ALASQL9C ALASRPT ALATSC ALAUTIL ALAVBIO ALAVSTR
Fix information
Fixed component name
DB2 LOG ANALYSI
Fixed component ID
5655E6601
Applicable component levels
R350 PSY UI79052
UP22/01/27 P F201
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.
[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSZJXP","label":"DB2 Tools for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.5.0"}]
Document Information
Modified date:
02 February 2022