PM65509: IBM INTERNAL APAR FOR NEGATIVE FEEDBACK ON ++HOLD DATA NOT CLEAR LY STATED FOR EXISTING V10.1 ENVIRONMENT ONLY.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• ++HOLD DATA DOES NOT CLEARLY GIVE INSTRUCTIONS FOR EXISTING
  USERS OF ADMIN VERSION 10.1IF MIGRATION IS NOT NEEDED.
  ALSO, DID NOT CLEARLY STATE INSTRUCTIONS FOR ADDING NEW
  COLUMNS TO THE CHANGES TABLE.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of the DB2 Administration Tool for     *
  *                 z/OS.                                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: The PTF UK76851 ++HOLD should have      *
  *                      described what users should have done   *
  *                      in the following three scenarios:       *
  *                                                              *
  *                      1.Existing users of DB2 Administration  *
  *                        Tool for z/OS Version 7.2 and         *
  *                        migration is not needed.              *
  *                      2.Existing users of DB2 Administration  *
  *                        Tool for z/OS Version 10.1.           *
  *                      3.New users of DB2 Administration       *
  *                        Tool for z/OS Version 10.1.           *
  *                                                              *
  *                      However, instructions regarding the new *
  *                      column SEQSVLR on table ADBCHG in the   *
  *                      DB2 Administration Tool for z/OS        *
  *                      Version 10.1 were missing from the      *
  *                      ++HOLD.                                 *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The PTF UK76851 ++HOLD should have described what users
  should have done in the following three scenarios:
  
  
  1. Existing users of DB2 Administration Tool for
     z/OS Version 7.2 and migration is not needed.
  
  2. Existing users of DB2 Administration Tool for
     z/OS Version 10.1.
  
  3. New users of DB2 Administration Tool for z/OS
     Version 10.1.
  
  However, instructions regarding the new column SEQSVLR on
  table ADBCHG in the DB2 Administration Tool for z/OS
  Version 10.1 were missing from the ++HOLD.
  

Problem conclusion

