IBM Support

PI87169: IBM MQ CD RELEASE BIND PACKAGE FAILS WITH DSNT230I

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as duplicate of another APAR.

Error description

  • Change Team finds BIND PACKAGE fails for (CSQ5B900) when
    searching for member (CSQ5B900) if run for the v9 Continuous
    Delivery release of MQ. This is because the 90X suffix should
    be used for DB2 plans. In the SCSPROC library, while the sample
    jobs for binding plans (CSQ45BPL) and packages (CSQ45BPK) both
    have the correct form of the names (i.e. CSQ5n90X), the jobs to
    migrate the DB2 table definitions from a previous release
    (CSQ4570T and CSQ4571T) have not been correctly updated and
    still refer to CSQ5B900.
    

Local fix

  • To circumvent, replace all occurrences of CSQ5B900 with CSQ5B90X
    

Problem summary

Problem conclusion

Temporary fix

Comments

  •  Users Affected:
    All users of IBM MQ for z/OS Version 9 Release 0 Modification 3
    Continuous Delivery (CD) Release.
    
    Problem summary:
    In the V9 Continuous Delivery release of MQ, when using jobs
    CSQ4570T or CSQ4571T to migrate the DB2 table definitions from
    V7, the BIND PACKAGE step fails with messages DSNT230I and
    DSNT233I, searching for member CSQ5B900.
    This is because the 90X suffix should be used for DB2 plans, but
    the sample JCL in these jobs incorrectly specifies 900.
    The correct plan name is CSQ5B90X, as in jobs CSQ45BPL and
    CSQ45BPK.
    
    Problem resolution:
    The JCL in CSQ4570T and CSQ4571T has been corrected.
    The fix is targeted for delivery in APAR PI89159 for V9.0.5.
    

APAR Information

  • APAR number

    PI87169

  • Reported component name

    MQ Z/OS V9

  • Reported component ID

    5655MQ900

  • Reported release

    010

  • Status

    CLOSED DUB

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-09-12

  • Closed date

    2017-10-20

  • Last modified date

    2018-02-26

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

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

Fix information

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"010","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
26 February 2018