Updates that apply to DB2® Path Checker Version 4.2 User's Guide (SC19-4141-00)
Date of change: April 3, 2014
Change description: This update enhances two messages to clarify meaning and provide more detailed user responses when DB2 Path Checker or one of its commands cannot find a required plan table, catalog table, or DSN statement table. Minor corrections were made to a step in six task topics that refers to a SET command.
Download the following PDF to see the entire topics that were affected by these changes.
Date of change: February 17, 2014
Topic: OPTIONS command
Change description: This update adds information about the MATCHSQL keyword for the OPTIONS command. When you use the option with the TEST command, you must set the object-type to AS PACKAGE and also set the FROM CATALOG parameter.
The MATCHSQL2 processing option matches SQL statements based on the SQL characteristics followed by the SQL statement text rather than by statement number or physical sequence in the program. This comparison is performed by comparing the SQL statement text in the catalog.
Because DB2 Path Checker compares the SQL statement text in the catalog, this option works only for the following commands:
- COMPARE PACKAGE
You must use both of the following options with the TEST command when MATCHSQL2 is active:
- AS PACKAGE
- FROM CATALOG
When you use MATCHSQL2, the SQL statements for the previous bind of the package must also be in the catalog. If the SQL statements are not in the catalog, the report indicates that none of the statements match and flags all statements as changed.
MATCHSQL2 might flag changes in the sequence of SQL statements in a program, even if the statements are exact duplicates.
MATCHSQL2 is mutually exclusive with MATCHSQL1, MATCHQUERYNO, and MATCHSEQUENCE. If you specify multiple options, DB2 Path Checker uses only the last one.
Date of change: December 16, 2013
Topic: Updates to Chapter 2: Customizing DB2 Path Checker by using Tools Customizer
Change description: Enhancements to the documentation for customization help you to get up and running with DB2 Path Checker more quickly and easily. The new topics include the following information:
- How to prepare to customize DB2 Path Checker, including a complete checklist of customization steps with links to detailed instructions;
- How to set up your environment prior to customization, including software requirements and installation verification;
- Worksheets to help you gather all the information that you need to customize the product, including data set names and parameter values.
See the PDF document for details.
Date of change: October 25, 2013
Topic: OPTIONS command
Change description: The following processing options have been added to the OPTIONS command:
Valid values for the APPLCOMPAT option are V11R1 or V10R1.
The value V11R1 specifies that the DB2 REBIND commands that DB2 Path Checker writes to the RBINDOUT and PBINDOUT data sets include the option APPLCOMPAT(V11R1). For more information, see the DB2 documentation for the REBIND option APPLCOMPAT.
The value V10R1 specifies that the DB2 REBIND commands that DB2 Path Checker writes to the RBINDOUT and PBINDOUT data sets include the option APPLCOMPAT(V10R1). For more information, see the DB2 documentation for the REBIND option APPLCOMPAT.
Valid values for the DESCSTAT option are YES or NO.
The value NO specifies that the DB2 REBIND commands that DB2 Path Checker writes to the RBINDOUT and PBINDOUT data sets include the DECSTAT(NO) option. For more information, see the DB2 documentation for the REBIND option DECSTAT.
The value YES specifies that the DB2 REBIND commands that DB2 Path Checker writes to the RBINDOUT and PBINDOUT data sets include the DECSTAT(YES) option. For more information, see the DB2 documentation for the REBIND option DECSTAT.
If you specify this keyword in the OPTIONS command, you must specify a value or the command will fail and issue message CKP1145E.
The following messages have been added:
CKP1145E An invalid option was specified for DESCSTAT. Valid values are YES or NO.
Explanation: The value of the DESCSTAT option is not valid.
User response: Specify one of the following values for DESCSTAT: YES or NO.
CKP1146E An invalid option was specified for APPLCOMPAT. Valid values are V10R1 or V11R1.
Explanation: The value of the APPLCOMPAT option is not valid.
User response: Specify one of the following values for APPLCOMPAT: V10R1 or V11R1.