DB2 Path Checker Version 3.1
|
|||||
APAR | CLOSE DATE |
PTF(s) | Fixing APAR if PE |
HIPER? | Abstract |
---|---|---|---|---|---|
2011 |
PATH CHECKER PGM CKPPTHCK CARD COLUMN | ||||
2010 |
PANEL CKPP0005 INCORRECTLY GENERATES MSG CKP1016I | ||||
2010 |
REPORT COMMAND FAILS WHEN PLAN TABLE OWNER NAME HAS SPECIAL CHARACTERS | ||||
2010 |
PERFORMANCE ISSUE WHEN PATH CHECKER USES EXPLAIN OR TEST AND THEPACKAGE IS BOUND AS DEGREE ANY. | ||||
2010 |
GETTING MESSAGE CEE0813S WHEN RUNNING A COMPARE. | ||||
2009 |
MSG CKP047E DDF CONNECT TO ANOTHER SSID | ||||
2009 |
INCORRECT RESULTS RUNNING TEST PACKAGE | ||||
2009 |
PATH CHECKER ABEND806 | ||||
2009 |
PATH CHECKER SHOWS DIFFERENT RESULTS IN INTERACTIVE MODE THAN INBATCH MODE R310 ONLY. | ||||
2009 |
ACCESS PATH DIFFERENCES BETWEEN DETAIL AND SUMMARY REPORTS | ||||
2009 |
TEST WITH OPTIONS CPUPCT 00 WRITES INCORRECT REBIND CARDS TO RBINDOUT | ||||
2009 |
CLARIFY SUMMARY REPORT INCLUDING DSN_STATEMNT COST | ||||
2009 |
CKP043E WHEN EXECUTING PROGRAM CKPPTHCK. | ||||
2009 |
PATH CHECKER FAILS WITH RC=16 | ||||
2009 |
CREATE AN OPTION CPUPCT2 N FOR PATH CHECKER | ||||
2008 |
PATH CHECKER OUTPUT MAY INCORRECTLY INDICATE THAT SQL STATEMENTSHAVE BEEN DELETED WHEN IN FACT THEY HAVE NOT. | ||||
2008 |
ADDITIONAL INTERNAL DIAGNOSTICS TO BE IMPLEMENTED FOR THE SYSDIAGN DD CARD. | ||||
2008 |
IN PATH CHECKER REPORT OUTPUT THE SVC UNITS FIELD IS LIMITED TO 7 DIGITS, BUT DB2 DEFINES THE SVC UNITS FIELD AS UP TO 10 DIGITS |
||||
2008 |
UNUSUAL RESULTS USING THE TEST COMMAND | ||||
2008 |
WHEN PATH CHECKER MESSAGE CKP044E IS ISSUED COMPLETION CODE IS SET TO CC=00. | ||||
2008 |
NO MEMBERS FOUND | ||||
2008 |
INCORRECT OUTPUT IN THE PLAN TABLE WHEN RUNNING A WILDCARDED EXPLAIN AGAINST THE DB2 CATALOG. | ||||
2008 |
PATH CHECKER TERMINATES WITH MSGCKP202E WITH ERROR CODE = 1,009.THE MSG EXPLANATION NEEDS TO BE ENHANCED AND PGM NOT TERMINATE. |
||||
2008 |
PROVIDE NEW CLIST AND INSTRUCTIONS FOR STARTING PATH CHECKER FROM LAUNCHPAD AND ADMIN TOOL. | ||||
2007 |
PATH CHECKER CKPBIND MUST SPECIFY ENCODING(EBCDIC) TO PROCESS ON VERSION 9 DB2. | ||||
2007 |
IN THE PATH CHECKER ISPF INTERFACE THE DEFAULT_AUTHID ENTERED BYTHE USER ON THE SETTINGS PANEL IS IGNORED, LEADS TO SQLCODE -204 |
||||
2007 |
INCONSISTENT RESULTS USING BINDIN DD STATEMENT | ||||
2007 |
PATH CHECKER ABEND0C4 WHEN DBRMOUT IS NOT LRECL 80 RECFM FB. | ||||
2007 |
PROVIDE OPTION TO START PATH CHECKER FROM THE LAUNCHPAD. | ||||
2007 |
THIS APAR TO SATISFY MARKETING REQUIREMENT MR0323064741. PATH CHECKER TO ISSUE REBIND COMMANDS FOR PACKAGES W/NO PATH CHANGE. |
||||
2007 |
SQLCODE418 -418 ON EXPLAIN SET WITH SQL WITH CONCATENATED RANGE TESTING. | ||||
2007 |
MESSAGE CKP045E OCCURRED AND PATH CHECKER JOB ENDS WITH RC=0. | ||||
2007 |
ABEND04E WITH 00E7000C ON COMPARE COMMANDS FOR PLANS WITH OPTIONSCATALOGSQL OR ANLOUT AND PATH CHECKER R310 W/ DB2 V9. | ||||
2007 |
SQLCODE -312 WITH MSGCKP214I EXPLAIN FAILED FOR STATEMENT | ||||
2007 |
PATH CHECKER SQLCODE -180 IF EITHER PLAN_TABLE DOES NOT HAVE THE COLUMN OR ROWS IN PLAN_TABLE DON'T HAVE A NOT NULL BINDTIME. |
||||
2007 |
SQLCODE -417 FROM PATH CHECKER. | ||||
2007 |
PATH CHECKER COMPARE TO X.X BEFORE 'TIMESTAMP VALUE' RESULT IN WHERE PREVIOUS VERSION AND BINDTIME ARE GREATER THAN THE BEFORE |
||||
2007 |
PATHCHECKER TEST & EXPLAIN COMMANDS FAIL W/ SQLCODE=-104 FOR UPDATE STATEMENTS AS UPDATE TABLE SET COL = COL + :HV WHERE | ||||
2007 |
PATH CHECKER WITH EXPLAIN DBRM AND MSGCKP217I MAY REPORT COST INCREASES WHEN THERE SHOULD BE NONE. | ||||
2007 |
CORRECT GRAMMAR ERROR IN HELP PANEL CKPH003 | ||||
2006 |
MSGCKP206I IS ISSUED WITH TWO SLIGHTLY DIFFERENT TEXTS DEPENDINGON IF THERE IS AN 'OLD' ACCESS PATH OR NOT. | ||||
2006 |
PATH CHECKER FAILS TO MATCH SOME EXISTING SQL WHEN USING THE OPTION MATCHSQL. | ||||
2006 |
APAR FOR PATH CHECKER R310 TO INCLUDE THE FIXES FOR R220 APARS PK32052, PK29523, PK28959, AND PK29523 ( FORWARD FIT ). |