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 System Services
Categories General System
Created by Guest
Created on Oct 26, 2018

RELATED IDEAS

OTMA settings should be in effect and honored when IMS starts to accept OTMA traffic

Customer is running with AOS=Y, but he has found that after an /ERE consequent to a IMS Cancel some CM1 Synclevel Confirm SL1 Messages were Enqueued with Affinity to FE IMS for a SERIAL PSB Transaction.
Input messages arrived from MQ before restart completed.
We thought this was caused by a "timing window" where Messages can be Enqueued before the APPC/OTMA SMQ ENABLEMENT ( AOS ) initialization completes. The Messages inserted with AFFINITY to FE IMS had in fact TYPE35 QLNQTIME prior to the time Message DFS2089I "APPC/OTMA SMQ Enablement active. RRS is used" was issued.
.
Having OTMA=Y specified in DFSPBxxx Procblib Member causes OTMA to be automatically started on every Restart. Once OTMA joins the XCF group, other members of the same group can start sending input to OTMA.
.
There is nothing however that can be done about this, since Restart hasn't completed before the OTMA clients started sending input. The only way to control when OTMA Clients can start sending Input is via the OTMA= parm and /STA OTMA. Similar issues exists with /STA DC. Both should only be started when IMS is ready to start processing transactions, otherwise timing issues and possible performance problems can occurs (i.e. flood conditions).
It is recommened that the customer change their OTMA= setting from OTMA=Y to OTMA=M. This will require issuing a /STA OTMA after every Restart of IMS. This will allow the customer to control when members connect to OTMA and eliminate the timing issue at restart.
.
The above suggestion however does not appear feasible to Customer, who would need to add the necessary logic to their Automation to manage this.
He has so decided to ask me open this RFE.
.
This subject has been discussed into RTC PMR Flow Work Item 102608 .

Idea priority High
  • Guest
    Reply
    |     Dec 13, 2018

    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 as there is an alternative route. On investigation we see that the IMS RRS function did not complete the initialization for some of your initial OTMA transactions from clients. This is a known behavior for both TM and OTMA. We recommend you to use the /START OTMA command, instead of OTMA=Y, to control when the client can submit transactions into OTMA. You can use automation to issue the /START OTMA command once you see the DFS2089I APPC/OTMA SMQ Enablement Active message.

    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.

    Sincerely
    Swetha Sridharan
    swetha.sridharan@ibm.com

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.