MVSFORUMS.com Forum Index MVSFORUMS.com
A Community of and for MVS Professionals
 
 FAQFAQ   SearchSearch   Quick Manuals   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

CKQC - Trigger Monitor display

 
Post new topic   Reply to topic   printer-friendly view    MVSFORUMS.com Forum Index -> CICS and Middleware
View previous topic :: View next topic  
Author Message
Manas Biswal
Intermediate


Joined: 29 Nov 2002
Posts: 382
Topics: 27
Location: Chennai, India

PostPosted: Tue Mar 09, 2004 12:05 pm    Post subject: CKQC - Trigger Monitor display Reply with quote

Hi all,

We just set up a CICS region to connect to a QM on our LPAR. When I run the CKQC transaction to check the connections, it is showing that the region is connected to the QM. But when I check the trigger monitor - CKTI, it is saying that there are no instances of the trigger monitor running. The following error is being displayed -
Quote:

CSQC457I CIC**** CSQCDSP No CKTI found. Display rejected


If I try to start the trigger monitor using the same transaction, it is displaying a successful start message -
Quote:

CSQC386I CIC**** CSQCSSQ STARTCKTI initiated from TERMID=GAAA TRANID=CKSQ
USERID=****** and is accepted


but again when I am displaying the trigger monitor, it is giving me the same error message. I also do not see the task in the region which is supposed to be running the CKTI transaction.
Can somebody please advise me on what to do here.

Thanks,
manas
Back to top
View user's profile Send private message Send e-mail Yahoo Messenger
kolusu
Site Admin
Site Admin


Joined: 26 Nov 2002
Posts: 12376
Topics: 75
Location: San Jose

PostPosted: Tue Mar 09, 2004 10:20 pm    Post subject: Reply with quote

Manas,

Code:

CSQC386I cics- applid csect- name command initiated from TERMID= term- id     
   TRANID= tran- id                                                           
                                                                               
   USERID= user- id and is accepted                                           
                                                                               
   Explanation: The MQSeries CICS adapter has processed the command command.   
   However, the CICS task might not have completed processing of the command   
   yet (for example, CKTI could be waiting for a certain event to occur before
   it can be stopped). command can be either STARTCKTI, STOPCKTI, or RESET.   
                                                                               
   Module: CSQCRST, CSQCSSQ                                                   
                                                                               
   Severity: 0                                                                 


I looked up the CSQC368I message and I found that even though you get a return code of zero CICS task might still be running and yet to complete.

kolusu
_________________
Kolusu
www.linkedin.com/in/kolusu
Back to top
View user's profile Send private message Send e-mail Visit poster's website
bob_buxton
Beginner


Joined: 20 Dec 2002
Posts: 44
Topics: 0
Location: Hampshire, England

PostPosted: Wed Mar 10, 2004 9:07 am    Post subject: Reply with quote

What is the name of the Initiation queue you are trying to use, does the queue exist in the queue manager. Remember queue names are case sensitive.

Check the CICS joblog, CKTI may have written messages there such as,
CSQC386I IYEBZCAD CSQCSSQ STARTCKTI initiated from TERMID=P086 TRANID=CKSQ
CSQC101D IYEBZCAD CSQCTASK Cannot open the initiation queue. MQCC=2 MQRC=2085
CSQC110I IYEBZCAD CSQCTASK Queue name = INITQ

2085 is queue not found
_________________
Bob Buxton
Ex Websphere MQ for zOS development
Back to top
View user's profile Send private message
Manas Biswal
Intermediate


Joined: 29 Nov 2002
Posts: 382
Topics: 27
Location: Chennai, India

PostPosted: Fri Mar 12, 2004 1:37 pm    Post subject: Reply with quote

Bingo Bob - I did find the messages in the Job log. The MQRC was 2035 which was due to insufficient authority to open the initiation queue. I got the access from mainframe security and now the trigger monitor is OK.

Thanks for your help.

Regards,
Manas
Back to top
View user's profile Send private message Send e-mail Yahoo Messenger
Display posts from previous:   
Post new topic   Reply to topic   printer-friendly view    MVSFORUMS.com Forum Index -> CICS and Middleware All times are GMT - 5 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


MVSFORUMS
Powered by phpBB © 2001, 2005 phpBB Group