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
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
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.
This RFE is satisfied by CICS TS 5.4 which is generally available from today June 16th 2017.
For more information see the announcement letter https://www-01.ibm.com/common/ssi/cgi-bin/ssialias?infotype=an&subtype=ca&supplier=897&letternum=ENUS217-113
The new RDO-defined resource MQMONITOR provides control over the transaction ID and user ID under which a monitor task runs, while also specifying the user ID to start the application tasks if an alternative user ID is not provided by the application. Any number of MQMONITOR instances may be defined and installed, each of which can be a trigger monitor, an MQ bridge monitor, or a user-written monitor. Using the MQMONITOR resource removes the need to manually start and stop monitors with the CKQC transaction.
This RFE is satisfied by CICS TS 5.4 which was announced on May 16th 2017 with a planned general availability date of June 16th 2017.
For more information see the announcement letter https://www-01.ibm.com/common/ssi/cgi-bin/ssialias?infotype=an&subtype=ca&supplier=897&letternum=ENUS217-113
The new RDO-defined resource MQMONITOR provides control over the transaction ID and user ID under which a monitor task runs, while also specifying the user ID to start the application tasks if an alternative user ID is not provided by the application. Any number of MQMONITOR instances may be defined and installed, each of which can be a trigger monitor, an MQ bridge monitor, or a user-written monitor. Using the MQMONITOR resource removes the need to manually start and stop monitors with the CKQC transaction.
This is something we would like to address. The RFE is being moved into 'Planned for Future release' status. Please note:
IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM’s sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion.
Thanks for the clarification Toby.
To have the CKTI user ID being configurable will solve this requirement.
The purpose is to have CKTI and associated user transaction being started under a user ID that we can specify.
I like to ask what is the motivation is for wanting the M Qconnection started under PLTPI userid? Is it because you want to make sure CKTI runs under PLTPI and also the triggerred transaction? We have quite a number of requirements to be able to configure what userid CKTI runs under and also what userid the triggered transaction runs under. If we gave you the ability to specify the userid for CKTI and the userid for the triggered transactions independent of what userid was used to start the CICS-MQ interface, would that satisfy this requirement ?