IBM Support

PL36601: SELECT STATEMENT ON SYSIBM.SYSCOPY NEEDS AT LEAST ONE BLANK ADDED TO THE ARGUMENTS.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • THE USER TRIED TO EXTRACT SOME ROWS AND CODED FOLLOWING SELECT
    STATEMENT.
     SELECT * FROM SYSIBM.SYSCOPY
            WHERE DBNAME = 'DB99TEST' AND TSNAME = 'TS99TES1'
            ORDER BY
                  ICDATE DESC,
                  ICTIME DESC :
    EXECUTION OF ABOVE SELECT GOT NO ROWS. HOWEVER, IF THE SELECT
    STATEMENT IS CHANGED AS FOLLOWS, HE GETS 2 ROWS.
     SELECT * FOR SYSIBM.SYSCOPY
            WHERE DBNAME = 'DB99TEST' AND TSNAME = 'TS99TES1 '
            ORDER BY ICDATE DESC,
                     ICTIME DESC :
     AS SHOWN ABOVE, ADDING AT LEAST ONE BLANK AFTER THE TSNAME TO
    MAKE THE ARGUMENT LONGER THAN THE ACTUAL TSNAME LENGTH CAUSES
    THE SELECT TO BE PROCESSED CORRECTLY.
    NO DOCUMENTS HAVE BEEN REQUESTED FOR THIS APAR.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: ALL DB2 USERS.                               *
    ****************************************************************
    * PROBLEM DESCRIPTION: SELECT STATEMENTS AGAINST SYSCOPY       *
    *                      RETURN INCORROUT UNLESS AT LEAST ONE    *
    *                      BLANK IS ADDED TO THE ARGUMENTS.        *
    ****************************************************************
    * RECOMMENDATION: APPLY THIS PTF, AND IF NECESSARY, RUN JOB    *
    *                 DSNQIJUP.  PLEASE REFER TO CONCLUSION        *
    *                 BELOW TO DETERMINE WHETHER YOU NEED TO       *
    *                 RUN DSNQIJUP.                                *
    ****************************************************************
    A KEY WAS ADDED TO SYSCOPY INDEX DSNUCH01, WHICH IS DESCENDING,
    BUT MARKED AS ASCENDING IN THE DB2 CATALOG. RDS THEN SET UP A
    GENERIC KEY ARGUMENT FOR THE INDEX COLUMN WHICH IS ASSUMED TO
    BE ASCENDING. THE ADDITION OF BLANK IN THE PREDICATE MADE THAT
    KEY ARGUMENT NONSARGABLE AND ALTERED THE KEY ARGUMENTS SO THAT
    THEY WORKED.
    

Problem conclusion

  • THE CATALOG INITIALIZATION MEMBER HAS BEEN CORRECTED: HOWEVER,
    THIS WILL ONLY BENEFIT NEW INSTALLS OF DB2 V2R1 THAT
    INCORPORATE THIS PTF. THOSE V2R1 SYSTEMS THAT HAVE ALREADY BEEN
    INSTALLED OR WERE MIGRATED FROM V1R3, REQUIRE JOB DSNQIJUP TO
    BE RUN.  ANOTHER PROBLEM INVOLVING THE DB2 CATALOG IS ALSO
    FIXED BY THIS APAR.  SOME CATALOG TABLES REPRESENT DSNDCX01
    AS ALLOWING DUPLICATES ALTHOUGH DSNDCX01 IS A UNIQUE INDEX.
    A SINGLE SUCCESSFUL EXECUTION OF DSNQIJUP WILL CORRECT ALL
    THE ERRORS IN THE CATALOG.
    .
    A REQUEST FOR PUBLICATION CHANGE HAS BEEN SUBMITTED TO
    CORRECT THE OBJECT IDENTIFIER CROSS-REFERENCE IN THE DB2
    DIAGNOSIS GUIDE AND REFERENCE (LY27953600) WHICH LISTS
    DSNDCX01 AS NONUNIQUE.
    ****************************************************************
    PLEASE REFER TO THE PTF COVER LETTER FOR SPECIFIC INSTRUCTIONS
    REGARDING JOB DSNQIJUP.
    ****************************************************************
    ****************************************************************
    ***** JOB DSNQIJUP DOES NOT NEED TO BE RUN IF THIS PTF     *****
    ***** IS APPLIED IN CONJUNCTION WITH INSTALLATION OF DB2.  *****
    ***** A CORRECTED CATALOG INITIALIZATION MEMBER HAS BEEN   *****
    ***** INCLUDED WITH THIS PTF.                              *****
    ***** JOB DSNQIJUP SHOULD BE EXECUTED IF ANY OF THE        *****
    ***** FOLLOWING QUERIES RETURN A VALUE (COUNT) OTHER THEN  *****
    ***** ZERO.                                                *****
    *****                                                      *****
    *****  - SELECT COUNT(*)                                   *****
    *****    FROM SYSIBM.SYSKEYS                               *****
    *****    WHERE IXCREATOR = 'SYSIBM'                        *****
    *****     AND IXNAME = 'DSNUCH01'                          *****
    *****     AND COLNAME = 'START_RBA'                        *****
    *****     AND ORDERING = 'A':                              *****
    *****   - SELECT COUNT(*)                                  *****
    *****     FROM SYSIBM.SYSINDEXES                           *****
    *****     WHERE CREATOR = 'SYSIBM'                         *****
    *****       AND NAME = 'DSNDCX01'                          *****
    *****       AND UNIQUERULE = 'D' :                         *****
    *****  - SELECT COUNT(*)                                   *****
    *****    FROM SYSIBM.SYSCOPY                               *****
    *****    WHERE IBMREQD = 'Y':                              *****
    *****                                                      *****
    ****************************************************************
    ADDITIONAL KEYWORDS: SQLINCORR
    

Temporary fix

Comments

  • RP89/04/03 REPINNED TO CORRECT APAR RESPONDER TEXT.  ATEXT
    

APAR Information

  • APAR number

    PL36601

  • Reported component name

    5740 IBM DATABA

  • Reported component ID

    5740XYR00

  • Reported release

    210

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    1988-12-23

  • Closed date

    1989-02-24

  • Last modified date

    1990-06-01

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

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

    UL47130

Modules/Macros

  •    DSNQIJUP DSNTIS06 DSNUECM0 DSNUEXLO DSNXDBD6
    

Fix information

  • Fixed component name

    5740 IBM DATABA

  • Fixed component ID

    5740XYR00

Applicable component levels

  • R210 PSY UL47130

       UP89/03/17 P F903

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.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"DB2 for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"210","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
01 August 2023