IBM Support

PI76719: REBIND AGAINST PACKAGE WITH LONG NAME OR DELIMITED NAMES EXCEEDS 221 BYTES ENCOUNTERS IKJ56701I AND IKJ56702I MESSAGES

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Scenario reported:
    REBIND against Advanced Trigger packages with long names or
    delimited names can encounter the following messages:
    IKJ56702I INVALID PACKAGE NAME,
    IKJ56701I MISSING LOCATION.COLLECTION.PACKAGE-ID.(VERSION)+
    IKJ56701I MISSING LOCATION.COLLECTION.PACKAGE-ID OR
    IKJ56701I MISSING COLLECTION.PACKAGE-ID OR
    IKJ56701I MISSING * FOR ALL PACKAGES OWNED, MAX LENGTH=221 CHARS
    
    EXAMPLE:
    REBIND PACKAGE (PACKAGE01234567890123456789012345678901234567890
    1234567890123456789012345678901234567890123456789012345678901234
    5678901234567Z.LONGNAME90123456789012345678901234567890123456789
    0123456789012345678901234567890123456789012345678901234567890123
    45678901234567Z.(V2345678901234567890123456789012345678901234567
    8901234567890123Z) )
    

Local fix

  • Use an asterisk (*) in place of the collection id as shown:
    
    REBIND PACKAGE(*.LONGNAME901234567890123456789012345678901234567
    8901234567890123456789012345678901234567890123456789012345678901
    2345678901234567Z.(*))
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All DB2 12 for z/OS users of REBIND PACKAGE command          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * When the REBIND PACKAGE command is executed, DB2 issues      *
    * error messages if the package has a long schema and a long   *
    * name.                                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    A package can be created with a long schema and a long name. The
    maximum allowable size of schema is up to 128 bytes in length;
    package name size is the same as schema name size. But when the
    package is rebound and when the long schema and the long name
    exceeds 221 bytes, DB2 issues error messages. The cause of this
    is that the schema/collection id and the package name are not
    handled correctly by the command parser.
    
    An example of error messages is below.
    
    MISSING LOCATION.COLLECTION.PACKAGE-ID.(VERSION)+
    MISSING LOCATION.COLLECTION.PACKAGE-ID OR
    MISSING COLLECTION.PACKAGE-ID OR
    MISSING *  FOR ALL PACKAGES OWNED, MAX LENGTH=221 CHARS
    

Problem conclusion

  • DB2 code has been modified to fix the problem described above.
    
    Additional Keywords: SQLTRIGGER SQLNATIVESQLPL
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI76719

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    C10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-02-15

  • Closed date

    2017-03-20

  • Last modified date

    2017-05-01

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

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

    UI45689

Modules/Macros

  • DSNECP45
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RC10 PSY UI45689

       UP17/04/04 P F704

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.



Document information

More support for: DB2 for z/OS

Software version: C10

Reference #: PI76719

Modified date: 01 May 2017


Translate this page: