| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Conditions for output from MQGET Warning terminal |
« View previous topic :: View next topic » |
| Author |
Message
|
| mbnewbie |
 Posted: Thu Oct 24, 2013 10:53 pm Post subject: Conditions for output from MQGET Warning terminal |
 |
|
Novice
Joined: 04 Oct 2013
Posts: 19
|
A colleague of mine wanted to know the conditions under which the control would be passed to the warning terminal of the MQGET node. I did a search on the MQ infocenter and filtered on MQCC_WARNING and MQGET to get the following results:
>2110 (083E) (RC2110): MQRC_FORMAT_ERROR - IBM<
>2242 (08C2) (RC2242): MQRC_INCOMPLETE_MSG - IBM<
>2120 (0848) (RC2120): MQRC_CONVERTED_MSG_TOO_BIG - IBM<
>2033 (07F1) (RC2033): MQRC_NO_MSG_AVAILABLE - IBM<
>2119 (0847) (RC2119): MQRC_NOT_CONVERTED - IBM<
>2245 (08C5) (RC2245): MQRC_INCONSISTENT_UOW - IBM<
>2111 (083F) (RC2111): MQRC_SOURCE_CCSID_ERROR - IBM<
>2241 (08C1) (RC2241): MQRC_INCOMPLETE_GROUP - IBM<
>2150 (0866) (RC2150): MQRC_DBCS_ERROR - IBM<
>2190 (088E) (RC2190): MQRC_CONVERTED_STRING_TOO_BIG<
>2115 (0843) (RC2115): MQRC_TARGET_CCSID_ERROR - IBM<
>2003 (07D3) (RC2003): MQRC_BACKED_OUT - IBM<
>2244 (08C4) (RC2244): MQRC_INCONSISTENT_ENCODINGS - IBM<
>2080 (0820) (RC2080): MQRC_TRUNCATED_MSG_FAILED - IBM<
>2079 (081F) (RC2079): MQRC_TRUNCATED_MSG_ACCEPTED<
>2112 (0840) (RC2112): MQRC_SOURCE_INTEGER_ENC_ERROR<
>2117 (0845) (RC2117): MQRC_TARGET_DECIMAL_ENC_ERROR<
>2144 (0860) (RC2144): MQRC_TARGET_LENGTH_ERROR - IBM<
>2116 (0844) (RC2116): MQRC_TARGET_INTEGER_ENC_ERROR<
>2145 (0861) (RC2145): MQRC_SOURCE_BUFFER_ERROR - IBM<
>2143 (085F) (RC2143): MQRC_SOURCE_LENGTH_ERROR - IBM<
>2146 (0862) (RC2146): MQRC_TARGET_BUFFER_ERROR - IBM<
>2070 (0816) (RC2070): MQRC_SIGNAL_REQUEST_ACCEPTED<
>2209 (08A1) (RC2209): MQRC_NO_MSG_LOCKED - IBM<
>2532 (09E4) (RC2532): MQRC_MSG_HANDLE_COPY_FAILURE<
>2272 (08E0) (RC2272): MQRC_PARTIALLY_CONVERTED - IBM<
>2284 (08EC) (RC2284): MQRC_CHANNEL_CONV_ERROR - IBM<
>2225 (08B1) (RC2225): MQRC_Q_DEPTH_LOW - IBM<
Out of these 28 scenarios many can be eliminated because they will not occur during a MQGET from a MQGET node for e.g. Q_DEPTH_LOW.
Using similar logic I may be able to eliminate the following :
2110, 2242, 2120, 2033, 2119, 2245, 2111, 2241, 2150, 2190, 2115, 2003, 2244, 2112, 2117, 2144, 2116, 2145, 2143, 2146, 2070, 2209, 2532, 2272, 2284 & 2225. Most of these calls have MQGMO_CONVERT specified and I do not see this property in the MQGET node by default (can be set by a previous compute node though)hence eliminated these calls. So I am left with 2080, 2079. Please let me know if my understanding is correct and whether we can have any other scenarios for warning
Last edited by mbnewbie on Thu Oct 24, 2013 11:28 pm; edited 1 time in total |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Thu Oct 24, 2013 11:10 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
I think you need to look again at your logic.
2033 is a very common error/warning and your code really needs to be able to handle this properly.
as is 2003. how are you going to handle messages that have been read and then the transaction is rolled back and backed out.
I've seen most of these over the years and some can indeed be ignored but if you are going to code up some error handling for these then you really need to understand how and why they may occur and then apply that understanding to how broker works.
Generally, the only thing I specifically handle in my code are 2033 errors. BUT and this is important each use of an MQGET node has to be considered on its own merit.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| Esa |
| Posted: Thu Oct 24, 2013 11:17 pm Post subject: |
|
|
Grand Master
Joined: 22 May 2008
Posts: 1387
Location: Finland
|
| smdavies99 wrote: |
2033 is a very common error/warning and your code really needs to be able to handle this properly. |
I'm under the impression that 2033 is propagated to 'No Message' terminal, not 'Warning'. |
|
| 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
|
|
|
|