• There are four different scenarios that need to be handled.
  
  Scenario 1. Existing users of DB2 Administration Tool for
  z/OS Version 7.2 and migration is not needed:
  
  Please check whether the table ADBCHG in your environment
  has the same structure as below:
  
  The model structure of ADBCHG in Version 7.2:
  
  CREATE TABLE ADBCHG
  (CHANGEID   DECIMAL(7, 0) NOT NULL GENERATED BY DEFAULT
        AS IDENTITY (START WITH 1, INCREMENT BY 1, NO CYCLE),
  OWNER      VARCHAR(128)  NOT NULL WITH DEFAULT CURRENT SQLID,
  NAME       VARCHAR(128)  NOT NULL,
  CREATEDBY  VARCHAR(128)  NOT NULL WITH DEFAULT USER,
  CREATEDTS  TIMESTAMP     NOT NULL WITH DEFAULT,
  ALTEREDBY  VARCHAR(128)  NOT NULL WITH DEFAULT USER,
  ALTEREDTS  TIMESTAMP     NOT NULL WITH DEFAULT,
  COMMENT    VARCHAR(128)  NOT NULL,
  CHANGETYPE CHAR(8)       NOT NULL,
  STATUS     CHAR(8)       NOT NULL,
  IGNOREID   INTEGER,
  MASKID     INTEGER,
  SRCVERID   INTEGER,
  TGTVERID   INTEGER,
  NEWVERID   INTEGER,
  DELTAVERID INTEGER,
  JCLDSN     VARCHAR(56)   NOT NULL WITH DEFAULT,
  JCLDSN2    VARCHAR(56)   NOT NULL WITH DEFAULT,
  WSLDSN     VARCHAR(56)   NOT NULL WITH DEFAULT,
  SCOPEID    INTEGER,
  ORGCHANGEID DECIMAL(7, 0)    WITH DEFAULT NULL,
  WSLID      INTEGER,
  RUNSQLID   CHAR(8)       NOT NULL WITH DEFAULT,
  JOBUSER    CHAR(8),
  LASTSCHEMA VARCHAR(128)  NOT NULL WITH DEFAULT,
  DEFERSW    CHAR(1)       NOT NULL WITH DEFAULT,
  ALLOWROT   CHAR(1),
  RIDGENA    CHAR(1)       NOT NULL WITH DEFAULT,
  TMSGENA    CHAR(1)       NOT NULL WITH DEFAULT,
    PRIMARY KEY (CHANGEID))
  IN >DB_NAME<.>TS_NAME<;
  
  If the structure of ADBCHG in your environment is the same as
  above, please ignore the following.  If the structure of
  ADBCHG in your environment is not the same as above, please
  run some of the following jobs in the SADBSAMP library
  supplied by Version 7.2:
  
  Step 1. If column RUNSQLID is not in ADBCHG,
          run ADBCHU01 to add column RUNSQLID to ADBCHG.
  Step 2. If column JOBUSER is not in ADBCHG, run ADBCHU05
          to add column JOBUSER to ADBCHG.
  Step 3. If column LASTSCHEMA is not in ADBCHG, run ADBCHU07
          to add column LASTSCHEMA to ADBCHG.
  Step 4: If column DEFERSW is not in ADBCHG, run ADBCHU09
          to add column DEFERSW to ADBCHG.
  Step 5. If column ALLOWROT is not in ADBCHG, run ADBCHU08
          to add column ALLOWROT to ADBCHG.
  Step 6. If columns RIDGENA and TMSGENA are not in ADBCHG,
          run ADBCHU12 to add columns RIDGENA and TMSGENA
          to ADBCHG.
  
  After running the jobs above, make sure the current structure of
  ADBCHG in your environment is the same as above.
  
  Scenario 2. Existing users of DB2 Administration Tool for z/OS
  Version 7.2 and need to migrate from Version 7.2 to Version
  10.1:
  
  Firstly, execute Scenario 1 to make sure your current structure
  ADBCHG in your environment is the same as the model structure
  of ADBCHG in Version 7.2.  Secondly, please run the following
  four jobs in the SAMPLE library supplied by Version 10.1.
  
  Step 1. Run ADBCHANU to add columns RAUTHSWID, RSECADMID,
          EAUTHSWID, ESECADMID, ENEWVER, ESCPSCH, ESCPNAM,
          EVERSCH, EVERNAM to ADBCHG.
  Step 2. Run ADBCHG02 to add columns APPCONT to ADBCHG.
  Step 3. Run ADBCHG03 to add columns IDENTSVL to ADBCHG.
  Step 4. Run ADBCHG04 to add columns SEQSVLR to ADBCHG.
  
  After running the JOBS above, make sure the current structure of
  ADBCHG in your environment is the same as following.
  
  The model structure of ADBCHG in Version 10.1:
  
  CREATE TABLE ADBCHG
   (CHANGEID   DECIMAL(7, 0) NOT NULL GENERATED BY DEFAULT
        AS IDENTITY (START WITH 1, INCREMENT BY 1, NO CYCLE),
    OWNER      VARCHAR(128)  NOT NULL WITH DEFAULT CURRENT SQLID,
    NAME       VARCHAR(128)  NOT NULL,
    CREATEDBY  VARCHAR(128)  NOT NULL WITH DEFAULT USER,
    CREATEDTS  TIMESTAMP     NOT NULL WITH DEFAULT,
    ALTEREDBY  VARCHAR(128)  NOT NULL WITH DEFAULT USER,
    ALTEREDTS  TIMESTAMP     NOT NULL WITH DEFAULT,
    COMMENT    VARCHAR(128)  NOT NULL,
    CHANGETYPE CHAR(8)       NOT NULL,
    STATUS     CHAR(8)       NOT NULL,
    IGNOREID   INTEGER,
    MASKID     INTEGER,
    SRCVERID   INTEGER,
    TGTVERID   INTEGER,
    NEWVERID   INTEGER,
    DELTAVERID INTEGER,
    JCLDSN     VARCHAR(56)   NOT NULL WITH DEFAULT,
    JCLDSN2    VARCHAR(56)   NOT NULL WITH DEFAULT,
    WSLDSN     VARCHAR(56)   NOT NULL WITH DEFAULT,
    SCOPEID    INTEGER,
    ORGCHANGEID DECIMAL(7, 0)    WITH DEFAULT NULL,
    WSLID      INTEGER,
    RUNSQLID   CHAR(8)       NOT NULL WITH DEFAULT,
    JOBUSER    CHAR(8),
    LASTSCHEMA VARCHAR(128)  NOT NULL WITH DEFAULT,
    DEFERSW    CHAR(1)       NOT NULL WITH DEFAULT,
    ALLOWROT   CHAR(1),
    RAUTHSWID   VARCHAR(128)  WITH DEFAULT,
    RSECADMID   VARCHAR(128)  WITH DEFAULT,
    EAUTHSWID   VARCHAR(128)  WITH DEFAULT,
    ESECADMID   VARCHAR(128)  WITH DEFAULT,
    ENEWVER     VARCHAR(3)    WITH DEFAULT,
    ESCPSCH     VARCHAR(128)  WITH DEFAULT,
    ESCPNAM     VARCHAR(128)  WITH DEFAULT,
    EVERSCH     VARCHAR(128)  WITH DEFAULT,
    EVERNAM     VARCHAR(128)  WITH DEFAULT,
    RIDGENA    CHAR(1)       NOT NULL WITH DEFAULT,
    TMSGENA    CHAR(1)       NOT NULL WITH DEFAULT,
    APPCONT    CHAR(1)       NOT NULL WITH DEFAULT,
    IDENTSVL   CHAR(1)       NOT NULL WITH DEFAULT,
    SEQSVLR    CHAR(1)       NOT NULL WITH DEFAULT,
    PRIMARY KEY (CHANGEID))
   IN ADBDCHG.ADBSCHG;
  
  Scenario 3. Existing users of DB2 Administration Tool for
  z/OS Version 10.1:
  
  Please check whether table ADBCHG in your environment has
  the same structure as the model structure of ADBCHG in
  Version 10.1.
  
  If the structure of ADBCHG in your environment is the same as
  the model structure of ADBCHG in Version 10.1, please ignore
  the following.
  If the structure of ADBCHG in your environment is not the same
  as the model structure of ADBCHG in Version 10.1, please run
  some of the following jobs in the SADBSAMP library supplied
  by Version 10.1:
  
  Step 1. If columns ENEWVER, ESCPSCH, ESCPNAM,EVERSCH,
          EVERNAM are not in ADBCHG, run ADBCHANU to add column
          ENEWVER, ESCPSCH, ESCPNAM,EVERSCH,EVERNAM
          to ADBCHG.
  Step 2. If columns RIDGENA and TMSGENA are not in ADBCHG, run
          ADBCHG01 to add RIDGENA and TMSGENA to ADBCHG.
  Step 3. If column APPCONT is not in ADBCHG, run ADBCHG02 to
          add column APPCONT to ADBCHG.
  Step 4. If column IDENTSVL is not in ADBCHG, run ADBCHG03 to
          add column IDENTSVL to ADBCHG.
  Step 5. If column SEQSVLR is not in ADBCHG, run ADBCHG04 to
          add column SEQSVLR to ADBCHG.
  
  After running the jobs above, make sure the current structure of
  in your environment is the same as the model structure of ADBCHG
  in Version 10.1.
  
  Note:
  In Step 1, the return code of job ADBCHANU will be greater than
  or equal to 8. Please check the job log after running job
  ADBCHANU.  If you find a SQLCODEN612 / SQLCODE=-612 message
  in the job log:
  
  DSNT408I SQLCODE = -612, ERROR: >COLUMN_NAME< IS A
  DUPLICATE NAME
  
  please ignore it, as it indicates that table ADBCHG already has
  the column.  The original structure of ADBCHG has columns
  RAUTHSWID, RSECADMID, EAUTHSWID, ESECADMID, and the job ADBCHANU
  also add columns RAUTHSWID, RSECADMID,EAUTHSWID, ESECADMID to
  table ADBCHG.
  
  Scenario 4. For new users of DB2 Administration Tool for z/OS
  Version 10.1:
  
  Install Version 10.1 and run the updated SADBSAMP(ADBCHANG) job
  by Version 10.1.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UK82897 UK82898 UK82899

Modules/Macros

•    ADBCHANG
  

Fix information

• Fixed component name

  DB2 ADMIN TOOL

• Fixed component ID

  568851500

Applicable component levels

• RA10 PSY UK82897

     UP12/10/31 P F210

• RA20 PSY UK82898

     UP12/10/30 P F210

• R720 PSY UK82899

     UP12/10/30 P F210

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.