|
View previous topic :: View next topic
|
| Author |
Message |
danik56
New User
Joined: 08 Mar 2017
Posts: 52
Location: Israel
|
|
|
|
I have configured MQMONITOR as outlined in the IBM doc but the CKTI transaction is not started. I can start it manually via CKQC.
Any idea what I am missing here ? |
|
| Back to top |
|
 |
Garry Carroll
Senior Member
Joined: 08 May 2006
Posts: 1193
Location: Dublin, Ireland
|
|
|
|
Any chance you have different security permissions to the CICS region? I assume you have, or defaulted, AUTOSTART(YES).
Garry. |
|
| Back to top |
|
|
Rohit Umarjikar
Global Moderator
Joined: 21 Sep 2010
Posts: 3053
Location: NYC,USA
|
|
| Back to top |
|
|
danik56
New User
Joined: 08 Mar 2017
Posts: 52
Location: Israel
|
|
|
|
I do not see any error messages related to CKTI in the log.
I have AUTOSTART(YES) set.
I did find apar PI90616 that corrects a MQMONITOR related issue but I still need to check if this apar was included in the May 18 ADCD for z/OS 2.3. |
|
| Back to top |
|
|
danik56
New User
Joined: 08 Mar 2017
Posts: 52
Location: Israel
|
|
|
|
I also found that by issuing CEMT SET MQMONITOR(name) START the log shows it failed with INVREQ RESP2=6.
I don't see any reason for this failure |
|
| Back to top |
|
|
Garry Carroll
Senior Member
Joined: 08 May 2006
Posts: 1193
Location: Dublin, Ireland
|
|
|
|
CEMT SET MQMONITOR takes values AUTOSTART or STARTED, not START.
Garry |
|
| Back to top |
|
|
Rohit Umarjikar
Global Moderator
Joined: 21 Sep 2010
Posts: 3053
Location: NYC,USA
|
|
|
|
| I am Sure you must have done but just check if you added initiation queue to INITPARM during the set up. |
|
| Back to top |
|
|
danik56
New User
Joined: 08 Mar 2017
Posts: 52
Location: Israel
|
|
|
|
| Garry Carroll wrote: |
CEMT SET MQMONITOR takes values AUTOSTART or STARTED, not START.
Garry |
It gives same error with STARTED and the QNAME is set to correct initiation queue name |
|
| Back to top |
|
|
danik56
New User
Joined: 08 Mar 2017
Posts: 52
Location: Israel
|
|
|
|
| Rohit Umarjikar wrote: |
| I am Sure you must have done but just check if you added initiation queue to INITPARM during the set up. |
Initiation queue name is defined correctly in the MQMONITOR resource definition. Btw, It seems INITPARM is no longer valid in the SIT for version 5.4 |
|
| Back to top |
|
|
danik56
New User
Joined: 08 Mar 2017
Posts: 52
Location: Israel
|
|
|
|
Issue still not resolved after applying APAR PI90616
No error in the log indicating why CKTI is not started by MQMONITOR |
|
| Back to top |
|
|
danik56
New User
Joined: 08 Mar 2017
Posts: 52
Location: Israel
|
|
|
|
To clarify, the MQMONITOR process fails to start and as a result CKTI does not start either.
Using CEMT to inquire on the MQM status shows it is STOPPED.
Attempting to use CEMT to change the MQM state to STARTED fails and the log shows :
CEMT SET MQMONITOR(MQ2) MONSTATUS(STARTED) RESP(INVREQ) RESP2(6).
I have no clue why RESP2(6) is returned. The MQM resource definition seems fine to me. |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA
|
|
|
|
| Quote: |
| I have no clue why RESP2(6) is returned. The MQM resource definition seems fine to me. |
You really need to learn how to use the manuals. It takes only a few seconds to find the SPI manual information about INVREQ on CICS SET MQMONITOR. And the manual says about RESP2(6):
| Quote: |
| An attempt to start the MQ monitor has failed. Verify TRANID and USERID attributes as well as security definitions. |
The resource definition seems fine to you, but obviously the computer does not agree. As the manual suggests, check the TRANID, USERID, and security definitions. There is SOMETHING wrong since you are not getting the MQMONITOR started. |
|
| Back to top |
|
|
danik56
New User
Joined: 08 Mar 2017
Posts: 52
Location: Israel
|
|
|
|
I read the manual very carefully and followed the instructions to the letter.
The userid and transid are correct.
CICS is running with SEC=NO, so I am not sure what security definitions I should check? |
|
| Back to top |
|
|
danik56
New User
Joined: 08 Mar 2017
Posts: 52
Location: Israel
|
|
|
|
After looking at AUX trace I found the cause for the failure.
CSD didn't include a program definition for DFHMQMNS.
After redoing the CSD upgrade, MQMONITOR now starts fine. |
|
| Back to top |
|
|
|
|
