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.
Republishing question as there was a typo in the last comment:
You mentioned you were installing CICS TS 5.4. Have you had a chance to look at the new MQMONITOR support in CICS TS 5.4 to see if this satisfies your requirement ?
You mentioned you were installing CICS TS 5.4. Have you had a chance to look at the new MQMONITOR support in CICS TS 5.3 to see if this satisfies your requirement ?
We've had favourable feedback from users, not about this specific message issue, but about the fact they can now configure the userids properly and the fact you can get CICS to start multiple CKTIs automatically, rather than previously releases when only one CKTI could be started automatically and you had to staart others yourself via use of CKQC.
If there were multiple ones would it show both ? Here is an example of the ones that come from the ACF2 system we have . We monitor on these messages for the health check of the MQ interface with CICS.
We have had time that the MQ was up but the CKTI was not started.... It was a timing issue.
00.25.55 STC79672 +DFHMQ0386 I MBCICO 455
455 02/12/2019 00:25:55 MBCICO STARTCKTI initiated from TERMID=MQ37
455 TRANID=MGQ4 USERID=TE9M13M and is accepted.
00.25.55 STC79672 +DFHMQ0386 I MBCICO 456
456 02/12/2019 00:25:55 MBCICO STARTCKTI initiated from TERMID=MQ98
456 TRANID=MGQ4 USERID=MP9M00M and is accepted.
Since we are now installing CICS 5.4 we should be able to test the facility and see if it will fit the purpose. Have you had feedback from this new enhancement from users ?
The new MQMONITOR resource introduced in CICS TS 5.4 provides the ability to uniquely indentify a CKTI instance mapping to a unique initiation queue, as well as providing configuration options to specify things like the userid the trigger monitor runs under and the userid the started task runs under.
Examples of messages produced are as follows:
11.05.14 STC43398 +DFHMQ0390 E IYK2ZFV1 240
240 02/10/2019 11:05:14 IYK2ZFV1 Unable to START transaction BooH
240 associated with MQMONITOR CSQ4SAMP. EIBFN=X'1008' EIBRESP=28
240 EIBRESP2=0 EIBRCODE=X'110000000000'.
11.11.22 STC43398 +DFHMQ0391 I 02/10/2019 11:11:22 IYK2ZFV1 Start requested for mqmonitor CSQ4SAMP, transaction CKTI.
11.11.27 STC43398 +DFHMQ0107 I 02/10/2019 11:11:27 IYK2ZFV1 A request to end CKTI has been received. CKTI ended.
11.11.27 STC43398 +DFHMQ0392 I 02/10/2019 11:11:27 IYK2ZFV1 Stop requested for mqmonitor CSQ4SAMP, transaction CKTI.
We believe this will satisfy the RFE. Whilst the messages do not contain the initiation queue name, this is not required as an EXEC CICS SET MQMONITOR(name) STARTED command for the specific MQMONITOR will start the CKTI instance for the associated initiation queue.