|
View previous topic :: View next topic
|
| Author |
Message |
arnab
New User
Joined: 13 Mar 2006
Posts: 59
Location: UK
|
|
|
|
Hello,
We have an online IMS system which writes into a MQ queue. However it fails everytime it tries to execute the MQ API command MQCONN. We only receive a System dump (SYSUDUMP) with a return code of 3042 and reason code of 05060024.
Looking into the Recovery termination logs (RTM2WA SUMMARY) , I could find the below:
+001C COMPLETION CODE 84000BE2
+008C ABENDING PROGRAM NAME/SVRB ADDRESS CSQQCONN
The completion code X'0BE2' is same as 3042 and CSQQCONN is probably the dynamic MQ caller.
Now I did look for 3042 but not sure if this is an IMS return code or the return code from MQ.
Other information:
SCROLL ===> CSR
IEA995I SYMPTOM DUMP OUTPUT 021
USER COMPLETION CODE=3042 REASON CODE=05060024
TIME=15.14.19 SEQ=17377 CPU=0000 ASID=01E9
PSW AT TIME OF ERROR 078D1E00 80B7D876 ILC 2 INTC 0D
NO ACTIVE MODULE FOUND
NAME=UNKNOWN
DATA AT PSW 00B7D870 - 00181610 0A0D5880 90CC4100
GR 0: 00000000_84000000 1: 00000000_84000BE2
2: 00000000_00000BE2 3: 00000000_80B7D832
4: 00000000_05060024 5: 00000000_00000080
6: 00000000_000060E4 7: 00000000_87000040
8: 00000000_008CE164 9: 00000000_000127C8
A: 00000000_000060C8 B: 00000000_7F57C928
C: 00000000_80B7D014 D: 00000000_000065AC
E: 00000000_80B7D8F0 F: 00000010_05060024
END OF SYMPTOM DUMP
Could you please advice on this and how I should proceed ?
Thanks in advance. |
|
| Back to top |
|
 |
arnab
New User
Joined: 13 Mar 2006
Posts: 59
Location: UK
|
|
|
|
Some more observations:
It is failing while trying to connect to the queue manager MQP1. Could this be a problem with the region (ASID) under which the IMS transaction is running that is not allowing it to connect to the MQ manager via the IMS bridge ?
Please help. |
|
| Back to top |
|
|
arnab
New User
Joined: 13 Mar 2006
Posts: 59
Location: UK
|
|
|
|
Hello,
The problem has been fixed now. It was a problem with the region under which the IMS transaction was running. It didnot have a SSM entry so couldnot access MQ.
Changing the transaction class, made it access MQ manager and it worked fine.
Thanks. |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Thank you for letting us know 
Your info may save someone else time in the future.
d |
|
| Back to top |
|
|
|
|
