| Author |
Message
|
| skiv |
 Posted: Tue Jul 11, 2006 2:34 am Post subject: MQOPEN question |
 |
|
Apprentice
Joined: 19 Jun 2006
Posts: 33
|
Hi
May I ask in the API crossing exit, the MQOPEN functions, how can I stop the connections or anything that can prevent the client from continuing to publish?
thanks alot |
|
| Back to top |
|
 |
| wschutz |
| Posted: Tue Jul 11, 2006 2:41 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Have the exit return a non-zero CC and RC.
_________________
-wayne |
|
| Back to top |
|
|
| skiv |
| Posted: Tue Jul 11, 2006 4:24 pm Post subject: |
|
|
Apprentice
Joined: 19 Jun 2006
Posts: 33
|
| I have the cc set to MQCC_FAILED and rc set to MQRC_NOT_AUTHORIZED.. but my publisher is still sending |
|
| Back to top |
|
|
| wschutz |
| Posted: Tue Jul 11, 2006 4:31 pm Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
sorry. mean to say set
ExitResponse to MQXCC_SUPPRESS_FUNCTION 
_________________
-wayne |
|
| Back to top |
|
|
| skiv |
| Posted: Tue Jul 11, 2006 7:37 pm Post subject: |
|
|
Apprentice
Joined: 19 Jun 2006
Posts: 33
|
I set that but still no use....
set it inside the MQOPEN function am I right?
pExitParms->ExitResponse = MQXCC_SUPPRESS_FUNCTION; |
|
| Back to top |
|
|
| wschutz |
| Posted: Wed Jul 12, 2006 2:35 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Yes, that should work..are you SURE your exit is being called.
Doc at:
http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/index.jsp?topic=/com.ibm.mq.amqzag.doc/amqzag08252.htm
| Quote: |
MQXCC_SUPPRESS_FUNCTION
Suppress function.
If an MQXR_BEFORE exit function returns this value, the queue manager sets the completion code for the API call to MQCC_FAILED, the reason code to MQRC_SUPPRESSED_BY_EXIT, and the API call is skipped. If returned by the MQXF_DATA_CONV_ON_GET exit function, data conversion is skipped.
The ExitResponse2 field must be set by the exit function to indicate whether the remaining MQXR_BEFORE exit functions and their matching MQXR_AFTER exit functions should be invoked. Any of these exit functions can alter the completion code and reason code of the API call that were set by the queue manager.
If an MQXR_AFTER or MQXR_CONNECTION exit function returns this value, the queue manager continues processing as though the exit had returned MQXCC_FAILED.
MQXCC_SKIP_FUNCTION
Skip function.
This is the same as MQXCC_SUPPRESS_FUNCTION, except the exit function can set the completion code and reason code of the API call.
|
_________________
-wayne |
|
| Back to top |
|
|
| skiv |
| Posted: Wed Jul 12, 2006 5:58 pm Post subject: |
|
|
Apprentice
Joined: 19 Jun 2006
Posts: 33
|
Sorry it works.. my mistake in the coding part...
Thanks alot for your help |
|
| Back to top |
|
|
|
|
