Updates to DB2® Path Checker V4.1 User's Guide

Product documentation


Abstract

Updates that apply to DB2® Path Checker Version 4.1 User's Guide (SC19-2959-01)

Content

The most recent update is listed first.





Update 8
Date of change: February 17, 2014
Topic: DB2 Path Checker commands syntax
Change description: This update provides additional information about the SEQBYVERSION keyword for the OPTIONS command. The information in Update 2 below was incomplete because it did not include a description of the keyword NOSEQBYVERSION, which turns off SEQBYVERSION.

NOSEQBYVERSION

Disables the SEQBYVERSION option. This option is the default.

SEQBYVERSION

This option is the only way to process comparisons for multiple editions or versions of a package. SEQBYVERSION selects the access paths by version and compares the most recent BIND_TIME access path to the previous access path for that version.

SEQBYVERSION is useful when a mass rebind has occurred, and access paths exist in the plan table that have current BIND_TIME values but are for previous versions of the package.


] Update 7 Date of change: January 21, 2014 Topic: CKP247I (New DB2 Path Checker message) Change description: The following informational message has been added to DB2 Path Checker: CKP247I COMPARE processing does not have a second access path to compare with the current access path. Explanation A COMPARE command could not find a second access path for the current version of the program to compare with the access path that has the most recent bind time. This message is displayed only when the SEQBYVERSION option is in effect. This option changes the behavior of a COMPARE command so that it selects access paths by version for comparison. Under this setting, the command compares the access paths that have the most recent bind time to the previous access path for the same version. User response No action is required. [


Update 6
Date of change: May 17, 2011
Topic: DB2 Path Checker commands syntax
Change description: The following processing option has been added to the OPTIONS command:

COMMITCOUNT
This option specifies the number of DB2 Path Checker objects DB2 Path Checker commands syntax(DBRMs) that are to be processed by a command before a commit. Each program name (DBRM) that is processed by a command counts as a single unit of work.

A commit and a message will be issued after every object is processed. If you specify a low number of DB2 Path Checker, COMMITCOUNT is useless. If you specify too many DB2 Path Checker objects, a faster release of DB2 resources that are needed by other JCL jobs that contain DB2 processing will not be allowed. In this case, a timeout might be the result for some of these jobs.

The following examples show how COMMITCOUNT works:
  • If COMMITCOUNT = 1 and there are 1000 DB2 Path Checker objects, 1000 commits and 1000 messages are issued.
  • If COMMITCOUNT = 100 and there are 1000 DB2 Path Checker objects, a commit and a message are issued after processing 100 objects, so 10 commits and 10 messages are issued.
  • If COMMITCOUNT = 100 and there are 999 DB2 Path Checker objects, a commit and a message are issued after processing 100 objects, so nine commits and nine messages are issued. The last 99 objects will be committed by program termination without a message being issued.

KEEPDYNAMIC(YES) is required to use the COMMITCOUNT option.



Update 5
Date of change: May 17, 2011
Topic: Messages
Change description: The following message has been added:

CKP231I SQL COMMIT PROCESSED
Explanation: OPTIONS COMMITCOUNT was specified, and an SQL commit was issued.
Programmer response: No action is required.
Severity: 0



Update 4
Date of change: May 17, 2011
Topic: Step 1. Binding DB2 Path Checker and granting plan access
Change description: The first part of the sample bind output has been updated:
1READY
  DSN SYSTEM(DB9G)
 DSN
  BIND PLAN(CKPPTHCK) PKLIST(CKPPTHCK.*)  ENCODING(EBCDIC)  ACTION(REPLACE) VALIDATE(BIND) ISOLATION(CS) RETAIN DEGREE(ANY)
 DSNT252I  -DB9G DSNTBCM1 BIND OPTIONS FOR PLAN CKPPTHCK
            ACTION        REPLACE RETAIN
            OWNER         P390H
            VALIDATE      BIND
            ISOLATION     CS
            ACQUIRE       USE
            RELEASE       COMMIT
            EXPLAIN       NO
            DYNAMICRULES  RUN
 DSNT253I  -DB9G DSNTBCM1 BIND OPTIONS FOR PLAN CKPPTHCK
            NODEFER       PREPARE
            CACHESIZE     3072
            QUALIFIER     P390H
            CURRENTSERVER
            CURRENTDATA   NO
            DEGREE        ANY
            SQLRULES      DB2
            DISCONNECT    EXPLICIT
            NOREOPT       VARS
            KEEPDYNAMIC   NO
            IMMEDWRITE    NO
            DBPROTOCOL    DRDA
            OPTHINT
            ENCODING      EBCDIC(01047)
            ROUNDING      HALFEVEN
            PATH
 DSNT200I  -DB9G  BIND FOR PLAN CKPPTHCK SUCCESSFUL
 DSN
  BIND PLAN(CKPA100) PKLIST(CKPPTHCK.*)  ENCODING(EBCDIC)  ACTION(REPLACE) VALIDATE(BIND) ISOLATION(CS) RETAIN DEGREE(ANY)
 DSNT252I  -DB9G DSNTBCM1 BIND OPTIONS FOR PLAN CKPA100
            ACTION        REPLACE RETAIN
            OWNER         P390H
            VALIDATE      BIND
            ISOLATION     CS
            ACQUIRE       USE
            RELEASE       COMMIT
            EXPLAIN       NO
            DYNAMICRULES  RUN
 DSNT253I  -DB9G DSNTBCM1 BIND OPTIONS FOR PLAN CKPA100
            NODEFER       PREPARE
            CACHESIZE     3072
            QUALIFIER     P390H
            CURRENTSERVER
            CURRENTDATA   NO
            DEGREE        ANY
            SQLRULES      DB2
            DISCONNECT    EXPLICIT
            NOREOPT       VARS
            KEEPDYNAMIC   NO
            IMMEDWRITE    NO
            DBPROTOCOL    DRDA
            OPTHINT
1           ENCODING      EBCDIC(01047)
            ROUNDING      HALFEVEN
            PATH
 DSNT200I  -DB9G  BIND FOR PLAN CKPA100  SUCCESSFUL
 



Update 3
Date of change: May 17, 2011
Topic: Step 1. Binding DB2 Path Checker and granting plan access
Change description: The figure with sample JCL for binding DB2 Path Checker has been updated with the following sample JCL:

//DB2BIND EXEC PGM=IKJEFT01,DYNAMNBR=20
//STEPLIB DD DISP=SHR,DSN=.SDSNLOAD  
//DBRMLIB DD DISP=SHR,DSN=.SCKPDBRM  
//SYSTSPRT DD SYSOUT=*  
//SYSPRINT DD SYSOUT=*  
//SYSTSIN DD *  
DSN
SYSTEM(SSID)  
BIND PLAN(CKPPTHCK) PKLIST(CKPPTHCK.*)   -      
     ENCODING(EBCDIC) ACTION(REPLACE)    -      
     VALIDATE(BIND) ISOLATION(CS) RETAIN DEGREE(ANY)  
BIND PLAN(CKPA100) PKLIST(CKPPTHCK.*)    -  
     ENCODING(EBCDIC) ACTION(REPLACE)    -  
     VALIDATE(BIND) ISOLATION(CS) RETAIN DEGREE(ANY)  
BIND PACKAGE(CKPPTHCK) MEMBER(CKPPTHCK)  -      
     KEEPDYNAMIC (YES) ENCODING(EBCDIC)  -    
     ACTION(REPLACE) VALIDATE(BIND) ISOLATION(CS)
BIND PACKAGE(CKPPTHCK) MEMBER(CKPA100)   -    
    ENCODING(EBCDIC) ACTION(REPLACE)     -    
    VALIDATE(BIND) ISOLATION(CS)              
BIND PACKAGE(CKPPTHCK) MEMBER(CKPBLD)    -
    ENCODING(EBCDIC) ACTION(REPLACE)     -
    VALIDATE(BIND) ISOLATION(CS)
END
/*
//




Update 2
Date of change: April 19, 2011
Topic: DB2 Path Checker commands syntax
Change description: The following processing option has been added to the OPTIONS command:

SEQBYVERSION
This option is the only way to get comparisons for multiple versions of a package. SEQBYVERSION selects the access paths by version and compares the most recent BIND_TIME access path to the previous access path for that version. SEQBYVERSION is useful when a mass rebind has occurred and access paths that have current BIND_TIME values exist in the PLAN_TABLE but are for previous versions of the package.

The following PDF shows the command syntax:

ckpugmst_OPTIONS.pdf ckpugmst_OPTIONS.pdf




Update 1
Date of change: March 21, 2011
Topic: Troubleshooting
Change description: The CKP245I message has been added:

CKP245I PROGRAM NAMES WILL BE SELECTED FROM BINDIN PROCESSING
Explanation: The execution JCL contained a DD statement for BINDIN, which will replace the program names in the DB2 Path Checker command with the program names from the BIND commands.
Programmer response: None.
Severity: 0



Rate this page:

(0 users)Average rating

Document information


More support for:

DB2 Tools for z/OS
DB2 Path Checker

Software version:

4.1.0

Operating system(s):

z/OS

Reference #:

7020358

Modified date:

2011-05-17

Translate my page

Machine Translation

Content navigation