ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General Discussion » Trigger

Post new topic  Reply to topic Goto page Previous  1, 2
 Trigger « View previous topic :: View next topic » 
Author Message
Dilrukshi
PostPosted: Fri Feb 21, 2003 3:38 am    Post subject: Reply with quote

Apprentice

Joined: 28 Apr 2002
Posts: 29

Hi,
I tried like wht u said still iam not successful. Could there be any problem with the MQSeries set up? I found a property like API exit: off in the Queue Manager properties. Wht does that mean? Can i set it on and will it be useful for me?
detail
Back to top
View user's profile Send private message
mgrabinski
PostPosted: Fri Feb 21, 2003 3:49 am    Post subject: Reply with quote

Master

Joined: 16 Oct 2001
Posts: 246
Location: Katowice, Poland

I've almost run out of ideas what is wrong but thee are still few question to ask:
Are you sure that there is no another trigger monitor active (possibly in another CICS region) on the same initiation queue?
Are there any messages in the dead letter queue?
Is there anything conected to your problem in the log?
Again, had the triggering queue been empty before you put a message there?
_________________
Marcin Grabinski <><
Back to top
View user's profile Send private message
Dilrukshi
PostPosted: Fri Feb 21, 2003 4:00 am    Post subject: Reply with quote

Apprentice

Joined: 28 Apr 2002
Posts: 29

hi
yes there are messages in the dead letter Queue.
Back to top
View user's profile Send private message
mgrabinski
PostPosted: Fri Feb 21, 2003 4:42 am    Post subject: Reply with quote

Master

Joined: 16 Oct 2001
Posts: 246
Location: Katowice, Poland

That's good! (I mean good for solving the problem

Can you get/browse those messages and see the reason codes?
You will find the reason code in the data part of the messages in DLQ, bytes 12th and 13th; they are in hex - convert them to decimal and consult with MQ manuals or post them here (if you choose to post, please post the whole message found in DLQ)
_________________
Marcin Grabinski <><
Back to top
View user's profile Send private message
Dilrukshi
PostPosted: Fri Feb 21, 2003 5:01 am    Post subject: Reply with quote

Apprentice

Joined: 28 Apr 2002
Posts: 29

This is the message

DLH &#9786; &#9786;?ATGLQUEUE MQA1
&#9787;? &#9786;?MQSTR &#9786;A06C001 CKTI 2002
040804451248èÇÑ??Ñ?????????????>?ÇÑ%
Back to top
View user's profile Send private message
mgrabinski
PostPosted: Fri Feb 21, 2003 6:21 am    Post subject: Reply with quote

Master

Joined: 16 Oct 2001
Posts: 246
Location: Katowice, Poland

I've made a mistake, the reason code is on bytes 11th end 12th
Nevertheless, I don't know how to read your DLQ message. I can see there your initiation queue name - ATGLQUEUE and it shoud start on the 13th byte. So I guess that the value '&#9786;?' represents the reason code, but I cannot make anything out of it. How is it coded? How did you get this message? Can you post the message in a more readable format or in hex?

