Portal | Manuals | References | Downloads | Info | Programs | JCLs | Mainframe wiki | Quick Ref
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Profile Log in to check your private messages Log in
 
CKTI not started in CICS 5.4

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> CICS
View previous topic :: :: View next topic  
Author Message
danik56

New User


Joined: 08 Mar 2017
Posts: 29
Location: Israel

PostPosted: Thu Jan 31, 2019 12:13 pm    Post subject: CKTI not started in CICS 5.4
Reply with quote

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
View user's profile Send private message

Garry Carroll

Senior Member


Joined: 08 May 2006
Posts: 1054
Location: Dublin, Ireland / Edinburgh, Scotland

PostPosted: Thu Jan 31, 2019 1:49 pm    Post subject:
Reply with quote

Any chance you have different security permissions to the CICS region? I assume you have, or defaulted, AUTOSTART(YES).

Garry.
Back to top
View user's profile Send private message
Rohit Umarjikar

Senior Member


Joined: 21 Sep 2010
Posts: 2175
Location: NY,USA

PostPosted: Thu Jan 31, 2019 8:46 pm    Post subject:
Reply with quote

Also, I guess you followed this procedure and hope that is correctly implemented and outlined.
https://www.ibm.com/support/knowledgecenter/en/SSGMCP_5.4.0/administering/mq/ckti-start-mqmonitor.html
In any any case did you find any Messages related to CKTI in region logs or dumps?
Back to top
View user's profile Send private message
danik56

New User


Joined: 08 Mar 2017
Posts: 29
Location: Israel

PostPosted: Fri Feb 01, 2019 11:35 am    Post subject: Reply to: CKTI not started in CICS 5.4
Reply with quote

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
View user's profile Send private message
danik56

New User


Joined: 08 Mar 2017
Posts: 29
Location: Israel

PostPosted: Fri Feb 01, 2019 12:56 pm    Post subject:
Reply with quote

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
View user's profile Send private message
Garry Carroll

Senior Member


Joined: 08 May 2006
Posts: 1054
Location: Dublin, Ireland / Edinburgh, Scotland

PostPosted: Fri Feb 01, 2019 1:29 pm    Post subject:
Reply with quote

CEMT SET MQMONITOR takes values AUTOSTART or STARTED, not START.

Garry
Back to top
View user's profile Send private message
Rohit Umarjikar

Senior Member


Joined: 21 Sep 2010
Posts: 2175
Location: NY,USA

PostPosted: Fri Feb 01, 2019 8:54 pm    Post subject:
Reply with quote

I am Sure you must have done but just check if you added initiation queue to INITPARM during the set up.
Back to top
View user's profile Send private message
danik56

New User


Joined: 08 Mar 2017
Posts: 29
Location: Israel

PostPosted: Fri Feb 01, 2019 9:28 pm    Post subject:
Reply with quote

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
View user's profile Send private message
danik56

New User


Joined: 08 Mar 2017
Posts: 29
Location: Israel

PostPosted: Fri Feb 01, 2019 10:03 pm    Post subject:
Reply with quote

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
View user's profile Send private message
danik56

New User


Joined: 08 Mar 2017
Posts: 29
Location: Israel

PostPosted: Sat Feb 02, 2019 3:12 pm    Post subject: Issue still not resolved after apar PI90616
Reply with quote

Issue still not resolved after applying APAR PI90616

No error in the log indicating why CKTI is not started by MQMONITOR
Back to top
View user's profile Send private message
danik56

New User


Joined: 08 Mar 2017
Posts: 29
Location: Israel

PostPosted: Sun Feb 17, 2019 5:08 pm    Post subject: Reply to: CKTI not started in CICS 5.4
Reply with quote

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
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 8455
Location: Dubuque, Iowa, USA

PostPosted: Sun Feb 17, 2019 6:26 pm    Post subject:
Reply with quote

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
View user's profile Send private message
danik56

New User


Joined: 08 Mar 2017
Posts: 29
Location: Israel

PostPosted: Sun Feb 17, 2019 6:37 pm    Post subject:
Reply with quote

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
View user's profile Send private message
danik56

New User


Joined: 08 Mar 2017
Posts: 29
Location: Israel

PostPosted: Sun Feb 17, 2019 10:20 pm    Post subject: Problem resolved
Reply with quote

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
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> CICS All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts CICS transaction priority vasanthz CICS 7 Fri Jul 12, 2019 12:12 am
No new posts CICS Web client request Uday Kumar R CICS 6 Fri May 17, 2019 9:13 pm
No new posts Identify who, from where, sign on CIC... Weilin Wen CICS 1 Thu May 09, 2019 1:23 pm
No new posts Need suggestion on CICS READ UPDATE subratarec CICS 8 Fri May 03, 2019 2:23 pm
No new posts logically splitting a CICS region - help jzhardy CICS 3 Tue Mar 26, 2019 4:52 am

Facebook
Back to Top
 
Job Vacancies | Forum Rules | Bookmarks | Subscriptions | FAQ | Polls | Contact Us