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 Not under consideration
Workspace IMS Transaction Manager
Categories Open Access TM
Created by Guest
Created on Mar 19, 2021

RELATED IDEAS

Resume TPIPE wait forever cancel timer for IMS Connect shutdown

IMS Connect resume TPIPE clients permanently listening on TPIPEs to retrieve sychronous / asynchronous callout request messages or undeliverable / re-routed output messages are currently blocking a normal IMS Connect shutdown, because IMS Connect waits until they have got a message from OTMA on their resume TPIPE wait forever request and acknowledged it - which may take a long time if no messages are written into the TPIPE at this point in time. A cancel time for such resume TPIPE requests could help. The idea is to modify the resume TPIPE wait forever requests into resume TPIPE requests with a timeout matching the cancel timer setting when IMS Connect is requested to shut down. These clients then would block the IMS Connect shutdown only until this cancel time has passed by. It would be good if this time can be separately configured and is not fix set in IMS Connect or derived from a different setting. It would be also good if the client gets a unique IMS Connect return / reason code when the cancel happens, such that the client knows about the IMS Connect shutdown and doesn't immeadiatly retry.

Idea priority Medium
  • Guest
    Reply
    |     Dec 3, 2021

    Hi,

    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.

    At this time, after reviewing this request for enhancement and assessing its potential value, we have decided to reject it. The reason we are rejecting this item is there are several viable alternatives. Here are a few:

    Method 1: Stop Tmember

    1. Client sends ResumeTpipe wait forever request to ICON.
    2. Issue /STO TMEM HWS1 TPIPE CLIENT01 command.
    3. OTMA sends suspend tpipe protocol message to ICON.
    4. ICON sends rc=8 rsn=SUSPTPIP (non-TMRA rsn 82) to client and closes the connection.

    Reason code SUSPTPIP (82) indicates "IMS suspended the tpipe as a result of a /STO TMEMBER TPIPE command".

    With tpipe CLIENT01 stopped, if client CLIENT01 issues another ResumeTpipe request on a new connection to ICON/OTMA, OTMA will send sense code x0028 rsn code x0001 back to the client.
    Sense code x0028 rsn code x0001 indicates IMS rejecte the ResumeTpipe request because the tpipe is stopped.

    Method 2: Stop OTMA

    1. Client sends ResumeTpipe wait forever request to ICON.
    2. Issue /STO OTMA command.
    3. OTMA notifies ICON that it is stopped.
    4. ICON sends rc=44 rsn=255 to client and keeps client connection open in RECV state.

    Return code 44 indicates "The DATASTORE is no longer available". Reason code 255 is the timer value wait forever.
    With OTMA stopped, if client issues another ResumeTpipe request to ICON/OTMA, ICON will send rc=4 rsn=STP/CLSE back to the client.

    Method 3: Shutdown IMS

    1. Client sends ResumeTpipe wait forever request to ICON.
    2. Issue /CHE FREEZE command to shut down IMS.
    3. OTMA notifies ICON that it is stopped/shutting down.
    4. ICON sends rc=44 rsn=255 to client and keeps client connection open in RECV state.

    Return code 44 indicates "The DATASTORE is no longer available". Reason code 255 is the timer value wait forever.
    With IMS stopped, if client issues another ResumeTpipe request to ICON/OTMA, ICON will send rc=4 rsn=STP/CLSE back to the client.

    We appreciate your input to IMS, and we hope that you will continue to submit ideas for improvements as customer feedback is a key component to shaping the future direction of IMS.

    Thank you.

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.