|
DB2 Log Analysis Tool Version 3.5
|
|||||
| APAR | CLOSE DATE |
PTF(s) | Fixing APAR if PE |
HIPER? | Abstract |
|---|---|---|---|---|---|
2018 |
SUPPRESSION OF LEADING ZEROS IN THE DELIMITED LOADFILE | ||||
2018 |
POSSIBLE LOOP IN MODULE ALADTL1 WHEN OUT OF MEMORY CONDITION OCCURS | ||||
2018 |
ISSUE WITH TRANSACTION REPORT IN DETAIL REPORT WHEN SKIP FORMATTING = Y | ||||
2018 |
LOB / XML ISSUES WHEN GENERATING LOADFILES | ||||
2018 |
EXCLUDED XML / LOB COLUMNS STILL REQUIRE TRACKING FOR LOADFILE /SQL GENERATION | ||||
2018 |
INCORRECT BEHAVIOR WHILE READING IMAGE COPY WITH MULTIPLE PARTITIONS IN A PBR2 TABLESPACE | ||||
2018 |
ADDING ABILITY TO CONTROL REPORT SELECTION VIA MODEPARM EVEN WHEN WRITING REPORTS TO DATASETS | ||||
2018 |
PERFORMANCE IMPROVEMENT FOR UOW LOOKUP | ||||
2018 |
VARIOUS LOB / XML ISSUES RESOLVED | ||||
2018 |
MESSAGE IEC0201 001-4 OR IEC036I 002-04 ON CATFILE | ||||
2018 |
CONTROL FILE REPORT MAY INCORRECTLY SHOW LOAD LIBRARIES AS NOT APF AUTHORIZED | ||||
2018 |
ADDING SUPPORT FOR TRANSPARENT DATASET ENCRYPTION WITHIN ACTIVE DB2 LOG FILES. | ||||
2018 |
ISSUES WITH DB2 SORT WHEN A FILE SIZE EXCEEDS 65,535 TRACKS | ||||
2018 |
THE LOADCARD CAN BE GENERATED INCORRECTLY WHEN REORDERING THE DATA COLUMNS | ||||
2018 |
INCORRECT LOADCARD CAN BE GENERATED WHEN SPLITTING LOADFILES | ||||
2018 |
BIND JOB RECEIVES SQLCODE -4743 WHEN APPLCOMPAT SET IN DB2 12 LESS THAN V12R1M100 | ||||
2018 |
ALAA440E AFTER DB2 SORT FAILURE DURING ROW MOVEMENT PROCESSING | ||||
2018 |
THE SQL PROCESSOR IN LOG ANALYSIS TOOL NOT HANDLING USER DEFINEDDATATYPES FOR VARCHAR, VARGRAPHIC | ||||
2018 |
VARIOUS ISSUES WHEN MULTIPLE VERSIONS OF A TABLE EXIST | ||||
2018 |
LONG RUNNING PROCESS WHEN USING IMAGE COPIES FROM PARTITIONED TABLESPACES | ||||
2018 |
ADDING A CONTINUEIF PARAMETER TO THE GENERATED DB2 LOADFILE AND LOADCARD | ||||
2018 |
MESSAGE ALAA440E WITH SPANNED RECORDS FOR REPORTING DATA AND SPANNED RECORDS FOR DISTRIBUTED TRANSACTIONS. | ||||
2018 |
VARIOUS ISSUES WITH GENERATING A DELIMITED OR FIXED FORMAT LOADFILE WITH MULTIPLE TABLES IN A SEGMENTED TABLESPACE | ||||
2017 |
ALAA157E CAN OCCUR EVEN WHEN PROCESSING A SINGLE MEMBER OF A DATASHARING ENVIRONMENT | ||||
2017 |
ABEND S0C4 IN MODULE ALAGEN1 WHEN PROCESSING OVER 1,000 ARCHIVE LOGS | ||||
2017 |
WHEN "USE ONLY ARCHLOG2 = P' AND 'ACTIVE LOG PRIORITY = Y', ARCHLOG1 IS USED | ||||
2017 |
POSSIBLE S0C4 IN CSECT ALALB2 WHEN DATA RECORD IS NEAR END OF BUFFER | ||||
2017 |
ABEND S0C4 IN MODULE ALADTL1 WHEN PROCESSING LOBS FROM IMAGE COPIES | ||||
2017 |
VARIOUS ISSUES WHEN CREATING A FIXED EXTERNAL OR DELIMITED LOADFILE AFTER MODIFYING MODEPARM FILE | ||||
2017 |
FIXED FORMAT AND DELIMITED LOADFILES ARE NOT HONORING THE LOAD SPECIFICATION | ||||
2017 |
U=77 ABEND WHEN PROCESSING LOBS | ||||
2017 |
MESSAGE ALAA172E DURING SQL GENERATION | ||||
2017 |
NULLS QUOTED IN SQL | ||||
2017 |
U077 ABEND WITH MULTIPLE LOBS | ||||
2017 |
ALAA470E DURING LOAD ON 32K PAGESIZES | ||||
2017 |
POSSIBLE S0C7 ABEND DURING THE BSDS REPORT | ||||
2017 |
S0C4 CAN OCCUR WHILE READING ACTIVE LOGS THAT HAVE MORE THAN 4GBOF DATA | ||||
2017 |
IEC141I 013-20 ON DD SYSPRINT CAN OCCUR WHEN USING IEBGENER FOR FAST BACKUP | ||||
2017 |
A S0C7 ABEND CAN OCCUR WHEN USING COMBO MODE AND INCREMENTAL IMAGE COPIES | ||||
2017 |
MESSAGE ALAA073E WHEN TABLE VERSIONING, FULL ROW IMAGES, AND A CHANGE IN COMPRESSION DICTIONARY OCCURS | ||||
2017 |
MISCELLANEOUS FILTER UNIQUENESS VALUE DOES NOT WORK | ||||
2017 |
AN IEC020I 001-4 MESSAGE ON DD ALAERRI CAN OCCUR IF RUNNING IN LOG BACKWARD MODE AND WARNING ALAA573W IS TRYING TO BE ISSUED. |
||||
2017 |
ENABLE CONTINUE AFTER ERRORS OPTION IN QUICK START USER SETTINGS | ||||
2017 |
MISSING TRANSACTION INFORMATION IN URIDF | ||||
2017 |
ROLL-UP APAR #1 | ||||
2017 |
ROLL UP APAR #2 | ||||
2017 |
U=78 ABEND IN MODULE ALADTL1 WHEN PROCESSING LOG RECORDS FOR DELETING POINTER ROWS | ||||
2017 |
S0C4 IN MODULE ALADTL1 WHEN ONLY REPORTING A REORG LOG YES | ||||
2017 |
ALAA068E ERROR WHEN THE DB2 DATASET FOR A PARTITION HAS BEEN DELETED | ||||
2017 |
POSSIBLE ALAA046E WHEN COMPRESSION DICTIONARY IS NOT IN THE FIRST DATASET OF A MULTI-DATASET NON-PARTITIONED TABLESPACE | ||||
2017 |
ABORTED UNITS OF WORK REPORTING INCORRECTLY WHEN SPANNED ACROSS ARCHIVE LOGS | ||||
2017 |
RUNLIB NOT PROPERLY ALLOCATED | ||||
2017 |
ABENDS0C4 IN ALADTL1 IS POSSIBLE WHEN A MIXTURE OF COMPRESSED AND UNCOMPRESSED LOG RECORDS EXIST FOR THE SAME OBJECT | ||||
2017 |
JOB READS TOO MANY IMAGE COPIES | ||||
2017 |
CREATE A 'CONTINUE PROCESSING ON ERRORS' OPTION FOR HIGH SPEED MODE | ||||
2017 |
PARAMETER "RESTART ASSIST ON CONTINUOUS MODE" NOT GETTING UPDATED IN THE GENERAL REPORT FROM THE MODEPARM FILE | ||||
2017 |
FASTER METHOD TO BACKUP EXTFILE | ||||
2017 |
ALAA148E MESSAGE ISSUED WITHOUT A DATASET NAME. | ||||
2017 |
ERROR MESSAGE ALAA564E WITH LONGVAR TYPE COLUMN | ||||
2016 |
ENHANCEMENT TO ALLOW THE USER TO CONTROL WHICH DIAGNOSTIC REPORTS ARE WRITTEN DURING A LOG ANALYSIS RUN | ||||
2016 |
POSSIBLE MISSING RECORDS USING HISPEED, ROWDATA AS QSAM, AND CONTINUOUS MODE WHEN EXTFILE RESIDES ON MULTI-VOLUME DATASET | ||||
2016 |
POSSIBLE EXCESSIVE LOG USAGE | ||||
2016 |
MESSAGE ALAA440E OR ALAA447E WHEN USING MISC FILTERS 16/11/02 PTF PECHANGE |
||||
2016 |
SUPPORT FOR FUTURE RELEASE OF DB2 | ||||
2016 |
ABEND0C4 IN ALAGEN1 WITH MANY URIDS | ABEND3247 WHEN USING A V11 DB2 SUBSYSTEM IN NFM AND DSNDECP IN CONVERSION |
||||
2016 |
ADDING A REPORTING OPTION FOR DB2 COMMANDS IN LOG ANALYSIS TOOL | ||||
2016 |
ALAA517E MESSAGE WHEN USING HIGH SPEED MODE WITH LOAD LOG YES | ||||
2016 |
ABEND S0C4 IN MODULE ALADTL2 | ||||
2016 |
MESSAGE ALAA440E OR ALAA447E WHEN USING MISC FILTERS | ||||
2016 |
ERROR MESSAGE ALAA628E - UNSUPPORTABLE DROP COLUMN ACTIVITY | ||||
2016 |
HANG IN MODULE ALAGEN1 | ||||
2016 |
ABEND S0C7 IN MODULE ALADTL2 WHEN USING COMPRESSION | ||||
2016 |
ABEND S0C4 WITH XML AND DATA CAPTURE CHANGES | ||||
2016 |
A UNIT OF WORK COULD BE REPORTED A SECOND TIME WHEN USING THE 64 BIT MEMORY THRESHOLD PARAMETER. | ||||
2016 |
INCLUDE / EXCLUDE COLUMNS FOR LOADFILE / LOADCARD GENERATION ARENOT ALWAYS HONORED | ||||
2016 |
POSSIBLE LOOP DURING ERROR HANDLING IN MODULE ALADTL1 | ||||
2016 |
MISSING RECORDS USING HIGH SPEED MODE AND PARALLELISM > 1 | ||||
2016 |
LOB/XML PROBLEMS WITH DROPPED OBJECT MODE | ||||
2016 |
ALLOW THE PROCESSING OF LOAD LOG YES ACTIVITY IN HI-SPEED PROCESSING | ||||
2016 |
ABEND S0C4 WHEN USING FLDPROCS IN TABLES THAT HAVE MULTIPLE VARIABLE LENGTH COLUMNS | ||||
2016 |
REPORTING ON LOAD LOG YES ACTIVITY MAY OMIT SOME ACTIVITY | ||||
2016 |
ISPF ERROR ISPV006 ON THE PROFILE PANEL | ||||
2016 |
TABLES WITH FIELD AND EDIT PROCEDURES MAY HAVE COLUMN NAMES INCORRECTLY DISPLAYED IN REPORTS AND GENERATED SQL | ||||
2016 |
ABEND U0075 OR S0C4 ABENDS WHEN TRACKED DATA INCLUDES XML | ||||
2016 |
AN SVC DUMP MAY OCCUR DURING CLEANUP PHASE OF A JOB THAT USED ZIIP OFFLOAD | ||||
2016 |
MESSAGE ALAA064E WHEN MULTI-DATASET NON-PARTITIONED TABLESPACE FLASH COPY MISSING BUT COPYTOCOPY IC EXISTS FOR R340 R350 | ||||
2016 |
USER COMPLETION CODE=0050 WHEN REPORTING USER PRIVILEGES | ||||
2016 |
IEC020I 001-4 ON MESSAGE LIBRARY IF USER NOT AUTHORIZED TO VIEW SOME OBJECTS BEING REPORTED | ||||
2016 |
PROVIDE TOLERATION SUPPORT FOR FUTURE DB2 ENHANCEMENTS | ||||
2016 |
NEW THRESHOLD PARAMETER TO STOP PROCESSING ARCHIVE LOGS IN GENERAL REPORT | ||||
2016 |
ABEND S0C4 IN MODULE ALADTL3 WHEN PRODUCING A TRANSACTION REPORT | ||||
2016 |
ABEND0C4 IN CSECT ALACFRR | ||||
2016 |
ABEND U22 AND/OR U47 WHILE PROCESSING LOBS | ||||
2016 |
MESSAGE ALAA440E WHEN REPORTING AN UPDATE WHEN IMAGE COPY IS BEING TAKEN. | ||||
2016 |
POSSIBLE ERRONEOUS ALAA516E WHEN PROCESSING A PAGE FORMAT RECORDTHAT SPANS MULTIPLE ARCHIVE LOGS | ||||
2016 |
SETUP PANEL LOADLIB ENTRIES IGNORED | ||||
2015 |
MESSAGE ALAA440E WHEN USING SHRLEVEL CHANGE IMAGE COPIES | ||||
2015 |
POSSIBLE ALAA447E WHEN PROCESSING AN IMAGE COPY THAT CONTAINS MULTIPLE PARTITIONS THAT ARE NOT CONTIGUOUS | ||||
2015 |
ABENDS0C4 IN MODULE ALADTL1 WHEN PROCESSING LOAD LOG YES WITH A COMPRESSED TS | ||||
2015 |
S0C6 ABEND IN MODULE ALADTL2 WHEN USING PARTITIONED OBJECTS AND COMPRESSION | ||||
2015 |
ABENDS0C7 IN MODULE ALADTL2 | ||||
2015 |
ALAA338E POSSIBLE WHEN USING RELATIVE END DATE AND CONTINUOUS MODE PROCESSING TOGETHER | ||||
2015 |
IMPROPER PARTITION NUMBER DERIVED | ||||
2015 |
PROFILE RENAME ISSUES WHEN FIRST PART OF RENAME IS AN ISPF COMMAND | ||||
2015 |
POSSIBLE LOOP/HANG AFTER MEMORY EXHAUSTION | ||||
2015 |
ALAA440E WHEN PROCESSING A SPANNED LOG RECORD AND MISC ONLY FILTERS | ||||
2015 |
ABENDS0C4 IN MODULE ALADTL2 OR ALAA052E ERROR MESSAGE | ||||
2015 |
INCREASING THE AMOUNT OF TABLES THAT CAN BE PROCESSED WHEN GENERATING A LOADFILE | ||||
2015 |
AN INCORRECT VALUE MAY BE GENERATED FOR FLOATING POINT NUMBERS DUE TO ERROR DURING ROUNDING. | ||||
2015 |
INVALID JCL MAY BE GENERATED FOLLOWING TCZ DISCOVER | ||||
2015 |
VARIOUS ISSUES AFTER MIGRATING TO DB2 11 CM INCLUDING SQLCODE -302 AND ALAA628E MESSAGE | ||||
2015 |
MESSAGE ALAA157E GENERATED INCORRECTLY | ||||
2015 |
ABEND S0C4 IN MODULE ALADTL1 WHEN TOTAL SUM OF PARTITIONS WITH DATA BEING REPORTED EXCEEDS 2700 | ||||
2015 |
ALAA064E WHEN ATTEMPTING TO USE FLASHCOPY IMAGE COPY FROM A MULTI-DATASET NON PARTITIONED TABLESPACE | ||||
2015 |
ABENDS0C4 ABEND IN MODULE ALADTL2 | ||||
2015 |
ROLLUP APAR | ||||