| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Security exit on AS/400 - 2012 Error |
« View previous topic :: View next topic » |
| Author |
Message
|
| tellmey |
 Posted: Thu Oct 14, 2004 10:05 am Post subject: Security exit on AS/400 - 2012 Error |
 |
|
Novice
Joined: 26 May 2004
Posts: 19
|
Hello All,
I have a security exit running on a Server-requester channel pair.
the Requester initiates the connection first and thru the security exit it sends its IP address & qmgr name to the server end.
So later on the server should be able to initiate the connection.
We has these exits running fine before between Unix-Windows workstations.
Now I am trying to port them to AS/400(server) - Windows(requester)
On the server end the IP address is updated correctly on the CONNAME of the channel. But still when I try to start the server channel it faces this 2012 error on an MQCONN.
Also the same MQCONN call works fine when the requester has initiated the connection.So I am thinking it is not a library issue.
If anyone has any suggestions please let me know
Thanks |
|
| Back to top |
|
 |
| clindsey |
| Posted: Thu Oct 14, 2004 11:13 am Post subject: |
|
|
Knight
Joined: 12 Jul 2002
Posts: 586
Location: Dallas, Tx
|
I had the same error once on AIX when I did not link the exit with the multi-threaded libs. That may be your problem too. Be sure you bind your exit code with QMQM/LIBMQM_R.
Charlie |
|
| Back to top |
|
|
| tellmey |
| Posted: Thu Oct 14, 2004 12:21 pm Post subject: Still doesnt work |
|
|
Novice
Joined: 26 May 2004
Posts: 19
|
Thanks Charlie
I have already tried that, but it still doesnt work.
MQCONN call works fine when requester starts the connection
It throws the 2012 error only when server end initiates the communication |
|
| Back to top |
|
|
| clindsey |
| Posted: Thu Oct 14, 2004 12:51 pm Post subject: |
|
|
Knight
Joined: 12 Jul 2002
Posts: 586
Location: Dallas, Tx
|
That is exactly the symptom I was getting. Sorry, I don't know much about iSeries. Is there any way you can 'dump' your channel exit to see the libs that are bound. Maybe there is "lib clean" proc that must be run to clear existing libs that are resident in shared memory.
Other than that, I am out of suggestions.
Good luck,
Charlie |
|
| Back to top |
|
|
| csmith28 |
| Posted: Thu Oct 14, 2004 4:26 pm Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
2012 X’07DC’ MQRC_ENVIRONMENT_ERROR
The call is not valid for the current environment.
v On z/OS, one of the following applies:
– An MQCONN or MQCONNX call was issued, but the application has been linked with
an adapter that is not supported in the environment in which the application is running.
For example, this can arise when the application is linked with the WebSphere MQ RRS
adapter, but the application is running in a DB2 Stored Procedure address space. RRS is
not supported in this environment. Stored Procedures wishing to use the WebSphere MQ
RRS adapter must run in a DB2 WLM-managed Stored Procedure address space.
– An MQCMIT or MQBACK call was issued, but the application has been linked with the
RRS batch adapter CSQBRSTB. This adapter does not support the MQCMIT and
MQBACK calls.
– An MQCMIT or MQBACK call was issued in the CICS or IMS environment.
– The RRS subsystem is not up and running on the z/OS system that ran the application.
v On Compaq OpenVMS Alpha, OS/2, OS/400, Compaq NonStop Kernel, UNIX systems, and
Windows, one of the following applies:
– The application is linked to the wrong libraries (threaded or nonthreaded).
– An MQBEGIN, MQCMIT, or MQBACK call was issued, but an external unit-of-work
manager is in use. For example, this reason code occurs on Windows when an MTS
object is running as a DTC transaction. This reason code also occurs if the queue
manager does not support units of work.
– The MQBEGIN call was issued in a WebSphere MQ client environment.
– An MQXCLWLN call was issued, but the call did not originate from a cluster workload
exit.
Corrective action: Do one of the following (as appropriate):v On z/OS:
– Link the application with the correct adapter.
– Modify the application to use the SRRCMIT and SRRBACK calls in place of the
MQCMIT and MQBACK calls. Alternatively, link the application with the RRS batch
adapter CSQBRRSI. This adapter supports MQCMIT and MQBACK in addition to
SRRCMIT and SRRBACK.
– Modify the application to use the SRRCMIT and SRRBACK calls in place of the
MQCMIT and MQBACK calls. Alternatively, link the application with the RRS batch
adapter CSQBRRSI. This adapter supports MQCMIT and MQBACK in addition to
SRRCMIT and SRRBACK.
– For a CICS or IMS application, issue the appropriate CICS or IMS call to commit or
backout the unit of work.
– Start the RRS subsystem on the z/OS system that is running the application.
v In the other environments:
– Link the application with the correct libraries (threaded or nonthreaded).
– Remove from the application the call that is not supported.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
|
| tellmey |
| Posted: Fri Oct 15, 2004 5:58 am Post subject: |
|
|
Novice
Joined: 26 May 2004
Posts: 19
|
I cleared the previous AMQZSTUB that was part of the bind directory and added LIBMQM_R.
Guess what happened...
when the requester inititates the connection, the server is throwing the 2012 error. And I manually set the conname on the server and tried to start the conneciton from the server end and that worked.
So now I have same exact opposite problem.
It sures makes me think its with the libraries.
But have no clue as to what is happening. |
|
| Back to top |
|
|
| tellmey |
| Posted: Fri Oct 15, 2004 10:23 am Post subject: |
|
|
Novice
Joined: 26 May 2004
Posts: 19
|
Do I need to use a threaded listener along with LIBMQM_R
Does anyone know? |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