For comparison, here is a sample meesage from my DLQ on a mainframe manager (I've cut and pasted it from my terminal emulator session):

Quote:

DLH KSP.INITQ WQP9 &#258;MQSTR WAP9W9A4CKTI 2003012216150216


The reason code here is invisible (it is 010A in hex which is 266 dec., meaning MQFB_TM_ERROR which means that the trigger message had a wrong format), but you can see other parts - initq name, qmgr name, CICS region and transaction name and finally date and time.

Could post something similiar to my example?[/quote]
_________________
Marcin Grabinski <><
Back to top
View user's profile Send private message
Dilrukshi
PostPosted: Mon Feb 24, 2003 12:27 am    Post subject: Reply with quote

Apprentice

Joined: 28 Apr 2002
Posts: 29

Hi,
Iam getting an information like this in the task list. Can this be used to trace back abt wht is happening?

CKQCM3 Display Task panel

Read task status information. Then press F12 to cancel.

Tasks 1 to 2 of 2

Txn User Task Task Thread Total Res In Last Thread
Id Id No. Status Status APIs Sec API-X MQ-Call ID
---- -------- ----- -------- -------- ---------- --- --- ---------- --------
CKTI STCCICS 00024 Normal Msg Wait 2 No No MQGET 09EEC1C8
CKTI WBS001 00598 Normal Msg Wait 3 No No MQGET 09EEC510


Thanks,
Dil
Back to top
View user's profile Send private message
oz1ccg
PostPosted: Mon Feb 24, 2003 2:14 am    Post subject: Reply with quote

Yatiri

Joined: 10 Feb 2002
Posts: 628
Location: Denmark

Hi,

when working on Z/OS I can recoment the supportpack MA10, which is MQBROWSE, yes exactly the same as the normal ISPF browse. MQBROWSE is based on on ISPF-BRIF.

The link is here:
http://www-3.ibm.com/software/ts/mqseries/txppacs/ma10.html

As I see it, it's one of the best supportpacks, even when it's a old one

Here is a snapshot of my DLQ:
Code:
 BROWSE QU QUEUE-MIP9.SAVED.VALID.DEADLET.QUEUE ----- Line 00000000 Col 001 080
 COMMAND ===>                                                  SCROLL ===> CSR 
********************************* Top of Data **********************************
                                                                               
                                                                               
 ------------------------------------------------------------------------------
DLH ........INIT.MCPCICS.Q01                                MIP9               
CDC400000000CDCE4DCDCCCE4DFF44444444444444444444444444444444DCDF4444444444444444
4380000100199593B4373932B8010000000000000000000000000000000049790000000000000000
 ------------------------------------------------------------------------------
DLH ........INIT.MCPCICS.Q01                                MIP9               
CDC400000000CDCE4DCDCCCE4DFF44444444444444444444444444444444DCDF4444444444444444
4380000100199593B4373932B8010000000000000000000000000000000049790000000000000000
 ------------------------------------------------------------------------------
DLH ........INIT.MCPCICS.Q01                                MIP9               
CDC400000000CDCE4DCDCCCE4DFF44444444444444444444444444444444DCDF4444444444444444
4380000100199593B4373932B8010000000000000000000000000000000049790000000000000000
 ------------------------------------------------------------------------------
DLH ........INIT.MCPCICS.Q01                                MIP9               
CDC400000000CDCE4DCDCCCE4DFF44444444444444444444444444444444DCDF4444444444444444
43800001001B9593B4373932B8010000000000000000000000000000000049790000000000000000
 ------------------------------------------------------------------------------
DLH ........INIT.MCPCICS.Q01                                MIP9               
CDC400000000CDCE4DCDCCCE4DFF44444444444444444444444444444444DCDF4444444444444444
43800001001B9593B4373932B8010000000000000000000000000000000049790000000000000000
 ------------------------------------------------------------------------------
DLH ........INIT.MCPCICS.Q01                                MIP9               
CDC400000000CDCE4DCDCCCE4DFF44444444444444444444444444444444DCDF4444444444444444
43800001001B9593B4373932B8010000000000000000000000000000000049790000000000000000
 ------------------------------------------------------------------------------


In the exapmple above it's quite easy to see the format on the DLH and the reason code 109(MQFB_APPL_CANNOT_BE_STARTED) and 10B(MQFB_APPL_TYPE_ERROR).

By the way, have you looked into the CICS log (of the CICS running CKTI and mybee also evt. the backend CICS), there might some interesting log entries there aswell.

Just my $0.02
_________________
Regards, Jørgen
Home of BlockIP2, the last free MQ Security exit ver. 3.00
Cert. on WMQ, WBIMB, SWIFT.
Back to top
View user's profile Send private message Send e-mail Visit poster's website MSN Messenger
oz1ccg
PostPosted: Tue Feb 25, 2003 3:05 pm    Post subject: Reply with quote

Yatiri

Joined: 10 Feb 2002
Posts: 628
Location: Denmark

Hi Dilrukshi,

What happens, have you get the thing rolling ... ???

Just interested ....
_________________
Regards, Jørgen
Home of BlockIP2, the last free MQ Security exit ver. 3.00
Cert. on WMQ, WBIMB, SWIFT.
Back to top
View user's profile Send private message Send e-mail Visit poster's website MSN Messenger
Dilrukshi
PostPosted: Wed Feb 26, 2003 12:52 am    Post subject: Reply with quote

Apprentice

Joined: 28 Apr 2002
Posts: 29

Hi,
Nope. I didn't get any clue from the DLQ. But i have another doubt in this. Does the MQSeries CICS bridge play any role in Triggerring?

Thanks
Dil
Back to top
View user's profile Send private message
oz1ccg
PostPosted: Wed Feb 26, 2003 6:18 am    Post subject: Reply with quote

Yatiri

Joined: 10 Feb 2002
Posts: 628
Location: Denmark

Shure.... I found this in los manualos.... :
Quote:
| Errors detected by the CICS bridge cause the bridge to:
| * Back out the unit of work
| * Copy request messages to the dead-letter queue
| * Send an error reply message back to the client if a reply-to queue is
| available
| * Write a CSQC7nn message to the CICS CSMQ transient data queue or issue
| a transaction abend. Where it is possible to put a message on the
| reply-to queue, the message will contain this abend code


So to get further on we need to see the reason code in the DeadLetter header..... CICS bridge is painfull to debug....

Just my $0.02
_________________
Regards, Jørgen
Home of BlockIP2, the last free MQ Security exit ver. 3.00
Cert. on WMQ, WBIMB, SWIFT.
Back to top
View user's profile Send private message Send e-mail Visit poster's website MSN Messenger
mgrabinski
PostPosted: Wed Feb 26, 2003 11:16 pm    Post subject: Reply with quote

Master

Joined: 16 Oct 2001
Posts: 246
Location: Katowice, Poland

I think that the key to your problem is the message in DLQ. Can you find some way to post it in a readable form? Something like oz1ccg did..
When we see the reason code, we'll be able to figure out what's going on.

You can look at last May Xephon's MQUpdate. There is an utility that browses messages from DLQ - " Dead letter queue browser: MQSeries for OS/390 ". (The utility is mine, but I may not post it - copyright agreement with Xephon prohibits me from doing so). The utility gets the MQDLH structure and presents it in a convienent way.

Here is a sample view from my utility:
Code:

   Message Descriptor:                             
    MsgId:            CSQ WQP9        Žúí# VÅ¡&#728;   
    CorelId:                                     
    Report:           0                           
    MsgType:          1                           
    Expiry:           -1                         
    Feedback:         0                           
    Encoding:         785                         
    CodedCharSetId:   870                         
    Format:           MQDEAD                     
    Priority:         0                           
    Persistence:      1                           
    BackoutCount:     0                           
    ReplyToQ:         TEST                       
    ReplyToQMgr:      SPIN                       
    UserId:           SPRM                       
    AccountingToken:   1                         
    ApplIdentityData:                             
     PutApplType:      2                       
     PutApplName:      MQPUT                   
     PutDate:          20030122               
     PutTime:          16150212               
     ApplOriginData:                           
                                               
                                           
Dead letter header:                           
Type:        DLH                               
Reason:      266                               
DestQ:       KSP.INITQ                         
DestQMgr:    WQP9                             
Format:      MQSTR                             
Encodig:     785                               
CCSId:       870                               
PutApplType: 1                                 
PutApplName: WAP9W9A4CKTI                       
PutDate:     20030122 
PutTime:     16150216 


So I suggest purchasing the MQUpdate May issue and installing the browser.
Here is the link:
http://www.xephon.com/index/updates/MQu.html
_________________
Marcin Grabinski <><
Back to top
View user's profile Send private message
Dilrukshi
PostPosted: Fri Mar 14, 2003 4:46 am    Post subject: Trigger Reply with quote

Apprentice

Joined: 28 Apr 2002
Posts: 29

Hi,
Got another doubt. The Cics transaction which was mentioned in the Process definiton (the transaction to be triggered) shld it not contain a map?
Will MQseries not trigger a transaction with a map? Should i give a non map cics transaction in the process definition and then start another transaction which contains the map? Is this the architecture?

Kindly advice me.
Thaks in advance.
Dil
Back to top
View user's profile Send private message
mgrabinski
PostPosted: Fri Mar 14, 2003 5:11 am    Post subject: Reply with quote

Master

Joined: 16 Oct 2001
Posts: 246
Location: Katowice, Poland

When you trigger a CICS transaction, it doesn't get any terminal ID. To display a map, you need TERMID (as far I know - but I'm not CICS programming expert). If you try to display a map with no terminal assigned, it should abend.
_________________
Marcin Grabinski <><
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Goto page Previous  1, 2 Page 2 of 2

MQSeries.net Forum Index » General Discussion » Trigger
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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.