IBM Support

PI65533: MESSAGE DFS1282E UNABLE TO CREATE OR USE TPIPE=XXXXXXXX FOR MEMBER=YYYY FOR MQ TPIPE AFTER IMS RESTART.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Message DFS1282E UNABLE TO CREATE OR USE TPIPE=xxxxxxxx FOR
    MEMBER=yyyy for MQ TPIPE after IMS restart.  Also MQ message
    CSQ2001I =xxxx CSQ2QCP0 OTMA REJECTED MESSAGE -
    APPLICATION ERROR, SENSE CODE=000E0000, XCFGNAME=gggggggg
    XCFMNAME=mmmmmmmm TPIPE=tttttttt
    
    During restart the OTMA member flag MTE1QUE can be incorrectly
    set.
    This changes a sync TPIPE to be a non-syncTPIPE and creates a
    hold queue for the TPIPE in restart.
    At the end of restart, MQ connects to IMS and resets the error
    MTE1QUE flag.
    However, the error non-sync TPIPE with hold queue was already
    there in IMS.
    IMS then rejected the incoming MQ transactions from the TPIPE.
    

Local fix

  • Create a new IMS Bridge Queue in MQ.  This creates a new TPIPE
    name.  Delete the old IMS Bridge Queue.  Create a Queue Alias
    for the old IMS Bridge Queue pointing to the new IMS Bridge
    Queue.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: IMS V13 OTMA customers using both MQSeries   *
    *                 and IMS Connect                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: After ERE, IMS rejected MQ transaction  *
    *                      with DFS1282E message.                  *
    ****************************************************************
    * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
    ****************************************************************
    When both MQSeries and IMS Connect are OTMA clients, an IMS hold
    queue could be created for MQSeries and the TPIPE for MQSeries
    can be changed from a sync TPIPE to a non-sync TPIPE.
    This error can happen when DFSYDRU0 user exit incorrectly sets
    a hold queue output flag for a MQSeries TPIPE or during ERE.
    After this hold queue is created for an MQSeries TPIPE,
    this TPIPE in IMS can no longer accept an input transaction
    from MQSeries. IMS will then reject the MQSeries transaction
    with a DFS1282E message.
    

Problem conclusion

  • GEN:
    KEYWORDS:
    
    *** END IMS KEYWORDS ***
    The hold queue creation routine in DFSYFD00 was enhanced to
    add additional checkings before it creates an hold queue.
    When the tpipe is a sync TPIPE or the client supports re-sync,
    we will not create a hold queue for the tpipe.
    

Temporary fix

  • *********
    * HIPER *
    *********
    

Comments

APAR Information

  • APAR number

    PI65533

  • Reported component name

    IMS V13

  • Reported component ID

    5635A0400

  • Reported release

    300

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-07-08

  • Closed date

    2016-07-21

  • Last modified date

    2016-08-02

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

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

    UI39565

Modules/Macros

  • DFSYFD00
    

Fix information

  • Fixed component name

    IMS V13

  • Fixed component ID

    5635A0400

Applicable component levels

  • R300 PSY UI39565

       UP16/07/27 P F607 Ž

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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Platform":[{"code":"PF054","label":"z Systems"}],"Version":"300","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
14 December 2020