A fix is available
APAR status
Closed as program error.
Error description
This APAR addresses the following issues: 1. Possible missing uncommitted unit of works when special type of log record are met in Db2 v12 non Data sharing environment when running in continuous mode. 2. Possible S0C4, S0C6 abends when generating the JCL with misc filters using ISPF. 3. Possible S0C4 in ALADTL4 when reporting large amount of deletes in table containing LOB column and requesting UNDO SQL generation. 4. Incorrect ALAA011E when Impact report is chosen in Data Sharing environment with one member. 5. Possible incorrect behavior when Impact report is chosen and subsystem has STCK to LRSN delta. 6. Possible S0C4 in ALADTL3 when requesting Detail Impact report 7. Possible ALAA157E when LRSN has an overflow to the highest byte and Log Backward is selected by the tool. 8. Possible ALAA053E for ALACLDEL and ALATSC on data sets that were allocated on TAPE units
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of Db2 Log Analysis Tool for z/OS * **************************************************************** This APAR addresses the following issues: 1) Possible missing uncommitted unit of works when special type of log record are met in Db2 v12 non Data sharing environment when running in continuous mode. 2) Possible S0C4, S0C6 abends when generating the JCL with misc filters using ISPF. 3) Possible S0C4 in ALADTL4 when reporting large amount of deletes in table containing LOB column and requesting UNDO SQL generation. 4) Incorrect ALAA011E when Impact report is chosen in Data Sharing environment with one member. 5) Possible incorrect behavior when Impact report is chosen and subsystem has STCK to LRSN delta. 6) Possible S0C4 in ALADTL3 when requesting Detail Impact report 7) Possible ALAA157E when LRSN has an overflow to the highest byte and Log Backward is selected by the tool. 8) Possible ALAA053E for ALACLDEL and ALATSC on data sets that were allocated on TAPE units
Problem conclusion
Apply the PTF
Temporary fix
Comments
APAR Information
APAR number
PH32445
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
2020-12-07
Closed date
2021-01-22
Last modified date
2021-02-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI73581
Modules/Macros
ALA@FSP ALAAC ALAAFWC ALAAFWR ALAARC1 ALAARC2 ALABSQL ALABSSQL ALACATF ALACDF ALACDICT ALACFREP ALACFRR ALACLDEL ALACREP ALACRRF ALACTAU ALACURR ALADELER ALADSNM ALADSPG ALADSUM ALADTS ALAERRIN ALAETV ALAEXP ALAEXPI ALAFCP ALAFR12 ALAFRMTR ALAFTC ALAGEN1 ALAGENR ALAGLOAD ALAIDRP ALAIR2 ALAIXP ALALAUD ALALB3 ALALF1 ALALF1A ALALF1B ALALF2 ALALF3 ALALF3W ALALF4 ALALFP ALALLB ALALPD ALAMDTL ALAMLOB ALAMLS ALAMPR2 ALAMPRT ALAMSP ALAPEXP ALAPGR ALAPGR2 ALAPSB ALARDR ALAREC ALAREC2 ALAREC3 ALAREC3W ALARRFC ALARXML ALASBDB ALASBDF ALASLX ALASQL1B ALASQL2B ALASUBG ALATC ALATSC ALATV ALATVF ALATVRP ALAUNCRE ALAVBIO ALAVRD
Fix information
Fixed component name
DB2 LOG ANALYSI
Fixed component ID
5655E6601
Applicable component levels
R350 PSY UI73581
UP21/01/27 P F101
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.
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Platform":[{"code":"PF054","label":"z\/OS"}],"Version":"3.5.0"}]
Document Information
Modified date:
02 February 2021