IBM Support

PI96440: UNSUCCESSFUL BIND USING BIND-ON-TARGET=Y

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • This fix applies to subsystem cloning and the subsystem cloning
    stored procedure.
    When BIND-ON-TARGET=Y option is used in the stored procedure,
    the following error messages might appear:
    {color:#d04437}DSNT230I !_SSID_ BIND DBRM-MEMBER-NAME
    ERROR{color}
    and
    {color:#d04437}DSNT233I !_SSID_ UNSUCCESSFUL BIND for
    CKZCSQ1C module.{color}
    where _SSID_ is the Db2 subsystem identifier.
    Once the fix is applied, these error messages are no longer
    issued. Also, when BIND-ON-TARGET=Y option is used this fix
    resolves a problem with binds for modules that were added in
    previous PTFs for the DB2SCHEMA-UPDATE command.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of IBM Db2 Cloning Tool z/OS.          *
    ****************************************************************
    * PROBLEM DESCRIPTION: This fix applies to subsystem cloning   *
    *                      and the subsystem cloning stored        *
    *                      procedure.                              *
    *                      When BIND-ON-TARGET=Y option is used    *
    *                      in the stored procedure, the following  *
    *                      error messages might appear:            *
    *                      {color:#d04437}DSNT230I !_SSID_ BIND    *
    *                      DBRM-MEMBER-NAME ERROR{color} and       *
    *                      {color:#d04437}DSNT233I !_SSID_         *
    *                      UNSUCCESSFUL BIND for CKZCSQ1C          *
    *                      module.{color} where _SSID_ is the      *
    *                      Db2 subsystem identifier. Once the      *
    *                      fix is applied, these error messages    *
    *                      are no longer issued. Also, when        *
    *                      BIND-ON-TARGET=Y option is used this    *
    *                      fix resolves a problem with binds for   *
    *                      modules that were added in previous     *
    *                      PTFs for the DB2SCHEMA-UPDATE command.  *
    ****************************************************************
    * RECOMMENDATION: APPLY the PTF.                               *
    ****************************************************************
    Code has been changed to correct this condition.
    

Problem conclusion

  • APPLY the PTF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI96440

  • Reported component name

    DB2 CLONING TOO

  • Reported component ID

    5655N1000

  • Reported release

    320

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-04-09

  • Closed date

    2018-04-12

  • Last modified date

    2018-05-01

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

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

Modules/Macros

  •    CKZCPLNC
    

Fix information

  • Fixed component name

    DB2 CLONING TOO

  • Fixed component ID

    5655N1000

Applicable component levels

  • R320 PSY UI55206

       UP18/04/17 P F804

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":"SSAUUE","label":"IBM Db2 Cloning Tool for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.2.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
01 May 2018