IBM Support

PM76860: POSSIBLE SQLCODE531 -531 ERROR IN DB2SQL COMMAND WHEN TRYING TO CHANGE STOGROUP NAMES IN DB2 V10

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Possible SQLCODE -531 error in DB2SQL command when trying to
    change STOGROUP names in DB2 V10.
    CKZ24621E SQL EXECUTE  FAILED, SQLCODE:     -531 SQLSTATE: 23504
    DSNT408I SQLCODE = -531, ERROR:  PARENT KEY IN A PARENT ROW
    CANNOT BE UPDATED BECAUSE IT HAS ONE OR MORE DEPENDENT ROWS IN
    RELATIONSHIP DSNSS@SV
    

Local fix

  • A possible work around might be to use STORCLAS, MGMTCLAS,
    DATACLAS in the DB2 STOGROUP and not change the STOGROUP name as
    part of the cloning. But instead change STORCLAS, MGMTCLAS,
    DATACLAS as part of the cloning with the DB2SQL command using
    the STORCLAS-MASKS, MGMTCLAS-MASKS, and DATACLAS-MASKS keywords.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    *                 All users of IBM DB2 Cloning Tool for z/OS   *
    *                                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    *                      Possible SQLCODE -531 error in DB2SQL   *
    *                      command when trying to change STOGROUP  *
    *                      names in DB2 V10.                       *
    *                      CKZ24621E SQL EXECUTE  FAILED, SQLCODE: *
    *                          -531 SQLSTATE: 23504                *
    *                      DSNT408I SQLCODE = -531, ERROR:         *
    *                          PARENT KEY IN A PARENT ROW          *
    *                      CANNOT BE UPDATED BECAUSE IT HAS ONE    *
    *                      OR MORE DEPENDENT ROWS IN  RELATIONSHIP *
    *                      DSNSS@SV                                *
    *                                                              *
    ****************************************************************
    * RECOMMENDATION: APPLY the PTF.                               *
    ****************************************************************
    Code has been changed to correct this condition.
    

Problem conclusion

  • Apply the PTF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM76860

  • Reported component name

    DB2 CLONING TOO

  • Reported component ID

    5655N1000

  • Reported release

    310

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2012-11-09

  • Closed date

    2012-11-26

  • Last modified date

    2016-09-16

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

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

Modules/Macros

  •    CKZ00246
    

Fix information

  • Fixed component name

    DB2 CLONING TOO

  • Fixed component ID

    5655N1000

Applicable component levels

  • R310 PSY UK83725

       UP12/11/29 P F211

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.

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSZJXP","label":"DB2 Tools for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.1.0"}]

Document Information

Modified date:
30 March 2021