|
DB2 Log Analysis Tool Version 3.2
|
|||||
| APAR | CLOSE DATE |
PTF(s) | Fixing APAR if PE |
HIPER? | Abstract |
|---|---|---|---|---|---|
2015 |
ALAA440E WHEN PROCESSING A SPANNED LOG RECORD AND MISC ONLY FILTERS | ||||
2014 |
MESSAGE IEC190I IN LOG ANALYSIS JOB WHEN RUNNING ON Z/OS 2.1 | ||||
2013 |
ABEND0C4 IN MODULE ALASBDF | ||||
2013 |
UNABLE TO EXCLUDE BASE/CLONE TABLES FROM FILTERS | ||||
2013 |
ABENDS0C4 IN MODULE ALAGEN1 | ||||
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 |
HEX ZEROS IN GENERATED JCL WHEN MISC FILTERS REQUESTED BUT NOT ENTERED | ||||
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 |
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 |
ABEND0C4 MAY OCCUR IN MODULE ALALF2 | ||||
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 |
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 |
LOG ANALYSIS TOOL NOT PROCESSING FIELDPROC PROPERLY FOR RRF TABLESPACES. | ||||
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 |
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 |
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 |
REPORTING ON ONLY A SPECIFIC URID THAT IS SPLIT ACROSS MULTIPLE DB2 LOGS DOES NOT REPORT THE WHOLE URID PROPERLY | ||||
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 |
ALAA445E NOT ISSUED WHEN A JOB IDENTIFIER THAT DOES NOT EXIST IS SPECIFIED. | ||||
2012 |
HELP PANEL UPDATES -FAST APPLY SQL COMMIT FREQUENCY FIELD, GENERAL REPORT PANEL HELP TYPO AND NON EBCIDIC DATA HANDLING | ||||
2011 |
WHEN CREATING THE LOADFILE FOR CHAR 255 COLUMN THAT CAN BE NULL DATA DOES NOT GET WRITTEN OUT CORRECTLY | ||||
2011 |
USING A USER CREATED COLUMN TYPE BASED ON VARBINARY, VARGRAPHIC,TIMESTAMP, OR TIMESTAMP WITH TIME ZONE MAY LEAD TO A S0C4 ABEND. |
||||
2011 |
DURING LOAD PROCESSING, SQLCODE104 MAY OCCUR IF CREATE TABLE STATEMENT IS LONGER THAN 454 LINES. | ||||
2011 |
POSSIBLE MISSING RECORDS AFTER FORCED ARCHIVE LOG. | ||||
2011 |
INCORRECT ERROR MESSGES, SOC4 ON CALL COMMAND, ISPF DIALOG ERROR | ||||
2011 |
POSSIBLE PROBLEM WITH LOB RECORDS THAT SPAN DB2 LOGS. | ||||
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 |
ABEND378 AND POSSIBLE ALAA064E WHEN LOB IMAGE COPY IS NOT AVAILABLE BUT ANOTHER EXACT COPY IS AVAILABLE. | ||||
2011 |
ABENDS0C4 WHEN REPORTING ON MANY DIFFERENT OBJECTS IN THE EXTENDED REPORT | ||||
2011 |
SQLCODE117 WHEN EXECUTING SQL GENERATED FOR A TABLE THAT HAS A COLUMN EXPLICITLY CREATED WITH THE PATTERN DB2_GEN%. | ||||
2011 |
POSSIBLE ABENDU0071 PROCESSING LOBS. | ||||
2011 |
ABEND0C4 IN MODULE ALASUBG OFFSET=0001814C | ||||
2011 |
OLD LOG POINTS IN LOW VOLUME DATASHARING SUBSYSTEMS CAN CAUSE OLDER LOGS THAN NEEDED TO BE READ AT TIMES. | ||||
2011 |
ABEND878-10 MEMORY LEAK OCCURING WHEN PROCESSING COMPRESSION DICTIONARIES FROM DB2 LOGS DURING DETAIL REPORT PHASE. | ||||
2011 |
POSSIBLE ABENDS0C4 IN ALADTL1 WHILE PROCESSING ALADCTP. | ||||
2011 |
THE USE OF 44 CHARACTER IMAGE COPY NAMES OR 44 CHARACTER LOG ANALYSIS FILE NAMES MAY LEAD TO ABENDC03 OR AN ALAA148E ERROR. |
||||
2011 |
ABENDC03 DURING GENERAL REPORT GENERATION IF AN MSGALAA037E IS SUPPOSED TO BE ISSUED. | ||||
2011 |
POTENTIAL ABENDS0C4 IN LOG ANALYSIS TOOL PROCESSING THOUSANDS OF LOBS OR PROCESSING MANY LARGE LOBS | ||||
2011 |
MORE THAN 31 ACTIVE LOGS STORED IN THE BSDS DB2 LOG ANALYSIS TOOL RECEIVES ABENDS0C4 READING THE BSDS | ||||
2011 |
BSDS PROCESSING MAY RESULT IN MISSED LOGS ON DATA SHARING 11/07/05 PTF PECHANGE |
||||
2011 |
SQL-601 CODE DURING GENERAL REPORT LOAD. | ||||
2011 |
PROBLEMS WITH LOADING NON-EBCDIC DATA. | ||||
2011 |
LAT REPORTS SOME UOWS MULTIPLE TIMES IF SHOW UNCOMMITTED = Y ANDTHE UOW IS SPLIT ACROSS MULTIPLE LOGS. | ||||
2011 |
U0083 ABEND WHEN URIDS FOR ONE DATASHARING MEMBER EXACTLY FILL A STORAGE UNIT AND HAVE OTHER URIDS FROM OTHER MEMBERS. | ||||
2011 |
INCORRECT DETAILED PROCESSING DATA FROM LOAD UTILITY THAT IS COMPRESSED AND NO OTHER LOG DATA PROCESSED WAS COMPRESSED | ||||
2011 |
IN CERTAIN CASES A PREVIOUS JOB IDENTIFIER FIELD WITHIN LOG ANALYSIS COULD BE APPENDED TO THE DSNS IN THE GENERATED JCL | ||||
2011 |
ABEND0C6 USING ADVANCED FILTERS, LARGE VARCHAR COLUMN, AND CHAR DATA IN HEX OPTIONS WHILE FILTERING ON VALUE IN LARGE VARCHAR CL |
||||
2011 |
PARTITION FILTERS NOT RETURNING DATA FOR PARTITIONS GREATER THAN1 WHEN A NON PARTITIONED TABLESPACE OCCURS FIRST IN FILTER LIST |
||||
2011 |
IMPROVEMENTS TO TABLE VERSIONING PROCESSING DURING HI SPEED MODE | ||||
2011 |
POSSIBLE SKIPPED RECORDS OR ABENDU088 FOR SOME COMBINATION OF SPANNED RECORDS. | ||||
2011 |
ALLOW MULTI-VOLUME ALLOCATIONS FOR THE TEMPORARY IMAGE COPY DD TICSPECS. | ||||
2011 |
POSSIBLE S0C4 IN LOG ANALYSIS TOOL WHEN GENERATING SQL FOR A NULL FLOATING POINT COLUMN. | ||||
2011 |
POSSIBLE PROBLEMS WITHIN LOG ANALYSIS TOOL WHEN ARCHLOG1 OR ARCHLOG2 IS WRITTEN TO MULTIPLE VOLUMES BUT THE OTHER IS NOT | ||||
2011 |
PROBLEMS PROCESSING MULTIPLE OBJECTS WITH TABLE VERSIONING INFORMATION IN LOG ANALYSIS. ABEND0C7 IN ALADCNV + X'82A' | ||||
2011 |
ABEND0C4 RC11. TVFILE NOT BEING ALLOCATED IN TWO PHASE JOB DURING CREATION OFLOADFILE WHEN NEEDED. | ||||
2011 |
POSSIBLE S0C4 WHEN CREATING A LOADFILE DUE TO A TABLE WITH ROW REORDER FORMAT HAVING A COLUMN ADDED | ||||
2011 |
LOB/XML ISSUES WHEN LOADING BACK INTO DB2. | ||||
2011 |
U0073 ABEND DURING GENERAL REPORT | ||||
2011 |
ABENDU0013 WHEN USING DROPPED OBJECT MODE AND FIRST ITEM IN RECOVERY IS LOAD REPLACE LOG YES | ||||
2011 |
HASH TABLES IN REPORTS GETTING ALAA516E OR ABENDU078 | ||||
2011 |
LOG ANALYSIS TOOL IS BEING ENHANCED TO WRITE THE IMPACT REPORT TO THE FOLLOWING DDS GENIMP, SUMIMP, AND DTLIMP | ||||
2011 |
ALAA073W WARNING WHEN USING LARGE SEGMENTED TABLESPACES | ||||
2011 |
LOG ANALYSIS TOOL MAY NOT REPORT ON CERTAIN OBJECTS AFTER THE DB2 LOG RBA HAS BEEN RESET | ||||
2011 |
ABENDS0C4 DURING ERROR HANDLING OF ERROR IN LOG READING PHASE OF DTL REPORT | ||||
2011 |
PROBLEMS WITH ADVANCED FILTERS IN ONE PHASE WORK FILE MODE WHEN DEALING WITH LARGE VOLUMES OF DATA. ALAA172E U4038 | ||||
2011 |
ABENDSC03 OCCURS WHEN AN ERROR IS ENCOUNTERED DURING FORMATTINGGWHEN USING 1 PHASE WORK FILE MODE. | ||||
2011 |
MSGALAA447E DUE TO SEGMENTED TABLESPACE AND ORDER OF UPDATES. | ||||
2011 |
DB2 LOG ANALYSIS TOOL ADDING SUPPORT FOR LARGE BLOCK INTERFACE (LBI) FOR INLINE IMAGE COPIES | ||||
2011 |
PROBLEMS PROCESSING MULTIPLE OBJECTS WITH NEW TABLE VERSIONING INFORMATION IN LOG ANALYSIS TOOL | ||||
2011 |
ABEND0C4 OR ERROR MSGALAA506E COULD RESULT WHEN THERE ARE MULTIPLE SPANNNED DB2 LOG RECORDS FOR THE SAME PAGE. | ||||
2011 |
DB2 LOG ANALYSIS TOOL FAST APPLY SQL UNABLE TO HANDLE SOME SQL STATEMENTS WITH ONE VERY LARGE COLUMN STRING | ||||
2011 |
DB2 LOG ANALYSIS TOOL FAST APPLY SQL MAY ISSUE A -330 SQL ERROR CODE WHEN HANDLING SQL FOR A UNICODE TABLE WITH XML COLUMNS | ||||
2011 |
WHEN USING ONE PHASE MODE, LOG ANALYSIS MAY ABEND WITH A SC03 IFTHE FILTER SYNTAX IN THE JCL IS NOT CORRECT | ||||
2011 |
MESSAGE ALAA447E WITH PARTITIONED TABLE IN LOG-FORWARD MODE | ||||
2011 |
S878 WHEN CERTAIN BUFFERS ARE NOT PROPERLY FREED | ||||
2010 |
INCOMPLETE ERROR MESSAGES ISSUED AND ABEND0C4 | ||||
2010 |
ABEND0C4 INCORROUT SPANNED DB2 LOG RECORD FOR DB2 RESTART | ||||
2010 |
LOG ANALYSIS TOOL GETS ABENDS013 REASON=000000E1 WITH LBI IMAGE COPIES | ||||
2010 |
POSSIBLE S0C4 WHEN USING HI-SPEED MODE AND HAVE LARGE UNITS OF WORK OR A UOW THAT HAS A LARGE SPAN FROM START TO FINISH. | ||||
2010 |
S002 ABEND WHILE PROCESSING LOB DATA | ||||
2010 |
POSSIBLE LONG RUNNING JOB WHEN USING ADVANCED FILTERS AND CURRENT ROW | ||||
2010 |
LOADFILE NOT BEING GENERATED PROPERLY AFTER ADDING A COLUMN TO A TABLE. POSSIBLE ABEND0C4. | ||||
2010 |
HIGH CPU OCCURS IN GENERAL REPORT DUE TO ROLLBACK | ||||
2010 |
LOB/XML SUPPORT ISSUES POST DB2 V10 SUPPORT | ||||
2010 |
RC8 OR USER ABEND55 USING IMPACT REPORT BY ROW | ||||
2010 |
ABENDU0024 IN DB2 LOG ANALYSIS TOOL MODULE ALADTL1 WHEN DEALING WITH COMPRESSION DICTIONARIES FOR LARGE TABLESPACES | ||||
2010 |
DUPLICATE LRSN CAUSING SORTING SEQUENCES FOR GENERATED DB2 LOADFILE FROM LOG ANALYSIS TOOL | ||||
2010 |
MISC FILTERS AND LOAD LOG YES COMBINATION CAN OMIT LOG RECORDS THAT SHOULD NOT BE OMITTED, ABENDS0C7 CAN OCCUR. | ||||
2010 |
WHEN PROCESSING MANY COMPRESSION DICTIONARIES A S0C4 IS POSSIBLEDUE TO EXHAUSTED STORAGE | ||||
2010 |
TABLE VERSIONING ISSUES WHEN COLUMNS ADDED TO A TABLE IN DB2 9 OR LATER AND A COLUMN WAS PREVIOUSLY VERSIONED | ||||
2010 |
SUPPORT FOR NEW FEATURES OF DB2 V10 | ||||
2010 |
MESSAGE ALAA052E VSAM PUT ERR FOR ROWDATA REASON CODE=8 RC08 ABENDU0055 DURING IMPACT REPORT BY ROW | ||||
2010 |
POSSIBLE PROBLEMS WITH ADVANCED FILTERS IN ONE PHASE WORK FILE MODE FOR PARTICULAR TIMEFRAMES | ||||
2010 |
DB2 LOG ANALYSIS MAY DISALLOW A VALID DSN WHEN SPECIFYING THE CONTINUOUS MODE FILE | ||||
2010 |
DB2 LOG ANALYSIS TOOL IS NOT HANDLING A DATE BEYOND THE MAXIMUM ALLOWED CORRECTLY, THIS COULD RESULT IN A S0C7 | ||||
2010 |
POSSIBLE S0C4 OR ALAA479E WHEN LAT FIND NO DATA TO REPORT WHEN USING HISPEED AND SYNCSORT | ||||
2010 |
ABENDSC03 ISSUED IN ALADTL1 WHEN ALAA064E MESSAGE ISSUED IN 1 PHASE MODE | ||||
2010 |
ABEND0C4 IN ALADTL3 FOR R320 IF THE MODE FILE WAS NOT PROPERLY CONVERTED FROM A PREVIOUS VERSION. | ||||
2010 |
PERFORMANCE ISSUES ADDRESSED ON "IMPACT REPORT BY ROW" OPTION HIGH CPU AND SLOW ELAPSED TIMES | ||||
2010 |
VARGRAPHIC COLUMNS NOT BEING HANDLED PROPERLY IN A UNICODE TABLESPACE THAT IS USING ROW REORDER FORMAT. | ||||
2010 |
IF A FLOATING POINT FIELD IS UPDATED BUT THE DISPLAYABLE FORMAT DOESN'T CHANGE, A POTENTIAL ALAA325E ERROR CAN OCCUR | ||||
2010 |
ALAGEN1 S0C4 WHEN COMPENSATION LOG RECORDS REMOVE ALL ACTIVITY IN A UOW AND THAT UOW IS SPLIT ACROSS MULTIPLE LOGS | ||||
2010 |
MATERIALIZED UNICODE CHAR FIELDS MAY BE MISSING A TRAILING X '0F' CHARACTER | ||||
2010 |
ABENDS0C4 IN ALADTL1 TRACKING REBIND COMMAND | ||||
2010 |
PROBLEMS GENERATING XML DATA WHEN XML SPANS MULTIPLE LOG RECORDS | ||||
2010 |
DB2 LOG ANALYSIS TOOL IS SPECIFYING THE FILE SEQUENCE NUMBER WHEN REQUESTING A CATALOGED IMAGE COPY THAT IS ON TAPE | ||||
2010 |
LOB DATA REPORTED INCORRECTLY IN IMPACT REPORT BY ROW | ||||
2010 |
ENHANCE IMPACT REPORT | ||||
2010 |
ABEND0C7 ALAGLOAD+B56 DURING A "LOAD DATA INTO DB2" JOB WHEN THEMODE FILE HAS BEEN OVERLAID AFTER THE "GEN/DTL REPORT" RUN | ||||
2010 |
S0C4 WHEN MULTIPLE DB2 ACTIVE LOGS ARE OVERWRITTEN WHILE DB2 LOGANALYSIS TOOL PROCESSING LOGS IN PARALLEL IN DATASHARING ENVIRON |
||||
2010 |
POSSIBLE SQLCODE -413 RUNNING DB2 LOG ANALYSIS TOOL WHEN COPYPAGESF COLUMN IN SYSCOPY IS OUT OF INTEGER RANGE. | ||||
2010 |
POSSIBLE ABEND0C4 WHEN PROCESSING MORE THAN 27,000 UTILITY RECORDS IN ONE RUN OF LOG ANALYSIS TOOL | ||||
2010 |
POSSIBLE ALAA440E OR ALAA447E WHEN PROCESSING LF AND LOG RECORD WAS READ BUT NOT USED IN GENERAL REPORT. | ||||
2010 |
MESSAGE ALAA521E DYN ALLOC ERR RETURN CODE 0002 REASON 1708 IMAGE COPY NEEDED FOR DICTIONARY NOT AVAILABLE IN HI SPEED MODE |
||||
2010 |
ABEND0C4 RC4 ALASTOR+6C4 R1 BAD IN ERROR HANDLING ROUTINE AFTER GETMAIN FAILURE IN THE DETAILS REPORT PROCESSING | ||||
2010 |
POSSIBLE WARNING / ERROR MESSAGES WHILE GENERATING THE MODEPARM FILE VIA ISPF PANELS IN DB2 LOG ANALYSIS TOOL | ||||
2010 |
LONG CPU TIMES WITH MUTLIPLE IMAGE COPIES PER TABLESPACE | ||||
2010 |
WHEN LONG RUNNING UOWS HAVE ACTIVITY FROM MULTIPLE OBJECTS IT ISPOSSIBLE TO SKIP THE UOW IN CONTINUOUS MODE | ||||
2010 |
ABEND0C7 DURING DATA COMPRESSION IF LOG BACKWARD PROCESSING IS FORCED ACROSS A REORG. | ||||
2010 |
ADVANCED FILTERS DO NOT WORK PROPERLY WHEN PROCESSING ARCHIVED OUTPUT AND USING MULTIPLE ARCHIVE OUTPUT DATASETS | ||||
2010 |
THE TVFILE DSNAME IN 2 PHASE PROCESSING MUST CONFORM TO INTERNALNAMING STANDARDS OR RESULTS IN RC=8 WITHOUT ANY ERROR MESSAGE | ||||
2010 |
U073 ABEND WHEN USING RESOLVE STARTED UOW AND JOB ENDS BEFORE CURRENT LOG. | ||||
2010 |
POSSIBLE U0031 IN ALADTL2 USING A COMPRESSED TABLESPACE OF TYPE G. | ||||
2010 |
ABEND=SC03 U0000 REASON=00000000 MAY OCCUR WHEN PROCESSING TABLESPACES WITH MORE THAN 999 PARTITIONS | ||||
2010 |
ENHANCEMENT TO SUPPORT DB2 CHANGES | ||||
2010 |
USE OF SYSLGRNX INVALID WITH ANY MEMID > 9 | ||||
2010 |
S0C4 U0000 REASON=00000011 IN ALASBDF AT OFFSET=00002474 | ||||
2010 |
DB2 LOG ANALYSIS TOOL TABLE VERSIONING LOGIC IS INCORRECTLY FLAGGING SOME DELETES AS NEEDING TABLE VERSION 0. | ||||
2010 |
DB2 LOG ANALYSIS TOOL U077 ABEND WITH LOB INSERTS | ||||
2010 |
POSSIBLE S0C4 WHEN WORKING WITH VERY WIDE TABLES IN LOG ANALYSISTOOL | ||||
2009 |
POSSIBLE S0C4 DURING QUIET TIME PROCESSING WHEN A FILTERED OBJECT CONTAINS A ROLLBACK THAT SPANS MULTIPLE LOGS. | ||||
2009 |
PROCESSING CAN BE SLOW DURING PROGAM ALAGLOAD WITH A HIGH NUMBEROF UOWS | ||||
2009 |
MISSING DETAIL RECORDS USING HIGH SPEED IN NON-DATA SHARING | ||||
2009 |
POSSIBLE S0C4 WHEN USING DB2 LOG ANALYSIS TOOL ADVANCED FILTERS WITH MORE THAN 200K LOG RECORDS TO PROCESS | ||||
2009 |
POSSIBLE S0C4 WHEN USING HISPEED AND THERE ARE MANY UOWS THAT HAVE A LARGE RANGE FROM START UOW TO END UOW | ||||
2009 |
MESSAGE LIBRARY MODIFICATION TO ALAA073 / ALAA549 | ||||
2009 |
DB2 LOG ANALYSIS TOOL PERFORMANCE ENHANCEMENT FOR LARGE UOWS IN HIGH SPEED MODE | ||||
2009 |
LOOP WHEN THE GETMAIL FAILURE NOT HANDLED PROPERLY SOME ERRORS IN SUBTASK NOT PROPERLY PROPAGATED BACK TO MAIN TASK |
||||
2009 |
THE "LOAD DATA INTO DB2" PANEL MAY INCORRECTLY GIVE AN ALAA546E ERROR WHEN THE USER SETS THE "GENERAL REPORT DATA" TO 'N' | ||||
2009 |
DB2 LOG ANALYSIS TOOL CAN ENCOUNTER ALAA440E/U=55 ABEND DUE TO AINCOMPATIBLE PARAMETER IN A SORT EXIT. | ||||
2009 |
SQL GENERATION ERROR HANDLING NOT PROPERLY HANDLED WHEN USING WORK FILES | ||||
2009 |
LONG RUN TIME AFTER 'START ETV' PROCESSING IN DB2 LOG ANALYSIS TOOL | ||||
2009 |
ROWDATA VALIDATION ERROR IN DROPPED OBJECT MODE | ||||
2009 |
LOG ANALYSIS SOMETIMES ENDS WITH A RC=8 WHEN NO DATA WAS FOUND WHEN IT SHOULD HAVE ENDED WITH A MAX RC=2 OR BYPASSED STEPS | ||||
2009 |
LOG ANALYSIS TOOL 1 PHASE WORK FILE MODE ERRORS WITH STRIPED EXTENDED-FORMAT DATASETS. | ||||
2009 |
USER ABEND 71 CAN OCCUR WITH MASS DELETE ON BASE TABLE W/LOB | ||||
2009 |
DB2 LOG ANALYSIS TOOL HSM RECALL PROCESSING NOT WORKING ON ALL MIGRATED DATASETS DUE TO LIMITATIONS IN UNIT NAME PROCESSING | ||||
2009 |
POSSIBLE S0C4 RUNNING DB2 LOG ANALYSIS TOOL AFTER 'START MERGE' WHEN USING WORK FILES MODE | ||||
2009 |
LOG ANALYSIS TOOL HI-SPEED MODE CAN ENCOUNTER VARIOUS PROBLEMS WHEN THE LAST LOG RECORD EXTRACTED IS IN A UNIT OF WORK BY | ||||
2009 |
ABENDSS0C4 DURING ERROR HANDLING FOR DYNAMIC ALLOCATION ERROR MESSAGES OCCURING DURING SUBTASKING | ||||
2009 |
S0C4 WHILE PROCESSING DB2 LOG FORMAT PAGE RECORDS THAT ARE SPANNED ACROSS LOGS | ||||
2009 |
ALAA064E WHEN MULTIPLE DB2 ACTIVE LOGS ARE OVERWRITTEN WHILE LATIS PROCESSING LOGS IN PARALLEL | ||||
2009 |
POSSIBLE S0C4 IN ALASUBG DURING CONTINUOUS MODE PROCESSING DUE TO CONTIGUOUS MEMORY CONTENTS | ||||
2009 |
ALAA041E CATFILE LOOKUP ERROR RUNNING DETAIL REPORT THAT INCLUDES AN OBJECT IN RECOVERY THAT SPANS MORE THAN 2 LOGS | ||||
2009 |
LONG RUNNING DB2 LOG ANALYSIS TOOL HIGH SPEED MODE JOB WITH LARGE VOLUME OF EXTFILE (EXTRACT FILES) AND UOW (UNITS OF WORK) |
||||
2009 |
ALA V3.2 ROLLUP APAR | ||||