IBM Z Software


This portal is to open public enhancement requests against IBM Z Software products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas

  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Add a new idea Subscribe
Status Delivered
Workspace IMS Transaction Manager
Categories General TM
Created by Guest
Created on Dec 11, 2019

RELATED IDEAS

Non-Stop TRAN and PSB

Customer requests Non-Stop TRAN and PSB to avoid DFS065 and U0456.

IMS stops transaction when transaction abend occurs. Following transactions are not processed and DFS065 message is sent back to the input terminal until /STA TRAN command is issued. Customer creates automation to issue /STA TRAN command when DFS554I message is issued but there are time lag between DFS554I and /STA TRAN. Some following transactions return DFS065 messages in customer environment that process 1,260 trx/sec. If DFS065 is returned, customer must operate terminal to re-input transaction.

In the same way, IMS stops PSB when BMP abend occurs.
Following BMPs using same PSB abend U0456 until /STA PGM command is issued.
Customer creates automation to issue /STA PGM command when DFS554I message is issued.
But ABEND U0456 occurs in some BMP's initiations because there are time lag between DFS554I and /STA PGM.

Customer wants to process next transaction because application bug almost never become clear in production system. Most abend reason is region timeout that depends on input data. Customer uses fast path transaction and fast path DB. Non-Discardable Messages exit routine(DFSNDMX0) is not called for non-message driven BMPs and IFPs.

Idea priority Medium
  • Guest
    Reply
    |     Sep 16, 2021

    It is our mission, within IMS, to deliver high quality code to our clients. Our goal is that this enhancement continues to help drive success for your company!

    I am excited to share with you that we have successfully delivered an enhancement that can help with the requested RFE ID 138834.

    This enhancement has been delivered via IMS service process:
    IMS 15 APAR[PTF]: PH31457[UI76732] - https://www.ibm.com/support/pages/apar/PH31457

    PH31457 enhances the DFSNDMX0 exit to support the message driven IFP regions operation. This allows system administrator to implement the DFSNDMX0 exit to specify what happens to transactions and programs when IMS calls the exit after an application program abends in an IFP region. This enhancement provides a more consistent mechanism to control the transactions and the programs after an application abends, across all dependent region types.

    Note: The support of not stop PSB is not included in APAR PH31457. The PSB support for this enhancement remains as an uncommitted candidate item in our backlog and will be tracked under RFE 128945 - http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=128945. Please refer to RFE 128945 for any updated status.

    Please share your feedback with us as you implement this enhancement.

    Have a great day!
    Haley Fung - hfung@us.ibm.com

  • Guest
    Reply
    |     Mar 5, 2020

    Thank you for your interest in keeping IMS a vital and successful product. Software development has continuously evolved during IMS's lifetime, and so has IMS itself. We have kept pace with, adopted, and implemented many industry standard best practices within our organization, including Continuous Delivery, Design Thinking, and Agile.

    When choosing new features to add from the list of requirements in our backlog, we assess which will bring the most value to as many clients as possible and prioritize those.

    After reviewing this request for enhancement and assessing its potential value, our decision is to add this item to our backlog. Items in our backlog are expected to be delivered within the next 18 months. We reserve the right to re-prioritize our backlog items as new requests come in. This helps ensure that we are constantly focused on providing the best value to all of our clients.


    Have a great day!
    Haley Fung - hfung@us.ibm.com

  • Guest
    Reply
    |     Dec 12, 2019

    This function should be extended to non-Fastpath transactions as well as the BMP and Fastpath transactions.
    This function should be selectable using the Stage1 APPLCTN and TRANSACT macros or through DRD or using an IMS Type2 command.

    If this function is delivered by PTF (as I fully expect since IMS V15.1 has moved to Continuous Delivery), there should be HOLD DATA to advise that any customer automation that pre-supposes IMS will stop and abending tran/program, will need to be revised to query the state of this new "non-stop" option, and handle a runaway abend situation in a different manner.

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.