|
DB2 Log Analysis Tool Version 3.3
|
|||||
| APAR | CLOSE DATE |
PTF(s) | Fixing APAR if PE |
HIPER? | Abstract |
|---|---|---|---|---|---|
2015 |
ABEND U0077 IN MODULE ALADTL4 | ||||
2015 |
ABENDU0083 IN MODULE ALAGLOAD | ||||
2015 |
U026 ABEND POSSIBLE WITH XML IN RUN AND SQL REQUESTED | ||||
2015 |
JOB FAILS WITH ALAA064E WHEN IMAGE COPY IS MISSING AND ONE WITH THE SAME LOGPOINTS EXIST | ||||
2015 |
AE PI28552 FIX COMPLETTION | ||||
2015 |
LOOP AND HIGH CPU CONSUMPTION IN GENERAL REPORT STEP | ||||
2015 |
POSSIBLE INCORRECT NUMBER OF INSERTS BEING REPORTED FROM A LOAD REPLACE | ||||
2015 |
DISCOVER MAY FAIL IF CLIST LIBRARY NAME IS LONG | ||||
2014 |
ALAA304I NO DB2 LOGS WERE READ | ||||
2014 |
ALAA447E WITH LOAD LOG YES UTILITY AND MULTIPLE SUBSEQUENT UPDATES TO THE SAME ROW | ||||
2014 |
SDC2 ABEND WHEN SAVE POINTS ARE PRESENT | ||||
2014 |
RACF FAILURE (ICH408I) WHEN OPENING DB2 LOGS | ||||
2014 |
MESSAGE ALAA506E INCORRECTLY GENERATED | ||||
2014 |
ABEND S0C4 IN ALASUBG WHEN MANY REMEMBER COORDINATOR LOG RECORDSARE PROCESSED | ||||
2014 |
SQL ERRORS NOT BEING DISPLAYED FOR PROFILES | ||||
2014 |
ERROR HANDLING GIVES AN ALAA500E MESSAGE. | ||||
2014 |
SET CURRENT SQLID DOES NOT WORK WHEN GENERATING JCL FOR ONE PHASE MODE | ||||
2014 |
ABEND U=0031 IN MODULE ALADTL2 | ||||
2014 |
ISPF ABENDS0C7 IN MODULE ALAISPMN | ||||
2014 |
EXPERT MODE END LOGPOINT NOT BEING USED | ||||
2014 |
ALAA447E ERROR MESSAGE IN LOG BACKWARD MODE | ||||
2014 |
ABENDS013 ON MODEFILE DURING GENERAL REPORT STEP | ||||
2014 |
ABENDU0071 IN MODULE ALADTL2 | ||||
2014 |
S0C4 ABEND IN ALAGEN1 | ||||
2014 |
ABENDS0C1 WHEN USING EXPERT OPTIONS | ||||
2014 |
ARCHIVE LOG ACCESS MAY BE FURTHER BACK IN TIME THAN NECESSARY | ||||
2014 |
USER ABENDU022 WITH COMPRESSION DICTIONARY | ||||
2014 |
CORRECTING THE DEFAULT IMAGE COPY PROCESSING TO LOCALSITE IF ZPARM INFORMATION CAN NOT BE FOUND. | ||||
2014 |
SOME ISPF PANELS ARE NOT ALLOWING ACCESS TO ALL FIELDS WHEN PF KEYS ARE BEING DISPLAYED. | ||||
2014 |
ALAA419I: CHAR CONVERSIONS ENDED | ||||
2014 |
VARIOUS ISSUES AFTER QUIESCING A SUBSYSTEM IN A DATA SHARING ENVIRONMENT WHILE RUNNING IN CONTINUOUS MODE | ||||
2013 |
ABEND S0C4 USING EXPERT OPTIONS | ||||
2013 |
INCORRECT OUTPUT POSSIBLE WITH MULTIPLE LOAD REPLACES | ||||
2013 |
ABENDU55 AND ABENDS0C4 ABEND USING 64 BIT MODE | ||||
2013 |
MESSAGE IEC190I IN LOG ANALYSIS JOB WHEN RUNNING ON Z/OS 2.1 | ||||
2013 |
VARIOUS ABENDS ASSOCIATED WITH LOB/XML COLUMNS ABENDU022 ABENDU047 ABENDU050 | ||||
2013 |
ADD ABILITY TO CREATE LOADFILE IN DELIMITED OUTPUT FORMAT | ||||
2013 |
HIGH CPU AND ELAPSED TIMES DURING HIGH SPEED MODE RUN | ||||
2013 |
PERFORMANCE MAY BE SLOW WITH LOAD LOG YES PRESENT | ||||
2013 |
ERROR MSG ALAA041E-CATFILE LOOKUP ERROR | ||||
2013 |
QUIET TIME REPORT INACCURATE UNDER CERTAIN CONDITION | ||||
2013 |
ALAA070W-UNCOMMITTED URID FOUND AND BYPASSED | ||||
2013 |
GENERAL REPORT NOT PROPERLY SKIPPING RECOVER TIMERANGE. | ||||
2013 |
ALAA156I: BU- MESSAGE | ||||
2013 |
END TIME RANGE CALCULATED INCORRECTLY WHEN USING RESOLVE UOW | ||||
2013 |
POSSIBLE INVALID JCL STATEMENT IF ADVANCED FILTERS BYPASSED AFTER SELECTING ADVANCED FILTERS | ||||
2013 |
POSSIBLE ALAA447E ALAA440E WHEN USING SHRLVL=CHANGE IMAGE COPY | ||||
2013 |
IDMAP REPORT MAY DROP LAST CHARACTER OF DBNAME AND / OR TSNAME | ||||
2013 |
ABENDOC4 DURING TABLE VERSIONING PROCESS WHEN AN EMPTY SYSOBD PAGE IS ENCOUNTERED | ||||
2013 |
XML DATA GENERATED MAY CONTAIN INVALID CHARACTERS | ||||
2013 |
ABEND0C4 IN MODULE ALASBDF | ||||
2013 |
POSSIBLE LOOP WHEN READING LOGS USING LSRN RANGES AND SOME ACTIVE LOGS ARE EMPTY | ||||
2013 |
EXCLUDED OBJECT FILTERS MAY FAIL WITHIN PRECOMPILED FILTERS | ||||
2013 |
NEW TUTORIAL OPTION - RUNNING REPORTS AFTER A TIME CHANGE | ||||
2013 |
ALAA064E WHEN LOG ANALYSIS TOOL ENCOUNTERS A DESTROYED DATASHARING MEMBER. | ||||
2013 |
ALAA073E WHEN PROCESSING A ONE PAGE COMPRESSION DICTIONARY | ||||
2013 |
REPORTING ON MULTIPLE LOAD REPLACES MAY MISS INSERTS | ||||
2013 |
UNABLE TO EXCLUDE BASE/CLONE TABLES FROM FILTERS | ||||
2013 |
ABENDS0C4 IN MODULE ALAGEN1 | ||||
2013 |
ABEND0C1 OCCURS WHILE PROCESSING PRECOMPILED FILTERS | ||||
2013 |
ABEND0C4 IN ALADTL3 OR INCORRECT DETAIL REPORT OUTPUT WHEN A TABLE HAS VERSIONING. | ||||
2013 |
SOME DADSM OBTAIN CALLS MAY FAIL WHEN CALLED AGAINST EXTENDED ADDRESS VOLUMES | ||||
2013 |
ALAA419I MESSAGE AND S0C4 ABEND IN ALADTL2 ON DB2 V10 ENFM | ||||
2013 |
ABEND U=878 IN ALAGEN1 | ||||
2013 |
ABENDU0077 IN ALADTL4 WHEN PROCESSING LOBS | ||||
2013 |
ABEND0C4 ABEND IN ALADTL1 WHEN PROCESSING LOBS | ||||
2012 |
ADDITIONAL INFORMATION IS BEING SUPPLIED FOR ALAA440E AND ALAA447E MESSAGES | ||||
2012 |
RUNNING A QUIET TIME REPORT THAT INCLUDES A UNIT OF WORK THAT ISSPLIT ACROSS LOGS MAY LEAD TO INVALID DATA | ||||
2012 |
ISPF PANELS RECEIVES A S0C4 ABEND WHEN MULTIPLE ADVANCED FILTERSWITHOUT COLUMNS ARE SAVED IN A PROFILE | ||||
2012 |
ALAA440E OR MISSING DATA WHEN REPORTING ON ROLLED BACK UNITS OF WORK THAT SPAN DB2 LOGS. | ||||
2012 |
ABEND U0061 IN ALADTL1 | ||||
2012 |
ABENDS0C4 IN ALAGEN1 DUE TO A CORRUPT ENTRY IN THE CONTINUOUS MODE FILE | ||||
2012 |
ABEND0C4 AND U=0088 ABEND IN MODULE ALAEXTF | ||||
2012 |
ABEND0C4 IN ALAGEN1 DURING GENERAL REPORT PHASE OF LOG ANALYSIS TOOL | ||||
2012 |
POSSIBLE S0C4 IN ALAGEN1 WHEN PROCESSING A LARGE NUMBER OF ARCHIVE LOGS THAT HAVE MANY UOW SPANNING BETWEEN THE LOG FILES. |
||||
2012 |
POSSIBLE ALAA460E COMBINED WITH S0C4 DURING LOG READING. | ||||
2012 |
THE CHANGE FLAG CAN LEAD TO FORMATTING ISSUES WHEN USED IN CONJUNCTION WITH DECFLOATS OR MASS DELETES | ||||
2012 |
RECORDS FROM LOAD UTILITY NOT BEING FLAGGED FOR IMPACT REPORT | ||||
2012 |
ADD SUPPORT FOR DB2 SORT V1.3 SORTIN/SORTOUT ENHANCEMENT | ||||
2012 |
PROGRAM HANG DURING HSM RECALL | ||||
2012 |
ABENDU066 ABEND DURING LOB MATERIALIZATION | ||||
2012 |
ABENDOC7 ABEND OR DICTIONARY MISMATCH WITH PARITITIONED COMPRESSED TABLESPACE. | ||||
2012 |
PROGRAM LOOP WHEN USING HIGH SPEED MODE | ||||
2012 |
ALAA011E NOT BEING ISSUED WHEN REQUESTED LOGRANGE IS NOT IN THE BSDS | ||||
2012 |
ABENDC03 AND ALAA041E WHEN PRODUCING AN AUDIT LOAD FILE | ||||
2012 |
ALAA040E-UNSUCCESSFUL PUT FOR ROWDATA DD | ||||
2012 |
ABENDU0031 ABEND WHEN TRYING TO FIND A DB2 V10 COMPRESSION DICTIONARY IN A PARTITION TABLESPACE OF TYPE LARGE | ||||
2012 |
ALAA073E IS POSSIBLE IN HISPEED WHEN PROCESSING ACTIVITY PRIOR TO A REORG THAT REBUILT THE DICTIONARY | ||||
2012 |
ABENDC03 ABEND WHEN REQUESTING CONTINUOUS MODE REPORT AND RUNNING IN 1 PHASE MODE | ||||
2012 |
GENERATING SQL BY UNIT OF WORK IN TWO PHASE MODE BYPASSES A POTENTIAL DB2 SORT | ||||
2012 |
TCZ INSTALLATION ISSUES | ||||
2012 |
COMMIT FREQUENCY REPORT SOMETIMES DROPPING LAST CHARACTER OF DBNAME AND/OR TSNAME. | ||||
2012 |
CHANGE IN DB2VER PARAMETER FORMAT IN PRODUCT BIND JOB | ||||
2012 |
EXCLUDED OBJECT FILTERS MAY NOT BE EXCLUDED, DEPENDING ON ORDER | ||||
2012 |
POSSIBLE MISSING UOW WHEN UOW SPANS LOG FILES WHEN PROCESSING IN CONTINUOUS MODE. | ||||
2012 |
MODIFICATION OF ERROR MESSAGE TO DISPLAY INFORMATION FROM TICSPECS DD | ||||
2012 |
UNDER CERTAIN CIRCUMSTANCES USE OF ARCHLOG2 INSTEAD OF ARCHLOG1 WHEN ARCHLOG1 SHOULD HAVE BEEN USED. | ||||
2012 |
THE CUSTOMIZE AUDIT TABLE PANEL DISPLAYED WHEN SPECIFYING AUDIT TABLE OPTIONS HAS 'PLAN NAME' AND 'JOB NAME' FIELDS REVERSED. | ||||
2012 |
TABLE OWNER BEING LISTED TWICE IN ADVANCED FILTER ERROR WHEN AN EXTRA COND PARAMETER IS USED. | ||||
2012 |
U66 ABEND WHILE RE-LOADING LOB DATA | ||||
2012 |
POSSIBLE S0C4 WHEN PROCESSING LOAD LOG YES DURING DROPPED OBJECTMODE. | ||||
2012 |
ALAA047E CAF ERROR WHEN GENERATING SQL WITH KEYED WHERE CLAUSE | ||||
2012 |
CHANGE BIND PROC ALABINDC DEFAULTS TO REDUCE BIND OUTPUT | ||||
2012 |
ABENDS0C4 WHEN PROCESSING ROLLBACK TO SAVEPOINT LOG RECORDS IN A CONTINUOUS MODE JOB | ||||
2012 |
SOME INSTANCES OF A U0078 ABEND ARE BEING CONVERTED TO AN ALAA447E MESSAGE | ||||
2012 |
USING A USER CREATED COLUMN TYPE BASED ON FLOAT MAY LEAD TO U=50ABEND. | ||||
2012 |
U=89 ABEND WHEN DIRECTORY BLOCKS ARE FULL IN LOB PDS IS CHANGINGTO ALAA575E MESSAGE | ||||
2012 |
ALAA447E MAY OCCUR WITH 32K PAGE IN REORG LOG YES | ||||
2012 |
SHRLEVEL CHANGE IMAGE COPY RESULTING IN ALAA447E / ALAA440E | ||||
2012 |
ABENDS0C7 DURING DECOMPRESSION IF REORG LOG(YES) DICTIONARY RECORD SPANS LOGS. | ||||
2012 |
SQL GENERATED WHEN A ROW CHANGE TIMESTAMP WAS THE ONLY COLUMN CHANGED IN AN UPDATE | ||||
2012 |
ABEND0C4 WHEN PROCESSING A UOW THAT SPANS MULTIPLE LOGS AND HAS ROLLBACK TO SAVEPOINT ENTRIES | ||||
2012 |
DUPLICATE LRSNS CAN CAUSE VARIOUS LOG ANALYSIS TOOL PROBLEMS. | ||||
2012 |
LOG ANALYSIS TOOL MAY HANG AFTER B37 ON EXTFILE | ||||
2012 |
ABENDU55 OR ALAA447E POSSIBLE WHEN USING UTILITIES WITH LOG YES OPTION AND TABLE VERSIONING HAS OCCURRED. | ||||
2012 |
HELP PANEL UPDATES -FAST APPLY SQL COMMIT FREQUENCY FIELD, GENERAL REPORT PANEL HELP TYPO AND NON EBCIDIC DATA HANDLING | ||||
2011 |
ADVANCED FILTERS NOT WORKING WITH 32K RECORDS | ||||
2011 |
ABENDS0C4 USING EXCLUDE OBJECT FILTERS | ||||
2011 |
ADVANCED FILTERS ON VARIABLE LENGTH COLUMNS WITH NULLABLE VALUESNOT WORKING PROPERLY | ||||
2011 |
POSSIBLE ALAA157E WHEN TRYING TO DETERMINE THE LOG PROCESSING MODE WHEN THE LOG READING MODE IS AUTO | ||||
2011 |
MESSAGE ALAA064E WHEN A MIXTURE OF IMAGE COPIES FOR LOBS AND BASE TABLES ARE STACKED ON THE SAME TAPE | ||||
2011 |
POSSIBLE DROPPED RECORDS IN DETAIL REPORT WHEN RUNNING HI SPEED MODE WITH EXCLUDE OBJECT FILTERS | ||||
2011 |
ABENDS0C1 IN ALADTL1 IF LOG ANALYSIS RUN INDICATES VERSIONING IS PRESENT IMAGE COPIES CONTAINS DUPLICATE PAGES NOT IN ORDER | ||||
2011 |
FIXES FOR MULTIPLE ABENDSOC4 AND SQLCODE117 | ||||