| Author |
Message
|
| rkv |
 Posted: Mon Jan 13, 2003 4:19 am Post subject: Messages are getting lost |
 |
|
Newbie
Joined: 13 Jan 2003
Posts: 5
|
Hi all,
Please help me out.
My cobol program is running as an IMS transaction using IMS bridge.Incoming message from MQSI hub are being read using GU call then the response is being sent back to hub using MQPUT1. We are using Clustering of MQSeries.The program recieves 4000 input messages from hub in about 30 minutes . Now this program should send 4000 replies corresponding to each of the input message but it is able to send only 99% of the replies .I donot know where are these 1% replies are going.My program is also not abending.
Can somebody please help.
Regards
RKV
_________________
RKV |
|
| Back to top |
|
 |
| PeterPotkay |
| Posted: Mon Jan 13, 2003 7:01 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7723
|
Could some of the messages be expiring before you account for them.
Can you prove you did 4000 succesful PUTS? What does your code do if the MQPUT1 fails? Does it alert you, or just go on?
Can you prove that you succesfully sent 4000 messages to the bridge?
Are you sure that all 4000 messages have valid reply2queue info?
Looks like a couple of days ago you had the opposite problem 
http://www.mqseries.net/phpBB2/viewtopic.php?t=7071
What did you do to solve that (and maybe create this?)
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| rkv |
| Posted: Tue Jan 14, 2003 9:03 pm Post subject: |
|
|
Newbie
Joined: 13 Jan 2003
Posts: 5
|
Thanks Peter,
Could some of the messages be expiring before you account for them.?
We have not checked that.But even if some of the message are expiring then the GU call for reading input message should indicate something.I am not sure on this?
If MQPUT1 fails then the program will abend with corresponding reason code.
There is no way to prove that my program sent 4000 messages to the bridge.We cannot even use the display statements as the IMS region is so configured that it can only show abend messages and not display statements of the cobol program.If we use display statements then the program goes for a system abend.
Regards
RKV
_________________
RKV |
|
| Back to top |
|
|
| oz1ccg |
| Posted: Tue Jan 14, 2003 11:58 pm Post subject: |
|
|
Yatiri
Joined: 10 Feb 2002
Posts: 628
Location: Denmark
|
Hi,
What you could do is running a GTF trace on mqseries as explained in problem determination. This gives you the whole picture of who is doing what and when.
You will see data, controlblocks, options, reasoncodes etc
Well, I know it's not a pretty way to go but it's usefull when caught in the snakepit
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 |
|
|
| PeterPotkay |
| Posted: Wed Jan 15, 2003 4:55 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7723
|
You can prove how many messages went into the Bridge queue and out of the Bridge queue by doing a queue statistics command on the queue. This will give you messages in and out of a queue.
You can also do this queue statitics command on the reply queue, to see exactly what went in and out from it.
If you have dedicated XMIT queues and channels for this test, you can run the command against the XMIT queues.
Watch the DLQ depths (you do have DLQs defind for all the QMs, right) for all QMs involved.
When I mentioned expired messages, I thought so more for the replies expiring than the requests. Verify the value being used for all messages on both PUTs.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| rkv |
| Posted: Wed Jan 15, 2003 9:51 pm Post subject: |
|
|
Newbie
Joined: 13 Jan 2003
Posts: 5
|
Jørgen Pedersen and Peter thank you very much for your kindness,
We are working (India) for some client and do not have administrative access to mqseries on mainframe. Even to know that our program(florida) is making successful MQ calls or not is told to us by MQSI(hub)people(phoenix) as they have it on windows Nt.
Thank you again for all the support and cooperation.
Regards
RKV
_________________
RKV |
|
| Back to top |
|
|
|
|
