IBM Support

PQ77460: DBD GEN FOR HDAM/HALDB SECONDARY INDEX PARTITIONED DATABASE RESULTS IN INDEX INSTEAD OF PSINDEX STATEMENTS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When doing a DBD gen for a secondary index to a HDAM/HALDB data
    base the statements produced indicate an INDEX rather than a
    PSINDEX database. RKSIZE parameter is omitted as well.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: DATA DICTIONARY REL6 USERS WITH APAR PQ30394 *
    ****************************************************************
    * PROBLEM DESCRIPTION: MSGDBD0111 E 'OPERAND-C-NOT VALID CODE' *
    *                       IS RECEIVED FOR TARGET DATABASE ON     *
    *                       XDFLD FORM.                            *
    *                      MSGDBD3106 E 'ROLE Y INCONSISTENT WITH  *
    *                       DATABASE CODE Z' IS RECEIVED ON THE    *
    *                       SEGMENT FORM.                          *
    *                      DBD_OUT FOR HALDB SECONDARY INDEX       *
    *                       GENERATES ACCESS=INDEX RATHER THEM     *
    *                       PSINDEX.                               *
    ****************************************************************
    * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
    ****************************************************************
    SEVERAL ERRORS WERE ENCOUNTERED DURING THE CREATION OF A HALDB
    SECONDARY INDEX USING THE ONLINE DICTIONARY FORMS.
    1. THE SIP SEGMENT FORM DID NOT ALLOW THE SEGMENT ROLE 'Y' TO BE
       SPECIFIED WITH A HALDB SECONDARY INDEX DATABASE. THE SEGMENT
       ROLE FOR ALL SECONDARY INDEX DATABASES IS 'Y'. THE PSINDEX
       DATABASE CODE IS 'Z'. THE INDEX DATABASE CODE IS 'Y'.
       MESSAGE DBD3106 E 'ROLE Y INCONSISTENT WITH DATABASE CODE Z'
       WAS ISSUED.
    2. THE XDFLD FORM DID NOT ALLOW CREATION OR UPDATES TO THE
       TARGET DATABASE. THE CODE FIELD WAS WRITE PROTECTED. GARBAGE
       WOULD APPEAR IN THE TARGET DATABASE CODE IF A DATABASE NAME
       WAS ENTERED AND COULD NOT BE CORRECTED.
       MESSAGE DBD0111 E 'OPERAND -C- NOT VALID CODE' WAS ISSUED.
    3. THE SECONDARY INDEX DATABASE FORM AUTOMATICALLY CREATED ALL
       DATABASES WITH ACCESS=INDEX WHETHER CODE 'Y'OR'Z'.
       A DBD_OUT FOR A HALDB SECONDARY INDEX WOULD RESULT IN SOURCE
       FOR AN INDEX DBD RATHER THAN A PSINDEX DBD.
    

Problem conclusion

  • THE SIP SEGMENT AND SECONDARY INDEX DATABASE FORM PROCESSORS
    HAVE BEEN MODIFIED.
    THE XDFLD FORMAT, DBDXXF, HAS ALSO BEEN MODIFIED. IT WILL BE
    NECESSARY TO RECOMPILE DBDXXF. JOB DBDAMFS MAY BE USED.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PQ77460

  • Reported component name

    OS/VS DATA DICT

  • Reported component ID

    5740XXF00

  • Reported release

    663

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2003-08-13

  • Closed date

    2003-08-25

  • Last modified date

    2003-09-04

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

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

    UQ79650 UQ79651

Modules/Macros

  •    DBDDSNP  DBDDXSP  DBDXXF
    

Fix information

  • Fixed component name

    OS/VS DATA DICT

  • Fixed component ID

    5740XXF00

Applicable component levels

  • R602 PSY UQ79650

       UP03/08/27 P F308

  • R663 PSY UQ79651

       UP03/08/27 P F308

[{"Line of Business":{"code":"LOB35","label":"Mainframe SW"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSAVJJ","label":"DB\/DC Data Dictionary"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"663"}]

Document Information

Modified date:
12 February 2021