View previous topic :: View next topic
|
Author |
Message |
sandy_venkat
New User
Joined: 16 May 2007 Posts: 35 Location: India
|
|
|
|
I am triggering a MQ from an IMS online screen. This MQ triggers a batch job which runs a program which has a cobol batch program that recieves the message sent by the online screen and writes into a simple FB file.
My issue is, the Receiving program abends giving SOC1 while trying to to connect to MQ (while calling using 'MQCONN'). Please help me to resolve this. |
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8696 Location: Dubuque, Iowa, USA
|
|
|
|
The error is in line 379. |
|
Back to top |
|
|
sandy_venkat
New User
Joined: 16 May 2007 Posts: 35 Location: India
|
|
|
|
Can you please elaborate on this? |
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8696 Location: Dubuque, Iowa, USA
|
|
|
|
Based on what you've provided so far, what kind of answer do you expect? This is not psychic day so unless you provide code and precise error messages, all we can do is guess. |
|
Back to top |
|
|
sandy_venkat
New User
Joined: 16 May 2007 Posts: 35 Location: India
|
|
|
|
I run the job which has my MQ mesage recieving program.
In the program,I move the queue name and try to connect to the MQ.
2000-PROCESS-MQ.
MOVE 'ABC.SCREEN.TO.XYZJOB.CONSIST' TO
Y4070-GET-OBJECTNAME
PERFORM Y4070-MQ-CONNECT
The MQ is tried to connect using the MQCONN call
Y4070-MQ-CONNECT.
CALL 'MQCONN' USING Y4070-MQM
Y4070-HCONN
Y4070-COMPCODE
Y4070-REASON
END-CALL
As soon as the call is completed (as checked from the debugger tool) the job comes out of this para and subsequently job abends with SOC1.
Do you thing the MQ setup is not correct?? |
|
Back to top |
|
|
sandy_venkat
New User
Joined: 16 May 2007 Posts: 35 Location: India
|
|
|
|
Y4070-REASON gives +0000000001
rest all are zeroes |
|
Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006 Posts: 6966 Location: porcelain throne
|
|
|
|
well
a SOC1 is a communication's error
a S0C1 is an operations' error.
having learned not to trust anything posted on this board by a TS,
i have no idea what you are encountering.
but, if I was you,
I would insure that all the necessary MQS loadlibs have been allocated by the COBOL step
and
I would insure that the proper MQS Stubs were allocated during the compile/link edit process.
do you have any batch, cobol, MQS programs running in your system?
if so, would use those as a basis of your comparision. |
|
Back to top |
|
|
sandy_venkat
New User
Joined: 16 May 2007 Posts: 35 Location: India
|
|
|
|
just found out that error code is 4039 |
|
Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006 Posts: 6966 Location: porcelain throne
|
|
Back to top |
|
|
sandy_venkat
New User
Joined: 16 May 2007 Posts: 35 Location: India
|
|
|
|
yes i checked it..
it states
"The channel was terminated because the user exit specified does not exist"
but i am not sure what 'user exit' means and where do we specify it. |
|
Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006 Posts: 6966 Location: porcelain throne
|
|
|
|
Quote: |
but i am not sure what 'user exit' means and where do we specify it.
|
well you have a choice here
if you have an existing MQS, batch, COBOL program that functions in your system, double check that the correct Stubs are accesssed and the proper MQS loadlibs are allocated. If that research proves fruitless then you are stuck learning about the quote above.
you may have multiple releases of MQS in your system. often using an earlier release load with a new release active MQS means changes.
this is the WebSphere MQ - Library were you can seach and learn - if that ends up being your only alternative. |
|
Back to top |
|
|
sandy_venkat
New User
Joined: 16 May 2007 Posts: 35 Location: India
|
|
|
|
I was using the CSQQCONN connector in my link edit include, which is for IMS . I used Batch connector 'CSQBSTUB' and it worked.
thanks. |
|
Back to top |
|
|
|