/******************************************************************************/ /* Document : Messages, Reason Codes, Error codes of Websphere MQ */ /* Doc. Version : 3 */ /* File : messages_mq.txt */ /* Purpose : MQ messages for easy reference for anybody who */ /* might be interested. */ /* Date : 09/03/2009 */ /* Compiled by : Albert van der Sel */ /* Comment : You cannot really "read" this file. Use find/search of your */ /* editor to search for a code or any other identifier. */ /******************************************************************************/ REMARK: >>> This file could be of use for someone interested in MQ err codes. <<< >>> There is really nothing "spectecular" here. It's just a series of <<< >>> sections of codes with some explanation. It also contains some <<< >>> fixlists information, as well as some notes/threads about MQ errors,<<< >>> kernel parameters etc.. . <<< >>> <<< >>> Sometimes, codes are repeated in different lists, so if you search, <<< >>> you might want to repeat the search a few times. <<< Some Common Reason Codes: ========================= # 0 (0000) (RC0): MQRC_NONE # 900 (0384) (RC900): MQRC_APPL_FIRST # 999 (03E7) (RC999): MQRC_APPL_LAST # 2001 (07D1) (RC2001): MQRC_ALIAS_BASE_Q_TYPE_ERROR # 2002 (07D2) (RC2002): MQRC_ALREADY_CONNECTED # 2003 (07D3) (RC2003): MQRC_BACKED_OUT # 2004 (07D4) (RC2004): MQRC_BUFFER_ERROR # 2005 (07D5) (RC2005): MQRC_BUFFER_LENGTH_ERROR # 2006 (07D6) (RC2006): MQRC_CHAR_ATTR_LENGTH_ERROR # 2007 (07D7) (RC2007): MQRC_CHAR_ATTRS_ERROR # 2008 (07D8) (RC2008): MQRC_CHAR_ATTRS_TOO_SHORT # 2009 (07D9) (RC2009): MQRC_CONNECTION_BROKEN # 2010 (07DA) (RC2010): MQRC_DATA_LENGTH_ERROR # 2011 (07DB) (RC2011): MQRC_DYNAMIC_Q_NAME_ERROR # 2012 (07DC) (RC2012): MQRC_ENVIRONMENT_ERROR # 2013 (07DD) (RC2013): MQRC_EXPIRY_ERROR # 2014 (07DE) (RC2014): MQRC_FEEDBACK_ERROR # 2016 (07E0) (RC2016): MQRC_GET_INHIBITED # 2017 (07E1) (RC2017): MQRC_HANDLE_NOT_AVAILABLE # 2018 (07E2) (RC2018): MQRC_HCONN_ERROR # 2019 (07E3) (RC2019): MQRC_HOBJ_ERROR # 2020 (07E4) (RC2020): MQRC_INHIBIT_VALUE_ERROR # 2021 (07E5) (RC2021): MQRC_INT_ATTR_COUNT_ERROR # 2022 (07E6) (RC2022): MQRC_INT_ATTR_COUNT_TOO_SMALL # 2023 (07E7) (RC2023): MQRC_INT_ATTRS_ARRAY_ERROR # 2024 (07E8) (RC2024): MQRC_SYNCPOINT_LIMIT_REACHED # 2025 (07E9) (RC2025): MQRC_MAX_CONNS_LIMIT_REACHED # 2026 (07EA) (RC2026): MQRC_MD_ERROR # 2027 (07EB) (RC2027): MQRC_MISSING_REPLY_TO_Q # 2029 (07ED) (RC2029): MQRC_MSG_TYPE_ERROR # 2030 (07EE) (RC2030): MQRC_MSG_TOO_BIG_FOR_Q # 2031 (07EF) (RC2031): MQRC_MSG_TOO_BIG_FOR_Q_MGR # 2033 (07F1) (RC2033): MQRC_NO_MSG_AVAILABLE # 2034 (07F2) (RC2034): MQRC_NO_MSG_UNDER_CURSOR # 2035 (07F3) (RC2035): MQRC_NOT_AUTHORIZED # 2036 (07F4) (RC2036): MQRC_NOT_OPEN_FOR_BROWSE # 2037 (07F5) (RC2037): MQRC_NOT_OPEN_FOR_INPUT # 2038 (07F6) (RC2038): MQRC_NOT_OPEN_FOR_INQUIRE # 2039 (07F7) (RC2039): MQRC_NOT_OPEN_FOR_OUTPUT # 2040 (07F8) (RC2040): MQRC_NOT_OPEN_FOR_SET # 2041 (07F9) (RC2041): MQRC_OBJECT_CHANGED # 2042 (07FA) (RC2042): MQRC_OBJECT_IN_USE # 2043 (07FB) (RC2043): MQRC_OBJECT_TYPE_ERROR # 2044 (07FC) (RC2044): MQRC_OD_ERROR # 2045 (07FD) (RC2045): MQRC_OPTION_NOT_VALID_FOR_TYPE # 2046 (07FE) (RC2046): MQRC_OPTIONS_ERROR # 2047 (07FF) (RC2047): MQRC_PERSISTENCE_ERROR # 2048 (0800) (RC2048): MQRC_PERSISTENT_NOT_ALLOWED # 2049 (0801) (RC2049): MQRC_PRIORITY_EXCEEDS_MAXIMUM # 2050 (0802) (RC2050): MQRC_PRIORITY_ERROR # 2051 (0803) (RC2051): MQRC_PUT_INHIBITED # 2052 (0804) (RC2052): MQRC_Q_DELETED # 2053 (0805) (RC2053): MQRC_Q_FULL # 2055 (0807) (RC2055): MQRC_Q_NOT_EMPTY # 2056 (0808) (RC2056): MQRC_Q_SPACE_NOT_AVAILABLE # 2057 (0809) (RC2057): MQRC_Q_TYPE_ERROR # 2058 (080A) (RC2058): MQRC_Q_MGR_NAME_ERROR # 2059 (080B) (RC2059): MQRC_Q_MGR_NOT_AVAILABLE # 2061 (080D) (RC2061): MQRC_REPORT_OPTIONS_ERROR # 2062 (080E) (RC2062): MQRC_SECOND_MARK_NOT_ALLOWED # 2063 (080F) (RC2063): MQRC_SECURITY_ERROR # 2065 (0811) (RC2065): MQRC_SELECTOR_COUNT_ERROR # 2066 (0812) (RC2066): MQRC_SELECTOR_LIMIT_EXCEEDED # 2067 (0813) (RC2067): MQRC_SELECTOR_ERROR # 2068 (0814) (RC2068): MQRC_SELECTOR_NOT_FOR_TYPE # 2069 (0815) (RC2069): MQRC_SIGNAL_OUTSTANDING # 2070 (0816) (RC2070): MQRC_SIGNAL_REQUEST_ACCEPTED # 2071 (0817) (RC2071): MQRC_STORAGE_NOT_AVAILABLE # 2072 (0818) (RC2072): MQRC_SYNCPOINT_NOT_AVAILABLE # 2075 (081B) (RC2075): MQRC_TRIGGER_CONTROL_ERROR # 2076 (081C) (RC2076): MQRC_TRIGGER_DEPTH_ERROR # 2077 (081D) (RC2077): MQRC_TRIGGER_MSG_PRIORITY_ERR # 2078 (081E) (RC2078): MQRC_TRIGGER_TYPE_ERROR # 2079 (081F) (RC2079): MQRC_TRUNCATED_MSG_ACCEPTED # 2080 (0820) (RC2080): MQRC_TRUNCATED_MSG_FAILED # 2082 (0822) (RC2082): MQRC_UNKNOWN_ALIAS_BASE_Q # 2085 (0825) (RC2085): MQRC_UNKNOWN_OBJECT_NAME # 2086 (0826) (RC2086): MQRC_UNKNOWN_OBJECT_Q_MGR # 2087 (0827) (RC2087): MQRC_UNKNOWN_REMOTE_Q_MGR # 2090 (082A) (RC2090): MQRC_WAIT_INTERVAL_ERROR # 2091 (082B) (RC2091): MQRC_XMIT_Q_TYPE_ERROR # 2092 (082C) (RC2092): MQRC_XMIT_Q_USAGE_ERROR # 2093 (082D) (RC2093): MQRC_NOT_OPEN_FOR_PASS_ALL # 2094 (082E) (RC2094): MQRC_NOT_OPEN_FOR_PASS_IDENT # 2095 (082F) (RC2095): MQRC_NOT_OPEN_FOR_SET_ALL # 2096 (0830) (RC2096): MQRC_NOT_OPEN_FOR_SET_IDENT # 2097 (0831) (RC2097): MQRC_CONTEXT_HANDLE_ERROR # 2098 (0832) (RC2098): MQRC_CONTEXT_NOT_AVAILABLE # 2099 (0833) (RC2099): MQRC_SIGNAL1_ERROR # 2100 (0834) (RC2100): MQRC_OBJECT_ALREADY_EXISTS # 2101 (0835) (RC2101): MQRC_OBJECT_DAMAGED # 2102 (0836) (RC2102): MQRC_RESOURCE_PROBLEM # 2103 (0837) (RC2103): MQRC_ANOTHER_Q_MGR_CONNECTED # 2104 (0838) (RC2104): MQRC_UNKNOWN_REPORT_OPTION # 2105 (0839) (RC2105): MQRC_STORAGE_CLASS_ERROR # 2106 (083A) (RC2106): MQRC_COD_NOT_VALID_FOR_XCF_Q # 2107 (083B) (RC2107): MQRC_XWAIT_CANCELED # 2108 (083C) (RC2108): MQRC_XWAIT_ERROR # 2109 (083D) (RC2109): MQRC_SUPPRESSED_BY_EXIT # 2110 (083E) (RC2110): MQRC_FORMAT_ERROR # 2111 (083F) (RC2111): MQRC_SOURCE_CCSID_ERROR # 2112 (0840) (RC2112): MQRC_SOURCE_INTEGER_ENC_ERROR # 2113 (0841) (RC2113): MQRC_SOURCE_DECIMAL_ENC_ERROR # 2114 (0842) (RC2114): MQRC_SOURCE_FLOAT_ENC_ERROR # 2115 (0843) (RC2115): MQRC_TARGET_CCSID_ERROR # 2116 (0844) (RC2116): MQRC_TARGET_INTEGER_ENC_ERROR # 2117 (0845) (RC2117): MQRC_TARGET_DECIMAL_ENC_ERROR # 2118 (0846) (RC2118): MQRC_TARGET_FLOAT_ENC_ERROR # 2119 (0847) (RC2119): MQRC_NOT_CONVERTED # 2120 (0848) (RC2120): MQRC_CONVERTED_MSG_TOO_BIG # 2121 (0849) (RC2121): MQRC_NO_EXTERNAL_PARTICIPANTS # 2122 (084A) (RC2122): MQRC_PARTICIPANT_NOT_AVAILABLE # 2123 (084B) (RC2123): MQRC_OUTCOME_MIXED # 2124 (084C) (RC2124): MQRC_OUTCOME_PENDING # 2125 (084D) (RC2125): MQRC_BRIDGE_STARTED # 2126 (084E) (RC2126): MQRC_BRIDGE_STOPPED # 2127 (084F) (RC2127): MQRC_ADAPTER_STORAGE_SHORTAGE # 2128 (0850) (RC2128): MQRC_UOW_IN_PROGRESS # 2129 (0851) (RC2129): MQRC_ADAPTER_CONN_LOAD_ERROR # 2130 (0852) (RC2130): MQRC_ADAPTER_SERV_LOAD_ERROR # 2131 (0853) (RC2131): MQRC_ADAPTER_DEFS_ERROR # 2132 (0854) (RC2132): MQRC_ADAPTER_DEFS_LOAD_ERROR # 2133 (0855) (RC2133): MQRC_ADAPTER_CONV_LOAD_ERROR # 2134 (0856) (RC2134): MQRC_BO_ERROR # 2135 (0857) (RC2135): MQRC_DH_ERROR # 2136 (0858) (RC2136): MQRC_MULTIPLE_REASONS # 2137 (0859) (RC2137): MQRC_OPEN_FAILED # 2138 (085A) (RC2138): MQRC_ADAPTER_DISC_LOAD_ERROR # 2139 (085B) (RC2139): MQRC_CNO_ERROR # 2140 (085C) (RC2140): MQRC_CICS_WAIT_FAILED # 2141 (085D) (RC2141): MQRC_DLH_ERROR # 2142 (085E) (RC2142): MQRC_HEADER_ERROR # 2143 (085F) (RC2143): MQRC_SOURCE_LENGTH_ERROR # 2144 (0860) (RC2144): MQRC_TARGET_LENGTH_ERROR # 2145 (0861) (RC2145): MQRC_SOURCE_BUFFER_ERROR # 2146 (0862) (RC2146): MQRC_TARGET_BUFFER_ERROR # 2148 (0864) (RC2148): MQRC_IIH_ERROR # 2149 (0865) (RC2149): MQRC_PCF_ERROR # 2150 (0866) (RC2150): MQRC_DBCS_ERROR # 2152 (0868) (RC2152): MQRC_OBJECT_NAME_ERROR # 2153 (0869) (RC2153): MQRC_OBJECT_Q_MGR_NAME_ERROR # 2154 (086A) (RC2154): MQRC_RECS_PRESENT_ERROR # 2155 (086B) (RC2155): MQRC_OBJECT_RECORDS_ERROR # 2156 (086C) (RC2156): MQRC_RESPONSE_RECORDS_ERROR # 2157 (086D) (RC2157): MQRC_ASID_MISMATCH # 2158 (086E) (RC2158): MQRC_PMO_RECORD_FLAGS_ERROR # 2159 (086F) (RC2159): MQRC_PUT_MSG_RECORDS_ERROR # 2160 (0870) (RC2160): MQRC_CONN_ID_IN_USE # 2161 (0871) (RC2161): MQRC_Q_MGR_QUIESCING # 2162 (0872) (RC2162): MQRC_Q_MGR_STOPPING # 2163 (0873) (RC2163): MQRC_DUPLICATE_RECOV_COORD # 2173 (087D) (RC2173): MQRC_PMO_ERROR # 2183 (0887) (RC2183): MQRC_API_EXIT_LOAD_ERROR # 2184 (0888) (RC2184): MQRC_REMOTE_Q_NAME_ERROR # 2185 (0889) (RC2185): MQRC_INCONSISTENT_PERSISTENCE # 2186 (088A) (RC2186): MQRC_GMO_ERROR # 2187 (088B) (RC2187): MQRC_CICS_BRIDGE_RESTRICTION # 2188 (088C) (RC2188): MQRC_STOPPED_BY_CLUSTER_EXIT # 2189 (088D) (RC2189): MQRC_CLUSTER_RESOLUTION_ERROR # 2190 (088E) (RC2190): MQRC_CONVERTED_STRING_TOO_BIG # 2191 (088F) (RC2191): MQRC_TMC_ERROR # 2192 (0890) (RC2192): MQRC_PAGESET_FULL # 2192 (0890) (RC2192): MQRC_STORAGE_MEDIUM_FULL # 2193 (0891) (RC2193): MQRC_PAGESET_ERROR # 2194 (0892) (RC2194): MQRC_NAME_NOT_VALID_FOR_TYPE # 2195 (0893) (RC2195): MQRC_UNEXPECTED_ERROR # 2196 (0894) (RC2196): MQRC_UNKNOWN_XMIT_Q # 2197 (0895) (RC2197): MQRC_UNKNOWN_DEF_XMIT_Q # 2198 (0896) (RC2198): MQRC_DEF_XMIT_Q_TYPE_ERROR # 2199 (0897) (RC2199): MQRC_DEF_XMIT_Q_USAGE_ERROR # 2201 (0899) (RC2201): MQRC_NAME_IN_USE # 2202 (089A) (RC2202): MQRC_CONNECTION_QUIESCING # 2203 (089B) (RC2203): MQRC_CONNECTION_STOPPING # 2204 (089C) (RC2204): MQRC_ADAPTER_NOT_AVAILABLE # 2206 (089E) (RC2206): MQRC_MSG_ID_ERROR # 2207 (089F) (RC2207): MQRC_CORREL_ID_ERROR # 2208 (08A0) (RC2208): MQRC_FILE_SYSTEM_ERROR # 2209 (08A1) (RC2209): MQRC_NO_MSG_LOCKED # 2210 (08A2) (RC2210): MQRC_SOAP_DOTNET_ERROR # 2211 (08A3) (RC2211): MQRC_SOAP_AXIS_ERROR # 2212 (08A4) (RC2212): MQRC_SOAP_URL_ERROR # 2217 (08A9) (RC2217): MQRC_CONNECTION_NOT_AUTHORIZED # 2218 (08AA) (RC2218): MQRC_MSG_TOO_BIG_FOR_CHANNEL # 2219 (08AB) (RC2219): MQRC_CALL_IN_PROGRESS # 2220 (08AC) (RC2220): MQRC_RMH_ERROR # 2222 (08AE) (RC2222): MQRC_Q_MGR_ACTIVE # 2223 (08AF) (RC2223): MQRC_Q_MGR_NOT_ACTIVE # 2224 (08B0) (RC2224): MQRC_Q_DEPTH_HIGH # 2225 (08B1) (RC2225): MQRC_Q_DEPTH_LOW # 2226 (08B2) (RC2226): MQRC_Q_SERVICE_INTERVAL_HIGH # 2227 (08B3) (RC2227): MQRC_Q_SERVICE_INTERVAL_OK # 2228 (08B4) (RC2228): MQRC_RFH_HEADER_FIELD_ERROR # 2229 (08B5) (RC2229): MQRC_RAS_PROPERTY_ERROR # 2232 (08B8) (RC2232): MQRC_UNIT_OF_WORK_NOT_STARTED # 2233 (08B9) (RC2233): MQRC_CHANNEL_AUTO_DEF_OK # 2234 (08BA) (RC2234): MQRC_CHANNEL_AUTO_DEF_ERROR # 2235 (08BB) (RC2235): MQRC_CFH_ERROR # 2236 (08BC) (RC2236): MQRC_CFIL_ERROR # 2237 (08BD) (RC2237): MQRC_CFIN_ERROR # 2238 (08BE) (RC2238): MQRC_CFSL_ERROR # 2239 (08BF) (RC2239): MQRC_CFST_ERROR # 2241 (08C1) (RC2241): MQRC_INCOMPLETE_GROUP # 2242 (08C2) (RC2242): MQRC_INCOMPLETE_MSG # 2243 (08C3) (RC2243): MQRC_INCONSISTENT_CCSIDS # 2244 (08C4) (RC2244): MQRC_INCONSISTENT_ENCODINGS # 2245 (08C5) (RC2245): MQRC_INCONSISTENT_UOW # 2246 (08C6) (RC2246): MQRC_INVALID_MSG_UNDER_CURSOR # 2247 (08C7) (RC2247): MQRC_MATCH_OPTIONS_ERROR # 2248 (08C8) (RC2248): MQRC_MDE_ERROR # 2249 (08C9) (RC2249): MQRC_MSG_FLAGS_ERROR # 2250 (08CA) (RC2250): MQRC_MSG_SEQ_NUMBER_ERROR # 2251 (08CB) (RC2251): MQRC_OFFSET_ERROR # 2252 (08CC) (RC2252): MQRC_ORIGINAL_LENGTH_ERROR # 2253 (08CD) (RC2253): MQRC_SEGMENT_LENGTH_ZERO # 2255 (08CF) (RC2255): MQRC_UOW_NOT_AVAILABLE # 2256 (08D0) (RC2256): MQRC_WRONG_GMO_VERSION # 2257 (08D1) (RC2257): MQRC_WRONG_MD_VERSION # 2258 (08D2) (RC2258): MQRC_GROUP_ID_ERROR # 2259 (08D3) (RC2259): MQRC_INCONSISTENT_BROWSE # 2260 (08D4) (RC2260): MQRC_XQH_ERROR # 2261 (08D5) (RC2261): MQRC_SRC_ENV_ERROR # 2262 (08D6) (RC2262): MQRC_SRC_NAME_ERROR # 2263 (08D7) (RC2263): MQRC_DEST_ENV_ERROR # 2264 (08D8) (RC2264): MQRC_DEST_NAME_ERROR # 2265 (08D9) (RC2265): MQRC_TM_ERROR # 2266 (08DA) (RC2266): MQRC_CLUSTER_EXIT_ERROR # 2267 (08DB) (RC2267): MQRC_CLUSTER_EXIT_LOAD_ERROR # 2268 (08DC) (RC2268): MQRC_CLUSTER_PUT_INHIBITED # 2269 (08DD) (RC2269): MQRC_CLUSTER_RESOURCE_ERROR # 2270 (08DE) (RC2270): MQRC_NO_DESTINATIONS_AVAILABLE # 2271 (08DF) (RC2271): MQRC_CONN_TAG_IN_USE # 2272 (08E0) (RC2272): MQRC_PARTIALLY_CONVERTED # 2273 (08E1) (RC2273): MQRC_CONNECTION_ERROR # 2274 (08E2) (RC2274): MQRC_OPTION_ENVIRONMENT_ERROR # 2277 (08E5) (RC2277): MQRC_CD_ERROR # 2278 (08E6) (RC2278): MQRC_CLIENT_CONN_ERROR # 2279 (08E7) (RC2279): MQRC_CHANNEL_STOPPED_BY_USER # 2280 (08E8) (RC2280): MQRC_HCONFIG_ERROR # 2281 (08E9) (RC2281): MQRC_FUNCTION_ERROR # 2282 (08EA) (RC2282): MQRC_CHANNEL_STARTED # 2283 (08EB) (RC2283): MQRC_CHANNEL_STOPPED # 2284 (08EC) (RC2284): MQRC_CHANNEL_CONV_ERROR # 2285 (08ED) (RC2285): MQRC_SERVICE_NOT_AVAILABLE # 2286 (08EE) (RC2286): MQRC_INITIALIZATION_FAILED # 2287 (08EF) (RC2287): MQRC_TERMINATION_FAILED # 2288 (08F0) (RC2288): MQRC_UNKNOWN_Q_NAME # 2289 (08F1) (RC2289): MQRC_SERVICE_ERROR # 2290 (08F2) (RC2290): MQRC_Q_ALREADY_EXISTS # 2291 (08F3) (RC2291): MQRC_USER_ID_NOT_AVAILABLE # 2292 (08F4) (RC2292): MQRC_UNKNOWN_ENTITY # 2294 (08F6) (RC2294): MQRC_UNKNOWN_REF_OBJECT # 2295 (08F7) (RC2295): MQRC_CHANNEL_ACTIVATED # 2296 (08F8) (RC2296): MQRC_CHANNEL_NOT_ACTIVATED # 2297 (08F9) (RC2297): MQRC_UOW_CANCELED # 2298 (08FA) (RC2298): MQRC_FUNCTION_NOT_SUPPORTED # 2299 (08FB) (RC2299): MQRC_SELECTOR_TYPE_ERROR # 2300 (08FC) (RC2300): MQRC_COMMAND_TYPE_ERROR # 2301 (08FD) (RC2301): MQRC_MULTIPLE_INSTANCE_ERROR # 2302 (08FE) (RC2302): MQRC_SYSTEM_ITEM_NOT_ALTERABLE # 2303 (08FF) (RC2303): MQRC_BAG_CONVERSION_ERROR # 2304 (0900) (RC2304): MQRC_SELECTOR_OUT_OF_RANGE # 2305 (0901) (RC2305): MQRC_SELECTOR_NOT_UNIQUE # 2306 (0902) (RC2306): MQRC_INDEX_NOT_PRESENT # 2307 (0903) (RC2307): MQRC_STRING_ERROR # 2308 (0904) (RC2308): MQRC_ENCODING_NOT_SUPPORTED # 2309 (0905) (RC2309): MQRC_SELECTOR_NOT_PRESENT # 2310 (0906) (RC2310): MQRC_OUT_SELECTOR_ERROR # 2311 (0907) (RC2311): MQRC_STRING_TRUNCATED # 2312 (0908) (RC2312): MQRC_SELECTOR_WRONG_TYPE # 2313 (0909) (RC2313): MQRC_INCONSISTENT_ITEM_TYPE # 2314 (090A) (RC2314): MQRC_INDEX_ERROR # 2315 (090B) (RC2315): MQRC_SYSTEM_BAG_NOT_ALTERABLE # 2316 (090C) (RC2316): MQRC_ITEM_COUNT_ERROR # 2317 (090D) (RC2317): MQRC_FORMAT_NOT_SUPPORTED # 2318 (090E) (RC2318): MQRC_SELECTOR_NOT_SUPPORTED # 2319 (090F) (RC2319): MQRC_ITEM_VALUE_ERROR # 2320 (0910) (RC2320): MQRC_HBAG_ERROR # 2321 (0911) (RC2321): MQRC_PARAMETER_MISSING # 2322 (0912) (RC2322): MQRC_CMD_SERVER_NOT_AVAILABLE # 2323 (0913) (RC2323): MQRC_STRING_LENGTH_ERROR # 2324 (0914) (RC2324): MQRC_INQUIRY_COMMAND_ERROR # 2325 (0915) (RC2325): MQRC_NESTED_BAG_NOT_SUPPORTED # 2326 (0916) (RC2326): MQRC_BAG_WRONG_TYPE # 2327 (0917) (RC2327): MQRC_ITEM_TYPE_ERROR # 2328 (0918) (RC2328): MQRC_SYSTEM_BAG_NOT_DELETABLE # 2329 (0919) (RC2329): MQRC_SYSTEM_ITEM_NOT_DELETABLE # 2330 (091A) (RC2330): MQRC_CODED_CHAR_SET_ID_ERROR # 2331 (091B) (RC2331): MQRC_MSG_TOKEN_ERROR # 2332 (091C) (RC2332): MQRC_MISSING_WIH # 2333 (091D) (RC2333): MQRC_WIH_ERROR # 2334 (091E) (RC2334): MQRC_RFH_ERROR # 2335 (091F) (RC2335): MQRC_RFH_STRING_ERROR # 2336 (0920) (RC2336): MQRC_RFH_COMMAND_ERROR # 2337 (0921) (RC2337): MQRC_RFH_PARM_ERROR # 2338 (0922) (RC2338): MQRC_RFH_DUPLICATE_PARM # 2339 (0923) (RC2339): MQRC_RFH_PARM_MISSING # 2340 (0924) (RC2340): MQRC_CHAR_CONVERSION_ERROR # 2341 (0925) (RC2341): MQRC_UCS2_CONVERSION_ERROR # 2342 (0926) (RC2342): MQRC_DB2_NOT_AVAILABLE # 2343 (0927) (RC2343): MQRC_OBJECT_NOT_UNIQUE # 2344 (0928) (RC2344): MQRC_CONN_TAG_NOT_RELEASED # 2345 (0929) (RC2345): MQRC_CF_NOT_AVAILABLE # 2346 (092A) (RC2346): MQRC_CF_STRUC_IN_USE # 2347 (092B) (RC2347): MQRC_CF_STRUC_LIST_HDR_IN_USE # 2348 (092C) (RC2348): MQRC_CF_STRUC_AUTH_FAILED # 2349 (092D) (RC2349): MQRC_CF_STRUC_ERROR # 2350 (092E) (RC2350): MQRC_CONN_TAG_NOT_USABLE # 2351 (092F) (RC2351): MQRC_GLOBAL_UOW_CONFLICT # 2352 (0930) (RC2352): MQRC_LOCAL_UOW_CONFLICT # 2353 (0931) (RC2353): MQRC_HANDLE_IN_USE_FOR_UOW # 2354 (0932) (RC2354): MQRC_UOW_ENLISTMENT_ERROR # 2355 (0933) (RC2355): MQRC_UOW_MIX_NOT_SUPPORTED # 2356 (0934) (RC2356): MQRC_WXP_ERROR # 2357 (0935) (RC2357): MQRC_CURRENT_RECORD_ERROR # 2358 (0936) (RC2358): MQRC_NEXT_OFFSET_ERROR # 2359 (0937) (RC2359): MQRC_NO_RECORD_AVAILABLE # 2360 (0938) (RC2360): MQRC_OBJECT_LEVEL_INCOMPATIBLE # 2361 (0939) (RC2361): MQRC_NEXT_RECORD_ERROR # 2362 (093A) (RC2362): MQRC_BACKOUT_THRESHOLD_REACHED # 2363 (093B) (RC2363): MQRC_MSG_NOT_MATCHED # 2364 (093C) (RC2364): MQRC_JMS_FORMAT_ERROR # 2365 (093D) (RC2365): MQRC_SEGMENTS_NOT_SUPPORTED # 2366 (093E) (RC2366): MQRC_WRONG_CF_LEVEL # 2367 (093F) (RC2367): MQRC_CONFIG_CREATE_OBJECT # 2368 (0940) (RC2368): MQRC_CONFIG_CHANGE_OBJECT # 2369 (0941) (RC2369): MQRC_CONFIG_DELETE_OBJECT # 2370 (0942) (RC2370): MQRC_CONFIG_REFRESH_OBJECT # 2371 (0943) (RC2371): MQRC_CHANNEL_SSL_ERROR # 2373 (0945) (RC2373): MQRC_CF_STRUC_FAILED # 2374 (0946) (RC2374): MQRC_API_EXIT_ERROR # 2375 (0947) (RC2375): MQRC_API_EXIT_INIT_ERROR # 2376 (0948) (RC2376): MQRC_API_EXIT_TERM_ERROR # 2377 (0949) (RC2377): MQRC_EXIT_REASON_ERROR # 2378 (094A) (RC2378): MQRC_RESERVED_VALUE_ERROR # 2379 (094B) (RC2379): MQRC_NO_DATA_AVAILABLE # 2380 (094C) (RC2380): MQRC_SCO_ERROR # 2381 (094D) (RC2381): MQRC_KEY_REPOSITORY_ERROR # 2382 (094E) (RC2382): MQRC_CRYPTO_HARDWARE_ERROR # 2383 (094F) (RC2383): MQRC_AUTH_INFO_REC_COUNT_ERROR # 2384 (0950) (RC2384): MQRC_AUTH_INFO_REC_ERROR # 2385 (0951) (RC2385): MQRC_AIR_ERROR # 2386 (0952) (RC2386): MQRC_AUTH_INFO_TYPE_ERROR # 2387 (0953) (RC2387): MQRC_AUTH_INFO_CONN_NAME_ERROR # 2388 (0954) (RC2388): MQRC_LDAP_USER_NAME_ERROR # 2389 (0955) (RC2389): MQRC_LDAP_USER_NAME_LENGTH_ERR # 2390 (0956) (RC2390): MQRC_LDAP_PASSWORD_ERROR # 2391 (0957) (RC2391): MQRC_SSL_ALREADY_INITIALIZED # 2392 (0958) (RC2392): MQRC_SSL_CONFIG_ERROR # 2393 (0959) (RC2393): MQRC_SSL_INITIALIZATION_ERROR # 2394 (095A) (RC2394): MQRC_Q_INDEX_TYPE_ERROR # 2395 (095B) (RC2395): MQRC_CFBS_ERROR # 2396 (095C) (RC2396): MQRC_SSL_NOT_ALLOWED # 2397 (095D) (RC2397): MQRC_JSSE_ERROR # 2398 (095E) (RC2398): MQRC_SSL_PEER_NAME_MISMATCH # 2399 (095F) (RC2399): MQRC_SSL_PEER_NAME_ERROR # 2400 (0960) (RC2400): MQRC_UNSUPPORTED_CIPHER_SUITE # 2401 (0961) (RC2401): MQRC_SSL_CERTIFICATE_REVOKED # 2402 (0962) (RC2402): MQRC_SSL_CERT_STORE_ERROR # 2406 (0966) (RC2406): MQRC_CLIENT_EXIT_LOAD_ERROR # 2407 (0967) (RC2407): MQRC_CLIENT_EXIT_ERROR # 2409 (0969) (RC2409): MQRC_SSL_KEY_RESET_ERROR # 2411 (096B) (RC2411): MQRC_LOGGER_STATUS # 2412 (096C) (RC2412): MQRC_COMMAND_MQSC # 2413 (096D) (RC2413): MQRC_COMMAND_PCF # 2414 (096E) (RC2414): MQRC_CFIF_ERROR # 2415 (096F) (RC2415): MQRC_CFSF_ERROR # 2416 (0970) (RC2416): MQRC_CFGR_ERROR # 2417 (0971) (RC2417): MQRC_MSG_NOT_ALLOWED_IN_GROUP # 2418 (0972) (RC2418): MQRC_FILTER_OPERATOR_ERROR # 2419 (0973) (RC2419): MQRC_NESTED_SELECTOR_ERROR # 2420 (0974) (RC2420): MQRC_EPH_ERROR # 2421 (0975) (RC2421): MQRC_RFH_FORMAT_ERROR # 2422 (0976) (RC2422): MQRC_CFBF_ERROR # 2423 (0977) (RC2423): MQRC_CLIENT_CHANNEL_CONFLICT # 2424 (0978) (RC2424): MQRC_SD_ERROR # 2425 (0979) (RC2425): MQRC_TOPIC_STRING_ERROR # 2426 (097A) (RC2426): MQRC_STS_ERROR # 2428 (097C) (RC2428): MQRC_NO_SUBSCRIPTION # 2429 (097D) (RC2429): MQRC_SUBSCRIPTION_IN_USE # 2430 (097E) (RC2430): MQRC_STAT_TYPE_ERROR # 2431 (097F) (RC2431): MQRC_SUB_USER_DATA_ERROR # 2432 (0980) (RC2432): MQRC_SUB_ALREADY_EXISTS # 2434 (0982) (RC2434): MQRC_IDENTITY_MISMATCH # 2435 (0983) (RC2435): MQRC_ALTER_SUB_ERROR # 2436 (0984) (RC2436): MQRC_DURABILITY_NOT_ALLOWED # 2437 (0985) (RC2437): MQRC_NO_RETAINED_MSG # 2438 (0986) (RC2438): MQRC_SRO_ERROR # 2440 (0988) (RC2440): MQRC_SUB_NAME_ERROR # 2441 (0989) (RC2441): MQRC_OBJECT_STRING_ERROR # 2442 (098A) (RC2442): MQRC_PROPERTY_NAME_ERROR # 2443 (098B) (RC2443): MQRC_SEGMENTATION_NOT_ALLOWED # 2444 (098C) (RC2444): MQRC_CBD_ERROR # 2445 (098D) (RC2445): MQRC_CTLO_ERROR # 2446 (098E) (RC2446): MQRC_NO_CALLBACKS_ACTIVE # 2448 (0990) (RC2448): MQRC_CALLBACK_NOT_REGISTERED # 2452 (0994) (RC2452): MQRC_CALLBACK_ERROR # 2453 (0995) (RC2453): MQRC_CALLBACK_STILL_ACTIVE # 2457 (0999) (RC2457): MQRC_OPTIONS_CHANGED # 2458 (099A) (RC2458): MQRC_READ_AHEAD_MSGS # 2459 (099B) (RC2459): MQRC_SELECTOR_SYNTAX_ERROR # 2460 (099C) (RC2460): MQRC_HMSG_ERROR # 2461 (099D) (RC2461): MQRC_CMHO_ERROR # 2462 (099E) (RC2462): MQRC_DMHO_ERROR # 2463 (099F) (RC2463): MQRC_SMPO_ERROR # 2464 (09A0) (RC2464): MQRC_IMPO_ERROR # 2465 (09A1) (RC2465): MQRC_PROPERTY_NAME_TOO_BIG # 2466 (09A2) (RC2466): MQRC_PROP_VALUE_NOT_CONVERTED # 2467 (09A3) (RC2467): MQRC_PROP_TYPE_NOT_SUPPORTED # 2469 (09A5) (RC2469): MQRC_PROPERTY_VALUE_TOO_BIG # 2470 (09A6) (RC2470): MQRC_PROP_CONV_NOT_SUPPORTED # 2471 (09A7) (RC2471): MQRC_PROPERTY_NOT_AVAILABLE # 2472 (09A8) (RC2472): MQRC_PROP_NUMBER_FORMAT_ERROR # 2473 (09A9) (RC2473): MQRC_PROPERTY_TYPE_ERROR # 2478 (09AE) (RC2478): MQRC_PROPERTIES_TOO_BIG # 2479 (09AF) (RC2479): MQRC_PUT_NOT_RETAINED # 2480 (09B0) (RC2480): MQRC_ALIAS_TARGTYPE_CHANGED # 2481 (09B1) (RC2481): MQRC_DMPO_ERROR # 2482 (09B2) (RC2482): MQRC_PD_ERROR # 2483 (09B3) (RC2483): MQRC_CALLBACK_TYPE_ERROR # 2484 (09B4) (RC2484): MQRC_CBD_OPTIONS_ERROR # 2485 (09B5) (RC2485): MQRC_MAX_MSG_LENGTH_ERROR # 2486 (09B6) (RC2486): MQRC_CALLBACK_ROUTINE_ERROR # 2487 (09B7) (RC2487): MQRC_CALLBACK_LINK_ERROR # 2488 (09B8) (RC2488): MQRC_OPERATION_ERROR # 2489 (09B9) (RC2489): MQRC_BMHO_ERROR # 2490 (09BA) (RC2490): MQRC_UNSUPPORTED_PROPERTY # 2492 (09BC) (RC2492): MQRC_PROP_NAME_NOT_CONVERTED # 2494 (09BE) (RC2494): MQRC_GET_ENABLED # 2495 (09BF) (RC2495): MQRC_MODULE_NOT_FOUND # 2496 (09C0) (RC2496): MQRC_MODULE_INVALID # 2497 (09C1) (RC2497): MQRC_MODULE_ENTRY_NOT_FOUND # 2498 (09C2) (RC2498): MQRC_MIXED_CONTENT_NOT_ALLOWED # 2499 (09C3) (RC2499): MQRC_MSG_HANDLE_IN_USE # 2500 (09C4) (RC2500): MQRC_HCONN_ASYNC_ACTIVE # 2501 (09C5) (RC2501): MQRC_MHBO_ERROR # 2502 (09C6) (RC2502): MQRC_PUBLICATION_FAILURE # 2503 (09C7) (RC2503): MQRC_SUB_INHIBITED # 2504 (09C8) (RC2504): MQRC_SELECTOR_ALWAYS_FALSE # 2507 (09CB) (RC2507): MQRC_XEPO_ERROR # 2509 (09CD) (RC2509): MQRC_DURABILITY_NOT_ALTERABLE # 2510 (09CE) (RC2510): MQRC_TOPIC_NOT_ALTERABLE # 2512 (09D0) (RC2512): MQRC_SUBLEVEL_NOT_ALTERABLE # 2513 (09D1) (RC2513): MQRC_PROPERTY_NAME_LENGTH_ERR # 2514 (09D2) (RC2514): MQRC_DUPLICATE_GROUP_SUB # 2515 (09D3) (RC2515): MQRC_GROUPING_NOT_ALTERABLE # 2516 (09D4) (RC2516): MQRC_SELECTOR_INVALID_FOR_TYPE # 2517 (09D5) (RC2517): MQRC_HOBJ_QUIESCED # 2518 (09D6) (RC2518): MQRC_HOBJ_QUIESCED_NO_MSGS # 2519 (09D7) (RC2519): MQRC_SELECTION_STRING_ERROR # 2520 (09D8) (RC2520): MQRC_RES_OBJECT_STRING_ERROR # 2521 (09D9) (RC2521): MQRC_CONNECTION_SUSPENDED # 2522 (09DA) (RC2522): MQRC_INVALID_DESTINATION # 2523 (09DB) (RC2523): MQRC_INVALID_SUBSCRIPTION # 2524 (09DC) (RC2524): MQRC_SELECTOR_NOT_ALTERABLE # 2525 (09DD) (RC2525): MQRC_RETAINED_MSG_Q_ERROR # 2526 (09DE) (RC2526): MQRC_RETAINED_NOT_DELIVERED # 2527 (09DF) (RC2527): MQRC_RFH_RESTRICTED_FORMAT_ERR # 2528 (09E0) (RC2528): MQRC_CONNECTION_STOPPED # 2529 (09E1) (RC2529): MQRC_ASYNC_UOW_CONFLICT # 2530 (09E2) (RC2530): MQRC_ASYNC_XA_CONFLICT # 2531 (09E3) (RC2531): MQRC_PUBSUB_INHIBITED # 2532 (09E4): MQRC_MSG_HANDLE_COPY_FAILURE # 2533 (09E5) (RC2533): MQRC_DEST_CLASS_NOT_ALTERABLE # 2534 (09E6) (RC2534): MQRC_OPERATION_NOT_ALLOWED # 2535 (09E7): MQRC_ACTION_ERROR # 2537 (09E9) (RC2537): MQRC_CHANNEL_NOT_AVAILABLE # 2538 (09EA) (RC2538): MQRC_HOST_NOT_AVAILABLE # 2539 (09EB) (RC2539): MQRC_CHANNEL_CONFIG_ERROR # 2540 (09EC) (RC2540): MQRC_UNKNOWN_CHANNEL_NAME # 2541 (09ED) (RC2541): MQRC_LOOPING_PUBLICATION # 6100 (17D4) (RC6100): MQRC_REOPEN_EXCL_INPUT_ERROR # 6101 (17D5) (RC6101): MQRC_REOPEN_INQUIRE_ERROR # 6102 (17D6) (RC6102): MQRC_REOPEN_SAVED_CONTEXT_ERR # 6103 (17D7) (RC6103): MQRC_REOPEN_TEMPORARY_Q_ERROR # 6104 (17D8) (RC6104): MQRC_ATTRIBUTE_LOCKED # 6105 (17D9) (RC6105): MQRC_CURSOR_NOT_VALID # 6106 (17DA) (RC6106): MQRC_ENCODING_ERROR # 6107 (17DB) (RC6107): MQRC_STRUC_ID_ERROR # 6108 (17DC) (RC6108): MQRC_NULL_POINTER # 6109 (17DD) (RC6109): MQRC_NO_CONNECTION_REFERENCE # 6110 (17DE) (RC6110): MQRC_NO_BUFFER # 6111 (17DF) (RC6111): MQRC_BINARY_DATA_LENGTH_ERROR # 6112 (17E0) (RC6112): MQRC_BUFFER_NOT_AUTOMATIC # 6113 (17E1) (RC6113): MQRC_INSUFFICIENT_BUFFER # 6114 (17E2) (RC6114): MQRC_INSUFFICIENT_DATA # 6115 (17E3) (RC6115): MQRC_DATA_TRUNCATED # 6116 (17E4) (RC6116): MQRC_ZERO_LENGTH # 6117 (17E5) (RC6117): MQRC_NEGATIVE_LENGTH # 6118 (17E6) (RC6118): MQRC_NEGATIVE_OFFSET # 6119 (17E7) (RC6119): MQRC_INCONSISTENT_FORMAT # 6120 (17E8) (RC6120): MQRC_INCONSISTENT_OBJECT_STATE # 6121 (17E9) (RC6121): MQRC_CONTEXT_OBJECT_NOT_VALID # 6122 (17EA) (RC6122): MQRC_CONTEXT_OPEN_ERROR # 6123 (17EB) (RC6123): MQRC_STRUC_LENGTH_ERROR # 6124 (17EC) (RC6124): MQRC_NOT_CONNECTED # 6125 (17ED) (RC6125): MQRC_NOT_OPEN # 6126 (17EE) (RC6126): MQRC_DISTRIBUTION_LIST_EMPTY # 6127 (17EF) (RC6127): MQRC_INCONSISTENT_OPEN_OPTIONS # 6128 (17FO) (RC6128): MQRC_WRONG_VERSION # 6129 (17F1) (RC6129): MQRC_REFERENCE_ERROR Processes: ========== MQ Processes: List 1: ===================== MQSERIES PROCESSES BY PLATFORM PLATFORM =AIX ProcName Process Function amqhasmx logger amqharmx log formatter,used only if the queue manager has linear logging selected amqzllp0 checkpoint processor amqzlaa0 queue manager agent(s) amqzxma0 processing controller runmqsc MQ Command interface amqpcsea PCF command processor amqcrsta Any remotely started channel over TCP/IP - Could be RECEIVER,REQUESTER,CLUSRCVR,SVRCONN,SENDER,SERVER amqcrs6a Any remotely started channel over LU62/SNA - Could be RECEIVER,REQUESTER,CLUSRCVR,SVRCONN,SENDER,SERVER runmqchl Any locally started channel over any protocol - Could be SENDER,SERVER,CLUSSDR,REQUESTER runmqlsr listener process runmqchi channel initiator PLATFORM = AS/400 ProcName Process Function AMQHIXK4 Storage Manager (Housekeeper) AMQMCPRA Data Store (Object Cache) AMQCLMAA Listener AMQALMP4 Check Point Process AMQRMCLA Sender channel AMQPCSVA PCF command processor AMQRIMNA Channel initiator (trigger monitor to start channel) AMQIQES4 Quiesce (forces user logoffs - for upgrades) AMQIQEJ4 Quiesce (without user logoffs - for daily use if desired) AMQCRSTA Any remotely started channel over TCP/IP - Could be RECEIVER,REQUESTER,CLUSRCVR,SVRCONN,SENDER,SERVER AMQCRS6A Any remotely started channel over LU62/SNA - Could be RECEIVER,REQUESTER,CLUSRCVR,SVRCONN,SENDER,SERVER PLATFORM = HP/UX ProcName Process Function amqhasmx logger amqharmx log formatter, used only if the queue manager has linear logging selected amqzllp0 checkpoint processor amqzlaa0 queue manager agents amqzxma0 processing controller runmqsc MQ Command interface amqpcsea PCF command processor amqcrsta Any remotely started channel over TCP/IP - Could be RECEIVER,REQUESTER,CLUSRCVR,SVRCONN,SENDER,SERVER amqcrs6a Any remotely started channel over LU62/SNA - Could be RECEIVER,REQUESTER,CLUSRCVR,SVRCONN,SENDER,SERVER runmqchl Any locally started channel over any protocol - Could be SENDER,SERVER,CLUSSDR,REQUESTER runmqlsr listener process runmqchi channel initiator PLATFORM = OS2 ProcName Process Function AMQHASM2.EXE The logger AMQHARM2.EXE Log formatter (LINEAR logs only) AMQZLLP0.EXE Checkpoint process AMQZLAA0.EXE LQM agents AMQZXMA0.EXE Execution controller AMQXSSV2.EXE Shared memory servers RUNMQSC.EXE MQSeries Command processor AMQPCSEA.EXE PCF command processor AMQCRSTA.EXE Any remotely started channel over TCP/IP - Could be RECEIVER,REQUESTER,CLUSRCVR,SVRCONN,SENDER,SERVER AMQCRS6A.EXE Any remotely started channel over LU62/SNA - Could be RECEIVER,REQUESTER,CLUSRCVR,SVRCONN,SENDER,SERVER RUNMQCHL.EXE Any locally started channel over any protocol - Could be SENDER,SERVER,CLUSSDR,REQUESTER RUNMQLSR LISTENER PROCESS RUNMQCHI CHANNEL INITIATOR PLATFORM = SOLARIS ProcName Process Function amqhasmx logger amqharmx log formatter, used only if the queue manager has linear logging selected amqzllp0 checkpoint processor amqzlaa0 queue manager agents amqzxma0 processing controller amqcrsta Any remotely started channel over TCP/IP - Could be RECEIVER,REQUESTER,CLUSRCVR,SVRCONN,SENDER,SERVER amqcrs6a Any remotely started channel over LU62/SNA - Could be RECEIVER,REQUESTER,CLUSRCVR,SVRCONN,SENDER,SERVER runmqchl Any locally started channel over any protocol - Could be SENDER,SERVER,CLUSSDR,REQUESTER runmqlsr listener process runmqchi channel initiator runmqsc MQ Command interface amqpcsea PCF command processor Windows/NT ProcName Process Function AMQHASMN.EXE The logger AMQHARMN.EXE Log formatter (LINEAR logs only) AMQZLLP0.EXE Checkpoint process AMQZLAA0.EXE LQM agents AMQZTRCN.EXE Trace AMQZXMA0.EXE Execution controller AMQXSSVN.EXE Shared memory servers AMQCRSTA.EXE Any remotely started channel over TCP/IP - Could be RECEIVER,REQUESTER,CLUSRCVR,SVRCONN,SENDER,SERVER AMQCRS6A.EXE Any remotely started channel over LU62/SNA - Could be RECEIVER,REQUESTER,CLUSRCVR,SVRCONN,SENDER,SERVER RUNMQCHL.EXE Any locally started channel over any protocol - Could be SENDER,SERVER,CLUSSDR,REQUESTER RUNMQLSR LISTENER PROCESS RUNMQCHI CHANNEL INITIATOR RUNMQSC.EXE MQSeries Command processor AMQPCSEA.EXE PCF command processor AMQSCM.EXE Service Control Manager Process Names Process Function amqpcsea Command server amqhasmx Logger amqharmx Log formatter (linear logs only) amqzllp0 Checkpoint processor amqzlaa0 Queue manager agents amqzfuma OAM process amqzxma0 Processing controller amqrrmfa Repository process (for clusters) amqzdmaa Deferred message processor OS/390 and z/OS are very simple: qmgrMSTR - the main address space (manager, API calls etc) qmgrCHIN - communications (listener, channels) qmgr = name of the queue manager MQ Processes: List 2: ===================== Windows/NT AMQHASMN.EXE - The logger AMQHARMN.EXE - Log formatter (LINEAR logs only) AMQZLLP0.EXE - Checkpoint process AMQZLAA0.EXE - LQM agents AMQZTRCN.EXE - Trace AMQZXMA0.EXE - Execution controller AMQXSSVN.EXE - Shared memory servers AMQCRSTA.EXE - Any remotely started channel over TCP/IP - Could be RECEIVER,REQUESTER,CLUSRCVR,SVRCONN,SENDER,SERVER AMQCRS6A.EXE - Any remotely started channel over LU62/SNA - Could be RECEIVER,REQUESTER,CLUSRCVR,SVRCONN,SENDER,SERVER RUNMQCHL.EXE - Any locally started channel over any protocol - Could be SENDER,SERVER,CLUSSDR,REQUESTER RUNMQLSR - LISTENER PROCESS RUNMQCHI - CHANNEL INITIATOR RUNMQSC.EXE - MQSeries Command processor AMQPCSEA.EXE - PCF command processor AMQSCM.EXE - Service Control Manager SOLARIS amqhasmx - logger amqharmx - log formatter, used only if the queue manager has linear logging selected amqzllp0 - checkpoint processor amqzlaa0 - queue manager agents amqzxma0 - processing controller amqcrsta - Any remotely started channel over TCP/IP - Could be RECEIVER,REQUESTER,CLUSRCVR,SVRCONN,SENDER,SERVER amqcrs6a - Any remotely started channel over LU62/SNA - Could be RECEIVER,REQUESTER,CLUSRCVR,SVRCONN,SENDER,SERVER runmqchl - Any locally started channel over any protocol - Could be SENDER,SERVER,CLUSSDR,REQUESTER runmqlsr - listener process runmqchi - channel initiator runmqsc - MQ Command interface amqpcsea - PCF command processor AS/400 AMQHIXK4 - Storage Manager (Housekeeper) AMQMCPRA - Data Store (Object Cache) AMQCLMAA - Listener AMQALMP4 - Check Point Process AMQRMCLA - Sender channel AMQCRSTA - Any remotely started channel over TCP/IP - Could be RECEIVER,REQUESTER,CLUSRCVR,SVRCONN,SENDER,SERVER AMQCRS6A - Any remotely started channel over LU62/SNA - Could be RECEIVER,REQUESTER,CLUSRCVR,SVRCONN,SENDER,SERVER AMQPCSVA - PCF command processor AMQRIMNA - Channel initiator (trigger monitor to start channel) AMQIQES4 - Quiesce (forces user logoffs - for upgrades) AMQIQEJ4 - Quiesce (without user logoffs - for daily use if desired) AIX amqhasmx - logger amqharmx - log formatter, used only if the queue manager has linear logging selected amqzllp0 - checkpoint processor amqzlaa0 - queue manager agent(s) amqzxma0 - processing controller amqcrsta - Any remotely started channel over TCP/IP - Could be RECEIVER,REQUESTER,CLUSRCVR,SVRCONN,SENDER,SERVER amqcrs6a - Any remotely started channel over LU62/SNA - Could be RECEIVER,REQUESTER,CLUSRCVR,SVRCONN,SENDER,SERVER runmqchl - Any locally started channel over any protocol - Could be SENDER,SERVER,CLUSSDR,REQUESTER runmqlsr - listener process runmqchi - channel initiator runmqsc - MQ Command interface amqpcsea - PCF command processor HP/UX amqhasmx - logger amqharmx - log formatter, used only if the queue manager has linear logging selected amqzllp0 - checkpoint processor amqzlaa0 - queue manager agents amqzxma0 - processing controller amqcrsta - Any remotely started channel over TCP/IP - Could be RECEIVER,REQUESTER,CLUSRCVR,SVRCONN,SENDER,SERVER amqcrs6a - Any remotely started channel over LU62/SNA - Could be RECEIVER,REQUESTER,CLUSRCVR,SVRCONN,SENDER,SERVER runmqchl - Any locally started channel over any protocol - Could be SENDER,SERVER,CLUSSDR,REQUESTER runmqlsr - listener process runmqchi - channel initiator runmqsc - MQ Command interface amqpcsea - PCF command processor OS2 AMQHASM2.EXE - The logger AMQHARM2.EXE - Log formatter (LINEAR logs only) AMQZLLP0.EXE - Checkpoint process AMQZLAA0.EXE - LQM agents AMQZXMA0.EXE - Execution controller AMQXSSV2.EXE - Shared memory servers AMQCRSTA.EXE - Any remotely started channel over TCP/IP - Could be RECEIVER,REQUESTER,CLUSRCVR,SVRCONN,SENDER,SERVER AMQCRS6A.EXE - Any remotely started channel over LU62/SNA - Could be RECEIVER,REQUESTER,CLUSRCVR,SVRCONN,SENDER,SERVER RUNMQCHL.EXE - Any locally started channel over any protocol - Could be SENDER,SERVER,CLUSSDR,REQUESTER RUNMQLSR - LISTENER PROCESS RUNMQCHI - CHANNEL INITIATOR RUNMQSC.EXE - MQSeries Command processor AMQPCSEA.EXE - PCF command processor MQSERIES PROCESSES BY PLATFORM PLATFORM =AIX ProcName Process Function amqhasmx logger amqharmx log formatter,used only if the queue manager has linear logging selected amqzllp0 checkpoint processor amqzlaa0 queue manager agent(s) amqzxma0 processing controller amqcrsta TCPIP Receiver channel & Client Connection amqcrs6a LU62 Receiver channel & Client Connection runmqchl Sender Channel runmqsc MQ Command interface amqpcsea PCF command processor PLATFORM = AS/400 ProcName Process Function AMQHIXK4 Storage Manager (Housekeeper) AMQMCPRA Data Store (Object Cache) AMQCLMAA Listener AMQALMP4 Check Point Process AMQRMCLA Sender channel AMQCRSTA TCP/IP Receiver channel & Client Connection AMQCRS6A LU62 Receiver channel & Client Connection AMQPCSVA PCF command processor AMQRIMNA Channel initiator (trigger monitor to start channel) AMQIQES4 Quiesce (forces user logoffs - for upgrades) AMQIQEJ4 Quiesce (without user logoffs - for daily use if desired) PLATFORM = HP/UX ProcName Process Function amqhasmx logger amqharmx log formatter, used only if the queue manager has linear logging selected amqzllp0 checkpoint processor amqzlaa0 queue manager agents amqzxma0 processing controller amqcrsta TCPIP Receiver channel & Client Connection amqcrs6a LU62 Receiver channel & Client Connection runmqchl Sender Channel runmqsc MQ Command interface amqpcsea PCF command processor PLATFORM = OS2 ProcName Process Function AMQHASM2.EXE The logger AMQHARM2.EXE Log formatter (LINEAR logs only) AMQZLLP0.EXE Checkpoint process AMQZLAA0.EXE LQM agents AMQZXMA0.EXE Execution controller AMQXSSV2.EXE Shared memory servers AMQCRSTA.EXE TCPIP Receiver channel & Client Connection AMQCRS6A.EXE LU62 Receiver channel & Client Connection RUNMQCHL.EXE Sender Channel RUNMQSC.EXE MQSeries Command processor AMQPCSEA.EXE PCF command processor PLATFORM = SOLARIS ProcName Process Function amqhasmx logger amqharmx log formatter, used only if the queue manager has linear logging selected amqzllp0 checkpoint processor amqzlaa0 queue manager agents amqzxma0 processing controller amqcrsta TCPIP Receiver channel & Client Connection Process Names Process Function amqpcsea Command server amqhasmx Logger amqharmx Log formatter (linear logs only) amqzllp0 Checkpoint processor amqzlaa0 Queue manager agents amqzfuma OAM process amqzxma0 Processing controller amqrrmfa Repository process (for clusters) amqzdmaa Deferred message processor MQ Processes: List 3: ===================== Description of WebSphere MQ tasks When a queue manager is running, you see some or all of the following batch jobs running under the QMQM user profile in the WebSphere MQ subsystem. The jobs are described briefly in Table 1, to help you decide how to prioritize them. Table 1. WebSphere MQ tasks. Job name Function AMQALMPX The checkpoint processor that periodically takes journal checkpoints AMQCLMAA Non-threaded TCP/IP listener AMQCRSTA TCP/IP-invoked channel responder AMQCRS6B LU62 receiver channel and client connection (see note). AMQFCXBA Broker worker job AMQPCSEA PCF command processor that handles PCF and remote administration requests AMQRMPPA Channel process pooling job AMQRRMFA Repository manager for clusters AMQZDMAA Deferred message handler AMQZFUMA Object authority manager (OAM) AMQZLAA0 Queue manager agents that perform the bulk of the work for applications that connect to the queue manager using MQCNO_STANDARD_BINDING AMQZLAS0 Queue manager agent AMQZXMA0 The execution controller that is the first job started by the queue manager. It deals with MQCONN requests, and starts agent processes to process WebSphere MQ API calls AMQZMGR0 Process controller. This job is used to start up and manage listeners and services. AMQZMUC0 Utility manager. This job executes critical queue manager utilities, for example the journal chain manager. AMQZMUR0 Utility manager. This job executes critical queue manager utilities, for example the journal chain manager. RUNMQBRK Broker control job RUNMQCHI The channel initiator RUNMQCHL Sender channel job that is started for each sender channel RUNMQDLQ Dead letter queue handler RUNMQLSR Threaded TCP/IP listener RUNMQTRM Trigger monitor Note: The LU62 receiver job runs in the communications subsystem and takes its run-time properties from the routing and communications entries that are used to start the job. See WebSphere MQ Intercommunication for more details. You can view all jobs connected to a queue manager, except listeners (which do not connect), using option 22 on the Work with Queue Manager (WRKMQM) panel. You can view listeners using the WRKMQMLSR command WebSphere(R) MQ Explorer messages: ================================== AMQ4000New object not created because the default object for the object type could not be found. Severity: 10 : Warning Explanation: The creation of an object requires a default template for each object type. The required default template for this object type could not be found. Response: Determine why the default object is not available, or create a new one. Then try the request again. AMQ4001The queue manager specified is already shown in the console. Severity: 0 : Information Response: Message for information only. AMQ4002Are you sure you want to delete the named ? Severity: 10 : Warning Explanation: A confirmation is required before the specified object is deleted. The type of object and name are provided in the message. Response: Continue only if you want to permanently delete the object. AMQ4003WebSphere MQ system objects are used internally by WebSphere MQ. You are advised not to delete them. Do you want to keep the WebSphere MQ system object? Severity: 0 : Information Explanation: A confirmation is required before an internal WebSphere MQ system object (for example SYSTEM.DEFAULT.LOCAL.QUEUE) is deleted. Response: Continue only if you want to permanently delete the system object. AMQ4004Clear all messages from the queue? Severity: 10 : Warning Explanation: The removal of the messages from the queue is an irreversible action. If the command is allowed to proceed the action cannot be undone. Response: Continue only if you want to permanently delete the messages. AMQ4005The object has been replaced or deleted. The properties could not be applied. Severity: 10 : Warning Explanation: During the process of updating the properties of the object, it was determined that the object has either been deleted or replaced by another instance. The properties have not been applied. AMQ4006WebSphere MQ successfully sent data to the remote queue manager and received the data returned. Severity: 0 : Information Explanation: An open channel has been successfully verified by WebSphere MQ as the result of a user request. Response: Message for information only. AMQ4007The message sequence number for the channel was reset. Severity: 0 : Information Explanation: A channel has had its sequence number successfully reset by WebSphere MQ as the result of a user request. Response: Message for information only. AMQ4008The request to start the channel was accepted. Severity: 0 : Information Explanation: A channel has been started successfully by WebSphere MQ as the result of a user request. Response: Message for information only. AMQ4009The request to stop the channel was accepted. Severity: 0 : Information Explanation: A channel has been stopped successfully by WebSphere MQ as the result of a user request. Response: Message for information only. AMQ4010The 'in-doubt' state was resolved. Severity: 0 : Information Explanation: A channel has had its 'in-doubt' state resolved successfully by WebSphere MQ as the result of a user request. Response: Message for information only AMQ4011The queue has been cleared of messages. Severity: 0 : Information Explanation: The CLEAR command completed successfully and has removed all messages from the target queue. If the CLEAR was performed using the MQGET API command, uncommitted messages might still be on the queue. AMQ4012The object was created successfully but it is not visible with the current settings for visible objects. Severity: 0 : Information Response: Message for information only. AMQ4014The character is not valid. Severity: 10 : Warning AMQ4015Supply a non-blank name. Severity: 0 : Information Response: Enter a valid name. AMQ4016The test message was put successfully. Severity: 0 : Information Explanation: The request to place a message on the target queue has completed successfully. The queue now contains the message. Response: Message for information only. AMQ4019An object called already exists. Do you want to replace the definition of the existing object? Severity: 0 : Information Response: Confirm that you want to replace the definition. AMQ4020The changes you are making to the attributes of page "" will affect the operation of the queue manager or another program currently using the object. Do you want to force the change to the object's attributes? Severity: 10 : Warning Explanation: You are trying to change a object that cannot be changed because the object is in use, or the change will affect other programs or queue managers. Some changes can be forced anyway. Response: Select Yes to try forcing the changes, or No to abandon the change. AMQ4021Failed to access one or more WebSphere MQ objects. Severity: 10 : Warning Explanation: The objects' icons have been marked to indicate the objects in error. AMQ4022The name specified for the initiation queue is the same as the name of the queue itself. Severity: 0 : Information Response: Specify a different name to that of the object being created or altered. AMQ4023The queue manager does not exist on this computer. Severity: 0 : Information Response: Message for information only. AMQ4024The object cannot be replaced. Severity: 0 : Information Explanation: The request to replace the object was unsuccessful. Response: To define this object, delete the existing object and try the operation again. AMQ4025The changes made to the cluster attributes of the queue will take effect once they have propagated across the network. Severity: 0 : Information Response: Refresh any views containing the cluster queues in the affected clusters to show the changes. AMQ4026You have created a queue which is shared in one or more clusters. The queue will be available as a cluster queue once its definition has propagated across the network. Severity: 0 : Information Response: Refresh any views containing the cluster queues in the affected clusters to show the cluster queue. AMQ4027An error occurred connecting to the queue manager. Are you sure you want to show this queue manager in the folder anyway? Severity: 10 : Warning Explanation: A connection could not be made to the specified remote queue manager. Response: Ensure that the named queue manager is running on the host and port specified, and has a channel corresponding to the specified name. Ensure that you have the authority to connect to the remote queue manager, and ensure that the network is running. Select Yes if you believe that the problem can be resolved later. Select No if you want to correct the problem now and try again. AMQ4028Platform not supported. This queue manager cannot be administered by the WebSphere MQ Explorer because it is running on an unsupported platform. The value for the Platform attribute of the queue manager is not supported by the WebSphere MQ Explorer. Severity: 20 : Error AMQ4029Command level too low. This queue manager cannot be administered by the WebSphere MQ Explorer because the command level of the queue manager is less than . Severity: 20 : Error Response: If you want to administer this queue manager, you must upgrade it to a newer version of WebSphere MQ. AMQ4030Queue manager cannot be administered because codepage conversion table not found. Severity: 20 : Error Explanation: This queue manager cannot be administered by the WebSphere MQ Explorer because a codepage conversion table was not found. Response: Install a codepage conversion table from CCSID to CCSID on the computer on which the WebSphere MQ Explorer is running. AMQ4031Queue manager cannot be administered because CCSID not found. Severity: 20 : Error Explanation: This queue manager cannot be administered by the WebSphere MQ Explorer because CCSID cannot be found in the CCSID table. The WebSphere MQ Explorer cannot convert character data to or from the unrecognized CCSID. AMQ4032Command server not responding within timeout period. Severity: 10 : Warning Response: Ensure that the command server is running and that the queue called 'SYSTEM.ADMIN.COMMAND.QUEUE' is configured to enable programs to get messages from it. AMQ4033Cannot get messages from the queue. Severity: 0 : Information Explanation: A reason code returned when the object was opened for input indicated that the queue is disabled for MQGET request. Response: To get messages from this queue, enable it for GET requests. AMQ4034Message too long. You tried to put a message on a queue that was bigger than the maximum allowed for the queue or queue manager. Severity: 10 : Warning Explanation: The request to put a message on a queue returned a reason code indicating that the data length of the message exceeds the maximum allowed in the definition of the queue. Response: Either change the MAXMSGL attribute of the queue so that it is equal to or greater than the length of the message, or reduce the length of the message being put on the queue. AMQ4035No message available. The response message did not arrive within a reasonable amount of time. Severity: 0 : Information Explanation: The request to get a message from a queue returned a reason code indicating that there are currently no messages on the queue that meet the selection criteria specified on the GET request. AMQ4036Access not permitted. You are not authorized to perform this operation. Severity: 10 : Warning Explanation: The queue manager's security mechanism has indicated that the userid associated with this request is not authorized to access the object. AMQ4037Object definition changed since it was opened. Severity: 0 : Information Explanation: Object definitions that affect this object have been changed since the Hobj handle used on this call was returned by the MQOPEN call. Response: Issue an MQCLOSE call to return the handle to the system. It is then usually sufficient to reopen the object and try the operation again. AMQ4038Object damaged. Severity: 10 : Warning Explanation: The object is damaged and cannot be accessed. Response: The object should be deleted. Alternatively, it might be possible to recover it from a media image or backup. AMQ4039Object in use. The object is already opened by another application. Severity: 10 : Warning Explanation: An MQOPEN call was issued, but the object in question has already been opened by this or another application with options that conflict with those specified in the Options parameter. This arises if the request is for shared input, but the object is already open for exclusive input. It also arises if the request is for exclusive input, but the object is already open for input (of any sort). Response: To change the attributes of an object, specify the Force option as 'Yes' to apply the changes. If you do this, any applications using the object must close and reopen the object to proceed. AMQ4040Cannot put messages on this queue. Severity: 0 : Information Explanation: MQPUT and MQPUT1 calls are currently inhibited for the queue, or for the queue to which this queue resolves. AMQ4042Queue full. The queue contains the maximum number of messages. Severity: 10 : Warning Explanation: On an MQPUT or MQPUT1 call, the call failed because the queue is full; that is, it already contains the maximum number of messages possible. AMQ4043Queue manager not available for connection. Severity: 10 : Warning Response: Ensure that the queue manager is running. If the queue manager is running on another computer, ensure it is configured to accept remote connections. AMQ4044Queue manager stopping. Severity: 0 : Information Explanation: An MQI call was issued, but the call failed because the queue manager is shutting down. If the call was an MQGET call with the MQGMO_WAIT option, the wait has been canceled. Response: You cannot issue any more MQI calls. AMQ4045Queue not empty. The queue contains one or more messages or uncommitted PUT or GET requests. Severity: 0 : Information Explanation: An operation that requires the queue to be empty has failed because the queue either contains messages or has uncommitted PUT or GET requests outstanding. AMQ4046Insufficient system resources available. Severity: 20 : Error AMQ4047Insufficient storage available. Severity: 20 : Error AMQ4048The request received an unexpected reason code from an underlying API or command request. The reason code was Severity: 20 : Error Explanation: While executing the requested operation, an unexpected return code was received. This has resulted in the operation not completing as expected. Response: Use the appropriate documentation to determine why the reason code was returned. AMQ4049Unknown object name. Severity: 10 : Warning Explanation: A command or API request was issued, but the object cannot be found. AMQ4050Allocation failed. An attempt to allocate a conversation to a remote system failed. Severity: 10 : Warning Explanation: The error might be due to an incorrect entry in the channel definition or it might be that the listening program on the remote system was not running. AMQ4051Bind failed. The bind to a remote system during session negotiation failed. Severity: 10 : Warning AMQ4052Coded character-set ID error. Cannot convert a command message to the CCSID of the target queue manager. Severity: 10 : Warning AMQ4053Channel in doubt. Operation not completed. Severity: 10 : Warning Explanation: The operation could not complete because the channel was in doubt. AMQ4054Channel in use. Severity: 10 : Warning Explanation: An attempt was made to perform an operation on a channel, but the channel is currently active. AMQ4055Channel status not found. Severity: 10 : Warning Explanation: No channel status is available for this channel. This might indicate that the channel has not been used. AMQ4056Command failed. Severity: 10 : Warning AMQ4057Configuration error in the channel definition or communication subsystem. Severity: 10 : Warning Explanation: Allocation of a conversation is not possible. AMQ4058Connection closed. Severity: 10 : Warning Explanation: The connection to a remote system has unexpectedly broken while receiving data. AMQ4059Could not establish a connection to the queue manager. Severity: 10 : Warning Explanation: The attempt to connect to the queue manager failed. This could be because the queue manager is incorrectly configured to allow a connection from this system, or the connection has been broken. Response: Try the operation again. If the error persists, examine the problem determination information to see if any information has been recorded. AMQ4060Dynamic queue scope error. Severity: 10 : Warning Explanation: The Scope attribute of the queue was set to MQSCO_CELL but this is not allowed for a dynamic queue. AMQ4061Remote system not available. Could not allocate a conversation to a remote system. Severity: 10 : Warning Response: The error might be transitory; try again later. AMQ4062An MQINQ call failed when the queue manager inquired about a WebSphere MQ object. Severity: 10 : Warning Response: Check the queue manager's error log for more information about the error. AMQ4063An MQOPEN call failed when the queue manager tried to open a WebSphere MQ object. Severity: 10 : Warning Response: Check the queue manager's error log for more information about the error. AMQ4064An MQSET call failed when the queue manager tried to set the values of the attributes of a WebSphere MQ object. Severity: 10 : Warning Response: Check the queue manager's error log for more information about the error. AMQ4065Message sequence number error. Severity: 10 : Warning Explanation: The message sequence number parameter was not valid. AMQ4066Message truncated because it is larger than the command server's maximum valid message size. Severity: 10 : Warning AMQ4067Communications manager not available. Severity: 20 : Error Explanation: The communications subsystem is not available. AMQ4068Queue is not a transmission queue. Severity: 10 : Warning Explanation: The queue specified in the channel definition was not a transmission queue. AMQ4069Object already exists. Severity: 10 : Warning Explanation: Could not create object because the object already existed. AMQ4070Object is open. Severity: 10 : Warning Explanation: An attempt was made to delete, change or clear an object that is in use. Response: Wait until the object is not in use, then try again. AMQ4071Object has wrong type. Could not replace a queue object of a different type. Severity: 10 : Warning AMQ4072Queue already exists in cell. Severity: 10 : Warning Explanation: Cannot define a queue with cell scope or change the scope of an existing queue from queue-manager scope to cell scope, because a queue with that name already exists in the cell. AMQ4073Ping error. You can only ping a sender or server channel. If the local channel is a receiver channel, ping from the remote queue manager. Severity: 10 : Warning AMQ4074Receive failed, possibly due to a communications failure. Severity: 10 : Warning AMQ4075Error while receiving data from a remote system, possibly due to a communications failure. Severity: 10 : Warning AMQ4076Remote queue manager terminating. Severity: 10 : Warning Explanation: The channel stopped because the remote queue manager was terminating. AMQ4077Remote queue manager not available. Severity: 10 : Warning Explanation: The channel could not be started because the remote queue manager was not available. Response: Ensure that the remote queue manager is started, and that it is configured to accept incoming communication requests. AMQ4078Send failed. An error occurred while sending data to a remote system, possibly due to a communications failure. Severity: 10 : Warning AMQ4079Channel closed by security exit. Severity: 10 : Warning AMQ4080Remote channel not known. Severity: 10 : Warning Explanation: There is no definition of this channel on the remote system. AMQ4081User exit not available. Severity: 10 : Warning Explanation: The channel was closed because the user exit specified does not exist. AMQ4082Unexpected WebSphere MQ error (). Severity: 20 : Error AMQ4083Queue manager name not known. Severity: 10 : Warning Explanation: If the queue manager is remote, this might indicate that another queue manager is incorrectly using the same connection name. Queue managers using TCP/IP on the same computer must listen on different port numbers. This means that they will also have different connection names. AMQ4084Cell directory is not available. Severity: 10 : Warning Explanation: The Scope attribute of the queue was set to MQSCO_CELL but no name service supporting a cell directory has been configured. Response: Configure a name service to support the cell directory. AMQ4085No name supplied for transmission queue. Severity: 10 : Warning Response: Supply a non-blank transmission queue name for this channel type. AMQ4086No connection name supplied. Severity: 10 : Warning Response: Supply a non-blank connection name for this channel type. AMQ4087An error occurred while trying to use a cluster resource. Severity: 10 : Warning Response: Check that the queues whose names start with 'SYSTEM.CLUSTER.' are not full and that messages are allowed to be put on them. AMQ4088Cannot share transmission queue in cluster. Severity: 10 : Warning Explanation: The queue is a transmission queue and cannot be shared in a cluster. AMQ4089PUT commands inhibited for system command queue called 'SYSTEM.ADMIN.COMMAND.QUEUE'. Severity: 10 : Warning AMQ4090Are you sure you want to inhibit PUT and GET commands for the queue called 'SYSTEM.ADMIN.COMMAND.QUEUE'? If you do, you will no longer be able to administer the queue manager using the WebSphere MQ Explorer. Severity: 10 : Warning Explanation: WebSphere MQ Explorer uses the queue called 'SYSTEM.ADMIN.COMMAND.QUEUE' to administer the queue manager. Response: Continue only if you really want to inhibit PUT or GET commands for this queue and stop using the WebSphere MQ Explorer to administer the queue manager. AMQ4091Cannot connect to remote queue manager. Severity: 10 : Warning Explanation: The remote queue manager is using an unsupported protocol for connections. The WebSphere MQ Explorer only supports connections to remote queue managers using the TCP/IP protocol. AMQ4092The queue manager could not be removed from the cluster because its membership of the cluster is defined using namelist . Severity: 10 : Warning Response: To remove the queue manager from the cluster, remove it from the namelist. Ensure that you do not inadvertently affect the definitions of other objects using the namelist. AMQ4093The cluster specified is already shown in the console. Severity: 0 : Information AMQ4094An error occurred adding this cluster to the console. Are you sure you want to show this cluster in the console anyway? Severity: 10 : Warning Response: Select Yes if you believe that the problem can be resolved later. Select No if you want to correct the problem now and try again. AMQ4095Queue manager is not a repository queue manager for cluster . Severity: 0 : Information Explanation: To administer a cluster, the WebSphere MQ Explorer needs a connection to the repository queue manager. AMQ4096Are you sure you want to clear the password for this channel? Severity: 0 : Information Response: Check with the user before clearing the password from the channel. Continue only if you really want to clear the password. AMQ4097Unmatched quotation mark. Severity: 10 : Warning Explanation: An unmatched quotation mark has been found in a list of attributes. Each value in the list can be enclosed in a pair of single or double quotation marks. (Only required for values which contain spaces, commas or quotation marks.) Response: Check that all opening and closing quotation marks are in pairs. (To include a quotation mark within an attribute, use two together with no space between.) AMQ4098Incorrect list format. Severity: 10 : Warning Explanation: The attribute can contain a list of values which must be separated by a space or a comma. Each value in the list can be enclosed in a pair of single or double quotation marks. (Only required for values which contain spaces, commas or quotation marks.) Response: Check that values are separated by a space or a comma, and that all opening and closing quotation marks are in pairs. (To include a quotation mark within an attribute, use two together with no space between.) AMQ4099Cannot communicate with one or more repository queue managers. Cluster is configured to use one or more repository queue managers which communicate using a protocol other than TCP/IP. Severity: 10 : Warning Explanation: The WebSphere MQ Explorer can only establish connections to remote queue managers using TCP/IP. Response: To complete removal of the queue manager from the cluster, issue the RESET CLUSTER ACTION(FORCEREMOVE) command from the repository queue manager. AMQ4103An error occurred connecting to the queue manager. Are you sure you want to show this queue manager in the folder? Severity: 10 : Warning Explanation: A connection could not be made to the specified remote queue manager. Response: Ensure that the named queue manager is running on the machine specified in the selected channel definition table. Ensure that you have the authority to connect to the remote queue manager, and ensure that the network is up and running. Select Yes if you believe that the problem can be resolved later. Select No if you want to correct the problem now and try again. AMQ4104The specified file does not contain a client definition table in the correct format. Severity: 10 : Warning Explanation: The given channel definition table is not in the correct format. Response: Specify a file in the correct format. AMQ4105The remote queue manager has not been removed because it is still required by other plug-ins. Severity: 10 : Warning Explanation: Other plug-ins have responded to the attempted removal of this queue manager by indicating that they are still using it. Response: Ensure that the other plug-ins have finished using the queue manager before trying to delete it again. AMQ4117This action cannot be undone. Are you sure you want to delete the WebSphere MQ queue manager from your system? Severity: 10 : Warning Explanation: A confirmation is required before the queue manager is deleted. Response: Continue only if you want to permanently delete the queue manager. AMQ4121The MQGET request received an unexpected reason code of . Severity: 10 : Warning Explanation: An unexpected reason code was returned from a MQGET API request. Use the reason code to determine the underlying reason why the request failed. Response: The MQGET request was not successful. Some messages might not have been retrieved. AMQ4122The MQPUT request received an unexpected reason code of . Severity: 10 : Warning Explanation: An unexpected reason code was returned from a MQPUT API request. Use the reason code to determine the underlying reason why the request failed. Response: MQPUT processing was unsuccessful. No message was placed on the queue. AMQ4123The was deleted successfully. Severity: 0 : Information Explanation: The object of the specified type and name has been successfully deleted. Response: none. AMQ4124The MQOPEN request received an unexpected reason code of . Severity: 10 : Warning Explanation: An unexpected reason code was returned from an MQOPEN API request. The queue has not been opened. Response: Use the reason code to determine the underlying reason for the failure. AMQ4125Putting a test message on the queue received an unexpected reason code . Severity: 10 : Warning Explanation: One of the underlying API requests was unsuccessful. The test message was not placed on the queue. AMQ4126The value of one of the properties specified is not valid. The request was not processed. Severity: 20 : Error Response: Specify a different value. AMQ4127WebSphere MQ failed to read queue manager information from disk because the file format is not valid. The request was not processed. Severity: 20 : Error Explanation: The format of the WebSphere MQ_Handles file is incorrect. This file has been backed up and removed, meaning that any remote queue manager definitions are lost. All local queue managers should be detected automatically and displayed in the WebSphere MQ Explorer. Response: Ensure that the Eclipse workspace has not been corrupted. AMQ4128Could not start the iKeyMan program. Severity: 30 : Severe error Explanation: An error was encountered when trying to execute the iKeyMan program. Response: Try again, and if symptoms persist contact the System Administrator. AMQ4129Could not query the user ID from Java. Severity: 10 : Warning Explanation: The Java API System.getProperty("user.id") threw a SecurityException. Response: Configure your Java security environment using the 'policytool' to allow WebSphere MQ Explorer to query the 'user.id'. AMQ4130A Browser Control could not be opened. Make sure Mozilla has been installed. Severity: 10 : Warning Explanation: The SWT Browser control depends on Mozilla being installed. Response: Ensure that the Mozilla browser is correctly installed. AMQ4131A Browser Control could not be opened. Severity: 10 : Warning Explanation: The SWT Browser control depends on the system browser being installed. Response: Ensure that the system browser is correctly installed. AMQ4132Are you sure you want to stop the named ""? Severity: 10 : Warning Explanation: A confirmation is required before the specified object is stopped. The type of object and name are provided in the message. Response: Continue only if you want to stop the object. AMQ4133When a queue manager is removed, WebSphere MQ Explorer destroys the connection information for that queue manager. To see the queue manager at a later date use the Add Queue Manager wizard. Remove the queue manager ? Severity: 10 : Warning Response: Continue only if you want to remove the queue manager. AMQ4134The default channel used by remote queue managers to administer this queue manager does not exist. Do you want to create the default remote administration channel SYSTEM.ADMIN.SVRCONN to allow this queue manager to be administered by other queue managers? Severity: 0 : Information Response: Select Yes to create the channel. AMQ4135The default channel used by remote queue managers to administer this queue manager is SYSTEM.ADMIN.SVRCONN. Do you want to delete this channel to prevent the queue manager being administered by other queue managers? Severity: 0 : Information Response: Select Yes to delete the channel. AMQ4136Are you sure you want to clear all FFSTs and Trace from this machine? This operation cannot be undone. Severity: 10 : Warning Explanation: Deleting all FFSTs and Trace from this machine means that any historical error logs and trace will be lost. Response: Select Yes to clear FFSTs and Trace AMQ4137The default remote administration channel SYSTEM.ADMIN.SVRCONN has been deleted successfully. Severity: 0 : Information Response: Message for information only. AMQ4138Are you sure you want to import new settings that will overwrite the current settings? This operation cannot be undone. Severity: 10 : Warning Explanation: Importing settings into the WebSphere MQ Explorer will overwrite the current settings. Response: Continue only if you want to overwrite the current settings. AMQ4139The default remote administration channel SYSTEM.ADMIN.SVRCONN was created successfully. Severity: 0 : Information Response: Message for information only. AMQ4140The custom CipherSpec is not valid. Severity: 10 : Warning AMQ4141The Distinguished Names specification is not valid. Severity: 10 : Warning AMQ4142The default remote administration channel SYSTEM.ADMIN.SVRCONN could not be created. Severity: 10 : Warning Explanation: A problem has occurred when issuing a command to the command server to create the channel. Response: Try again, and if symptoms persist contact the Systems Administrator. AMQ4143The default remote administration channel SYSTEM.ADMIN.SVRCONN could not be created. Severity: 10 : Warning Explanation: A problem has occurred with the underlying data model, and the channel could not be created. Response: Try again, and if symptoms persist contact the Systems Administrator. AMQ4144The default remote administration channel SYSTEM.ADMIN.SVRCONN could not be deleted. Severity: 10 : Warning Explanation: A problem has occurred issuing a command to the command server to delete the channel. Response: Ensure that the channel is not in use and try again. If symptoms persist, contact the Systems Administrator. AMQ4145An error occurred connecting to the remote queue manager using the intermediate queue manager. Are you sure you want to show this queue manager in the folder anyway? Severity: 10 : Warning Explanation: A connection could not be made to the specified remote queue manager. Response: Ensure that the intermediate queue manager is available and that the named remote queue manager is running, and is accessible from the intermediate queue manager. Ensure that you have the authority to connect to the remote queue manager, and ensure that the network is up and running. Select Yes if you believe that the problem can be resolved later. Select No if you want to correct the problem now and try again. AMQ4146Eclipse cannot create or read the workspace for WebSphere MQ Explorer. Severity: 40 : Stop Error Explanation: To load the WebSphere MQ Explorer, a valid workspace is required. Response: Ensure that you can write to the Eclipse workspace. AMQ4147Eclipse cannot write to the workspace for WebSphere MQ Explorer in . Severity: 40 : Stop Error Explanation: To load the WebSphere MQ Explorer, write access to the workspace is required. Response: Ensure that you can write to the Eclipse workspace. AMQ4148The object was created successfully. Severity: 0 : Information Response: Message for information only. AMQ4149The request to start the listener was accepted. Severity: 0 : Information Explanation: A user request to start the listener was accepted by WebSphere MQ. Response: Message for information only. AMQ4150The request to stop the listener was accepted. Severity: 0 : Information Explanation: A user request to stop the listener was accepted by WebSphere MQ. Response: Message for information only. AMQ4151The request to start the service was accepted. Severity: 0 : Information Explanation: A user request to start the service was accepted by WebSphere MQ. Response: Message for information only. AMQ4152The request to stop the service was accepted. Severity: 0 : Information Explanation: A user request to stop the service was accepted by WebSphere MQ. Response: Message for information only. AMQ4153WebSphere MQ cannot stop the listener because it is not running. Severity: 10 : Warning AMQ4154WebSphere MQ cannot start the service because no start command has been specified. Severity: 10 : Warning Response: Ensure that the service has a start command specified. AMQ4155WebSphere MQ cannot stop the service because no stop command has been specified. Severity: 10 : Warning Response: Ensure that the service has a stop command specified. AMQ4156WebSphere MQ cannot stop the service because the service is not running. Severity: 10 : Warning AMQ4157WebSphere MQ cannot start the service because the services is already running. Severity: 10 : Warning AMQ4158WebSphere MQ cannot start the listener because it is already running. Severity: 10 : Warning AMQ4159WebSphere MQ cannot start the client connection channel because one or more of the properties are incorrectly specified. Severity: 10 : Warning Response: Ensure that the client connection has the correct queue manager name and connection name before trying to start. AMQ4160WebSphere MQ cannot process the request because the executable specified cannot be started. Severity: 10 : Warning Explanation: The requested was unsuccessful because the program which was defined to be run to complete the action could not be started. Reasons why the program could not be started are :- The program does not exist at the specified location. The WebSphere MQ user does not have sufficient access to execute the program. If StdOut or StdErr are defined for the program, the WebSphere MQ user does not have sufficient access to the locations specified. Response: Check the Queue Manager error logs for further details on the cause of the failure, correct the problem and try again. AMQ4161The parameter specified is not valid. Severity: 20 : Error Explanation: The parameter specified when trying to create or alter an object is not valid. Response: Ensure that valid parameters are specified, then try again. AMQ4162The password cannot be cleared. Severity: 0 : Information Response: Try to clear the password again later. AMQ4163The password cannot be changed. Severity: 10 : Warning Explanation: The attempt to change the password failed because of an error. Response: Try a different password AMQ4164The password was successfully changed. Severity: 0 : Information Response: Message for information only. AMQ4165No password entered in the new password field. No change applied. Severity: 10 : Warning Explanation: You must enter a new password in both the new and confirm password fields. Response: Enter a new password in the new password field. AMQ4166No password entered in the confirm new password field. No change applied. Severity: 10 : Warning Explanation: You must enter a new password in both the new and confirm password fields. Response: Re-enter the new password in the confirm new password field. AMQ4167Passwords do not match. No change applied. Severity: 10 : Warning Explanation: You must enter the same new password in both the new and confirm password fields. Response: Ensure that the passwords in the new and confirm fields match. AMQ4168WebSphere MQ failed to start listening for objects. Severity: 20 : Error Explanation: No objects will be displayed in the currently selected view. Response: Check the problem determination information, and ensure that WebSphere MQ and the queue manager in question are both running correctly. AMQ4169WebSphere MQ failed to set the object filter. Severity: 20 : Error Explanation: The WebSphere MQ Explorer cannot listen for objects, so no objects will be displayed in the currently selected view. Response: Check the problem determination information, and ensure that WebSphere MQ and the queue manager in question are both running correctly. AMQ4170The object name specified is not valid. Severity: 20 : Error Explanation: The object name specified when trying to create or alter an object is not valid. Response: Ensure that a valid object name is specified, then try again. AMQ4171There was an error when communicating with the queue manager. Severity: 20 : Error Explanation: A request for information from the queue manager failed. Response: Try the operation again. If the error persists, examine the problem determination information to see if any details have been recorded. AMQ4172There was an error when trying to set or retrieve information. Severity: 20 : Error Explanation: There was an error when trying to set or retrieve information from the queue manager. This might have happened because you specified incorrect or inconsistent attributes when trying create or update an object. Response: If this error occurred during object creation or modification, ensure that the attributes specified are correct for this type of object. If the error persists, examine the problem determination information to see if any details have been recorded. AMQ4173WebSphere MQ cannot clear one or more Trace and FFST files. Severity: 10 : Warning Explanation: WebSphere MQ cannot clear some files, possibly because these files are currently in use, or the WebSphere MQ Explorer does not have the appropriate access permission. Response: Check that tracing is disabled, and that the WebSphere MQ Explorer has appropriate access permission to delete the Trace and FFST files. AMQ4174FFSTs and Trace were cleared successfully. Severity: 0 : Information Response: Message for information only. AMQ4175WebSphere MQ cannot process your request because the value specified is not valid. Severity: 20 : Error Explanation: Only certain combinations and values are valid for the object your are trying to alter or create. Please check the values and try again. Response: Specify a valid value and try again. AMQ4176WebSphere MQ cannot process your request because the object name specified is not valid. Severity: 20 : Error Explanation: Only certain combinations and values are valid for the object your are trying to alter or create. You might also see this message if you have specified an invalid QSG disposition. Response: Check all values are valid for this type of object and try again. If you have altered the disposition of this object, check that the value is correct. AMQ4177The WebSphere MQ Explorer cannot process your request because the connection to WebSphere MQ is quiescing. Severity: 20 : Error Explanation: The connection to WebSphere MQ is quiescing, so no new information can be queried. Response: Wait for the connection to end, then try reconnecting. AMQ4178WebSphere MQ cannot process your request because there was a disposition conflict detected. Severity: 20 : Error Explanation: A disposition conflict was detected. Please ensure that all disposition related fields are correct for this type of object. Response: Ensure that all disposition related fields are correct for this type of object and try again. AMQ4179WebSphere MQ cannot process your request because the string provided was of an incorrect length. Severity: 20 : Error Explanation: A string value has been modified or supplied that is too long when creating or modifying an object. Response: Check the values being supplied and try again. AMQ4180WebSphere MQ cannot process your request because there was a parameter conflict. Severity: 20 : Error Explanation: When creating or modifying an object, the combination of parameters specified is not valid. Response: Check that the combination specified is valid for the object and try again. AMQ4181WebSphere MQ is not responding. Do you want to continue waiting? Severity: 10 : Warning Explanation: WebSphere MQ does not appear to be responding. This could be because of a heavily loaded remote system, or a slow network connection. However there could have been a system failure. Choosing not to continue could leave the WebSphere MQ Explorer in an unknown state, so you should restart it. Response: If you choose not to continue waiting, restart the WebSphere MQ Explorer, if the problem persists check for problem determination information. AMQ4182No objects were found. Severity: 10 : Warning Explanation: The query did not find any objects. Response: If you were expecting objects to be found, check the problem determination information, and ensure that WebSphere MQ and the queue manager in question are both running correctly. AMQ4183Query failed because the queue manager is not in a queue-sharing group. Severity: 10 : Warning Explanation: WebSphere MQ issued a query that required the queue manager to be a member of a queue-sharing group. Response: Try the operation again, if the problem persists check the problem determination information for more details. AMQ4184WebSphere MQ is unable to perform your request because the channel is not active. Severity: 20 : Error AMQ4185WebSphere MQ failed to import your settings. Severity: 20 : Error Response: Try again. If the error persists, examine the problem determination information to see if any details have been recorded. AMQ4186WebSphere MQ failed to export your settings. Severity: 20 : Error Response: Try again. If the error persists, examine the problem determination information to see if any details have been recorded. AMQ4187WebSphere MQ has succesfully imported your settings. (You must restart WebSphere MQ Explorer to apply the imported settings.) Severity: 0 : Information Response: Restart WebSphere MQ explorer to apply the imported settings AMQ4188Are you sure you want to remove queue manager from cluster ? Severity: 10 : Warning Explanation: A confirmation is required before the queue manager is removed from the cluster. Response: Continue only if you want to permanently remove the queue manger from the cluster. AMQ4189The queue manager could not be suspended from the cluster. The operation failed with error . Severity: 20 : Error Explanation: The queue manager has not been removed from the cluster. Response: Try the operation again. If the error persists, examine the problem determination information to see if any information has been recorded. AMQ4190An error occurred when clearing the queue manager's REPOS field. The operation failed with error . Severity: 20 : Error Explanation: The queue manager has only partially been removed from the cluster. The queue manager has been suspended from the cluster. The REPOS field of the queue manager and the CLUSTER fields of the associated cluster channels have not been cleared. Response: Try the operation again. If the error persists, examine the problem determination information to see if any information has been recorded. AMQ4191An error occurred when clearing the CLUSTER field of channel . The operation failed with error . Severity: 20 : Error Explanation: The queue manager has only partially been removed from the cluster. The queue manager has been suspended from the cluster and the queue manager's REPOS field has been cleared. Some of the CLUSTER fields of other associated cluster channels might also have been cleared. Response: To completely remove the queue manager, ensure that all the CLUSTER fields of associated cluster channels are cleared. AMQ4192The queue manager could not be removed from a cluster because channel is using cluster namelist . Severity: 10 : Warning Response: Remove the cluster channel from the cluster namelist. Ensure that you do not inadvertently affect the definitions of other objects using the namelist. Then try removing the queue manager again. AMQ4193The information supplied could not be correctly converted to the required code page. Severity: 20 : Error Explanation: All or part of the information entered required conversion to a different code page. One or more characters could not be converted to an equivalent character in the new code page. Response: Change the characters used, then try the operation again. AMQ4194Request failed because the queue manager attempted to use a default transmission queue which is not valid. Severity: 20 : Error Explanation: An MQOPEN or MQPUT1 call specified a remote queue as the destination. The queue manager used the default transmission queue, as there is no queue defined with the same name as the destination queue manager, but the attempt failed because the default transmission queue is not a valid local queue. Response: Check that the queue manager's default transmission queue property (DefXmitQName) specifies a valid local queue. AMQ4195WebSphere MQ Explorer is now in an unknown state and should be restarted. Do you want to restart WebSphere MQ Explorer? Severity: 10 : Warning Explanation: You have chosen not to wait for WebSphere MQ to respond to a request. WebSphere MQ Explorer is therefore in an unknown state and should be restarted. Response: Restart the WebSphere MQ Explorer and try the operation again. If the problem persists check for problem determination information. AMQ4196The command or operation is not valid against the type of object or queue specified Severity: 20 : Error Explanation: You have attempted a command or operation against an object or queue whose type is not valid for the operation specified. For instance: browsing a remote queue; issuing the clear command against a queue whose type is not QLOCAL; clearing by API calls, a queue who type cannot be opened for input. Response: Retry the command or operation against an object or queue whose type is valid for the operation requested. AMQ4197An MQOPEN or MQPUT1 call was issued specifying an alias queue as the target, but the BaseQName in the alias queue attributes is not recognized as a queue name. Severity: 20 : Error Explanation: An MQOPEN or MQPUT1 call was issued specifying an alias queue as the target, but the BaseQName in the alias queue attributes is not recognized as a queue name. This reason code can also occur when BaseQName is the name of a cluster queue that cannot be resolved successfully. Response: Correct the queue definitions. AMQ4207The path specified is not valid. Severity: 20 : Error Response: Check the path specified and try again. AMQ4400Explorer cannot administer the queue manager because the queue is not defined. Severity: 10 : Warning Explanation: Explorer uses the queue to administer queue managers. Response: Define the queue and retry. AMQ4401Explorer cannot administer the queue manager because the user is not authorised to open the queue . Severity: 10 : Warning Explanation: Explorer uses the queue to administer this queue manager. Response: Allow Explorer to open the queue and retry. AMQ4402The queue could not be opened for reason . Severity: 10 : Warning Explanation: Explorer uses the queue to administer this queue manager. Response: Allow Explorer to open the queue and retry. AMQ4500Are you sure you want to forcibly remove queue manager from cluster ? Severity: 10 : Warning Explanation: You should only forcibly remove a queue manager from a cluster when it has already been deleted and cannot be removed from the cluster in the normal way. A confirmation is required before the queue manager is forcibly removed. Response: Continue only if you want to forcibly remove the queue manager. AMQ4501The queue manager was successfully removed from the cluster. Severity: 0 : Information Explanation: The queue manager will still appear as a member of the cluster until the configuration changes have been sent across the network and the cluster channels to the queue manager have become inactive. This might take a long time. AMQ4502You have shared the queue in cluster . The queue manager is not a member of this cluster. Severity: 10 : Warning Response: To make the queue available to the members of this cluster, you must join the queue manager to the cluster. AMQ4503The list of values is too long. Severity: 10 : Warning Explanation: The list of values that you have entered is too long. The maximum number of characters allowed for this value is . AMQ4504The value is too long. Severity: 10 : Warning Explanation: You have entered a value containing too many characters. The maximum number of characters allowed for each value of this attribute is . AMQ4505There are too many entries in the list. Severity: 10 : Warning Explanation: You have entered too many values in the list. The maximum number of values is . AMQ4506Cannot connect to queue manager . It cannot be removed from the cluster in the normal way. Severity: 10 : Warning Response: Try the operation again when the queue manager is available. If the queue manager no longer exists, you can choose to forcibly remove the queue manager from the cluster. AMQ4507The remote queue manager is not using TCP/IP. Severity: 10 : Warning Explanation: The connection information available for the remote queue manager uses a communication protocol other than TCP/IP. The WebSphere MQ Explorer cannot connect to the queue manager to remove it from the cluster in the normal way. Response: If the queue manager no longer exists, you can choose to forcibly remove the queue manager from the cluster. AMQ4508The queue manager successfully left the cluster. Severity: 0 : Information Explanation: The queue manager will still appear as a member of the cluster until the configuration changes have been sent across the network and the cluster channels to the queue manager have become inactive. This might take a long time. AMQ4509The request to suspend membership of the cluster has been accepted. Severity: 0 : Information Response: Message for information only. AMQ4510The request to resume membership of the cluster has been accepted. Severity: 0 : Information Response: Message for information only. AMQ4511The queue manager is not a member of the cluster. Severity: 0 : Information Response: Message for information only. AMQ4513The request to refresh the information about the cluster has been accepted. Severity: 0 : Information Response: Message for information only. AMQ4514The queue manager is not a member of cluster . Severity: 10 : Warning Explanation: The object that you have shared in the cluster will not be available to other members of the cluster until you make this queue manager a member of the cluster. AMQ4515The repository queue manager for cluster is not available for connection. Severity: 10 : Warning Explanation: Views showing cluster queues in this cluster might not be complete. AMQ4516Cluster workload exit error. Severity: 10 : Warning Explanation: The queue manager's cluster workload exit failed unexpectedly or did not respond in time. AMQ4517Cluster resolution error. Severity: 10 : Warning Explanation: The definition of the cluster queue could not be resolved correctly because a response from a repository queue manager was not available. AMQ4518AMQ4518=A call was stopped by the cluster exit. Severity: 10 : Warning Explanation: The queue manager's cluster workload exit rejected a call to open or put a message onto a cluster queue. AMQ4519No destinations are available. Severity: 10 : Warning Explanation: At the time that the message was put, there were no longer any instances of the queue in the cluster. AMQ4520The WebSphere MQ Explorer could not initialize TCP/IP. Administration of remote queue managers and clusters is not possible. Severity: 10 : Warning AMQ4521The text you entered contained a comma (,) which is used as a list separator character. Severity: 10 : Warning Explanation: This value does not accept lists. Response: If you want to use a comma as part of a value, enclose the value in double quotes. AMQ4522The wizard was unable to add the queue manager to the cluster. All changes will be rolled back. Severity: 10 : Warning Explanation: A problem occurred while defining objects or modifying the queue manager's properties. Response: Ensure that the default objects exist for the queue manager. AMQ4523The wizard was unable to add one of the queue managers to the cluster. All changes will be rolled back. Severity: 10 : Warning Explanation: A problem occurred while defining objects or modifying one of the queue managers' properties. Response: Ensure that the default objects exist for the queue manager. AMQ4571Are you sure you want to change the location of the Key Repository for queue manager ? Severity: 10 : Warning Explanation: You might prevent the queue manager from starting if you change the Key Repository field to a location which is not valid. Response: Ensure that the location specified is correct before continuing. AMQ4572The request to refresh the information about all clusters has been accepted. Severity: 0 : Information Response: Message for information only. AMQ4574IBM WebSphere Explorer is already running. Severity: 30 : Severe error AMQ4575An error occurred initializing the data model. Severity: 30 : Severe error AMQ4576The working directory is not valid. Severity: 30 : Severe error AMQ4577An error occurred initializing the process. Severity: 30 : Severe error AMQ4578An error occurred loading the messages file . Severity: 30 : Severe error AMQ4579An error occurred loading the system libraries. Severity: 30 : Severe error AMQ4580An internal method detected an unexpected system return code. The method returned . Severity: 30 : Severe error Response: Examine the problem determination information on this computer to establish the cause of the error. AMQ4581Parameter check failed on the internal function . The error was . Severity: 30 : Severe error Response: Examine the problem determination information on this computer to establish the cause of the error. AMQ4582Queue manager is not available for client connection. Severity: 30 : Severe error Response: Ensure the queue manager is running and is configured to accept remote connections. AMQ4583Queue manager is not available for connection. Severity: 30 : Severe error Response: Ensure the queue manager is running. AMQ4584Queue manager is not available for cluster connection. Severity: 30 : Severe error Response: Ensure that the queue manager is running. If the queue manager has been deleted it might continue to be displayed as a member of a cluster for up to 30 days. AMQ4585An internal method encountered an unexpected error. Severity: 30 : Severe error Response: Examine the problem determination information on this computer to establish the cause of the error. AMQ4586The attempt to create the URL for file failed. Severity: 30 : Severe error Explanation: The file name specified was not recognized. Response: Ensure that the file exists at the specified location and can be read. AMQ4587The attempt to read from URL failed. Severity: 30 : Severe error Explanation: There was an error when the system tried to read the Client channel definition table. Response: Ensure that the file exists at the specified location and can be read. AMQ4588The attempt to read from URL failed. Severity: 30 : Severe error Explanation: There was an error when the system tried to read the file. Response: Ensure that the file exists at the specified location and can be read. AMQ4589No connection was found to application . Severity: 10 : Warning Explanation: The connection was not found. Possibly the connection was closed before the command was issued. Response: Check that the application connection has not been closed in the background. AMQ4590The queue manager connection to application could not be closed. Severity: 20 : Error Explanation: The connection could not be closed due to a PCF error. Response: Check for FFSTs. AMQ4591The command server for is not running. Severity: 30 : Severe error Explanation: The command server has stopped for some reason, so the request cannot be processed. Response: Start the command server. If the error persists, examine the problem determination information to see if any details have been recorded. AMQ4592The connection was closed successfully. Severity: 0 : Information Explanation: The request to close the connection to an application was successful. Response: Message for information only. AMQ4593Do you really want to stop the connection to application "" Severity: 0 : Information Explanation: WebSphere MQ explorer is about to stop a connection, stopping the connection will prevent further communication between MQ and the application in question. Response: Select yes if you want to stop the connection. AMQ4700PCF command identifier () not valid for queue manager . Severity: 10 : Warning Explanation: The specified PCF command is not supported by this queue manager. AMQ4800Error initializing . Severity: 30 : Severe error Explanation: An error occurred while starting this application. Response: Check that the WebSphere MQ runtime libraries are available. Check that the PATH system environment variable includes the directory for these runtime libraries.) AMQ4801Error getting the location of the help system. Severity: 10 : Warning Explanation: To launch the standalone Eclipse help system, the WebSphere MQ file transfer application needs to know where it is installed. Response: Check that Eclipse has been installed with WebSphere MQ. AMQ4802Error launching the help system. Severity: 10 : Warning Explanation: The WebSphere MQ file transfer application failed to create an instance of the Eclipse standalone help system. Response: Check that Eclipse has been installed with WebSphere MQ. AMQ4803Error starting the help system. Severity: 10 : Warning Explanation: The WebSphere MQ file transfer application failed to start the standalone Eclipse system. Response: Check that Eclipse has been installed with WebSphere MQ. AMQ4805Error saving the history log file. Severity: 10 : Warning Explanation: The WebSphere MQ file transfer application could not read the history log file. This file is called com.ibm.mq.fta.log.ser and is in your home directory. On Windows, this is %APPDATA%\IBM\WebSphere MQ FileTransferApp On Unix, this is $HOME/.mqdata Response: Check that the read/write properties on this file allow you to write to it. AMQ4806Error reading the history log. Severity: 10 : Warning Explanation: The WebSphere MQ file transfer application could not read the history log file. This file is called com.ibm.mq.fta.log.ser and is in your home directory. On Windows, this is %APPDATA%\IBM\WebSphere MQ FileTransferApp On Unix, this is $HOME/.mqdata Response: Check that the read/write properties on this file allow you to write to it. AMQ4807The message size specified () is outside the permitted range. Severity: 10 : Warning Response: Specify a value of 1000 to 100 000 000. XXXX 4200-4217 - WebSphere MQ Default Configuration AMQ4200There is a problem with the default configuration. Unable to display the Default Configuration window. Explanation: There is a problem with WebSphere MQ. Response: Use the 'Details>>' button to show further details about the problem and contact your systems administrator. AMQ4201Unable to check if the computer exists. Explanation: WebSphere MQ was unable to check if the computer name you entered exists on your computer's domain. Response: Retry the operation, if the problem persists contact your systems administrator. AMQ4202Unable to contact the computer '%1'. Explanation: WebSphere MQ was unable to locate a computer with this name on your computer's TCP/IP domain. Response: Enter a different computer name. AMQ4203Unable to set up the default configuration. Explanation: WebSphere MQ was unable to set up the default configuration. This error may occur if WebSphere MQ is busy with another operation. Response: Retry the operation. If the problem persists, use the 'Details>>' and 'Print' buttons to record further details about the problem and contact your systems administrator. AMQ4204Unable to join the default cluster. Explanation: WebSphere MQ was unable to join your computer to the default cluster. This error may occur if WebSphere MQ is busy with another operation. Response: Retry the operation. If the problem persists, use the 'Details>>' and 'Print' buttons to record further details about the problem and contact your systems administrator. AMQ4205Unable to allow remote administration of the queue manager. Explanation: WebSphere MQ was unable change the configuration of your queue manager to allow it to be remotely administered. This error may occur if WebSphere MQ is busy with another operation. Response: Retry the operation. If the problem persists, use the 'Details>>' and 'Print' buttons to record further details about the problem and contact your systems administrator. AMQ4206Unable to prevent remote administration of the queue manager. Explanation: WebSphere MQ was unable change the configuration of your queue manager to prevent it from being remotely administered. This error may occur if WebSphere MQ is busy with another operation. Response: Retry the operation. If the problem persists, use the 'Details>>' and 'Print' buttons to record further details about the problem and contact your systems administrator. AMQ4208Show this panel again the next time the queue manager is started? Explanation: You can choose whether you want the same panel to be shown the next time this queue manager is started, and the default configuration is not complete. Response: Select whether you want the panel to be shown next time. AMQ4209The TCP/IP name of the remote computer must not be your own computer name. Explanation: You have selected that the repository queue manager is on another computer, but you have entered the name of your own computer. Response: Enter the correct name of the repository queue manager. AMQ4210The command server must be active to complete this operation. Use the WebSphere MQ Services to start it, then retry the operation. Explanation: The operation you requested needs the command server to be running. Response: Use WebSphere MQ Services to start the command server, then retry the operation. AMQ4211The computer name entered must be on your local domain ('%1'). AMQ4212Unable to complete this task because you do not have authority to administer WebSphere MQ. You must be in the Administrators group, in the mqm group or logged in with the SYSTEM ID to administer WebSphere MQ. Explanation: Your userid is not authorized to carry out the operation you requested. Response: Retry the operation on a userid with the required authority, or contact your systems administrator. AMQ4213Unable to delete the queue manager '%1' because it is being used by another program. Close any program using the queue manager, then click 'Retry'. Explanation: WebSphere MQ was unable to delete the old default configuration queue manager because another program is using the queue manager. Response: Close the programs that are using the queue manager, and click Retry. AMQ4214The computer '%1' is not known on the network. Explanation: WebSphere MQ is unable to locate a computer with this name on your network. Response: Enter a different computer name. AMQ4215Upgrade of the default configuration was cancelled. Explanation: You pressed 'Cancel' while running the default configuration wizard to upgrade the default configuration. Response: None AMQ4216The WebSphere MQ services component does not have the authority it requires. AMQ4217The MQSeriesServices component does not have the authority to create the default configuration. 4235-4238 - Prepare WebSphere MQ Wizard AMQ4235WebSphere MQ running on this computer was unable to retrieve group membership information for user '%1' AMQ4236WebSphere MQ running on this computer can now retrieve group membership information for user '%1'. AMQ4237WebSphere MQ running on this computer is still unable to retrieve group membership information for user '%1'. AMQ4238You are not authorized to run the Prepare WebSphere MQ Wizard. To run this wizard, you must be in the in the 'Administrators' group. 4250-4274 - 'Postcard' messages AMQ4250No nickname supplied - Please supply one. AMQ4251Cannot Initialise WinSock - TCP/IP may not be installed. Please install TCP/IP and try again. Explanation: Postcard was not able to initialize the interface to TCP/IP. Response: Check that TCP/IP has been installed successfully. If the problem persists, refer to your systems administrator. AMQ4252Cannot Find WinSock - TCP/IP may not be installed. Please install TCP/IP and try again. Explanation: Postcard was not able to find the interface to TCP/IP. Response: Check that TCP/IP has been installed successfully. If the problem persists, refer to your systems administrator. AMQ4253Cannot get fully qualified TCP/IP domain name - Please ensure that the TCP/IP protocol is configured. Explanation: Postcard was not able to determine the TCP/IP domain name for your computer. Response: Check that TCP/IP has been installed successfully. If the problem persists, refer to your systems administrator. AMQ4254Failed to Allocate System Memory - Please contact your system administrator. Explanation: Postcard was not able to allocate enough memory to run correctly. Response: Close other programs to release system memory. If the problem persists, refer to your systems administrator. AMQ4255Please supply a user name with which you wish to communicate. AMQ4256Please supply %s's computer name (this must be a TCP/IP name). Please supply %s's computer name (this must be a TCP/IP name). AMQ4257The call MQCONN failed while preparing for a Put operation, with Completion Code [%s (%ld)], Reason Code [%s (%ld)]. Explanation: An error occurred when Postcard tried to connect to the queue manager in order to send the postcard. This error may occur if WebSphere MQ is busy with another operation. Response: Try to send the postcard again. If the problem persists contact your systems administrator. AMQ4258The call MQOPEN failed while preparing for a Put operation, with Completion Code [%s (%ld)], Reason Code [%s (%ld)]. Explanation: An error occurred when Postcard tried to open a queue in order to send the postcard. This error may occur if WebSphere MQ is busy with another operation. Response: Try to send the postcard again. If the problem persists contact your systems administrator. AMQ4259The call MQCLOSE failed while preparing for a Put operation, with Completion Code [%s (%ld)], Reason Code [%s (%ld)]. Explanation: An error occurred when Postcard tried to close the queue after sending the postcard. This error may occur if WebSphere MQ is busy with another operation. Response: If the problem persists contact your systems administrator. AMQ4260The call MQDISC failed while preparing for a Put operation, with Completion Code [%s (%ld)], Reason Code [%s (%ld)]. Explanation: An error occurred when Postcard tried to disconnect from the queue manager after sending the postcard. This error may occur if WebSphere MQ is busy with another operation. Response: If the problem persists contact your systems administrator. AMQ4261The call MQPUT failed with Completion Code [%s (%ld)], Reason Code [%s (%ld)]. Explanation: An error occurred when Postcard tried to send the postcard by putting its data to the queue. This error may occur if WebSphere MQ is busy with another operation. Response: Try to send the postcard again. If the problem persists contact your systems administrator. AMQ4262The call MQCONN failed while preparing for a Get operation, with Completion Code [%s (%ld)], Reason Code [%s (%ld)]. Explanation: An error occurred when Postcard tried to connect to the queue manager in order to receive postcards. This error may occur if WebSphere MQ is busy with another operation. Response: Restart Postcard. If the problem persists contact your systems administrator. AMQ4263The call MQOPEN failed while preparing for a Get operation, with Completion Code [%s (%ld)], Reason Code [%s (%ld)]. Explanation: An error occurred when Postcard tried to open a queue in order to send the postcard. This error may occur if WebSphere MQ is busy with another operation. Response: Restart Postcard. If the problem persists contact your systems administrator. AMQ4264The call MQCLOSE failed while preparing for a Get operation, with Completion Code [%s (%ld)], Reason Code [%s (%ld)]. Explanation: An error occurred when Postcard tried to close the queue after receiving postcards. This error may occur if WebSphere MQ is busy with another operation. Response: If the problem persists contact your systems administrator. AMQ4265The call MQDISC failed while preparing for a Get operation, with Completion Code [%s (%ld)], Reason Code [%s (%ld)]. Explanation: An error occurred when Postcard tried to disconnect from the queue manager after receiving postcards. This error may occur if WebSphere MQ is busy with another operation. Response: If the problem persists contact your systems administrator. AMQ4266Please type in a message that you wish to send to %s. AMQ4267The call MQGET failed with Completion Code [%s (%ld)], Reason Code [%s (%ld)]. Explanation: An error occurred when Postcard tried to receive a postcards by getting its data from the queue. This error may occur if WebSphere MQ is busy with another operation. Response: Restart Postcard. If the problem persists contact your systems administrator. AMQ4268MQI Postcard is unable to contact the queue manager on the remote computer. Verify that the default configuration is up and running on the remote computer. AMQ4269Unable to run MQI Postcard because you do not have authority to use WebSphere MQ. You must be in the Administators group, in the mqm group, or logged in with the SYSTEM ID to use WebSphere MQ. Explanation: Your user Id is not authorized to use Postcard. You must be in the Administrator's group, in the mqm group, or logged in with the SYSTEM ID to use WebSphere MQ. Response: Use Postcard on a user Id with the required authority, or contact your systems administrator. AMQ4270MQI Postcard is unable to send messages to the remote computer. MQI Postcard can only exchange messages with computers that are on the same TCP/IP domain as this computer (%1). AMQ4271Unable to open a local queue called '%1' on the mailbox queue manager '%2'. Use WebSphere MQ Explorer to create the queue, then restart MQI Postcard. Explanation: Postcard was unable to automatically create the queue it uses on the queue manager. Response: Use WebSphere MQ Explorer to create the queue, and restart Postcard. AMQ4272The mailbox queue manager '%1' does not exist on this computer. Explanation: The mailbox queue manager name specified after the '-m' parameter to Postcard does not exist on this computer. Response: Restart Postcard specifying the name of a queue manager that does exist on this computer. AMQ4273Unable to contact the target mailbox '%1'. Explanation: Postcard was unable send the message as it could not contact the target mailbox. Response: Click 'Retry' to attempt to send the message again, otherwise click 'Cancel'. AMQ4274MQI Postcard has detected that '%1' is the name of a computer and a queue manager. Explanation: Postcard has detected that the destination mailbox name is the name of a computer and of a queue manager. Response: Select whether you want to send the message to the computer or the queue manager with this name, then click OK. 4300-4309 - WebSphere MQ API Exerciser AMQ4300Please supply some text in order for the MQPUT(1) operation to succeed. Explanation: No text has been supplied for the user so that the MQPUT or MQPUT1 operation can proceed. Response: Supply some text in the editable area so that the MQPUT or MQPUT1 operation can proceed. AMQ4301Please supply some text in order for the MQPUT operation to succeed. Explanation: No text has been supplied for the user so that the MQPUT operation may proceed. Response: Supply some text in the editable area so that the MQPUT may proceed. AMQ4302Please supply some text in order for the MQPUT1 operation to succeed. Explanation: No text has been supplied for the user so that the MQPUT1 operation may proceed. Response: Supply some text in the editable area so that the MQPUT1 may proceed. AMQ4303The command server for the queue manager [%s] is not started. Start the command server and try again. Explanation: In order for the API Exerciser to function, a command server must be running. Response: Either start the command server from the MQServices application or run strmqcsv from the command line. AMQ4304API Exerciser cannot enumerate objects for queue manager [%s]. Explanation: The API Exerciser encountered a problem trying to enumerate queues. Response: Ensure that the command server is running (from the Service application) and that there are queues configured for the queue manager. AMQ4305There are no queue managers present in the system. Please create one and try again. Explanation: The API Exerciser could not find any queue managers on the system. Response: Use the Services application to create one or run crtmqm . AMQ4306Memory allocation failure. Stop some other applications and try again. Explanation: There are not sufficient system resources available in the system to satisfy the running of API Exerciser. Response: Shut some other applications down and try running the API Exerciser again. AMQ4307API Exerciser encountered a COM failure and cannot continue. Please ensure that WebSphere MQ has been correctly installed and configured and that your user id. is a member of the mqm group. Explanation: When the API Exerciser started, it was unable to make a COM connection to WebSphere MQ Services. Response: Ensure that WebSphere MQ has been correctly installed and configured, and that your user ID is a member of the mqm group. If the problem persists, refer to your systems administrator. AMQ4308API Exerciser cannot continue. Please ensure that the userid you are using is a member of the mqm group. AMQ4309API Exerciser cannot continue. Please ensure that the userid you are using is a member of the Administrator group. 4350-4764 - Installation messages AMQ4350Setup cannot continue; a later version of this product is installed. Explanation: Installation detected that a version of this product later than version 5.3 is already installed on the computer. Response: Do not attempt to install version 5.3 when a later version is already installed. AMQ4351Uninstallation cannot continue; uninstallation is already running. Explanation: An attempt was made to run two copies of uninstallation at once. Response: Run only one copy of uninstallation at a time. AMQ4352Setup cannot continue; a supported version of Windows(R) is required. AMQ4353Setup cannot continue; '%s' is not an Administrator. Explanation: The user running installation does not have administrator authority. Response: Log off and log back on using a user ID with administrator authority. AMQ4354No repository computer name entered. AMQ4355Repository computer name is not valid. AMQ4356Enter a remote computer name. AMQ4357Registration failed for file '%s' (code 0x%8.8lx). AMQ4358Unregistration failed for file '%s' (code 0x%8.8lx). AMQ4359Unable to register file '%s'. AMQ4360Unable to unregister file '%s'. AMQ4361Uninstall cannot continue; Administrator logon required. AMQ4362Failed to create the default configuration. AMQ4363Setup could not detect the Windows NT(R) Service Pack level (Service Pack 3 or later is required). Is Service Pack 3 or later installed? AMQ4364Setup could not detect the Windows NT Service Pack level (Service Pack 6a or later is required). Is Service Pack 6a or later installed? AMQ4365Setup cannot continue because Service Pack 3 is not installed. AMQ4366Setup cannot continue because Service Pack 6a or later is not installed. AMQ4367Setup cannot continue because Internet Explorer Version 4.01 SP1 is not installed. AMQ4368Select at least one component to proceed. AMQ4369The 'Web Administration Server' component requires the 'Server' component. AMQ4370Uninstallation of the 'Server' component requires uninstallation of the 'Web Administration Server' component. AMQ4371The 'Documentation in Other Languages' component requires the 'Documentation in English' component. AMQ4372Uninstallation of the 'Documentation in English' component requires uninstallation of the 'Documentation in Other Languages' component. AMQ4373There is not enough space on drive %s (program files) to install these components. Please free up some disk space or modify your selections AMQ4374There is not enough space on drive %s (data files) to install these components. Please free up some disk space or modify your selections AMQ4375The program files top-level folder is not valid. Explanation: The program files top-level folder is not a valid path. Response: Enter a valid path. AMQ4376The data files top-level folder is not valid. Explanation: The data files top-level folder is not a valid path. Response: Enter a valid path. AMQ4377The log files folder is not valid. Explanation: The log files folder name is not a valid path. Response: Enter a valid path. AMQ4378A root folder is not allowed for the program files top-level folder. Explanation: WebSphere MQ cannot be installed in a root folder, for example 'c:\'. Response: Enter a non-root folder. AMQ4379A root folder is not allowed for the data files top-level folder. Explanation: WebSphere MQ cannot be installed in a root folder, for example 'c:\'. Response: Enter a non-root folder. AMQ4380A root folder is not allowed for the log files folder. Explanation: WebSphere MQ cannot be installed in a root folder, for example 'c:\'. Response: Enter a non-root folder. AMQ4381There is not enough space on drive %s (log files) to install these components. Please free up some disk space or modify your selections AMQ4382Unable to create or replace folder '%s' AMQ4383Uninstallation cannot continue; failed to save queue manager configuration. Explanation: An error occurred while saving the current queue manager configuration to a file. Response: Check that the registry keys under 'HKEY_LOCAL_MACHINE\SOFTWARE\IBM\WebSphere MQ'are readable by an administrator. Check that there is enough space on the drive containing the data files folder (where the configuration is being saved in file \config\config.reg). If the error persists, contact your systems administrator. AMQ4385Unknown language specified ('%s') AMQ4386Codepage (%d) for specified language not available. AMQ4387Before Setup can display help, this computer's help system needs upgrading to HTML Help 1.3. Would you like to upgrade now? (You might need to restart the computer.) AMQ4388WebSphere MQ Setup or uninstallation is already running. AMQ4389Setup could not create a local 'mqm' group (code %d). Explanation: An error occurred creating a local user group called 'mqm'. Response: Review the installation log file for details of any problems. If the error persists, contact your systems administrator. AMQ4390Setup could not create a global 'Domain mqm' group (code %d). Explanation: An error occurred creating a local user group called 'mqm'. Response: Review the installation log file for details of any problems. If the error persists, contact your systems administrator. AMQ4391Setup could not find the global 'Domain mqm' group. Explanation: The global 'mqm ' group was created, but could not then be found. Response: Review the installation log file for details of any problems. If the error persists, contact your systems administrator. AMQ4392Setup could not add the global 'Domain mqm' group to the local 'mqm' group (code %d). Explanation: An error occurred adding the global 'mqm' group to the local 'mqm' group. Response: Review the installation log file for details of any problems. If the error persists, contact your systems administrator. AMQ4393No ports were specified; no listeners will be created. AMQ4394No queue managers are selected for remote administration. AMQ4395One or more 'Server' component prerequisites were not selected; the component cannot be installed. AMQ4396One or more prerequisite upgrades were not selected; WebSphere MQ will not operate correctly. AMQ4397Cannot install on a network drive (drive %s), AMQ4703One or more problems occurred during Setup. Review '%s' for details Explanation: Setup was only partially successful. Response: Review the installation log file for details of any problems. AMQ4704If specified, TCP/IP domain must be '%s' AMQ4705Current maintenance level is '%s'. Re-apply maintenance after Setup completes. Explanation: Some service has been applied to the current installation. Installation or reinstallation of WebSphere MQ components might regress some files. Response: Review the instructions that came with the service that was applied. If necessary re-apply the service. AMQ4706Dialog '%s' failed. AMQ4707Error migrating '%s'. Explanation: An error occurred migrating a .ini file to the registry. Response: Review the installation log file for details of any problems. If the error persists, contact your systems administrator. AMQ4708Error creating remote administration channel for queue manager '%s'. AMQ4709Error creating TCP/IP listener for queue manager '%s'. AMQ4710Error updating '%s' environment variable. AMQ4711One or more problems occurred during uninstallation. Review '%s' for details Explanation: Uninstallation was only partially successful. Response: If the installation log file is available, review it for details of any problems. If the error persists, contact your systems administrator. AMQ4712The WebSphere MQ Service failed to stop. Explanation: An error occurred trying to stop the WebSphere MQ service Response: Review the installation log file for details of any problems. If the error persists, contact your systems administrator. AMQ4713The WebSphere MQ Service failed to start. Explanation: An error occurred trying to start the WebSphere MQ service Response: Review the installation log file for details of any problems. If the error persists, contact your systems administrator. AMQ4714Failed to delete the WebSphere MQ Service (code %d). Explanation: An error occurred trying to delete the WebSphere MQ service Response: Review the installation log for details of any problems. If the error persists, contact your systems administrator. AMQ4715Failed to add the WebSphere MQ Service. Explanation: An error occurred trying to create the WebSphere MQ service Response: Review the installation log for details of any problems. If the error persists, contact your systems administrator. AMQ4716Can't load '%s'. AMQ4717Can't start dialog '%s'. AMQ4718Can't load performance counters (code 0x%8.8lx). Explanation: An error occurred trying to register the WebSphere MQ performance counter library. Response: Review the installation log for details of any problems. If the error persists, contact your systems administrator. AMQ4719Error migrating queue manager command files. Explanation: An error occurred migrating queue manager command files. Response: Review the installation log for details of any problems. If the error persists, contact your systems administrator. AMQ4720Error initializing security environment. AMQ4721WebSphere MQ messages language changed to %s. AMQ4722Setup cannot continue without VGA or better screen resolution. Explanation: Setup was run using a monitor resolution less than VGA resolution. Response: Use a monitor with resolution equal to or better than 640 x 480 pixels. AMQ4723Error during uninstaller initialization. You might not be able to uninstall WebSphere MQ. AMQ4724Error restoring queue manager configuration. Explanation: An error occurred restoring queue manager configuration from the config.reg file in the data directory. Response: Review the installation log file for details of any problems. If the error persists, contact your systems administrator. AMQ4725The Server feature cannot be installed without 800 x 600 or better screen resolution. AMQ4726The 'Internet Gateway' component requires the 'Windows NT Client' component. AMQ4727Uninstallation of the 'Windows NT Client' component requires uninstallation of the 'Internet Gateway' component. AMQ4728Setup could not create a default configuration because some files were locked. Run WebSphere MQ First Steps after restarting the computer. AMQ4729You cannot install the Windows Client from the client CD because WebSphere MQ server components are already installed on this computer. To install the Windows Client on this computer, use the server CD. Explanation: An attempt has been made to install a feature using the Windows client CD when one or more features have already been installed using the server CD. This is not allowed. Either uninstall the server features first, or use only the server CD. Response: Review the installation log file for details of any problems. If the error persists, contact your systems administrator. AMQ4730Java(TM) support is now separately available; see the installation notes. Setup will delete existing MQSeries(R) V5.1 Java files. AMQ4731Setup cannot continue without SVGA or better screen resolution (800 x 600). AMQ4732No installation language specified. Use the TRANSFORMS property. Explanation: An attempt was made to invoke an installation without specifying a user-interface language. Use the TRANSFORMS property to specify a language. Response: Review the installation log file for details of any problems. If the error persists, contact your systems administrator. AMQ4733Unable to launch program '%s'. Explanation: An error occurred trying to execute the indicated program. Response: Review the installation log file for details of any problems. If the error persists, contact your systems administrator. AMQ4734Can't open file '%s'. Explanation: Setup was unable to open the indicated file for reading. Response: Review the installation log file for details of any problems. If the error persists, contact your systems administrator. AMQ4735Error %1 reading response file '%2'. Explanation: An error occurred. Response: Review the installation log file for details of any problems. If the error persists, contact your systems administrator. AMQ4736Error %1 creating response file '%2'. Explanation: An error occurred restoring queue manager configuration from the config.reg file in the data directory. Response: Review the installation log file for details of any problems. If the error persists, contact your systems administrator. AMQ4737Unknown value '%1' for property '%2' in '%3'. AMQ4738Repair option is not supported. AMQ4739One or more problems occurred. Review the trace and/or log file for details. AMQ4740Unknown feature(s) '%1' in command-line property '%2'. Explanation: A property, for example ADDLOCAL, containing a feature-list was specified, but one or more of the feature names was invalid. Response: Remove the invalid feature name. If the error persists, contact your systems administrator. AMQ4742Unknown feature(s) '%1' in property '%2' in '%3'. Explanation: A property, for example ADDLOCAL, containing a feature-list was specified, but one or more of the feature names was invalid. Response: Remove the invalid feature name. If the error persists, contact your systems administrator. AMQ4743Unknown property '%1' in '%2'. AMQ4744Have you purchased sufficient license units to install IBM(R) WebSphere MQ on this computer? (For further information on license units refer to the Quick Beginnings book.) Explanation: You must purchase the appropriate number of license units for the number of processors in this computer. Response: If you have purchased the appropriate number of license units, reply "Yes", otherwise reply "No". AMQ4745After the upgrade you might need to reboot. Is it OK to proceed? AMQ4745This installation requires %d license units to have been purchased with IBM WebSphere MQ (for further information on license units refer to the Quick Beginnings book). If you do not know how many license units have been purchased, ask your system administrator or vendor. Have sufficient license units been purchased for this installation? AMQ4746Setup needs to install or upgrade this computer to version 2.0 of Microsoft(R) Windows Installer. (MSI). OK to proceed (you might need to reboot)? Explanation: A version of Microsoft Windows Installer (MSI) earlier than 2.0 is installed. WebSphere MQ Setup requires at least version 2.0. Response: Reply "Yes" to install MSI version 2.0, otherwise "No". To install WebSphere MQ, version 2.0 is required. AMQ4747You must reboot before continuing with installation. Do you want to reboot now? AMQ4748Can't install on top of an Early-Release installation. Uninstall the Early Release first. Explanation: An attempt was made to install WebSphere MQ on top of an Early Version ("beta"). Response: Uninstall the Early Version before proceeding. If the error persists, contact your systems administrator. AMQ4749Can't install an Early Release on top of Version %s. Uninstall first. Explanation: An attempt was made to install an Early Version ("beta") on top of another version of WebSphere MQ. Response: Uninstall the existing version of WebSphere MQ before proceeding with the Early Version. If the error persists, contact your systems administrator. AMQ4750Can't convert. Need production version of WebSphere MQ. Explanation: The property TRIALTOPROD has been specified but the WebSphere MQ version on the CD is not a production version. Response: Do not specify TRIALTOPROD if the version of WebSphere MQ you are using is not a production version. If the error persists, contact your systems administrator. AMQ4751Can't convert. Installed product is not an Evaluation Copy. Explanation: The property TRIALTOPROD has been specified but the WebSphere MQ version installed is not an Evaluation Copy. Response: Do not specify TRIALTOPROD if the installed version of WebSphere MQ is not an Evaluation Copy. If the error persists, contact your systems administrator. AMQ4752You have insufficient license units for this installation, and you must purchase additional units from your vendor. You can continue to install WebSphere MQ, but this status will be recorded in the error log. For information on how to inform WebSphere MQ when you have purchased sufficient license units, refer to the System Administration Guide. Do you want to proceed with WebSphere MQ installation? Explanation: You replied "No" to message number AMQ4744. Response: Reply "Yes" to continue the installation, or "No" to cancel. Make sure that you purchase the appropriate number of license units. AMQ4753SupportPac(TM) MC74 (Microsoft Cluster Server support) is installed on this system. You must uninstall the SupportPac before installing WebSphere MQ server; see the Installation Guide. Explanation: WebSphere MQ installation requires that SupportPac MC74 be uninstalled. Response: For more information, see the WebSphere MQ Installation Guide. AMQ4754SupportPac MS0J (Web Administration Server) is installed on this computer. You must uninstall the SupportPac before uninstalling WebSphere MQ server. AMQ4756IBM WebSphere MQ Version %s is not installed. AMQ4757IBM WebSphere MQ files are in use. Stop activity and retry. Explanation: One or more WebSphere MQ files are being used by processes running on the system. Response: Ensure that all queue managers, listeners, channels and WebSphere MQ services are stopped. Use the Windows task manager to ensure that there are no processes running with an "amq", "runmq", or "strmq" prefix. Stop any tools used to monitor WebSphere MQ and stop any Performance Monitor tasks. If the process locking WebSphere MQ files cannot be identified, installation can usually procede following a reboot, with the WebSphere MQ service disabled. AMQ4758Maintenance levels out of sequence. Latest maintenance applied is %s. AMQ4759SupportPac MA0C (Publish And Subscribe) is installed on this system. You must uninstall the SupportPac before installing WebSphere MQ server; see the Installation Guide. AMQ4760Error installing %s. Examine log file '%s'. AMQ4761Error uninstalling %s. Examine log file '%s'. AMQ4762No maintenance is installed. AMQ4763Cannot overwrite WebSphere MQ Version %1 with Version %2. Explanation: The service level you are trying to install is less than that already installed. The installation will not proceed. Response: Check that you are attempting to install the latest CSD. AMQ4764WebSphere MQ 'Client' feature at version %1 maintenance level %2 is not installed. 5000-5999 - Installable services See Reading a message for an explanation of how to interpret these messages. AMQ5005Unexpected error Severity: 20 : Error Explanation: An unexpected error occurred in an internal function of the product. Response: Save the generated output files and contact your IBM support center. AMQ5006Unexpected error: rc = Severity: 20 : Error Explanation: An unexpected error occurred in an internal function of the product. Response: Save the generated output files and contact your IBM support center. AMQ5008An essential WebSphere MQ process () cannot be found and is assumed to be terminated. Severity: 40 : Stop Error Explanation: 1) A user has inadvertently terminated the process. 2) The system is low on resources. Some operating systems terminate processes to free resources. If your system is low on resources, it is possible it has terminated the process so that a new process can be created. Response: WebSphere MQ will stop all MQ processes. Inform your systems administrator. When the problem is rectified WebSphere MQ can be restarted. AMQ5009WebSphere MQ agent process has terminated unexpectedly. Severity: 40 : Stop Error Explanation: WebSphere MQ has detected that an agent process has terminated unexpectedly. The queue manager connection(s) that this process is responsible for will be broken. Response: Use any previous FFSTs to determine the reason for the failure. Try to eliminate the following reasons before contacting your IBM support center. 1) A user has inadvertently terminated the process. 2) The system is low on resources. Some operating systems terminate processes to free resources. If your system is low on resources, it is possible that the operating system has terminated the process so that a new process can be created. AMQ5010The system is restarting the WorkLoad Management Server process. Severity: 10 : Warning Explanation: The system has detected that the WorkLoad Management server process (amqzlwa0, pid:) has stopped and is restarting it. Response: Save the generated output files which may indicate the reason why the WorkLoad Management process stopped. If the reason the WorkLoad Management Server process stopped is a problem in a WorkLoad Management user exit, correct the problem, otherwise contact your IBM support center. AMQ5011The Queue Manager ended for reason Severity: 10 : Warning Explanation: The Queue Manager ended because of a previous error or Response: This message should be preceded by a message or FFST information from the internal routine that detected the error. Take the action associated with the earlier error information. AMQ5019Unable to access program . Severity: 40 : Stop Error Explanation: A request was made to execute the program , however the operation was unsuccessful because the program could not be found in the specified location. Response: Check the definition of the service specifies the correct and full path to the program to run. If the path is correct then verify that the program exists in the specified location and that WebSphere MQ userid has permission to access it. AMQ5020Permission denied attempting to execute program . Severity: 40 : Stop Error Explanation: A request was made to execute the program , however the operation was unsuccessful because the WebSphere MQ operating environment has insufficient permissions to access the program file. Response: Check the access permissions of the of the program to be executed and if necessary alter them to include execute permission for the WebSphere MQ userId. Also check that the WebSphere MQ userId has search access on all directories which compose the path to the program file. AMQ5021Unable to start program . Severity: 40 : Stop Error Explanation: A request was made to execute the program however the operation was unsuccessful. Reasons for the failure may include a shortage of available system resources a problem with the program to be started Response: If the problem persists then the WebSphere MQ error logs should be consulted for further information related to this error. The Operating System error recording facilities should also be consutled for information relating to shortage of system resources. AMQ5022The Channel Initiator has started. ProcessId(). Severity: 0 : Information Explanation: The Channel Initiator process has started. Response: None. AMQ5023The Channel Initiator has ended. ProcessId(). Severity: 0 : Information Explanation: The Channel Initiator process has ended. Response: None. AMQ5024The Command Server has started. ProcessId(). Severity: 0 : Information Explanation: The Command Server process has started. Response: None. AMQ5025The Command Server has ended. ProcessId(). Severity: 0 : Information Explanation: The Command Server process has ended. Response: None. AMQ5026The Listener has started. ProcessId(). Severity: 0 : Information Explanation: The Listener process has started. Response: None. AMQ5027The Listener has ended. ProcessId(). Severity: 0 : Information Explanation: The Listener process has ended. Response: None. AMQ5028The Server has started. ProcessId(). Severity: 0 : Information Explanation: The Server process has started. Response: None. AMQ5029The Server has ended. ProcessId(). Severity: 0 : Information Explanation: The Server process has ended. Response: None. AMQ5030The Command has started. ProcessId(). Severity: 0 : Information Explanation: The Command has started. Response: None. AMQ5032Error () accessing file . Severity: 40 : Stop Error Explanation: While attempting to access the file the error occurred. Response: Use the information contained in the error to locate and correct the cause of the failure. AMQ5036Error detected processing line , position in service environment file. Severity: 40 : Stop Error Explanation: While processing the environment file an error was detected on line at position . Possible causes are Variable name too long Variable value too long Incorrectly formed line. Lines must be in the format =. There should be no blank characters in name field. All characters following the '=' are part of the value field. Response: This error will not stop the command from executing but any data on the invalid line is not processed. AMQ5037The Queue Manager task has started. Severity: 0 : Information Explanation: The Utility Task Manager, processId() type(), has started the task. Response: None. AMQ5038The Queue Manager task failed to start with error-code . Severity: 40 : Stop Error Explanation: The Utility Task Manager, attempted to start the task but the start request failed with error code . Response: The failure to start the identified task may not be critical to queue-manager operation however all of the queue manager functionality may not be available. Further details of the failure are available in WebSphere MQ error logs. AMQ5041The Queue Manager task has ended. Severity: 0 : Information Explanation: The Queue Manager task has ended. Response: None. AMQ5042Request to start failed. Severity: 40 : Stop Error Explanation: The request to start the process failed. Response: Consult the Queue Manager error logs for further details on the cause of the failure. AMQ5043Statistics recording is unavailable due to error code . Severity: 40 : Stop Error Explanation: The statistics collection task was unable to start due the error code . Statistics collection will be unavailable until the problem is rectified and the Queue Manager is restarted. Response: Consult the Queue Manager error logs for further details on the cause of the failure. AMQ5044 task operation restricted due to Reason Code . Severity: 10 : Warning Explanation: The task encountered a non-fatal error which may effect the operation of the task. Response: Using the Reason Code and any previous messages recorded in the Error Logs correct the error. It may be necessary to restart the Queue Manager in order remove the restriction caused by the failure. AMQ5045System reconfiguration event received Severity: 0 : Information Explanation: The Queue Manager received a system re-configuration event. This is likely to have been caused by an administrative change in the configuration of the machine (for example dynamically adding or removing resources such as memory or processors). Response: No action is required unless this notification was unexpected. AMQ5203An error occurred calling the XA interface. Severity: 0 : Information Explanation: The error number is where a value of 1 indicates the supplied flags value of was invalid, 2 indicates that there was an attempt to use threaded and non-threaded libraries in the same process, 3 indicates that there was an error with the supplied queue manager name , 4 indicates that the resource manager id of was invalid, 5 indicates that an attempt was made to use a second queue manager called when another queue manager was already connected, 6 indicates that the Transaction Manager has been called when the application isn't connected to a queue manager, 7 indicates that the XA call was made while another call was in progress, 8 indicates that the xa_info string in the xa_open call contained an invalid parameter value for parameter name , 9 indicates that the xa_info string in the xa_open call is missing a required parameter, parameter name , and 10 indicates that MQ was called in dynamic registration mode but cannot find the ax_reg and ax_unreg functions ! Either call MQ in non-dynamic registration mode or supply the correct library name via the AXLIB parameter in the xa_open string. Response: Correct the error and try the operation again. AMQ5204A non-threaded application tried to run as a Trusted application. Severity: 10 : Warning Explanation: Only applications linked with the threaded MQ libraries can run as Trusted applications. Response: Make sure that the application is relinked with the threaded MQ libraries, or set the the environment variable MQ_CONNECT_TYPE to STANDARD. AMQ5205File or directory not owned by user . Severity: 40 : Stop Error Explanation: WebSphere MQ has detected that the file or directory is not owned by the user . This is not necessarily an error but you should investigate further if this is unexpected. Response: If this is unexpected then you should alter the ownership of the file or directory back to the user . If this is expected, then WebSphere MQ will continue however WebSphere MQ will be unable to verify the security of this file or directory. If the access permissions are too strict then you may encounter problems if WebSphere MQ cannot access the contents of the file or directory. If the access permissions are too relaxed then there may be an increased risk to the security of the WebSphere MQ system. AMQ5206Duplicate parameters detected. Severity: 10 : Warning Explanation: WebSphere MQ has detected that the activity about to be displayed contains two or more parameters in the same group with the same parameter identifier. The activity may be displayed incorrectly. Response: Inform the author of the activity that there may be an error in it. AMQ5358WebSphere MQ could not load AX support module . Severity: 20 : Error Explanation: An error has occurred loading the AX support module . This module needs to be loaded so that dynamically-registering resource managers, such as DB2, can participate in global units of work. Response: Look for a previous message outlining the reason for the load failure. Message AMQ6175 should have been issued if the load failed because of a system error. If this is the case then follow the guidance given in message AMQ6175 to resolve the problem. In the absence of prior messages or FFST information related to this problem check that the AX support module and the mqmax library have been correctly installed on your system. AMQ5501There was not enough storage to satisfy the request Severity: 20 : Error Explanation: An internal function of the product attempted to obtain storage, but there was none available. Response: Stop the product and restart it. If this does not resolve the problem, save the generated output files and contact your IBM support center. AMQ5502The CDS directory name is not in the correct format. Severity: 20 : Error Explanation: An internal function of the DCE Naming service found a CDS directory name in the wrong format. The name was expected to start with either '/...' for a fully qualified name (from global root), or '/.:' for a partially qualified name (from local cell root). Response: Save the generated output files and contact your IBM support center. AMQ5503The name of the local DCE cell cannot be determined, status = Severity: 20 : Error Explanation: The DCE Naming Service attempted to determine the name of the local DCE cell by calling 'dce_cf_get_cell_name()', which returned a nonzero return code. Response: Save the generated output files and contact your IBM support center. AMQ5504DCE error. No value for the XDS attribute found. Severity: 20 : Error Explanation: The DCE Naming service called om_get() to get the entry from the object returned by ds_read(). Although the status was correct, no objects were returned. Response: Save the generated output files and contact your IBM support center. AMQ5505DCE error. No value for the XDS attribute number found. Severity: 20 : Error Explanation: The DCE Naming service called om_get() to get the entry from the object returned by ds_read(). Although the status was correct, no objects were returned. Response: Save the generated output files and contact your IBM support center. AMQ5506DCE error. returned for attribute number . Severity: 20 : Error Explanation: The DCE Naming service queried an object by calling which returned a nonzero return code. Response: Save the generated output files and contact your IBM support center. AMQ5507DCE error. failed for an unknown reason. Severity: 20 : Error Explanation: An unexpected error occurred in an internal function of the DCE Naming service. Response: Save the generated output files and contact your IBM support center. AMQ5508DCE error. The requested attribute is not present. Severity: 20 : Error Explanation: The DCE Naming service was attempting to extract the value from an attribute, but the attribute cannot be found in the XDS object. Response: Save the generated output files and contact your IBM support center. AMQ5509DCE error. The XDS workspace cannot be initialized. Severity: 20 : Error Explanation: The DCE Naming service called 'ds_initialize()' to initialize the XDS workspace, but 'ds_initialize()' returned a nonzero return code. Response: Save the generated output files and contact your IBM support center. AMQ5510DCE error. returned with problem . Severity: 20 : Error Explanation: The DCE Naming service found an unexpected XDS error. Response: Save the generated output files and contact your IBM support center. AMQ5511Installable service component returned . Severity: 20 : Error Explanation: The internal function, that adds a component to a service, called the component initialization process. This process returned an error. Response: Check the component was installed correctly. If it was, and the component was supplied by IBM, then save the generated output files and contact your IBM support center. If the component was not supplied by IBM, save the generated output files and follow the support procedure for that component. AMQ5511 (iSeries)An installable service component returned an error. Severity: 20 : Error Explanation: Installable service component returned . The internal function, that adds a component to a service, called the component initialization process. This process returned an error. Response: Check the component was installed correctly. If it was, and the component was supplied by IBM, then save the generated output files and contact your IBM support center. If the component was not supplied by IBM, save the generated output files and follow the support procedure for that component. AMQ5512Installable service component returned for queue manager name = . Severity: 20 : Error Explanation: An installable service component returned an unexpected return code. Response: Check the component was installed correctly. If it was, and the component was supplied by IBM, then save the generated output files and contact your IBM support center. If the component was not supplied by IBM, save the generated output files and follow the support procedure for that component. AMQ5512 (iSeries)An installable service component returned an unexpected return code. Severity: 20 : Error Explanation: Installable service component returned for queue manager name = . Response: Check the component was installed correctly. If it was, and the component was supplied by IBM, then save the generated output files and contact your IBM support center. If the component was not supplied by IBM, save the generated output files and follow the support procedure for that component. AMQ5513 returned . Severity: 20 : Error Explanation: An unexpected error occurred. Response: Save the generated output files and contact your IBM support center. AMQ5519Bad DCE identity. Status = , auth = , keytab file = , principal = . Severity: 20 : Error Explanation: The keytab file was not installed correctly, or the WebSphere MQ user ID has a different password from that used to create the keytab file. Response: Make sure that the MQ user ID defined when the product was installed has the same password as that defined by the keytab file, and that the keytab file has been installed correctly. AMQ5519 (iSeries)Bad DCE identity. Severity: 20 : Error Explanation: Status = , auth = , keytab file = , principal = . The keytab file was not installed correctly, or the WebSphere MQ user ID has a different password from that used to create the keytab file. Response: Make sure that the MQ user ID defined when the product was installed has the same password as that defined by the keytab file, and that the keytab file has been installed correctly. AMQ5520The system could not load the module for the installable service component . The system return code was . The Queue Manager is continuing without this component. Severity: 10 : Warning Explanation: The queue manager configuration data included a stanza for the installable service component with the module . The system returned when it tried to load this module. The Queue Manager is continuing without this component. Response: Make sure that the module can be loaded. Put the module into a directory where the system can load it, and specify its full path and name in the configuration data . Then stop and restart the queue manager. AMQ5520 (iSeries)The system could not load a module. The Queue Manager is continuing without this component. Severity: 10 : Warning Explanation: The queue manager configuration data included a stanza for the installable service component with the module . The system returned when it tried to load this module. The Queue Manager is continuing without this component. Response: Make sure that the module can be loaded. Put the module into a directory where the system can load it, and specify its full path and name in the configuration data . Then stop and restart the queue manager. AMQ5521The system could not open "". Severity: 10 : Warning Explanation: The system failed to open the default object "" at connect time for reason . This may be because "" has been deleted or changed. Response: Recreate the default objects by running "strmqm -c " (where is the name of the queue manager) and retry the application. AMQ5522A WebSphere MQ installable service component could not be initialized. Severity: 20 : Error Explanation: An installable service component returned an unexpected return code. Response: Check the queue manager error logs for messages explaining which installable service could not be initialized and why that service could not be initialized. Check the component was installed correctly. If it was, and the component was supplied by IBM, then save the generated output files and contact your IBM support center. If the component was not supplied by IBM, save the generated output files and follow the support procedure for that component. AMQ5524The WebSphere MQ Object Authority Manager has failed to migrate authority data. Severity: 20 : Error Explanation: The Object Authority Manager has attempted to migrate existing queue manager authority data from a previous version of an Object Authority Manager and failed. Response: Check this log for any previous related messages, follow their recommendations then restart the queue manager. AMQ5525The WebSphere MQ Object Authority Manager has failed. Severity: 20 : Error Explanation: The Object Authority Manager has failed to complete an MQ request. Response: Check the queue manager error logs for messages explaining the failure and try to correct the problem accordingly. AMQ5526The WebSphere MQ Object Authority Manager has failed with reason Severity: 20 : Error Explanation: The Object Authority Manager has failed an operation on the Object Authority Manager's data queue with reason . Response: Investigate why the error has occured and correct the problem. AMQ5527The WebSphere MQ Object Authority Manager has failed to locate an essential authority file Severity: 20 : Error Explanation: The Object Authority Manager has failed to locate the authority file . The migration of authority data cannot continue until the file has been restored. The queue manager will shutdown. Response: Restore the authority file mentioned above and restart the queue manager. AMQ5528The WebSphere MQ Object Authority Manager has failed to locate an object's authority file Severity: 20 : Error Explanation: The Object Authority Manager has failed to locate the authority file for the object of type (). The authority access to this object will initially be limited to members of the mqm group. Where type is one of the following: 1) Queue 2) Namelist 3) Process 5) Queue Manager Response: To extend access to this object use the setmqaut command, see the WebSphere MQ System Administration documentation for details. AMQ5529The Remote OAM Service is not available. Severity: 20 : Error Explanation: The Remote OAM service is not available. The call returned , errno : . The context string is Response: To extend access to this object use the setmqaut command, see the WebSphere MQ System Administration documentation for details. AMQ5600Usage: crtmqm [-z] [-q] [-c Text] [-d DefXmitQ] [-h MaxHandles] [-g ApplicationGroup] Severity: 0 : Information Explanation: This shows the correct usage. Response: None. AMQ5601[-t TrigInt] [-u DeadQ] [-x MaxUMsgs] [-lp LogPri] [-ls LogSec] Severity: 0 : Information Response: None. AMQ5602[-lc | -ll] [-lf LogFileSize] [-ld LogPath] QMgrName Severity: 0 : Information Explanation: This shows the correct usage. Response: None. AMQ5602 (iSeries)[-ll] [-lf LogFileSize] [-ld LogPath] [-lz ASPNum] QMgrName Severity: 0 : Information Explanation: This shows the correct usage. Response: None. AMQ5603Usage: dltmqm [-z] QMgrName Severity: 0 : Information Explanation: This shows the correct usage. Response: None. AMQ5604Usage: dspmqaut [-m QMgrName] [-n ObjName] -t ObjType (-p Principal | -g Group) [-s ServiceComponent] Severity: 0 : Information Response: None. AMQ5605Usage: endmqm [-z] [-c | -w | -i | -p] QMgrName Severity: 0 : Information Explanation: This shows the correct usage. Response: None. AMQ5606Usage: setmqaut [-m QMgrName] [-n ObjName] -t ObjType (-p Principal | -g Group) [-s ServiceComponent] Authorizations Severity: 0 : Information Response: None. AMQ5607Usage: strmqm [-a|-c|-r][-d none|minimal|all][-z][-ns] [QMgrName] Severity: 0 : Information Explanation: This shows the correct usage. Response: None. AMQ5608Usage: dspmqtrn [-m QMgrName] [-e] [-i] Severity: 0 : Information Explanation: This shows the correct usage. Response: None. AMQ5609Usage: rsvmqtrn -m QMgrName (-a | ((-b | -c | -r RMId) Transaction,Number)) Severity: 0 : Information Explanation: This shows the correct usage. Response: None. AMQ5610 (iSeries)Usage: strmqtrc [-m QMgrName] [-e] [-t TraceType] [-o mqm|pex|all] [-x TraceType] [-l MaxFileSize] [-d UserDataSize] Severity: 0 : Information Explanation: None. Response: None. AMQ5610 (Unix)Usage: strmqtrc [-m QMgrName] [-e] [-t TraceType] [-x TraceType] [-l MaxFileSize] [-d UserDataSize] Severity: 0 : Information Explanation: This applies to UNIX systems. MaxFileSize is the maximum size of a trace file in millions of bytes. UserDataSize is the size of user data to be traced in bytes. Response: None. AMQ5610 (Windows)Usage: strmqtrc [-t TraceType] [-x TraceType] [-l MaxFileSize] [-d UserDataSize] Severity: 0 : Information Explanation: This applies to Windows NT and Windows 2000 systems only. MaxFileSize is the maximum size of a trace file in millions of bytes. UserDataSize is the size of user data to be traced in bytes. Response: None. AMQ5611 (Unix)Usage: endmqtrc [-m QMgrName] [-e] [-a] Severity: 0 : Information Explanation: This applies to UNIX systems. Response: None. AMQ5611 (Windows)Usage: endmqtrc Severity: 0 : Information Explanation: This applies to Windows NT and Windows 2000 systems only. Response: None. AMQ5612Usage: dspmqtrc [-t TemplateFile] [-hs] [-o OutputFileName] [-C InputFileCCSID] InputFileName(s) Severity: 0 : Information Explanation: Options: -t Template file for formatting trace data -h Skip the trace file header -s Summary (format only the trace header) -o Save trace output to file -C Specifies the CCSID value for the input file Response: None. AMQ5613Usage: dspmq [-m QMgrName] [-o status | -s] [-o default] Severity: 0 : Information AMQ5614Usage: setmqtry Severity: 0 : Information Explanation: This shows the correct usage. Response: None. AMQ5615Default objects cannot be created: CompCode = Reason = . Severity: 20 : Error Explanation: During the creation of a queue manager, using the crtmqm command, the default objects could not be created. Possible reasons for this include another command, issued elsewhere, quiescing or stopping the queue manager, or insufficient storage being available. Response: Use the Completion and Reason codes shown in the message to determine the cause of the failure, then re-try the command. AMQ5616Usage: setmqprd LicenseFile Severity: 0 : Information Explanation: This shows the correct usage. Response: None. AMQ5617Default objects cannot be created. Severity: 20 : Error Explanation: During the creation of a queue manager using the crtmqm command, the default objects could not be created. The most likely reason for this error is that the queue manager was started before the crtmqm command had completed. Response: Ensure that the queue manager being created is not started before the create request completes. Stop the queue manager if it is already running. Restart the queue manager using the strmqm command with the '-c' option to request that the default objects are created. AMQ5618integer Severity: 0 : Information AMQ5619string Severity: 0 : Information AMQ5620channel_name Severity: 0 : Information AMQ5621process_name Severity: 0 : Information AMQ5622q_name Severity: 0 : Information AMQ5623connection_name Severity: 0 : Information AMQ5624generic_channel_name Severity: 0 : Information AMQ5625generic_process_name Severity: 0 : Information AMQ5626generic_q_name Severity: 0 : Information AMQ5627qalias_name Severity: 0 : Information AMQ5628qmodel_name Severity: 0 : Information AMQ5629qlocal_name Severity: 0 : Information AMQ5630qremote_name Severity: 0 : Information AMQ5631namelist_name Severity: 0 : Information AMQ5632generic_namelist_name Severity: 0 : Information AMQ5633generic_Q_Mgr_name Severity: 0 : Information AMQ5634generic_cluster_name Severity: 0 : Information AMQ5635The argument supplied with the -l flag is not valid. Severity: 20 : Error Explanation: The argument supplied with the -l flag must be in the range 1 - 4293. Response: Submit the command again with a valid argument. AMQ5636cluster_name Severity: 0 : Information AMQ5637 (AIX)The environment variable EXTSHM is set to "ON". This is incompatable with the way WebSphere MQ uses shared memory. Reset the environment variable EXTSHM and retry the command. Severity: 20 : Error Explanation: On AIX the environment variable EXTSHM causes shared memory segments to be fixed size. WebSphere MQ expects to be able to extend shared memory segments. Response: Reset the environment variable EXTSHM and retry the command. AMQ5646Usage: setmqcap Processors Severity: 0 : Information AMQ5647Usage: dspmqcap Severity: 0 : Information AMQ5648Usage: dmpmqaut [-m QMgrName] [-n Profile | -l] [-t ObjType] [-p Principal | -g Group] [-s ServiceComponent] [-e | -x] Severity: 0 : Information Response: None. AMQ5649generic_authinfo_name Severity: 0 : Information AMQ5650authinfo_name Severity: 0 : Information AMQ5651qmname Severity: 0 : Information AMQ5652The Deferred Message process failed to connect to the WebSphere MQ queue manager for reason . Severity: 30 : Severe error Explanation: The WebSphere MQ queue manager might have generated earlier messages or FFST information explaining why the deferred message process (amqzdmaa) could not connect. Response: Correct any configuration errors. Configuration errors that can cause this problem include badly configured CLWL Exit modules. If the problem persists contact your IBM service representative. AMQ5653The mqm user is not defined. Severity: 30 : Severe error Explanation: The system call getpwnam("mqm") failed with errno . The program was running as . Response: Create the mqm user as a member of the mqm group and retry the operation. AMQ5654Usage: dspmqrte [-c] [-n] [-l Persistence] [-m QMgrName] [-o] [-p Priority] Severity: 0 : Information Explanation: This shows the correct usage of the DSPMQRTE command. Response: None. AMQ5655[-rq ReplyQName [-rqm ReplyQMgrName]] [-ro ReportOptions] Severity: 0 : Information Explanation: This shows the correct usage of the DSPMQRTE command. Response: None. AMQ5656[-xs Expiry] [-xp Pass] [-qm TargetQMgrName] [-ac [-ar]] Severity: 0 : Information Explanation: This shows the correct usage of the DSPMQRTE command. Response: None. AMQ5657[-d Delivery] [-f Forwarding] [-s Activities] [-t Detail] Severity: 0 : Information Explanation: This shows the correct usage of the DSPMQRTE command. Response: None. AMQ5658[-i CorrelId] [-b] [-v Verbosity] [-w WaitTime] -q TargetQName Severity: 0 : Information Explanation: This shows the correct usage of the DSPMQRTE command. Response: None. AMQ5700listener_name Severity: 0 : Information AMQ5701service_name Severity: 0 : Information AMQ5749display_cmd Severity: 0 : Information AMQ5750filter_keyword Severity: 0 : Information AMQ5751operator Severity: 0 : Information AMQ5752filter_value Severity: 0 : Information AMQ5805WebSphere MQ Publish/Subscribe broker currently running for queue manager. Severity: 10 : Warning Explanation: The command was unsuccessful because queue manager currently has an WebSphere MQ Publish/Subscribe broker running. Response: None. AMQ5806WebSphere MQ Publish/Subscribe broker started for queue manager . Severity: 0 : Information Explanation: WebSphere MQ Publish/Subscribe broker started for queue manager . Response: None. AMQ5807WebSphere MQ Publish/Subscribe broker for queue manager ended. Severity: 0 : Information Explanation: The WebSphere MQ Publish/Subscribe broker on queue manager has ended. Response: None. AMQ5808WebSphere MQ Publish/Subscribe broker for queue manager is already quiescing. Severity: 10 : Warning Explanation: The endmqbrk command was unsuccessful because an orderly shutdown of the WebSphere MQ Publish/Subscribe broker running on queue manager is already in progress. Response: None. AMQ5808 (iSeries)WebSphere MQ Publish/Subscribe broker is already quiescing. Severity: 10 : Warning Explanation: The endmqbrk command was unsuccessful because an orderly shutdown of the broker, running on queue manager , is already in progress. Response: None. AMQ5809WebSphere MQ Publish/Subscribe broker for queue manager starting. Severity: 0 : Information Explanation: The dspmqbrk command has been issued to query the state of the WebSphere MQ Publish/Subscribe broker. The WebSphere MQ Publish/Subscribe broker is currently initializing. Response: None. AMQ5810WebSphere MQ Publish/Subscribe broker for queue manager running. Severity: 0 : Information Explanation: The dspmqbrk command has been issued to query the state of the WebSphere MQ Publish/Subscribe broker. The WebSphere MQ Publish/Subscribe broker is currently running. Response: None. AMQ5811WebSphere MQ Publish/Subscribe broker for queue manager quiescing. Severity: 0 : Information Explanation: The dspmqbrk command has been issued to query the state of the WebSphere MQ Publish/Subscribe broker. The WebSphere MQ Publish/Subscribe broker is currently performing a controlled shutdown. Response: None. AMQ5812WebSphere MQ Publish/Subscribe broker for queue manager stopping. Severity: 0 : Information Explanation: Either the dspmqbrk command or the endmqbrk command has been issued. The WebSphere MQ Publish/Subscribe broker is currently performing an immediate shutdown. If the endmqbrk command has been issued to request that the broker terminate, the command is unsuccessful because the broker is already performing an immediate shutdown. Response: None. AMQ5813WebSphere MQ Publish/Subscribe broker for queue manager not active. Severity: 0 : Information Explanation: An WebSphere MQ Publish/Subscribe broker administration command has been issued to query or change the state of the broker. The WebSphere MQ Publish/Subscribe broker is not currently running. Response: None. AMQ5814WebSphere MQ Publish/Subscribe broker for queue manager ended abnormally. Severity: 0 : Information Explanation: The dspmqbrk command has been issued to query the state of the WebSphere MQ Publish/Subscribe broker. The WebSphere MQ Publish/Subscribe broker has ended abnormally. Response: Refer to the queue manager error logs to determine why the broker ended abnormally. AMQ5815Invalid WebSphere MQ Publish/Subscribe broker initialization file stanza for queue manager (). Severity: 20 : Error Explanation: The broker was started using the strmqbrk command. The broker stanza in the queue manager initialization file is not valid. The broker will terminate immediately. The invalid attribute is . Response: Correct the broker stanza in the queue manager initialization file. AMQ5815 (iSeries)Invalid WebSphere MQ Publish/Subscribe broker initialization file stanza. Severity: 20 : Error Explanation: The broker was started using the strmqbrk command. The Broker stanza in the queue manager() initialization file is not valid. The broker will terminate immediately. The invalid attribute is . Response: Correct the Broker stanza in the queue manager initialization file. AMQ5815 (Windows)The WebSphere MQ Publish/Subscribe broker configuration for queue manager () is not valid. Severity: 20 : Error Explanation: The broker was started using the strmqbrk command. The broker configuration information is not valid. The broker will terminate immediately. The invalid attribute is . Response: Correct the broker attribute using the cfgmqbrk configuration tool. AMQ5816Unable to open WebSphere MQ Publish/Subscribe broker control queue for reason ,. Severity: 20 : Error Explanation: The broker has failed to open the broker control queue (). The attempt to open the queue failed with completion code and reason . The most likely reasons for this error are that an application program has opened the broker control queue for exclusive access, or that the broker control queue has been defined incorrectly. The broker will terminate immediately. Response: Correct the problem and restart the broker. AMQ5817An invalid stream queue has been detected by the broker. Severity: 10 : Warning Explanation: WebSphere MQ has detected an attempt to use a queue () as a stream queue, but the attributes of the queue make it unsuitable for use as a stream queue. The most likely reason for this error is that the queue is: (1) Not a local queue; (2) A shareable queue; (3) A temporary dynamic queue. If the queue was created using implicit stream creation, the model stream might have been defined incorrectly. The message that caused the stream to be created will be rejected or put to the dead-letter queue, depending upon the message report options and broker configuration. Response: Correct the problem and resubmit the request. AMQ5818Unable to open WebSphere MQ Publish/Subscribe broker stream queue. Severity: 10 : Warning Explanation: The broker has failed to open a stream queue (). The attempt to open the queue failed with completion code and reason . The most likely reason for this error is that an application has the queue open for exclusive access. The stream will be temporarily shut down and an attempt will be made to restart the stream after a short interval. Response: Correct the problem. AMQ5819An WebSphere MQ Publish/Subscribe broker stream has ended abnormally. Severity: 10 : Warning Explanation: The broker stream () has ended abnormally for reason . The broker will attempt to restart the stream. If the stream should repeatedly fail then the broker will progressively increase the time between attempts to restart the stream. Response: Investigate why the problem occurred and take appropriate action to correct the problem. If the problem persists, contact your IBM service representative. AMQ5820WebSphere MQ Publish/Subscribe broker stream () restarted. Severity: 0 : Information Explanation: The broker has restarted a stream that ended abnormally. This message will frequently be preceded by message AMQ5867 or AMQ5819 indicating why the stream ended. Response: Correct the problem. AMQ5821WebSphere MQ Publish/Subscribe broker unable to contact parent broker. Severity: 10 : Warning Explanation: The broker has been started specifying a parent broker. The broker has been unable to send a message to the parent broker () for reason . The broker will terminate immediately. Response: Investigate why the problem occurred and take appropriate action to correct the problem. The problem is likely to be caused by the parent broker name not resolving to the name of a transmission queue on the local broker. AMQ5822WebSphere MQ Publish/Subscribe broker failed to register with parent broker. Severity: 10 : Warning Explanation: The broker has been started specifying a parent broker (). The broker attempted to register as a child of the parent broker, but received an exception response () indicating that this was not possible. The broker will attempt to reregister as a child of the parent periodically. The child might not be able to process global publications or subscriptions correctly until this registration process has completed normally. Response: Investigate why the problem occurred and take appropriate action to correct the problem. The problem is likely to be caused by the parent broker not yet existing, or a problem with the SYSTEM.BROKER.INTER.BROKER.COMMUNICATIONS queue at the parent broker. AMQ5823Exit path attribute invalid in WebSphere MQ Publish/Subscribe broker stanza. Severity: 10 : Warning Explanation: The broker exit path attribute is not valid. The attribute should be specified as: (). The broker will terminate immediately. Response: Correct the problem with the attribute and restart the broker. AMQ5824WebSphere MQ Publish/Subscribe broker exit module could not be loaded. Severity: 10 : Warning Explanation: The broker exit module could not be loaded for reason :. The broker will terminate immediately. Response: Correct the problem with the broker exit module and restart the broker. AMQ5825The address of the WebSphere MQ Publish/Subscribe broker exit function could not be found. Severity: 10 : Warning Explanation: The address of the broker exit function could not be found in module for reason :. The broker will terminate immediately. Response: Correct the problem with the broker exit function in module , and restart the broker. AMQ5826The WebSphere MQ Publish/Subscribe broker has failed to propagate a subscription to another broker. Severity: 10 : Warning Explanation: The broker failed to propagate subscription to stream () at broker (). Reason codes and . An application has either registered or deregistered a global subscription to stream (). The broker has attempted to propagate the subscription change to broker () but the request has not been successful. The message broker will immediately attempt to refresh the state of the global subscriptions for stream () at broker (). Until the subscription state has been successfully refreshed, messages published on stream () through broker () might not reach this broker. Response: Use the reason codes to investigate why the problem occurred and take appropriate action to correct the problem. AMQ5827An WebSphere MQ Publish/Subscribe broker internal subscription has failed. Severity: 10 : Warning Explanation: The broker failed to subscribe to stream () at broker () with reason codes and . Related brokers learn about each others configuration by subscribing to information published by each other. A broker has discovered that one of these internal subscriptions has failed. The broker will reissue the subscription immediately. The broker cannot function correctly without knowing some information about neighboring brokers. The information that this broker has about broker () is not complete and this could lead to subscriptions and publications not being propagated around the network correctly. Response: Investigate why the problem occurred and take appropriate action to correct the problem. The most likely cause of this failure is a problem with the SYSTEM.BROKER.CONTROL.QUEUE at broker (), or a problem with the definition of the route between this broker and broker (). AMQ5828WebSphere MQ Publish/Subscribe broker exit returned an ExitResponse that is not valid. Severity: 10 : Warning Explanation: The broker exit returned an ExitResponse that is not valid. The message has been allowed to continue and an FFST has been generated that contains the entire exit parameter structure. Response: Correct the problem with the broker exit. AMQ5829Usage: [-m QMgrName] [-p ParentQMgrName] Severity: 0 : Information Explanation: This shows the correct usage. Response: None. AMQ5830Usage: endmqbrk [-c | -i] [-m QMgrName] Severity: 0 : Information Explanation: This shows the correct usage. Response: None. AMQ5831Usage: dspmqbrk [-m QMgrName] Severity: 0 : Information Explanation: This shows the correct usage. Response: None. AMQ5832WebSphere MQ Publish/Subscribe broker failed to publish configuration information on SYSTEM.BROKER.ADMIN.STREAM. Severity: 10 : Warning Explanation: Related brokers learn about each others configuration by subscribing to information published by each other. A broker has discovered that one of these internal publications has failed. The broker will republish the information immediately. Brokers cannot function correctly without knowing some information about neighboring brokers. The information that neighboring brokers have of this broker might not be complete and this could lead to some subscriptions and publications not being propagated around the network. Response: Investigate why the problem occurred and take appropriate action to correct the problem. AMQ5833A loop has been detected in the WebSphere MQ Publish/Subscribe broker hierarchy. Severity: 20 : Error Explanation: The broker, on queue manager (), introduced a loop in the broker hierarchy. This broker will terminate immediately. Response: Remove broker () from the hierarchy, either by deleting the broker, or by removing knowledge of the broker's parent, using the clrmqbrk command. AMQ5834Conflicting queue manager names in the WebSphere MQ Publish/Subscribe broker hierarchy. Severity: 10 : Warning Explanation: The names of the queue managers () and () in the broker hierarchy both start with the same 12 characters. The first 12 characters of a broker's queue manager name should be unique to ensure that no confusion arises within the broker hierarchy, and to guarantee unique message ID allocation. Response: Use a queue manager naming convention that guarantees uniqueness of the first 12 characters of the queue manager name. AMQ5835WebSphere MQ Publish/Subscribe broker failed to inform its parent of a relation for reason . Severity: 0 : Information Explanation: The failed to notify its parent on queue manager () of the relation () in the broker hierarchy. The notification message will be put to the parent's dead-letter queue. A failure to notify a broker of a new relation will mean that no loop detection can be performed for the new relation. Response: Diagnose and correct the problem on the parent queue manager. One possible reason for this is that the parent broker does not yet exist. AMQ5836Duplicate queue manager name located in the WebSphere MQ Publish/Subscribe hierarchy. Severity: 0 : Information Explanation: Multiple instances of the queue manager name () have been located. This could either be the result of a previously resolved loop in the broker hierarchy, or multiple queue managers in the broker hierarchy having the same name. Response: If this broker introduced a loop in the hierarchy (typically identified by message AMQ5833), this message can be ignored. It is strongly recommended that every queue manager in a broker hierarchy has a unique name. It is not recommended that multiple queue managers use the same name. AMQ5837WebSphere MQ Publish/Subscribe broker failed to quiesce queue () for reason . Severity: 10 : Warning Explanation: When a broker is deleted, the broker's input queues are quiesced by making the queue get inhibited, and writing the contents of the queue to the dead-letter queue (depending upon the report options of the message). The broker was unable to quiesce the named queue for the reason shown. The attempt to delete the broker will fail. Response: Investigate why the problem occurred, take appropriate action to correct the problem, and reissue the dltmqbrk command. Likely reasons include the queue being open for input by another process, there being no dead-letter queue defined at this queue manager, or the operator setting the queue to get inhibited while the dltmqbrk command is running. If there is no dead-letter queue defined, the reason will be reported as MQRC_UNKNOWN_OBJECT_NAME. If the problem occurs because there is no dead-letter queue defined at this broker, the operator can either define a dead-letter queue, or manually empty the queue causing the problem. AMQ5837 (iSeries)WebSphere MQ Publish/Subscribe broker failed to quiesce queue. Severity: 10 : Warning Explanation: When a broker is deleted, the broker's input queues are quiesced by making the queue get inhibited, and writing the contents of the queue to the dead-letter queue (depending upon the report options of the message). The broker was unable to quiesce the queue () for reason . The attempt to delete the broker will fail. Response: Investigate why the problem occurred, take appropriate action to correct the problem, and reissue the dltmqbrk command. Likely reasons include the queue being open for input by another process, there being no dead-letter queue defined at this queue manager, or the operator setting the queue to get inhibited while the dltmqbrk command is running. If there is no dead-letter queue defined, the reason will be reported as MQRC_UNKNOWN_OBJECT_NAME. If the problem occurs because there is no dead-letter queue defined at this broker, the operator can either define a dead-letter queue, or manually empty the queue causing the problem. AMQ5838WebSphere MQ Publish/Subscribe broker cannot be deleted. Severity: 10 : Warning Explanation: The broker cannot be deleted as child () is still registered. A broker cannot be deleted until all other brokers that have registered as children of that broker, have deregistered as its children. Response: Use the clrmqbrk and dltmqbrk commands to change the broker topology so that broker () is not registered as a child of the broker being deleted. AMQ5839WebSphere MQ Publish/Subscribe broker received an unexpected inter-broker communication. Severity: 10 : Warning Explanation: A broker has received an inter-broker communication that it did not expect. The message was sent by broker (). The message will be processed according to the report options in that message. The most likely reason for this message is that the broker topology has been changed while inter-broker communication messages were in transit (for example, on a transmission queue) and that a message relating to the previous broker topology has arrived at a broker in the new topology. This message may be accompanied by an informational FFST including details of the unexpected communication. Response: If the broker topology has changed and the broker named in the message is no longer related to the broker issuing this message, this message can be ignored. If the clrmqbrk command was issued to unilaterally remove knowledge of broker () from this broker, the clrmqbrk command should also be used to remove knowledge of this broker from broker (). If the clrmqbrk command was issued to unilaterally remove knowledge of this broker from broker (), the clrmqbrk command should also be used to remove knowledge of broker () at this broker. AMQ5840WebSphere MQ Publish/Subscribe broker unable to delete queue. Severity: 10 : Warning Explanation: The broker has failed to delete the queue () for reason . The broker typically attempts to delete queues during dltmqbrk processing, in which case the dltmqbrk command will fail. Response: The most likely reason for this error is that some other process has the queue open. Determine why the queue cannot be deleted, remove the inhibitor, and retry the failed operation. In a multi-broker environment, it is likely that a message channel agent might have queues open, which the broker needs to delete for a dltmqbrk command to complete. AMQ5841WebSphere MQ Publish/Subscribe broker () deleted. Severity: 0 : Information Explanation: The broker () has been deleted using the dltmqbrk command. Response: None. AMQ5842WebSphere MQ Publish/Subscribe broker () cannot be deleted for reason :. Severity: 20 : Error Explanation: An attempt has been made to delete the broker () but the request has failed for reason :. Response: Determine why the dltmqbrk command cannot complete successfully. The message logs for the queue manager might contain more detailed information on why the broker cannot be deleted. Resolve the problem that is preventing the command from completing and reissue the dltmqbrk command. AMQ5842 (iSeries)WebSphere MQ Publish/Subscribe broker cannot be deleted. Severity: 20 : Error Explanation: An attempt has been made to delete the WebSphere MQ Publish/Subscribe broker () but the request has failed for reason :. Response: Determine why the dltmqbrk command cannot complete successfully. The message logs for the queue manager might contain more detailed information on why the broker cannot be deleted. Resolve the problem that is preventing the command from completing and reissue the dltmqbrk command. AMQ5843WebSphere MQ Publish/Subscribe broker () cannot be started as it is partially deleted. Severity: 10 : Warning Explanation: An attempt has been made to start a broker that is in a partially deleted state. An earlier attempt to delete the broker has failed. The broker deletion must be completed before the broker will be allowed to restart. When broker deletion is successful, message AMQ5841 is issued, indicating that the broker has been deleted. If this message is not received on completion of a dltmqbrk command, the broker deletion has not been completed and the command will have to be reissued. Response: Investigate why the earlier attempt to delete the broker failed. Resolve the problem and reissue the dltmqbrk command. AMQ5843 (iSeries)WebSphere MQ Publish/Subscribe broker cannot be started as it is partially deleted. Severity: 10 : Warning Explanation: An attempt has been made to start the broker that is in a partially deleted state. An earlier attempt to delete the broker has failed. The broker deletion must be completed before the broker will be allowed to restart. When broker deletion is successful, message AMQ5841 is issued, indicating that the broker has been deleted. If this message is not received on completion of a dltmqbrk command, the broker deletion has not been completed and the command will have to be reissued. Response: Investigate why the earlier attempt to delete the broker failed. Resolve the problem and reissue the dltmqbrk command. AMQ5844The relation between two WebSphere MQ Publish/Subscribe brokers is unknown. Severity: 10 : Warning Explanation: The clrmqbrk command has been issued in an attempt to remove a brokers knowledge of a relation of that broker. The relative () is unknown at broker (). If the "-p" flag was specified, the broker does not currently have a parent. If the "-c" flag was specified, the broker does not recognize the named child. Response: Investigate why the broker is unknown. AMQ5845Usage: dltmqbrk -m QMgrName Severity: 0 : Information Explanation: This shows the correct usage. Response: None. AMQ5846Usage: clrmqbrk -p | -c ChildQMgrName -m QMgrName Severity: 0 : Information Explanation: This shows the correct usage. Response: None. AMQ5847WebSphere MQ Publish/Subscribe broker () has removed knowledge of relation (). Severity: 0 : Information Explanation: The clrmqbrk command has been used to remove knowledge of broker () from broker (). Response: None. AMQ5847 (iSeries)WebSphere MQ Publish/Subscribe broker relation removed. Severity: 0 : Information Explanation: The clrmqbrk command has been used to remove knowledge of broker () from broker (). Response: None. AMQ5848WebSphere MQ Publish/Subscribe broker () has failed to remove references to relation () for reason :. Severity: 20 : Error Explanation: An attempt has been made to remove references to broker () from broker () using the clrmqbrk command, but the request has been unsuccessful. Response: Determine why the clrmqbrk command cannot complete successfully. The message logs for the queue manager might contain more detailed information on why the broker cannot be deleted. Resolve the problem that is preventing the command from completing and then reissue the clrmqbrk command. AMQ5848 (iSeries)WebSphere MQ Publish/Subscribe broker has failed to remove references to a related broker. Severity: 20 : Error Explanation: An attempt has been made to remove references to broker () from broker () using the clrmqbrk command, but the request has been unsuccessful for reason :. Response: Determine why the clrmqbrk command cannot complete successfully. The message logs for the queue manager might contain more detailed information on why the broker cannot be deleted. Resolve the problem that is preventing the command from completing and then reissue the clrmqbrk command. AMQ5849WebSphere MQ Publish/Subscribe broker may not change parent. Severity: 10 : Warning Explanation: An attempt has been made to start broker (), nominating broker () as its parent. The broker () has previously been started, nominating broker () as its parent. The strmqbrk command cannot be used to change an existing relationship. Response: Do not attempt to change the broker topology by using the strmqbrk command. The dltmqbrk and clrmqbrk commands are the only supported means of changing the broker topology. Refer to the documentation of those commands for guidance on changing the broker topology. AMQ5850WebSphere MQ Publish/Subscribe broker interrupted while creating queue. Severity: 10 : Warning Explanation: The broker was interrupted while creating queue () for user ID (). When the broker creates a queue, it first creates the queue with default security attributes and it then sets the appropriate security attributes for the queue. If the broker should be interrupted during this operation (for example the queue manager is shut down), the broker cannot reliably detect that the security attributes have not been set correctly. The broker was creating a queue, but was interrupted before it could complete creation of the queue and setting the initial authority. If the interrupt occurred before the initial authority of the queue could be set, it might be necessary for the operator to set the appropriate authorities using the setmqaut command. Response: Confirm that the named queue has the appropriate security attributes and modify them as necessary. AMQ5851WebSphere MQ Publish/Subscribe broker interrupted while creating internal queue. Severity: 10 : Warning Explanation: The broker was interrupted while creating internal queue () for user ID (). When the broker creates an internal queue, it first creates the queue with default security attributes and it then sets the appropriate security attributes for the queue. If the broker should be interrupted during this operation (for example the queue manager is shut down), the broker attempts to delete and redefine the queue. If the internal queue is available to users (for example, the default stream or the administration stream), it is possible that a user will put a message on the queue while it is in this invalid state, or that a user application has the queue open. In this situation the broker does not automatically redefine the queue and cannot be restarted until the queue has been emptied or closed. Response: Examine any messages on the named queue and take appropriate action to remove them from the queue. Ensure that no applications have the queue open. AMQ5852WebSphere MQ Publish/Subscribe broker failed to propagate delete publication command. Severity: 0 : Information Explanation: The broker failed to propagate delete publication command for stream () to related broker () for reason . When an application issues a delete publication command to delete a global publication, the command has to be propagated to all brokers in the sub-hierarchy supporting the stream. The broker reporting the error has failed to forward a delete publication command to a related broker () who supports stream (). Delete publication commands are propagated without MQRO_DISCARD_MSG and the command message might have been written to a dead-letter queue. The topic for which the delete publication has failed is (). Response: If the delete publication has failed because the stream has been deleted at the related broker, this message can be ignored. Investigate why the delete publication has failed and take the appropriate action to recover the failed command. AMQ5853WebSphere MQ Publish/Subscribe failed to propagate a delete publication command. Severity: 0 : Information Explanation: The broker failed to propagate a delete publication command for stream () to a previously related broker. When an application issues a delete publication command to delete a global publication, the command is propagated to all brokers in the sub-hierarchy supporting the stream. The broker topology was changed after deleting the publication, but before a broker removed by the topology change processed the propagated delete publication message. The topic for which the delete publication has failed is (). Response: It is the user's responsibility to quiesce broker activity before changing the broker topology using the clrmqbrk command. Investigate why this delete publication activity was not quiesced. The delete publication command will have been written to the dead-letter queue at the broker that was removed from the topology. In this case, further action might be necessary to propagate the delete publication command that was not quiesced before the clrmqbrk command was issued. If this message occurs as a result of the dltmqbrk command, the publication will have been deleted as a result of the dltmqbrk command, and the delete publication message will have been written to the dead-letter queue at the queue manager where the broker was deleted. In this case the delete publication message on the dead-letter queue can be discarded. AMQ5854WebSphere MQ Publish/Subscribe broker failed to propagate a delete publication command. Severity: 0 : Information Explanation: When an application issues a delete publication command to delete a global publication, the command has to be propagated to all brokers in the sub-hierarchy supporting the stream. At the time the delete publication was propagated, broker () was a known relation of this message broker supporting stream (). Before the delete publication command arrived at the related broker, the broker topology was changed so that broker () no longer supported stream (). The topic for which the delete publication has failed is (). Response: It is the user's responsibility to quiesce broker activity before changing the stream topology of the broker. Investigate why this delete publication activity was not quiesced. The delete publication command will have been written to the dead-letter queue at broker (). AMQ5855WebSphere MQ Publish/Subscribe broker ended. Severity: 10 : Warning Explanation: An attempt has been made to run the broker () but the broker has ended for reason :. Response: Determine why the broker ended. The message logs for the queue manager might contain more detailed information on why the broker cannot be started. Resolve the problem that is preventing the command from completing and reissue the strmqbrk command. AMQ5856Broker publish command message cannot be processed. Reason code . Severity: 10 : Warning Explanation: The WebSphere MQ Publish/Subscribe broker failed to process a publish message for stream (). The broker was unable to write the publication to the dead-letter queue and was not permitted to discard the publication. The broker will temporarily stop the stream and will restart the stream and consequently retry the publication after a short interval. Response: Investigate why the error has occurred and why the publication cannot be written to the dead-letter queue. Either manually remove the publication from the stream queue, or correct the problem that is preventing the broker from writing the publication to the dead-letter queue. AMQ5857Broker control command message cannot be processed. Reason code . Severity: 10 : Warning Explanation: The WebSphere MQ Publish/Subscribe broker failed to process a command message on the SYSTEM.BROKER.CONTROL.QUEUE. The broker was unable to write the command message to the dead-letter queue and was not permitted to discard the command message. The broker will temporarily stop the stream and will restart the stream and consequently retry the command message after a short interval. Other broker control commands cannot be processed until this command message has been processed successfully or removed from the control queue. Response: Investigate why the error has occurred and why the command message cannot be written to the dead-letter queue. Either, manually remove the command message from the stream queue, or correct the problem that is preventing the broker from writing the command message to the dead-letter queue. AMQ5858Broker could not send publication to subscriber queue. Severity: 10 : Warning Explanation: A failure has occurred sending a publication to subscriber queue () at queue manager () for reason . The broker configuration options prevent it from recovering from this failure by discarding the publication or by sending it to the dead-letter queue. Instead the broker will back out the unit of work under which the publication is being sent and retry the failing command message a fixed number of times. If the problem still persists, the broker will then attempt to recover by failing the command message with a negative reply message. If the issuer of the command did not request negative replies, the broker will either discard or send to the dead-letter queue the failing command message. If the broker configuration options prevent this, the broker will restart the affected stream, which will reprocess the failing command message again. This behavior will be repeated until such time as the failure is resolved. During this time the stream will be unable to process further publications or subscriptions. Response: Usually the failure will be due to a transient resource problem, for example, the subscriber queue, or an intermediate transmission queue, becoming full. Use reason code to determine what remedial action is required. If the problem persists for a long time, you will notice the stream being continually restarted by the broker. Evidence of this occurring will be a large number of AMQ5820 messages, indicating stream restart, being written to the error logs. In such circumstances, manual intervention will be required to allow the broker to dispose of the failing publication. To do this, you will need to end the broker using the endmqbrk command and restart it with appropriate disposition options. This will allow the publication to be sent to the rest of the subscribers, while allowing the broker to discard or send to the dead-letter queue the publication that could not be sent. AMQ5859WebSphere MQ Publish/Subscribe broker stream is terminating due to an internal resource problem. Severity: 10 : Warning Explanation: The broker stream () has run out of internal resources and will terminate with reason code . If the command in progress was being processed under syncpoint control, it will be backed out and retried when the stream is restarted by the broker. If the command was being processed out of syncpoint control, it will not be able to be retried when the stream is restarted. Response: This message should only be issued in very unusual circumstances. If this message is issued repeatedly for the same stream, and the stream is not especially large in terms of subscriptions, topics, and retained publications, save all generated diagnostic information and contact your IBM Support Center for problem resolution. AMQ5862WebSphere MQ Publish/Subscribe broker for queue manager migrating. Severity: 0 : Information Explanation: The dspmqbrk command has been issued to query the state of the broker. The broker is currently being migrated. Response: None. AMQ5863WebSphere MQ Integrator broker not ready for migration. See message logs for guidance. Severity: 10 : Warning Explanation: The migmqbrk command was unsuccessful because the WebSphere MQ Integrator broker was not ready to accept messages. The state of the WebSphere MQ Publish/Subscribe message broker is exported to the WebSphere MQ Integrator broker in a series of messages sent to queue SYSTEM.BROKER.INTERBROKER.QUEUE. Before migration commences the WebSphere MQ Publish/Subscribe broker checks whether the WebSphere MQ Integrator broker is ready to accept messages on this queue. This check has failed for reason so migration has been abandoned. Response: Reason code should be used to determine the nature of the problem. A value of 1 means that queue SYSTEM.BROKER.INTERBROKER.QUEUE does not exist. This is probably because no WebSphere MQ Integrator broker has been defined yet on this queue manager. A value of 2 means that the WebSphere MQ Integrator broker does not have the queue open probably because it hasn't been started or the first message flow has yet to be deployed for it. If both of these steps have been taken then the WebSphere MQ Integrator broker may have been created incorrectly. In particular, it should have been created in migration mode. If the broker was not created with the migration flag set then it will need to be deleted and recreated before migration can commence. Any other value in the reason code will need to be reported to your IBM Support Center for problem resolution. Note that until the problem has been resolved the WebSphere MQ Publish/Subscribe broker can still be restarted with the the strmqbrk command. AMQ5864Broker reply message could not be sent. The command will be retried. Severity: 10 : Warning Explanation: While processing a publish/subscribe command, the WebSphere MQ Publish/Subscribe broker could not send a reply message to queue () at queue manager () for reason . The broker was also unable to write the message to the dead-letter queue. Since the command is being processed under syncpoint control, the broker will attempt to retry the command in the hope that the problem is only of a transient nature. If, after a set number of retries, the reply message still could not be sent, the command message will be discarded if the report options allow it. If the command message is not discardable, the stream will be restarted, and processing of the command message recommenced. Response: Use reason code to determine what remedial action is required. If the failure is due to a resource problem (for example, a queue being full), you might find that the problem has already cleared itself. If not, this message will be issued repeatedly each time the command is retried. In this case you are strongly advised to define a dead-letter queue to receive the reply message so that the broker can process other commands while the problem is being investigated. Check the application from which the command originated and ensure that it is specifying its reply-to queue correctly. AMQ5865Broker reply message could not be sent. Severity: 10 : Warning Explanation: While processing a publish/subscribe command, the WebSphere MQ Publish/Subscribe broker could not send a reply message to queue () at queue manager () for reason . The broker was also unable to write the message to the dead-letter queue. As the command is not being processed under syncpoint control, the broker is not able to retry the command. Response: Use reason code to determine what remedial action is required. If the failure is due to a resource problem (for example, a queue being full), you might find that the problem has already cleared itself. If not, check the application from which the command originated and ensure that it is specifying its reply-to queue correctly. You might find that defining a dead-letter queue to capture the reply message on a subsequent failure will help you with this task. AMQ5866Broker command message has been discarded. Reason code . Severity: 10 : Warning Explanation: The WebSphere MQ Publish/Subscribe broker failed to process a publish/subscribe command message, which has now been discarded. The broker will begin to process new command messages again. Response: Look for previous error messages to indicate the problem with the command message. Correct the problem to prevent the failure from happening again. AMQ5867WebSphere MQ Publish/Subscribe broker stream has ended abnormally. Severity: 10 : Warning Explanation: The broker stream () has ended abnormally for reason . The broker will attempt to restart the stream. If the stream should repeatedly fail, the broker will progressively increase the time between attempts to restart the stream. Response: Use the reason code to investigate why the problem occurred. A reason code of 1 indicates that the stream ended because a command message could not be processed successfully. Look in the error logs for earlier messages to determine the reason why the command message failed. A reason code of 2 indicates that the stream ended because the broker exit could not be loaded. Until the problem with the broker exit has been resolved, the stream will continue to fail. AMQ5868User is no longer authorized to subscribe to stream. Severity: 0 : Information Explanation: The broker has attempted to publish a publication to a subscriber, but the subscriber no longer has browse authority to stream queue (). The publication is not sent to the subscriber and his subscription is deregistered. An event publication containing details of the subscription that was removed is published on SYSTEM.BROKER.ADMIN.STREAM. While user ID () remains unauthorized, the broker will continue to deregister subscriptions associated with that user ID. Response: If the authority of user ID () was intentionally removed, consider removing all of that user IDs subscriptions immediately by issuing an MQCMD_DEREGISTER_SUBSCRIBER command, specifying the MQREGO_DEREGISTER_ALL option on the subscriber's behalf. If the authority was revoked accidentally, reinstate it, but be aware that some, if not all, of the subscriber's subscriptions will have been deregistered by the broker. AMQ5869WebSphere MQ Publish/Subscribe broker is checkpointing registrations. Severity: 0 : Information Explanation: A large number of changes have been made to the publisher and subscriber registrations of stream (). These changes are being checkpointed, in order to minimize both stream restart time and the amount of internal queue space being used. Response: None. AMQ5870(Unexpected Error) Severity: 0 : Information Explanation: N/A Response: N/A AMQ5871(Resource Problem) Severity: 0 : Information Explanation: N/A Response: N/A AMQ5872(WebSphere MQ Publish/Subscribe broker has a known child) Severity: 0 : Information Explanation: N/A Response: N/A AMQ5873(WebSphere MQ Publish/Subscribe broker active) Severity: 0 : Information Explanation: N/A Response: N/A AMQ5874(One or more queues could not be quiesced) Severity: 0 : Information Explanation: N/A Response: N/A AMQ5875WebSphere MQ Publish/Subscribe broker cannot write a message to the dead-letter queue. Severity: 10 : Warning Explanation: The broker attempted to put a message to the dead-letter queue () but the message could not be written to the dead-letter queue for reason :. The message was being written to the dead-letter queue with a reason of :. Response: Determine why the message cannot be written to the dead-letter queue. Also, if the message was not deliberately written to the dead-letter queue, for example by a message broker exit, determine why the message was written to the dead-letter queue and resolve the problem that is preventing the message from being sent to its destination. AMQ5876A parent conflict has been detected in the WebSphere MQ Publish/Subscribe broker hierarchy. Severity: 20 : Error Explanation: The broker () has been started, naming this broker as its parent. This broker was started naming broker () as its parent. The broker will send an exception message to broker () indicating that a conflict has been detected. The most likely reason for this message is that the broker topology has been changed while inter-broker communication messages were in transit (for example, on a transmission queue) and that a message relating to the previous broker topology has arrived at a broker in the new topology. This message may be accompanied by an informational FFST including details of the unexpected communication. Response: If the broker topology has changed and the broker named in the message no longer identifies this broker as its parent, this message can be ignored - for example, if the command "clrmqbrk -m -p" was issued. If broker () has been defined as this broker's parent, and this broker has been defined as broker ()'s parent, the clrmqbrk or the dltmqbrk commands should be used to resolve the conflict. AMQ5877WebSphere MQ Publish/Subscribe broker stream has ended abnormally. Severity: 10 : Warning Explanation: A broker stream () has ended abnormally for reason . The broker recovery routines failed to reset the stream state and the stream cannot be restarted automatically. Response: Investigate why the stream failed and why the broker's recovery routine could not recover following the failure. Take appropriate action to correct the problem. Depending upon the broker configuration and the nature of the problem it will be necessary to restart either the broker,or both the queue manager and the broker, to make the stream available. If the problem persists contact your IBM service representative. AMQ5878WebSphere MQ Publish/Subscribe broker recovery failure detected. Severity: 10 : Warning Explanation: An earlier problem has occurred with the broker, and either a stream has been restarted or the broker has been restarted. The restarted stream or broker has detected that the previous instance of the stream or broker did not clean up successfully and the restart will fail. Response: Investigate the cause of the failure that caused a stream or broker restart to be necessary, and why the broker or stream was unable to clean up its resources following the failure. When the broker processes with a non trusted routing exit (RoutingExitConnectType=STANDARD), the broker runs in a mode where it is more tolerant of unexpected failures and it is likely that the restart will succeed after a short delay. In the case of a stream restart, the broker will normally periodically retry the failing restart. In the case of a broker restart, it will be necessary to manually retry the broker restart after a short delay. When the broker processes without a routing exit, or with a trusted routine exit (RoutingExitConnectType=FASTPATH), the broker runs in a mode where it is less tolerant of unexpected failures and a queue manager restart will be necessary to resolve this problem. When the broker is running in this mode, it is important that the broker processes are not subjected to unnecessary asynchronous interrupts, for example, kill. If the problem persists, contact your IBM service representative. AMQ5879WebSphere MQ Publish/Subscribe broker has been migrated. Severity: 10 : Warning Explanation: The command was unsuccessful because the MQ Pub/Sub broker at queue manager has been migrated. After migration the only command which can be issued against the migrated broker is the dltmqbrk command. Response: Issue the dltmqbrk command to delete the migrated broker. AMQ5880User is no longer authorized to subscribe to stream. Severity: 0 : Information Explanation: The broker has attempted to publish a publication to a subscriber but the subscriber no longer has altusr authority to stream queue (). The publication is not sent to the subscriber and that user IDs subscription is deregistered. An event publication containing details of the subscription that was removed is published on SYSTEM.BROKER.ADMIN.STREAM. While user ID () remains unauthorized, the broker will continue to deregister subscriptions associated with that user ID. Response: If the authority of user ID () was intentionally removed, consider removing subscriptions immediately by issuing an MQCMD_DEREGISTER_SUBSCRIBER command for the appropriate topics on the subscriber's behalf. If the authority was revoked accidentally, reinstate it, but be aware that some, if not all, of the subscriber's subscriptions will have been deregistered by the broker. AMQ5881The WebSphere MQ Publish/Subscribe broker configuration parameter combination is not valid. Severity: 20 : Error Explanation: A combination of Broker stanzas in the queue manager initialization file is not valid. The broker will not operate until this has been corrected. An combination of (1) indicates that SyncPointIfPersistent has been set to TRUE and DiscardNonPersistentInputMsg has been set to FALSE. DiscardNonPersistentInputMsg must be set to TRUE when SyncPointIfPersistent is set to TRUE. An combination of (2) indicates that SyncPointIfPersistent has been set to TRUE and DiscardNonPersistentResponse has been set to FALSE. DiscardNonPersistentResponse must be set to TRUE when SyncPointIfPersistent is set to TRUE. An combination of (3) indicates that SyncPointIfPersistent has been set to TRUE and DiscardNonPersistentPublication has been set to FALSE. DiscardNonPersistentPublication must be set to TRUE when SyncPointIfPersistent is set to TRUE. Response: Alter the message broker stanzas to comply with the above rules and retry the command. AMQ5881 (Windows)The WebSphere MQ Publish/Subscribe broker configuration parameter combination is not valid. Severity: 20 : Error Explanation: A combination of Broker parameters in the broker configuration information is not valid. The broker will not operate until this has been corrected. An combination of (1) indicates that SyncPointIfPersistent has been set to TRUE and DiscardNonPersistentInputMsg has been set to FALSE. DiscardNonPersistentInputMsg must be set to TRUE when SyncPointIfPersistent is set to TRUE. An combination of (2) indicates that SyncPointIfPersistent has been set to TRUE and DiscardNonPersistentResponse has been set to FALSE. DiscardNonPersistentResponse must be set to TRUE when SyncPointIfPersistent is set to TRUE. An combination of (3) indicates that SyncPointIfPersistent has been set to TRUE and DiscardNonPersistentPublication has been set to FALSE. DiscardNonPersistentPublication must be set to TRUE when SyncPointIfPersistent is set to TRUE. Response: Alter the message broker configuration information using the cfgmqbrk tool to comply with the above rules and retry the command. AMQ5882WebSphere MQ Publish/Subscribe broker has written a message to the dead-letter queue. Severity: 10 : Warning Explanation: The broker has written a message to the dead-letter queue () for reason :. Note. To save log space, after the first occurrence of this message for stream (), it will only be written periodically. Response: If the message was not deliberately written to the dead-letter queue, for example by a message broker exit, determine why the message was written to the dead-letter queue, and resolve the problem that is preventing the message from being sent to its destination. AMQ5883WebSphere MQ Publish/Subscribe broker state not recorded. Severity: 10 : Warning Explanation: The broker state on stream () not recorded while processing a publication outside of syncpoint. A nonpersistent publication has requested a change to either a retained message or a publisher registration. This publication is being processed outside of syncpoint because the broker has been configured with the SyncPointIfPersistent option set. A failure has occurred hardening either the publisher registration or the retained publication to the broker's internal queue. All state changes attempted as a result of this publication will be backed-out. Processing of the publication will continue and the broker will attempt to deliver it to all subscribers. Response: Investigate why the failure occurred. It is probably due to a resource problem occurring on the broker. The most likely cause is 'queue full' on a broker queue. If your publications also carry state changes, you are advised to send them either as persistent publications or turn off the SyncPointIfPersistent option. In this way, they will be carried out under syncpoint and the broker can retry them in the event of a failure such as this. AMQ5884WebSphere MQ Publish/Subscribe broker control queue is not a local queue. Severity: 10 : Warning Explanation: WebSphere MQ Publish/Subscribe has detected that the queue 'SYSTEM.BROKER.CONTROL.QUEUE' exists and is not a local queue. This makes the queue unsuitable for use as the control queue of the broker. The broker will terminate immediately. Response: Delete the definition of the existing queue and, if required, re-create the queue to be of type MQQT_LOCAL. If you do not re-create the queue the broker will automatically create one of the correct type when started. AMQ5885Usage: migmqbrk -m QMgrName Severity: 0 : Information Explanation: This shows the correct usage. Response: None. AMQ5886WebSphere MQ Publish/Subscribe broker is being migrated. Severity: 10 : Warning Explanation: The command cannot be issued at this time because the MQ Pub/Sub broker at queue manager is being migrated. Response: Once migration has commenced then the only command which can be issued against the MQ Pub/Sub broker is the endmqbrk command to cancel the migration. Once the broker has ended if migration did not complete then it can be reattempted using the migmqbrk command again. Alternatively it can be cancelled by restarting the broker using the strmqbrk command. AMQ5887Migration started for stream Severity: 0 : Information Explanation: Migration of stream has started. Response: None. AMQ5888Migration complete for stream Severity: 0 : Information Explanation: All of the state of stream has been exported to the WebSphere MQ Integrator broker. Response: None. AMQ5889WebSphere MQ Publish/Subscribe broker has been successfully migrated. It will now be deleted. Severity: 0 : Information Explanation: Migration of the broker has completed successfully. The broker will now be deleted. Response: The broker is no longer startable. If deletion fails then the dltmqbrk command will need to be re-issued to complete its deletion. AMQ5890The migration of the WebSphere MQ Publish/Subscribe broker has failed. Severity: 10 : Warning Explanation: The WebSphere MQ Publish/Subscribe broker is being migrated. During this migration all persistent state, for example subscriptions, are exported to the WebSphere MQ Integrator broker as a series of messages sent to queue . A migration message could not be written to this queue for reason . Response: Use the MQPUT failure code to determine why the message cannot be written to the queue. The reason code could indicate that the queue manager is terminating in which case the migmqbrk command will need to be re-issued after the queue manager has restarted. Alternatively there may be a problem with the queue which may need to be rectified before migration can be attempted again. AMQ5891WebSphere MQ Publish/Subscribe broker has failed to receive a reply while exporting its state to WebSphere MQ Integrator. Severity: 10 : Warning Explanation: The WebSphere MQ Publish/Subscribe broker is being migrated. During this migration all persistent state, for example subscriptions, are exported to the WebSphere MQ Integrator broker as a series of messages. A reply message for one of the migration messages could not be retrieved from queue for reason . The migration of the WebSphere MQ Publish/Subscribe broker has failed. Response: Use the MQGET failure code to determine why the reply message could not be received from the reply queue. The reason code could indicate that the queue manager is terminating in which the migmqbrk command will need to be re-issued after the queue manager has restarted. A reason code of 2033 indicates that no reply message was received within a 30 second wait interval. In this case the problem is more likely to have occurred at the WebSphere MQ Integrator broker. Check for error messages issued at the WebSphere MQ Integrator broker. AMQ5892Migration of stream has failed for reason :. Severity: 0 : Information Explanation: Migration of stream has failed. Response: Use reason code to investigate the reason for the failure. Once the problem has been resolved, re-issue the migmqbrk command to retry migration. AMQ5892 (iSeries)Migration of stream has failed. Severity: 0 : Information Explanation: Migration of stream has failed for reason :. Response: Use reason code to investigate the reason for the failure. Once the problem has been resolved, re-issue the migmqbrk command to retry migration. AMQ5893WebSphere MQ Publish/Subscribe broker () cannot be migrated for reason :. Severity: 20 : Error Explanation: An attempt has been made to migrate the WebSphere MQ Publish/Subscribe broker () but the request has failed for reason :. Response: Determine why the migmqbrk command cannot complete successfully. The message logs for the queue manager might contain more detailed information outlining why the broker cannot be migrated. Resolve the problem that is preventing the command from completing and reissue the migmqbrk command. AMQ5893 (iSeries)WebSphere MQ Publish/Subscribe broker cannot be migrated. Severity: 20 : Error Explanation: An attempt has been made to migrate the broker () but the request has failed for reason :. Response: Determine why the migmqbrk command cannot complete successfully. The message logs for the queue manager might contain more detailed information outlining why the broker cannot be migrated. Resolve the problem that is preventing the command from completing and reissue the migmqbrk command. AMQ5894WebSphere MQ Publish/Subscribe broker cannot be migrated. Severity: 10 : Warning Explanation: The WebSphere MQ Publish/Subscribe broker cannot be migrated yet because the state of stream is not consistent with respect to related broker . While an WebSphere MQ Publish/Subscribe broker is being migrated a check is made to ensure that the state of each stream is consistent with respect to all of the broker's relations. This check has failed because an inconsistency has been detected in the state of stream with respect to broker . The problem will most likely be of a transient nature, caused because the WebSphere MQ Publish/Subscribe broker has yet to complete processing a recent change to the topology of the broker network. For example, the stream in question may have recently been created or deleted at related broker and this broker has yet to complete its processing for this change. Another cause maybe that either this broker, or broker , have just been added into the broker network and subscriptions have yet to be exchanged the two brokers. If this is the case then the brokers will be inconsistent with respect to all streams. If no recent topology changes have been made then there maybe a current failure with the propagation of subscriptions to broker . Response: In all cases migration of the WebSphere MQ Publish/Subscribe broker will need to be suspended until the inconsistency has been resolved. You will need to restart the broker using the strmqbrk command so that it can resolve the problem. After a short while, the broker can be ended and migration reattempted. If repeated attempts to migrate the broker all fail with this message then try to resolve the underlying problem. Look for earlier occurrences of message AMQ5826 and follow the guidance given there. In all cases ensure that the channels between the two brokers are running. AMQ5895WebSphere MQ Publish/Subscribe broker cannot be migrated. Severity: 10 : Warning Explanation: A topic has been detected which cannot be exported to the WebSphere MQ Integrator broker. The topic cannot be migrated because it contains wildcard characters recognised by the WebSphere MQ Integrator broker. The wildcard characters used by WebSphere MQ Integrator are the '+' and the '#' characters. The state associated with the topic isn't migrated and migration of the WebSphere MQ Publish/Subscribe broker fails. Response: The WebSphere MQ Publish/Subscribe broker cannot be migrated while topic is in use. All applications using topics which contain either the '+' or '#' characters will need to be redesigned to use different topic strings. Note that the amqspsd sample can be used to dump the state of the WebSphere MQ Publish/Subscribe broker. Within the dump produced by this program locate topic to determine information about the publishing or subscribing applications concerned. Until the problem has been resolved the WebSphere MQ Publish/Subscribe broker can be restarted as normal using the strmqbrk command. AMQ5896Unknown attribute for WebSphere MQ Publish/Subscribe broker configuration parameter GroupId. Severity: 20 : Error Explanation: The broker has attempted to create stream belonging to group , this group is unknown. Response: Modify the attribute for broker configuration parameter GroupId, to a group that exists, or create the group . 6000-6999 - Common services See Reading a message for an explanation of how to interpret these messages. AMQ6004An error occurred during WebSphere MQ initialization or ending. Severity: 30 : Severe error Explanation: An error was detected during initialization or ending of MQ. The MQ error recording routine has been called. Response: Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ6005 (iSeries)An error occurred during WebSphere MQ startup. Severity: 30 : Severe error Explanation: An attempt to start the storage monitor process (job QMQM in subsystem QSYSWRK) was unsuccessful. Response: Check the joblog for this job and for the QMQM job for possible reasons for failure, correct the error and try the command again. If the problem is not resolved, a problem may have been logged. Use WRKPRB to record the problem identifier, and to save the QPSRVDMP, QPJOBLOG, and QPDSPJOB files. Contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ6015The operating system is either too busy or has insufficient resources to complete a system request. Severity: 30 : Severe error Explanation: A system request was rejected by the operating system with return code . WebSphere MQ retried the request, but it continued to fail. This failure may indicate that the operating system is either too busy or has insufficient resources to complete the request. Response: Investigate whether the system is constrained by the workload on this system or by the workload on a server that it is using, and reduce the workload. AMQ6025Program not found. Severity: 30 : Severe error Explanation: WebSphere MQ is unable to start program because it was not found. Response: Check the program name is correctly specified and rerun the program. AMQ6026A resource shortage prevented the creation of a WebSphere MQ process. Severity: 30 : Severe error Explanation: An attempt to create an MQ process was rejected by the operating system due to a process limit (either the number of processes for each user or the total number of processes running system wide), or because the system does not have the resources necessary to create another process. Response: Investigate whether a process limit is preventing the creation of the process and if so why the system is constrained in this way. Consider raising this limit or reducing the workload on the system. AMQ6035WebSphere MQ failed, no storage available. Severity: 30 : Severe error Explanation: An internal function of the product attempted to obtain storage, but there was none available. Response: Stop the product and restart it. If this does not resolve the problem, save the generated output files and contact your IBM support center. AMQ6037WebSphere MQ was unable to obtain enough storage. Severity: 20 : Error Explanation: The product is unable to obtain enough storage. The product's error recording routine may have been called. Response: Stop the product and restart it. If this does not resolve the problem see if a problem has been recorded. If a problem has been recorded, use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ6047Conversion not supported. Severity: 30 : Severe error Explanation: WebSphere MQ is unable to convert string data tagged in CCSID to data in CCSID . Response: Check the WebSphere MQ Application Programming Reference Appendix and the appropriate National Language Support publications to see if the CCSIDs are supported by your system. AMQ6048DBCS error Severity: 30 : Severe error Explanation: WebSphere MQ is unable to convert string data due to a DBCS error. Conversion is from CCSID to CCSID . Response: Check the WebSphere MQ Application Programming Reference Appendix and the appropriate National Language Support publications to see if the CCSIDs are supported by your system. AMQ6049DBCS-only string not valid. Severity: 30 : Severe error Explanation: WebSphere MQ is unable to convert string data in CCSID to data in CCSID . Message descriptor data must be in single-byte form. CCSID is a DBCS-only CCSID. Response: Check the CCSID of your job or system and change it to one supporting SBCS or mixed character sets. Refer to the WebSphere MQ Application Programming Reference Appendix and the appropriate National Language Support publications for character sets and CCSIDs supported. AMQ6050CCSID error. Severity: 30 : Severe error Explanation: WebSphere MQ is unable to convert string data in CCSID to data in CCSID . Response: Check the WebSphere MQ Application Programming Reference Appendix and the appropriate National Language Support publications to see if the CCSIDs are supported by your system. AMQ6051Conversion length error. Severity: 30 : Severe error Explanation: WebSphere MQ is unable to convert string data in CCSID to data in CCSID , due to an input length error. AMQ6052Conversion length error. Severity: 30 : Severe error Explanation: WebSphere MQ is unable to convert string data in CCSID to data in CCSID . AMQ6053CCSID error Severity: 30 : Severe error Explanation: WebSphere MQ is unable to convert string data in CCSID to data in CCSID . Response: One of the CCSIDs is not supported by the system. Check the WebSphere MQ Application Programming Reference Appendix and the appropriate National Language Support publications to see if the CCSIDs are supported by your system. AMQ6064An internal WebSphere MQ error has occurred. Severity: 30 : Severe error Explanation: An error has been detected, and the MQ error recording routine has been called. Response: Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ6088 (iSeries)An internal WebSphere MQ error has occurred. Severity: 40 : Stop Error Explanation: An internal error occurred when API call was made. Response: Use WRKPRB to record the problem identifier, and to save the QPSRVDMP, QPJOBLOG, and QPDSPJOB files. Contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ6089 (iSeries)WebSphere MQ was unable to display an error message. Severity: 30 : Severe error Explanation: An attempt to display an error message was unsuccessful. This may be because the AMQMSG message file could not be found. The message identifier is . Response: Check that the library list is set up correctly to access the AMQMSG message file. If a change is necessary, rerun the failing application and record the error message. If you are unable to resolve the problem, contact your IBM support center. AMQ6090WebSphere MQ was unable to display an error message . Severity: 0 : Information Explanation: MQ has attempted to display the message associated with return code hexadecimal . The return code indicates that there is no message text associated with the message. Associated with the request are inserts : : : : . Response: Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ6091An internal WebSphere MQ error has occurred. Severity: 0 : Information Explanation: Private memory has detected an error, and is abending due to . The error data is . Response: Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ6092 (Windows)Manual conversion required for CCSID: Severity: 0 : Information Explanation: CCSID exists in new format but could not be reconciled against your old format. Response: Manually edit CCSID entry in conv\table\ccsid.tbl if you wish to retain your old conversion. For assistance call your Service Representative. AMQ6100An internal WebSphere MQ error has occurred. Severity: 0 : Information Explanation: MQ has detected an error, and is abending due to . The error data is . Response: Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ6103 (iSeries)WebSphere MQ job submission error. Severity: 30 : Severe error Explanation: WebSphere MQ is unable to submit job . AMQ6107CCSID not supported. Severity: 30 : Severe error Explanation: WebSphere MQ is unable to convert string data in CCSID to data in CCSID , because one of the CCSIDs is not recognized. Response: Check the WebSphere MQ Application Programming Reference Appendix and the appropriate National Language Support publications to see if the CCSIDs are supported by your system. AMQ6109An internal WebSphere MQ error has occurred. Severity: 30 : Severe error Explanation: An error has been detected, and the MQ error recording routine has been called. Response: Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ6110An internal WebSphere MQ error has occurred. Severity: 30 : Severe error Explanation: An error has been detected, and the MQ error recording routine has been called. Response: Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ6112 (iSeries)WebSphere MQ CCSID is using a default value. Severity: 10 : Warning Explanation: When initializing WebSphere MQ, no valid job CCSID was found, so the CCSID used is the default 37. This warning message will be issued until a valid CCSID has been set correctly. Response: Set the job CCSID. AMQ6114 (iSeries)An internal WebSphere MQ error has occurred. Severity: 30 : Severe error Explanation: An error has been detected, and the MQ error recording routine has been called. Response: Use WRKPRB to record the problem identifier, and to save the QPSRVDMP, QPJOBLOG, and QPDSPJOB files. Contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ6115An internal WebSphere MQ error has occurred. Severity: 10 : Warning Explanation: An error has been detected, and the MQ error recording routine has been called. Response: Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ6118An internal WebSphere MQ error has occurred () Severity: 40 : Stop Error Explanation: An error has been detected, and the MQ error recording routine has been called. Response: Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ6119An internal WebSphere MQ error has occurred () Severity: 40 : Stop Error Explanation: MQ detected an unexpected error when calling the operating system. The MQ error recording routine has been called. Response: Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ6120An internal WebSphere MQ error has occurred. Severity: 40 : Stop Error Explanation: An error has been detected, and the MQ error recording routine has been called. Response: Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ6121An internal WebSphere MQ error has occurred. Severity: 40 : Stop Error Explanation: An error has been detected, and the MQ error recording routine has been called. Response: MQ has detected a parameter count of that is not valid. Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ6122An internal WebSphere MQ error has occurred. Severity: 40 : Stop Error Explanation: An error has been detected, and the MQ error recording routine has been called. Response: MQ has detected parameter that is not valid, having value . Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ6125An internal WebSphere MQ error has occurred. Severity: 40 : Stop Error Explanation: An internal error has occurred with identifier . This message is issued in association with other messages. Response: Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ6134 (iSeries)Trace continues in buffer Severity: 0 : Information AMQ6135 (iSeries)Stopping early trace Severity: 0 : Information AMQ6136 (iSeries)Stopping early trace system time Severity: 0 : Information AMQ6137 (iSeries)Resuming MQI trace Severity: 0 : Information AMQ6138 (iSeries)Resuming MQI trace system time Severity: 0 : Information AMQ6139 (iSeries)Stopping MQI trace Severity: 0 : Information AMQ6140 (iSeries)Stopping MQI trace system time Severity: 0 : Information AMQ6141 (iSeries)Starting MQI trace Severity: 0 : Information AMQ6142 (iSeries)Starting MQI trace system time Severity: 0 : Information AMQ6143 (iSeries)WebSphere MQ function stack Severity: 0 : Information AMQ6144 (iSeries)No stack available Severity: 0 : Information AMQ6145 (iSeries)Terminating MQI trace Severity: 0 : Information AMQ6146 (iSeries)Entering end job processing Severity: 0 : Information AMQ6147 (iSeries)Terminating MQI trace system time Severity: 0 : Information AMQ6148An internal WebSphere MQ error has occurred. Severity: 0 : Information Explanation: MQ has detected an error, and is abending due to . The error data is . Response: Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ6150 (iSeries)WebSphere MQ resource busy. Severity: 30 : Severe error Explanation: MQ was unable to access an MQ object within the normal timeout period of minutes. Response: MQ will continue to wait for access. Ensure that all jobs using MQ are released. If the situation persists, quiesce the queue manager. AMQ6150 (Windows)WebSphere MQ semaphore is busy. Severity: 10 : Warning Explanation: WebSphere MQ was unable to acquire a semaphore within the normal timeout period of minutes. Response: MQ will continue to wait for access. If the situation does not resolve itself and you suspect that your system is locked then investigate the process which owns the semaphore. The PID of this process will be documented in the accompanying FFST. AMQ6151 (iSeries)WebSphere MQ resource released. Severity: 30 : Severe error Explanation: An MQ resource, for which another process has been waiting, for a period of over minutes has been released. Response: No recovery is needed. AMQ6152 (iSeries)WebSphere MQ failed to end commitment control while attempting to quiesce a queue manager. Severity: 30 : Severe error Explanation: WebSphere MQ failed to end commitment control whilst quiescing queue manager . Response: There are one or more active resources under commitment control. Use the Work with Job (WRKJOB) command with the OPTION(*CMTCTL) parameter to display the active resources under commitment control. Check the job log for previously issued messages. AMQ6153 (iSeries)The attempt to quiesce queue manager failed Severity: 30 : Severe error Explanation: The attempt to quiesce queue manager was unsuccessful Response: Check the job log for previously issued messages. If the quiesce was issued with the *CNTRLD option, re-issue the command with the *IMMED option. If a low TIMEOUT retry delay was used, re-issue the request with a higher value. AMQ6154 (iSeries)Queue manager has been quiesced. Severity: 0 : Information Explanation: The queue manager has been successfully quiesced. Response: None. AMQ6158 (iSeries)SBCS CCSID not found. Severity: 30 : Severe error Explanation: WebSphere MQ is unable to find an SBCS CCSID which corresponds to mixed DBCS-SBCS CCSID . Response: Check the CCSID of your job or system and check it has a SBCS equivalent. Refer to the National Language Support Planning Guide for character sets and CCSIDs supported. If the CCSID used does have an SBCS equivalent, save the job log containing this message and contact your IBM support center. AMQ6159 (iSeries)WebSphere MQ job submission error. Severity: 30 : Severe error Explanation: WebSphere MQ for iSeries is unable to release job . Response: Contact you System Administrator to remove job . Ensure you have *JOBCTL authority and try again. AMQ6160EXPLANATION: Severity: 0 : Information AMQ6161ACTION: Severity: 0 : Information AMQ6162An error has occurred reading an INI file. Severity: 20 : Error Explanation: An error has occurred when reading the MQS.INI file or a queue manager QM.INI file. Response: If you have been changing the INI file content check and correct the change. If you have not changed the INI file, use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ6162 (Windows)An error occurred when reading the configuration data. Severity: 20 : Error Explanation: An error has occurred when reading the configuration data. Response: If you have changed the configuration data, check and correct the change. If you have not changed the configuration data, use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ6163An error has occurred locking an INI file. Severity: 10 : Warning Explanation: An error has occurred locking the MQS.INI file or a queue manager QM.INI file. Response: If you have been changing the INI file permissions check and correct the change. If you have not changed the INI file, use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ6163 (Windows)An error has occurred locking the configuration data. Severity: 10 : Warning Explanation: An error has occurred locking the configuration data. Response: If you have changed the the registry permissions, check and correct the change. If you have not changed the registry, use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ6164An expected stanza in an INI file is missing or contains errors. Severity: 10 : Warning Explanation: An expected stanza is missing from the MQS.INI file or a queue manager QM.INI file or the stanza contains errors. Response: If you have been changing the INI file content check and correct the change. AMQ6164 (Windows)An expected stanza in the configuration data is missing or contains errors. Severity: 10 : Warning Explanation: An expected stanza is missing from the configuration data or the stanza contains errors. Response: If you have changed the configuration data, check and correct the change. AMQ6165Unable to access an INI file. Severity: 10 : Warning Explanation: Access to the MQS.INI file or a queue manager QM.INI file is denied. Response: If you have been changing the INI file permissions check and correct the change. AMQ6165 (Windows)Unable to access the configuration data. Severity: 10 : Warning Explanation: Access to the configuration data is denied. Response: If you have changed the configuration data permissions, check and correct the changes. AMQ6166An INI file is missing. Severity: 20 : Error Explanation: The MQS.INI file or a queue manager QM.INI file is missing. Response: If you have been changing the INI file recover the previous file and retry the operation. AMQ6166 (Windows)An entry in the configuration data is missing. Severity: 20 : Error Explanation: A required entry in the configuration data is missing. Response: If you have changed the configuration data, recover the previous configuration data and retry the operation. AMQ6172No codeset found for current locale. Severity: 20 : Error Explanation: No codeset could be determined for the current locale. Check that the locale in use is supported. Response: None. AMQ6173No CCSID found for codeset . Severity: 20 : Error Explanation: Codeset . has no supported CCSID. Check that the locale in use is supported. CCSIDs can be added by updating the file /var/mqm/conv/table/ccsid.tbl. Response: None. AMQ6174The library was not found. The queue manager will continue without this module. Severity: 0 : Information Explanation: The dynamically loadable library was not found. Response: Check that the file exists and is either fully qualified or is in the appropriate directory. AMQ6174 (iSeries)The library was not found. Severity: 0 : Information Explanation: The dynamically loadable file was not found. The queue manager will continue without this module. Response: Check that the file exists and is either fully qualified or is in the appropriate directory. AMQ6174 (Unix)The dynamically loadable shared library was not found. The system returned error number and error message . The queue manager will continue without this module. Severity: 0 : Information Explanation: This message applies to UNIX systems. The shared library was not found. Response: Check that the file exists, and is either fully qualified or is in the appropriate director, also check the file access permissions. AMQ6175 (AIX)The system could not dynamically load the shared library . The system returned error number and error message . The queue manager will continue without this module. Severity: 30 : Severe error Explanation: This message applies to AIX systems. The shared library failed to load correctly due to a problem with the library. Response: Check the file access permissions and that the file has not been corrupted. AMQ6175 (Unix)The system could not dynamically load the shared library . The system returned error message . The queue manager will continue without this module. Severity: 30 : Severe error Explanation: This message applies to UNIX systems. The shared library failed to load correctly due to a problem with the library. Response: Check the file access permissions and that the file has not been corrupted. AMQ6175 (Windows)The system could not dynamically load the library . The system return code was . The queue manager will continue without this module. Severity: 30 : Severe error Explanation: This message applies to Windows NT and Windows 2000 systems only. The dynamically loadable file failed to load correctly due to an internal error. The MQ error recording routine has been called. Response: Check that the file has not been corrupted then use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ6177 (Windows)An internal WebSphere MQ error has occurred. Severity: 40 : Stop Error Explanation: An error has been detected, and the MQ error recording routine has been called. Response: Details of the error have been stored at . A synopsis is given in the data section below. Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ6179The system could not find symbol in the dynamically loaded library . The system returned error number and error message . Severity: 30 : Severe error Explanation: The library does not contain symbol or it has not been exported. Response: Check that symbol name is correct and has been exported from the library. AMQ6179 (Unix)The system could not find the symbol in the dynamically loaded shared library . The system returned error message . Severity: 30 : Severe error Explanation: This message applies to UNIX systems. The shared library does not contain symbol or it has not been exported. Response: Check that symbol name is correct and has been exported from the library. AMQ6180 (Windows)Default conversion not supported. Severity: 30 : Severe error Explanation: WebSphere MQ is unable to convert string data tagged in CCSID to data in CCSID . Response: Check the default CCSIDs specified in the ccsid.tbl file and make sure that conversion is supported between these CCSIDs. AMQ6182Error found in line of ccsid.tbl Severity: 30 : Severe error Explanation: Line contains and error. The content of the line is . Processing continues but the line in error is ignored. Response: Correct the line and rerun the program or command giving this message. AMQ6183An internal WebSphere MQ error has occurred. Severity: 10 : Warning Explanation: An error has been detected, and the WebSphere MQ error recording routine has been called. The failing process is process . Response: Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ6184An internal WebSphere MQ error has occurred on queue manager . Severity: 10 : Warning Explanation: An error has been detected, and the WebSphere MQ error recording routine has been called. The failing process is process . Response: Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ6184 (iSeries)An internal WebSphere MQ error has occurred. Severity: 10 : Warning Explanation: An internal MQ error has occurred on queue manager and the MQ error recording routine has been called. The failing process is process . Response: Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ6187User is not authorized for RestrictedMode queue manager. Severity: 40 : Stop Error Explanation: All users must be in the RestrictedMode application_group. AMQ6188 (AIX)The system could not dynamically load the shared library as the entry point to the library, symbol 'MQStart', could not be located within the library. The queue manager will continue without this library. Severity: 30 : Severe error Explanation: This message applies to AIX systems. The shared library failed to load correctly due to a problem with the library. Response: Check that the entry point to the library, symbol 'MQStart', exists and has been exported from the library. AMQ6188 (Unix)The system could not dynamically load the shared library as the entry point to the library, symbol 'MQStart', could not be located within the library. The system returned error message . The queue manager will continue without this library. Severity: 30 : Severe error Explanation: This message applies to UNIX systems. The shared library failed to load correctly due to a problem with the library. Response: Check that the entry point to the library, symbol 'MQStart', exists and has been exported from the library. AMQ6188 (Windows)The system could not dynamically load the library due to a problem with the dll. The errno was . The queue manager will continue without this module. Severity: 30 : Severe error Explanation: This message applies to Windows NT and Windows 2000 systems only. The dynamically loadable file failed to load correctly due to a problem with the dll. Response: Check that the dll is in the correct place with the correct file permissions etc. and has not been corrupted. AMQ6190 (Windows)Program not found. Severity: 30 : Severe error Explanation: The program cannot be found. Response: Check that the program specified is available on your system. If the program name is not fully qualified, ensure that the PATH environment variable includes the directory where the program is located. AMQ6191 (Windows)Program failed to start, return code . Severity: 30 : Severe error Explanation: The program was invoked, but failed to start. The failure reason code is . Response: Check that the program specified is available on your system, and that sufficient system resources are available. Where applicable, verify that the user is authorized to run the program. AMQ6192 (Windows)IBM WebSphere MQ Utilities Severity: 0 : Information AMQ6193 (Windows)The registry entry was not found. Severity: 20 : Error Explanation: WebSphere MQ for Windows NT and Windows 2000 sets the registry entry when the product is installed, but the entry is now missing. Response: If the registry has been edited, restore the previous version. If the product is newly installed, check whether the installation was successful, and reinstall the product if necessary. AMQ6196An error has occurred whilst processing a temporary INI file Severity: 20 : Error Explanation: An error has occurred when creating a backup of an INI file. The backup file already exists Response: You may have created a backup of the INI file with the name , or an earlier operation may have failed. Move or delete the file and reattempt the operation. If you have not changed the INI file, use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ6207 (AIX)Failed to attach shared memory segment as Segment table is Full. Severity: 20 : Error Explanation: When running in native mode an application may attach only 10 shared memory segments. The application which issued this message attempted to exceed this number. By setting the environment variable EXTSHM=ON this limit can be removed. Further explanation on using this variable and other options available, may be found in the documentation. Response: Either reduce the number of segments to which your application needs to attach or set the EXTSHM=ON variable in your environment before starting the application. AMQ6208 Severity: 10 : Warning Explanation: Response: AMQ6209An unexpected asynchronous signal ( : ) has been received and ignored. Severity: 10 : Warning Explanation: Process received an unexpected asynchronous signal and ignored it. This has not caused an error but the source of the signal should be determined as it is likely that the signal has been generated externally to WebSphere MQ. Response: Determine the source of the signal and prevent it from re-occurring. AMQ6212Failed to load Library as C++ environment is not initialised. Severity: 10 : Warning Explanation: An attempt was made to load the identified C++ shared library. However, the attempt failed because the C++ environment has not been initialized for the current process. Response: Ensure the application is linked with the appropriate C++ runtime environment. AMQ6218 (AIX)EXTSHM variable detected with unrecognised value and has been reset to . Severity: 20 : Error Explanation: Processes that access the internal queue manager control blocks must use the AIX Extended Shared Memory model, and while one such process was starting, WebSphere MQ detected that the EXTSHM variable was set but did not contain an appropriate value. This value has been reset and the process will continue with the new setting. Response: No further action is required. To prevent this message being issued in future, correct the value of the EXTSHM variable in your environment. AMQ6230Message suppressed times in the last seconds. Severity: 20 : Error Explanation: Message was issued times in the last seconds but only the first instance of the message was written to the log. The suppressed messages may have included differing message arguments. Response: If you wish to see all occurrences of this message you should alter the definition of the SuppressMessage attribute in the Queue Manager configuration. AMQ6231 (Unix)Usage: mqchkdir [-f] Severity: 20 : Error Explanation: An incorrect option was specified on the command line for the command. Response: Reissue the command specifying the correct parameters. AMQ6232 (Unix)Operating System userid not found. Severity: 20 : Error Explanation: A request was made to the operating system to lookup the details of the identified userid but the request failed. Response: Using the operating system supplied tools check for the existence of the identified userid, and if missing then recreate it. AMQ6233 (Unix)Operating System authorisation group not found. Severity: 20 : Error Explanation: A request was made to the operating system to lookup the details of the identified group but the request failed. Response: Using the operating system supplied tools check for the existence of the identified group, and if missing then recreate it. AMQ6234 (Unix)Unknown Queue Manager name specified. Severity: 20 : Error Explanation: An invalid Queue Manager name was specified in the parameters to the command. Response: Reissue the command specifying a valid Queue Manager name. AMQ6235 (Unix)Directory missing. Severity: 20 : Error Explanation: The identified directory is missing. Response: Reissue the command selecting the option to create missing directories. AMQ6236 (Unix)Missing directory has been created. Severity: 20 : Error Explanation: The identified directory was missing but has been created. Response: None AMQ6237 (Unix)File missing. Severity: 20 : Error Explanation: The identified file is missing. Response: Reissue the command selecting the option to create missing files. AMQ6238 (Unix)Missing file has been created. Severity: 20 : Error Explanation: The identified file was missing but has been created. Response: None AMQ6239 (Unix)Permission denied attempting to access filesystem location . Severity: 20 : Error Explanation: An attempt to query the filesystem object identified failed because the command issued did not have authority to access the object. Response: Check the authority on the object and of the user executing the command and reissue the command. AMQ6240 (Unix)You must be an operating system superuser to run this command. Severity: 20 : Error Explanation: In irder to run this command you must be logged on as a user with superuser privelages. Response: Log in as an appropriate user and reissue the command. AMQ6241 (Unix)The filesystem object is a symbolic link. Severity: 20 : Error Explanation: While checking the filesystem, an object was found which is a symbolic link. Response: This is not an error however you should verify that the symbolic link is expected and that the destination of the symbolic link is correct. AMQ6242 (Unix)Incorrect ownership for . Current() Expected() Severity: 20 : Error Explanation: The filesystem object is owned by the user with uid when it was expected to be owned by the user with uid . Response: Correct the ownership using operating system commands or reissue the command selecting the option to fix the incorrect owership. AMQ6243 (Unix)Incorrect group ownership for . Current() Expected() Severity: 20 : Error Explanation: The filesystem object is owned by the group with gid when it was expected to be owned by the group with gid . Response: Correct the ownership using operating system commands or reissue the command selecting the option to fix the incorrect owership. AMQ6244 (Unix)Incorrect permissions on object . Current() Expected() Severity: 20 : Error Explanation: The filesystem object has the wrong file permissions. Response: Correct the ownership using operating system commands or reissue the command selecting the option to fix the incorrect owership. AMQ6245 (Unix)Error executing system call on file error . Severity: 20 : Error Explanation: The execution of the system call on file failed and the error code was returned. Response: Investigate the cause of the failure using the operating system error code and reissue the command. AMQ6251 (Unix)The system could not dynamically load the shared library . The queue manager will continue without this module. Severity: 30 : Severe error Explanation: This message applies to UNIX systems. The shared library failed to load as it is probably a -bit library, a -bit library is required. Note that MQ tried to find a -bit library named either or , but failed. The following message gives details of the original failure. Response: Supply the name of a -bit library. AMQ6252 (Unix)The system could not dynamically load the shared library . The queue manager will continue without this module. Severity: 30 : Severe error Explanation: This message applies to UNIX systems. The shared library failed to load as it is probably a -bit library, a -bit library is required. Note that MQ found and loaded a -bit library named however this also failed to load with the system returning error message . The following message gives details of the original failure. Response: Supply the name of a -bit library. AMQ6253 (Unix)The system could not dynamically load the shared library . The queue manager will continue without this module. Severity: 30 : Severe error Explanation: This message applies to UNIX systems. The shared library failed to load as it is probably a -bit library, a -bit library is required. Note that MQ attempted to locate and load a -bit library named either of these: . The first library failed to load as it also is probably a -bit library, the second library is a -bit library, however this also failed to load with the system returning error message . The following message gives details of the original failure. Response: Supply the name of a -bit library. AMQ6254 (Unix)The system could not dynamically load the shared library , library has been used instead. Severity: 0 : Information Explanation: This message applies to UNIX systems. The shared library failed to load as it is probably a -bit library, a -bit library is required. Note that MQ has sucessfully located and loaded a -bit library named . Response: Supply the name of a -bit library or put the library (alternatively a symbolic link can be used) in the appropriate place: 32-bit libraries in /var/mqm/exits; 64-bit libraries in /var/mqm/exits64. AMQ6255 (Unix)The system could not dynamically load the shared library . The queue manager will continue without this module. Severity: 30 : Severe error Explanation: This message applies to UNIX systems. The shared library failed to load as it is probably a -bit library, a -bit library is required. The following message gives details of the original failure. Response: Supply the name of a -bit library. AMQ6256 (Unix)The system could not dynamically load the shared library . The queue manager will continue without this module. Severity: 30 : Severe error Explanation: This message applies to UNIX systems. The shared library failed to load as it is probably a -bit library, a -bit library is required. Note that MQ tried to find a -bit library named , but failed. The following message gives details of the original failure. Response: Supply the name of a -bit library. AMQ6257Message suppression enabled for message numbers (). Severity: 0 : Information Explanation: The message contain's a list of message id's for which entries repeated within the suppression interval will be suppressed. Response: If you wish to see all occurrences of these messages you should alter the definition of the SuppressMessage attribute in the Queue Manager configuration. AMQ6258Message exclusion enabled for message numbers (). Severity: 0 : Information Explanation: The message contain's a list of message id's which have been excluded. Requests to write these messages to the error log will be discarded. Response: If you wish to see instances of these messages you should alter the definition of the ExcludeMessage attribute in the Queue Manager configuration. AMQ6259Message cannot be . Severity: 10 : Warning Explanation: Message cannot be excluded or suppressed but was specified in the ExcludeMessage or SuppressMessage configuration for the Queue Manager. The Queue Manager will continue however the request to suppress or exclude this message will be ignored. Response: Update the Queue Manager configuration to remove the specified message identifier. AMQ6260Help Topic not found Severity: 10 : Warning Explanation: The requested help topic could not be located. For further assistance, please refer to the WebSphere MQ manuals. Response: Ensure that the WebSphere MQ InfoCenter is installed. AMQ6261 (Unix)An exception occurred trying to dynamically load shared library . The queue manager will continue without this module. Severity: 30 : Severe error Explanation: This message applies to UNIX systems. Exception number name , occurred trying to dynamically load shared library . Response: Check the shared library has not been corrupted. If the shared library contains any initializer functions, ensure these are not causing the problem and that they conform to the expected function prototype. AMQ6261 (Windows)An exception occurred trying to load DLL . The queue manager will continue without this module. Severity: 30 : Severe error Explanation: This message applies to Windows systems only. Exception number error , occurred trying to load DLL . Response: Check the DLL has not been corrupted. If the DLL contains any initializer functions, ensure these are not causing the problem and that they conform to the expected function prototype. AMQ6666 (iSeries)Required WebSphere MQ system profile(s) can not be accessed. Severity: 40 : Stop Error Explanation: The required MQ system profile(s) QMQM and/or QMQMADM are not found or have been disabled. MQ can not continue processing the command without the profiles existing and enabled on the system. The major error code is , the minor error code is . The major error codes and their meanings are as follows: *DISABLED - The user profile has been disabled. *PWDEXP - The password for the user profile has expired . *EXIST - The user profile does not exist. If none of these error codes are shown the major error code contains the exception identifier. The minor error code identifies the user profile which cannot be accessed. Response: Check that both QMQM and QMQMADM profiles exist and are both enabled using the DSPUSRPRF command, or contact the WebSphere MQ system administrator. AMQ6708A disk full condition was encountered when formatting a new log file in location . Severity: 20 : Error Explanation: The queue manager attempted to format a new log file in directory . The drive or file system containing this directory did not have sufficient free space to contain the new log file. Response: Increase the amount of space available for log files and retry the request. AMQ6708 (iSeries)A disk full condition was encountered when formatting a new log file. Severity: 20 : Error Explanation: The queue manager attempted to format a new log file in directory . The drive or file system containing this directory did not have sufficient free space to contain the new log file. Response: Increase the amount of space available for log files and retry the request. AMQ6709The log for the Queue manager is full. Severity: 20 : Error Explanation: This message is issued when an attempt to write a log record is rejected because the log is full. The queue manager will attempt to resolve the problem. Response: This situation may be encountered during a period of unusually high message traffic. However, if you persistently fill the log, you may have to consider enlarging the size of the log. You can either increase the number of log files by changing the values in the queue manager configuration file. You will then have to stop and restart the queue manager. Alternatively, if you need to make the log files themselves bigger, you will have to delete and recreate the queue manager. AMQ6710Queue manager unable to access directory . Severity: 20 : Error Explanation: The queue manager was unable to access directory for the log. This could be because the directory does not exist, or because the queue manager does not have sufficient authority. Response: Ensure that the directory exists and that the queue manager has authority to read and write to it. Ensure that the LogPath attribute in the queue manager's configuration file matches the intended log path. AMQ6767Log file could not be opened for use. Severity: 20 : Error Explanation: Log file could not be opened for use. Possible reasons include the file being missing, the queue manager being denied permission to open the file or the contents of the file being incorrect. Response: If the log file was required to start the queue manager, ensure that the log file exists and that the queue manager is able to read from and write to it. If the log file was required to recreate an object from its media image and you do not have a copy of the required log file, delete the object instead of recreating it. AMQ6774Log file did not contain the requested log record. Severity: 20 : Error Explanation: Log file does not contain the log record whose LSN is . This is because the log file numbers have wrapped and the log file name has been reused by a newer file. Once a log file name has been reused, it is not possible to access the data in the previous versions of the file to use this name. The operation which requested this log record cannot be completed. AMQ6782The log file numbers have wrapped. Severity: 0 : Information Explanation: Each log file formatted is assigned a number which makes up part of its file name. The numbers are allocated sequentially and consist of seven digits giving a maximum of 10 million different log file names. Once all available numbers have been allocated, the queue manager again starts allocating numbers starting from zero. Once a file number has been re-allocated, you can no longer access data in the previous log files allocated the same number. The file numbers wrapped at log sequence number . Response: You should periodically take media images of all WebSphere MQ objects. You must ensure that media images of all objects which you may need to recreate do not span more than 10 million log files. AMQ6901 (iSeries)WebSphere MQ for iSeries AMQ6902 (iSeries)WebSphere MQ for iSeries - Samples AMQ6903 (iSeries)Installation failed, WebSphere MQ resources are still active. Severity: 30 : Severe error Explanation: An attempt to install WebSphere MQ was unsuccessful because MQ resources from a previous installation of MQ are still active. This failure may indicate that a queue manager from a previous installation of MQ is still running or has active jobs. Response: Ensure that all queue managers from previous installations of WebSphere MQ have been quiesced, and that the QMQM subsystem is not active using the WRKSBS and ENDSBS commands. Refer to the installation section in the WebSphere MQ for iSeries Quick Beginnings publication for further details. AMQ6904 (iSeries)Installation of WebSphere MQ for iSeries failed due to previous release installed. Explanation: Some releases of WebSphere MQ for iSeries require migration before a later release can be installed. Response: If you wish to retain your current MQ information you must step through the migration process - see the Quick Beginnings Manual. If you do not wish to retain your current MQ information remove the current version of MQ before retrying the install. AMQ6905 (iSeries)Found new MQ jobs to end, and MQ jobs currently ending. Severity: 0 : Information Explanation: Jobs with locks on library QMQM are ended so that WebSphere MQ may be deleted or updated. Response: None. AMQ6906 (iSeries) jobs still ending. Severity: 40 : Stop Error Explanation: Jobs report state of 'already being deleted' after timeout. Response: If system is heavily loaded wait and reissue the command CALL QMQM/AMQIQES4 to try to delete jobs using WebSphere MQ resources. If this message is issued again, issue the command WRKOBJLCK for library QMQM to see which jobs have not been deleted, and end them manually. AMQ6907 (iSeries)All WebSphere MQ pre-requisite PTFs on OS/400 programs are installed. Severity: 0 : Information Explanation: None. Response: None. AMQ6908 (iSeries)WebSphere MQ pre-requisite PTF for program is not installed. Severity: 40 : Stop Error Explanation: PTF - is not installed on system in state 'Permanently applied' 'Temporarily applied' or 'Superseded'. WebSphere MQ installation will proceed, but you must install the PTF before starting WebSphere MQ. Response: Use the command GO CMDPTF to display commands to order and apply the required PTF -.. AMQ6909 (iSeries)User space recovery failed, WebSphere MQ is running. Severity: 30 : Severe error Explanation: An attempt to recover user space was unsuccessful because MQ was running. Response: Quiesce WebSphere MQ for iSeries and try again. See the section on "Quiescing WebSphere MQ" in the WebSphere MQ for iSeries Quick Beginnings. AMQ6910 (iSeries)The attempt to quiesce the queue manager failed. Severity: 30 : Severe error Explanation: The attempt to quiesce the queue manager was unsuccessful because the current job has locks on library QMQM. Response: Sign off the current job, sign on and attempt to quiesce the queue manager again. See the section on "Quiescing WebSphere MQ" in the WebSphere MQ for iSeries Quick Beginnings. AMQ6911 (iSeries)WebSphere MQ quiesce is performing a RCDMQMIMG, please wait. Severity: 0 : Information Explanation: WebSphere MQ quiesce is performing a Record Object Image (RCDMQMIMG) for all objects. Please wait, there may be some delay until this is completed. Response: None. AMQ6912 (iSeries)WebSphere MQ for iSeries - Java AMQ6913 (iSeries)WebSphere MQ for iSeries - Java samples AMQ6988yes Severity: 0 : Information AMQ6988 (iSeries)Yes AMQ6989no Severity: 0 : Information AMQ6989 (iSeries)No AMQ6992 (iSeries)Program parameter error. Severity: 40 : Stop Error Explanation: WebSphere MQ for iSeries program has an incorrect number of parameters, or an error in the parameter value. Response: Display the job log, using the DSPJOBLOG command, for more information on the problem. AMQ6993 (iSeries)Program ended abnormally. Severity: 40 : Stop Error Explanation: A WebSphere MQ for iSeries program, , is ending abnormally. Response: Display the job log, using the DSPJOBLOG command, for information why the job or subsystem ended abnormally. Correct the error and retry the request. AMQ6994 (Windows)5724-H72 (C) Copyright IBM Corp. 1994, 2004. ALL RIGHTS RESERVED. Severity: 0 : Information Explanation: None. Response: None. AMQ6995 (iSeries)xcsFFST has been called; take a look at the job log. Severity: 0 : Information AMQ6998 (iSeries)An internal WebSphere MQ error has occurred. Severity: 40 : Stop Error Explanation: WebSphere MQ for iSeries is diagnosing an unexpected error. Response: Save the job log, and contact your IBM support center. AMQ6999 (iSeries)An internal WebSphere MQ error has occurred. Severity: 0 : Information Explanation: WebSphere MQ has experienced an internal failure, from which it could not recover. Response: Use WRKPRB to check if a problem has been created. If one has, record the problem identifier, and save the QPSRVDMP, QPJOBLOG, and QPDSPJOB files. If a problem has not been created, save the job log. Contact your IBM support center. Do not discard these files until the problem has been resolved. 7000-7999 - WebSphere MQ product See Reading a message for an explanation of how to interpret these messages. AMQ7001The location specified for creation of the queue manager is not valid. Severity: 40 : Stop Error Explanation: The directory under which queue managers are to be created is not valid. It may not exist, or there may be a problem with authorization. Response: The location is specified in the machine-wide ini file. Correct the file and submit the request again. AMQ7001 (Windows)The location specified for the creation of the queue manager is not valid. Severity: 40 : Stop Error Explanation: The directory under which the queue managers are to be created is not valid. It may not exist, or there may be a problem with authorization. Response: The location is specified in the configuration data. Correct the configuration data and submit the request again. AMQ7002An error occurred manipulating a file. Severity: 40 : Stop Error Explanation: An internal error occurred while trying to create or delete a queue manager file. It is likely that the error was caused by a disk having insufficient space, or by problems with authorization to the underlying filesystem. Response: Identify the file that caused the error, using problem determination techniques. For example check if there are any FFST files, which may identify the queue manager file causing the error. This error may also be caused if users have created, renamed or deleted that file. Correct the error in the filesystem and submit the request again. AMQ7002 (Windows)An error occurred manipulating a file. Severity: 40 : Stop Error Explanation: An internal error occurred while trying to create or delete a queue manager file. In the case of a failure to delete a file a common reason for this error is that a non MQ process, such as the windows explorer or a virus checker, is accessing the file. In the case where the object that cannot be deleted is a directory then a non MQ process may be accessing a file within the directory or one of its subdirectories. It is also possible that the error was caused by a disk having insufficient space, or by problems with authorization to the underlying filesystem. Response: Identify the file that caused the error, using problem determination techniques. For example check if there are any FFST files, which may identify the queue manager file causing the error. This error may also be caused if users have created, renamed or deleted that file. Correct the error in the filesystem and submit the request again. AMQ7005The queue manager is running. Severity: 40 : Stop Error Explanation: You tried to perform an action that requires the queue manager stopped, however, it is currently running. You probably tried to delete or start a queue manager that is currently running. Response: If the queue manager should be stopped, stop the queue manager and submit the failed command again. AMQ7006Missing attribute on stanza starting on line of ini file . Severity: 20 : Error Explanation: The stanza starting on line of configuration file is missing the required attribute. Response: Check the contents of the file and retry the operation. AMQ7006 (Windows)Missing attribute from configuration data. Severity: 20 : Error Explanation: The stanza in the configuration data is missing the required attribute. Response: Check the contents of the configuration data and retry the operation. AMQ7008The queue manager already exists. Severity: 40 : Stop Error Explanation: You tried to create a queue manager that already exists. Response: If you specified the wrong queue manager name, correct the name and submit the request again. AMQ7010The queue manager does not exist. Severity: 40 : Stop Error Explanation: You tried to perform an action against a queue manager that does not exist. You may have specified the wrong queue manager name. Response: If you specified the wrong name, correct it and submit the command again. If the queue manager should exist, create it, and then submit the command again. AMQ7011The queue manager files have not been completely deleted. Severity: 40 : Stop Error Explanation: While deleting the queue manager, an error occurred deleting a file or directory. The queue manager may not have been completely deleted. Response: Follow problem determination procedures to identify the file or directory and to complete deletion of the queue manager. AMQ7012The specified trigger interval is not valid. Severity: 40 : Stop Error Explanation: You specified a value for the trigger interval that is not valid. The value must be not less than zero and not greater than 999 999 999. Response: Correct the value and resubmit the request. AMQ7013There is an error in the name of the specified dead-letter queue. Severity: 40 : Stop Error Explanation: You specified a name for the dead-letter queue that is not valid. Response: Correct the name and resubmit the request. AMQ7014There is an error in the name of the specified default transmission queue. Severity: 40 : Stop Error Explanation: You specified a name for the default transmission queue that is not valid. Response: Correct the name and submit the command again. AMQ7015There is an error in the maximum number of open object handles specified. Severity: 40 : Stop Error Explanation: You specified a value for the maximum number of open object handles to be allowed that is not valid. The value must be not less than zero and not greater than 999 999 999. Response: Correct the value and submit the command again. AMQ7016There is an error in the maximum number of uncommitted messages specified. Severity: 40 : Stop Error Explanation: You specified a value for the maximum number of uncommitted messages to be allowed that is not valid. The value must be not less than 1 and not greater than 999 999 999. Response: Correct the value and submit the command again. AMQ7017Log not available. Severity: 40 : Stop Error Explanation: The queue manager was unable to use the log. This could be due to a log file being missing or damaged, or the log path to the queue manager being inaccessible. Response: Ensure that the LogPath attribute in the queue manager configuration file is correct. If a log file is missing or otherwise unusable, restore a backup copy of the file, or the entire queue manager. AMQ7018The queue manager operation cannot be completed. Severity: 20 : Error Explanation: An attempt has been made to perform an operation on a queue manager. Resources required to perform the operation are not available. AMQ7019An error occurred while creating the directory structure for the new queue manager. Severity: 40 : Stop Error Explanation: During creation of the queue manager an error occurred while trying to create a file or directory. Response: Identify why the queue manager files cannot be created. It is probable that there is insufficient space on the specified disk, or that there is a problem with access control. Correct the problem and submit the command again. AMQ7020The operation was carried out, but one or more transactions remain in-doubt. Severity: 10 : Warning Explanation: The queue manager tried to resolve all internally coordinated transactions which are in-doubt. In-doubt transactions still remain after the queue manager has attempted to deliver the outcome of these transactions to the resource managers concerned. Transactions remain in-doubt when the queue manager cannot deliver the outcome of the transaction to each of the participating resource managers. For example, a resource manager may not be available at this time. Response: Use the DSPMQTRN command to display the remaining in-doubt transactions. AMQ7020 (iSeries)The operation was carried out, but one or more transactions remain in-doubt. Severity: 10 : Warning Explanation: The queue manager tried to resolve all internally coordinated transactions which are in-doubt. In-doubt transactions still remain after the queue manager has attempted to deliver the outcome of these transactions to the resource managers concerned. Transactions remain in-doubt when the queue manager cannot deliver the outcome of the transaction to each of the participating resource managers. For example, a resource manager may not be available at this time. Response: Use the Work with Transactions (WRKMQMTRN) command to display the remaining in-doubt transactions. AMQ7021An error occurred while deleting the directory structure for the queue manager. Severity: 40 : Stop Error Explanation: While deleting the queue manager, an error occurred deleting a file or directory. The queue manager may not have been completely deleted. Response: Follow problem determination procedures to identify the file or directory and to complete deletion of the queue manager. AMQ7022The resource manager identification number is not recognized. Severity: 20 : Error Explanation: The identification number of the resource manager you supplied was not recognized. Response: Ensure that you entered a valid resource manager identification number. Use the DSPMQTRN command to display a list of resource managers and their identification numbers. AMQ7023The resource manager was in an invalid state. Severity: 20 : Error Explanation: The resource manager, the identification number of which you supplied, was in an invalid state. Response: Ensure that you entered the correct resource manager identification number. Use the DSPMQTRN command to display a list of resource managers and their identification numbers. A resource manager is in an invalid state, if it is still available to resolve the transaction, use the -a optional flag to resolve this and all other internally coordinated in-doubt transactions. AMQ7024Arguments supplied to a command are not valid. Severity: 20 : Error Explanation: You supplied arguments to a command that it could not interpret. It is probable that you specified a flag not accepted by the command, or that you included extra flags. Response: Correct the command and submit it again. Additional information on the arguments causing the error may be found in the error logs for the queue, or queue manager, referenced in the command. AMQ7025Error in the descriptive text argument (-c parameter) of the crtmqm command. Severity: 40 : Stop Error Explanation: The descriptive text you supplied to the crtmqm command was in error. Response: Correct the descriptive text argument and submit the command again. AMQ7026A principal or group name was invalid. Severity: 40 : Stop Error Explanation: You specified the name of a principal or group which does not exist. Response: Correct the name and resubmit the request. AMQ7027Argument supplied to command is invalid. Severity: 20 : Error Explanation: The argument was supplied to the command which could not be interpreted. This argument is either not accepted by the command, or an extra flag has been included. Response: Correct the command and submit it again. AMQ7028The queue manager is not available for use. Severity: 40 : Stop Error Explanation: You have requested an action that requires the queue manager running, however, the queue manager is not currently running. Response: Start the required queue manager and submit the command again. AMQ7030Quiesce request accepted. The queue manager will stop when all outstanding work is complete. Severity: 0 : Information Explanation: You have requested that the queue manager end when there is no more work for it. In the meantime, it will refuse new applications that attempt to start, although it allows those already running to complete their work. Response: None. AMQ7031The queue manager is stopping. Severity: 40 : Stop Error Explanation: You issued a command that requires the queue manager running, however, it is currently in the process of stopping. The command cannot be run. Response: None AMQ7041Object already exists. Severity: 40 : Stop Error Explanation: A Define Object operation was performed, but the name selected for the object is already in use by an object that is unknown to WebSphere MQ. The object name selected by MQ was , in directory , of object type . Response: Remove the conflicting object from the MQ system, then try the operation again. AMQ7042Media image not available for object of type . Severity: 20 : Error Explanation: The media image for object , type , is not available for media recovery. A log file containing part of the media image cannot be accessed. Response: A previous message indicates which log file could not be accessed. Restore a copy of the log file and all subsequent log files from backup. If this is not possible, you must delete the object instead. AMQ7042 (iSeries)Media image not available for object . Severity: 20 : Error Explanation: The media image for object , type , is not available for media recovery. A log file containing part of the media image cannot be accessed. Response: A previous message indicates which log file could not be accessed. Restore a copy of the log file and all subsequent log files from backup. If this is not possible, you must delete the object instead. AMQ7044Media recovery not allowed. Severity: 20 : Error Explanation: Media recovery is not possible on a queue manager using a circular log. Damaged objects must be deleted on such a queue manager. Response: None. AMQ7047An unexpected error was encountered by a command. Severity: 40 : Stop Error Explanation: An internal error occurred during the processing of a command. Response: Follow problem determination procedures to identify the cause of the error. AMQ7048The queue manager name is either not valid or not known Severity: 40 : Stop Error Explanation: Either the specified queue manager name does not conform to the rules required by WebSphere MQ or the queue manager does not exist. The rules for naming MQ objects are detailed in the WebSphere MQ Command Reference. Response: Correct the name and submit the command again. AMQ7053The transaction has been committed. Severity: 0 : Information Explanation: The prepared transaction has been committed. Response: None. AMQ7054The transaction has been backed out. Severity: 0 : Information Explanation: The prepared transaction has been backed out. Response: None. AMQ7055The transaction number is not recognized. Severity: 20 : Error Explanation: The number of the transaction you supplied was not recognized as belonging to an in-doubt transaction. Response: Ensure that you entered a valid transaction number. It is possible that the transaction number you entered corresponds to a transaction which was committed or backed out before you issued the command to resolve it. AMQ7056Transaction number ,. Severity: 0 : Information Explanation: This message is used to report the number of an in-doubt transaction. Response: None. AMQ7059An error has occurred reading an INI file. Severity: 20 : Error Explanation: An error has occurred when reading the MQS.INI file or a queue manager QM.INI file. Response: If you have been changing the INI file content check and correct the change. If you have not changed the INI file, use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ7059 (Windows)An error occurred when reading the configuration data. Severity: 20 : Error Explanation: An error has occurred when reading the configuration data. Response: If you have changed the configuration data, check and correct the change. If you have not changed the configuration data, use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ7060An error has occurred locking an INI file. Severity: 20 : Error Explanation: An error has occurred locking the MQS.INI file or a queue manager QM.INI file. Response: If you have been changing the INI file permissions check and correct the change. If you have not changed the INI file, use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ7060 (Windows)An error has occurred locking the configuration data. Severity: 20 : Error Explanation: An error has occurred locking the configuration data. Response: If you have changed the configuration data permissions, check and correct the change. If you have not changed the configuration data, use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ7061An expected stanza in an INI file is missing or contains errors. Severity: 20 : Error Explanation: An expected stanza is missing from the MQS.INI file or a queue manager QM.INI file or the stanza contains errors. Response: If you have been changing the INI file content check and correct the change. AMQ7061 (Windows)An expected stanza in the configuration data is missing or contains errors. Severity: 20 : Error Explanation: An expected stanza is missing from the configuration data or the stanza contains errors. Response: If you have changed the configuration data, check and correct the change. AMQ7062Unable to access an INI file. Severity: 20 : Error Explanation: Access to the MQS.INI file or a queue manager QM.INI file is denied. Response: If you have been changing the INI file permissions check and correct the change. AMQ7062 (Windows)Unable to access the configuration data. Severity: 20 : Error Explanation: Access to the configuration data is denied. Response: If you have changed the configuration data permissions, check and correct the change. AMQ7063An INI file is missing. Severity: 20 : Error Explanation: The MQS.INI file or a queue manager QM.INI file is missing. Response: If you have been changing the INI file recover the previous file and retry the operation. AMQ7063 (Windows)Configuration data is missing. Severity: 20 : Error Explanation: The configuration data for WebSphere MQ is missing. Response: If you have changed the configuration data, recover the previous configuration data and retry the operation. AMQ7064Log path not valid or inaccessible. Severity: 40 : Stop Error Explanation: The supplied log path could not be used by the queue manager. Possible reasons for this include the path not existing, the queue manager not being able to write to the path, or the path residing on a remote device. Response: Ensure that the log path exists and that the queue manager has authority to read and write to it. If the queue manager already exists, ensure that the LogPath attribute in the queue manager's configuration file matches the intended log path. AMQ7064 (iSeries)Auxiliary storage pool identifier not found. Explanation: The auxiliary storage pool identifier supplied does not exist on the system and could not be used by the queue manager to create a journal receiver. Response: Specify *SYSTEM, or the identifier of an existing auxiliary storage pool and try the request again. You can use WRKDSKSTS to check the assignment of disk units to auxiliary storage pools. AMQ7065Insufficient space on disk. Severity: 40 : Stop Error Explanation: The operation cannot be completed due to shortage of disk space. Response: Either make more disk space available, or reduce the disk requirements of the command you issued. AMQ7066There are no prepared transactions. Severity: 10 : Warning Explanation: There are no prepared transactions to be resolved. Response: None. AMQ7068Authority file contains an authority stanza that is not valid. Severity: 40 : Stop Error Explanation: A syntax error has been found in one of the files containing authorization information for the queue manager. Response: Correct the contents of the incorrect authorization file by editing it. AMQ7069The queue manager was created successfully, but cannot be made the default. Severity: 40 : Stop Error Explanation: The queue manager was defined to be the default queue manager for the machine when it was created. However, although the queue manager has been created, an error occurred trying to make it the default. There may not be a default queue manager defined for the machine at present. Response: There is probably a problem with the machine-wide ini file. Verify the existence of the file, its access permissions, and its contents. If its backup file exists, reconcile the contents of the two files and then delete the backup. Finally, either update the machine-wide ini file by hand to specify the desired default queue manager, or delete and recreate the queue manager. AMQ7069 (Windows)The queue manager was created successfully, but cannot be made the default. Severity: 40 : Stop Error Explanation: The queue manager was defined to be the default queue manager for the machine when it was created. However, although the queue manager has been created, an error occurred trying to make it the default. There may not be a default queue manager defined for the machine at present. Response: There is probably a problem with the configuration data. Update the configuration data to specify the desired default queue manager, or delete and recreate the queue manager. AMQ7072Invalid QM.INI file stanza. Refer to the error log for more information. Severity: 40 : Stop Error Explanation: An invalid QM.INI file stanza was found. Refer to the error log for more information. Response: Correct the error and then retry the operation. AMQ7072 (Windows)Stanza not valid. Refer to the error log for more information. Severity: 40 : Stop Error Explanation: A stanza that is not valid was found. Refer to the error log for more information. Response: Correct the error and retry the operation. AMQ7073Log size not valid. Severity: 40 : Stop Error Explanation: Either the number of log files or the size of the log files was outside the accepted values. Response: Make sure that the log parameters you enter lie within the valid range. AMQ7074Unknown stanza key on line of ini file . Severity: 10 : Warning Explanation: Line of the configuration file contained a stanza called . This stanza is not recognized. Response: Check the contents of the file and retry the operation. AMQ7074 (iSeries)Unknown stanza key. Severity: 10 : Warning Explanation: Line of the configuration file contained a stanza key . This stanza is not recognized. Response: Check the contents of the file and retry the operation. AMQ7074 (Windows)Unknown stanza key at in the configuration data. Severity: 10 : Warning Explanation: Key contained a stanza called . This stanza is not recognized. Response: Check the contents of the configuration data and retry the operation. AMQ7075Unknown attribute in ini file. Severity: 10 : Warning Explanation: Line of the configuration file contained an attribute called that is not valid. This attribute is not recognized in this context. Response: Check the contents of the file and retry the operation. AMQ7075 (Windows)Unknown attribute at in the configuration data. Severity: 10 : Warning Explanation: Key in the configuration data contained an attribute called that is not valid. This attribute is not recognized in this context. Response: Check the contents of the configuration data and retry the operation. AMQ7076Invalid value for attribute in ini file. Severity: 10 : Warning Explanation: Line of the configuration file contained value that is not valid for the attribute . Response: Check the contents of the file and retry the operation. AMQ7076 (Windows)Value not valid for attribute at in the configuration data. Severity: 10 : Warning Explanation: Key in the configuration data contained value that is not valid for the attribute . Response: Check the contents of the configuration data and retry the operation. AMQ7077You are not authorized to perform the requested operation. Severity: 40 : Stop Error Explanation: You tried to issue a command for the queue manager. You are not authorized to perform the command. Response: Contact your system administrator to perform the command for you. Alternatively, request authority to perform the command from your system administrator. AMQ7078You entered an object type that is invalid with a generic profile name. Severity: 40 : Stop Error Explanation: You entered an object type of *ALL or *MQM and an object name that contains generic characters, this is an invalid combination. Response: Correct the command and submit it again. AMQ7080No objects processed. Severity: 10 : Warning Explanation: No objects were processed, either because no objects matched the criteria given, or because the objects found did not require processing. Response: None. AMQ7081Object , type recreated. Severity: 0 : Information Explanation: The object , type was recreated from its media image. Response: None. AMQ7082Object , type is not damaged. Severity: 10 : Warning Explanation: Object , type cannot be recreated since it is not damaged. Response: None AMQ7083A resource problem was encountered by a command. Severity: 20 : Error Explanation: The command failed due to a resource problem. Possible causes include the log being full or the command running out of memory. Response: Look at the previous messages to diagnose the problem. Rectify the problem and retry the operation. AMQ7084Object , type damaged. Severity: 20 : Error Explanation: The object , type was damaged. The object must be deleted or, if the queue manager supports media recovery, recreated from its media image. Response: Delete the object or recreate it from its media image. AMQ7085Object , type not found. Severity: 20 : Error Explanation: Object , type cannot be found. Response: None. AMQ7086Media image for object , type recorded. Severity: 0 : Information Explanation: The media image for object , type , defined in Queue Manager , has been recorded. Response: None. AMQ7087Object , type is a temporary object Severity: 20 : Error Explanation: Object , type is a temporary object. Media recovery operations are not permitted on temporary objects. Response: None. AMQ7088Object , type in use. Severity: 20 : Error Explanation: Object , type is in use. Either an application has it open or, if it is a local queue, there are uncommitted messages on it. Response: Ensure that the object is not opened by any applications, and that there are no uncommitted messages on the object, if it is a local queue. Then, retry the operation. AMQ7089Media recovery already in progress. Severity: 20 : Error Explanation: Another media recovery operation is already in progress. Only one media recovery operation is permitted at a time. Response: Wait for the existing media recovery operation to complete and retry the operation. AMQ7090 (iSeries)The queue manager CCSID is not valid. Severity: 40 : Stop Error Explanation: The CCSID to be used by the QMGR is not valid for the iSeries platform. The CCSID encoding must be a valid EBCDIC value. Response: Check that the CCSID that you have entered is a valid EBCDIC value. AMQ7090 (Windows)The queue manager CCSID is not valid. Severity: 40 : Stop Error Explanation: The CCSID to be used by the QMGR is not valid, because: 1) It is a DBCS CCSID. 2) The CCSID encoding is not ASCII or ASCII related. EBCDIC or UCS2 encodings are not valid on this machine. 3) The CCSID encoding is unknown. Response: Check the CCSID is valid for the machine on which you are working. AMQ7091You are performing authorization for the queue manager, but you specified an object name. Severity: 40 : Stop Error Explanation: Modification of authorizations for a queue manager can be performed only from that queue manager. You must not specify an object name. Response: Correct the command and submit it again. AMQ7092An object name is required but you did not specify one. Severity: 40 : Stop Error Explanation: The command needs the name of an object, but you did not specify one. Response: Correct the command and submit it again. AMQ7093An object type is required but you did not specify one. Severity: 40 : Stop Error Explanation: The command needs the type of the object, but you did not specify one. Response: Correct the command and submit it again. AMQ7094You specified an object type that is not valid, or more than one object type. Severity: 40 : Stop Error Explanation: Either the type of object you specified was not valid, or you specified multiple object types on a command which supports only one. Response: Correct the command and submit it again. AMQ7095An entity name is required but you did not specify one. Severity: 40 : Stop Error Explanation: The command needs one or more entity names, but you did not specify any. Entities can be principals or groups. Response: Correct the command and submit it again. AMQ7096An authorization specification is required but you did not provide one. Severity: 40 : Stop Error Explanation: The command sets the authorizations on WebSphere MQ objects. However you did not specify which authorizations are to be set. Response: Correct the command and submit it again. AMQ7097You gave an authorization specification that is not valid. Severity: 40 : Stop Error Explanation: The authorization specification you provided to the command contained one or more items that could not be interpreted. Response: Correct the command and submit it again. AMQ7098The command accepts only one entity name. You specified more than one. Severity: 40 : Stop Error Explanation: The command can accept only one principal or group name. You specified more than one. Response: Correct the command and submit it again. AMQ7099Entity has the following authorizations for object : Severity: 0 : Information Explanation: Informational message. The list of authorizations follows. Response: None. AMQ7104Resource manager has prepared. Severity: 0 : Information Explanation: This message reports the state of a resource manager with respect to an in-doubt transaction. Response: None. AMQ7105Resource manager has committed. Severity: 0 : Information Explanation: This message reports the state of a resource manager with respect to an in-doubt transaction. Response: None. AMQ7106Resource manager has rolled back. Severity: 0 : Information Explanation: This message reports the state of a resource manager with respect to an in-doubt transaction. Response: None. AMQ7107Resource manager is . Severity: 0 : Information Explanation: This message reports the identification number and name of a resource manager. Response: None. AMQ7108Any in-doubt transactions have been resolved. Severity: 0 : Information Explanation: All, if there were any, of the internally coordinated transactions which were in-doubt, have now been resolved. This message reports successful completion of the RSVMQTRN command when the -a option is used. Response: None. AMQ7108 (iSeries)Any in-doubt transactions have been resolved. Severity: 0 : Information Explanation: All, if there were any, of the internally coordinated transactions which were in-doubt, have now been resolved. Response: None. AMQ7109A decision on behalf of the unavailable resource manager has been delivered. Severity: 0 : Information Explanation: A decision for an internally coordinated transaction which was in-doubt, has now been delivered on behalf of the unavailable resource manager. This message reports successful completion of the RSVMQTRN command when the -r option is used. Response: None. AMQ7110Media image for the syncfile recorded. Severity: 0 : Information Explanation: The media image for the syncfile has been recorded. Response: None. AMQ7111Resource manager has participated. Severity: 0 : Information Explanation: This message reports the state of a resource manager with respect to an in-doubt transaction. Response: None. AMQ7112Transaction number , has encountered an error. Severity: 0 : Information Explanation: This message is used to report the number of an in-doubt transaction which has encountered an error with one or more resource managers. Response: Refer to the queue manager error log for more information about which resource managers are in error. Ensure that the resource managers that were in error, are working correctly, restart the queue manager. If the problem persists, use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ7113The Database Name argument, -rn, is missing from the command crtmqm Severity: 20 : Error Explanation: The required flag, -rn, was omitted from the command crtmqm Response: Add the flag and associated database name and submit it again. AMQ7114The Database Password argument, -rp, is missing from the command crtmqm Severity: 20 : Error Explanation: The required flag, -rp, was omitted from the command crtmqm Response: Add the flag and associated database password and submit it again. AMQ7115The Database Type argument, -rt, is missing from the command crtmqm Severity: 20 : Error Explanation: The required flag, -rt, was omitted from the command crtmqm Response: Add the flag and associated database type and submit it again AMQ7116The Database Type argument, -rt, is greater than 8 characters long Severity: 20 : Error Explanation: The argument supplied with the flag -rt, is greater than 8 characters long Response: Reduce the length of the database type argument and submit it again AMQ7117The MSD shared library failed to load. Severity: 20 : Error Explanation: The MSD shared library was either not located or failed to load correctly. Response: Ensure that the database type is specified correctly when creating a queue manager since this is used to form the name of the shared library to be loaded. Further information on the failure may be found in the FFST logs. Also, ensure that ensure that the MSD shared library is installed correctly. AMQ7120The Trial Period license for this copy of WebSphere MQ has expired. Severity: 20 : Error Explanation: This copy of WebSphere MQ was licensed to be used in trial mode for a limited period only. This period has expired. Response: Install a Production license for this copy of WebSphere MQ. AMQ7121The trial period for this copy of WebSphere MQ has now expired. Severity: 20 : Error Explanation: This copy of WebSphere MQ was licensed for a limited period only. This period has now expired. Response: Install a Production license for this copy of WebSphere MQ. AMQ7122The Trial Period License Agreement was not accepted. Severity: 10 : Warning Explanation: When the Trial Period License Agreement is displayed, the user must accept it before this copy of WebSphere MQ can be used. Response: Submit the command again and accept the agreement. AMQ7123There is one day left in the trial period for this copy of WebSphere MQ. Severity: 0 : Information Explanation: This copy of WebSphere MQ is licensed for a limited period only. Response: None. AMQ7124This is the final day of the trial period for this copy of WebSphere MQ. Severity: 10 : Warning Explanation: This copy of WebSphere MQ is licensed for a limited period only. Response: Install a Production license for this copy of WebSphere MQ. AMQ7125There are days left in the trial period for this copy of WebSphere MQ. Severity: 0 : Information Explanation: This copy of WebSphere MQ is licensed for a limited period only. Response: None. AMQ7126This copy of WebSphere MQ is now running in Production mode. Severity: 0 : Information Explanation: A Production license has been installed for this copy of WebSphere MQ. Response: None. AMQ7127 Press Enter when you have read the messages Severity: 0 : Information Explanation: One or more messages have been displayed. They will disappear when the user presses the Enter key. Response: Press the Enter key when the messages are no longer required. AMQ7128No license installed for this copy of WebSphere MQ. Severity: 20 : Error Explanation: The installation of WebSphere MQ is invalid since no Production, Beta, or Trial Period license has been installed. Response: Check that the installation steps described in the Quick Beginnings book have been followed, and if the problem persists contact your IBM service representative. AMQ7129The trial period for this copy of WebSphere MQ has already been started. Severity: 0 : Information Explanation: This copy of WebSphere MQ is licensed for a limited period only and the trial period has been started previously. Response: None. AMQ7130This copy of WebSphere MQ is running in Production mode. Severity: 0 : Information Explanation: A Production license has been installed for this copy of WebSphere MQ. A beta or trial period cannot be started. Response: None. AMQ7131International License Agreement for Evaluation of Programs Part 1 - General Terms PLEASE READ THIS AGREEMENT CAREFULLY BEFORE USING THE PROGRAM. IBM WILL LICENSE THE PROGRAM TO YOU ONLY IF YOU FIRST ACCEPT THE TERMS OF THIS AGREEMENT. BY USING THE PROGRAM YOU AGREE TO THESE TERMS. IF YOU DO NOT AGREE TO THE TERMS OF THIS AGREEMENT, PROMPTLY RETURN THE UNUSED PROGRAM TO IBM. Severity: 0 : Information Explanation: This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only. Response: None. AMQ7132 The Program is owned by International Business Machines Corporation or one of its subsidiaries (IBM) or an IBM supplier, and is copyrighted and licensed, not sold. The term "Program" means the original program and all whole or partial copies of it. A Program consists of machine-readable instructions, its components, data, audio-visual content (such as images, text, recordings, or pictures), and related licensed materials. Severity: 0 : Information Explanation: This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only. Response: None. AMQ7133 This Agreement includes Part 1 - General Terms and Part 2 - Country Unique Terms and is the complete agreement regarding the use of this Program, and replaces any prior oral or written communications between you and IBM. The terms of Part 2 may replace or modify those of Part 1. Severity: 0 : Information Explanation: This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only. Response: None. AMQ7134 1. License Use of the Program IBM grants you a nonexclusive, nontransferable license to use the Program. You may 1) use the Program only for internal evaluation, testing or demonstration purposes, on a trial or "try-and-buy" basis and 2) make and install a reasonable number of copies of the Program in support of such use, unless IBM identifies a specific number of copies in the documentation accompanying the Program. The terms of this license apply to each copy you make. You will reproduce the copyright notice and any other legends of ownership on each copy, or partial copy, of the Program. Severity: 0 : Information Explanation: This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only. Response: None. AMQ7135 THE PROGRAM MAY CONTAIN A DISABLING DEVICE THAT WILL PREVENT IT FROM BEING USED UPON EXPIRATION OF THIS LICENSE. YOU WILL NOT TAMPER WITH THIS DISABLING DEVICE OR THE PROGRAM. YOU SHOULD TAKE PRECAUTIONS TO AVOID ANY LOSS OF DATA THAT MIGHT RESULT WHEN THE PROGRAM CAN NO LONGER BE USED. Severity: 0 : Information Explanation: This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only. Response: None. AMQ7136 You will 1) maintain a record of all copies of the Program and 2) ensure that anyone who uses the Program does so only for your authorized use and in compliance with the terms of this Agreement. You may not 1) use, copy, modify or distribute the Program except as provided in this Agreement; 2) reverse assemble, reverse compile, or otherwise translate the Program except as specifically permitted by law without the possibility of contractual waiver; or 3) sublicense, rent or lease the Program. Severity: 0 : Information Explanation: This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only. Response: None. AMQ7137 This license begins with your first use of the Program and ends 1) as of the duration or date specified in the documentation accompanying the Program or 2) when the Program automatically disables itself. Unless IBM specifies in the documentation accompanying the Program that you may retain the Program (in which case, an additional charge may apply), you will destroy the Program and all copies made of it within ten days of when this license ends. Severity: 0 : Information Explanation: This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only. Response: None. AMQ7138 2. No Warranty SUBJECT TO ANY STATUTORY WARRANTIES WHICH CANNOT BE EXCLUDED, IBM MAKES NO WARRANTIES OR CONDITIONS EITHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, THE WARRANTY OF NON-INFRINGEMENT AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, REGARDING THE PROGRAM OR TECHNICAL SUPPORT, IF ANY. IBM MAKES NO WARRANTY REGARDING THE CAPABILITY OF THE PROGRAM TO CORRECTLY PROCESS, PROVIDE AND/OR RECEIVE DATE DATA WITHIN AND BETWEEN THE 20TH AND 21ST CENTURIES. This exclusion also applies to any of IBM's subcontractors, suppliers or program developers (collectively called "Suppliers"). Manufacturers, suppliers, or publishers of non-IBM Programs may provide their own warranties. Severity: 0 : Information Explanation: This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only. Response: None. AMQ7139 3. Limitation of Liability NEITHER IBM NOR ITS SUPPLIERS ARE LIABLE FOR ANY DIRECT OR INDIRECT DAMAGES, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST SAVINGS, OR ANY INCIDENTAL, SPECIAL, OR OTHER ECONOMIC CONSEQUENTIAL DAMAGES, EVEN IF IBM IS INFORMED OF THEIR POSSIBILITY. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THE ABOVE EXCLUSION OR LIMITATION MAY NOT APPLY TO YOU. Severity: 0 : Information Explanation: This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only. Response: None. AMQ7140 4. General Nothing in this Agreement affects any statutory rights of consumers that cannot be waived or limited by contract. Severity: 0 : Information Explanation: This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only. Response: None. AMQ7141 IBM may terminate your license if you fail to comply with the terms of this Agreement. If IBM does so, you must immediately destroy the Program and all copies you made of it. You may not export the Program. Neither you nor IBM will bring a legal action under this Agreement more than two years after the cause of action arose unless otherwise provided by local law without the possibility of contractual waiver or limitation. Neither you nor IBM is responsible for failure to fulfill any obligations due to causes beyond its control. There is no additional charge for use of the Program for the duration of this license. IBM does not provide program services or technical support, unless IBM specifies otherwise. Severity: 0 : Information Explanation: This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only. Response: None. AMQ7142Reply 'yes' to accept the Agreement. Reply 'no' if you do not agree to the terms of the Agreement. Reply 'no' and submit the command again, if you want to read the Agreement again. Severity: 0 : Information Explanation: The Trial Period License Agreement has been displayed to the user and the user should now accept or reject the Agreement. Response: Reply 'yes' or 'no' and press 'Enter'. AMQ7143 Press Enter to continue Severity: 0 : Information Explanation: Part of the Trial Period License Agreement has been displayed to the user. The user should press the Enter key to indicate that they are ready for the next part of the Agreement to be displayed. Response: Press the Enter key when ready for the next part of the Agreement to be displayed. AMQ7144 The laws of the country in which you acquire the Program govern this Agreement, except 1) in Australia, the laws of the State or Territory in which the transaction is performed govern this Agreement; 2) in Albania, Armenia, Belarus, Bosnia/Herzegovina, Bulgaria, Croatia, Czech Republic, Georgia, Hungary, Kazakhstan, Kirghizia, Former Yogoslav Republic of Macedonia (FYROM), Moldova, Poland, Romania, Russia, Slovak Republic, Slovenia, Ukraine, and Federal Republic of Yugoslavia, the laws of Austria govern this Agreement; 3) in the United Kingdom, all disputes relating to this Agreement will be governed by English law and will be submitted to the exclusive jurisdiction of the English courts; 4) in Canada, the laws of the Province of Ontario govern this Agreement; and 5) in the United States and Puerto Rico, and People's Republic of China, the laws of the State of New York govern this Agreement. Severity: 0 : Information Explanation: This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only. Response: None. AMQ7145 Part 2 - Country Unique Terms AUSTRALIA: No Warranty (Section 2): The following paragraph is added to this Section: Although IBM specifies that there are no warranties, you may have certain rights under the Trade Practices Act 1974 or other legislation and are only limited to the extent permitted by the applicable legislation. Limitation of Liability (Section 3): The following paragraph is added to this Section: Severity: 0 : Information Explanation: This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only. Response: None. AMQ7146 Where IBM is in breach of a condition or warranty implied by the Trade Practices Act 1974, IBM's liability is limited to the repair or replacement of the goods, or the supply of equivalent goods. Where that condition or warranty relates to right to sell, quiet possession or clear title, or the goods are of a kind ordinarily acquired for personal, domestic or household use or consumption, then none of the limitations in this paragraph apply. Severity: 0 : Information Explanation: This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only. Response: None. AMQ7147 NEW ZEALAND: No Warranty (Section 2): The following paragraph is added to this Section: Although IBM specifies that there are no warranties, you may have certain rights under the Consumer Guarantees Act 1993 or other legislation which cannot be excluded or limited. The Consumer Guarantees Act 1993 will not apply in respect of any goods or services which IBM provides, if you require the goods and services for the purposes of a business as defined in the Act. Severity: 0 : Information Explanation: This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only. Response: None. AMQ7148 Limitation of Liability (Section 3): The following paragraph is added to this Section: Where products or services are not acquired for the purposes of a business as defined in the Consumer Guarantees Act 1993, the limitations in this Section are subject to the limitations in that Act. Severity: 0 : Information Explanation: This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only. Response: None. AMQ7149 GERMANY: No Warranty (Section 2): The following paragraphs are added to this Section: The minimum warranty period for Programs is six months. In case a Program is delivered without specifications, we will only warrant that the Program information correctly describes the Program and that the Program can be used according to the Program information. You have to check the usability according to the Program information within the "money-back guaranty" period. Limitation of Liability (Section 3): The following paragraph is added to this Section: The limitations and exclusions specified in the Agreement will not apply to damages caused by IBM with fraud or gross negligence, and for express warranty. Severity: 0 : Information Explanation: This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only. Response: None. AMQ7150 INDIA: General (Section 4): The following replaces the fourth paragraph of this Section: If no suit or other legal action is brought, within two years after the cause of action arose, in respect of any claim that either party may have against the other, the rights of the concerned party in respect of such claim will be forfeited and the other party will stand released from its obligations in respect of such claim. Severity: 0 : Information Explanation: This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only. Response: None. AMQ7151 IRELAND: No Warranty (Section 2): The following paragraph is added to this Section: Except as expressly provided in these terms and conditions, all statutory conditions, including all warranties implied, but without prejudice to the generality of the foregoing all warranties implied by the Sale of Goods Act 1893 or the Sale of Goods and Supply of Services Act 1980 are hereby excluded. ITALY: Limitation of Liability (Section 3): This section is replaced by the following: Unless otherwise provided by mandatory law, IBM is not liable for any damages which might arise. Severity: 0 : Information Explanation: This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only. Response: None. AMQ7152 UNITED KINGDOM: Limitation of Liability (Section 3): The following paragraph is added to this Section at the end of the first paragraph: The limitation of liability will not apply to any breach of IBM's obligations implied by Section 12 of the Sales of Goods Act 1979 or Section 2 of the Supply of Goods and Services Act 1982. Severity: 0 : Information Explanation: This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only. Response: None. AMQ7153A license could not be installed for this copy of WebSphere MQ. Severity: 20 : Error Explanation: A Production, Beta or Trial Period license could not be installed for this copy of WebSphere MQ. This is because the 'nodelock' file in the 'qmgrs/@SYSTEM' directory could not be created or updated. Response: Check the ownership and permissions of the 'qmgrs/@SYSTEM' directory. AMQ7154The Production license for this copy of WebSphere MQ has expired. Severity: 20 : Error Explanation: The production license for this copy of WebSphere MQ has an expiry date. This date has been passed. Response: Contact your IBM support center. AMQ7155License file not found or not valid. Severity: 20 : Error Explanation: The program requires that the file is present, available and is a valid license file. Response: Check that the installation steps described in the Quick Beginnings book have been followed, and if the problem persists contact your IBM service representative. AMQ7156This copy of WebSphere MQ is already running in Production mode. Severity: 0 : Information Explanation: A Production license has previously been installed for this copy of WebSphere MQ. Response: None. AMQ7157The Production license is not valid for this copy of WebSphere MQ. Severity: 20 : Error Explanation: The license has been installed but it is not a valid production license for this copy of WebSphere MQ. Response: Submit the SETMQPRD command again specifying the name of a valid production license. AMQ7158The Trial Period license is not valid for this copy of WebSphere MQ. Severity: 20 : Error Explanation: The license has been installed but it is not a valid trial period license for this copy of WebSphere MQ. Response: Check that the correct version of the file is available. AMQ7159A FASTPATH application has ended unexpectedly. Severity: 10 : Warning Explanation: A FASTPATH application has ended in a way which did not allow the queue manager to clean up the resources owned by that application. Any resources held by the application can only be released by stopping and restarting the queue manager. Response: Investigate why the application ended unexpectedly. Avoid ending FASTPATH applications in a way which prevents WebSphere MQ from releasing resources held by the application. AMQ7160Queue Manager Object Severity: 0 : Information AMQ7161Object Catalogue Severity: 0 : Information AMQ7162The setmqaut command completed successfully. Severity: 0 : Information AMQ7163 (iSeries)WebSphere MQ job started for . Severity: 0 : Information Explanation: The job's PID is the CCSID is . The job name is . Response: None AMQ7164 (iSeries)WebSphere MQ is waiting for a job to start. Severity: 0 : Information Explanation: WebSphere MQ has been waiting seconds to start job for Queue Manager: Response: Check that the job queue that is associated with job description is not held, and that the subsystem that is associated with the job queue is active. AMQ7165The Beta license for this copy of WebSphere MQ has expired. Severity: 20 : Error Explanation: This copy of WebSphere MQ was licensed to be used for Beta testing for a limited period only. This period has expired. Response: Install a Production license for this copy of WebSphere MQ. AMQ7166The Beta period for this copy of WebSphere MQ has now expired. Severity: 20 : Error Explanation: This copy of WebSphere MQ was licensed for a limited period only. This period has now expired. Response: Install a Production license for this copy of WebSphere MQ. AMQ7167The 'Early Release of Programs License Agreement' was not accepted. Severity: 10 : Warning Explanation: When the IBM International License Agreement for Early Release of Programs is displayed, the user must accept it before this copy of WebSphere MQ can be used. Response: Submit the command again and accept the agreement. AMQ7168There is one day left in the Beta test period for this copy of WebSphere MQ. Severity: 0 : Information Explanation: This copy of WebSphere MQ is licensed for a limited period only. Response: None. AMQ7169This is the final day of the Beta test period for this copy of WebSphere MQ. Severity: 10 : Warning Explanation: This copy of WebSphere MQ is licensed for a limited period only. Response: Install a Production license for this copy of WebSphere MQ. AMQ7170 (iSeries)Option is not valid for this transaction. Severity: 20 : Error Explanation: The Resolve option is not valid for external transactions. The Commit and Backout options are not valid for internal transactions. Response: Select a different option for this transaction. AMQ7171IBM International License Agreement for Early Release of Programs Part 1 - General Terms PLEASE READ THIS AGREEMENT CAREFULLY BEFORE USING THE PROGRAM. IBM WILL LICENSE THE PROGRAM TO YOU ONLY IF YOU FIRST ACCEPT THE TERMS OF THIS AGREEMENT. BY USING THE PROGRAM YOU AGREE TO THESE TERMS. IF YOU DO NOT AGREE TO THE TERMS OF THIS AGREEMENT, PROMPTLY RETURN THE UNUSED PROGRAM TO IBM. Severity: 0 : Information Explanation: This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only. Response: None. AMQ7172 The Program is owned by International Business Machines Corporation or one of its subsidiaries (IBM) or an IBM supplier, and is copyrighted and licensed, not sold. The term "Program" means the original program and all whole or partial copies of it. A Program consists of machine-readable instructions, its components, data, audio-visual content (such as images, text, recordings, or pictures), and related licensed materials. Severity: 0 : Information Explanation: This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only. Response: None. AMQ7173 The term "Early Release" means that the Program is not formally released or generally available. The term does not imply that the Program will be formally released or made generally available. IBM does not guarantee that a Program formally released or made generally available will be similar to, or compatible with, Early Release versions. THIS AGREEMENT INCLUDES PART 1 - GENERAL TERMS AND PART 2 - COUNTRY-UNIQUE TERMS AND IS THE COMPLETE AGREEMENT REGARDING THE USE OF THIS PROGRAM, AND REPLACES ANY PRIOR ORAL OR WRITTEN COMMUNICATIONS BETWEEN YOU AND IBM. THE TERMS OF PART 2 MAY REPLACE OR MODIFY THOSE OF PART 1. Severity: 0 : Information Explanation: This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only. Response: None. AMQ7174 1.License Use of the Program IBM grants you a nonexclusive, nontransferable license to use the Program. You may 1) use the Program only for internal evaluation or testing purposes and 2) make and install a reasonable number of copies of the Program in support of such use, unless IBM identifies a specific number of copies in the documentation accompanying the Program. The terms of this license apply to each copy you make. You will reproduce the copyright notice and any other legends of ownership on each copy, or partial copy, of the Program. Severity: 0 : Information Explanation: This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only. Response: None. AMQ7175 THE PROGRAM MAY CONTAIN A DISABLING DEVICE THAT WILL PREVENT IT FROM BEING USED UPON EXPIRATION OF THIS LICENSE. YOU WILL NOT TAMPER WITH THIS DISABLING DEVICE OR THE PROGRAM. YOU SHOULD TAKE PRECAUTIONS TO AVOID ANY LOSS OF DATA THAT MIGHT RESULT WHEN THE PROGRAM CAN NO LONGER BE USED. You will 1) maintain a record of all copies of the Program and 2) ensure that anyone who uses the Program does so only for your authorized use and in compliance with the terms of this Agreement. Severity: 0 : Information Explanation: This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only. Response: None. AMQ7176 You may not 1) use, copy, modify, or distribute the Program except as provided in this Agreement; 2) reverse assemble, reverse compile, or otherwise translate the Program except as specifically permitted by law without the possibility of contractual waiver; or 3) sublicense, rent, or lease the Program. Severity: 0 : Information Explanation: This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only. Response: None. AMQ7177 This license begins with your first use of the Program and ends 1) as of the duration or date specified in the documentation accompanying the Program, 2) when the Program automatically disables itself, or 3) when IBM makes the Program generally available. Unless IBM specifies in the documentation accompanying the the Program that you may retain the Program (in which case, an additional charge may apply), you will destroy the Program and all copies made of it within ten days of when this license ends. Severity: 0 : Information Explanation: This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only. Response: None. AMQ7178 2.No Warranty SUBJECT TO ANY STATUTORY WARRANTIES WHICH CANNOT BE EXCLUDED, IBM MAKES NO WARRANTIES OR CONDITIONS EITHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, THE WARRANTY OF NON-INFRINGEMENT AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, REGARDING THE PROGRAM OR TECHNICAL SUPPORT, IF ANY.. IBM MAKES NO WARRANTY REGARDING THE CAPABILITY OF THE PROGRAM TO CORRECTLY PROCESS, PROVIDE AND/OR RECEIVE DATE DATA WITHIN AND BETWEEN THE 20TH AND 21ST CENTURIES. This exclusion also applies to any of IBM's subcontractors, suppliers or program developers (collectively called "Suppliers"). Manufacturers, suppliers, or publishers of non-IBM Programs may provide their own warranties. Severity: 0 : Information Explanation: This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only. Response: None. AMQ7179 3.Limitation of Liability NEITHER IBM NOR ITS SUPPLIERS ARE LIABLE FOR ANY DIRECT OR INDIRECT DAMAGES, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST SAVINGS, OR ANY INCIDENTAL, SPECIAL, OR OTHER ECONOMIC CONSEQUENTIAL DAMAGES, EVEN IF IBM IS INFORMED OF THEIR POSSIBILITY. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THE ABOVE EXCLUSION OR LIMITATION MAY NOT APPLY TO YOU. 4.Rights In Data You hereby assign to IBM all right, title, and interest (including ownership of copyright) in any data, suggestions, and written materials related to your use of the Program you provide to IBM. If IBM requires it, you will sign an appropriate document to assign such rights. Severity: 0 : Information Explanation: This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only. Response: None. AMQ7180 5.General Nothing in this Agreement affects any statutory rights of consumers that cannot be waived or limited by contract. IBM may terminate your license if you fail to comply with the terms of this Agreement. If IBM does so, you must immediately destroy the Program and all copies you made of it. You may not export the Program. Severity: 0 : Information Explanation: This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only. Response: None. AMQ7181 Neither you nor IBM will bring a legal action under this Agreement more than two years after the cause of action arose unless otherwise provided by local law without the possibility of contractual waiver or limitation. Neither you nor IBM is responsible for failure to fulfill any obligations due to causes beyond its control. There is no additional charge for use of the Program for the duration of this license. Neither of us will charge the other for rights in data or any work performed as a result of this Agreement. IBM does not provide program services or technical support, unless IBM specifies otherwise. Severity: 0 : Information Explanation: This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only. Response: None. AMQ7182 The laws of the country in which you acquire the Program govern this Agreement, except 1) in Australia, the laws of the State or Territory in which the transaction is performed govern this Agreement; 2) in Albania, Armenia, Belarus, Bosnia/Herzegovina, Bulgaria, Croatia, Czech Republic, Georgia, Hungary, Kazakhstan, Kirghizia, Former Yugoslav Republic of Macedonia (FYROM), Moldova, Poland, Romania, Russia, Slovak Republic, Slovenia, Ukraine, and Federal Republic of Yugoslavia, the laws of Austria govern this Agreement; 3) in the United Kingdom, all disputes relating to this Agreement will be governed by English Law and will be submitted to the exclusive jurisdiction of the English courts; 4) in Canada, the laws of the Province of Ontario govern this Agreement; and 5) in the United States and Puerto Rico, and People's Republic of China, the laws of the State of New York govern this Agreement. Severity: 0 : Information Explanation: This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only. Response: None. AMQ7183 Part 2 - Country-unique Terms AUSTRALIA: No Warranty (Section 2): The following paragraph is added to this Section: Although IBM specifies that there are no warranties, you may have certain rights under the Trade Practices Act 1974 or other legislation and are only limited to the extent permitted by the applicable legislation. Limitation of Liability (Section 3): The following paragraph is added to this Section: Where IBM is in breach of a condition or warranty implied by the Trade Practices Act 1974, IBM's liability is limited to the repair or replacement of the goods, or the supply of equivalent goods. Where that condition or warranty relates to right to sell, quiet possession or clear title, or the goods are of a kind ordinarily acquired for personal, domestic or household use or consumption, then none of the limitations in this paragraph apply. Severity: 0 : Information Explanation: This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only. Response: None. AMQ7184 GERMANY: No Warranty (Section 2): The following paragraphs are added to this Section: The minimum warranty period for Programs is six months. In case a Program is delivered without Specifications, IBM will only warrant that the Program information correctly describes the Program and that the Program can be used according to the Program information. You have to check the usability according to the Program information within the "money-back guaranty" period. Limitation of Liability (Section 3): The following paragraph is added to this Section: The limitations and exclusions specified in the Agreement will not apply to damages caused by IBM with fraud or gross negligence, and for express warranty. Severity: 0 : Information Explanation: This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only. Response: None. AMQ7185 INDIA: General (Section 5): The following replaces the fourth paragraph of this Section: If no suit or other legal action is brought, within two years after the cause of action arose, in respect of any claim that either party may have against the other, the rights of the concerned party in respect of such claim will be forfeited and the other party will stand released from its obligations in respect of such claim. Severity: 0 : Information Explanation: This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only. Response: None. AMQ7186 IRELAND: No Warranty (Section 2): The following paragraph is added to this Section: Except as expressly provided in these terms and conditions, all statutory conditions, including all warranties implied, but without prejudice to the generality of the foregoing, all warranties implied by the Sale of Goods Act 1893 or the Sale of Goods and Supply of Services Act 1980 are hereby excluded. Severity: 0 : Information Explanation: This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only. Response: None. AMQ7187 ITALY: Limitation of Liability (Section 3): This Section is replaced by the following: Unless otherwise provided by mandatory law, IBM is not liable for any damages which might arise. Severity: 0 : Information Explanation: This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only. Response: None. AMQ7188 JAPAN: Rights In Data (Section 4): The following paragraph is added to this Section: You also agree to assign to IBM the rights regarding derivative works, as defined in Articles 27 and 28 of the Japanese Copyright Law. You also agree not to exercise your moral rights. Severity: 0 : Information Explanation: This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only. Response: None. AMQ7189 NEW ZEALAND: No Warranty (Section 2): The following paragraph is added to this Section: Although IBM specifies that there are no warranties, you may have certain rights under the Consumer Guarantees Act 1993 or other legislation which cannot be excluded or limited. The Consumer Guarantees Act 1993 will not apply in respect of any goods or services which IBM provides, if you require the goods and services for the purposes of a business as defined in that Act. Limitation of Liability (Section 3): The following paragraph is added to this Section: Where Programs are not acquired for the purposes of a business as defined in the Consumer Guarantees Act 1993, the limitations in this Section are subject to the limitations in that Act. Severity: 0 : Information Explanation: This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only. Response: None. AMQ7190 UNITED KINGDOM: Limitation of Liability (Section 3): The following paragraph is added to this Section at the end of the first paragraph: The limitation of liability will not apply to any breach of IBM's obligations implied by Section 12 of the Sale of Goods Act 1979 or Section 2 of the Supply of Goods and Services Act 1982. Severity: 0 : Information Explanation: This is part of the Early Release of Programs License Agreement (VZ125-5544-01 10/97 (MK002))which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only. Response: None. AMQ7191There are days left in the beta test period for this copy of WebSphere MQ. Severity: 0 : Information Explanation: This copy of WebSphere MQ is licensed for a limited period only. Response: None. AMQ7192The Beta test period for this copy of WebSphere MQ has already been started. Severity: 0 : Information Explanation: This copy of WebSphere MQ is licensed for a limited period only and the Beta test period has been started previously. Response: None. AMQ7193Reply 'yes' to accept the Agreement. Reply 'no' if you do not agree to the terms of the Agreement. Reply 'no' and submit the command again, if you want to read the Agreement again. Severity: 0 : Information Explanation: The IBM International License Agreement for Early Release of Programs has been displayed to the user and the user should now accept or reject the Agreement. Response: Reply 'yes' or 'no' and press 'Enter'. AMQ7194 Press Enter to continue Severity: 0 : Information Explanation: Part of the IBM International License Agreement for Early Release of Programs has been displayed to the user. The user should press the Enter key to indicate that they are ready for the next part of the Agreement to be displayed. Response: Press the Enter key when ready for the next part of the Agreement to be displayed. AMQ7195The Beta test license is not valid for this copy of WebSphere MQ. Severity: 20 : Error Explanation: The license has been installed but it is not a valid trial period license for this copy of WebSphere MQ. Response: Check that the correct version of the file is available. AMQ7196By installing this product, you accept the terms of the International Program License Agreement and the License Information supplied with the product. Severity: 0 : Information Response: None. AMQ7197A production or trial license could not be installed for this copy of WebSphere MQ. Severity: 20 : Error Explanation: This copy of WebSphere MQ is a beta version and cannot be used with a production or trial license. Response: Uninstall the beta version of WebSphere MQ and install the production or trial version. AMQ7198Insufficient license units. Severity: 10 : Warning Explanation: The purchased processor allowance () is less than the number of processors () in this machine. Response: Ensure sufficient license units have been purchased and use the MQ setmqcap command to set the purchased processor allowance for this installation. Refer to the Quick Beginnings book for more information. AMQ7198 (iSeries)Insufficient license units. Severity: 10 : Warning Explanation: The purchased processor allowance for this installation is zero. Response: Ensure sufficient license units have been purchased and use the MQ CHGMQMCAP command to set the purchased processor allowance for this installation. Refer to the Quick Beginnings book for more information. AMQ7199The purchased processor allowance is set to . Severity: 0 : Information Explanation: The purchased processor allowance for this installation has been set to using the MQ setmqcap command. Response: None. AMQ7199 (iSeries)The purchased processor allowance is set to . Severity: 0 : Information Explanation: The purchased processor allowance for this installation has been set to using the MQ CHGMQMCAP command. Response: None. AMQ7200The purchased processor allowance is Severity: 0 : Information Explanation: The purchased processor allowance is currently set to Response: Ensure sufficient license units have been purchased and, if necessary, use the MQ setmqcap command to change the purchased processor allowance for this installation. Refer to the Quick Beginnings book for more information. AMQ7200 (iSeries)The purchased processor allowance is Severity: 0 : Information Explanation: The purchased processor allowance is currently set to Response: Ensure sufficient license units have been purchased and, if necessary, use the MQ CHGMQMCAP command to change the purchased processor allowance for this installation. Refer to the Quick Beginnings book for more information. AMQ7201The number of processors in this machine is Severity: 0 : Information Explanation: The operating system reports that the number of processors in this machine is Response: None. AMQ7202The number of license units is sufficient for all future possible upgrades to this machine. Severity: 0 : Information Explanation: The purchased processor allowance for this installation has been set to -1, which allows any permitted processor configuration. Response: None. AMQ7203Purchased processor allowance not set (use setmqcap). Severity: 10 : Warning Explanation: The purchased processor allowance for this installation has not been set. Response: Ensure sufficient license units have been purchased and use the MQ setmqcap command to set the purchased processor allowance for this installation. Refer to the Quick Beginnings book for more information. AMQ7203 (iSeries)Purchased processor allowance not set (use CHGMQMCAP). Severity: 10 : Warning Explanation: The purchased processor allowance for this installation has not been set. Response: Ensure sufficient license units have been purchased and use the MQ CHGMQMCAP command to set the purchased processor allowance for this installation. Refer to the Quick Beginnings book for more information. AMQ7204Intel Hyper-Threading support enabled with Logical Processor Mask . Severity: 0 : Information Explanation: Install has detected Intel Hyper=Threading support enabled for Logical Processors. The current Processor Mask is set to . Response: None. AMQ7205System call SetProcessAffinityMask failed for Logical Processor Mask . Process Affinity Mask is , process is continuing. Severity: 0 : Information Explanation: Microsoft Windows system call SetProcessAffinityMask failed. If this problem persists contact your IBM service representative. Response: None. AMQ7206 (Windows)Group name has been truncated. Severity: 40 : Stop Error Explanation: WebSphere MQ only supports group names up to 12 characters long. The operating system is attempting to return a group longer than this. Response: Reduce the group name to 12 characters or less. AMQ7207 (Windows)User ID longer than 12 characters. Severity: 40 : Stop Error Explanation: WebSphere MQ only supports user names up to 12 characters long. This operation is being attempted from a user name longer than this. Response: Reduce the user name to 12 characters or less. AMQ7208The queue manager failed to pass a PCF message to another queue manager. Severity: 10 : Warning Explanation: The queue manager attempted to put a PCF message to to start the channel to cluster queue manager . The put failed with reason . When the queue manager resolves a cluster queue to a remote cluster queue manager, the message is put to the SYSTEM.CLUS.TRANSMIT.QUEUE. If the channel to the remote cluster queue manager is not running, the queue manager attempts to start the channel by sending a PCF message to . Response: Resolve the problem with and if necessary start the channel manually. AMQ7209The queue manager attempted to open SYSTEM.CHANNEL.INITQ which failed with reason Severity: 10 : Warning Explanation: When the queue manager resolves a cluster queue to a remote cluster queue manager, the message is put to the SYSTEM.CLUS.TRANSMIT.QUEUE. If the channel to the remote cluster queue manager is not running, the queue manager attempts to start the channel by sending a PCF message to the SYSTEM.CHANNEL.INITQ Response: Resolve the problem with the SYSTEM.CHANNEL.INITQ and if necessary start the channels manually. AMQ7210The Cluster Workload exit module could not be loaded. Severity: 10 : Warning Explanation: The Cluster Workload exit module could not be loaded for reason . Response: Correct the problem with the Cluster Workload exit module AMQ7211The Queue Manager is still waiting for a reply from the Cluster Workload Exit server process. Severity: 10 : Warning Explanation: The Queue Manager is configured to run the Cluster Workload Exit in SAFE mode. This means that the Cluster Workload Exit is run by a server process (amqzlw0). The Queue Manager has been waiting seconds for this server process to reply to a request to run the Cluster Workload Exit. It is possible that the exit is hung or is looping. Response: End the Queue Manager, resolve the problem with the Cluster Workload Exit and restart the Queue Manager AMQ7212The address of the Cluster exit function could not be found. Severity: 10 : Warning Explanation: The address of the Cluster exit function could not be found in module for reason . Response: Correct the problem with the Cluster exit function in the module AMQ7214The module for API Exit could not be loaded. Severity: 40 : Stop Error Explanation: The module for API Exit could not be loaded for reason . Response: Correct the problem with the API Exit module . AMQ7215The API Exit function could not be found in the module . Severity: 40 : Stop Error Explanation: The API Exit function could not be found in the module . The internal return code was . Response: Correct the problem with the API Exit . AMQ7215 (iSeries)Could not find a function in API Exit . Severity: 40 : Stop Error Explanation: The API Exit function could not be found in the module . The internal return code was . Response: Correct the problem with the API Exit . AMQ7216An API Exit initialization function returned an error. Severity: 10 : Warning Explanation: The API Exit function in the module returned CompCode and ReasonCode . Response: Correct the problem with the API Exit AMQ7217The response set by the exit is not valid. Severity: 10 : Warning Explanation: The API Exit module function returned a response code that is not valid in the ExitResponse field of the API Exit parameters (MQAXP). Response: Investigate why the API Exit set a response code that is not valid. AMQ7219profile: Severity: 0 : Information AMQ7220object type: Severity: 0 : Information AMQ7221entity: Severity: 0 : Information AMQ7222entity type: Severity: 0 : Information AMQ7223authority: Severity: 0 : Information AMQ7224profile: , object type: Severity: 0 : Information AMQ7225No matching authority records. Severity: 0 : Information Explanation: No authority records match the specified parameters. AMQ7226The profile name is invalid. Severity: 20 : Error Explanation: The profile name contains invalid characters, contains an invalid wildcard specification, or is of invalid length. Response: Correct the profile name and submit it again. AMQ7227WebSphere MQ encountered the following network error: Severity: 10 : Warning Explanation: MQ failed to successfully complete a network operation due to the specified error. Response: Ensure that your network is functioning correctly. AMQ7228 (iSeries)Display MQ Authority Records for Severity: 0 : Information AMQ7229 log records accessed on queue manager during the log replay phase. Severity: 0 : Information Explanation: log records have been accessed so far on queue manager during the log replay phase in order to bring the queue manager back to a previously known state. Response: None. AMQ7230Log replay for queue manager complete. Severity: 0 : Information Explanation: The log replay phase of the queue manager restart process has been completed for queue manager . Response: None. AMQ7231 log records accessed on queue manager during the recovery phase. Severity: 0 : Information Explanation: log records have been accessed so far on queue manager during the recovery phase of the transactions manager state. Response: None. AMQ7232Transaction manager state recovered for queue manager . Severity: 0 : Information Explanation: The state of transactions at the time the queue manager ended has been recovered for queue manager . Response: None. AMQ7233 out of in-flight transactions resolved for queue manager . Severity: 0 : Information Explanation: transactions out of in-flight at the time queue manager ended have been resolved. Response: None. AMQ7234 messages from queue loaded on queue manager . Severity: 0 : Information Explanation: messages from queue have been loaded on queue manager . Response: None. AMQ7235 (iSeries)Queue manager library already exists. Severity: 40 : Stop Error Explanation: The library already exists. Response: Specify a library which does not already exist. AMQ7236WebSphere MQ queue manager activated. Severity: 0 : Information Explanation: WebSphere MQ queue manager has been activated. Response: None. AMQ7237WebSphere MQ queue manager is not a backup queue manager. Severity: 10 : Warning Explanation: WebSphere MQ queue manager is not a backup queue manager and so cannot be activated. A possible reason might be that the queue manager is configured for circular logging. Response: Re-try the command without the '-a' option. AMQ7238WebSphere MQ queue manager replay completed. Severity: 0 : Information Explanation: WebSphere MQ queue manager replay has completed. Response: None. AMQ7249WebSphere MQ queue manager cannot be started for replay. Severity: 20 : Error Explanation: WebSphere MQ queue manager cannot be started for replay. A possible reason might be that the queue manager is configured for circular logging. Response: Re-try the command without the '-r' option. AMQ7250WebSphere MQ queue manager has not been activated. Severity: 20 : Error Explanation: WebSphere MQ queue manager cannot be started because it has previously been started for replay but has not been activated. Response: Activate the queue manager and try starting the queue manager again. AMQ7253The command requires one of the following arguments: . Severity: 20 : Error Explanation: The command required at least one of the following arguments, none of which you supplied: . Response: Check the WebSphere MQ System Administration documentation for details on the usage of the command, correct the command and then retry. AMQ7305Trigger message could not be put on an initiation queue. Severity: 10 : Warning Explanation: The attempt to put a trigger message on queue on queue manager failed with reason code . The message will be put on the dead-letter queue. Response: Ensure that the initiation queue is available, and operational. AMQ7306The dead-letter queue must be a local queue. Severity: 10 : Warning Explanation: An undelivered message has not been put on the dead-letter queue on queue manager , because the queue is not a local queue. The message will be discarded. Response: Inform your system administrator. AMQ7307A message could not be put on the dead-letter queue. Severity: 10 : Warning Explanation: The attempt to put a message on the dead-letter queue on queue manager failed with reason code . The message will be discarded. Response: Ensure that the dead-letter queue is available and operational. AMQ7308Trigger condition was not satisfied. Severity: 0 : Information Explanation: At least one of the conditions required for generating a trigger message was not satisfied, so a trigger message was not generated. If you were expecting a trigger message, consult the WebSphere MQ Application Programming Guide for a list of the conditions required. (Note that arranging for condition to be satisfied might not be sufficient because the conditions are checked in an arbitrary order, and checking stops when the first unsatisfied condition is discovered.) Response: If a trigger message is required, ensure that all the conditions for generating one are satisfied. AMQ7310Report message could not be put on a reply-to queue. Severity: 10 : Warning Explanation: The attempt to put a report message on queue on queue manager failed with reason code . The message will be put on the dead-letter queue. Response: Ensure that the reply-to queue is available and operational. AMQ7315Failed to put message to accounting queue. Reason() Severity: 20 : Error Explanation: The attempt to put a messsage containing accounting data to the queue failed with reason code . The message data has been discarded. This error message will be written only once for attempts to put a message to the queue as part of the same operation which fail for the same reason. Response: Ensure that the queue is available and operational. AMQ7316Failed to put message to statistics queue. Reason() Severity: 20 : Error Explanation: The attempt to put a messsage containing statistics data to the queue failed with reason code . The message data has been discarded. This error message will be written only once for attempts to put a message to the queue as part of the same operation which fail for the same reason. Response: Ensure that the queue is available and operational. AMQ7432 (iSeries)WebSphere MQ journal entry not available for replay. Severity: 40 : Stop Error Explanation: A journal replay operation was attempted, but the operation required journal entries from journal receivers that are not currently present on the system. Response: Restore the required journal receivers from backup. Then try the operation again. AMQ7433 (iSeries)An Error occured while performing a journal replay. Severity: 40 : Stop Error Explanation: WebSphere MQ encountered a problem reading one or more journal entries while performing a journal replay operation. Response: If you have previously created a journal receiver for a queue manager or are performing a cold restart of a queue manager, delete the QMQMCHKPT file from the queue manager subdirectory in /QIBM/UserData/mqm/qmgrs/ and attempt to restart the queue manager. If the problem persists, use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ7434 (iSeries)The MQ commitment control exit program was called incorrectly. Code . Severity: 40 : Stop Error Explanation: The WebSphere MQ commitment control exit program was called with incorrect parameters. Response: If the program was called by OS/400 as part of a commit or rollback, save the job log, and contact your IBM support center. AMQ7435 (iSeries)The MQ commitment control exit program failed. Code . Severity: 40 : Stop Error Explanation: The WebSphere MQ commitment control exit program failed due to an unexpected error. Response: Save the job log, and contact your IBM support center. AMQ7459 (iSeries)WebSphere MQ journal receiver is the oldest in the chain Severity: 0 : Information Explanation: The oldest journal receiver in the receiver chain is in library . Response: None AMQ7460 (iSeries)WebSphere MQ startup journal information. Severity: 0 : Information Explanation: This message is issued periodically by WebSphere MQ to help you identify which journal receivers can be removed from the system because they are no longer required for startup recovery. Response: None AMQ7461 (iSeries)WebSphere MQ object re-created - reapply authorities. Severity: 0 : Information Explanation: A previously damaged object has been re-created, either automatically, or by explicit use of the Recreate Object (RCRMQMOBJ) command. The authorities that applied to this object have not been re-created. Response: Use the Grant Authority (GRTMQMAUT) command, as appropriate, to re-create the required authorities to this MQ object. AMQ7462 (iSeries)WebSphere MQ media recovery journal information. Severity: 0 : Information Explanation: This message is issued periodically by WebSphere MQ to help you identify which journal receivers can be removed from the system because they are no longer required for media recovery. Response: None AMQ7463The log for queue manager is full. Severity: 20 : Error Explanation: This message is issued when an attempt to write a log record is rejected because the log is full. The queue manager will attempt to resolve the problem. Response: This situation may be encountered during a period of unusually high message traffic. However, if you persistently fill the log, you may have to consider enlarging the size of the log. You can either increase the number of log files by changing the values in the queue manager configuration file. You will then have to stop and restart the queue manager. Alternatively, if you need to make the log files themselves bigger, you will have to delete and recreate the queue manager. AMQ7464The log for queue manager is no longer full. Severity: 0 : Information Explanation: This message is issued when a log was previously full, but an attempt to write a log record has now been accepted. The log full situation has been resolved. Response: None AMQ7465The log for queue manager is full. Severity: 20 : Error Explanation: An attempt to resolve a log full situation has failed. This is due to the presence of a long-running transaction. Response: Try to ensure that the duration of your transactions is not excessive. Commit or roll back any old transactions to release log space for further log records. AMQ7466There is a problem with the size of the logfile. Severity: 10 : Warning Explanation: The log for queue manager is too small to support the current data rate. This message is issued when the monitoring tasks maintaining the log cannot keep up with the current rate of data being written. Response: The number of primary log files configured should be increased to prevent possible log full situations. AMQ7467The oldest log file required to start queue manager is . Severity: 0 : Information Explanation: The log file contains the oldest log record required to restart the queue manager. Log records older than this may be required for media recovery. Response: You can move log files older than to an archive medium to release space in the log directory. If you move any of the log files required to recreate objects from their media images, you will have to restore them to recreate the objects. AMQ7468The oldest log file required to perform media recovery of queue manager is . Severity: 0 : Information Explanation: The log file contains the oldest log record required to recreate any of the objects from their media images. Any log files prior to this will not be accessed by media recovery operations. Response: You can move log files older than to an archive medium to release space in the log directory. AMQ7469Transactions rolled back to release log space. Severity: 0 : Information Explanation: The log space for the queue manager is becoming full. One or more long-running transactions have been rolled back to release log space so that the queue manager can continue to process requests. Response: Try to ensure that the duration of your transactions is not excessive. Consider increasing the size of the log to allow transactions to last longer before the log starts to become full. AMQ7472Object , type damaged. Severity: 10 : Warning Explanation: Object , type has been marked as damaged. This indicates that the queue manager was either unable to access the object in the file system, or that some kind of inconsistency with the data in the object was detected. Response: If a damaged object is detected, the action performed depends on whether the queue manager supports media recovery and when the damage was detected. If the queue manager does not support media recovery, you must delete the object as no recovery is possible. If the queue manager does support media recovery and the damage is detected during the processing performed when the queue manager is being started, the queue manager will automatically initiate media recovery of the object. If the queue manager supports media recovery and the damage is detected once the queue manager has started, it may be recovered from a media image using the rcrmqmobj command or it may be deleted. AMQ7472 (iSeries)Object , type damaged. Severity: 10 : Warning Explanation: Object , type has been marked as damaged. This indicates that the queue manager was either unable to access the object in the file system, or that some kind of inconsistency with the data in the object was detected. Response: If a damaged object is detected, the action performed depends on whether the queue manager supports media recovery and when the damage was detected. If the queue manager does not support media recovery, you must delete the object as no recovery is possible. If the queue manager does support media recovery and the damage is detected during the processing performed when the queue manager is being started, the queue manager will automatically initiate media recovery of the object. If the queue manager supports media recovery and the damage is detected once the queue manager has started, it may be recovered from a media image using the RCRMQMOBJ command or it may be deleted. AMQ7477 (iSeries)WebSphere MQ session no longer active. Severity: 10 : Warning Explanation: The commitment control exit program was called during a commit or rollback operation. The queue manager was stopped while the program was registered. This might have resulted in the rolling back of some uncommitted message operations. Response: Inform your system administrator that uncommitted message operations might have been rolled back when the queue manager was stopped. AMQ7484Failed to put message to logger event queue. Reason() Severity: 20 : Error Explanation: The attempt to put a logger event messsage to the queue failed with reason code . The message data has been discarded. Response: Ensure that the queue is available and operational. Current logger status information can be displayed with the DISPLAY QMSTATUS runmqsc command. AMQ7601Duplicate XA resource manager is not valid. Severity: 40 : Stop Error Explanation: Line of the configuration file contained a duplicate XA resource manager . This is not valid for attribute . Each XA resource manager must be given a unique name. Response: Check the contents of the file and retry the operation. AMQ7601 (Windows)Duplicate XA resource manager not valid for attribute at in the configuration data. Severity: 40 : Stop Error Explanation: Key in the configuration data contained a duplicate XA resource manager . This is not valid for attribute . Each XA resource manager must be given a unique name. Response: Check the contents of the configuration data and retry the operation. AMQ7602 (iSeries)The MQ commitment control exit program was called incorrectly. Severity: 40 : Stop Error Explanation: The WebSphere MQ commitment control exit program was called with incorrect parameters. Response: If the program was called by OS/400 as part of a commit or rollback, save the job log, and contact your IBM support center. AMQ7603WebSphere MQ has been configured with invalid resource manager . Severity: 20 : Error Explanation: The XA switch file for resource manager indicates that an attempt has been made to configure another queue manager as an external resource manager. This is not allowed so the queue manager will terminate. Response: Remove the offending XAResourceManager stanza from the qm.ini configuration file and restart the queue manager. AMQ7603 (Windows)WebSphere MQ has been configured with resource manager that is not valid. Severity: 20 : Error Explanation: The XA switch file for resource manager indicates that an attempt has been made to configure another queue manager as an external resource manager. This is not allowed, so the queue manager will terminate. Response: Remove the offending XAResourceManager stanza from the configuration data and restart the queue manager. AMQ7604The XA resource manager was not available when called for . The queue manager is continuing without this resource manager. Severity: 10 : Warning Explanation: The XA resource manager has indicated that it is not available, by returning XAER_RMERR on an xa_open request or XAER_RMFAIL when called for something else. Normally this indicates that the resource manager has been shut down. In this case the resource manager cannot participate in any new transactions. Any in-flight transactions in which it was involved will be backed out, and any transactions in which it is in-doubt will only be resolved when contact with the resource manager is re-established. A further message will be issued when the queue manager has been able to do this. If the problem occurred on an xa_open request, and the resource manager should be available, then there may be a configuration problem. Response: Try to establish the reason why the resource manager is unavailable. It may be that an invalid XAOpenString has been defined for the resource manager in the 'qm.ini' configuration file. If this is the case, stop and then restart the queue manager so that any change will be picked up. Alternatively, the queue manager may be reaching a resource constraint with this resource manager. For example, the resource manager may not be able to accommodate all of the queue manager processes being connected at one time, you may need to alter one of its tuning parameters. AMQ7604 (iSeries)The XA resource manager was not available when called. Severity: 10 : Warning Explanation: The XA resource manager has indicated that it is not available, by returning XAER_RMERR on an xa_open request or XAER_RMFAIL when called for . The queue manager is continuing without this resource manager. Normally this indicates that the resource manager has been shut down. In this case the resource manager cannot participate in any new transactions. Any in-flight transactions in which it was involved will be backed out, and any transactions in which it is in-doubt will only be resolved when contact with the resource manager is re-established. A further message will be issued when the queue manager has been able to do this. If the problem occurred on an xa_open request, and the resource manager should be available, then there may be a configuration problem. Response: Try to establish the reason why the resource manager is unavailable. It may be that an invalid XAOpenString has been defined for the resource manager in the 'qm.ini' configuration file. If this is the case, stop and then restart the queue manager so that any change will be picked up. Alternatively, the queue manager may be reaching a resource constraint with this resource manager. For example, the resource manager may not be able to accommodate all of the queue manager processes being connected at one time, you may need to alter one of its tuning parameters. AMQ7605The XA resource manager has returned an unexpected return code , when called for . Severity: 20 : Error Explanation: WebSphere MQ received an unexpected return code when calling XA resource manager at its entry point. This indicates an internal error, either within MQ or the resource manager. Response: Try to determine the source of the error. A trace of the failure could be used to look at the XA flows between MQ and the resource manager. MQ has allocated an RMId of to this resource manager. This will be useful when isolating the flows associated with the resource manager concerned. If the error occurs on an xa_commit or xa_rollback request, the queue manager will not attempt to redeliver the commit or rollback instruction for this transaction, until after the queue manager has been restarted. The transaction indoubt is identified by the following XID of X. If you think that the error lies within the queue manager, contact your IBM support center. Do not discard any information describing the problem until after the problem has been resolved. AMQ7605 (iSeries)The XA resource manager has returned an unexpected return code. Severity: 20 : Error Explanation: WebSphere MQ received unexpected return code when calling XA resource manager at its entry point. This indicates an internal error, either within MQ or the resource manager. Response: Try to determine the source of the error. A trace of the failure could be used to look at the XA flows between MQ and the resource manager. MQ has allocated an RMId of to this resource manager. This will be useful when isolating the flows associated with the resource manager concerned. If the error occurs on an xa_commit or xa_rollback request, the queue manager will not attempt to redeliver the commit or rollback instruction for this transaction, until after the queue manager has been restarted. The transaction indoubt is identified by the following XID of X. If you think that the error lies within the queue manager, contact your IBM support center. Do not discard any information describing the problem until after the problem has been resolved. AMQ7606A transaction has been committed but one or more resource managers have backed out. Severity: 20 : Error Explanation: WebSphere MQ was processing the commit operation for a transaction involving external resource managers. One or more of these resource managers failed to obey the commit request and instead rolled back their updates. The outcome of the transaction is now mixed and the resources owned by these resource managers may now be out of synchronization. MQ will issue further messages to indicate which resource managers failed to commit their updates. Response: The transaction with the mixed outcome is identified by the following XID of X. The messages which identify the failing resource managers will also contain this same XID. If the transaction has completed it won't be displayed by the dspmqtrn command and all other transaction participants will have committed their updates. If the transaction is displayed by the dspmqtrn command then there are some participants still in prepared state. In order to preserve data integrity you will need to perform recovery steps local to the failing resource managers. AMQ7607A transaction has been rolled back but one or more resource managers have committed. Severity: 20 : Error Explanation: WebSphere MQ was rolling back a transaction involving external resource managers. One or more of these resource managers failed to obey the rollback request and instead committed their updates. The outcome of the transaction is now mixed and the resources owned by these resource managers may now be out of synchronization. MQ will issue further messages to indicate which resource managers failed to roll back their updates. Response: The transaction with the mixed outcome is identified by the following XID of X. The messages which identify the failing resource managers will also contain this same XID. If the transaction has completed it won't be displayed by the dspmqtrn command and all other transaction participants will have rolled back their updates. If the transaction is displayed by the dspmqtrn command then there are some participants still in prepared state. In order to preserve data integrity you will need to perform recovery steps local to the failing resource managers. AMQ7608XA resource manager returned a heuristic return code. Severity: 20 : Error Explanation: This message is associated with an earlier AMQ7606 message reporting a mixed transaction outcome. It identifies one of the resource managers () that failed to commit its updates. The transaction associated with this failure is identified by the following XID of X. Response: Use the return code returned by the resource manager to determine the effects of the failure. The return code indicates that the resource manager made a heuristic decision about the outcome of the transaction which disagrees with the commit decision of the queue manager. In order to preserve data integrity you will need to perform recovery steps local to this resource manager. AMQ7609XA resource manager returned a heuristic return code. Severity: 20 : Error Explanation: This message is associated with an earlier AMQ7607 message reporting a mixed transaction outcome. It identifies one of the resource managers () that failed to rollback its updates. The transaction associated with this failure is identified by the following XID of X. Response: Use the return code returned by the resource manager to determine the effects of the failure. The return code indicates that the resource manager made a heuristic decision about the outcome of the transaction which disagrees with the rollback decision of the queue manager. In order to preserve data integrity you will need to perform recovery steps local to this resource manager. AMQ7612Switch call exception Severity: 20 : Error Explanation: Exception number occurred when calling resource manager switch . Response: Check the resource manager switch has not been corrupted. AMQ7622WebSphere MQ could not load the XA switch load file for resource manager . Severity: 20 : Error Explanation: An error has occurred loading XA switch file . If the error occurred during startup then the queue manager will terminate. At all other times the queue manager will continue without this resource manager meaning that it will no longer be able to participate in global transactions. The queue manager will also retry the load of the switch file at regular intervals so that the resource manager will be able to participate again should the load problem be resolved. Response: Look for a previous message outlining the reason for the load failure. Message AMQ6175 is issued if the load failed because of a system error. If this is the case then follow the guidance given in message AMQ6175 to resolve the problem. In the absence of prior messages or FFST information related to this problem check that the name of the switch load file is correct and that it is present in a directory from which it can be dynamically loaded by the queue manager. The easiest method of doing this is to define the switch load file as a fully-qualified name. Note that if the queue manager is still running it will need to be restarted in order that any changes made to its configuration data can be picked up. AMQ7623WebSphere MQ has not been configured with XA resource manager. Severity: 10 : Warning Explanation: The queue manager has noticed that XA resource manager was removed from the qm.ini file of the queue manager. However, it was logged as being involved in transactions that are still in-doubt. The queue manager cannot resolve these transactions.The queue manager is continuing without this resource manager. Response: First check that the qm.ini configuration file of the queue manager concerned hasn't been mistakenly altered resulting in an 'XAResourceManager' stanza being removed, or the 'Name' of any the resource managers being changed. If the qm.ini file was changed by mistake then you will need to reinstate resource manager in the qm.ini file before stopping and then restarting the queue manager in order that the change will be picked up. If you have intentionally removed a resource manager from the qm.ini file, consider the integrity implications of your action since the resource manager concerned may be in an in-doubt state. If you are sure that is not the case then you can use the 'rsvmqtrn' command to deliver an outcome on behalf of the resource manager in order that the queue manager can forget about the transactions concerned. If you cannot be sure that such an action will not cause an integrity problem then you should consider re-instating the resource manager in the qm.ini file so that the queue manager can contact the resource manager and automatically resolve the transactions concerned next time the queue manager is restarted. AMQ7623 (Windows)WebSphere MQ has not been configured with XA resource manager which may be involved in in-doubt transactions. The queue manager is continuing without this resource manager. Severity: 10 : Warning Explanation: The queue manager has recognized that XA resource manager was removed from the registry entry of the queue manager. However, it was logged as being involved in transactions that are still in-doubt. The queue manager cannot resolve these transactions. Response: Check that the configuration data entry of the queue manager concerned has not been altered by mistake, resulting in an 'XAResourceManager' stanza being removed, or the 'Name' of any the resource managers being changed. If the configuration data entry was changed by mistake, you need to reinstate resource manager in the configuration data before stopping, and then restarting the queue manager to access the change. If you have intentionally removed a resource manager from the configuration data, consider the integrity implications of your action because the resource manager concerned may be in an in-doubt state. If you are sure that this is not the case, you can use the 'rsvmqtrn' command to instruct the resource manager to inform the queue manager that it can forget about the transactions concerned. If using the 'rsvmqtrn' command could result in an integrity problem, you should consider reinstating the resource manager in the configuration data, so that the queue manager can contact the resource manager and automatically resolve the transactions concerned next time the queue manager is restarted. AMQ7624An exception occurred during an call to XA resource manager . Severity: 20 : Error Explanation: An exception has been detected during a call to an XA resource manager. The queue manager will continue after assuming a return code of XAER_RMERR from the call. Response: An FFST should have been produced which documents the exception. Use this and any further FFSTs to try and determine the reason for the failure. A trace of the problem will be useful to identify the XA flows between the queue manager and the resource manager concerned. MQ has allocated an RMId of to this resource manager. Use this to isolate the flows concerned. First contact the supplier of the resource manager for problem resolution. If however you think that the problem lies within the queue manager then contact your IBM support center. Do not discard any information describing the problem until after it has been resolved. AMQ7625The XA resource manager has become available again. Severity: 0 : Information Explanation: WebSphere MQ has managed to regain contact with a resource manager that had become unavailable. Any in-doubt transactions involving this resource manager will be resolved. The resource manager will now be able to participate in new transactions. Response: None. AMQ7626XA resource manager initialization failure. Refer to the error log for more information. Severity: 20 : Error Explanation: The queue manager has failed to initialize one or more of the XA resource managers defined in the qm.ini configuration file. Response: Correct the error and restart the queue manager. AMQ7626 (Windows)XA resource manager initialization failure. Refer to the error log for more information. Severity: 20 : Error Explanation: The queue manager has failed to initialize one or more of the XA resource managers defined in the configuration data. Response: Correct the error and restart the queue manager. AMQ7701DMPMQLOG command is starting. Severity: 0 : Information Explanation: You have started the DMPMQLOG command and it is processing your request. Response: None. AMQ7702DMPMQLOG command has finished successfully. Severity: 0 : Information Explanation: The DMPMQLOG command has finished processing your request and no errors were detected. Response: None. AMQ7703DMPMQLOG command has used option with an invalid value . Severity: 20 : Error Explanation: You started the DMPMQLOG command specifying an invalid option value. The value for option is either missing or of an incorrect format. Response: Refer to the command syntax, and then try the command again. AMQ7704DMPMQLOG command has used an invalid option . Severity: 20 : Error Explanation: You started the DMPMQLOG command specifying an invalid option of . Response: Refer to the command syntax and then try the command again. AMQ7705Usage: dmpmqlog [-b | -s StartLSN | -n ExtentNumber] [-e EndLSN] [-f LogFilePath] [-m QMgrName] Severity: 0 : Information Response: None. AMQ7706DMPMQLOG command has used an incorrect queue manager name or path . Severity: 20 : Error Explanation: The DMPMQLOG command has used as the queue manager name and, if shown, as the directory path for . Either and/or is incorrect; if is not shown then it is which is incorrect. Possible reasons for the error include: that is not an existing queue manager name; the entries for in the MQ system initialization (INI) file are incorrect; is not a correct path for . If you started the command specifying option -m (queue manager name option) with a value then this value will have been used as the queue manager name, otherwise the default queue manager name will have been used. Response: Check that is an existing queue manager name. Check your MQ system's initialization (INI) file to ensure that and its associated entries are correct. If is shown, check that it is a correct MQ system directory path for . AMQ7706 (iSeries)DMPMQLOG command has used an incorrect queue manager name or path. Severity: 20 : Error Explanation: The DMPMQLOG command has used as the queue manager name and, if shown, as the directory path for . Either and/or is incorrect; if is not shown then it is which is incorrect. Possible reasons for the error include: that is not an existing queue manager name; the entries for in the MQ system initialization (INI) file are incorrect; is not a correct path for . If you started the command specifying option -m (queue manager name option) with a value then this value will have been used as the queue manager name, otherwise the default queue manager name will have been used. Response: Check that is an existing queue manager name. Check your MQ system's initialization (INI) file to ensure that and its associated entries are correct. If is shown, check that it is a correct MQ system directory path for . AMQ7706 (Windows)DMPMQLOG command has used an incorrect queue manager name or path . Severity: 20 : Error Explanation: The DMPMQLOG command has used as the queue manager name and, if shown, as the directory path for . Either and/or is incorrect; if is not shown then it is which is incorrect. Possible reasons for the error include: that is not an existing queue manager name; the entries for in the MQ configuration data are incorrect; is not a correct path for . If you started the command specifying option -m (queue manager name option) with a value then this value will have been used as the queue manager name, otherwise the default queue manager name will have been used. Response: Check that is an existing queue manager name. Check your MQ configuration data to ensure that and its associated entries are correct. If is shown, check that it is a correct MQ system directory path for . AMQ7707DMPMQLOG command has failed: CompCode = 0x. Severity: 20 : Error Explanation: The DMPMQLOG command has detected an error and the MQ recording routine has been called. Possible reasons for this include a damaged log file, a problem during initialization for the queue manager or an internal MQ failure. Response: Check that the queue manager being used by DMPMQLOG, as specified by you using the -m command option or defaulted, exists and is not currently running. If it does not exist, try the command again specifying an existing queue manager. If it is running, stop the queue manager and then try the command again. Otherwise, use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Do not discard these files until the problem has been resolved. Note the completion code (CompCode) and then contact your IBM support center. AMQ7708DMPMQLOG command has used an invalid default queue manager name. Severity: 20 : Error Explanation: You started the DMPMQLOG command without specifying option -m (queue manager name option) and so your MQ default queue manager name has been used. However, this default name either could not be found or is invalid. Response: Check that the default queue manager name exists and is valid, and then try the command again. AMQ7709DMPMQLOG command has used an invalid combination of options. Severity: 20 : Error Explanation: You started the DMPMQLOG command specifying an invalid combination of the options -b (base LSN option), -s (start LSN option) and -n (extent number option). Only 1 or none of these options may be specified. Response: Refer to the command syntax and then try the command again. AMQ7710DMPMQLOG command has used option -n which is invalid for circular logging. Severity: 20 : Error Explanation: You started the DMPMQLOG command specifying option -n (extent number option) but this is not valid when your MQ log is defined as circular. Response: Use a different option and then try the command again. AMQ7711DMPMQLOG command has used option -m with a value that is too long. Severity: 20 : Error Explanation: You started the DMPMQLOG command specifying option -m (queue manager name option) with a value that is more than characters. Response: Specify a shorter queue manager name and then try the command again. AMQ7712DMPMQLOG command has used option -f with a value which is too long. Severity: 20 : Error Explanation: You started the DMPMQLOG command specifying option -f (log file path option) with a value which is more than characters. Response: Specify a shorter log file path name and then try the command again. AMQ7713DMPMQLOG command was unable to allocate sufficient storage. Severity: 20 : Error Explanation: The DMPMQLOG command has been unable to allocate some storage. Response: Free some storage and then try the command again. AMQ7714DMPMQLOG command has reached the end of the log. Severity: 0 : Information Explanation: The DMPMQLOG command has processed any log data and has now reached the end of the log. Response: None. AMQ7715DMPMQLOG command cannot open file . Severity: 20 : Error Explanation: The DMPMQLOG command was unable to open file for reading. Response: Check that the file exists, can be opened for reading, and that you have authority to access it, and then try the command again. AMQ7716DMPMQLOG command has finished unsuccessfully. Severity: 0 : Information Explanation: The DMPMQLOG command has finished with your request but an error has been detected. The previous message issued by the command can be used to identify the error. Response: Refer to the previous message issued by the command. AMQ7717DMPMQLOG command has failed to initialize: CompCode = 0x. Severity: 20 : Error Explanation: The DMPMQLOG command has failed during its initialization and the MQ recording routine has been called. Possible reasons for this include that your queue manager is already running. The completion code can be used to identify the error. Response: Check that the queue manager being used by DMPMQLOG, as specified by you using the -m command option or defaulted, exists and is not currently running. If it is running, stop the queue manager and then try the command again. Otherwise, use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ7718DMPMQLOG command is using a default of for the queue manager name. Severity: 0 : Information Explanation: You have started the DMPMQLOG command without specifying option -m (queue manager name option) and so a default value of is being used. This value is obtained from your default queue manager name. Response: None. AMQ7718 (iSeries)DMPMQLOG command is using a the default queue manager name. Severity: 0 : Information Explanation: You have started the DMPMQLOG command without specifying option -m (queue manager name option) and so a default value of is being used. This value is obtained from your MQ default queue manager name. Response: None. AMQ7719DMPMQLOG command is using a default of for the starting dump location. Severity: 0 : Information Explanation: You have started the DMPMQLOG command without specifying option -b (base LSN option), option -s (start LSN option) or option -n (extent number option), and so a default value of is being used. This value is the Log Sequence Number (LSN) of the first record in the active part of the log, and will be used as the location from which to start dumping. Response: None. AMQ7719 (iSeries)DMPMQLOG command is using the default starting dump location. Severity: 0 : Information Explanation: You have started the DMPMQLOG command without specifying option -b (base LSN option), option -s (start LSN option) or option -n (extent number option), and so a default value of is being used. This value is the Log Sequence Number (LSN) of the first record in the active part of the log, and will be used as the location from which to start dumping. Response: None. AMQ7720DMPMQLOG command is using extent but the current extent is . Severity: 20 : Error Explanation: You have started the DMPMQLOG command specifying option -n (extent number option) with a value of but this value is greater than , which represents the extent currently being used. Response: When using option -n, specify its value as being less than or equal to the extent number currently being used. AMQ7721DMPMQLOG command has not found any log records in extent number . Severity: 0 : Information Explanation: During its normal processing, the DMPMQLOG command did not find any log records in this extent. Response: None. AMQ7722DMPMQLOG command cannot find the object catalogue for queue manager . Severity: 20 : Error Explanation: The DMPMQLOG command is using the queue manager named but cannot find the manager's object catalogue file. This file should have been created at the time the queue manager was created. Response: Refer to the "System Management Guide" for a description of the location and name of the object catalogue file. Check that the file exists and is available for use by this command. If it does not exist then you will need to re-create the queue manager. AMQ7722 (iSeries)DMPMQLOG command cannot find the object catalogue for the queue manager. Severity: 20 : Error Explanation: The DMPMQLOG command is using the queue manager named but cannot find the manager's object catalogue file. This file should have been created at the time the queue manager was created. Response: Refer to the "System Management Guide" for a description of the location and name of the object catalogue file. Check that the file exists and is available for use by this command. If it does not exist then you will need to re-create the queue manager. AMQ7723DMPMQLOG command cannot find the requested Log Sequence Number (LSN). Severity: 20 : Error Explanation: The DMPMQLOG command has been started with an LSN but it cannot be found in the log. Response: Check for an existing LSN and then try the command again. AMQ7724DMPMQLOG command cannot use the requested extent number. Severity: 20 : Error Explanation: The DMPMQLOG command has been started with an extent number but it is beyond the end of the log. Response: Check for an existing extent number and then try the command again. AMQ7725DMPMQLOG command cannot find an old Log Sequence Number (LSN). Severity: 20 : Error Explanation: The DMPMQLOG command has been started specifying an LSN which is older than the log's base LSN. However, the specified LSN could not be found. Response: Check for an existing LSN and then try the command again. AMQ7726DMPMQLOG command has used option -s with an incorrect value for circular logging. Severity: 20 : Error Explanation: You started the DMPMQLOG command specifying option -s (start LSN option) with a value which is less than the base LSN of a log which is defined as circular. LSN values less than the base LSN can only be specified when using a linear log. Response: When using option -s with a circular log, specify an option value which is equal or greater to the log's base LSN, and then try the command again. AMQ7751 (iSeries)MIGRATEMQM program is starting. Severity: 0 : Information Explanation: You have started the MIGRATEMQM program. Response: None. AMQ7752 (iSeries)MIGRATEMQM has completed successfully. Severity: 0 : Information Explanation: The MIGRATEMQM program has completed migration of your queue manager and no errors were detected. Response: None. AMQ7753 (iSeries)MIGRATEMQM has failed due to errors. Severity: 20 : Error Explanation: See the previously listed messages in the job log. Correct the errors and then restart the MIGRATEMQM program. Response: None. AMQ7754 (iSeries)MIGRATEMQM has detected an error and is unable to continue. Severity: 20 : Error Explanation: See the previously listed messages in this job log, or in associated job logs. Correct the errors and then restart the MIGRATEMQM program. Response: None. AMQ7755 (iSeries)Unable to locate a required journal receiver. Severity: 20 : Error Explanation: The MIGRATEMQM program attempted to locate the journal receivers to use for migration, but the operation required access to a journal or journal receiver that is not currently present on the system. Response: Restore the required journal or journal receiver from backup. Then restart the MIGRATEMQM program. AMQ7756 (iSeries)Unable to locate a required journal entry. Severity: 20 : Error Explanation: The MIGRATEMQM program was unable to retrieve a journal entry required for migration. The operation may have failed because a required journal receiver is not currently present on the system. Response: Restore the required journal receiver from backup. Then restart the MIGRATEMQM program. AMQ7757 (iSeries)Queue manager already exists. Severity: 20 : Error Explanation: The MIGRATEMQM program is unable to create a queue manager with the same name as used in the previous release because a queue manager of this name has already been created. Response: Delete the queue manager. Then restart the MIGRATEMQM program. AMQ7758 (iSeries)Queue manager starting. Severity: 0 : Information Explanation: The queue manager "" is starting. Response: None. AMQ7759 (iSeries)Recreating WebSphere MQ objects. Severity: 0 : Information Explanation: WebSphere MQ objects are being recreated from their media images contained in the log. Response: None. AMQ7760 (iSeries)Recreating WebSphere MQ channels. Severity: 0 : Information Explanation: WebSphere MQ channels are being recreated from the previous channel definition file. Response: None. AMQ7761 (iSeries)Unexpected return code from command . Severity: 20 : Error Explanation: An unexpected return code, , was returned by command . Response: See the previously listed messages in this job log, or in associated job logs. AMQ7762 (iSeries)Unexpected error from channel migration. Severity: 20 : Error Explanation: The migration of channel definitions or channel synchronization data encountered an unexpected error. Response: See the previously listed messages in this job log, or in associated job logs. AMQ7770Sent file Severity: 40 : Stop Error Explanation: The file was successfully sent. Response: None. AMQ7771Received file. Severity: 40 : Stop Error Explanation: The file was successfully received. Response: None. AMQ7772Complete file list Severity: 40 : Stop Error Explanation: Displays a list of complete files. Response: None. AMQ7773Incomplete file list Severity: 40 : Stop Error Explanation: Displays a list of incomplete files. Response: None. AMQ7774Other message list Severity: 40 : Stop Error Explanation: Displays a list of other messages. Response: None. AMQ7775Nothing to list. Severity: 40 : Stop Error Explanation: Nothing to list. Response: None. AMQ7776Deleted. Severity: 40 : Stop Error Explanation: File deleted. Response: None. AMQ7777Nothing to delete. Severity: 40 : Stop Error Explanation: Nothing to delete. Response: None. AMQ7778Syntax error. The correct syntax is: Severity: 40 : Stop Error Explanation: Invalid arguments supplied. Response: One or more options were incorrectly specified when issuing the send or receive command. Check the options used and reissue the command. AMQ7779Cannot connect to default queue manager. Severity: 40 : Stop Error Explanation: Queue manager not available. Response: Check that the queue manager exists and that the listener is running. AMQ7780Cannot connect to queue manager Severity: 40 : Stop Error Explanation: Queue manager not available. Response: Check that the queue manager exists and that the listener is running. AMQ7781Application memory unavailable. Severity: 40 : Stop Error Explanation: There is insufficient memory to perform the requested action. Response: 1) Check the message size is not excessive 2) Close other applications and try the command again AMQ7783Queue name required. Severity: 40 : Stop Error Explanation: A queue name was not specified when issuing a send or receive command. Response: Reissue the command with the QueueName option. AMQ7784Cannot open queue Severity: 40 : Stop Error Explanation: Cannot open queue Response: Check that the queue exists. AMQ7785Cannot open file Severity: 40 : Stop Error Explanation: Cannot open file Response: Check that the file exists, that it is in the correct location and has the appropriate file permissions. AMQ7786Cannot put to queue Severity: 40 : Stop Error Explanation: Cannot put to queue Response: 1) Check the Queue Manager has sufficient log space for sending large messages 2) Check the queue does not have put inhibited 3) Check the queue is not full 4) Check the message size of the queue is greater than the message size 5) Check the user has sufficient authority to put messages on the queue AMQ7787No file name specified. Severity: 40 : Stop Error Explanation: No file name specified. Response: A file name was not specified when issuing a send command. Reissue the command with the FileName option. AMQ7788Message length is too small to send data. Severity: 40 : Stop Error Explanation: Message length is too small to send data. Response: Increase the message size and resend with a send command, using the -l MessageSize option to specify a larger message size. AMQ7789Sending file has changed. Severity: 40 : Stop Error Explanation: The file being sent has been changed before the complete file has been sent. Response: Check the file for integrity and reissue the send command. AMQ7790Cannot get from queue Severity: 40 : Stop Error Explanation: The list, get, delete or extract request has failed. Response: 1) Check the queue does have get inhibited 2) Check the user has sufficient WMQ authority to get messages from the queue AMQ7791Cannot write to file. Severity: 40 : Stop Error Explanation: The get or extract request has failed. Response: 1) Check that the file is not write-protected. In Windows Explorer, right-click the file name and select Properties. Check the user has sufficient authority to write to the destination file system. 2) Check the destination file system exists 3) Check the destination file system is not full AMQ7792CorrelId is invalid. Severity: 40 : Stop Error Explanation: CorrelId is invalid. Response: 1) Check that a valid correlation ID has been specified when receiving a file with the -c option. 2) It must be 48 characters in length. 3) Use the -v option of the receive command to display the correlation ID. AMQ7793MsgId is invalid. Severity: 40 : Stop Error Explanation: MsgId is invalid. Response: 1) Check that a valid message ID has been specified when receiving an 'other' message with the -u option. 2) It must be 48 characters in length. AMQ7794No messages to receive. Severity: 40 : Stop Error Explanation: There are no FTA files on the specified queue. Response: Check with the sender that the file was actually sent. AMQ7795Cannot delete the file because it's not unique. Severity: 40 : Stop Error Explanation: Cannot delete the file because it's not unique. Response: None. AMQ7796Cannot replace an existing file. Severity: 40 : Stop Error Explanation: Cannot replace an existing file. Response: Reissue the command with the -y option. AMQ7797Unable to load the WebSphere MQ library. Severity: 40 : Stop Error Explanation: Unable to load the WebSphere MQ library. Response: None. AMQ7798Unable to locate . Severity: 40 : Stop Error Explanation: This application requires . Response: Check that is available and installed correctly. AMQ7799Unable to start . Severity: 40 : Stop Error Explanation: This application cannot start . Response: Check that is available and installed correctly. AMQ7800CorrelId Severity: 0 : Information Explanation: None. Response: None. AMQ7801Dir Severity: 0 : Information Explanation: None. Response: None. AMQ7802UserData Severity: 0 : Information Explanation: None. Response: None. AMQ7803FileName Severity: 0 : Information Explanation: None. Response: None. AMQ7804Length Severity: 0 : Information Explanation: None. Response: None. AMQ7805MsgId Severity: 0 : Information Explanation: None. Response: None. AMQ7806Could not start WebSphere MQ web administration server: . Severity: 0 : Information Explanation: An unsuccessful attempt was made to start the web administration server on port . Response: Check the product is installed correctly; the required registry keys and values are correct and the web server port is not already in use. If the problem persists contact your service representative. AMQ7807WebSphere MQ web administration server running. Severity: 0 : Information Explanation: WebSphere MQ web administration server running. Listening on port , root directory is . Response: No action is required. AMQ7808Internal run-time error in WebSphere MQ web administration: . Severity: 0 : Information Explanation: WebSphere MQ web administration had the following internal run-time error: . Response: Check that: the product is installed correctly and that the required registry keys and values are correct. If the problem persists contact your service representative. AMQ7809WebSphere MQ Publish/Subscribe web administration user limit reached. Severity: 10 : Warning Explanation: The maximum number of concurrent web administration users has been reached (). Response: Use the 'Web Administration Server' properties page in the Microsoft Management Console to increase the value of the web administration 'MaxClients' parameter. AMQ7810 (Windows)Failed to create class, reason code: . Severity: 20 : Error Explanation: While trying to create class on error code was encountered. The associated error message generated by the operating system is: Response: Check the system documentation to determine the course of action required to rectify the problem. AMQ7880 (Windows)Error code starting / WebSphere MQ service. Severity: 0 : Information Explanation: The service was unable to start /. The error message reported was as follows: Response: Use WebSphere MQ Explorer to investigate why the service could not begin. If recovery for this service is active, MQ will attempt to recover. AMQ7881 (Windows)Unable to stop / WebSphere MQ service, return code . Severity: 10 : Warning Explanation: The WebSphere MQ service was unable to stop /. The error message reported was as follows: Response: Use WebSphere MQ Explorer to investigate why the service could not be stopped. AMQ7882 (Windows)Attempting to recover / WebSphere MQ service. Severity: 0 : Information Explanation: The WebSphere MQ service has detected that / has failed, and is attempting to restart it. Response: No Action Required. AMQ7883 (Windows)/ WebSphere MQ service started from recovery. Severity: 0 : Information Explanation: The WebSphere MQ service has successfully recovered /. Response: No Action Required. AMQ7884 (Windows)Unable to recover / WebSphere MQ service. Severity: 10 : Warning Explanation: The WebSphere MQ service has attempted to recover /, but all attempts have failed. There will be no more attempts to recover this service. Response: Use WebSphere MQ Explorer to investigate why the service failed and could not be restarted. AMQ7885 (Windows)Unable to delete queue manager , error . Severity: 10 : Warning Explanation: An attempt to delete queue manager failed. WebSphere MQ returned error code : Response: Ensure that the queue manager name has been specified correctly, and try again. AMQ7886 (Windows)Unable to create queue manager . Severity: 10 : Warning Explanation: Queue manager could not be created. WebSphere MQ returned error : Response: Check the error and application event logs to investigate the reason for the the returned error and suggested responses to take to rectify the fault. If the problem cannot be resolved then use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ7890 (Windows)Unable to open mapped file containing WebSphere MQ performance data. Severity: 20 : Error Explanation: The WebSphere MQ extensible counter dll was unable to open a mapped file used to collect queue performance data. Your system may be running short on virtual memory. Response: No action required. Performance statistics for MQ queues will not be displayed. AMQ7891 (Windows)Unable to create a mutex to access WebSphere MQ performance data. Severity: 20 : Error Explanation: The WebSphere MQ extensible counter dll was unable to create a mutex required to synchronise collection of queue performance data Response: No action required. Performance statistics for MQ queues will not be displayed. AMQ7892 (Windows)Unable to map to shared memory file containing WebSphere MQ performance data. Severity: 20 : Error Explanation: The WebSphere MQ extensible counter dll was unable to map the shared memory file required for collection of queue performance data. Response: No action required. Performance statistics for MQ queues will not be displayed. AMQ7893 (Windows)Unable to open "Performance" key for WebSphere MQ services. Status code: . Severity: 20 : Error Explanation: The WebSphere MQ extensible counter dll was unable to obtain performance counter values from the "Performance" key for WebSphere MQ services. Status code is the return value from the Windows registry call RegOpenKeyEx. Response: No action required. Performance statistics for MQ queues will not be displayed. AMQ7894 (Windows)Unable to read the "Performance\First Counter" value for WebSphere MQ services. Status code: . Severity: 20 : Error Explanation: The WebSphere MQ extensible counter dll was unable to obtain performance counter values from the "Performance\First Counter" key for WebSphere MQ services. Status code is the return value from the Windows registry call RegOpenKeyEx. Response: No action required. Performance statistics for MQ queues will not be displayed. AMQ7895 (Windows)Unable to read the "Performance\First Help" value for WebSphere MQ services. Status code: . Severity: 20 : Error Explanation: The WebSphere MQ extensible counter dll was unable to obtain performance counter values from the "Performance\First Help" key for WebSphere MQ services. Status code is the return value from the Windows registry call RegOpenKeyEx. Response: No action required. Performance statistics for MQ queues will not be displayed. AMQ7901The data-conversion exit has not loaded. Severity: 30 : Severe error Explanation: The data-conversion exit program, , failed to load. The internal function gave exception . Response: Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ7903The data-conversion exit cannot be found. Severity: 30 : Severe error Explanation: Message data conversion has been requested for a WebSphere MQ message with a user-defined format, but the necessary data-conversion exit program, , cannot be found. The internal function gave exception . Response: Check that the necessary data-conversion exit exists. AMQ7904The data-conversion exit cannot be found, or loaded. Severity: 30 : Severe error Explanation: Message data conversion was requested for a WebSphere MQ message with a user-defined format, but the necessary data conversion exit program, , was not found, or loaded. The function call gave a return code of . Response: Check that the necessary data conversion exit routine exists in one of the standard directories for dynamically loaded modules. If necessary, inspect the generated output to examine the message descriptor (MQMD structure) of the MQ message for the conversion which was requested. This may help you to determine where the message originated. AMQ7905Unexpected exception in data-conversion exit. Severity: 30 : Severe error Explanation: The data-conversion exit program, , ended with an unexpected exception . The message has not been converted. Response: Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ7907Unexpected exception in data-conversion exit. Severity: 30 : Severe error Explanation: The data-conversion exit routine, , ended with an unexpected exception. The message has not been converted. Response: Correct the error in the data-conversion exit routine. AMQ7908 (Windows)Display active directory CRL server details. Severity: 0 : Information Explanation: Display active directory CRL server details. Response: None. AMQ7909 (Windows)There are no active directory CRL server details to display. Severity: 0 : Information Explanation: No active directory CRL server definitions could be found. Response: None. AMQ7910 (Windows)Usage: setmqscp [-m QmgrName | * ] [-a] [-d] [-r] Severity: 0 : Information AMQ7911 (Windows)The default Active Directory could not be located on your domain. Severity: 20 : Error Explanation: No domain controllers with Active Directories could be found on the domain that your computer is a member of. Response: Active Directory support for MQ client connections cannot be used without a default Active Directory available on your domain. AMQ7912 (Windows)The Active Directory support library failed to initialize. Severity: 20 : Error Explanation: WebSphere MQ support libraries for Active Directory client connections could not be initialized. Response: Check that the Active Directory client pre-requisite software has been installed on your machine before attempting to use this feature. AMQ7913 (Windows)The WebSphere MQ Active Directory container could not be created. Severity: 20 : Error Explanation: WebSphere MQ has failed to create an IBM-MQClientConnections container as a child of your domain's system container in the Active Directory. Response: Ensure that you have permission to create sub-containers of the system container, and modify the otherWellKnownObjects property of the system container. AMQ7914 (Windows)Migration of the client connection table for Queue Manager failed with reason code . Severity: 10 : Warning Explanation: The client connection table for this Queue Manager could not be migrated at this time. Response: Ensure that the client connection table exists and is not corrupted, and that you have authority to create new objects in the Active Directory on your domain. AMQ7915 (Windows)Created service connection point for connection . Severity: 0 : Information Explanation: The service connection point was successfully created for this client connection. Response: None. AMQ7916 (Windows)The Active Directory channel definition table could not be opened. Severity: 20 : Error Explanation: The IBM-MQClientConnections Active Directory container could not be located in the Global Catalog. Response: Ensure that setmqscp has been used to create the container object and that you have permission to read the container and its child objects. AMQ7917 (Windows)Display active directory channel details. Severity: 0 : Information Explanation: Display active directory channel details. Response: None. AMQ7918 (Windows)The WebSphere MQ Active Directory container could not be deleted. Severity: 20 : Error Explanation: There was a problem when attempting to delete the MQ Active Directory container. The container must be empty before it can be deleted from the directory. Response: None. AMQ7919 (Windows)There are no active directory client channel details to display. Severity: 0 : Information Explanation: No active directory client channel definitions could be found. Response: None. AMQ7920 (Windows)Usage: setmqcrl [-m QmgrName] [-a] [-d] [-r] Severity: 0 : Information AMQ7921An incorrect eye-catcher field in an MQDXP structure has been detected. Severity: 30 : Severe error Explanation: The MQDXP structure passed to the Internal Formats Conversion routine contains an incorrect eye-catcher field. Response: Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ7922A PCF message is incomplete. Severity: 30 : Severe error Explanation: Message data conversion cannot convert a message in Programmable Command Format (PCF) because the message is only bytes long and does not contain a PCF header. The message has either been truncated, or it contains data that is not valid. Response: Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Do not discard these files until the problem has been resolved. Use the file containing the Message Descriptor of the message to determine the source of the message and to see how data that is not valid became included in the message. AMQ7923A message had an unrecognized integer encoding - . Severity: 30 : Severe error Explanation: Message data conversion cannot convert a message because the integer encoding value of the message, , was not recognized. Response: Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Do not discard these files until the problem has been resolved. Use the file containing the Message Descriptor of the message to determine the source of the message and to see how data that is not valid became included in the message. AMQ7924Bad length in the PCF header (length = ). Severity: 30 : Severe error Explanation: Message data conversion cannot convert a message in Programmable Command Format (PCF) because the PCF header structure contains an incorrect length field. Either the message has been truncated, or it contains data that is not valid. Response: Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Do not discard these files until the problem has been resolved. Use the file containing the Message Descriptor of the message to determine the source of the message and to see how data that is not valid became included in the message. AMQ7925Message version is not supported. Severity: 30 : Severe error Explanation: Message data conversion cannot convert a message because the Version field of the message contains an incorrect value. Response: Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Do not discard these files until the problem has been resolved. Use the file containing the Message Descriptor of the message to determine the source of the message and to see how data that is not valid became included in the message. AMQ7926A PCF message has an incorrect parameter count value . Severity: 30 : Severe error Explanation: Message data conversion cannot convert a message in Programmable Command Format (PCF) because the parameter count field of the PCF header is incorrect. Response: Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Do not discard these files until the problem has been resolved. Use the file containing the Message Descriptor of the message to determine the source of the message and to see how data that is not valid became included in the message. AMQ7927Bad type in PCF structure number (type = ). Severity: 30 : Severe error Explanation: A Programmable Command Format (PCF) structure passed to the Internal Formats Converter contained an incorrect type field. Response: Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Do not discard these files until the problem has been resolved. Use the file containing the Message Descriptor of the message to determine the source of the message and to see how data that is not valid became included in the message. AMQ7928Bad length in PCF structure number (length = ). Severity: 30 : Severe error Explanation: A Programmable Command Format (PCF) structure passed to the Internal Formats Converter contained an incorrect length field. Response: Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Do not discard these files until the problem has been resolved. Use the file containing the Message Descriptor of the message to determine the source of the message and to see how data that is not valid became included in the message. AMQ7929A PCF structure is incomplete. Severity: 30 : Severe error Explanation: Message data conversion cannot convert a message in Programmable Command Format (PCF) because structure number , of Type value , within the message is incomplete. The message has either been truncated, or it contains data that is not valid. Response: Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Do not discard these files until the problem has been resolved. Use the file containing the Message Descriptor of the message to determine the source of the message and to see how data that is not valid became included in the message. AMQ7930Bad CCSID in PCF structure number (CCSID = ). Severity: 30 : Severe error Explanation: A Programmable Command Format (PCF) structure passed to the Internal Formats Converter contains an incorrect CCSID. Response: Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Do not discard these files until the problem has been resolved. Use the file containing the Message Descriptor of the message to determine the source of the message and to see how data that is not valid became included in the message. AMQ7931Bad length in PCF structure number (length = ). Severity: 30 : Severe error Explanation: Message data conversion cannot convert a message in Programmable Command Format (PCF) because one of the structures of the message contains an incorrect length field. Response: Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Do not discard these files until the problem has been resolved. Use the file containing the Message Descriptor of the message to determine the source of the message and to see how data that is not valid became included in the message. AMQ7932Bad count in PCF structure number (count = ). Severity: 30 : Severe error Explanation: Message data conversion cannot convert a message in Programmable Command Format (PCF) because a StringList structure of the message contains an incorrect count field. Response: Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Do not discard these files until the problem has been resolved. Use the file containing the Message Descriptor, the headers of the message, and the incorrect structure to determine the source of the message, and to see how data that is not valid became included in the message. AMQ7933Bad string length in PCF structure. Severity: 30 : Severe error Explanation: Message data conversion cannot convert a message in Programmable Command Format (PCF) because structure number of the message contains an incorrect string length value . Response: Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Do not discard these files until the problem has been resolved. Use the file containing the Message Descriptor, the headers of the message, and the incorrect structure to determine the source of the message and to see how data that is not valid became included in the message. AMQ7934Wrong combination of MQCCSI_DEFAULT with MQCCSI_EMBEDDED or MQEPH_CCSID_EMBEDDED. Severity: 30 : Severe error Explanation: Message data conversion could not convert a message in Programmable Command Format (PCF) because structure of the message contained a CodedCharSetId field of MQCCSI_DEFAULT while the message itself had a CodedCharSetId of MQCCSI_EMBEDDED, or the Flags field of the MQEPH structure containing the PCF specified flag MQEPH_CCSID_EMBEDDED. These are incorrect combinations. Response: Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Do not discard these files until the problem has been resolved. Use the file containing the Message Descriptor, the headers of the message and the incorrect structure to determine the source of the message and to see how data that is not valid became included in the message. AMQ7935Bad CCSID in message header (CCSID = ). Severity: 30 : Severe error Explanation: Message data conversion could not convert a message because the Message Descriptor of the message contained an incorrect CodedCharSetId field. Response: Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Do not discard these files until the problem has been resolved. Use the file containing the Message Descriptor of the message to determine the source of the message and to see how data that is not valid became included in the message. AMQ7936The file already exists. Severity: 30 : Severe error Explanation: The output file already exists, but REPLACE has not been specified. Response: Specify REPLACE to over-write the existing file, or select a different output file name. AMQ7937Structure length in MQFMT_IMS_VAR_STRING format message is not valid. Severity: 30 : Severe error Explanation: This error is detected when attempting data conversion. The valid range for the length is 4 (with no string data) to 32767. The message is returned unconverted with a reason code of MQRC_CONVERTED_STRING_TOO_BIG. Response: Check the content of the message before data conversion and correct the message format. When converting data using two or more bytes per character, remember that the number of bytes in each character can change during data conversion. This causes the message lengths to change. AMQ7943Usage: crtmqcvx SourceFile TargetFile Severity: 0 : Information Explanation: None. Response: None. AMQ7953One structure has been parsed. Severity: 0 : Information Explanation: The crtmqcvx command has parsed one structure. Response: None. AMQ7954 structures have been parsed. Severity: 0 : Information Explanation: The crtmqcvx command has parsed structures. Response: None. AMQ7955Unexpected field: . Severity: 0 : Information Explanation: The field within the structure is of a type that is not recognized. Response: Correct the field and retry the command. AMQ7956Bad array dimension. Severity: 0 : Information Explanation: An array field of the structure has an incorrect dimension value. Response: Correct the field and retry the command. AMQ7957Warning at line . Severity: 20 : Error Explanation: The structure contains another field after a variable length field. A variable length field must be the last field of the structure. Response: Correct the structure and retry the command. AMQ7958Error at line in field . Severity: 30 : Severe error Explanation: Field name is a field of type 'float'. Fields of type float are not supported by this command. Response: Either correct the structure to eliminate fields of type float, or write your own routine to support conversion of these fields. AMQ7959Error at line in field . Severity: 30 : Severe error Explanation: Field name is a field of type 'double'. Fields of type double are not supported by this command. Response: Either correct the structure to eliminate fields of type double, or write your own routine to support conversion of these fields. AMQ7960Error at line in field . Severity: 30 : Severe error Explanation: Field name is a 'pointer' field. Fields of type pointer are not supported by this command. Response: Either correct the structure to eliminate fields of type pointer, or write your own routine to support conversion of these fields. AMQ7961Error at line in field . Severity: 30 : Severe error Explanation: Field name is a 'bit' field. Bit fields are not supported by this command. Response: Either correct the structure to eliminate bit fields, or write your own routine to support conversion of these fields. AMQ7962No input file specified. Severity: 30 : Severe error Explanation: This command requires that an input file is specified. Response: Specify the name of the input file and retry the command. AMQ7963No output file specified. Severity: 30 : Severe error Explanation: This command requires that an output file name is specified. Response: Specify the name of the output file and retry the command. AMQ7964Unexpected option . Severity: 30 : Severe error Explanation: The option specified is not valid for this command. Response: Retry the command with a valid option. AMQ7965Incorrect number of arguments. Severity: 30 : Severe error Explanation: The command was passed an incorrect number of arguments. Response: Retry the command, passing it the correct number of arguments. AMQ7968Cannot open file . Severity: 30 : Severe error Explanation: You cannot open the file . Response: Check that you have the correct authorization to the file and retry the command. AMQ7969Syntax error. Severity: 30 : Severe error Explanation: This line of the input file contains a language syntax error. Response: Correct the syntax error and retry the command. AMQ7970Syntax error on line . Severity: 30 : Severe error Explanation: This message identifies where, in the input file, a previously reported error was detected. Response: Correct the error and retry the command. AMQ7A01 (iSeries)Convert MQ Data Type AMQ7A02 (iSeries)Display MQ Version AMQ7A03 (iSeries)Create MQ Listener AMQ7A04 (iSeries)Listener name AMQ7A05 (iSeries)Listener control AMQ7A06 (iSeries)Listener backlog AMQ7A07 (iSeries)Change MQ Listener AMQ7A08 (iSeries)Copy MQ Listener AMQ7A09 (iSeries)From Listener AMQ7A0A (iSeries)To Listener AMQ7A0B (iSeries)Display MQ Listener AMQ7A0C (iSeries)Delete MQ Listener AMQ7A0D (iSeries)LSRNAME not allowed with PORT Severity: 40 : Stop Error Explanation: A listener object can not be specified with a port. Response: Specify either a listener object or a port number. AMQ7A0E (iSeries)LSRNAME not allowed with IPADDR Severity: 40 : Stop Error Explanation: A listener object can not be specified with an IP address. Response: Specify either a listener object or an IP address. AMQ7A0F (iSeries)Work with MQ Listener object AMQ7A10 (iSeries)Create MQ Service AMQ7A11 (iSeries)Change MQ Service AMQ7A12 (iSeries)Copy MQ Service AMQ7A13 (iSeries)Service name AMQ7A14 (iSeries)Start program AMQ7A15 (iSeries)Start program arguments AMQ7A16 (iSeries)End program AMQ7A17 (iSeries)End program arguments AMQ7A18 (iSeries)Standard output AMQ7A19 (iSeries)Standard error AMQ7A1A (iSeries)Service type AMQ7A1B (iSeries)Service control AMQ7A1C (iSeries)From Service AMQ7A1D (iSeries)To Service AMQ7A1E (iSeries)Display MQ Service AMQ7A20 (iSeries)Delete MQ Service AMQ7A21 (iSeries)Work with MQ Service object AMQ7A23 (iSeries)Start MQ Service AMQ7A24 (iSeries)End MQ Service AMQ7A25 (iSeries)Channel initiator control AMQ7A26 (iSeries)Command server control AMQ7A27 (iSeries)Display Queue Manager Status AMQ7A28 (iSeries)Display Listener Status AMQ7A29 (iSeries)Display Service Status AMQ7A2A (iSeries)LSRNAME not allowed with OPTION Severity: 40 : Stop Error Explanation: A listener object can not be specified with an end option. Response: Specify either a listener object or an end option. AMQ7A2B (iSeries)Service startup AMQ7A2C (iSeries)Work with Connection Handles AMQ7A2D (iSeries)Connection Identifier AMQ7A2E (iSeries)End Queue Manager Connection AMQ7A2F (iSeries)Work with MQ Connections AMQ7A30 (iSeries)Header Compression AMQ7A31 (iSeries)Message Compression AMQ7A32 (iSeries)Message compression *ANY not valid for channel type. Severity: 30 : Severe error Explanation: The message compression value *ANY is only valid for *RCVR, *RQSTR and *SVRCN channel types. Response: Specify a valid message compression list. AMQ7A33 (iSeries)Channel Monitoring AMQ7A34 (iSeries)Channel Statistics AMQ7A35 (iSeries)Cluster Workload Rank AMQ7A36 (iSeries)Cluster Workload Priority AMQ7A37 (iSeries)Cluster Channel Weight AMQ7A38 (iSeries)Cluster workload channels AMQ7A39 (iSeries)Cluster workload queue use AMQ7A3A (iSeries)Queue Monitoring AMQ7A3B (iSeries)Queue Manager Statistics AMQ7A3C (iSeries)Cluster Sender Monitoring AMQ7A3D (iSeries)Queue Statistics AMQ7A3E (iSeries)Cluster Sender Statistics AMQ7A3F (iSeries)Statistics Interval AMQ7A40 (iSeries)Display MQ Route Information AMQ7A41 (iSeries)Correlation Identifier AMQ7A42 (iSeries)Message Persistence AMQ7A43 (iSeries)Message Priority AMQ7A44 (iSeries)Report Option AMQ7A45 (iSeries)Reply Queue AMQ7A46 (iSeries)Reply Queue Manager AMQ7A47 (iSeries)Message Expiry AMQ7A48 (iSeries)Expiry Report AMQ7A49 (iSeries)Route Information AMQ7A4A (iSeries)Reply Message AMQ7A4B (iSeries)Deliver Message AMQ7A4C (iSeries)Forward Message AMQ7A4D (iSeries)Maximum Activities AMQ7A4E (iSeries)Route Detail AMQ7A4F (iSeries)Browse Only AMQ7A50 (iSeries)Display Message AMQ7A51 (iSeries)Target Queue Manager AMQ7A52 (iSeries)Display Information AMQ7A53 (iSeries)Wait Time AMQ7A54 (iSeries)RTEINF(*YES) required for RPLYMSG(*YES). Severity: 30 : Severe error Explanation: RPLYMSG(*YES) can not be specified without RTEINF(*YES). Response: If RPLYMSG(*YES) is specified then RTEINF(*YES) must also be specified. AMQ7A55 (iSeries)RPLYQ required for RPLYMQM. Severity: 30 : Severe error Explanation: RPLYMQM can not be specified without RPLYQ. Response: If RPLYMQM is specified then RPLYQ must also be specified. AMQ7A56 (iSeries)CRRLID specified with invalid parameters. Severity: 30 : Severe error Explanation: The CRRLID parameter was specified with one or more of MSGPST, MSGPRTY, OPTION, RPLYQ, RPLYMQM, EXPIRY, EXPRPT, RTEINF RPLYMSG, DLVRMSG, FWDMSG, MAXACTS and DETAIL which are invalid with CRRLID. Response: Specify only those parameters which are valid with CRRLID. AMQ7A57 (iSeries)DSPMSG(*NO) specified with invalid parameters. Severity: 30 : Severe error Explanation: DSPMSG(*NO) was specified with one or more of BROWSE, DSPINF and WAIT which are invalid with DSPMSG(*NO). Response: Specify only those parameters which are valid with DSPMSG(*NO). AMQ7A58 (iSeries)RPLYQ required for DSPMSG(*NO) and RPLYMSG(*YES). Severity: 30 : Severe error Explanation: DSPMSG(*NO) and RPLYMSG(*YES) can not be specified without RPLYQ. Response: If DSPMSG(*NO) and RPLYMSG(*YES) are specified than RPLYQ must also be specified. AMQ7A59 (iSeries)RPLYQ required for DSPMSG(*NO) and OPTION not *NONE. Severity: 30 : Severe error Explanation: DSPMSG(*NO) and OPTION not *NONE can not be specified without RPLYQ. Response: If DSPMSG(*NO) and OPTION not *NONE are specified than RPLYQ must also be specified. AMQ7A5A (iSeries)Run WebSphere MQ Commands AMQ7A5B (iSeries)Non Persistent Message Class AMQ7A5C (iSeries)NPMCLASS not allowed with queue type *ALS or *RMT. Severity: 40 : Stop Error Explanation: The NPMCLASS parameter may not be specified for a queue of type *ALS or *RMT. Response: Remove the NPMCLASS parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again. AMQ7A5D (iSeries)MONQ not allowed with queue type *ALS or *RMT. Severity: 40 : Stop Error Explanation: The MONQ parameter may not be specified for a queue of type *ALS or *RMT. Response: Remove the MONQ parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again. AMQ7A5E (iSeries)STATQ not allowed with queue type *ALS or *RMT. Severity: 40 : Stop Error Explanation: The STATQ parameter may not be specified for a queue of type *ALS or *RMT. Response: Remove the STATQ parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again. AMQ7A5F (iSeries)ACCTQ not allowed with queue type *ALS or *RMT. Severity: 40 : Stop Error Explanation: The ACCTQ parameter may not be specified for a queue of type *ALS or *RMT. Response: Remove the ACCTQ parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again. AMQ7A60 (iSeries)All queue managers have been quiesced. Severity: 0 : Information Explanation: All queue managers have been successfully quiesced. Response: None. AMQ7A61 (iSeries)MQMNAME not valid for TRCEARLY(*YES). Severity: 40 : Stop Error Explanation: The MQMNAME parameter may only be specified for TRCEARLY(*NO). TRCEARLY(*YES) applies to all queue managers. Response: If TRCEARLY(*YES) is required remove MQMNAME from the command. AMQ7A62 (iSeries)MQMNAME not valid for SET(*END). Severity: 40 : Stop Error Explanation: The MQMNAME parameter may only be specified for SET(*ON) or SET(*OFF). SET(*END) applies to all queue managers. Response: If SET(*END) is required remove MQMNAME from the command. AMQ7B00 (iSeries)MQI Accounting AMQ7B01 (iSeries)Input file AMQ7B02 (iSeries)Queue Accounting AMQ7B03 (iSeries)Member containing input AMQ7B04 (iSeries)Accounting Interval AMQ7B05 (iSeries)Accounting Override AMQ7B06 (iSeries)Trace data size AMQ7B07 (iSeries)Perform replay only AMQ7B08 (iSeries)Activate backup AMQ7B09 (iSeries)No connection handles to display AMQ7B0A (iSeries)Trace Route Recording AMQ7B0B (iSeries)Activity Recording AMQ7B0C (iSeries)No queue manager connections to display AMQ7B0D (iSeries)No listener objects to display AMQ7B0E (iSeries)No service objects to display AMQ7B0F (iSeries)CLWLRANK not allowed with queue type *MDL. Severity: 40 : Stop Error Explanation: The CLWLRANK parameter may not be specified for a queue of type *MDL. Response: Remove the CLWLRANK parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again. AMQ7B10 (iSeries)CLWLPRTY not allowed with queue type *MDL. Severity: 40 : Stop Error Explanation: The CLWLPRTY parameter may not be specified for a queue of type *MDL. Response: Remove the CLWLPRTY parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again. AMQ7B11 (iSeries)LSRNAME not allowed with BACKLOG Severity: 40 : Stop Error Explanation: A listener object can not be specified with a listener backlog. Response: Specify either a listener object or a listener backlog. AMQ7B12 (iSeries)MONCHL not valid for channel type *CLTCN. Severity: 40 : Stop Error Explanation: The MONCHL parameter may not be specified with channel type *CLTCN. Response: Remove the MONCHL parameter from the command or, if the command is CRTMQMCHL, specify a different value for CHLTYPE. Then try the command again. AMQ7B13 (iSeries)STATCHL not valid for channel type *CLTCN. Severity: 40 : Stop Error Explanation: The STATCHL parameter may not be specified with channel type *CLTCN. Response: Remove the STATCHL parameter from the command or, if the command is CRTMQMCHL, specify a different value for CHLTYPE. Then try the command again. AMQ7B14 (iSeries)CLWLRANK only valid for channel types *CLUSSDR and *CLUSRCVR. Severity: 40 : Stop Error Explanation: The CLWLRANK parameter may only be specified with channel types *CLUSSDR or *CLUSRCVR. Response: Remove the CLWLRANK parameter from the command or, if the command is CRTMQMCHL, specify a different value for CHLTYPE. Then try the command again. AMQ7B15 (iSeries)CLWLPRTY only valid for channel types *CLUSSDR and *CLUSRCVR. Severity: 40 : Stop Error Explanation: The CLWLPRTY parameter may only be specified with channel types *CLUSSDR or *CLUSRCVR. Response: Remove the CLWLPRTY parameter from the command or, if the command is CRTMQMCHL, specify a different value for CHLTYPE. Then try the command again. AMQ7B16 (iSeries)CLWLWGHT only valid for channel types *CLUSSDR and *CLUSRCVR. Severity: 40 : Stop Error Explanation: The CLWLWGHT parameter may only be specified with channel types *CLUSSDR or *CLUSRCVR. Response: Remove the CLWLWGHT parameter from the command or, if the command is CRTMQMCHL, specify a different value for CHLTYPE. Then try the command again. AMQ7B17 (iSeries)CLWLUSEQ only allowed with queue type *LCL. Severity: 40 : Stop Error Explanation: The CLWLUSEQ parameter may only be specified for a queue of type *LCL. Response: Remove the CLWLUSEQ parameter from the command or, if the command is CRTMQMQ, specify a value of *LCL for QTYPE. Then try the command again. AMQ7B18 (iSeries)MCAUSRID not valid for channel type *CLTCN. Severity: 40 : Stop Error Explanation: The MCAUSRID parameter may not be specified with channel type *CLTCN. Response: Remove the MCAUSRID parameter from the command or, if the command is CRTMQMCHL, specify a different value for CHLTYPE. Then try the command again. 8000-8999 - Administration See Reading a message for an explanation of how to interpret these messages. AMQ8001WebSphere MQ queue manager created. Severity: 0 : Information Explanation: WebSphere MQ queue manager created. Response: None. AMQ8002WebSphere MQ queue manager deleted. Severity: 0 : Information Explanation: WebSphere MQ queue manager deleted. Response: None. AMQ8003WebSphere MQ queue manager started. Severity: 0 : Information Explanation: WebSphere MQ queue manager started. Response: None. AMQ8004WebSphere MQ queue manager ended. Severity: 0 : Information Explanation: WebSphere MQ queue manager ended. Response: None. AMQ8005WebSphere MQ queue manager changed. Severity: 0 : Information Explanation: WebSphere MQ queue manager changed. Response: None. AMQ8006WebSphere MQ queue created. Severity: 0 : Information Explanation: WebSphere MQ queue created. Response: None. AMQ8007WebSphere MQ queue deleted. Severity: 0 : Information Explanation: WebSphere MQ queue deleted. Response: None. AMQ8008WebSphere MQ queue changed. Severity: 0 : Information Explanation: WebSphere MQ queue changed. Response: None. AMQ8009 (iSeries)WebSphere MQ queue created by copying. Severity: 0 : Information Explanation: Queue created in library by copying. Response: None. AMQ8010WebSphere MQ process created. Severity: 0 : Information Explanation: WebSphere MQ process created. Response: None. AMQ8011WebSphere MQ process deleted. Severity: 0 : Information Explanation: WebSphere MQ process deleted. Response: None. AMQ8012WebSphere MQ process changed. Severity: 0 : Information Explanation: WebSphere MQ process changed. Response: None. AMQ8013 (iSeries)WebSphere MQ process copied. Severity: 0 : Information Explanation: Process created in library by copying. Response: None. AMQ8014WebSphere MQ channel created. Severity: 0 : Information Explanation: WebSphere MQ channel created. Response: None. AMQ8015WebSphere MQ channel deleted. Severity: 0 : Information Explanation: WebSphere MQ channel deleted. Response: None. AMQ8016WebSphere MQ channel changed. Severity: 0 : Information Explanation: WebSphere MQ channel changed. Response: None. AMQ8017 (iSeries)WebSphere MQ channel copied. Severity: 0 : Information Explanation: Channel created by copying. Response: None. AMQ8018Start WebSphere MQ channel accepted. Severity: 0 : Information Explanation: The channel is being started. The start channel function has been initiated. This involves a series of operations across the network before the channel is actually started. The channel status displays "BINDING" for a short period while communication protocols are negotiated with the channel with whom communication is being initiated. Response: None. AMQ8019Stop WebSphere MQ channel accepted. Severity: 0 : Information Explanation: The channel has been requested to stop. Response: None. AMQ8020Ping WebSphere MQ channel complete. Severity: 0 : Information Explanation: Ping channel complete. Response: None. AMQ8021Request to start WebSphere MQ Listener accepted. Severity: 0 : Information Explanation: The Request to start the Listener has been accepted and is being processed. Response: Should the request to start the listener be unsuccessful then information related to the error will be available in the queue manager error log. Once started the status of the listener may be monitored using the MQSC command 'DISPLAY LSSTATUS'. On iSeries the status of the listener may also be monitored using the 'WRKMQMLSR OPTION(*STATUS)' command. AMQ8022WebSphere MQ queue cleared. Severity: 0 : Information Explanation: All messages on queue have been deleted. Response: None. AMQ8023WebSphere MQ channel reset. Severity: 0 : Information Explanation: Channel has been reset. Response: None. AMQ8024WebSphere MQ channel initiator started. Severity: 0 : Information Explanation: The channel initiator for queue has been started. Response: None. AMQ8025WebSphere MQ channel resolved. Severity: 0 : Information Explanation: In doubt messages for WebSphere MQ channel have been resolved. Response: None. AMQ8026End WebSphere MQ queue manager accepted. Severity: 0 : Information Explanation: A controlled stop request has been initiated for queue manager . Response: None. AMQ8027WebSphere MQ command server started. Severity: 0 : Information Explanation: The command server has been started. Response: None. AMQ8028WebSphere MQ command server ended. Severity: 0 : Information Explanation: The command server has been stopped. Response: None. AMQ8029WebSphere MQ authority granted. Severity: 0 : Information Explanation: Authority for object granted. Response: None. AMQ8030WebSphere MQ authority revoked. Severity: 0 : Information Explanation: Authority for object revoked. Response: None. AMQ8031 (iSeries)Message Queue Manager connected. Severity: 0 : Information Explanation: The message queue manager has been connected. Response: None. AMQ8032 (iSeries)Message Queue Manager disconnected. Severity: 0 : Information Explanation: The message queue manager has been disconnected. Response: None. AMQ8033WebSphere MQ object recreated. Severity: 0 : Information Explanation: MQ object has been recreated from image. Response: None. AMQ8034WebSphere MQ object image recorded. Severity: 0 : Information Explanation: Image of MQ object has been recorded. Response: None. AMQ8035WebSphere MQ Command Server Status . . : Running Severity: 0 : Information Explanation: None. Response: None. AMQ8036WebSphere MQ command server status . . : Stopping Severity: 0 : Information Explanation: None. Response: None. AMQ8037WebSphere MQ command server status . . : Starting Severity: 0 : Information Explanation: None. Response: None. AMQ8038WebSphere MQ command server status . . : Running with queue disabled Severity: 0 : Information Explanation: None. Response: None. AMQ8039WebSphere MQ command server status . . : Stopped Severity: 0 : Information Explanation: None. Response: None. AMQ8040WebSphere MQ command server ending. Severity: 0 : Information Explanation: None. Response: None. AMQ8041The queue manager cannot be restarted or deleted because processes, that were previously connected, are still running. Severity: 40 : Stop Error Explanation: Processes, that were connected to the queue manager the last time it was running, are still active. The queue manager cannot be restarted. Response: Stop the processes and try to start the queue manager. AMQ8041 (iSeries)The queue manager cannot be restarted or deleted. Severity: 40 : Stop Error Explanation: Jobs that were connected to the queue manager the last time it was running, are still active. The queue manager cannot be restarted or deleted. Response: Use option 22 from WRKMQM to identify which jobs are connected to the queue manager. End the connected jobs and then retry the command. AMQ8042Process is still running. Severity: 0 : Information AMQ8043Non runtime application attempted to connect to runtime only queue manager. Severity: 0 : Information Explanation: A non runtime application attempted to connect to a queue manager on a node where support for non runtime applications has not been installed. The connect attempt will be rejected with a reason of MQRC_ENVIRONMENT_ERROR. Response: If the node is intended to support only runtime applications, investigate why a non runtime application has attempted to connect to the queue manager. If the node is intended to support non runtime only applications, investigate if the base option has been installed. The base option must be installed if non runtime applications are to run on this node. AMQ8044 (Windows)An error occurred while removing the queue manager from the Active Directory. Severity: 0 : Information Explanation: The attempt to remove the queue manager from the Windows Active Directory failed. This may be because the appropriate entry could not be opened or modified, or the Service Control Point has already been removed. Response: Check that your account has the authority to delete objects from the Active Directory, and that the entry has not already been deleted. AMQ8045 (Windows)An error occurred while removing the queue manager from the Service Control Manager. Severity: 0 : Information Explanation: The attempt to remove the queue manager from the Windows registry failed. This may be because the appropriate entry could not be opened or modified. Response: Check that the registry has sufficient space on your disk to grow and that your account has the authority to modify it. AMQ8046Migrating objects for . Severity: 0 : Information Response: None. AMQ8047Channel migration statistics : migrated. failed. Severity: 0 : Information Explanation: Information on the number of channel objects migrated from previous versions of WebSphere MQ channel definitions as well as any failures that occurred. Response: None. AMQ8048Default objects statistics : created. replaced. failed. Severity: 0 : Information Explanation: Information on the number of objects created or replaced successfully as well as any failures that occurred while creating the default objects. Response: None. AMQ8049Object . Unable to create or replace. Severity: 20 : Error Explanation: While creating or replacing the default object for WebSphere MQ queue manager an error occurred. The error was due to improper authorization. The reason code is . Response: Check this log for more details of what the problem may be. Make sure there are sufficient resources such as disk space and storage. For damaged or corrupted objects, replace these from backup objects. If all else fails, delete the queue manager using dltmqm and create it again using crtmqm. AMQ8050Creating or replacing default objects for . Severity: 0 : Information Response: None. AMQ8051For details of the failures that occurred, please check AMQERR01.LOG. Severity: 0 : Information Response: None. AMQ8052Completing setup. Severity: 0 : Information Response: None. AMQ8053Object . Unable to create or replace. Severity: 20 : Error Explanation: While creating or replacing the default object for WebSphere MQ queue manager an error occurred. The error was due to a broken connection. The reason code is . Response: Check this log for more details of what the problem may be. Make sure there is sufficient resources such as disk space and storage. For damaged or corrupted objects, replace these from backup objects. If all else fails, delete the queue manager using dltmqm and create it again using crtmqm. AMQ8054Object . Unable to create or replace. Severity: 20 : Error Explanation: While creating or replacing the default object for WebSphere MQ queue manager an error occurred. The error was due to unavailable storage. The reason code is . Response: Check this log for more details of what the problem may be. Make sure there is sufficient resources such as disk space and storage. For damaged or corrupted objects, replace these from backup objects. If all else fails, delete the queue manager using dltmqm and create it again using crtmqm. AMQ8055Object . Unable to create or replace. Severity: 20 : Error Explanation: While creating or replacing the default object for WebSphere MQ queue manager an error occurred. The error was due to a damaged object. The reason code is . Response: Check this log for more details of what the problem may be. Make sure there is sufficient resources such as disk space and storage. For damaged or corrupted objects, replace these from backup objects. If all else fails, delete the queue manager using dltmqm and create it again using crtmqm. AMQ8056Object . Unable to create or replace. Severity: 20 : Error Explanation: While creating or replacing the default object for WebSphere MQ queue manager an error occurred. The error was due to a channel definition error. The error code is (X). Response: Check this log for more details of what the problem may be. Make sure there is sufficient resources such as disk space and storage. For damaged or corrupted objects, replace these from backup objects. If all else fails, delete the queue manager using dltmqm and create it again using crtmqm. AMQ8057Object . Unable to create or replace. Severity: 20 : Error Explanation: While creating or replacing the default object for WebSphere MQ queue manager an error occurred. The error was due to invalid records in the channel definition file. The error code is (X). Response: Check this log for more details of what the problem may be. Make sure there is sufficient resources such as disk space and storage. For damaged or corrupted objects, replace these from backup objects. If all else fails, delete the queue manager using dltmqm and create it again using crtmqm. AMQ8058Object . Unable to create or replace. Severity: 20 : Error Explanation: While creating or replacing the default object for WebSphere MQ queue manager an error occurred. The error was due to not finding the channel definition file. The error code is (X). Response: Check this log for more details of what the problem may be. Make sure there is sufficient resources such as disk space and storage. For damaged or corrupted objects, replace these from backup objects. If all else fails, delete the queue manager using dltmqm and create it again using crtmqm. AMQ8059Object . Unable to create or replace. Severity: 20 : Error Explanation: While creating or replacing the default object for WebSphere MQ queue manager an error occurred. The error was due to an unexpected error, error code (X). Response: Check this log for more details of what the problem may be. Make sure there is sufficient resources such as disk space and storage. For damaged or corrupted objects, replace these from backup objects. If all else fails, delete the queue manager using dltmqm and create it again using crtmqm. AMQ8061 (Windows)Command is not valid. Severity: 10 : Warning Explanation: The command at line in the WebSphere MQ service command file for queue manager is not valid for use in the service command file. The line is ignored. Response: Check the contents of the file and retry the operation. AMQ8062 (Windows)Unexpected return code, , from command . Severity: 10 : Warning Explanation: An unexpected return code, , was returned by command . This command was issued by the WebSphere MQ service for queue manager . Response: Verify that the command and parameters are correct. AMQ8063 (Windows)Not authorized to issue command . Severity: 20 : Error Explanation: The current user is not authorized to issue the command . The command is ignored. Response: Add the user to the local 'mqm' security group and retry the operation. AMQ8064 (Windows)Not authorized to start trusted application. Severity: 20 : Error Explanation: The user is not authorized to start the trusted application . The application has not started. Response: Add the user to the local 'mqm' security group and restart the application. AMQ8065 (Windows)Local group not found. Severity: 20 : Error Explanation: The local group is unavailable. It is not possible to verify that the user is authorized. The function cannot continue. Response: Create the required local group and retry the operation. AMQ8066 (Windows)Local mqm group not found. Severity: 20 : Error Explanation: The local mqm group is unavailable. It is not possible to verify that the user is authorized. The function cannot continue. Response: Create the local mqm group and retry the operation. AMQ8067WebSphere MQ channel auto-defined. Severity: 0 : Information Explanation: Channel auto-defined. Response: None. AMQ8068Setup completed. Severity: 0 : Information Response: None. AMQ8069ApplicationGroup for the crtmqm command does not contain the mqm userid. Severity: 40 : Stop Error Explanation: WebSphere MQ queue manager not created. The ApplicationGroup specified for the crtmqm command must contain the mqm userid when the RestrictedMode option (-g) is specified. Response: None. AMQ8070ApplicationGroup for crtmqm command is not defined. Severity: 40 : Stop Error Explanation: WebSphere MQ queue manager not created. RestrictedMode option (-g) specified, but the ApplicationGroup does not exist. Response: None. AMQ8071RestrictedMode option not supported on this platform. Severity: 40 : Stop Error Explanation: WebSphere MQ queue manager not created. The RestrictedMode option was specified but is not supported on this platform. Response: None. AMQ8072 (Windows)Not authorized to administer channels. Severity: 10 : Warning Explanation: The command server for queue manager received an administration command for channels. The user is not authorized to administer WebSphere MQ channels. The command server has not processed the command. Response: Add the user to the local 'mqm' security group, and ensure that the security policy is set as required. AMQ8073 (Windows)Authorization failed because SID: () could not be resolved. Severity: 10 : Warning Explanation: The Object Authority Manager was unable to resolve the specified SID into entity and domain information. Response: Ensure that the application provides a SID that is recognized on this system, that all necessary domain controllers are available, and that the security policy is set as you required. AMQ8074 (Windows)Authorization failed as the SID does not match the entity . Severity: 10 : Warning Explanation: The Object Authority Manager received inconsistent data - the supplied SID does not match that of the supplied entity information. Response: Ensure that the application is supplying valid entity and SID information. AMQ8075 (Windows)Authorization failed because the SID for entity cannot be obtained. Severity: 10 : Warning Explanation: The Object Authority Manager was unable to obtain a SID for the specified entity. Response: Ensure that the entity is valid, and that all necessary domain controllers are available. AMQ8076 (Windows)Authorization failed because no SID was supplied for entity . Severity: 10 : Warning Explanation: The Object Authority Manager was not supplied with SID information for the specified entity, and the security policy is set to 'NTSIDsRequired'. Response: Ensure that the application is supplying a valid SID, and that the security policy is set as you require. AMQ8077 (Windows)Entity has insufficient authority to access object . Severity: 10 : Warning Explanation: The specified entity is not authorized to access the required object. The following requested permissions are unauthorized: Response: Ensure that the correct level of authority has been set for this entity against the required object, or ensure that the entity is a member of a privileged group. AMQ8078Waiting for queue manager to end. Severity: 0 : Information Response: None. AMQ8079 (iSeries)WebSphere MQ trigger monitor job started. Severity: 0 : Information Explanation: The message queue manager trigger monitor job has been started for queue manager to process messages on the selected initiation queue. See previously issued messages for job details.' Response: None. AMQ8079 (Windows)Access was denied when attempting to retrieve group membership information for user . Severity: 10 : Warning Explanation: WebSphere MQ, running with the authority of user , was unable to retrieve group membership information for the specified user. Response: Ensure Active Directory access permissions allow user to read group memberships for user . To retrieve group membership information for a domain user, MQ must run with the authority of a domain user. AMQ8080 (iSeries)WebSphere MQ trigger monitor job start failed. Severity: 40 : Stop Error Explanation: Message queue manager trigger job failed to start for manager . Failure reason code is . See previously issued messages for more information.' Response: None. AMQ8081 (Windows)Not authorized to administer queue managers. Severity: 10 : Warning Explanation: The command server for queue manager received an administration command for a queue manager. The user is not authorized to administer WebSphere MQ queue managers. The command server has not processed the command. Response: Add the user to the local 'mqm' security group, and ensure that the security policy is set as required. AMQ8082 (Windows)Not authorized to administer clusters. Severity: 10 : Warning Explanation: The command server for queue manager received an administration command for clusters. The user is not authorized to administer WebSphere MQ clusters. The command server has not processed the command. Response: Add the user to the local 'mqm' security group, and ensure that the security policy is set as required. AMQ8083WebSphere MQ queue manager starting. Severity: 0 : Information Explanation: WebSphere MQ queue manager starting. Response: None. AMQ8084WebSphere MQ connection not found. Severity: 40 : Stop Error Explanation: The connection specified does not exist. Response: Correct the connection name and then try the command again. AMQ8085WebSphere MQ queue manager is being started for replay. Severity: 0 : Information Explanation: WebSphere MQ queue manager is being started for replay. The strmqm command has been issued with the '-r' option. see the WebSphere MQ System Administration documentation for details. Response: None. AMQ8086WebSphere MQ queue manager is being activated. Severity: 0 : Information Explanation: WebSphere MQ queue manager is being activated. The strmqm command has been issued with the '-a' option. see the WebSphere MQ System Administration documentation for details. Response: None. AMQ8086 (iSeries)WebSphere MQ queue manager is being activated. Severity: 0 : Information Explanation: WebSphere MQ queue manager is being activated. The STRMQM command has been issued with the ACTIVATE(*YES) option. see the WebSphere MQ System Administration documentation for further details. Response: None. AMQ8087Attempt to migrate listener to a QM object failed with . Severity: 20 : Error Explanation: Whilst processing legacy services, listener could not be migrated to an MQ object named , the object creation failed with . Response: Save the generated output files and contact your IBM support center. AMQ8088Attempt to migrate trigger monitor to a QM object failed with . Severity: 20 : Error Explanation: Whilst processing legacy services, trigger monitor could not be migrated to an MQ object named , the object creation failed with . Response: Save the generated output files and contact your IBM support center. AMQ8089Attempt to migrate channel service to a QM object failed with . Severity: 20 : Error Explanation: Whilst processing legacy services, channel service could not be migrated to an MQ object named , the object creation failed with . Response: Save the generated output files and contact your IBM support center. AMQ8090Attempt to migrate channel initiator to a QM object failed with . Severity: 20 : Error Explanation: Whilst processing legacy services, channel initiator could not be migrated to an MQ object named , the object creation failed with . Response: Save the generated output files and contact your IBM support center. AMQ8091Attempt to migrate custom service to a QM object failed with . Severity: 20 : Error Explanation: Whilst processing legacy services, custom service could not be migrated to an MQ object named , the object creation failed with . Response: Save the generated output files and contact your IBM support center. AMQ8092Service migration statistics : migrated. failed. Severity: 0 : Information Explanation: Information on the number of service objects migrated from previous versions of WebSphere MQ for Windows services as well as any failures that occurred. Response: None. AMQ8101WebSphere MQ error () has occurred. Severity: 40 : Stop Error Explanation: An unexpected reason code with hexadecimal value was received from the WebSphere MQ queue manager during command processing. (Note that hexadecimal values in the range X'07D1'-X'0BB7' correspond to MQI reason codes 2001-2999.) More information might be available in the log. If the reason code value indicates that the error was associated with a particular parameter, the parameter concerned is . Response: Correct the error and then try the command again. AMQ8102WebSphere MQ object name specified in not valid. Severity: 30 : Severe error Explanation: The object name specified in is not valid. The length of the name must not exceed 48 characters, or 20 characters if it is a channel name. The name should contain the following characters only: lowercase a-z, uppercase A-Z, numeric 0-9, period (.), forward slash (/), underscore (_) and percent sign (%). Response: Change the length of the parameter value or change the parameter value to contain a valid combination of characters, then try the command again. AMQ8103Insufficient storage available. Severity: 40 : Stop Error Explanation: There was insufficient storage available to perform the requested operation. Response: Free some storage and then try the command again. AMQ8104WebSphere MQ directory not found. Severity: 40 : Stop Error Explanation: Directory was not found. This directory is created when WebSphere MQ is installed successfully. Refer to the log for more information. Response: Verify that installation of WebSphere MQ was successful. Correct the error and then try the command again. AMQ8105Object error. Severity: 40 : Stop Error Explanation: An object error occurred. Refer to the log for more information. Response: Correct the error and then try the command again. AMQ8106WebSphere MQ queue manager being created. Severity: 0 : Information Explanation: The queue manager is being created. Response: Wait for the creation process to complete and then try the command again. AMQ8107WebSphere MQ queue manager running. Severity: 10 : Warning Explanation: The queue manager is running. Response: None. AMQ8108WebSphere MQ queue manager ending. Severity: 10 : Warning Explanation: The queue manager is ending. Response: Wait for the queue manager to end and then try the command again. AMQ8109WebSphere MQ queue manager being deleted. Severity: 40 : Stop Error Explanation: The queue manager is being deleted. Response: Wait for the deletion process to complete. AMQ8110WebSphere MQ queue manager already exists. Severity: 40 : Stop Error Explanation: The queue manager already exists. Response: None. AMQ8111 (iSeries)Message Queue Manager exists under a different name. Severity: 30 : Severe error Explanation: A message queue manager exists with a name different from the value specified in . Response: Change the parameter value to the name of the existing message queue manager and then try the command again. AMQ8112 (iSeries)PRCNAME not allowed with queue type *ALS or *RMT. Severity: 40 : Stop Error Explanation: The PRCNAME parameter may not be specified for a queue of type *ALS or *RMT. Response: Remove the PRCNAME parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again. AMQ8113 (iSeries)TRGENBL not allowed with queue type *ALS or *RMT. Severity: 40 : Stop Error Explanation: The TRGENBL parameter may not be specified for a queue of type *ALS or *RMT. Response: Remove the TRGENBL parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again. AMQ8114 (iSeries)GETENBL not allowed with queue type *RMT. Severity: 40 : Stop Error Explanation: The GETENBL parameter may not be specified for a queue of type *RMT. Response: Remove the GETENBL parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again. AMQ8115 (iSeries)SHARE not allowed with queue type *ALS or *RMT. Severity: 40 : Stop Error Explanation: The SHARE parameter may not be specified for a queue of type *ALS or *RMT. Response: Remove the SHARE parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again. AMQ8116 (iSeries)MSGDLYSEQ not allowed with queue type *ALS or *RMT. Severity: 40 : Stop Error Explanation: The MSGDLYSEQ parameter may not be specified for a queue of type *ALS or *RMT. Response: Remove the MSGDLYSEQ parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again. AMQ8117WebSphere MQ queue manager deletion incomplete. Severity: 40 : Stop Error Explanation: Deletion of queue manager was only partially successful. An object was not found, or could not be deleted. Refer to the log for more information. Response: Delete any remaining queue manager objects. AMQ8118WebSphere MQ queue manager does not exist. Severity: 40 : Stop Error Explanation: The queue manager does not exist. Response: Either create the queue manager (crtmqm command) or correct the queue manager name used in the command and then try the command again. AMQ8119 (iSeries)TRGTYPE not allowed with queue type *ALS or *RMT. Severity: 40 : Stop Error Explanation: The TRGTYPE parameter may not be specified for a queue of type *ALS or *RMT. Response: Remove the TRGTYPE parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again. AMQ8120 (iSeries)TRGDEPTH not allowed with queue type *ALS or *RMT. Severity: 40 : Stop Error Explanation: The TRGDEPTH parameter may not be specified for a queue of type *ALS or *RMT. Response: Remove the TRGDEPTH parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again. AMQ8121 (iSeries)TRGMSGPTY not allowed with queue type *ALS or *RMT. Severity: 40 : Stop Error Explanation: The TRGMSGPTY parameter may not be specified for a queue of type *ALS or *RMT. Response: Remove the TRGMSGPTY parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again. AMQ8122 (iSeries)TRGDATA not allowed with queue type *ALS or *RMT. Severity: 40 : Stop Error Explanation: The TRGDATA parameter may not be specified for a queue of type *ALS or *RMT. Response: Remove the TRGDATA parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again. AMQ8123 (iSeries)RTNITV not allowed with queue type *ALS or *RMT. Severity: 40 : Stop Error Explanation: The RTNITV parameter may not be specified for a queue of type *ALS or *RMT. Response: Remove the RTNITV parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again. AMQ8124 (iSeries)MAXMSGLEN not allowed with queue type *ALS or *RMT. Severity: 40 : Stop Error Explanation: The MAXMSGLEN parameter may not be specified for a queue of type *ALS or *RMT. Response: Remove the MAXMSGLEN parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again. AMQ8125 (iSeries)BKTTHLD not allowed with queue type *ALS or *RMT. Severity: 40 : Stop Error Explanation: The BKTTHLD parameter may not be specified for a queue of type *ALS or *RMT. Response: Remove the BKTTHLD parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again. AMQ8126 (iSeries)BKTQNAME not allowed with queue type *ALS or *RMT. Severity: 40 : Stop Error Explanation: The BKTQNAME parameter may not be specified for a queue of type *ALS or *RMT. Response: Remove the BKTQNAME parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again. AMQ8127 (iSeries)INITQNAME not allowed with queue type *ALS or *RMT. Severity: 40 : Stop Error Explanation: The INITQNAME parameter may not be specified for a queue of type *ALS or *RMT. Response: Remove the INITQNAME parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again. AMQ8128 (iSeries)USAGE not allowed with queue type *ALS or *RMT. Severity: 40 : Stop Error Explanation: The USAGE parameter may not be specified for a queue of type *ALS or *RMT. Response: Remove the USAGE parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again. AMQ8129 (iSeries)DFNTYPE only allowed with queue type *MDL. Severity: 40 : Stop Error Explanation: The DFNTYPE parameter may only be specified for a queue of type *MDL. Response: Remove the DFNTYPE parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again. AMQ8130 (iSeries)TGTQNAME only allowed with queue type *ALS. Severity: 40 : Stop Error Explanation: The TGTQNAME parameter may only be specified for a queue of type *ALS. Response: Remove the TGTQNAME parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again. AMQ8131 (iSeries)RMTQNAME only allowed with queue type *RMT. Severity: 40 : Stop Error Explanation: The RMTQNAME parameter may only be specified for a queue of type *RMT. Response: Remove the RMTQNAME parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again. AMQ8132 (iSeries)RMTMQMNAME only allowed with queue type *RMT. Severity: 40 : Stop Error Explanation: The RMTMQMNAME parameter may only be specified for a queue of type *RMT. Response: Remove the RMTMQMNAME parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again. AMQ8133 (iSeries)TMQNAME only allowed with queue type *RMT. Severity: 40 : Stop Error Explanation: The TMQNAME parameter may only be specified for a queue of type *RMT. Response: Remove the TMQNAME parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again. AMQ8134 (iSeries)HDNBKTCNT not allowed with queue type *ALS or *RMT. Severity: 40 : Stop Error Explanation: The HDNBKTCNT parameter may not be specified for a queue of type *ALS or *RMT. Response: Remove the HDNBKTCNT parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again. AMQ8135Not authorized. Severity: 40 : Stop Error Explanation: You are not authorized to perform the requested operation for the WebSphere MQ object specified in . Either you are not authorized to perform the requested operation, or you are not authorized to the specified MQ object. For a copy command, you may not be authorized to the specified source MQ object, or, for a create command, you may not be authorized to the system default MQ object of the specified type. Response: Obtain the necessary authority from your security officer or WebSphere MQ administrator. Then try the command again. AMQ8136 (iSeries)Error detected by prompt control program. Severity: 30 : Severe error Explanation: A prompt control program detected errors. Response: See the previously listed messages in the job log. Correct the errors and then prompt for the command again. AMQ8137WebSphere MQ queue manager already starting. Severity: 40 : Stop Error Explanation: The strmqm command was unsuccessful because the queue manager is already starting. Response: Wait for the strmqm command to complete. AMQ8138The WebSphere MQ queue has an incorrect type. Severity: 40 : Stop Error Explanation: The operation is not valid with queue because it is not a local queue. Response: Change the QNAME parameter to specify a queue of the correct type. AMQ8139Already connected. Severity: 10 : Warning Explanation: A connection to the WebSphere MQ queue manager already exists. Response: None. AMQ8140Resource timeout error. Severity: 40 : Stop Error Explanation: A timeout occurred in the communication between internal WebSphere MQ queue manager components. This is most likely to occur when the system is heavily loaded. Response: Wait until the system is less heavily loaded, then try the command again. AMQ8141WebSphere MQ queue manager starting. Severity: 40 : Stop Error Explanation: The queue manager is starting. Response: Wait for the queue manager startup process to complete and then try the command again. AMQ8142WebSphere MQ queue manager stopped. Severity: 40 : Stop Error Explanation: The queue manager is stopped. Response: Use the strmqm command to start the queue manager, and then try the command again. AMQ8143WebSphere MQ queue not empty. Severity: 40 : Stop Error Explanation: The queue specified in is not empty or contains uncommitted updates. Response: Commit or roll back any uncommitted updates. If the command is DELETE QLOCAL, use the CLEAR QLOCAL command to clear the messages from the queue. Then try the command again. AMQ8144Log not available. Severity: 40 : Stop Error Explanation: The WebSphere MQ logging resource is not available. Response: Use the dltmqm command to delete the queue manager and then the crtmqm command to create the queue manager. Then try the command again. AMQ8145Connection broken. Severity: 40 : Stop Error Explanation: The connection to the WebSphere MQ queue manager failed during command processing. This may be caused by an endmqm command being issued by another user, or by a queue manager error. Response: Use the strmqm command to start the message queue manager, wait until the message queue manager has started, and try the command again. AMQ8146WebSphere MQ queue manager not available. Severity: 40 : Stop Error Explanation: The queue manager is not available because it has been stopped or has not been created. Response: Use the crtmqm command to create the message queue manager, or the strmqm command to start the message queue manager as necessary. Then try the command again. AMQ8146 (iSeries)WebSphere MQ queue manager not available. Severity: 40 : Stop Error Explanation: The queue manager is not available because it has been stopped or has not been created. Response: Use the CRTMQM command to create the message queue manager or the STRMQM command to start the message queue manager as necessary, then retry the command. If a queue manager was not specified, ensure that a default queue manager has been created and is started using the WRKMQM command. AMQ8147WebSphere MQ object not found. Severity: 40 : Stop Error Explanation: If the command entered was Change or Display, the object specified does not exist. If the command entered was Copy, the source object does not exist. If the command entered was Create, the system default MQ object of the specified type does not exist. Response: Correct the object name and then try the command again or, if you are creating a new queue or process object, either specify all parameters explicitly or ensure that the system default object of the required type exists. The system default queue names are SYSTEM.DEFAULT.LOCAL.QUEUE, SYSTEM.DEFAULT.ALIAS.QUEUE and SYSTEM.DEFAULT.REMOTE.QUEUE. The system default process name is SYSTEM.DEFAULT.PROCESS. AMQ8147 (iSeries)WebSphere MQ object not found. Severity: 40 : Stop Error Explanation: If the command entered was Change or Display, the MQ object specified does not exist. If the command entered was Copy, the source MQ object does not exist. If the command entered was Create, the system default MQ object of the specified type does not exist. Response: Correct the MQ object name and then try the command again or, if you are creating a new MQ queue or process object, either specify all parameters explicitly or ensure that the system default object of the required type exists. The system default queue names are SYSTEM.DEFAULT.LOCAL.QUEUE, SYSTEM.DEFAULT.ALIAS.QUEUE and SYSTEM.DEFAULT.REMOTE.QUEUE. The system default process name is SYSTEM.DEFAULT.PROCESS. AMQ8148WebSphere MQ object in use. Severity: 40 : Stop Error Explanation: The object specified in is in use by an MQ application program. Response: Wait until the object is no longer in use and then try the command again. If the command is ALTER or CHANGE, specify FORCE to force the processing of the object regardless of any application program affected by the change. If the object is the dead-letter queue and the open input count is nonzero, it may be in use by an MQ channel. If the object is another queue object with a nonzero open output count, it may be in use by a MQ channel (of type RCVR or RQSTR). In either case, use the STOP CHANNEL and START CHANNEL commands to stop and restart the channel in order to solve the problem. To alter the queue USAGE the FORCE option must be used if the queue is not empty. AMQ8149WebSphere MQ object damaged. Severity: 40 : Stop Error Explanation: The object specified in is damaged. Response: The object contents are not valid. Issue the DISPLAY CHANNEL, DISPLAY QUEUE, or DISPLAY PROCESS command, as required, to determine the name of the damaged object. Issue the DEFINE command, for the appropriate object type, to replace the damaged object, then try the command again. AMQ8150WebSphere MQ object already exists. Severity: 40 : Stop Error Explanation: The object specified for could not be created because it already exists. Response: Check that the name is correct and try the command again specifying REPLACE, or delete the object. Then try the command again. AMQ8151WebSphere MQ object has different type. Severity: 40 : Stop Error Explanation: The type specified for object is different from the type of the object being altered or defined. Response: Use the correct MQ command for the object type, and then try the command again. AMQ8152Source WebSphere MQ object has different type. Severity: 40 : Stop Error Explanation: The type of the source object is different from that specified. Response: Correct the name of the command, or source object name, and then try the command again, or try the command using the REPLACE option. AMQ8153Insufficient disk space for the specified queue. Severity: 40 : Stop Error Explanation: The command failed because there was insufficient disk space available for the specified queue. Response: Release some disk space and then try the command again. AMQ8154API exit load error. Severity: 40 : Stop Error Explanation: The WebSphere MQ queue manager was unable to load the API crossing exit. Response: Ensure that the API crossing exit program is valid, and that its name and directory are correctly specified. Correct any error and then try the command again. AMQ8155Connection limit exceeded. Severity: 40 : Stop Error Explanation: The queue manager connection limit has been exceeded. Response: The maximum limit on the number of WebSphere MQ application programs that may be connected to the queue manager has been exceeded. Try the command later. AMQ8156WebSphere MQ queue manager quiescing. Severity: 40 : Stop Error Explanation: The queue manager is quiescing. Response: The queue manager was stopping with -c specified for endmqm. Wait until the queue manager has been restarted and then try the command again. AMQ8157Security error. Severity: 40 : Stop Error Explanation: An error was reported by the security manager program. Response: Inform your systems administrator, wait until the problem has been corrected, and then try the command again. AMQ8158 (iSeries)API exit not found. Severity: 40 : Stop Error Explanation: The API crossing exit program was not found. Response: Ensure that the API crossing exit program for the MQI exists, and that its name and library are correctly specified. Correct any errors and then try the command again. AMQ8159 (iSeries)MAXDEPTH not allowed with queue type *ALS or *RMT. Severity: 40 : Stop Error Explanation: The MAXDEPTH parameter may not be specified for a queue of type *ALS or *RMT. Response: Remove the MAXDEPTH parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again. AMQ8160 (iSeries)DFTSHARE not allowed with queue type *ALS or *RMT. Severity: 40 : Stop Error Explanation: The DFTSHARE parameter may not be specified for a queue of type *ALS or *RMT. Response: Remove the DFTSHARE parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again. AMQ8161 (iSeries)AUT(*MQMPASSID) only allowed with OBJTYPE(*ADM). Severity: 40 : Stop Error Explanation: AUT(*MQMPASSID) may only be specified with OBJTYPE(*ADM). Response: Change the AUT parameter to specify another value and then try the command again. AMQ8162 (iSeries)AUT(*MQMPASSALL) only allowed with OBJTYPE(*ADM). Severity: 40 : Stop Error Explanation: AUT(*MQMPASSALL) may only be specified with OBJTYPE(*ADM). Response: Change the AUT parameter to specify another value and then try the command again. AMQ8163 (iSeries)AUT(*MQMSETID) only allowed with OBJTYPE(*ADM). Severity: 40 : Stop Error Explanation: AUT(*MQMSETID) may only be specified with OBJTYPE(*ADM). Response: Change the AUT parameter to specify another value and then try the command again. AMQ8164 (iSeries)AUT(*MQMSETALL) only allowed with OBJTYPE(*ADM). Severity: 40 : Stop Error Explanation: AUT(*MQMSETALL) may only be specified with OBJTYPE(*ADM). Response: Change the AUT parameter to specify another value and then try the command again. AMQ8165 (iSeries)AUT(*MQMALTUSR) only allowed with OBJTYPE(*ADM). Severity: 40 : Stop Error Explanation: AUT(*MQMALTUSR) may only be specified with OBJTYPE(*ADM). Response: Change the AUT parameter to specify another value and then try the command again. AMQ8166 (iSeries)WebSphere MQ reference object not found. Severity: 40 : Stop Error Explanation: The object specified by the REFOBJ and REFOBJTYPE parameters does not exist. Response: Correct the reference object name and type, and then try the command again. AMQ8167 (iSeries)Referenced object name not valid. Severity: 30 : Severe error Explanation: The referenced object name specified in REFOBJ is not valid. The length of the name must not exceed 48 characters and the name should contain the following characters only: lowercase a-z, uppercase A-Z, numeric 0-9, period (.), forward slash (/), underscore (_) and percent sign (%). Response: Change the length of the parameter value or change the parameter value to contain a valid combination of characters. Then try the command again. AMQ8168 (iSeries)User profile name for parameter USER not found. Severity: 30 : Severe error Explanation: The user profile name specified for parameter USER could not be found on the system, and is not the special value *PUBLIC. Response: Correct the user profile name, or use the Create User Profile (CRTUSRPRF) command to create the user profile then try the request again. AMQ8169 (iSeries)Authorization list for parameter AUTL does not exist. Severity: 30 : Severe error Explanation: The authorization list specified for parameter AUTL does not exist. It may have been destroyed. Response: Either specify an authorization list that exists, or create the authorization list using the Create Authorization List (CRTAUTL) command. Try the request again. AMQ8170 (iSeries)REFOBJTYPE(*OBJTYPE) and OBJTYPE(*ALL) cannot be used together. Severity: 30 : Severe error Explanation: REFOBJTYPE(*OBJTYPE) can be specified only with a specific object type. Response: Change the REFOBJTYPE or OBJTYPE input value to a specific object type. Then try the Grant Authority (GRTMQMAUT) command again. AMQ8171 (iSeries)Authority of *AUTL is only allowed with USER(*PUBLIC). Severity: 30 : Severe error Explanation: AUT(*AUTL) was specified on either the Grant Authority (GRTMQMAUT) command or the Revoke Authority (RVKMQMAUT) command with the USER parameter not set to *PUBLIC. Only the authority for *PUBLIC can be deferred to the authorization list. Response: Change the AUT parameter to the authorities that are correct for the users or change the USER parameter to *PUBLIC. Then try the command again. AMQ8172Already disconnected. Severity: 10 : Warning Explanation: The MQI reason code of 2018 was returned from the WebSphere MQ queue manager in response to an MQDISC request issued during command processing. Response: None. AMQ8173No processes to display. Severity: 0 : Information Explanation: There are no matching processes defined on this system. Response: Using the DEFINE PROCESS command to create a process. AMQ8174No queues to display. Severity: 0 : Information Explanation: There are no matching queues defined on this system. Response: Use the appropriate command to define a queue of the type that you require, that is, DEFINE QALIAS, DEFINE QLOCAL, DEFINE QMODEL, or DEFINE QREMOTE. AMQ8175 (iSeries)WebSphere MQ trace has started. Severity: 0 : Information Explanation: The trace has started successfully. Response: None. AMQ8176 (iSeries)WebSphere MQ trace has been written. Severity: 0 : Information Explanation: The trace has been written successfully. Response: None. AMQ8177 (iSeries)WebSphere MQ trace has stopped. Severity: 0 : Information Explanation: The trace has stopped. Response: None. AMQ8178 (iSeries)WebSphere MQ trace did not start. Severity: 40 : Stop Error Explanation: The trace did not start successfully. Response: None. AMQ8179 (iSeries)WebSphere MQ trace output error. Severity: 40 : Stop Error Explanation: The trace was not output successfully. Response: None. AMQ8180 (iSeries)WebSphere MQ trace end request failed. Severity: 40 : Stop Error Explanation: Your request to end the trace was not successful. Response: None. AMQ8181 (iSeries)No jobs to display. Severity: 10 : Warning Explanation: There are no matching jobs running on this system. Response: Specify another job name from the STRMQMSRV command. AMQ8182 (iSeries)WebSphere MQ trace already off. Severity: 10 : Warning Explanation: An attempt was made to set trace off, but the trace is not active. Response: None. AMQ8183 (iSeries)WebSphere MQ trace already running. Severity: 10 : Warning Explanation: An attempt was made to start trace, but trace is already running. Response: Either leave trace running as it is, or, if you want to change the trace settings, turn trace off and then turn it on again with appropriate settings. AMQ8184 (iSeries)Requested job cannot be found Severity: 10 : Warning Explanation: The job specified cannot be found in the table that controls WebSphere MQ for iSeries trace. As a result no trace action can be performed. Response: Specify an appropriate job name. AMQ8185Operating system object already exists. Severity: 40 : Stop Error Explanation: The WebSphere MQ object cannot be created because an object that is not known to MQ already exists in the MQ directory with the name that should be used for the new object. Refer to the log for previous messages. Response: Remove the non-MQ object from the MQ library, and try the command again. AMQ8186Image not available for WebSphere MQ object . Severity: 40 : Stop Error Explanation: The object type cannot be recreated because the image is not fully available in the logs that are currently online. Refer to earlier messages in the error log for information about the logs that need to be brought online for this object to be recreated. Response: Bring the relevant logs online, and try the command again. AMQ8187WebSphere MQ object is currently open. Severity: 40 : Stop Error Explanation: The object , type , is currently in use, so the command cannot be issued against it. If a generic list was presented to the command, the command is still issued against the other objects in the list. Response: Wait until the object is no longer in use, and try the command again. AMQ8188Insufficient authorization to WebSphere MQ object . Severity: 40 : Stop Error Explanation: You are not authorized to issue the command against the object type . If a generic list was presented to the command, the command is still issued against the other objects in the list. Response: Obtain sufficient authorization for the object, and retry the command. AMQ8189WebSphere MQ object is damaged. Severity: 40 : Stop Error Explanation: The object type is damaged and the command cannot be issued against it. If a generic list was presented to the command then the command is still issued against the other objects in the list. Response: Issue the appropriate DEFINE command for the object, specifying REPLACE, and then try the command again. AMQ8190 succeeded on objects and failed on objects. Severity: 40 : Stop Error Explanation: An operation performed on a generic list of objects was not completely successful. Response: Examine the log for details of the errors encountered, and take appropriate action. AMQ8191WebSphere MQ command server is starting. Severity: 40 : Stop Error Explanation: The command server is starting. Response: Wait for the strmqcsv command to complete and then try the operation again. AMQ8191 (iSeries)WebSphere MQ command server is starting. Severity: 40 : Stop Error Explanation: The command server is starting. Response: Wait for the STRMQMCSVR command to complete and then try the operation again. AMQ8192WebSphere MQ command server already starting. Severity: 40 : Stop Error Explanation: The request to start the command server was unsuccessful because the command server is already starting. Response: Wait for the strmqcsv command to complete. AMQ8192 (iSeries)WebSphere MQ command server already starting. Severity: 40 : Stop Error Explanation: The request to start the command server was unsuccessful because the command server is already starting. Response: Wait for the STRMQMCSVR command to complete. AMQ8193WebSphere MQ command server is ending. Severity: 40 : Stop Error Explanation: The command server is ending. Response: Wait for the endmqcsv command to complete and then try the command again. AMQ8193 (iSeries)WebSphere MQ command server is ending. Severity: 40 : Stop Error Explanation: The command server is ending. Response: Wait for the ENDMQMCSVR command to complete and then try the command again. AMQ8194WebSphere MQ command server already ending. Severity: 40 : Stop Error Explanation: The end command server request was unsuccessful because the command server is already ending. Response: Wait for the endmqcsv command to complete. AMQ8194 (iSeries)WebSphere MQ command server already ending. Severity: 40 : Stop Error Explanation: The end command server request was unsuccessful because the command server is already ending. Response: Wait for the ENDMQMCSVR command to complete. AMQ8195WebSphere MQ command server already running. Severity: 40 : Stop Error Explanation: The strmqcsv command was unsuccessful because the command server is already running. Response: None. AMQ8195 (iSeries)WebSphere MQ command server already running. Severity: 40 : Stop Error Explanation: The STRMQMCSVR command was unsuccessful because the command server is already running. Response: None. AMQ8196WebSphere MQ command server already stopped. Severity: 40 : Stop Error Explanation: The request to end the command server was unsuccessful because the command server is already stopped. Response: None. AMQ8197Deleted WebSphere MQ queue damaged. Severity: 20 : Error Explanation: The deleted MQ queue was damaged, and any messages it contained have been lost. Response: None. AMQ8198 (iSeries)Program called with incorrect number of parameters. Severity: 20 : Error Explanation: The number of parameters passed in the call to program is not correct. Response: Correct the calling program and then retry the operation. AMQ8199 (iSeries)Error in call identifier parameter passed to program QMQM. Severity: 20 : Error Explanation: The call identifier, the first parameter passed to program QMQM, is not in the required packed decimal format, or its value is not supported. Permitted values of the call identifier are contained in the RPG copy file CMQR. Response: Correct the calling program, and retry the call. AMQ8200 (iSeries)MODENAME only allowed with TRPTYPE(*LU62). Severity: 40 : Stop Error Explanation: The MODENAME parameter may only be specified with TRPTYPE(*LU62). Response: Remove the MODENAME parameter from the command or change the TRPTYPE parameter value to specify *LU62 and then try the command again. AMQ8201 (iSeries)TPGMNAME only allowed with TRPTYPE(*LU62). Severity: 40 : Stop Error Explanation: The TPGMNAME parameter may only be specified with TRPTYPE(*LU62). Response: Remove the TPGMNAME parameter from the command or change the TRPTYPE parameter value to specify *LU62. Then try the command again. AMQ8202TMQNAME only allowed with channel type *SDR or *SVR. Severity: 40 : Stop Error Explanation: The TMQNAME parameter may only be specified with channel type *SDR or *SVR. Response: Remove the TMQNAME parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *SDR or *SVR. Then try the command again. AMQ8203 (iSeries)CONNAME only allowed with channel type *SDR, *SVR, *RQSTR, *CLUSSDR, *CLTCN and *CLUSRCVR Severity: 40 : Stop Error Explanation: The CONNAME parameter may only be specified with channel type *SDR, *SVR, *RQSTR, *CLUSSDR, *CLTCN or *CLUSRCVR. Response: Remove the CONNAME parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *SDR, *SVR, *RQSTR, *CLUSSDR, *CLTCN or *CLUSRCVR. Then try the command again. AMQ8204MCANAME only allowed with channel type *SDR, *SVR, or *RQSTR. Severity: 40 : Stop Error Explanation: The MCANAME parameter may only be specified with channel type *SDR, *SVR, or *RQSTR. Response: Remove the MCANAME parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *SDR, *SVR, or *RQSTR. Then try the command again. AMQ8205DSCITV only allowed with channel type *CLUSSDR, *CLUSRCVR, *SVRCN, *SDR or *SVR. Severity: 40 : Stop Error Explanation: The DSCITV parameter may only be specified with channel type *CLUSSDR, *CLUSRCVR, *SVRCN, *SDR or *SVR. Response: Remove the DSCITV parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *CLUSSDR, *CLUSRCVR, *SVRCN, *SDR or *SVR. Then try the command again. AMQ8206SHORTRTY only allowed with channel type *CLUSSDR, CLUSRCVR, *SDR or *SVR. Severity: 40 : Stop Error Explanation: The SHORTRTY parameter may only be specified with channel type *CLUSSDR, *CLUSRCVR, *SDR or *SVR. Response: Remove the SHORTRTY parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *CLUSSDR, *CLUSRCVR, *SDR or *SVR. Then try the command again. AMQ8207SHORTTMR only allowed with channel type *CLUSSDR, CLUSRCVR, *SDR or *SVR. Severity: 40 : Stop Error Explanation: The SHORTTMR parameter may only be specified with channel type *CLUSSDR, *CLUSRCVR, *SDR or *SVR. Response: Remove the SHORTTMR parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *CLUSSDR, CLUSRCVR, *SDR or *SVR. Then try the command again. AMQ8208LONGRTY only allowed with channel type *CLUSSDR, *CLUSRCVR, *SDR or *SVR. Severity: 40 : Stop Error Explanation: The LONGRTY parameter may only be specified with channel type *CLUSSDR, *CLUSRCVR, *SDR or *SVR. Response: Remove the LONGRTY parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *CLUSSDR, CLUSRCVR, *SDR or *SVR. Then try the command again. AMQ8209LONGTMR only allowed with channel type *CLUSSDR, *CLUSRCVR, *SDR or *SVR. Severity: 40 : Stop Error Explanation: The LONGTMR parameter may only be specified with channel type *CLUSSDR, *CLUSRCVR, *SDR or *SVR. Response: Remove the LONGTMR parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *CLUSSDR, *CLUSRCVR, *SDR or *SVR. Then try the command again. AMQ8210PUTAUT only allowed with channel type *RCVR or RQSTR. Severity: 40 : Stop Error Explanation: The PUTAUT parameter may only be specified with channel type *RCVR or RQSTR. Response: Remove the PUTAUT parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *RCVR or RQSTR. Then try the command again. AMQ8211BATCHINT only allowed with channel type *SDR or *SVR. Severity: 40 : Stop Error Explanation: The BATCHINT parameter may only be specified with channel type *SDR or *SVR. Response: Remove the BATCHINT parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *SDR or *SVR. Then try the command again. AMQ8212 (iSeries)TPGMNAME parameter required with TRPTYPE(*LU62). Severity: 40 : Stop Error Explanation: A required parameter was not specified. Response: Enter a value for parameter TPGMNAME. AMQ8213 (iSeries)TMQNAME parameter required with channel type *SDR or *SVR. Severity: 40 : Stop Error Explanation: The TMQNAME parameter must be specified with channel type *SDR or *SVR. Response: Enter a value for parameter TMQNAME. AMQ8214CONNAME parameter missing. Severity: 40 : Stop Error Explanation: The CONNAME parameter must be specified with channel types SDR, RQSTR, CLNTCONN, and CLUSSDR. It is also required with channel type CLUSRCVR if the TRPTYPE is not TCP. Response: Enter a value for parameter CONNAME. AMQ8214 (iSeries)CONNAME parameter missing. Severity: 40 : Stop Error Explanation: The CONNAME parameter must be specified with channel types *SDR, *RQSTR, and *CLUSSDR. It is also required with channel type *CLUSRCVR if the TRPTYPE is not *TCP. Response: Enter a value for parameter CONNAME. AMQ8215 (iSeries)CVTMSG only allowed with channel type *SDR, *SVR, *CLUSSDR or *CLUSRCVR. Severity: 40 : Stop Error Explanation: The CVTMSG parameter may only be specified with channel type *SDR, *SVR, *CLUSSDR or *CLUSRCVR. Response: Remove the CVTMSG parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *SDR, *SVR, *CLUSSDR or CLUSRCVR. Then try the command again. AMQ8216 (iSeries)MODENAME only allowed with TRPTYPE(*LU62). Severity: 40 : Stop Error Explanation: The MODENAME parameter may only be specified with TRPTYPE(*LU62). Response: Remove the MODENAME parameter from the command or change the TRPTYPE parameter value to specify *LU62. Then try the command again. AMQ8217 (iSeries)CONNAME only allowed with channel type *SDR, *SVR, *RQSTR, *CLUSSDR or CLUSRCVR. Severity: 40 : Stop Error Explanation: The CONNAME parameter may only be specified with channel type *SDR, *SVR, *RQSTR, CLUSSDR or CLUSRCVR. Response: Remove the CONNAME parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *SDR, *SVR, *RQSTR, CLUSSDR or CLUSRCVR. Then try the command again. AMQ8218The system cannot accept the combination of parameters entered. Severity: 30 : Severe error AMQ8219Command server queue is open, retry later. Severity: 30 : Severe error Response: Wait and try again later. AMQ8220 (iSeries)The PNGMQMCHL command has completed. Severity: 0 : Information Explanation: The PNGMQMCHL command sent bytes of data to and received the data back in . seconds. The number of bytes will be less than the amount requested on the command, when the length requested is greater than the allowed maximum, in one communications transmission, for the operating system and communications protocol. Response: None. AMQ8221 (iSeries)Ping data length truncated, specified length , actual length . Severity: 10 : Warning Explanation: The length of the ping data sent was reduced because of constraints in the current configuration. Response: None. AMQ8222 (iSeries)The data sent and received by the PNGMQMCHL command was not identical. Severity: 40 : Stop Error Explanation: Ping data compare failed at offset , data sent , data received . Response: This is probably due to a communications failure. Other messages may have been issued. AMQ8223 (iSeries)No channels to display. Severity: 0 : Information Explanation: There are no channels defined on this system. Response: Create a channel using the CRTMQMCHL command. AMQ8224 (iSeries)From channel not found. Severity: 30 : Severe error Explanation: The source WebSphere MQ channel does not exist. Response: Correct the MQ channel name and then try the command again. AMQ8225 (iSeries)From channel and to channel names are equal. Severity: 30 : Severe error Explanation: The same name has been specified for the from channel name and the to channel name. Response: Choose two different names, of which the from channel must exist. AMQ8226WebSphere MQ channel already exists. Severity: 40 : Stop Error Explanation: The channel cannot be created because it already exists. Response: Check that the name is correct and try the command again specifying REPLACE, or delete the channel and then try the command again. AMQ8227Channel not found. Severity: 30 : Severe error Explanation: The channel could not be found. Response: Correct the Channel Name if wrong and then try the command again. For DEFINE CHANNEL check that the Channel Name in error exists. AMQ8228 (iSeries)Unexpected return code . Severity: 30 : Severe error Explanation: The unexpected return code was returned to a channel command. Response: This message is associated with an internal error. Use WRKPRB to record the problem identifier, and to save the QPSRVDMP, QPJOBLOG, and QPDSPJOB files. Contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ8229 (iSeries)No message queue managers to display. Severity: 0 : Information Explanation: There are no message queue managers to administer. Response: Add a queue manager using PF6 or the ADMQMNAM command. AMQ8230 (iSeries)No queue manager objects to display. Severity: 0 : Information Explanation: Either the queue manager has no objects to display (this is unlikely), or the selection criteria resulted in zero objects to display. Response: Change or remove the selection criteria. AMQ8231 (iSeries)No responses to display. Severity: 0 : Information Explanation: There are no commands or command responses to display. Response: None. AMQ8232 (iSeries)No messages to display. Severity: 0 : Information Explanation: The queue is empty, or the queue does not exist. Response: None. AMQ8233 (iSeries)No message data to display. Severity: 0 : Information Explanation: The message contains no data. Response: None. AMQ8234 (iSeries)No response data to display. Severity: 0 : Information Explanation: There is no response data to display for this command. This is probably because the command has not yet completed. Response: None. AMQ8235 (iSeries)No command parameters to display. Severity: 0 : Information Explanation: Some commands have no required parameters. Response: None. AMQ8236 (iSeries)Channel not found. Severity: 30 : Severe error Explanation: CHGMQMCHL was issued for a non-existent channel. Response: Correct the WebSphere MQ channel name and then try the command again. AMQ8237 (iSeries)NPMSPEED only allowed with channel type *SDR, *SVR, *RCVR *RQSTR, CLUSSDR or CLUSRCVR. Severity: 40 : Stop Error Explanation: The NPMSPEED parameter may only be specified with channel type *SDR, *SVR, *RCVR *RQSTR, CLUSSDR or CLUSRCVR. Response: Remove the NPMSPEED parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *SDR, *SVR, *RCVR *RQSTR, CLUSSDR or CLUSRCVR. Then try the command again. AMQ8238 (iSeries)Queue manager connection already open. Severity: 30 : Severe error Explanation: An MQCONN call was issued, but the thread or process is already connected to a different queue manager. The thread or process can connect to only one queue manager at a time. Response: Use the MQDISC call to disconnect from the queue manager which is already connected, and then issue the MQCONN call to connect to the new queue manager. Disconnecting from the existing queue manager will close any queues which are currently open, it is recommended that any uncommitted units of work should be committed or backed out before the MQDISC call is used. AMQ8239 (iSeries)LOCLADDR not valid for channel type *RCVR or *SVRCN. Severity: 40 : Stop Error Explanation: The LOCLADDR parameter may only be specified with channel type *SDR, *SVR, *RQSTR, *CLUSSDR, *CLUSRCVR or *CLTCN. Response: Remove the CONNAME parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *SDR, *SVR, *RQSTR, *CLUSSDR, *CLUSRCVR or *CLTCN. Then try the command again. AMQ8240 (iSeries)Unexpected error in . Severity: 40 : Stop Error Explanation: The unexpected return code was returned during processing. Response: This message is associated with an internal error. Use WRKPRB to record the problem identifier, and to save the QPSRVDMP, QPJOBLOG, and QPDSPJOB files. Contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ8241 (iSeries)Unexpected message format received. Severity: 40 : Stop Error Explanation: The unexpected message format was received in message on the internal reply queue. Response: This message is probably a message sent erroneously to this queue. The message in error is written to the SYSTEM.ADMIN.EXCEPTION.QUEUE, where it may be viewed using the WRKMQMMSG command. AMQ8242SSLCIPH definition wrong. Severity: 40 : Stop Error Explanation: The definition of the SSLCIPH parameter was wrong. Response: Correct the SSLCIPH definition and try the command again. AMQ8243SSLPEER definition wrong. Severity: 40 : Stop Error Explanation: The definition of the SSLPEER parameter was wrong. Possible causes may be that the syntax was invalid or that it contained an invalid attribute type. Response: Correct the SSLPEER definition and try the command again. AMQ8266 (iSeries)No objects to display. Severity: 0 : Information Explanation: There are no objects with the specified name and type. Response: None. AMQ8276Display Connection details. Severity: 0 : Information Explanation: The DISPLAY CONN command completed successfully. Details follow this message. AMQ8277 (iSeries)Object changed. Severity: 40 : Stop Error Explanation: The definition of WebSphere MQ object changed after it had been opened, thereby invalidating the open operation. Response: Try the command again. AMQ8278 (iSeries)Maximum handle limit reached. Severity: 40 : Stop Error Explanation: An attempt was made to exceed the maximum handle limit specified for the message queue manager. Response: Increase the maximum handle limit specified for the message queue manager using the CHGMQM command. Then try the command again. AMQ8279 (iSeries)Option not valid for type. Severity: 40 : Stop Error Explanation: The options specified when opening WebSphere MQ object were not valid for the object type. Response: Correct the definition of the failing object. Then try the command again. AMQ8280 (iSeries)Queue does not exist. Severity: 30 : Severe error Explanation: The queue being displayed does not exist on this queue manager. Response: Check the name of the queue and retry the operation. If you are attempting to display a queue of type *ALS, check the queue definition references an existing queue definition. AMQ8282 (iSeries)Queue manager is not defined on the connected queue manager. Severity: 30 : Severe error Explanation: Either the necessary queue manager name has been entered incorrectly on the add queue manager panel, or the queue manager has not been defined on the connected queue manager. Response: Correct the name, or define on the connected queue manager by creating a local queue with name and usage *TMQ (transmission queue), and then creating sender and receiver channels on both the connected queue manager and queue manager . AMQ8283 (iSeries)The administration application data store program failed to start. Severity: 40 : Stop Error Explanation: The program AMQMCPRA (data store program) was not started because of reason code . Response: Check the joblog for AMQMCPRA by issuing a WRKSPLF QMQM. Correct the problem and try to start the Administration application by invoking the STRMQMADM command. If the problem persists contact your systems programmer. AMQ8284 (iSeries)This user is not authorized to queue . Severity: 40 : Stop Error Explanation: Queue (queue manager ) has not been authorized for your use. Response: Have queue authorized for your use. If queue manager is not the local queue manager, you might not be authorized to the transmission queue for this queue manager. AMQ8287No channels with status to display. Severity: 0 : Information Explanation: There are no channels having status information to display. This indicates either, that the channel has not been started previously, or, that the channel has been started but has not yet completed a transmission sequence. Response: None. AMQ8288 (iSeries)Not authorized to command Severity: 40 : Stop Error Explanation: You are not authorized to perform the requested operation for WebSphere MQ command . Response: Obtain the necessary authority from your WebSphere MQ administrator. Then try the command again. AMQ8289 (iSeries)You are not authorized to the WebSphere MQ command. Severity: 40 : Stop Error Explanation: You are not authorized to the WebSphere MQ command because your user profile is not a member of the QMQMADM group. Response: Ask your MQ administrator to give your user profile *ALLOBJ authority, or add your user profile to the QMQMADM group (either as a primary or supplemental group) AMQ8291 (iSeries)WebSphere MQ remote trace already running. Severity: 10 : Warning Explanation: An attempt was made to start remote trace, but it is already running. Response: Either leave remote trace running as it is, or, if you want to change the settings, turn remote trace off and then turn it on again with appropriate settings. AMQ8294 (iSeries)WebSphere MQ remote trace already off. Severity: 10 : Warning Explanation: An attempt was made to end remote trace, but it is already off. Response: Leave remote trace off. AMQ8295 (iSeries)WebSphere MQ object not secured by authorization list. Severity: 40 : Stop Error Explanation: The specified object is not secured by the authorization list to be revoked from it. Response: Use the display authority (DSPMQMAUT) command to determine what authorization list is securing the object, if any. Issue the RVKMQMAUT command again with the authorization list that is securing the the object to revoke the authorization list's authority. AMQ8296 MQSC commands completed successfully. Severity: 0 : Information Explanation: The command has completed successfully. The MQ commands from have been processed without error and a report written to the printer spool file. Response: None. AMQ8297 MQSC commands verified successfully. Severity: 0 : Information Explanation: The command completed successfully. The MQ commands from have been verified and a report written to the printer spool file. Response: None. AMQ8298Error report generated for MQSC command process. Severity: 40 : Stop Error Explanation: The command attempted to process a sequence of MQ commands and encountered some errors, however, the operation may have partially completed. Response: If the STRMQMMQSC command was executed a report has been written to a printer spool file. Examine the spooled printer file for details of the errors encountered and correct the MQSC source and retry the operation. AMQ8299Cannot open for MQSC process. Severity: 40 : Stop Error Explanation: The command failed to open for MQ command processing. Response: Check that the intended file exists, and has been specified correctly. Correct the specification or create the object, and try the operation again. AMQ8300 (iSeries)Too many exit programs/user data fields defined. Severity: 30 : Severe error Explanation: An attempt was made to create or change a channel which had more than the allowed maximum of a total of six exit programs and/or user data fields defined. Response: Re-define the channel so that a total of six exit programs and/or user data fields are defined. AMQ8301 (iSeries)WebSphere MQ storage monitor job could not be started. Severity: 50 : System Error Explanation: An attempt to start the storage monitor process (job QMQM in subsystem QSYSWRK) was unsuccessful. Response: Check the job log for the reason for the failure, and try the command again. AMQ8302Internal failure initializing WebSphere MQ services. Severity: 50 : System Error Explanation: An error occurred while attempting to initialize WebSphere MQ services. Response: A call to xcsInitialize ended with the FAIL, STOP, or STOP_ALL return code. Refer to the log for messages diagnosing this problem. AMQ8303Insufficient storage available to process request. Severity: 50 : System Error AMQ8304Tracing cannot be started. Too many traces are already running. Severity: 40 : Stop Error Explanation: A maximum of 9 traces may be running concurrently. This number is already running. Response: Stop one or more of the other traces and try the command again. AMQ8305Tracing cannot be started. Too many traces are already running. Severity: 40 : Stop Error Explanation: A maximum of 9 traces can be running concurrently, and this number of traces is already running. Response: Stop one or more of the other traces and try the command again. AMQ8306 (iSeries)BATCHSIZE only allowed with channel type *SDR, *SVR, *RCVR, *RQSTR, CLUSSDR or CLUSRCVR. Severity: 40 : Stop Error Explanation: The BATCHSIZE parameter may only be specified with channel type *SDR, *SVR, *RCVR, *RQSTR, CLUSSDR or CLUSRCVR. Response: Remove the BATCHSIZE parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *SDR, *SVR, *RCVR *RQSTR, CLUSSDR or CLUSRCVR. Then try the command again. AMQ8307 (iSeries)SEQNUMWRAP only allowed with channel type *SDR, *SVR, *RCVR , *RQSTR, CLUSSDR or CLUSRCVR. Severity: 40 : Stop Error Explanation: The SEQNUMWRAP parameter may only be specified with channel type *SDR, *SVR, *RCVR, *RQSTR, CLUSSDR or CLUSRCVR. Response: Remove the SEQNUMWRAP parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *SDR, *SVR, *RCVR *RQSTR, CLUSSDR or CLUSRCVR. Then try the command again. AMQ8308 (iSeries)MSGRTYEXIT only allowed with channel type *CLUSRCVR, *RCVR or *RQSTR. Severity: 40 : Stop Error Explanation: The MSGRTYEXIT parameter may only be specified with channel type *CLUSRCVR, *RCVR or *RQSTR. Response: Remove the MSGRTYEXIT parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *CLUSRCVR, *RCVR or *RQSTR. Then try the command again. AMQ8309 (iSeries)MSGRTYDATA only allowed with channel type *CLUSRCVR, *RCVR or *RQSTR. Severity: 40 : Stop Error Explanation: The MSGRTYDATA parameter may only be specified with channel type *CLUSRCVR, *RCVR or *RQSTR. Response: Remove the MSGRTYDATA parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *CLUSRCVR, *RCVR or *RQSTR. Then try the command again. AMQ8310 (iSeries)MSGRTYNBR only allowed with channel type *CLUSRCVR, *RCVR or *RQSTR. Severity: 40 : Stop Error Explanation: The MSGRTYNBR parameter may only be specified with channel type *CLUSRCVR, *RCVR or *RQSTR. Response: Remove the MSGRTYNBR parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *CLUSRCVR, *RCVR or *RQSTR. Then try the command again. AMQ8311 (iSeries)MSGRTYITV only allowed with channel type *CLUSRCVR, *RCVR or *RQSTR. Severity: 40 : Stop Error Explanation: The MSGRTYITV parameter may only be specified with channel type *CLUSRCVR, *RCVR or *RQSTR. Response: Remove the MSGRTYITV parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *CLUSRCVR, *RCVR or *RQSTR. Then try the command again. AMQ8312 (iSeries)CLUSTER only allowed with queue type *ALS, *LCL and *RMT. Severity: 40 : Stop Error Explanation: The CLUSTER parameter may only be specified with queue type *ALS, *LCL and *RMT. Response: Remove the CLUSTER parameter from the command or, if the command is CRTMQMQ, change the QTYPE parameter value to specify *ALS, *LCL or *RMT. Then try the command again. AMQ8313 (iSeries)CLUSNL only allowed with queue type *ALS, *LCL and *RMT. Severity: 40 : Stop Error Explanation: The CLUSNL parameter may only be specified with queue type *ALS, *LCL and *RMT. Response: Remove the CLUSNL parameter from the command or, if the command is CRTMQMQ, change the QTYPE parameter value to specify *ALS, *LCL or *RMT. Then try the command again. AMQ8314 (iSeries)DEFBIND only allowed with queue type *ALS, *LCL and *RMT. Severity: 40 : Stop Error Explanation: The DEFBIND parameter may only be specified with queue type *ALS, *LCL and *RMT. Response: Remove the DEFBIND parameter from the command or, if the command is CRTMQMQ, change the QTYPE parameter value to specify *ALS, *LCL or *RMT. Then try the command again. AMQ8315No namelists to display. Severity: 0 : Information Explanation: There are no matching namelists defined on this system. Response: Use the Create Namelist (CRTMQMNL) command to create a namelist. AMQ8316No cluster queue managers to display. Severity: 0 : Information Explanation: There are no matching cluster queue managers defined on this system. Response: None. AMQ8317 (iSeries)CLUSTER only allowed with channel type *CLUSSDR and *CLUSRCVR. Severity: 40 : Stop Error Explanation: The CLUSTER parameter may only be specified with channel type *CLUSSDR and *CLUSRCVR. Response: Remove the CLUSTER parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *CLUSSDR or *CLUSRCVR. Then try the command again. AMQ8318 (iSeries)CLUSNL only allowed with channel type *CLUSSDR and *CLUSRCVR. Severity: 40 : Stop Error Explanation: The CLUSNL parameter may only be specified with channel type *CLUSSDR and *CLUSRCVR. Response: Remove the CLUSNL parameter from the command or, if the command is CRTMQMCHL, change the CHLQTYPE parameter value to specify *CLUSSDR or *CLUSRCVR. Then try the command again. AMQ8319MSGEXIT only allowed with channel type *SDR, *SVR, *RCVR *RQSTR, *CLUSSDR or *CLUSRCVR. Severity: 40 : Stop Error Explanation: The MSGEXIT parameter may only be specified with channel type *SDR, *SVR, *RCVR, *RQSTR, *CLUSSDR, or *CLUSRCVR. Response: Remove the MSGEXIT parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *SDR or *SVR or *RCVR or *RQSTR or *CLUSSDR or *CLUSRCVR. Then try the command again. AMQ8320 (iSeries)MSGUSRDATA only allowed with channel type *SDR, *SVR, *RCVR *RQSTR, or *CLUSSDR or *CLUSRCVR. Severity: 40 : Stop Error Explanation: The MSGUSRDATA parameter may only be specified with channel type *SDR, *SVR, *RCVR *RQSTR, *CLUSSDR or *CLUSRCVR. Response: Remove the MSGUSRDATA parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *SDR or *SVR or *RCVR or *RQSTR or *CLUSSDR or *CLUSRCVR. Then try the command again. AMQ8321 (iSeries)Process is still running. Severity: 0 : Information AMQ8322 (iSeries)TIMEOUT only allowed with ENDCCTJOB(*YES). Severity: 40 : Stop Error Explanation: The TIMEOUT parameter may only be specified when connected jobs are being ended with the ENDCCTJOB option set to *YES. Response: Remove the TIMEOUT parameter from the command or, if you want to fully quiesce the queue manager, change the ENDCCTJOB parameter to *YES. Then try the command again. AMQ8323 (iSeries)OPTION(*PREEMPT) must not be used with ENDCCTJOB(*YES). Severity: 40 : Stop Error Explanation: When performing a pre-emptive shutdown of the queue manager the ENDCCTJOB(*YES) parameter is not allowed. Response: Change the ENDCCTJOB(*YES) parameter to ENDCCTJOB(*NO) or, if you want to fully quiesce the queue manager without doing a pre-emptive shutdown, change the OPTION(*PREEMPT) parameter to another value. Then try the command again. AMQ8324 (iSeries)OPTION(*WAIT) not allowed with MQMNAME(*ALL). Severity: 40 : Stop Error Explanation: The OPTION(*WAIT) parameter is not allowed when performing a shutdown of all queue managers. Response: Remove the OPTION(*WAIT) parameter from the command or, specify individual queue manager names to shut down the queue managers one-by-one with the OPTION(*WAIT) parameter. Then try the command again. AMQ8325 (iSeries)MQMNAME(*ALL) is not allowed with ENDCCTJOB(*NO). Severity: 40 : Stop Error Explanation: The MQMNAME(*ALL) parameter is only allowed when performing a full shutdown of the queue managers. Response: Specify individual queue manager names to shut the queue managers down one-by-one or change the ENDCCTJOB parameter to *YES. Then try the command again. AMQ8330Running Severity: 0 : Information AMQ8331Ended normally Severity: 0 : Information AMQ8332Ended immediately Severity: 0 : Information AMQ8333Ended preemptively Severity: 0 : Information AMQ8334Ended unexpectedly Severity: 0 : Information AMQ8335Starting Severity: 0 : Information AMQ8336Quiescing Severity: 0 : Information AMQ8337Ending immediately Severity: 0 : Information AMQ8338Ending preemptively Severity: 0 : Information AMQ8339Being deleted Severity: 0 : Information AMQ8340Not available Severity: 0 : Information AMQ8341SUBPOOL()PID() Severity: 0 : Information AMQ8342No authorities to display. Severity: 0 : Information Explanation: There are no authority records defined on this system, satisfying the input parameters. Response: Use the appropriate input to list all the authorities defined on the system, or enter the command again with different input.. AMQ8343 (iSeries)The requested operation is not valid for user QMQMADM. Severity: 0 : Information Explanation: You are not allowed to completely delete the authorities assigned to user QMQMADM, for a valid WebSphere MQ object, with the authority *REMOVE or *NONE. Response: Remove QMQMADM from the list of users to this command. AMQ8344 (iSeries)The delete option is only valid for a generic profile name. Severity: 0 : Information Explanation: The delete option, which will delete this authority profile by removing all the users from this authority profile, is not valid for an object name or the special value &class. Response: To delete users from an object, work from the WRKMQMAUTD command. AMQ8345 (iSeries)BATCHHB not valid for channel type *RCVR, *RQSTR, *SVRCN or *CLTCN. Severity: 40 : Stop Error Explanation: The BATCHHB parameter may only be specified with channel type *SDR, *SVR, *CLUSSDR, or *CLUSRCVR. Response: Remove the BATCHHB parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *SDR, *SVR, *CLUSSDR or *CLUSRCVR. Then try the command again. AMQ8346 (iSeries)Parameter mismatch between QMNAME and QMID. Severity: 40 : Stop Error Explanation: The Queue Manager Name for Removal (QMNAME) parameter is not *QMID and there is a value for the Queue Manager Identifier for Removal (QMID) parameter. Response: A value for QMID is not allowed unless QMNAME is *QMID. Change the value specified on the QMNAME parameter or the value of the QMID parameter and then try the request again. AMQ8347 (iSeries)USERID not valid for channel type *RCVR, *SVRCN or *CLUSRCVR. Severity: 40 : Stop Error Explanation: The USERID parameter may only be specified with channel type *SDR, *SVR, *RQSTR, *CLUSSDR, or *CLTCN. Response: Remove the USERID parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *SDR, *SVR, *RQSTR, *CLUSSDR, or *CLTCN. Then try the command again. AMQ8348 (iSeries)PASSWORD not valid for channel type *RCVR, *SVRCN or *CLUSRCVR. Severity: 40 : Stop Error Explanation: The PASSWORD parameter may only be specified with channel type *SDR, *SVR, *RQSTR, *CLUSSDR, or *CLTCN. Response: Remove the PASSWORD parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *SDR, *SVR, *RQSTR, *CLUSSDR, or *CLTCN. Then try the command again. AMQ8349 (iSeries)Authority changes to failed. Severity: 40 : Stop Error Explanation: Authority changes to an object were requested but could not be made. Response: Check the authorities that you are granting are relevant to the object type of . AMQ8350Usage: dspmqver [-p Components] [-f Fields] [-b] [-v] Severity: 0 : Information Explanation: This shows the correct usage. Response: None. AMQ8359QMNAME()STATUS(Being deleted) Severity: 0 : Information AMQ8370Usage: runmqdnm -q Queue -a Assembly [-m QueueManager] [-c ClassName] [-u Text] [-s Syncpoint] [-n MaxThreads] [-t Timeout] [-b BackoutThreshold] [-r BackoutQueue] [-p Context] [-d] Severity: 0 : Information Explanation: This shows the correct usage. Response: None. AMQ8371 is not a valid command line option. Severity: 40 : Stop Error Explanation: The option was specified on the command line to the application however this is not one of the valid set of command line options. Response: Check the usage information for the application and then retry. AMQ8372The required command line option is missing. Severity: 40 : Stop Error Explanation: The application expects several mandatory command line options. One of these, , was not specified. Response: Check the usage information for the application and ensure that all required parameters are specified then retry. AMQ8373Invalid value specified for command line option (). Severity: 40 : Stop Error Explanation: The value specified for command line option () is invalid. Response: Check the usage information for the application and ensure that all options specify values in the valid range then retry. AMQ8374 WebSphere MQ queue manager does not exist. Severity: 40 : Stop Error Explanation: The WebSphere MQ queue manager does not exist. Response: Either create the queue manager (crtmqm command) or correct the queue manager name used in the command and then try the command again. AMQ8375WebSphere MQ queue manager not available. Severity: 40 : Stop Error Explanation: The WebSphere MQ queue manager is not available because it has been stopped or is otherwise not contactable. Response: Use the strmqm command to start the message queue manager as necessary or correct any intermittent problems (eg. network connectivity) then try the command again. AMQ8376WebSphere MQ queue not found. Severity: 40 : Stop Error Explanation: The queue could not be found, it may not have been created. Response: Ensure that the name of the queue specified is correct, queue names are case sensitive. If the queue is not created, use the runmqsc command to create it. Then try the command again. AMQ8377Unexpected error was received by the application. Severity: 40 : Stop Error Explanation: The error was returned unexpectedly to the application. Response: Save the generated output files and contact your IBM support center. AMQ8378Unexpected exception received from .NET Framework Severity: 40 : Stop Error Explanation: The application received an exception from the underlying .NET framework, information about the exception follows: Response: Examine the information contained within the exception to determine if it is possible to resolve locally. If it is not possible to resolve the problem locally, save the generated output files and contact your IBM support center. AMQ8379Assembly could not be loaded Severity: 40 : Stop Error Explanation: The WebSphere MQ .NET Monitor attempted to load assembly but received an exception from the underlying .NET framework indicating that it could not be found. Response: Check that the assembly does exist and is accessible to the user running the application then retry. If the assembly should be available, contact your IBM support center. AMQ8380No classes implementing IMQObjectTrigger found in . Severity: 40 : Stop Error Explanation: The WebSphere MQ .NET monitor was unable to identify any classes in referenced assembly which implement the IMQObjectTrigger interface. Response: It is a requirement of the WebSphere MQ .NET monitor that either a single class implementing the IMQObjectTrigger interface exists in the referenced assembly or that a class is identified in that assembly to execute. Either modify the assembly to include a single class implementing IMQObjectTrigger or specify a class name on the command line and retry. AMQ8381Too many classes implementing IMQObjectTrigger () found in . Severity: 40 : Stop Error Explanation: The WebSphere MQ .NET monitor found classes in referenced assembly all of which implement the IMQObjectTrigger interface. Response: It is a requirement of the WebSphere MQ .NET monitor that either a single class implementing the IMQObjectTrigger interface exists in the referenced assembly or that a class is identified in that assembly to execute. Either modify the assembly to include a single class implementing IMQObjectTrigger or specify a class name on the command line and retry. AMQ8382A Message breaking the backout threshold () was moved to Severity: 10 : Warning Explanation: Whilst processing queue a message whose backout count exceeded the specified backout threshold () was successfully moved to Response: The message moved to the backout queue has a backout count greater than the backout threshold specified (or picked up from the input queue BOTHRESH attribute). You should investigate the reason why this message was rolled back onto the input queue and resolve that issue. If backout processing is not required, modify the command line options and or queue definitions to achieve the required behaviour from the .NET monitor. AMQ8383A Message breaking the backout threshold () could not be moved. Severity: 40 : Stop Error Explanation: While processing queue a message whose backout count exceeded the specified backout threshold () was encountered however, it was not possible to move it to either a backout queue or the dead-letter queue. Response: Because it was not possible to move the backed out message to another queue, it has been left on the input queue. As a result, the .NET monitor has ended. It is possible that the backout queue or dead-letter queue are full or disabled for put - in this case, resolve this problem first. If backout processing should have resulted in the message being placed on another queue, check the command line options, input queue definition and queue manager dead-letter queue attribute to ensure that they are correct, then retry. AMQ8390Usage: endmqdnm -q Queue [-m QueueManager] Severity: 0 : Information Explanation: This shows the correct usage. Response: None. AMQ8391 is not a valid command line option. Severity: 40 : Stop Error Explanation: The option was specified on the command line to the application however this is not one of the valid set of command line options. Response: Check the usage information for the application and then retry. AMQ8392The required command line option is missing. Severity: 40 : Stop Error Explanation: The application expects mandatory command line options. One of these, , was not specified. Response: Check the usage information for the application and ensure that all required parameters are specified then retry. AMQ8393Invalid value specified for command line option (). Severity: 40 : Stop Error Explanation: The value specified for command line option () is invalid. Response: Check the usage information for the application and ensure that all options specify values in the valid range then retry. AMQ8394WebSphere MQ queue manager does not exist. Severity: 40 : Stop Error Explanation: The WebSphere MQ queue manager does not exist. Response: Either create the queue manager (crtmqm command) or correct the queue manager name used in the command and then try the command again. AMQ8395WebSphere MQ queue manager not available. Severity: 40 : Stop Error Explanation: The WebSphere MQ queue manager is not available because it has been stopped or is otherwise not contactable. Response: Use the strmqm command to start the message queue manager as necessary or correct any intermittent problems (eg. network connectivity) then try the command again. AMQ8396WebSphere MQ queue not found. Severity: 40 : Stop Error Explanation: The queue could not be found, it may not have been created. Response: Ensure that the name of the queue specified is correct, queue names are case sensitive. If the queue is not created, use the runmqsc command to create it. Then try the command again. AMQ8397Unexpected error was received by the application. Severity: 40 : Stop Error Explanation: The error was returned unexpectedly to the application. Response: Save the generated output files and contact your IBM support center. AMQ8398Unexpected exception received from .NET Framework Severity: 40 : Stop Error Explanation: The application received an exception from the underlying .NET framework, information about the exception follows: Response: Examine the information contained within the exception to determine if it is possible to resolve locally. If it is not possible to resolve the problem locally, save the generated output files and contact your IBM support center. AMQ8401 MQSC commands read. Severity: 0 : Information Explanation: The MQSC script contains commands. Response: None. AMQ8402 commands have a syntax error. Severity: 0 : Information Explanation: The MQSC script contains commands having a syntax error. Response: None. AMQ8403 valid MQSC commands could not be processed. Severity: 0 : Information Explanation: The MQSC script contains commands that failed to process. Response: None. AMQ8404Command failed. Severity: 0 : Information Explanation: An MQSC command has been recognized, but cannot be processed. Response: None. AMQ8405Syntax error detected at or near end of command segment below:- Severity: 0 : Information Explanation: The MQSC script contains commands having a syntax error. Response: None. AMQ8406Unexpected 'end of input' in MQSC. Severity: 0 : Information Explanation: An MQSC command contains a continuation character, but the 'end of input' has been reached without completing the command. Response: None. AMQ8407Display Process details. Severity: 0 : Information Explanation: The MQSC DISPLAY PROCESS command completed successfully, and details follow this message. Response: None. AMQ8408Display Queue Manager details. Severity: 0 : Information Explanation: The MQSC DISPLAY QMGR command completed successfully, and details follow this message. Response: None. AMQ8409Display Queue details. Severity: 0 : Information Explanation: The MQSC DISPLAY QUEUE command completed successfully, and details follow this message. Response: None. AMQ8410Parser Error. Severity: 0 : Information Explanation: The MQSC Parser has an internal error. Response: None. AMQ8411Duplicate Keyword Error. Severity: 0 : Information Explanation: A command in the MQSC script contains duplicate keywords. Response: None. AMQ8412Numeric Range Error. Severity: 0 : Information Explanation: The value assigned to an MQSC command keyword is out of the permitted range. Response: None. AMQ8413String Length Error. Severity: 0 : Information Explanation: A string assigned to an MQSC keyword is either NULL, or longer than the maximum permitted for that keyword. Response: None. AMQ8414Display Channel details. Severity: 0 : Information Explanation: The MQSC DISPLAY CHL command completed successfully, and details follow this message. Response: None. AMQ8415Ping WebSphere MQ Queue Manager command complete. Severity: 0 : Information Explanation: The MQSC PING QMGR command completed successfully. Response: None. AMQ8416MQSC timed out waiting for a response from the command server. Severity: 0 : Information Explanation: MQSC did not receive a response message from the remote command server in the time specified. Response: None. AMQ8417Display Channel Status details. Severity: 0 : Information Explanation: The MQSC DISPLAY CHANNEL STATUS command completed successfully, and details follow this message. Response: None. AMQ8418 command responses received. Severity: 0 : Information Explanation: Running in queued mode, command responses were received from the remote command server. Response: None. AMQ8419The Queue is already in the DCE cell. Severity: 0 : Information Explanation: The Queue is already in the cell, that is, its SCOPE attribute is already CELL. Response: None. AMQ8420Channel Status not found. Severity: 0 : Information Explanation: No status was found for the specified channel(s). Response: None. AMQ8421A required keyword was not specified. Severity: 0 : Information Explanation: A keyword required in this command was not specified. Response: None. AMQ8422MQSC found the following response to a previous command on the reply q :- Severity: 0 : Information Explanation: MQSC found additional command responses on the reply q. They will fill follow this message. Response: None. AMQ8423Cell Directory not available. Severity: 0 : Information Explanation: The DCE cell directory is not available, so the requested operation has failed. Response: None. AMQ8424Error detected in a name keyword. Severity: 0 : Information Explanation: A keyword in an MQSC command contained a name string which was not valid. This may be because it contained characters which are not accepted in MQ names. Typical keywords which can produce this error are QLOCAL (and the other q types), CHANNEL, XMITQ, INITQ, MCANAME etc. Response: None. AMQ8425Attribute value error. Severity: 0 : Information Explanation: A keyword in an MQSC command contained a value that was not valid. Response: None. AMQ8426Valid MQSC commands are: Severity: 0 : Information Explanation: The text shows valid MQSC commands. Response: None. AMQ8427Valid syntax for the MQSC command: Severity: 0 : Information Explanation: The text shown is the valid syntax for the MQSC command. Response: None. AMQ8428TYPE Keyword has already been specified. Severity: 0 : Information Explanation: The TYPE has already been specified after the DISPLAY verb, for example DISPLAY QUEUE(*) type(QLOCAL) type(QALIAS). Response: Delete the second TYPE keyword and run the command again. AMQ8429 (iSeries)Error detected in a exit parameter. Severity: 0 : Information Explanation: A syntax error occurred an the exit parameter. This may be because it contained characters which are not accepted as exit names. Check the parameters in the MSGEXIT, RCVEXIT, SCYEXIT and SENDEXIT definitions. Response: None. AMQ8430Remote queue manager name is unknown. Severity: 0 : Information Explanation: The Remote queue manager name is not known to this queue manager. Check that a transmission queue of the same name as the remote queue manager name exists. Response: Create a transmission queue of the same name as the remote queue manager if one does not exist. AMQ8431Transmission queue does not exist Severity: 0 : Information Explanation: The transmission queue does not exist on this queue manager. Response: None. AMQ8432You are not allowed to set both the REPOS and REPOSNL fields. Severity: 0 : Information Explanation: An attempt to set both the REPOS and REPOSNL fields has been made. Only one of these fields can have a value other than blank. Both of the fields may be blank. Response: None. AMQ8433You are not allowed to set both the CLUSTER and CLUSNL fields. Severity: 0 : Information Explanation: An attempt to set both the CLUSTER and CLUSNL fields has been made. Only one of these fields can have a value other than blank. Both of the fields may be blank. Response: None. AMQ8434The repository is unavailable. Severity: 0 : Information Explanation: The repository is unavailable and the data cannot be accessed. Stop and restart the queue manager. Response: None. AMQ8435All valid MQSC commands were processed. Severity: 0 : Information Explanation: The MQSC script contains no commands that failed to process. Response: None. AMQ8436One valid MQSC command could not be processed. Severity: 0 : Information Explanation: The MQSC script contains one command that failed to process. Response: None. AMQ8437No MQSC commands read. Severity: 0 : Information Explanation: The MQSC script contains no commands. Response: None. AMQ8438One MQSC command read. Severity: 0 : Information Explanation: The MQSC script contains one command. Response: None. AMQ8439No commands have a syntax error. Severity: 0 : Information Explanation: The MQSC script contains no commands having a syntax error. Response: None. AMQ8440One command has a syntax error. Severity: 0 : Information Explanation: The MQSC script contains one command which has a syntax error. Response: None. AMQ8441Display Cluster Queue Manager details. Severity: 0 : Information Explanation: The MQSC DISPLAY CLUSQMG command completed successfully, and details follow this message. Response: None. AMQ8442USAGE can not be set to XMITQ with either the CLUSTER or CLUSNL fields set. Severity: 0 : Information Explanation: An attempt has been made to set USAGE to XMITQ when the CLUSTER or CLUSNL field has a value. Change the value of USAGE, or set the CLUSTER and CLUSNL fields to blank, and try the command again. Response: None. AMQ8442 (iSeries)USAGE can not be set to *TMQ with either the CLUSTER or CLUSNL fields set. Severity: 0 : Information Explanation: An attempt has been made to set USAGE to *TMQ when the CLUSTER or CLUSNL field has a value. Change the value of USAGE, or set the CLUSTER and CLUSNL fields to blank, and try the command again. Response: None. AMQ8443Only the CLUSTER or CLUSNL field may have a value. Severity: 0 : Information Explanation: An attempt has been made to set both CLUSTER and CLUSNL fields. One and only one of the fields may have a value, the other field must be blank. Change the value of one of the fields to blank and try the command again. Response: None. AMQ8444The CLUSTER or CLUSNL fields must have a value. Severity: 0 : Information Explanation: Both the CLUSTER and CLUSNL fields are blank. One and only one of the fields may be blank, the other field must be a value. Change one of the fields from blank to a value and try the command again. Response: None. AMQ8445Program cannot open queue manager object. Severity: 30 : Severe error Explanation: An attempt to open a queue manager object has failed. Response: See the previously listed messages in the job log. AMQ8446Channel is currently active. Severity: 30 : Severe error Explanation: The requested operation failed because the channel is currently active. Response: See the previously listed messages in the job log. AMQ8447Requested operation on channel not valid for this channel type. Severity: 30 : Severe error Explanation: The operation requested cannot be performed because channel is not of a suitable type. For example, only sender, server and cluster-sender channels can be resolved. Response: Check that the correct operation was requested. If it was, check that the correct channel name was specified. AMQ8448Channel is not running. Severity: 30 : Severe error Explanation: A request to end channel has failed because the channel is not running. Response: Check that the correct operation was requested. If it was, check that the correct channel name was specified. AMQ8449Queue inhibited for MQGET. Severity: 30 : Severe error Explanation: An MQGET failed because the queue had been previously inhibited for MQGET. Response: None. AMQ8450Display queue status details. Severity: 0 : Information Explanation: The MQSC DISPLAY QSTATUS command completed successfully. Details follow this message. AMQ8451 (iSeries)STATUS(*STOPPED) not allowed with CONNAME specified. Severity: 0 : Information Explanation: The STATUS(*STOPPED) parameter is not allowed when specifying CONNAME on the ENDMQMCHL command. Response: Remove the CONNAME parameter from the command or, specify STATUS(*INACTIVE) to end the channel instance for the specified connection name. AMQ8452 (iSeries)STATUS(*STOPPED) not allowed with RQMNAME specified. Severity: 0 : Information Explanation: The STATUS(*STOPPED) parameter is not allowed when specifying RQMNAME on the ENDMQMCHL command. Response: Remove the RQMNAME parameter from the command or, specify STATUS(*INACTIVE) to end the channel instance for the specified remote queue manager. AMQ8453The path is invalid Severity: 20 : Error Explanation: You typed a path which was not syntactically correct for the operating system you are running WebSphere MQ on. Response: Determine the correct syntax of a path name for the operating system you are running WebSphere MQ on and use this information to type in a valid path. AMQ8454Syntax error found in parameter . Severity: 20 : Error Explanation: The data you entered for does not conform to the syntax rules laid down by WebSphere MQ for this parameter. Response: Carefully check the data entered for this parameter in conjunction with the WebSphere MQ Command Reference to determine the cause of error. AMQ8455Password length error Severity: 20 : Error Explanation: The password string length is rounded up by WebSphere MQ to the nearest eight bytes. This rounding causes the total length of the SSLCRYP string to exceed its maximum. Response: Decrease the size of the password, or of earlier fields in the SSLCRYP string. AMQ8456Conflicting parameters in command. Severity: 20 : Error Explanation: The command contains parameters that cannot be used together. Response: Refer to the WebSphere MQ Script (MQSC) Command Reference to determine an allowable combination of parameters for this command. AMQ8457WebSphere MQ connection stopped. Severity: 0 : Information Explanation: The STOP CONN command successfully stopped the connection that was specified. Response: None. AMQ8458WebSphere MQ connection not stopped. Severity: 0 : Information Explanation: The STOP CONN command could not stop the connection that was specified. Response: None. AMQ8459Not Found. Severity: 0 : Information Explanation: You specified an identifier that was not found. Please try the command again and supply a valid identifier. Response: None. AMQ8460Syntax error in connection identifier. Severity: 0 : Information Explanation: You specified an invalid connection identifier. A valid connection identifier contains 16 hex characters, where all of the characters in the connection identifier should lie within the range 0-9, a-z or A-Z. Response: Correct the connection identifier so that it conforms to the above specification. AMQ8461Connection identifier not found. Severity: 0 : Information Explanation: You specified a connection identifier which is not associated with this queue manager. Response: Correct the connection identifier so that it describes a connection identifier which is associated with this queue manager. Use the command DISPLAY CONN to identify potential connection identifiers to use with this command. AMQ8498Starting MQSC for queue manager . Severity: 0 : Information Explanation: The MQSC script contains commands. Response: None. AMQ8499Usage: runmqsc [-e] [-v] [-w WaitTime [-x]] QMgrName Severity: 0 : Information Explanation: None. Response: None. AMQ8500WebSphere MQ Display MQ Files Severity: 0 : Information AMQ8501Common services initialization failed with return code . Severity: 20 : Error Explanation: A request by the command server to initialize common services failed with return code . Response: None. AMQ8502Connect shared memory failed with return code . Severity: 20 : Error Explanation: A request by the command server to connect shared memory failed with return code . Response: None. AMQ8503Post event semaphore failed with return code . Severity: 20 : Error Explanation: A request by the command server to post an event semaphore failed with return code . Response: None. AMQ8504Command server MQINQ failed with reason code . Severity: 20 : Error Explanation: An MQINQ request by the command server, for the WebSphere MQ queue , failed with reason code . Response: None. AMQ8505Reallocate memory failed with return code . Severity: 20 : Error Explanation: A request by the command server to reallocate memory failed with return code . Response: None. AMQ8506Command server MQGET failed with reason code . Severity: 20 : Error Explanation: An MQGET request by the command server, for the WebSphere MQ queue , failed with reason code . Response: None. AMQ8507Command server MQPUT1 request for an undelivered message failed with reason code . Severity: 20 : Error Explanation: An attempt by the command server to put a message to the dead-letter queue, using MQPUT1, failed with reason code . The MQDLH reason code was . Response: None. AMQ8508Queue Manager Delete Object List failed with return code . Severity: 20 : Error Explanation: A request by the command server to delete a queue manager object list failed with return code . Response: None. AMQ8509Command server MQCLOSE reply-to queue failed with reason code . Severity: 20 : Error Explanation: An MQCLOSE request by the command server for the reply-to queue failed with reason code . Response: None. AMQ8510Command server queue is open, try again later. Severity: 30 : Severe error AMQ8511Usage: strmqcsv [QMgrName] Severity: 0 : Information AMQ8512Usage: endmqcsv [-c | -i] QMgrName Severity: 0 : Information AMQ8513Usage: dspmqcsv [QMgrName] Severity: 0 : Information AMQ8514No response received after seconds. Severity: 20 : Error Explanation: The command server has not reported the status of running, to the start request, before the timeout of seconds was reached. Response: None. AMQ8549Total string length exceeds the maximum value of 999 characters. Severity: 0 : Information Explanation: The total length of a channel exit string is 999 characters. The string list assigned to an MQSC keyword is longer than the maximum value of 999 characters permitted for that keyword. Response: None. AMQ8550Display namelist details. Severity: 0 : Information Explanation: The MQSC DISPLAY NAMELIST command completed successfully, and details follow this message. Response: None. AMQ8551WebSphere MQ namelist changed. Severity: 0 : Information Explanation: WebSphere MQ namelist changed. Response: None. AMQ8552WebSphere MQ namelist created. Severity: 0 : Information Explanation: WebSphere MQ namelist created. Response: None. AMQ8553WebSphere MQ namelist deleted. Severity: 0 : Information Explanation: WebSphere MQ namelist deleted. Response: None. AMQ8554String List String Count Error. Severity: 0 : Information Explanation: The number of strings within the stringlist is greater than the maximum number allowed for the keyword. Reduce the number of strings within the list and try the command again. Response: None. AMQ8555String List String Length Error. Severity: 0 : Information Explanation: A string in a string list assigned to a keyword is longer than the maximum permitted for that keyword. Response: None. AMQ8556RESUME QUEUE MANAGER accepted. Severity: 0 : Information Explanation: The RESUME QUEUE MANAGER command has been accepted for processing. The command will be sent to the repository which will process the command and notify all other repositories that this queue manager is now back in the cluster. Response: None. AMQ8557SUSPEND QUEUE MANAGER accepted. Severity: 0 : Information Explanation: The SUSPEND QUEUE MANAGER command has been accepted for processing. The command will be sent to the repository which will process the command and notify all other repositories that this queue manager is leaving the cluster. Response: None. AMQ8558REFRESH CLUSTER accepted. Severity: 0 : Information Explanation: The REFRESH CLUSTER command has been accepted for processing. The command will be sent to the Repository which will process the command and notify all other repositories that the Cluster needs refreshing. Response: None. AMQ8559RESET CLUSTER accepted. Severity: 0 : Information Explanation: The RESET CLUSTER command has been accepted for processing. The command will be sent to the Repository which will process the command and notify all other repositories that the Cluster needs resetting. Response: None. AMQ8560WebSphere MQ security cache refreshed. Severity: 0 : Information Explanation: The Object Authority Manager security cache has been refreshed. Response: None. AMQ8561 (Windows)Domain controller unavailable. Severity: 10 : Warning Explanation: WebSphere MQ was unable to contact the domain controller to obtain information for user . Response: Ensure that a domain controller for the domain on which user is defined is available. Alternatively, if you are using a computer which is not currently connected to the network and have logged on using a domain user ID, you may wish to log on using a local user ID instead. AMQ8563WebSphere MQ authentication information object created. Severity: 0 : Information Explanation: WebSphere MQ authentication information object created. Response: None. AMQ8564WebSphere MQ authentication information object deleted. Severity: 0 : Information Explanation: WebSphere MQ authentication information object deleted. Response: None. AMQ8565Queue Status not found. Severity: 0 : Information Explanation: Queue Status for the specified queue could not be found. Response: None. AMQ8566Display authentication information details. Severity: 0 : Information Explanation: The MQSC DISPLAY AUTHINFO command completed successfully. Details follow this message. Response: None. AMQ8567WebSphere MQ authentication information changed. Severity: 0 : Information Explanation: WebSphere MQ authentication information changed. Response: None. AMQ8568 (iSeries)No authinfo objects to display. Severity: 0 : Information Explanation: There are no matching authinfo objects defined on this system. Response: Using the DEFINE AUTHINFO command to create an authinfo object. AMQ8569Error in filter specification Severity: 0 : Information Explanation: You specified an invalid filter. Check the WHERE statement and make sure that the operator is valid for the type of parameter, that the parameter can be filtered on, and that the value that you specified for the filter is valid for the type of attribute you are filtering on. Response: None. AMQ8570Attribute value error in . Severity: 0 : Information Explanation: The keyword contained a value that was not valid for this configuration. Please check the MQSC Command Reference to determine valid values for . Response: None. AMQ8601WebSphere MQ trigger monitor started. Severity: 0 : Information Explanation: The WebSphere MQ trigger monitor has been started. Response: None. AMQ8601 (iSeries)WebSphere MQ trigger monitor started. Severity: 0 : Information Explanation: The trigger monitor has been started with initiation queue . Response: None. AMQ8602WebSphere MQ trigger monitor ended. Severity: 0 : Information Explanation: The WebSphere MQ trigger monitor has ended. Response: None. AMQ8603Usage: runmqtrm [-m QMgrName] [-q InitQ] Severity: 0 : Information Explanation: None. Response: None. AMQ8604Use of WebSphere MQ trigger monitor not authorized. Severity: 0 : Information Explanation: The trigger monitor cannot be run due to lack of authority to the requested queue manager or initiation queue. Response: Obtain the necessary authority from your security officer or WebSphere MQ administrator. Then try the command again. AMQ8605Queue manager not available to the WebSphere MQ trigger monitor Severity: 0 : Information Explanation: The queue manager specified for the trigger monitor does not exist, or is not active. Response: Check that you named the correct queue manager. Ask your systems administrator to start it, if it is not active. Then try the command again. AMQ8606Insufficient storage available for the WebSphere MQ trigger monitor. Severity: 0 : Information Explanation: There was insufficient storage available for the WebSphere MQ trigger monitor to run. Response: Free some storage and then try the command again. AMQ8607WebSphere MQ trigger monitor connection failed. Severity: 0 : Information Explanation: The trigger monitor's connection to the requested queue manager failed because of MQI reason code from MQCONN. Response: Consult your systems administrator about the state of the queue manager. AMQ8608WebSphere MQ trigger monitor connection broken. Severity: 0 : Information Explanation: The connection to the queue manager failed while the trigger monitor was running. This may be caused by an endmqm command being issued by another user, or by a queue manager error. Response: Consult your systems administrator about the state of the queue manager. AMQ8609Initiation queue missing or wrong type Severity: 0 : Information Explanation: The named initiation queue could not be found; or the queue type is not correct for an initiation queue. Response: Check that the named queue exists, and is a local queue, or that the named queue is an alias for a local queue which exists. AMQ8610Initiation queue in use Severity: 0 : Information Explanation: The WebSphere MQ trigger monitor could not open the initiation queue because the queue is open for exclusive use by another application. Response: Wait until the queue is no longer in use, and try the command again. AMQ8611Initiation queue could not be opened. Severity: 0 : Information Explanation: The WebSphere MQ trigger monitor could not open the initiation queue; reason code was returned from MQOPEN. Response: Consult your systems administrator. AMQ8612Waiting for a trigger message Severity: 0 : Information Explanation: The WebSphere MQ trigger monitor is waiting for a message to arrive on the initiation queue. Response: None. AMQ8613Initiation queue changed or deleted Severity: 0 : Information Explanation: The WebSphere MQ trigger monitor is unable to continue because the initiation queue has been deleted or changed since it was opened. Response: Retry the command. AMQ8614Initiation queue not enabled for input. Severity: 0 : Information Explanation: The WebSphere MQ trigger monitor cannot read from the initiation queue because input is not enabled. Response: Ask your systems administrator to enable the queue for input. AMQ8615WebSphere MQ trigger monitor failed to get message. Severity: 0 : Information Explanation: The WebSphere MQ trigger monitor failed because of MQI reason code from MQGET. Response: Consult your systems administrator. AMQ8616End of application trigger. Severity: 0 : Information Explanation: The action to trigger an application has been completed. Response: None. AMQ8617Not a valid trigger message. Severity: 0 : Information Explanation: The WebSphere MQ trigger monitor received a message that is not recognized as a valid trigger message. It has been written to the undelivered message queue. Response: Consult your systems administrator. AMQ8618Error starting triggered application. Severity: 0 : Information Explanation: An error was detected when trying to start the application identified in a trigger message. Response: Check that the application the trigger monitor was trying to start is available. AMQ8619Application type not supported. Severity: 0 : Information Explanation: A trigger message was received which specifies application type ; the trigger monitor does not support this type. Response: Use an alternative trigger monitor for this initiation queue. AMQ8620Trigger message with warning Severity: 0 : Information Explanation: The trigger monitor received a message with a warning. For example, it may have been truncated or it could not be converted to the trigger monitor's data representation. The reason code for the warning is . Response: None. AMQ8621Usage: runmqtmc [-m QMgrName] [-q InitQ] Severity: 0 : Information Explanation: None. Response: None. AMQ8622Usage: CICS-Transaction-Name [MQTMC2 structure] Severity: 0 : Information Explanation: None. Response: None. AMQ8623WebSphere MQ listener changed. Severity: 0 : Information Explanation: WebSphere MQ listener changed. Response: None. AMQ8624WebSphere MQ service changed. Severity: 0 : Information Explanation: WebSphere MQ service changed. Response: None. AMQ8625WebSphere MQ service created. Severity: 0 : Information Explanation: WebSphere MQ service created. Response: None. AMQ8626WebSphere MQ listener created. Severity: 0 : Information Explanation: WebSphere MQ listener created. Response: None. AMQ8627WebSphere MQ service object deleted. Severity: 0 : Information Explanation: WebSphere MQ service object deleted. Response: None. AMQ8628WebSphere MQ listener object deleted. Severity: 0 : Information Explanation: WebSphere MQ listener object deleted. Response: None. AMQ8629Display service information details. Severity: 0 : Information Explanation: The MQSC DISPLAY SERVICE command completed successfully. Details follow this message. Response: None. AMQ8630Display listener information details. Severity: 0 : Information Explanation: The MQSC DISPLAY LISTENER command completed successfully. Details follow this message. Response: None. AMQ8631Display listener status details. Severity: 0 : Information Explanation: The MQSC DISPLAY LSSTATUS command completed successfully. Details follow this message. AMQ8632Display service status details. Severity: 0 : Information Explanation: The MQSC DISPLAY SVSTATUS command completed successfully. Details follow this message. AMQ8649Reset WebSphere MQ Queue Manager accepted. Severity: 0 : Information Explanation: The MQSC RESET QMGR command completed successfully. Details follow this message. Response: None. AMQ8650Activity information unavailable. Severity: 0 : Information Explanation: The DSPMQRTE command was expecting activity information but it was unavailable. This does not always constitute an error. Reasons why the activity information is unavailable include the following: 1) One of the queue managers on the route did not support trace-route messaging. 2) One of the queue managers on the route did not allow route information to be returned to the reply queue. See the documentation on the ActivityRecording and TraceRouteRecording queue manager attributes for more details. 3) The report could not a find route back to the reply queue. Response: Try and determine whether the activity information should have been available. Running the command with the 'outline' verbosity option (used with the -v flag) may be useful in determining where the message was when the activity information was generated. AMQ8650 (iSeries)Activity information unavailable. Severity: 0 : Information Explanation: The DSPMQMRTE command was expecting activity information but it was unavailable. This does not always constitute an error. Reasons why the activity information is unavailable include the following: 1) One of the queue managers on the route did not support trace-route messaging. 2) One of the queue managers on the route did not allow route information to be returned to the reply queue. See the documentation on the ActivityRecording and TraceRouteRecording queue manager attributes for more details. 3) The report could not a find route back to the reply queue. Response: Try and determine whether the activity information should have been available. Running the command with DSPINF(*ALL) may be useful in determining where the message was when the activity information was generated. AMQ8651DSPMQRTE command has finished with errors. Severity: 0 : Information Explanation: The DSPMQRTE command has finished processing your request but an execution error was detected. Previous messages issued by the command can be used to identify the error. Response: Refer to previous messages issued by the command. AMQ8651 (iSeries)DSPMQMRTE command has finished with errors. Severity: 0 : Information Explanation: The DSPMQMRTE command has finished processing your request but an execution error was detected. Previous messages issued by the command can be used to identify the error. Response: Refer to previous messages issued by the command. AMQ8652DSPMQRTE command has finished. Severity: 0 : Information Explanation: The DSPMQRTE command has finished processing your request and no execution errors were detected. Response: None. AMQ8652 (iSeries)DSPMQMRTE command has finished. Severity: 0 : Information Explanation: The DSPMQMRTE command has finished processing your request and no execution errors were detected. Response: None. AMQ8653DSPMQRTE command started with options . Severity: 0 : Information Explanation: You have started the DSPMQRTE command with command line options and the command is now processing your request. Response: Wait for the command to finish processing your request. Any further messages that are issued can be used to determine the outcome of the request. AMQ8653 (iSeries)DSPMQMRTE command started. Severity: 0 : Information Explanation: You have started the DSPMQMRTE command and the command is now processing your request. Response: Wait for the command to finish processing your request. Any further messages that are issued can be used to determine the outcome of the request. AMQ8654Trace-route message arrived on queue manager . Severity: 0 : Information Explanation: The DSPMQRTE command has received confirmation of the successful arrival of the trace-route message at its destination queue on queue manager . Response: None. AMQ8654 (iSeries)Trace-route message arrived on queue manager . Severity: 0 : Information Explanation: The DSPMQMRTE command has received confirmation of the successful arrival of the trace-route message at its destination queue on queue manager . Response: None. AMQ8655Trace-route message expired. Severity: 0 : Information Explanation: The DSPMQRTE command has received confirmation that the trace-route message has expired. Response: The expiry interval of trace-route messages generated by the DSPMQRTE command can be altered using the -xs option if this is required. AMQ8655 (iSeries)Trace-route message expired. Severity: 0 : Information Explanation: The DSPMQMRTE command has received confirmation that the trace-route message has expired. Response: The expiry interval of trace-route messages generated by the DSPMQMRTE command can be altered using the EXPIRY parameter if this is required. AMQ8656DSPMQRTE command received an exception report from queue manager with feedback . Severity: 0 : Information Explanation: The DSPMQRTE command trace-route message caused an exception on queue manager . The Feedback field in the report was or . Response: Use the feedback given to determine why the trace-route message caused the exception. AMQ8656 (iSeries)DSPMQMRTE command received an exception report from queue manager with feedback . Severity: 0 : Information Explanation: The DSPMQMRTE command trace-route message caused an exception on queue manager . The Feedback field in the report was or . Response: Use the feedback given to determine why the trace-route message caused the exception. AMQ8657DSPMQRTE command used 0x. Severity: 0 : Information Explanation: You started the DSPMQRTE command specifying that it should generate a trace-route message. This took place and the trace-route message had X. Response: The can be used to retrieve responses to this trace-route request. Run the DSPMQRTE command again specifying this identifier with the -i flag and with the target queue specified as the queue where the responses are expected to return or where the trace-route message is expected to have arrived. This may be on another queue manager. AMQ8657 (iSeries)DSPMQMRTE command used 0x. Severity: 0 : Information Explanation: You started the DSPMQMRTE command specifying that it should generate a trace-route message. This took place and the trace-route message had X. Response: The can be used to retrieve responses to this trace-route request. Run the DSPMQMRTE command again specifying this identifier for CRLLID and with the target queue specified as the queue where the responses are expected to return or where the trace-route message is expected to have arrived. This may be on another queue manager. AMQ8658DSPMQRTE command failed to put a message on the target queue. Severity: 0 : Information Explanation: The request for the DSPMQRTE command to put a trace-route message on the target queue was unsuccessful. Previous messages issued by the command can be used to identify why the message could not be put on the target queue. Response: Refer to previous messages issued by the command. AMQ8658 (iSeries)DSPMQMRTE command failed to put a message on the target queue. Severity: 0 : Information Explanation: The request for the DSPMQMRTE command to put a trace-route message on the target queue was unsuccessful. Previous messages issued by the command can be used to identify why the message could not be put on the target queue. Response: Refer to previous messages issued by the command. AMQ8659DSPMQRTE command successfully put a message on queue , queue manager . Severity: 0 : Information Explanation: The request for the DSPMQRTE command to put a message on the target queue was successful. The target queue resolved to on queue manager . Response: None. AMQ8659 (iSeries)DSPMQMRTE command successfully put a message on queue , queue manager . Severity: 0 : Information Explanation: The request for the DSPMQMRTE command to put a message on the target queue was successful. The target queue resolved to on queue manager . Response: None. AMQ8660DSPMQRTE command could not correctly order the following activities: Severity: 0 : Information Explanation: The DSPMQRTE command received the following activities, but they could not be printed in the correct order. This is commonly because an activity report has been received that does not contain a TraceRoute PCF group or is missing the RecordedActivities parameter which would allow it to be ordered correctly. Response: Find and correct the application that is generating activity reports without the necessary information for them to be ordered correctly. AMQ8660 (iSeries)DSPMQMRTE command could not correctly order the following activities: Severity: 0 : Information Explanation: The DSPMQMRTE command received the following activities, but they could not be printed in the correct order. This is commonly because an activity report has been received that does not contain a TraceRoute PCF group or is missing the RecordedActivities parameter which would allow it to be ordered correctly. Response: Find and correct the application that is generating activity reports without the necessary information for them to be ordered correctly. AMQ8661DSPMQRTE command will not put to queue , queue manager . Severity: 20 : Error Explanation: You started the DSPMQRTE command specifying that the trace-route message should not be delivered to a local queue (-d yes was not specified). However, it has been determined that the target queue does not resolve to a transmission queue. Therefore the DSPMQRTE command has chosen not to put the trace-route message to the target queue on queue manager . Response: Determine whether it was expected that the target queue would resolve to a local queue. AMQ8661 (iSeries)DSPMQMRTE command will not put to queue , queue manager . Severity: 20 : Error Explanation: You started the DSPMQMRTE command specifying that the trace-route message should not be delivered to a local queue (DLVRMSG(*NO) was specified). However, it has been determined that the target queue does not resolve to a transmission queue. Therefore the DSPMQMRTE command has chosen not to put the trace-route message to the target queue on queue manager . Response: Determine whether it was expected that the target queue would resolve to a local queue. AMQ8662Trace-route message delivered on queue manager . Severity: 0 : Information Explanation: The DSPMQRTE command has received confirmation of the successful delivery of the trace-route message on queue manager to a requesting application. Response: None. AMQ8662 (iSeries)Trace-route message delivered on queue manager . Severity: 0 : Information Explanation: The DSPMQMRTE command has received confirmation of the successful delivery of the trace-route message on queue manager to a requesting application. Response: None. AMQ8663Client connection not supported in this environment. Severity: 20 : Error Explanation: An attempt was made to connect to a queue manager using a client connection. However, client connections are not supported in your environment. Response: Connect to the queue manager using a server connection. AMQ8664DSPMQRTE command could not connect to queue manager . Severity: 20 : Error Explanation: You started the DSPMQRTE command specifying that it should connect to queue manager . The command could not connect to that queue manager. Previous messages issued by the command can be used to identify the error. Response: Refer to previous messages issued by the command. AMQ8664 (iSeries)DSPMQMRTE command could not connect to queue manager . Severity: 20 : Error Explanation: You started the DSPMQMRTE command specifying that it should connect to queue manager . The command could not connect to that queue manager. Previous messages issued by the command can be used to identify the error. Response: Refer to previous messages issued by the command. AMQ8665DSPMQRTE command was supplied an invalid CorrelId . Severity: 20 : Error Explanation: You started the DSPMQRTE command specifying option -i with a CorrelId that was invalid. The CorrelId was either too long or not in the correct format. Response: Refer to the command syntax, and then try the command again. AMQ8665 (iSeries)DSPMQMRTE command was supplied an invalid CorrelId . Severity: 20 : Error Explanation: You started the DSPMQMRTE command specifying CRLLID with a CorrelId that was invalid. Response: Refer to the command syntax, and then try the command again. AMQ8666Queue on queue manager . Severity: 0 : Information Explanation: The DSPMQRTE command trace-route message has been confirmed as having taken a route involving queue on queue manager in an attempt to reach the destination queue. Response: Wait for subsequent messages which may indicate another queue which the message has been routed through. AMQ8666 (iSeries)Queue on queue manager . Severity: 0 : Information Explanation: The DSPMQMRTE command trace-route message has been confirmed as having taken a route involving queue on queue manager in an attempt to reach the destination queue. Response: Wait for subsequent messages which may indicate another queue which the message has been routed through. AMQ8667DSPMQRTE command could not open reply queue , queue manager . Severity: 20 : Error Explanation: You started the DSPMQRTE command specifying reply queue . However the DSPMQRTE command could not successfully open a queue of that name on queue manager . Previous messages issued by the command can be used to identify the error. If the -rq option was not specified then the reply queue will be a temporary dynamic queue modelled on SYSTEM.DEFAULT.MODEL.QUEUE. Response: Refer to previous messages issued by the command. Specify a reply queue that can be opened and then retry the command. AMQ8667 (iSeries)DSPMQMRTE command could not open reply queue , queue manager . Severity: 20 : Error Explanation: You started the DSPMQMRTE command specifying reply queue . However the DSPMQMRTE command could not successfully open a queue of that name on queue manager . Previous messages issued by the command can be used to identify the error. If the RPLYQ parameter was not specified then the reply queue will be a temporary dynamic queue modelled on SYSTEM.DEFAULT.MODEL.QUEUE. Response: Refer to previous messages issued by the command. Specify a reply queue that can be opened and then retry the command. AMQ8668DSPMQRTE command could not open queue , queue manager . Severity: 20 : Error Explanation: You started the DSPMQRTE command specifying queue , using the -q option. However the DSPMQRTE command could not successfully open a queue of that name on queue manager . Previous messages issued by the command can be used to identify the error. Response: Refer to previous messages issued by the command. Specify a queue, using the -q option, that can be opened and then retry the command. AMQ8668 (iSeries)DSPMQMRTE command could not open queue , queue manager . Severity: 20 : Error Explanation: You started the DSPMQMRTE command specifying queue for the QNAME parameter. However the DSPMQMRTE command could not successfully open a queue of that name on queue manager . Previous messages issued by the command can be used to identify the error. Response: Refer to previous messages issued by the command. Specify a queue, using the QNAME parameter, that can be opened and then retry the command. AMQ8669DSPMQRTE command failed to resolve queue manager on queue manager . Severity: 20 : Error Explanation: The DSPMQRTE command attempted to resolve queue manager (supplied by the -qm option) on queue manager but the attempt failed. The queue specified by the -q option could not be opened. Response: Ensure that queue manager can be resolved on queue manager or specify a different queue manager with the -qm option. Retry the command. AMQ8669 (iSeries)DSPMQMRTE command failed to resolve queue manager on queue manager . Severity: 20 : Error Explanation: The DSPMQMRTE command attempted to resolve queue manager (supplied by the TGTMQM parameter) on queue manager but the attempt failed. The queue specified by the QNAME parameter could not be opened. Response: Ensure that queue manager can be resolved on queue manager or specify a different queue manager with the TGTMQM parameter. Retry the command. AMQ8670Loading of server module failed. Severity: 20 : Error Explanation: An attempt to dynamically load the server module failed. Typically this is because only the client modules are installed. Response: Check which modules are installed and retry the command with the -c option specified if applicable. AMQ8671DSPMQRTE command was not supplied a reply queue when one was required. Severity: 20 : Error Explanation: The DSPMQRTE command was expecting a reply queue specified by the -rq option but no reply queue was specified. Specifying a reply queue is mandatory if both the -n (no display) option and a response generating option (-ar or -ro [activity|coa|cod|exception|expiration]) is specified. Response: Specify a reply queue and retry the command. AMQ8672DSPMQRTE command failed to get a message from queue , queue manager . Severity: 20 : Error Explanation: The DSPMQRTE command attempted to get a message from queue , queue manager , but the attempt failed. Previous messages issued by the command can be used to identify the error. Response: Refer to previous messages issued by the command. AMQ8672 (iSeries)DSPMQMRTE command failed to get a message from queue , queue manager . Severity: 20 : Error Explanation: The DSPMQMRTE command attempted to get a message from queue , queue manager , but the attempt failed. Previous messages issued by the command can be used to identify the error. Response: Refer to previous messages issued by the command. AMQ8673DSPMQRTE command was supplied option with an invalid object name . Severity: 20 : Error Explanation: You started the DSPMQRTE command specifying option with an object name that is invalid. In general, the names of WebSphere MQ objects can have up to 48 characters. An object name can contain the following characters: 1) Uppercase alphabetic characters (A through Z). 2) Lowercase alphabetic characters (a through z). 3) Numeric digits (0 through 9). 4) Period (.), forward slash (/), underscore (_), percent (%). See the WebSphere MQ System Administration documentation for further details and restrictions. Response: Specify a valid object name and then try the command again. AMQ8673 (iSeries)DSPMQMRTE command was supplied with an invalid object name . Severity: 20 : Error Explanation: You started the DSPMQMRTE command specifying an object name that is invalid. In general, the names of WebSphere MQ objects can have up to 48 characters. An object name can contain the following characters: 1) Uppercase alphabetic characters (A through Z). 2) Lowercase alphabetic characters (a through z). 3) Numeric digits (0 through 9). 4) Period (.), forward slash (/), underscore (_), percent (%). See the WebSphere MQ System Administration documentation for further details and restrictions. Response: Specify a valid object name and then try the command again. AMQ8674DSPMQRTE command is now waiting for information to display. Severity: 0 : Information Explanation: The DSPMQRTE command has successfully generated and put the trace-route message and is now waiting for responses to be returned to the reply queue to indicate the route that the trace-route message took to its destination. Response: Wait for responses to be returned to the reply queue and for the information about the route to be displayed. AMQ8674 (iSeries)DSPMQMRTE command is now waiting for information to display. Severity: 0 : Information Explanation: The DSPMQMRTE command has successfully generated and put the trace-route message and is now waiting for responses to be returned to the reply queue to indicate the route that the trace-route message took to its destination. Response: Wait for responses to be returned to the reply queue and for the information about the route to be displayed. AMQ8675DSPMQRTE command was supplied an invalid option . Severity: 20 : Error Explanation: You started the DSPMQRTE command specifying an option of that was not recognized. The command will end. Response: Refer to the command syntax and retry the command. AMQ8676DSPMQRTE command was supplied an invalid combination of options. Severity: 20 : Error Explanation: You started the DSPMQRTE command specifying a combination of the options that is not valid. The -i option cannot be specified with one or more of the following options: -ac, -ar, -d, -f, -l, -n, -o, -p, -qm, -ro, -rq, -rqm, -s, -t, -xs, -xp. The -n option cannot be specified with one or more of the following options: -b, -i, -v, -w. The -ar option can only be specified if the -ac option has also been specified. The -rqm option can only be specified if the -rq option has also been specified. Response: Refer to the command documentation and then try the command again. AMQ8677DSPMQRTE command was supplied an option with conflicting values. Severity: 20 : Error Explanation: You started the DSPMQRTE command specifying values for option that conflict. At least two values were specified for the same option but they conflict with each other. The DSPMQRTE command will end. Response: Refer to the command syntax and then try the command again. AMQ8677 (iSeries)DSPMQMRTE command was supplied a parameter with conflicting values. Severity: 20 : Error Explanation: You started the DSPMQMRTE command specifying values that conflict. At least two values were specified for the same parameter but they conflict with each other. The DSPMQMRTE command will end. Response: Refer to the command syntax and then try the command again. AMQ8678DSPMQRTE command was supplied option with an invalid value . Severity: 20 : Error Explanation: You started the DSPMQRTE command specifying an invalid option value. The value for option is either not recognized or of an incorrect format. Response: Refer to the command syntax, and then try the command again. AMQ8678 (iSeries)DSPMQMRTE command was supplied an invalid value . Severity: 20 : Error Explanation: You started the DSPMQMRTE command specifying an invalid parameter value. Value is either not recognized or of an incorrect format. Response: Refer to the command syntax, and then try the command again. AMQ8679Persistent messages not allowed on reply queue , queue manager . Severity: 20 : Error Explanation: It was specified that the DSPMQRTE command should put a persistent trace-route message on the target queue (see the documentation for the -l option). However, persistent messages are not allowed on the reply queue because it is a temporary dynamic queue and persistent responses were expected to return to it. The trace-route message was not put on the target queue. Response: Ensure that the reply queue is not a temporary dynamic queue. Use the -rq option to specify the reply queue. AMQ8679 (iSeries)Persistent messages not allowed on reply queue , queue manager . Severity: 20 : Error Explanation: It was specified that the DSPMQMRTE command should put a persistent trace-route message on the target queue (see the documentation for the MSGPST parameter). However, persistent messages are not allowed on the reply queue because it is a temporary dynamic queue and persistent responses were expected to return to it. The trace-route message was not put on the target queue. Response: Ensure that the reply queue is not a temporary dynamic queue. Use the RPLYQ parameter to specify the reply queue. AMQ8680DSPMQRTE command failed to open queue manager . Severity: 20 : Error Explanation: The DSPMQRTE command tried to open queue manager for inquire but the open failed. Previous messages issued by the command can be used to identify the error. Response: Refer to previous messages issued by the command. AMQ8680 (iSeries)DSPMQMRTE command failed to open queue manager . Severity: 20 : Error Explanation: The DSPMQMRTE command tried to open queue manager for inquire but the open failed. Previous messages issued by the command can be used to identify the error. Response: Refer to previous messages issued by the command. AMQ8681DSPMQRTE command has detected an error, reason . Severity: 20 : Error Explanation: The DSPMQRTE command has detected an error from an MQI call during the execution of your request. The reason for failure is or . Response: See the WebSphere MQ Messages documentation for an explanation of the reason for failure. Follow any correction action and retry the command. AMQ8681 (iSeries)DSPMQMRTE command has detected an error, reason . Severity: 20 : Error Explanation: The DSPMQMRTE command has detected an error from an MQI call during the execution of your request. The reason for failure is or . Response: See the WebSphere MQ Messages documentation for an explanation of the reason for failure. Follow any correction action and retry the command. AMQ8682Trace-route message processed by application on queue manager . Severity: 0 : Information Explanation: The DSPMQRTE command successfully put a trace-route message on the target queue and it was then delivered by queue manager to application which processed the message. Response: Determine if it was expected that this application would process the trace-route message. AMQ8682 (iSeries)Trace-route message processed by application on queue manager . Severity: 0 : Information Explanation: The DSPMQMRTE command successfully put a trace-route message on the target queue and it was then delivered by queue manager to application which processed the message. Response: Determine if it was expected that this application would process the trace-route message. AMQ8683Trace-route message reached the maximum activities limit of . Severity: 0 : Information Explanation: The DSPMQRTE command trace-route message was rejected after the number of activities of which it was a participant reached the maximum activities limit. The limit was set to . The maximum activities limit is set using the -s option. Response: Using the output from the command determine whether it is expected that the trace-route message should have reached the maximum activities limit. AMQ8683 (iSeries)Trace-route message reached the maximum activities limit of . Severity: 0 : Information Explanation: The DSPMQMRTE command trace-route message was rejected after the number of activities of which it was a participant reached the maximum activities limit. The limit was set to . The maximum activities limit is set using the MAXACTS parameter. Response: Using the output from the command determine whether it is expected that the trace-route message should have reached the maximum activities limit. AMQ8684Trace-route message reached trace-route incapable queue manager . Severity: 0 : Information Explanation: The DSPMQRTE command trace-route message was rejected because it was about to be sent to a queue manager which does not support trace-route messaging. This behaviour was requested because the forwarding options specified on the command only allowed the trace-route message to be forwarded to queue managers which support trace-route messaging. Sending a trace-route message to a queue manager which cannot process it in accordance with its specified options could cause undesirable results, including having the trace-route message be put to a local queue on the remote queue manager. If this is acceptable then the '-f all' option can be specified. Response: Retry the command with different forwarding options, if appropriate. AMQ8684 (iSeries)Trace-route message reached trace-route incapable queue manager . Severity: 0 : Information Explanation: The DSPMQMRTE command trace-route message was rejected because it was about to be sent to a queue manager which does not support trace-route messaging. This behaviour was requested because the forwarding options specified on the command only allowed the trace-route message to be forwarded to queue managers which support trace-route messaging. Sending a trace-route message to a queue manager which cannot process it in accordance with its specified options could cause undesirable results, including having the trace-route message be put to a local queue on the remote queue manager. If this is acceptable then FWDMSG(*ALL) can be specified. Response: Retry the command with different forwarding options, if appropriate. AMQ8685Trace-route message rejected due to invalid forwarding options X. Severity: 20 : Error Explanation: The DSPMQRTE command trace-route message was rejected because one or more of the forwarding options was not recognized and it was in the MQROUTE_FORWARD_REJ_UNSUP_MASK bitmask. The forwarding options, when they were last observed, in hexadecimal were X. Response: Change the application that inserted the forwarding options that were not recognized to insert valid and supported forwarding options. AMQ8685 (iSeries)Trace-route message rejected due to invalid forwarding options X. Severity: 20 : Error Explanation: The DSPMQMRTE command trace-route message was rejected because one or more of the forwarding options was not recognized and it was in the MQROUTE_FORWARD_REJ_UNSUP_MASK bitmask. The forwarding options, when they were last observed, in hexadecimal were X. Response: Change the application that inserted the forwarding options that were not recognized to insert valid and supported forwarding options. AMQ8686Trace-route message rejected due to invalid delivery options X. Severity: 20 : Error Explanation: The DSPMQRTE command trace-route message was rejected because one or more of the delivery options was not recognized and it was in the MQROUTE_DELIVER_REJ_UNSUP_MASK bitmask. The delivery options, when they were last observed, in hexadecimal were X. Response: Change the application that inserted the delivery options that were not recognized to insert valid and supported delivery options. AMQ8686 (iSeries)Trace-route message rejected due to invalid delivery options X. Severity: 20 : Error Explanation: The DSPMQMRTE command trace-route message was rejected because one or more of the delivery options was not recognized and it was in the MQROUTE_DELIVER_REJ_UNSUP_MASK bitmask. The delivery options, when they were last observed, in hexadecimal were X. Response: Change the application that inserted the delivery options that were not recognized to insert valid and supported delivery options. AMQ8687Program ending. Severity: 0 : Information Explanation: The program operation was interrupted by a SIGINT signal on UNIX systems or a CTRL+c/CTRL+BREAK signal on Windows systems. The program is now ending. Response: Wait for the program to end. AMQ8688DSPMQRTE command has detected an unexpected error, reason . Severity: 20 : Error Explanation: The DSPMQRTE command has detected an unexpected error during execution of your request. The reason for failure is or . The WebSphere MQ error recording routine has been called. Response: Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ8688 (iSeries)DSPMQMRTE command has detected an unexpected error, reason . Severity: 20 : Error Explanation: The DSPMQMRTE command has detected an unexpected error during execution of your request. The reason for failure is or . The WebSphere MQ error recording routine has been called. Response: Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ8689Loading of client module failed. Severity: 20 : Error Explanation: An attempt to dynamically load the client module failed. Typically this is because the client modules are not installed. Response: Check which modules are installed and retry the command without the -c option specified, if applicable. AMQ8701Usage: rcdmqimg [-z] [-l] [-m QMgrName] -t ObjType [GenericObjName] Severity: 0 : Information Explanation: None. Response: None. AMQ8702Usage: rcrmqobj [-z] [-m QMgrName] -t ObjType [GenericObjName] Severity: 0 : Information Explanation: None. Response: None. AMQ8703Usage: dspmqfls [-m QMgrName] [-t ObjType] GenericObjName Severity: 0 : Information Explanation: None. Response: None. AMQ8705Display Queue Manager Status Details. Severity: 0 : Information Explanation: The MQSC DISPLAY QMSTATUS command completed successfully. Details follow this message. Response: None. AMQ8706Request to stop WebSphere MQ Listener accepted. Severity: 0 : Information Explanation: The channel listener program has been requested to stop. This command executes asynchronously so may complete after this message has been displayed. Response: Further information on the progress of the request is available in the queue manager error log. AMQ8707 (iSeries)Start WebSphere MQ DLQ Handler Severity: 0 : Information AMQ8708Dead-letter queue handler started to process INPUTQ(). Severity: 0 : Information Explanation: The dead-letter queue handler (runmqdlq) has been started and has parsed the input file without detecting any errors and is about to start processing the queue identified in the message. Response: None. AMQ8708 (iSeries)Dead-letter queue handler started to process INPUTQ(). Severity: 0 : Information Explanation: The dead-letter queue handler (STRMQMDLQ) has been started and has parsed the input file without detecting any errors and is about to start processing the queue identified in the message. Response: None. AMQ8709Dead-letter queue handler ending. Severity: 0 : Information Explanation: The dead-letter queue handler (runmqdlq) is ending because the WAIT interval has expired and there are no messages on the dead-letter queue, or because the queue manager is shutting down, or because the dead-letter queue handler has detected an error. If the dead-letter queue handler has detected an error, an earlier message will have identified the error. Response: None. AMQ8709 (iSeries)Dead-letter queue handler ending. Severity: 0 : Information Explanation: The dead-letter queue handler (STRMQMDLQ) is ending because the WAIT interval has expired and there are no messages on the dead-letter queue, or because the queue manager is shutting down, or because the dead-letter queue handler has detected an error. If the dead-letter queue handler has detected an error, an earlier message will have identified the error. Response: None. AMQ8710Usage: runmqdlq [QName[QMgrName]]. Severity: 0 : Information Explanation: Syntax for the usage of runmqdlq. Response: None. AMQ8711 (iSeries)Job has terminated unexpectedly. Severity: 10 : Warning Explanation: Execution of the command caused job to be started, but the job terminated unexpectedly. Response: Consult the log for job to determine why it was terminated. AMQ8721Dead-letter queue message not prefixed by a valid MQDLH. Severity: 10 : Warning Explanation: The dead-letter queue handler (runmqdlq) retrieved a message from the nominated dead-letter queue, but the message was not prefixed by a recognizable MQDLH. This typically occurs because an application is writing directly to the dead-letter queue but is not prefixing messages with a valid MQDLH. The message is left on the dead-letter queue and the dead-letter queue handler continues to process the dead-letter queue. Each time the dead-letter queue handler repositions itself to a position before this message to process messages that could not be processed on a previous scan it will reprocess the failing message and will consequently re-issue this message. Response: Remove the invalid message from the dead-letter queue. Do not write messages to the dead-letter queue unless they have been prefixed by a valid MQDLH. If you require a dead-letter queue handler that can process messages not prefixed by a valid MQDLH, you must change the sample program called amqsdlq to cater for your needs. AMQ8721 (iSeries)Dead-letter queue message not prefixed by a valid MQDLH. Severity: 10 : Warning Explanation: The dead-letter queue handler (STRMQMDLQ) retrieved a message from the nominated dead-letter queue, but the message was not prefixed by a recognizable MQDLH. This typically occurs because an application is writing directly to the dead-letter queue but is not prefixing messages with a valid MQDLH. The message is left on the dead-letter queue and the dead-letter queue handler continues to process the dead-letter queue. Each time the dead-letter queue handler repositions itself to a position before this message to process messages that could not be processed on a previous scan it will reprocess the failing message and will consequently re-issue this message. Response: Remove the invalid message from the dead-letter queue. Do not write messages to the dead-letter queue unless they have been prefixed by a valid MQDLH. If you require a dead-letter queue handler that can process messages not prefixed by a valid MQDLH, you must change the sample program called amqsdlq to cater for your needs. AMQ8722Dead-letter queue handler unable to put message: Rule Reason . Severity: 10 : Warning Explanation: This message is produced by the dead-letter queue handler when it is requested to redirect a message to another queue but is unable to do so. If the reason that the redirect fails is the same as the reason the message was put to the dead-letter queue then it is assumed that no new error has occurred and no message is produced. The retry count for the message will be incremented and the dead-letter queue handler will continue. Response: Investigate why the dead-letter queue handler was unable to put the message to the dead-letter queue. The line number of the rule used to determine the action for the message should be used to help identify to which queue the dead-letter queue handler attempted to PUT the message. AMQ8729The listener could not be stopped at this time. Severity: 10 : Warning Explanation: A request was made to stop a listener, however the listener could not be stopped at this time. Reasons why a listener could not be stopped are: The listener has active channels and the communications protocol being used is LU 6.2, SPX or NETBIOS. The listener has active channels and the communications protocol being used is TCP/IP and channel threads are restricted to run within the listener process. Response: End the channels using the STOP CHANNEL command and reissue the request. AMQ8730Listener already active. Severity: 10 : Warning Explanation: A request was made to start a listener, however the listener is already running and cannot be started. Response: If the listener should not be running then use the STOP LISTENER command to stop the listener before reissuing the command. AMQ8731Listener not active. Severity: 10 : Warning Explanation: A request was made to stop a listener, however the listener is not running. Response: If the listener should be running then use the START LISTENER command to start the listener. AMQ8732Request to stop Service accepted. Severity: 0 : Information Explanation: The Request to stop the Service has been accepted and is being processed. Response: None. AMQ8733Request to start Service accepted. Severity: 0 : Information Explanation: The Request to start the Service has been accepted and is being processed. Response: None. AMQ8734Command failed - Program could not be started. Severity: 20 : Error Explanation: The command requested was unsuccessful because the program which was defined to be run to complete the action could not be started. Reasons why the program could not be started are The program does not exist at the specified location. The WebSphere MQ user does not have sufficient access to execute the program. If STDOUT or STDERR are defined for the program, the WebSphere MQ user does not have sufficient access to the locations specified. Response: Check the Queue Manager error logs for further details on the cause of the failure and correct before reissuing the command. AMQ8735Command failed - Access denied. Severity: 20 : Error Explanation: The command requested was unsuccessful because access was denied attempting to execuete the program defined to run. Response: Examine the definition of the object and ensure that the path to program file is correct. If the defined path is correct ensure that the program exists at the location specified and that the WebSphere MQ user has access to execute the program. AMQ8736Command failed - Program start failed. Severity: 20 : Error Explanation: The command requested was unsuccessful because the attempt to execute the program defined to run was unsuccessful. Response: Examine the definition of the object and ensure that the path to program file is correct. If the defined path is correct ensure that the program exists at the location specified and that the WebSphere MQ user has access to execute the program. Further information on the failure may be available in the WebSphere MQ error logs. AMQ8737Service already active. Severity: 10 : Warning Explanation: A request was made to start a service, however the service is already running and cannot be started. Response: If the service should not be running then use the STOP SERVICE command to stop the service before reissuing the command. If the intention is to allow more than one instance of s service to run, then the service definition may be altered to be of SERVTYPE(COMMAND) which allows more than one instance of the service to be executed concurrently, however status of services of type COMMAND is not available from the SVSTAUS command. AMQ8738Service not active. Severity: 10 : Warning Explanation: A request was made to stop a service, however the service is not running. Response: If the service should be running then use the START SERVICE command to start the service. AMQ8739Stop cannot be executed for service with blank STOPCMD. Severity: 20 : Error Explanation: A request was made to STOP a service, however the service has no Stop Command defined so no action could be taken. Response: Examine the definition of the service and if necessary update the definition of the service to include the command to run when STOP is issued. For services of type 'SERVER' the command to run when STOP is executed is stored when the service is started so any alteration to the service definition will have no effect until the service is restarted following the update. AMQ8740Start cannot be executed for service with blank STARTCMD. Severity: 20 : Error Explanation: A request was made to START a service, however the service has no Start Command defined so no action could be taken. Response: Examine the definition of the service and if necessary update the definition of the service to include the command to run when START is issued. AMQ8741Unable to connect to queue manager. Severity: 20 : Error Explanation: The dead-letter queue handler (runmqdlq) could not connect to queue manager . This message is typically issued when the requested queue manager has not been started or is quiescing, or if the process does not have sufficient authority. The completion code () and the reason () can be used to identify the error. The dead-letter queue handler ends. Response: Take appropriate action based upon the completion code and reason. AMQ8741 (iSeries)Unable to connect to queue manager. Severity: 20 : Error Explanation: The dead-letter queue handler (STRMQMDLQ) could not connect to queue manager . This message is typically issued when the requested queue manager has not been started or is quiescing, or if the process does not have sufficient authority. The completion code () and the reason () can be used to identify the error. The dead-letter queue handler ends. Response: Take appropriate action based upon the completion code and reason. AMQ8742Unable to open queue manager: CompCode = Reason = . Severity: 20 : Error Explanation: The dead-letter queue handler (runmqdlq) could not open the queue manager object. This message is typically issued because of a resource shortage or because the process does not have sufficient authority. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends. Response: Take appropriate action based upon the completion code and reason. AMQ8742 (iSeries)Unable to open queue manager: CompCode = Reason = . Severity: 20 : Error Explanation: The dead-letter queue handler (STRMQMDLQ) could not open the queue manager object. This message is typically issued because of a resource shortage or because the process does not have sufficient authority. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends. Response: Take appropriate action based upon the completion code and reason. AMQ8743Unable to inquire on queue manager: CompCode = Reason = . Severity: 20 : Error Explanation: The dead-letter queue handler (runmqdlq) could not inquire on the queue manager. This message is typically issued because of a resource shortage or because the queue manager is ending. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends. Response: Take appropriate action based upon the completion code and reason. AMQ8743 (iSeries)Unable to inquire on queue manager: CompCode = Reason = . Severity: 20 : Error Explanation: The dead-letter queue handler (STRMQMDLQ) could not inquire on the queue manager. This message is typically issued because of a resource shortage or because the queue manager is ending. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends. Response: Take appropriate action based upon the completion code and reason. AMQ8744Unable to close queue manager: CompCode = Reason = . Severity: 20 : Error Explanation: The dead-letter queue handler (runmqdlq) could not close the queue manager. This message is typically issued because of a resource shortage or because the queue manager is ending. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends. Response: Take appropriate action based upon the completion code and reason. AMQ8744 (iSeries)Unable to close queue manager: CompCode = Reason = . Severity: 20 : Error Explanation: The dead-letter queue handler (STRMQMDLQ) could not close the queue manager. This message is typically issued because of a resource shortage or because the queue manager is ending. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends. Response: Take appropriate action based upon the completion code and reason. AMQ8745Unable to open dead-letter queue for browse. Severity: 20 : Error Explanation: The dead-letter queue handler (runmqdlq) could not open the dead-letter queue for browsing. This message is typically issued because another process has opened the dead-letter queue for exclusive access, or because an invalid dead-letter queue name was specified. Other possible reasons include resource shortages or insufficient authority. The completion code() and the reason() can be used to identify the error. The dead-letter queue handler ends. Response: Take appropriate action based upon the completion code and reason. AMQ8745 (iSeries)Unable to open dead-letter queue for browse. Severity: 20 : Error Explanation: The dead-letter queue handler (STRMQMDLQ) could not open the dead-letter queue for browsing. This message is typically issued because another process has opened the dead-letter queue for exclusive access, or because an invalid dead-letter queue name was specified. Other possible reasons include resource shortages or insufficient authority. The completion code() and the reason() can be used to identify the error. The dead-letter queue handler ends. Response: Take appropriate action based upon the completion code and reason. AMQ8746Unable to close dead-letter queue: CompCode = Reason = . Severity: 20 : Error Explanation: The dead-letter queue handler (runmqdlq) could not close the dead-letter queue. This message is typically issued because of a resource shortage or because the queue manager is ending. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends. Response: Take appropriate action based upon the completion code and reason. AMQ8746 (iSeries)Unable to close dead-letter queue: CompCode = Reason = . Severity: 20 : Error Explanation: The dead-letter queue handler (STRMQMDLQ) could not close the dead-letter queue. This message is typically issued because of a resource shortage or because the queue manager is ending. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends. Response: Take appropriate action based upon the completion code and reason. AMQ8747Integer parameter outside permissible range. Severity: 20 : Error Explanation: The integer parameter () supplied to the dead-letter handler was outside of the valid range for on line . Response: Correct the input data and restart the dead-letter queue handler. AMQ8748Unable to get message from dead-letter queue: CompCode = Reason = . Severity: 20 : Error Explanation: The dead-letter queue handler (runmqdlq) could not get the next message from the dead-letter queue. This message is typically issued because of the queue manager ending, a resource problem, or another process having deleted the dead-letter queue. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends. Response: Take appropriate action based upon the completion code and reason. AMQ8748 (iSeries)Unable to get message from dead-letter queue: CompCode = Reason = . Severity: 20 : Error Explanation: The dead-letter queue handler (STRMQMDLQ) could not get the next message from the dead-letter queue. This message is typically issued because of the queue manager ending, a resource problem, or another process having deleted the dead-letter queue. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends. Response: Take appropriate action based upon the completion code and reason. AMQ8749Unable to commit/backout action on dead-letter queue: CompCode = Reason = . Severity: 20 : Error Explanation: The dead-letter queue handler (runmqdlq) was unable to commit or backout an update to the dead-letter queue. This message is typically issued because of the queue manager ending, or because of a resource shortage. If the queue manager has ended, the update to the dead-letter queue (and any associated updates) will be backed out when the queue manager restarts. If the problem was due to a resource problem then the updates will be backed out when the dead-letter queue handler terminates. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends. Response: Take appropriate action based upon the completion code and reason. AMQ8749 (iSeries)Unable to commit/backout action on dead-letter queue: CompCode = Reason = . Severity: 20 : Error Explanation: The dead-letter queue handler (STRMQMDLQ) was unable to commit or backout an update to the dead-letter queue. This message is typically issued because of the queue manager ending, or because of a resource shortage. If the queue manager has ended, the update to the dead-letter queue (and any associated updates) will be backed out when the queue manager restarts. If the problem was due to a resource problem then the updates will be backed out when the dead-letter queue handler terminates. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends. Response: Take appropriate action based upon the completion code and reason. AMQ8750No valid input provided to runmqdlq. Severity: 20 : Error Explanation: Either no input was provided to runmqdlq, or the input to runmqdlq contained no valid message templates. If input was provided to runmqdlq but was found to be invalid, earlier messages will have been produced explaining the cause of the error. The dead-letter queue handler will ends. Response: Correct the input data and restart the dead-letter queue handler. AMQ8750 (iSeries)No valid input provided to STRMQMDLQ. Severity: 20 : Error Explanation: Either no input was provided to STRMQMDLQ, or the input to STRMQMDLQ contained no valid message templates. If input was provided to STRMQMDLQ but was found to be invalid, earlier messages will have been produced explaining the cause of the error. The dead-letter queue handler will ends. Response: Correct the input data and restart the dead-letter queue handler. AMQ8751Unable to obtain private storage. Severity: 20 : Error Explanation: The dead-letter queue handler (runmqdlq) was unable to obtain private storage. This problem would typically arise as a result of some more global problem. For example if there is a persistent problem that is causing messages to be written to the DLQ and the same problem (for example queue full) is preventing the dead-letter queue handler from taking the requested action with the message, it is necessary for the dead-letter queue handler to maintain a large amount of state data to remember the retry counts associated with each message, or if the dead-letter queue contains a large number of messages and the rules table has directed the dead-letter queue handler to ignore the messages. Response: Investigate if some more global problem exists, and if the dead-letter queue contains a large number of messages. If the problem persists contact your support center. AMQ8751 (iSeries)Unable to obtain private storage. Severity: 20 : Error Explanation: The dead-letter queue handler (STRMQMDLQ) was unable to obtain private storage. This problem would typically arise as a result of some more global problem. For example if there is a persistent problem that is causing messages to be written to the DLQ and the same problem (for example queue full) is preventing the dead-letter queue handler from taking the requested action with the message, it is necessary for the dead-letter queue handler to maintain a large amount of state data to remember the retry counts associated with each message, or if the dead-letter queue contains a large number of messages and the rules table has directed the dead-letter queue handler to ignore the messages. Response: Investigate if some more global problem exists, and if the dead-letter queue contains a large number of messages. If the problem persists contact your support center. AMQ8752Parameter() exceeds maximum length on line . Severity: 20 : Error Explanation: A parameter supplied as input to the dead-letter handler exceeded the maximum length for parameters of that type. Response: Correct the input data and restart the dead-letter queue handler. AMQ8753Duplicate parameter() found on line . Severity: 20 : Error Explanation: Two or more parameters of the same type were supplied on a single input line to the dead-letter queue handler. Response: Correct the input and restart the dead-letter queue handler. AMQ8756Error detected releasing private storage. Severity: 20 : Error Explanation: The dead-letter queue handler (runmqdlq) was informed of an error while attempting to release an area of private storage. The dead-letter queue handler ends. Response: This message should be preceded by a message or FFST information from the internal routine that detected the error. Take the action associated with the earlier error information. AMQ8756 (iSeries)Error detected releasing private storage. Severity: 20 : Error Explanation: The dead-letter queue handler (STRMQMDLQ) was informed of an error while attempting to release an area of private storage. The dead-letter queue handler ends. Response: This message should be preceded by a message or FFST information from the internal routine that detected the error. Take the action associated with the earlier error information. AMQ8757Integer parameter() outside permissible range on line . Severity: 20 : Error Explanation: An integer supplied as input to the dead-letter handler was outside of the valid range of integers supported by the dead-letter queue handler. Response: Correct the input data and restart the dead-letter queue handler. AMQ8758 errors detected in input to runmqdlq. Severity: 20 : Error Explanation: One or more errors have been detected in the input to the dead-letter queue handler(runmqdlq). Error messages will have been generated for each of these errors. The dead-letter queue handler ends. Response: Correct the input data and restart the dead-letter queue handler. AMQ8758 (iSeries) errors detected in input to STRMQMDLQ. Severity: 20 : Error Explanation: One or more errors have been detected in the input to the dead-letter queue handler(STRMQMDLQ). Error messages will have been generated for each of these errors. The dead-letter queue handler ends. Response: Correct the input data and restart the dead-letter queue handler. AMQ8759Invalid combination of parameters to dead-letter queue handler on line . Severity: 20 : Error Explanation: An invalid combination of input parameters has been supplied to the dead-letter queue handler. Possible causes are: no ACTION specified, ACTION(FWD) but no FWDQ specified, HEADER(YES|NO) specified without ACTION(FWD). Response: Correct the input data and restart the dead-letter queue handler. AMQ8760Unexpected failure while initializing process: Reason = . Severity: 30 : Severe error Explanation: The dead-letter queue handler (runmqdlq) could not perform basic initialization required to use MQ services because of an unforeseen error. The dead-letter queue handler ends. Response: Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Contact your support center. Do not discard these files until the problem has been resolved. AMQ8760 (iSeries)Unexpected failure while initializing process: Reason = . Severity: 30 : Severe error Explanation: The dead-letter queue handler (STRMQMDLQ) could not perform basic initialization required to use MQ services because of an unforeseen error. The dead-letter queue handler ends. Response: Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Contact your support center. Do not discard these files until the problem has been resolved. AMQ8761Unexpected failure while connecting to queue manager: CompCode = Reason = . Severity: 30 : Severe error Explanation: The dead-letter queue handler (runmqdlq) could not connect to the requested queue manager because of an unforeseen error. The dead-letter queue handler ends. Response: Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Contact your support center. Do not discard these files until the problem has been resolved. AMQ8761 (iSeries)Unexpected failure while connecting to queue manager: CompCode = Reason = . Severity: 30 : Severe error Explanation: The dead-letter queue handler (STRMQMDLQ) could not connect to the requested queue manager because of an unforeseen error. The dead-letter queue handler ends. Response: Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Contact your support center. Do not discard these files until the problem has been resolved. AMQ8762Unexpected error while attempting to open queue manager: CompCode = Reason = . Severity: 30 : Severe error Explanation: The dead-letter queue handler (runmqdlq) could not open the queue manager because of an unforeseen error. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends. Response: Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Contact your support center. Do not discard these files until the problem has been resolved. AMQ8762 (iSeries)Unexpected error while attempting to open queue manager: CompCode = Reason = . Severity: 30 : Severe error Explanation: The dead-letter queue handler (STRMQMDLQ) could not open the queue manager because of an unforeseen error. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends. Response: Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Contact your support center. Do not discard these files until the problem has been resolved. AMQ8763Unexpected error while inquiring on queue manager: CompCode = Reason = . Severity: 30 : Severe error Explanation: The dead letter queue handler (runmqdlq) could not inquire on the queue manager because of an unforeseen error. The completion code and the reason can be used to identify the error. The dead letter queue handler ends. Response: Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Contact your support center. Do not discard these files until the problem has been resolved. AMQ8763 (iSeries)Unexpected error while inquiring on queue manager: CompCode = Reason = . Severity: 30 : Severe error Explanation: The dead letter queue handler (STRMQMDLQ) could not inquire on the queue manager because of an unforeseen error. The completion code and the reason can be used to identify the error. The dead letter queue handler ends. Response: Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Contact your support center. Do not discard these files until the problem has been resolved. AMQ8764Unexpected error while attempting to close queue manager: CompCode = Reason = . Severity: 30 : Severe error Explanation: The dead-letter queue handler (runmqdlq) could not close the queue manager because of an unforeseen error. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends. Response: Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Contact your support center. Do not discard these files until the problem has been resolved. AMQ8764 (iSeries)Unexpected error while attempting to close queue manager: CompCode = Reason = . Severity: 30 : Severe error Explanation: The dead-letter queue handler (STRMQMDLQ) could not close the queue manager because of an unforeseen error. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends. Response: Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Contact your support center. Do not discard these files until the problem has been resolved. AMQ8765Unexpected failure while opening dead-letter queue for browse: CompCode = Reason = . Severity: 30 : Severe error Explanation: The dead-letter queue handler (runmqdlq) could not open the dead-letter queue for browsing because of an unforeseen error. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends. Response: Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Contact your support center. Do not discard these files until the problem has been resolved. AMQ8765 (iSeries)Unexpected failure while opening dead-letter queue for browse: CompCode = Reason = . Severity: 30 : Severe error Explanation: The dead-letter queue handler (STRMQMDLQ) could not open the dead-letter queue for browsing because of an unforeseen error. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends. Response: Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Contact your support center. Do not discard these files until the problem has been resolved. AMQ8766Unexpected error while closing dead-letter queue: CompCode = Reason = . Severity: 30 : Severe error Explanation: The dead-letter queue handler (runmqdlq) could not close the dead-letter queue because of an unforeseen error. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends. Response: Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Contact your support center. Do not discard these files until the problem has been resolved. AMQ8766 (iSeries)Unexpected error while closing dead-letter queue: CompCode = Reason = . Severity: 30 : Severe error Explanation: The dead-letter queue handler (STRMQMDLQ) could not close the dead-letter queue because of an unforeseen error. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends. Response: Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Contact your support center. Do not discard these files until the problem has been resolved. AMQ8767Unexpected error while getting message from dead-letter queue: CompCode = Reason = . Severity: 30 : Severe error Explanation: The dead-letter queue handler (runmqdlq) could not get the next message from the dead-letter queue because of an unforeseen error. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends. Response: Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Contact your support center. Do not discard these files until the problem has been resolved. AMQ8767 (iSeries)Unexpected error while getting message from dead-letter queue: CompCode = Reason = . Severity: 30 : Severe error Explanation: The dead-letter queue handler (STRMQMDLQ) could not get the next message from the dead-letter queue because of an unforeseen error. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends. Response: Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Contact your support center. Do not discard these files until the problem has been resolved. AMQ8768Unexpected error committing/backing out action on dead-letter queue: CompCode = Reason = . Severity: 30 : Severe error Explanation: The dead-letter queue handler (runmqdlq) was unable to either commit or backout an update to the dead-letter queue because of an unforeseen error. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends. Response: Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Contact your support center. Do not discard these files until the problem has been resolved. AMQ8768 (iSeries)Unexpected error committing/backing out action on dead-letter queue: CompCode = Reason = . Severity: 30 : Severe error Explanation: The dead-letter queue handler (STRMQMDLQ) was unable to either commit or backout an update to the dead-letter queue because of an unforeseen error. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends. Response: Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Contact your support center. Do not discard these files until the problem has been resolved. AMQ8769Unable to disconnect from queue manager: CompCode = Reason = . Severity: 30 : Severe error Explanation: The dead-letter queue handler (runmqdlq) was unable to disconnect from the queue manager because of an unexpected error. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends. Response: Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Contact your support center. Do not discard these files until the problem has been resolved. AMQ8769 (iSeries)Unable to disconnect from queue manager: CompCode = Reason = . Severity: 30 : Severe error Explanation: The dead-letter queue handler (STRMQMDLQ) was unable to disconnect from the queue manager because of an unexpected error. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends. Response: Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Contact your support center. Do not discard these files until the problem has been resolved. AMQ8770 (iSeries)Cannot open for command . Severity: 40 : Stop Error Explanation: The command failed to open for WebSphere MQ processing. Response: Check that the intended file or member exists, and was specified correctly. Correct the specification or create the object and try the operation again. AMQ8822Invalid response, please re-enter (y or n): Severity: 0 : Information Response: None. AMQ8919There are no matching WebSphere MQ queue manager names. Severity: 30 : Severe error AMQ8934 (iSeries)Message . . . . : Severity: 10 : Warning AMQ8935 (iSeries)Cause . . . . . : Severity: 10 : Warning AMQ8936 (iSeries)Recovery . . . : Severity: 10 : Warning AMQ8937 (iSeries)Technical Description . . . . . . . . : Severity: 10 : Warning AMQ8A01 (iSeries)Create Message Queue Manager AMQ8A02 (iSeries)Delete Message Queue Manager AMQ8A04 (iSeries)Work with MQ Messages AMQ8A05 (iSeries)Change Message Queue Manager AMQ8A06 (iSeries)Display Message Queue Manager AMQ8A07 (iSeries)End Message Queue Manager AMQ8A08 (iSeries)Start Message Queue Manager AMQ8A09 (iSeries)Change MQ Queue AMQ8A0A (iSeries)Clear MQ Queue AMQ8A0B (iSeries)Copy MQ Queue AMQ8A0C (iSeries)Create MQ Queue AMQ8A0D (iSeries)Delete MQ Queue AMQ8A0E (iSeries)Display MQ Queue AMQ8A0F (iSeries)Work with MQ Queues AMQ8A10 (iSeries)Change MQ Process AMQ8A11 (iSeries)Copy MQ Process AMQ8A12 (iSeries)Create MQ Process AMQ8A13 (iSeries)Delete MQ Process AMQ8A14 (iSeries)Display MQ Process AMQ8A15 (iSeries)Work with MQ Processes AMQ8A16 (iSeries)Start MQ Command Server AMQ8A17 (iSeries)End MQ Command Server AMQ8A18 (iSeries)Display MQ Command Server AMQ8A19 (iSeries)Set MQ AMQ8A20 (iSeries)Quiesce Message Queue Managers AMQ8A21 (iSeries)Quiesce Retry Delay AMQ8A23 (iSeries)Work with Queue Status AMQ8A30 (iSeries)Create MQ Channel AMQ8A31 (iSeries)Display MQ Channel AMQ8A32 (iSeries)Start MQ Listener AMQ8A33 (iSeries)Ping MQ Channel AMQ8A34 (iSeries)Delete MQ Channel AMQ8A36 (iSeries)Work with MQ Channels AMQ8A37 (iSeries)Change MQ Channel AMQ8A38 (iSeries)Copy MQ Channel AMQ8A39 (iSeries)Reset MQ Channel AMQ8A40 (iSeries)End MQ Channel AMQ8A41 (iSeries)Start MQ Channel AMQ8A42 (iSeries)Start MQ Channel Initiator AMQ8A43 (iSeries)Grant MQ Object Authority AMQ8A44 (iSeries)Revoke MQ Object Authority AMQ8A45 (iSeries)Display MQ Object Authority AMQ8A46 (iSeries)Display MQ Object Names AMQ8A47 (iSeries)Refresh WebSphere MQ Authority AMQ8A48 (iSeries)Work with MQ Authority AMQ8A49 (iSeries)Start MQ Service AMQ8A50 (iSeries)End MQ Service AMQ8A51 (iSeries)Connect MQ AMQ8A52 (iSeries)Disconnect MQ AMQ8A53 (iSeries)Work with MQ Authority Data AMQ8A54 (iSeries)Resolve MQ Channel AMQ8A55 (iSeries)Work with MQ Channel Status AMQ8A56 (iSeries)SSL Client Authentication AMQ8A57 (iSeries)SSL CipherSpec AMQ8A58 (iSeries)SSL Peer name AMQ8A59 (iSeries)Local communication address AMQ8A5A (iSeries)Batch Heartbeat Interval AMQ8A5B (iSeries)Remove Queues AMQ8A5C (iSeries)Refresh Repository AMQ8A5D (iSeries)IP Address AMQ8A60 (iSeries)Cluster Name AMQ8A61 (iSeries)Cluster Name List AMQ8A62 (iSeries)Mode Name AMQ8A63 (iSeries)Password AMQ8A64 (iSeries)Transaction Program Name AMQ8A65 (iSeries)User Profile AMQ8A66 (iSeries)Network Connection Priority AMQ8A67 (iSeries)Batch Interval AMQ8A68 (iSeries)Batch Interval AMQ8A69 (iSeries)Cluster Workload Exit Data AMQ8A6A (iSeries)Cluster Workload Exit AMQ8A6B (iSeries)Repository Cluster AMQ8A6C (iSeries)Repository Cluster Namelist AMQ8A6D (iSeries)Cluster Workload Exit Data Length AMQ8A6E (iSeries)Maximum Message Length AMQ8A6F (iSeries)Default Queue Manager AMQ8A70 (iSeries)Default Binding AMQ8A71 (iSeries)Channel Table AMQ8A72 (iSeries)Change MQ Namelist AMQ8A73 (iSeries)List of Names AMQ8A74 (iSeries)Namelist AMQ8A75 (iSeries)Create MQ Namelist AMQ8A76 (iSeries)Recreate MQ Object AMQ8A77 (iSeries)Record MQ Object Image AMQ8A78 (iSeries)Start WebSphere MQ Commands AMQ8A7A (iSeries)Copy MQ Namelist AMQ8A7B (iSeries)From Namelist AMQ8A7C (iSeries)To Namelist AMQ8A7D (iSeries)Delete MQ Namelist AMQ8A7E (iSeries)Display MQ Namelist AMQ8A7F (iSeries)Work with MQ Namelist AMQ8A80 (iSeries)Group Profile AMQ8A81 (iSeries)User Profile AMQ8A82 (iSeries)Service Component AMQ8A83 (iSeries)Work with MQ Queue Manager AMQ8A84 (iSeries)Work with MQ Clusters AMQ8A85 (iSeries)Start MQ Trigger Monitor AMQ8A86 (iSeries)End MQ Listeners AMQ8A87 (iSeries)Work with MQ Transactions AMQ8A88 (iSeries)Resolve MQ Transaction AMQ8A89 (iSeries)Work with MQ Cluster Queues AMQ8A8A (iSeries)Display Journal Receiver Data AMQ8A8B (iSeries)Start MQ Pub/Sub Broker AMQ8A8C (iSeries)End MQ Pub/Sub Broker AMQ8A8D (iSeries)Display MQ Pub/Sub Broker AMQ8A8E (iSeries)Clear MQ Pub/Sub Broker AMQ8A8F (iSeries)Delete MQ Pub/Sub Broker AMQ8B01 (iSeries)Message Queue Manager name AMQ8B02 (iSeries)Text 'description' AMQ8B03 (iSeries)Trigger interval AMQ8B04 (iSeries)Undelivered message queue AMQ8B05 (iSeries)Default transmission queue AMQ8B06 (iSeries)Maximum handle limit AMQ8B07 (iSeries)Maximum uncommitted messages AMQ8B08 (iSeries)Queue name AMQ8B09 (iSeries)Output AMQ8B0A (iSeries)Library AMQ8B0B (iSeries)File to receive output AMQ8B0C (iSeries)OPTION(*MVS) not valid without specifying a value for WAIT. Severity: 40 : Stop Error Explanation: The OPTION(*MVS) parameter may not be specified without specifying a value for the WAIT parameter. Response: Remove the OPTION(*MVS) parameter from the command or, specify a value for the WAIT parameter. Then try the command again. AMQ8B0D (iSeries)Member to receive output AMQ8B0E (iSeries)Replace or add records AMQ8B0F (iSeries)Option AMQ8B10 (iSeries)Mode AMQ8B11 (iSeries)Put enabled AMQ8B12 (iSeries)Default message priority AMQ8B13 (iSeries)Default message persistence AMQ8B14 (iSeries)Process name AMQ8B15 (iSeries)Triggering enabled AMQ8B16 (iSeries)Get enabled AMQ8B17 (iSeries)Sharing enabled AMQ8B18 (iSeries)Default share option AMQ8B19 (iSeries)Message delivery sequence AMQ8B1A (iSeries)Harden backout count AMQ8B1B (iSeries)Trigger type AMQ8B1C (iSeries)Trigger depth AMQ8B1D (iSeries)Trigger message priority AMQ8B1E (iSeries)Trigger data AMQ8B1F (iSeries)Retention interval AMQ8B20 (iSeries)Maximum queue depth AMQ8B21 (iSeries)Maximum message length AMQ8B22 (iSeries)Backout threshold AMQ8B23 (iSeries)Backout requeue name AMQ8B24 (iSeries)Initiation queue AMQ8B25 (iSeries)Usage AMQ8B26 (iSeries)Definition type AMQ8B27 (iSeries)Target queue AMQ8B28 (iSeries)Remote queue AMQ8B29 (iSeries)Remote Message Queue Manager AMQ8B2A (iSeries)Transmission queue AMQ8B2B (iSeries)From queue name AMQ8B2C (iSeries)To queue name AMQ8B2D (iSeries)Replace AMQ8B2E (iSeries)Queue type AMQ8B2F (iSeries)Application type AMQ8B30 (iSeries)Application identifier AMQ8B31 (iSeries)User data AMQ8B32 (iSeries)Environment data AMQ8B33 (iSeries)From process AMQ8B34 (iSeries)To process AMQ8B36 (iSeries)Job name AMQ8B37 (iSeries)Number AMQ8B3A (iSeries)Convert message AMQ8B3B (iSeries)Replace to member AMQ8B3C (iSeries)Heartbeat interval AMQ8B3D (iSeries)Non Persistent Message Speed AMQ8B3E (iSeries)Force AMQ8B3F (iSeries)No Jobs to display AMQ8B41 (iSeries)Queue definition scope AMQ8B42 (iSeries)Queue depth high threshold AMQ8B43 (iSeries)Queue depth low threshold AMQ8B44 (iSeries)Queue full events enabled AMQ8B45 (iSeries)Queue high events enabled AMQ8B46 (iSeries)Queue low events enabled AMQ8B47 (iSeries)Service interval AMQ8B48 (iSeries)Service interval events AMQ8B49 (iSeries)Distribution list support AMQ8B4A (iSeries)Parent Message Queue Manager AMQ8B4B (iSeries)Break Parent link AMQ8B4C (iSeries)Child Message Queue Manager AMQ8B53 (iSeries)Authorization events enabled AMQ8B54 (iSeries)Inhibit events enabled AMQ8B55 (iSeries)Local error events enabled AMQ8B56 (iSeries)Remote error events enabled AMQ8B57 (iSeries)Performance events enabled AMQ8B58 (iSeries)Start and stop events enabled AMQ8B59 (iSeries)Automatic Channel Definition AMQ8B5A (iSeries)Auto Chan. Def. events enabled AMQ8B5B (iSeries)Auto Chan. Def. exit program AMQ8B5C (iSeries)Redefine system objects AMQ8B5D (iSeries)Wait time AMQ8B5E (iSeries)Startup Status Detail AMQ8B60 (iSeries)Transaction type AMQ8B61 (iSeries)Log recovery events enabled AMQ8B62 (iSeries)IP protocol AMQ8B63 (iSeries)Configuration events enabled AMQ8B64 (iSeries)Refresh Message Queue Manager AMQ8B65 (iSeries)Refresh Type AMQ8B66 (iSeries)Include Interval AMQ8B67 (iSeries)WebSphere MQ queue manager refreshed. AMQ8B68 (iSeries)Channel events enabled AMQ8B69 (iSeries)SSL events enabled AMQ8B6A (iSeries)Filter command AMQ8B6B (iSeries)Filter keyword AMQ8B6C (iSeries)Filter operator AMQ8B6D (iSeries)Filter value AMQ8B6E (iSeries)Filter value not valid with keyword . Severity: 30 : Severe error Explanation: The filter value is not valid with the keyword . Response: Specify a valid filter value for the keyword . AMQ8B70 (iSeries)Change MQ AuthInfo object AMQ8B71 (iSeries)Copy MQ AuthInfo object AMQ8B72 (iSeries)Create MQ AuthInfo object AMQ8B73 (iSeries)Delete MQ AuthInfo object AMQ8B74 (iSeries)Display MQ AuthInfo object AMQ8B75 (iSeries)From AuthInfo name AMQ8B76 (iSeries)AuthInfo name AMQ8B77 (iSeries)AuthInfo type AMQ8B78 (iSeries)User name AMQ8B79 (iSeries)User password AMQ8B7A (iSeries)Work with AuthInfo objects AMQ8B7B (iSeries)To AuthInfo name AMQ8B80 (iSeries)Change MQ Processor Allowance AMQ8B81 (iSeries)Display MQ Processor Allowance AMQ8B82 (iSeries)Sufficient Licence Units AMQ8C01 (iSeries)From channel AMQ8C02 (iSeries)Channel name AMQ8C03 (iSeries)Channel type AMQ8C04 (iSeries)SSL key reset count AMQ8C05 (iSeries)Remote queue manager AMQ8C07 (iSeries)Transmission queue AMQ8C08 (iSeries)Connection name AMQ8C09 (iSeries)Message channel agent AMQ8C10 (iSeries)Message channel agent user ID AMQ8C12 (iSeries)Batch size AMQ8C13 (iSeries)Disconnect interval AMQ8C14 (iSeries)Short retry count AMQ8C15 (iSeries)Short retry interval AMQ8C16 (iSeries)Long retry count AMQ8C17 (iSeries)Long retry interval AMQ8C18 (iSeries)Security exit AMQ8C19 (iSeries)Message exit AMQ8C20 (iSeries)Send exit AMQ8C21 (iSeries)Receive exit AMQ8C22 (iSeries)SSL CRL Namelist AMQ8C23 (iSeries)SSL Key Repository AMQ8C24 (iSeries)Put authority AMQ8C25 (iSeries)Sequence number wrap AMQ8C27 (iSeries)Transport type AMQ8C28 (iSeries)Data count AMQ8C29 (iSeries)Count AMQ8C30 (iSeries)To channel AMQ8C31 (iSeries)Message sequence number AMQ8C32 (iSeries)SSL Cryptographic Hardware AMQ8C33 (iSeries)Security exit user data AMQ8C34 (iSeries)Send exit user data AMQ8C35 (iSeries)Receive exit user data AMQ8C36 (iSeries)Message exit user data AMQ8C37 (iSeries)Resolve option AMQ8C38 (iSeries)Connection name AMQ8C39 (iSeries)Transmission queue name AMQ8C40 (iSeries)SSL Repository Password AMQ8C41 (iSeries)First Message AMQ8C42 (iSeries)Maximum number of messages AMQ8C43 (iSeries)Maximum message size AMQ8C44 (iSeries)Message retry exit AMQ8C45 (iSeries)Message retry exit data AMQ8C46 (iSeries)Number of message retries AMQ8C47 (iSeries)Message retry interval AMQ8C48 (iSeries)Coded Character Set AMQ8C49 (iSeries)Max message length AMQ8C50 (iSeries)Repository name AMQ8C51 (iSeries)Repository name list AMQ8C52 (iSeries)Cluster workload exit length AMQ8C53 (iSeries)Cluster workload exit AMQ8C54 (iSeries)Cluster workload exit data AMQ8C55 (iSeries)Suspend Cluster Queue Manager AMQ8C56 (iSeries)Reset Cluster AMQ8C57 (iSeries)Refresh MQ Cluster AMQ8C58 (iSeries)Resume Cluster Queue Manager AMQ8C59 (iSeries)Action AMQ8C5A (iSeries)Queue Manager Name for removal AMQ8C5B (iSeries)Work with MQ Listeners AMQ8C5C (iSeries)Queue Manager Id for removal AMQ8C60 (iSeries)Display Cluster Message Queue Manager AMQ8C61 (iSeries)Cluster Queue Manager name AMQ8C62 (iSeries)End MQ Listeners AMQ8C63 (iSeries)Port number AMQ8C64 (iSeries)Message channel agent Type AMQ8C65 (iSeries)Task user identifier AMQ8D01 (iSeries)Trace MQ AMQ8D02 (iSeries)Trace option setting AMQ8D03 (iSeries)Trace level AMQ8D04 (iSeries)Trace types AMQ8D05 (iSeries)Maximum storage to use AMQ8D06 (iSeries)Trace early AMQ8D07 (iSeries)Exclude types AMQ8D0A (iSeries)Output member options AMQ8D10 (iSeries)Object name AMQ8D11 (iSeries)Object type AMQ8D12 (iSeries)User names AMQ8D13 (iSeries)Authority AMQ8D14 (iSeries)Authorization list AMQ8D15 (iSeries)Reference object name AMQ8D16 (iSeries)Reference object type AMQ8D17 (iSeries)Object name AMQ8D18 (iSeries)Process name AMQ8D19 (iSeries)Queue name AMQ8D1A (iSeries)Queue Manager Library AMQ8D1B (iSeries)ASP Number AMQ8D1C (iSeries)Journal receiver threshold AMQ8D20 (iSeries)Channel name AMQ8D22 (iSeries)Cluster name AMQ8D23 (iSeries)Cluster namelist name AMQ8D24 (iSeries)User name AMQ8D25 (iSeries)Channel status AMQ8D26 (iSeries)End connected jobs AMQ8D27 (iSeries)Timeout interval (seconds) AMQ8D28 (iSeries)Object/Profile name AMQ8D29 (iSeries)Service Component name AMQ8D30 (iSeries)Keep Alive Interval 9000-9999 - Remote See Reading a message for an explanation of how to interpret these messages. AMQ9001 Channel ended normally. Severity: 0 : Information Explanation: Channel ended normally. Response: None. AMQ9002 Channel is starting. Severity: 0 : Information Explanation: Channel is starting. Response: None. AMQ9003 (iSeries)Channel last message sequence number is . Severity: 0 : Information Explanation: Channel last message sequence number is . Response: None. AMQ9004 (iSeries)Channel status information. Severity: 0 : Information Explanation: Channel status information: Number of Messages in Doubt - In Doubt Sequence Number - In Doubt Logic Unit of Work ID - Response: None. AMQ9181 The response set by the exit is not valid. Severity: 30 : Severe error Explanation: The user exit returned a response code that is not valid in the ExitResponse field of the channel exit parameters (MQCXP). Message AMQ9190 is issued giving more details, and the channel stops. Response: Investigate why the user exit program set a response code that is not valid. AMQ9182 The secondary response set by the exit is not valid. Severity: 30 : Severe error Explanation: The user exit returned a secondary response code in the ExitResponse2 field of the channel exit parameters (MQCXP) that is not valid. Message AMQ9190 is issued giving more details, and the channel stops. Response: Investigate why the user exit program set a secondary response code that is not valid. AMQ9184 The exit buffer address set by the exit is not valid. Severity: 30 : Severe error Explanation: The user exit returned an address for the exit buffer that is not valid, when the secondary response code in the ExitResponse2 field of the channel exit parameters (MQCXP) is set to MQXR2_USE_EXIT_BUFFER. Message AMQ9190 is issued giving more details, and the channel stops. Response: Investigate why the user exit program set an exit buffer address that is not valid. The most likely cause is the failure to set a value, so that the value is 0. AMQ9185 The exit space set by the exit is not valid. Severity: 30 : Severe error Explanation: The user exit returned an exit space value that is not valid in the ExitSpace field of the channel exit parameters (MQCXP). Message AMQ9190 is issued giving more details, and the channel stops. Response: Investigate why the user exit program set an exit space value that is not valid. Correct the error. AMQ9186 Too much exit space reserved by send exits. Severity: 30 : Severe error Explanation: At exit initialization the send exits in the send exit chain for channel returned values in the ExitSpace field of the channel exit parameters (MQCXP). The total of these ExitSpace values is . The maximum number of bytes that can be sent in a single transmission is . Room must be left for at least 1024 bytes of message data in each transmission. So too much exit space has been reserved by the send exits. The channel stops. Response: Investigate why the send exit programs set exit space values that are too large. Correct the error. AMQ9187 The header compression value set by the exit is not valid. Severity: 30 : Severe error Explanation: The user exit returned a header compression value in the CurHdrCompression field of the channel exit parameters (MQCXP) that was not one of the negotiated supported values specified in the HdrCompList field of the channel description (MQCD). Message AMQ9190 is issued giving more details, and the channel stops. Response: Investigate why the user exit program specified a header compression value that was not one of the negotiated supported values. AMQ9188 The message compression value set by the exit is not valid. Severity: 30 : Severe error Explanation: The user exit returned a message compression value in the CurMsgCompression field of the channel exit parameters (MQCXP) that was not one of the negotiated supported values specified in the MsgCompList field of the channel description (MQCD). Message AMQ9190 is issued giving more details, and the channel stops. Response: Investigate why the user exit program specified a message compression value that was not one of the negotiated supported values. AMQ9189 The data length set by the exit is not valid. Severity: 30 : Severe error Explanation: The user exit returned a data length value that was not greater than zero. Message AMQ9190 is issued giving more details, and the channel stops. Response: Investigate why the user exit program set a data length that is not valid. AMQ9190 Channel stopping because of an error in the exit. Severity: 30 : Severe error Explanation: The user exit , invoked for channel with id and reason , returned values that are not valid, as reported in the preceding messages. The channel stops. Response: Investigate why the user exit program set values that are not valid. AMQ9195 Data length larger than maximum segment length. Severity: 30 : Severe error Explanation: The data length set by send exit is larger than the maximum segment length (). The maximum segment length is the maximum number of bytes that can be sent in a single transmission minus the user exit space required by all the send exits subsequent to the current one in the send exit chain. Message AMQ9190 is issued giving more details, and the channel stops. Response: Investigate why the user exit program set a data length that is not valid. Correct the error. AMQ9196 Data length is larger than the agent buffer length. Severity: 30 : Severe error Explanation: The data length set by exit is larger than the agent buffer length. The user exit returned data in the supplied agent buffer, but the length specified is greater than the length of the buffer. Message AMQ9190 is issued giving more details, and the channel stops. Response: Investigate why the user exit program set a data length that is not valid. Correct the error. AMQ9197 Data length is larger than the exit buffer length. Severity: 30 : Severe error Explanation: The data length set by exit is larger than the exit buffer length. The user exit returned data in the supplied exit buffer, but the length specified is greater than the length of the buffer. Message AMQ9190 is issued giving more details, and the channel stops. Response: Investigate why the user exit program set a data length that is not valid. AMQ9201 Allocate failed to host . Severity: 30 : Severe error Explanation: The attempt to allocate a conversation using to host was not successful. Response: The error may be due to an incorrect entry in the parameters contained in the channel definition to host . Correct the error and try again. If the error persists, record the error values and contact your systems administrator. The return code from the call was (X). It may be possible that the listening program at host is not running. If this is the case, perform the relevant operations to start the listening program for protocol and try again. AMQ9202 Remote host not available, retry later. Severity: 30 : Severe error Explanation: The attempt to allocate a conversation using to host was not successful. However the error may be a transitory one and it may be possible to successfully allocate a conversation later. Response: Try the connection again later. If the failure persists, record the error values and contact your systems administrator. The return code from is (X). The reason for the failure may be that this host cannot reach the destination host. It may also be possible that the listening program at host was not running. If this is the case, perform the relevant operations to start the listening program, and try again. AMQ9203 A configuration error for occurred. Severity: 30 : Severe error Explanation: Error in configuration for communications to host . Allocation of a conversation to host was not possible. Response: The configuration error may be one of the following: 1.If the communications protocol is LU 6.2, it may be that one of the transmission parameters (Mode, or TP Name) is incorrect. Correct the error and try again. The mode name should be the same as the mode defined on host . The TP name on should be defined. 2.If the communications protocol is LU 6.2, it may be that an LU 6.2 session has not been established. Contact your systems administrator. 3.If the communications protocol is TCP/IP, it may be that the host name specified is incorrect. Correct the error and try again. 4.If the communications protocol is TCP/IP, it may be that the host name specified cannot be resolved to a network address. The host name may not be in the nameserver. The return code from the call was (X). Record the error values and tell the system administrator. AMQ9204 Connection to host rejected. Severity: 30 : Severe error Explanation: Connection to host over was rejected. Response: The remote system may not be configured to allow connections from this host. Check the listener program has been started on host . If the conversation uses LU 6.2, it is possible that either the User ID or Password supplied to the remote host is incorrect. If the conversation uses TCP/IP, it is possible that the remote host does not recognize the local host as a valid host. The return code from the call was X(). Record the error values and tell the systems administrator. AMQ9205 The host name supplied is not valid. Severity: 30 : Severe error Explanation: The supplied host name could not be resolved into a network address. Either the name server does not contain the host, or the name server was not available. Response: Check the configuration on your host. AMQ9206 Error sending data to host . Severity: 30 : Severe error Explanation: An error occurred sending data over to . This may be due to a communications failure. Response: The return code from the call was X(). Record these values and tell your systems administrator. AMQ9207 The data received from host is not valid. Severity: 30 : Severe error Explanation: Incorrect data format received from host over . It may be that an unknown host is attempting to send data. An FFST file has been generated containing the invalid data received. Response: Tell the systems administrator. AMQ9208 Error on receive from host . Severity: 30 : Severe error Explanation: An error occurred receiving data from over . This may be due to a communications failure. Response: The return code from the call was (X). Record these values and tell the systems administrator. AMQ9209 Connection to host closed. Severity: 30 : Severe error Explanation: An error occurred receiving data from over . The connection to the remote host has unexpectedly terminated. Response: Tell the systems administrator. AMQ9210 Remote attachment failed. Severity: 30 : Severe error Explanation: There was an incoming attachment from a remote host, but the local host could not complete the bind. Response: The return code from the call was (X). Record these values and tell the systems administrator who should check the configuration. AMQ9211 Error allocating storage. Severity: 30 : Severe error Explanation: The program was unable to obtain enough storage. Response: Stop some programs which are using storage and retry the operation. If the problem persists contact your systems administrator. AMQ9212 A TCP/IP socket could not be allocated. Severity: 30 : Severe error Explanation: A TCP/IP socket could not be created, possibly because of a storage problem. Response: The return code from the call was (X). Try the program again. If the failure persists, record the error values and tell the systems administrator. AMQ9213A communications error for occurred. Severity: 30 : Severe error Explanation: An unexpected error occurred in communications. Response: The return code from the call was (X). Record these values and tell the systems administrator. AMQ9214 Attempt to use an unsupported communications protocol. Severity: 30 : Severe error Explanation: An attempt was made to use an unsupported communications protocol type . Response: Check the channel definition file. It may be that the communications protocol entered is not a currently supported one. AMQ9215 Communications subsystem unavailable. Severity: 30 : Severe error Explanation: An attempt was made to use the communications subsystem, but it has not been started. Response: Start the communications subsystem, and rerun the program. AMQ9216 Usage: [-m QMgrName] [-n TPName] Severity: 20 : Error Explanation: Values passed to the responder channel program are not valid. The parameters that are not valid are as follows :- The responder channel program exits. Response: Correct the parameters passed to the channel program and retry the operation. AMQ9216 (AIX)Usage: [-m QMgrName] Severity: 20 : Error Explanation: Values passed to the responder channel program are not valid. The parameters that are not valid are as follows :- The responder channel program exits. Response: Correct the parameters passed to the channel program and retry the operation. AMQ9216 (HP-UX)Usage: [-m QMgrName] Severity: 20 : Error Explanation: Values passed to the responder channel program are not valid. The parameters that are not valid are as follows :- The responder channel program exits. Response: Correct the parameters passed to the channel program and retry the operation. AMQ9217 The TCP/IP listener program could not be started. Severity: 30 : Severe error Explanation: An attempt was made to start a new instance of the listener program, but the program was rejected. Response: The failure could be because either the subsystem has not been started (in this case you should start the subsystem), or there are too many programs waiting (in this case you should try to start the listener program later). AMQ9218 The listener program could not bind to port number . Severity: 30 : Severe error Explanation: An attempt to bind the socket to the listener port was unsuccessful. Response: The failure could be due to another program using the same port number. The return code from the call for port was . Record these values and tell the systems administrator. AMQ9219 The TCP/IP listener program could not create a new connection for the incoming conversation. Severity: 30 : Severe error Explanation: An attempt was made to create a new socket because an attach request was received, but an error occurred. Response: The failure may be transitory, try again later. If the problem persists, record the return code and tell the systems administrator. It may be necessary to free some jobs, or restart the communications system. AMQ9220 The communications program could not be loaded. Severity: 30 : Severe error Explanation: The attempt to load the library or procedure failed with error code . Response: Either the library must be installed on the system or the environment changed to allow the program to locate it. AMQ9221 Unsupported protocol was specified. Severity: 30 : Severe error Explanation: The specified value of was not recognized as one of the protocols supported. Response: Correct the parameter and retry the operation. AMQ9222 Cannot find the configuration file. Severity: 10 : Warning Explanation: The configuration file cannot be found. This file contains default definitions for communication parameters. Default values will be used. Response: None. AMQ9223 Enter a protocol type. Severity: 30 : Severe error Explanation: The operation you are performing requires that you enter the type of protocol. Response: Add the protocol parameter and retry the operation. AMQ9224 Unexpected token detected. Severity: 30 : Severe error Explanation: On line of the INI file, keyword was read when a keyword was expected. Response: Correct the file and retry the operation. AMQ9224 (Windows)Unexpected token detected. Severity: 30 : Severe error Explanation: Keyword was read when a keyword was expected. Response: Correct the configuration data and retry the operation. AMQ9225 File syntax error. Severity: 30 : Severe error Explanation: A syntax error was detected on line while processing the INI file. Response: Correct the problem and retry the operation. AMQ9225 (Windows)File syntax error. Severity: 30 : Severe error Explanation: A syntax error was detected while processing the configuration data. Response: Correct the problem and retry the operation. AMQ9226 Usage: [-m QMgrName] -t (TCP | LU62 | NETBIOS | SPX) [ProtocolOptions] Severity: 10 : Warning Explanation: Values passed to the listener program were invalid. The parameter string passed to this program is as follows: [-m QMgrName] ( -t TCP [-p Port] | -t LU62 [-n TPName] | -t NETBIOS [-l LocalName] [-e Names] [-s Sessions] [-o Commands] [-a Adaptor] | -t SPX [-x Socket]) Default values will be used for parameters not supplied. Response: Correct the parameters passed to the listener program and retry the operation. AMQ9226 (AIX)Usage: [-m QMgrName] -t TCP [ProtocolOptions] Severity: 10 : Warning Explanation: Values passed to the listener program were invalid. The parameter string passed to this program is as follows: [-m QMgrName] -t TCP [-p Port] Default values will be used for parameters not supplied. Response: Correct the parameters passed to the listener program and retry the operation. AMQ9226 (Unix)Usage: [-m QMgrName] -t TCP [ProtocolOptions] Severity: 10 : Warning Explanation: Values passed to the listener program were invalid. The parameter string passed to this program is as follows: [-m QMgrName] -t TCP [-p Port] Default values will be used for parameters not supplied. Response: Correct the parameters passed to the listener program and retry the operation. AMQ9227 local host name not provided. Severity: 30 : Severe error Explanation: A name is required for the process to register with the network. Response: Add a local name to the configuration file and retry the operation. AMQ9228 The responder program could not be started. Severity: 30 : Severe error Explanation: An attempt was made to start an instance of the responder program, but the program was rejected. Response: The failure could be because either the subsystem has not been started (in this case you should start the subsystem), or there are too many programs waiting (in this case you should try to start the responder program later). The reason code was . AMQ9229 The application has been ended. Severity: 30 : Severe error Explanation: You have issued a request to end the application. Response: None. AMQ9230 An unexpected event occurred. Severity: 30 : Severe error Explanation: During the processing of network events, an unexpected event occurred. Response: None. AMQ9231 The supplied parameter is not valid. Severity: 30 : Severe error Explanation: The value of the parameter has the value . This value has either not been specified or has been specified incorrectly. Response: Check value of the parameter and correct it if necessary. If the fault persists, record the return code (,) and and tell the systems administrator. AMQ9232 No specified Severity: 30 : Severe error Explanation: The operation requires the specification of the field. Response: Specify the and retry the operation. AMQ9233 Error creating thread. Severity: 30 : Severe error Explanation: The process attempted to create a new thread. The most likely cause of this problem is a shortage of an operating system resource (for example: memory). Use any previous FFSTs to determine the reason for the failure. The WebSphere MQ internal return code describing the reason for the failure is . Response: Contact the systems administrator. If the problem persists contact your IBM support center. AMQ9235 The supplied local communications address cannot be resolved. Severity: 30 : Severe error Explanation: The local communications address (LOCLADDR) value cannot be resolved into an IP address. Response: Enter a local communications address value which can be resolved into an IP address, and try again. AMQ9236 The supplied Partner LU was invalid. Severity: 30 : Severe error Explanation: The Partner LU name was invalid. Response: Either the Partner LU name was entered incorrectly or it was not in the communications configuration. Correct the error and try again. AMQ9237 A configuration error for occurred. Severity: 30 : Severe error Explanation: Allocation of a conversation to host was not possible. The configuration error may be one of the following: 1. It may be that one of the transmission parameters (Mode, or TP Name) was incorrect. Correct the error and try again. The mode name should be the same as the mode defined on host . The TP name on should be defined. 2. It may be that an LU 6.2 session has not been established. Contact your systems administrator. The return code from is with associated . Response: Record the error values and tell the system administrator. AMQ9238 A communications error for occurred. Severity: 30 : Severe error Explanation: An unexpected error occurred in communications. Response: The return code from the call was with associated . AMQ9239Usage: [-m QMgrName] -n TpName -g Gateway-name Severity: 10 : Warning Explanation: Values passed to the listener program were invalid. The parameter string passed to this program is as follows, default values being used for parameters not supplied: [-m QMgrName] -n TpName -g Gateway-name Response: Correct the parameters passed to the listener program and retry the operation. AMQ9240 An SPX socket was already in use. Severity: 30 : Severe error Explanation: The Listener received return code when attempting to open socket . Response: The specified socket is already in use by another process. To use another socket specify another socket on the command line to RUNMQLSR or update the default in the qm.ini file. AMQ9240 (iSeries)An SPX socket was already in use. Severity: 30 : Severe error Explanation: The Listener received return code when attempting to open socket . Response: The specified socket is already in use by another process. To use another socket specify another socket on the command line to STRMQMLSR or update the default in the qm.ini file. AMQ9240 (Windows)An SPX socket was already in use. Severity: 30 : Severe error Explanation: The listener received return code when attempting to open socket . Response: The specified socket is already in use by another process. To use another socket, specify a different socket on the command line to the runmqlsr command, or update the default in the configuration data. AMQ9241 SPX is not available. Severity: 30 : Severe error Explanation: WebSphere MQ received return code when attempting to start SPX communications. Response: Ensure that IPX/SPX support is installed on the machine and that it is started before trying to start a WebSphere MQ SPX channel. AMQ9242 SPX resource problem. Severity: 30 : Severe error Explanation: WebSphere MQ received return code when attempting to start SPX communications, indicating a resource problem. Response: Ensure that sufficient IPX/SPX resources are available before commencing communications over IPX/SPX. AMQ9243 The queue manager does not exist. Severity: 30 : Severe error Explanation: You tried to perform an action against a queue manager that does not exist. You may have specified the wrong queue manager name. Response: If you specified the wrong name, correct the name and submit the command again. If the queue manager does not exist, create the queue manager and submit the command again. AMQ9244The default queue manager does not exist. Severity: 30 : Severe error Explanation: You tried to perform an action against a queue manager that does not exist. Response: Create the default queue manager and submit the command again. AMQ9245 (Windows)Unable to obtain account details for channel MCA user ID. Severity: 10 : Warning Explanation: WebSphere MQ was unable to obtain the account details for MCA user ID . This user ID was the MCA user ID for channel on queue manager and may have been defined in the channel definition, or supplied either by a channel exit or by a client. Response: Ensure that the user ID is correct and that it is defined on the Windows local system, the local domain or on a trusted domain. For a domain user ID, ensure that all necessary domain controllers are available. AMQ9246The TCP/IP listener on port could not start a new channel. Severity: 30 : Severe error Explanation: An attempt has been made to connect to the queue manager by starting a new channel within the TCP/IP listener which is listening on port . The maximum socket number which can be used by a channel running on this listener is . A socket number beyond this maximum was allocated for the new channel. This connection attempt has been rejected, but the listener continues to listen for further connection requests. The socket number allocated for a new listener channel is related to the number of channels currently running within that listener process. The problem has arisen because too many channels are directed at the port on which this listener is listening. Response: An extra listener process should be started to listen on a different port. Some of the channels to the queue manager should be redirected from the port on which the existing listener is listening to the new port. AMQ9247SSPI Security: bad return from SSPI call. Severity: 30 : Severe error Explanation: Channel has been closed because the SSPI channel exit received a bad return code from SSPI. Response: Consult the appropriate SSPI manuals to find out the meaning of status on call , and correct the error. AMQ9248The program could not bind to a socket. Severity: 30 : Severe error Explanation: The attempt to bind to socket failed with return code . The failing call was . The most likely cause of this problem is incorrect configuration of the local address or incorrect start and end port parameters. Response: Contact the system administrator. If the problem persists contact your IBM support center. AMQ9255Listener already running. Severity: 30 : Severe error Explanation: The request to start the WebSphere MQ listener failed because there is already a listener running against the specified network resources. Response: None. AMQ9259Connection timed out from host . Severity: 30 : Severe error Explanation: A connection from host over timed out. Response: Check to see why data was not received in the expected time. Correct the problem. Reconnect the channel, or wait for a retrying channel to reconnect itself. AMQ9401Channel autodefined. Severity: 0 : Information Explanation: Channel which did not previously exist has been autodefined. Response: None. AMQ9402Autodefinition exit for Channel failed to load. Severity: 30 : Severe error Explanation: Autodefinition of Channel failed because would not load. Response: Ensure that the user exit is specified correctly in the queue manager definition, and that the user exit program is correct and available. AMQ9403Autodefinition of Channel suppressed by user exit. Severity: 30 : Severe error Explanation: Autodefinition exit for Channel returned a failure code. Response: None. AMQ9404REFRESH CLUSTER REPOS(YES) command processed, cluster , objects changed. Severity: 0 : Information Explanation: The queue manager successfully processed a REFRESH CLUSTER command with the REPOS(YES) option for the indicated cluster. Response: None. AMQ9405FORCEREMOVE QUEUES(YES) command processed, cluster target . Severity: 0 : Information Explanation: The repository queue manager successfully processed a RESET ACTION(FORCEREMOVE) command with the QUEUES(YES) option for the indicated cluster and target queue manager. Response: None. AMQ9406REFRESH CLUSTER REPOS(YES) command failed, this queue manager is a full repository for cluster . Severity: 30 : Severe error Explanation: The repository queue manager could not process a REFRESH CLUSTER command with the REPOS(YES) option for the indicated cluster, because the local queue manager provides full repository management services for the cluster. The command is ignored. Response: Either 1) Reissue the command without REPOS(YES), or 2) Issue the command on a queue manager which is not a full repository, or 3) Change this queue manager definition so that it is not a full repository. AMQ9407Cluster queue is defined inconsistently. Severity: 10 : Warning Explanation: The definition of cluster queue on the queue manager with UUID has different DEFPRTY, DEFPSIST and DEFBIND values from the definition of the same cluster queue on the queue manager with UUID . Both definitions now exist in the local repository. All definitions of the same cluster queue should be identical. In particular, problems arise if your applications rely on a queue default value which is defined inconsistently to determine messaging behavior. This applies, for example, if the applications open a cluster queue with option MQOO_BIND_AS_Q_DEF. If different instances of the queue have different DEFBIND values the behavior of the message transfer differs depending on which instance of the queue is selected when it is opened. In general the instance selected varies across opens. Response: For each inconsistency decide which of the values is the correct one. Alter the definitions of cluster queue so that all definitions have correct DEFPRTY, DEFPSIST and DEFBIND values. AMQ9408BIND_ON_OPEN messages for channel to dead-letter queue. Severity: 0 : Information Explanation: The remote CLUSRCVR for channel was deleted while undelivered BIND_ON_OPEN messages associated with that channel existed on the local SYSTEM.CLUSTER.TRANSMIT.QUEUE. These messages could not be allocated to another channel because they were put BIND_ON_OPEN, but were very unlikely to ever flow along the channel with which they were associated as this has now been deleted. An attempt has therefore been made to move them from the transmission queue to the local dead-letter queue. The MQDLH reason is MQFB_BIND_OPEN_CLUSRCVR_DEL. Note that any internal WebSphere MQ Clustering messages for the deleted channel will also have been removed from the SYSTEM.CLUSTER.TRANSMIT.QUEUE (these are discarded) so the current depth of the queue may have decreased by more than the number of user messages moved to the dead-letter queue. Response: Examine the contents of the dead-letter queue. Each message is contained in an MQDLH structure that includes the reason why it was written and where it was originally addressed. Also look at previous error messages to see if the attempt to put messages to the dead-letter queue failed. AMQ9409Repository manager ended abnormally. Severity: 30 : Severe error Explanation: The repository manager ended abnormally. Response: Look at previous error messages for the repository manager in the error files to determine the cause of the failure. AMQ9410Repository manager started Severity: 0 : Information Explanation: The repository manager started successfully. Response: None. AMQ9411Repository manager ended normally. Severity: 0 : Information Explanation: The repository manager ended normally. Response: None. AMQ9412Repository command received for . Severity: 30 : Severe error Explanation: The repository manager received a command intended for some other queue manager, whose identifier is . The command was sent by the queue manager with identifier . Response: Check the channel and cluster definitions of the sending queue manager. AMQ9413Repository command format error, command code Severity: 30 : Severe error Explanation: An internal error has occurred. Response: Collect the items listed in the 'Problem determination' section of the System Administration manual and contact your IBM support center. AMQ9415Repository command unexpected, command code , cluster object , sender Severity: 30 : Severe error Explanation: An internal error has occurred. Response: Collect the items listed in the 'Problem determination' section of the System Administration manual and contact your IBM support center. AMQ9415 (iSeries)An internal error has occurred. Severity: 30 : Severe error Explanation: Repository command unexpected, command code , cluster object , sender Response: Collect the items listed in the 'Problem determination' section of the System Administration manual and contact your IBM support center. AMQ9416Repository command processing error, RC=, command code , cluster object , sender . Severity: 30 : Severe error Explanation: An internal error has occurred. Response: Collect the items listed in the 'Problem determination' section of the System Administration manual and contact your IBM support center. AMQ9416 (iSeries)An internal error has occurred. Severity: 30 : Severe error Explanation: Repository command processing error, RC=, command code , cluster object , sender . Response: Collect the items listed in the 'Problem determination' section of the System Administration manual and contact your IBM support center. AMQ9417Manually defined CLUSSDR channels have been forcibly removed. Severity: 0 : Information Explanation: The administrator has asked for the queue manager to be deleted, or forcibly removed, but has not yet deleted the manually defined CLUSSDR channels to . The auto-defined channels to have been deleted, but continues to receive updates until the manually defined CLUSSDR channels have been deleted. Response: Delete the manually defined CLUSSDR channels to . AMQ9418Only one repository for cluster . Severity: 0 : Information Explanation: The queue manager has received information about a cluster for which it is the only repository. Response: Alter the REPOS or REPOSNL attribute of the queue manager, that is to have the second full repository for the cluster, to specify the cluster name. AMQ9419No cluster-receiver channels for cluster Severity: 0 : Information Explanation: The repository manager has received information about a cluster for which no cluster-receiver channels are known. Response: Define cluster-receiver channels for the cluster on the local queue manager. AMQ9420No repositories for cluster . Severity: 0 : Information Explanation: The queue manager has received information about a cluster for which no repositories are known. Response: Alter the REPOS or REPOSNL attribute of the queue manager, that is to have a full repository for the cluster, to specify the cluster name. AMQ9421Invalid cluster record action code detected Severity: 30 : Severe error Explanation: An invalid record was read from the SYSTEM.CLUSTER.REPOSITORY.QUEUE. An FFST record has been generated containing the invalid record. was Response: Collect the items listed in the Problem Determination section of the System Administration manual and contact your IBM support center. AMQ9422Repository manager error, RC= Severity: 30 : Severe error Explanation: An internal error has occurred. Response: Collect the items listed in the 'Problem determination' section of the System Administration manual and contact your IBM support center. AMQ9425An internal error has occurred. Severity: 30 : Severe error Explanation: Repository command merge error, command code , cluster object , sender Response: Collect the items listed in the 'Problem determination' section of the System Administration manual and contact your IBM support center. AMQ9426Repository command recipient unknown. Severity: 30 : Severe error Explanation: The repository manager tried to send a command to another queue manager using channel . The recipient queue manager, whose identifier is , could not be found. Command code . Response: Check the channel and cluster definitions of the sending and receiving queue managers. AMQ9427CLUSSDR channel does not point to a repository queue manager. Severity: 30 : Severe error Explanation: A CLUSSDR channel must point to a queue manager that hosts repositories for all clusters of which the channel is a member. In addition, the CLUSRCVR for the channel must be a member of all the same clusters as the CLUSSDR channel. The queue manager pointed to by CLUSSDR channel does not meet these criteria for cluster . The remote queue manager has a QMID of . Response: Check the definitions on the local and remote queue managers to ensure that the CLUSSDR channel points to a queue manager that hosts a repository for the cluster, and that the CLUSRCVR for the channel is a member of the cluster. AMQ9428Unexpected publication of a cluster queue object received. Severity: 30 : Severe error Explanation: The local queue manager has received a publication of a cluster queue object from a remote queue manager on cluster . The local queue manager discards the request because it does not host a repository for cluster and has not subscribed to the published object. The remote CLUSSDR channel used to access the local queue manager has a channel name of and the remote queue manager has a QMID of . Response: Check the definitions on the local and remote queue managers to ensure that the CLUSSDR channel points to a repository queue manager for the cluster. AMQ9429Unexpected publication of a cluster queue deletion received. Severity: 30 : Severe error Explanation: The local queue manager has received a publication of a cluster queue deletion from a remote queue manager on cluster . The local queue manager discards the request because it does not host a repository for cluster and has not subscribed to the published object. The remote CLUSSDR channel used to access the local queue manager has a channel name of and the remote queue manager has a QMID of . Response: Check the definitions on the local and remote queue managers to ensure that the CLUSSDR channel points to a repository queue manager for the cluster. AMQ9430Unexpected cluster queue manager publication received. Severity: 30 : Severe error Explanation: The local queue manager has received a cluster queue manager publication on cluster . The local queue manager should not have received the publication because it does not host a repository for cluster , it has not subscribed to information concerning the published object, and the published object does not match any of its CLUSSDRs. The queue manager that sent the publication to the local queue manager has QMID (note that this is not necessarily the queue manager which originated the publication). CLUSSDR channel was used to send the publication. Response: Check the CLUSSDR definition on the sending queue manager to ensure that it points to a repository queue manager for the cluster. AMQ9431Remote queue manager no longer hosts a repository for cluster Severity: 0 : Information Explanation: The local queue manager has received a message from remote queue manager QMID indicating that it no longer hosts a repository for cluster . CLUSSDR channel is altered so that it can no longer be used to access queue manager within cluster . If the local queue manager does not host a repository for cluster the relevant subscriptions and publications are remade if possible. Response: None. AMQ9432Query received by a non-repository queue manager Severity: 30 : Severe error Explanation: The local queue manager has received a query from a remote queue manager on cluster . The local queue manager discards the query because it does not host a repository for cluster . The remote CLUSSDR channel used to access the local queue manager has a channel name of and the remote queue manager has a QMID of . Response: Check the definitions on the local and remote queue managers to ensure that the CLUSSDR channel points to a repository queue manager for the cluster. AMQ9433CLUSRCVR must be in the same cluster as its matching CLUSSDR. Severity: 30 : Severe error Explanation: CLUSRCVR channel is not defined as a member of cluster . The local queue manager has received a command that indicates that CLUSSDR channel on the remote queue manager with QMID is defined as a member of cluster . Response: Alter the CLUSRCVR or CLUSSDR definitions for channel , so that they are both members of the same cluster. AMQ9434Unrecognized message on . Severity: 30 : Severe error Explanation: The repository manager found a message on one of its queues having, either a format that could not be recognized, or that did not come from a queue manager or repository manager. The message was put on the dead-letter queue. Response: Examine the message on the dead-letter queue to determine the originator of the message. AMQ9435Unable to put repository manager message. Severity: 30 : Severe error Explanation: The repository manager tried to send a message to the SYSTEM.CLUSTER.COMMAND.QUEUE on another queue manager whose identifier is , but the MQPUT call was unsuccessful. MQCC=, MQRC=. Processing continues, but the repository information may be out of date. Response: Refer to the Application Programming Reference manual for information about MQCC and MQRC . Check the channel and cluster definitions on the local and target queue managers, and ensure that the channels between them are running. When the problem is corrected, the repository information will normally be updated automatically. The REFRESH CLUSTER command can be used to ensure that the repository information is up to date. AMQ9436Unable to send repository manager message. Severity: 30 : Severe error Explanation: The repository manager tried to send a message to the SYSTEM.CLUSTER.COMMAND.QUEUE on a queue manager that has the full repository for the specified cluster(), but the MQPUT call was unsuccessful. MQCC=, MQRC=. Processing continues, but repository information may be out of date. Response: Refer to the Application Programming Reference manual for information about MQCC and MQRC . Check the channel and cluster definitions on the local and target queue managers, and ensure that the channels between them are running. When the problem is corrected, the repository information will normally be updated automatically. The REFRESH CLUSTER command can be used to ensure that the repository information is up to date. AMQ9437Unable to commit repository changes. Severity: 30 : Severe error Explanation: The repository manager tried to commit some updates to the repository but was unsuccessful. Processing continues, but repository information may be out of date. Response: If this occurs when the repository manager is stopping, this message can be ignored, because the repository information will normally be updated automatically when the repository manager is restarted. If there is an isolated occurrence at other times, use the REFRESH CLUSTER command to bring the repository information up to date. If the problem persists, contact your IBM support center for assistance. AMQ9438CONNAME could not be discovered for CLUSRCVR . Severity: 30 : Severe error Explanation: TCP/IP CLUSRCVR was validly specified with a blank or absent CONNAME parameter. However when the repository process, amqrrmfa, attempted to obtain the CONNAME (IP address) for itself it was unable to. If there is an existing matching CLUSRCVR object in the cache its CONNAME is used. The CONNAME used was . Response: Check the error log for a message arising from an associated TCP/IP call (gethostname, gethostbyname or inet_ntoa). Pass all the error information to your systems administrator. AMQ9439Repository corruption: bad CLQMGR object for channel . Severity: 30 : Severe error Explanation: An internal error has occurred. Response: Collect the items listed in the 'Problem determination' chapter in the System Administration guide and contact your IBM support center. AMQ9440Reset command failed. Severity: 0 : Information Explanation: Reset Cluster() Qmname() command failed. To issue this command, queue manager must be a repository for cluster . Alter the queue manager attributes Repos, or Reposnl, to include cluster and retry the command. Response: None. AMQ9441Reset command processed. Severity: 0 : Information Explanation: The reset Cluster() Qmname() command has processed on this repository and other queue managers have been sent notification. Response: None. AMQ9442Refresh Cluster command processed. Severity: 0 : Information Explanation: The Refresh Cluster() command caused objects to be refreshed and objects to be republished. Response: None. AMQ9443Suspend Qmgr Cluster command processed. Severity: 0 : Information Explanation: The Suspend Qmgr Cluster command completed. objects suspended.I n the case of a name list the cluster name is the first name in the list. Response: None. AMQ9444Resume Qmgr Cluster command processed. Severity: 0 : Information Explanation: The Resume Qmgr Cluster() command completed. objects resumed. In the case of a name list the cluster name is the first name in the list. Response: None. AMQ9445Error creating channel . Severity: 30 : Severe error Explanation: Channel tried to replace itself by creating channel . The attempt to create the channel was unsuccessful for the following reason: "". A previous message may give further information. Response: Rectify the problem which prevented successful creation of channel . Restart channel . AMQ9446Error deleting channel . Severity: 30 : Severe error Explanation: Channel tried to delete itself after creating channel to replace it. The attempt to delete the channel was unsuccessful for the following reason: "". Response: If channel still exists rectify the problem which prevented its deletion and then manually delete the channel. AMQ9447Unable to backout repository changes. Severity: 30 : Severe error Explanation: Following an error, the repository manager tried to backout some updates to the repository, but was unsuccessful. The repository manager terminates. Response: If the repository manager subsequently restarts successfully, this message can be ignored. If the repository manager does not restart, contact your IBM support center for assistance. AMQ9448Repository manager stopping because of errors. Restart in seconds. Severity: 30 : Severe error Explanation: A severe error, as reported in the preceding messages, occurred during repository manager processing. The repository manager was unable to continue and terminates. The repository manager will try to restart after the specified interval. Response: Correct the problem reported in the preceding messages. AMQ9449Repository manager restarted. Severity: 0 : Information Explanation: The repository manager restarted successfully following an error. Response: None. AMQ9450Usage: [-m QMgrName] -f OutputFile [-v OutputFileVersion] Severity: 10 : Warning Explanation: Values passed to the channel table writer program were invalid. The parameter string passed to this program is as follows: [-m QMgrName] -f OutputFile [-v OutputFileVersion] where OutputFileVersion can be either 2 or 5 (5 is the default) Default values will be used for parameters not supplied. Response: Correct the parameters passed to the channel table writer program and retry the operation. AMQ9453FORCEREMOVE command failed, cluster target is not unique. Severity: 0 : Information Explanation: The repository queue manager could not process a RESET ACTION(FORCEREMOVE) command for the indicated cluster and target queue manager, because there is more than one queue manager with the specified name in the cluster. The command is ignored. Response: Reissue the command specifying the identifier (QMID) of the queue manager to be removed, rather than its name. AMQ9455FORCEREMOVE command failed, cluster , target , not found. Severity: 0 : Information Explanation: The repository queue manager could not process a RESET ACTION(FORCEREMOVE) command for the indicated cluster and target queue manager, because no information about that queue manager was found in the local repository. The command is ignored. Response: Reissue the command, specifying the correct queue manager name or identifier. AMQ9456Update not received for queue , queue manager from full repository for cluster . Severity: 0 : Information Explanation: The repository manager detected a queue that has been used in the last 30 days for which updated information should have been sent from a full repository. However, this has not occurred. The repository manager will keep the information about this queue for a further 60 days. Response: If the queue is still required, check that: 1) The cluster channels to and from the full repository and the queue manager that hosts the queue, are able to run. 2) The repository managers running on these queue managers have not ended abnormally. AMQ9456 (iSeries)Update not received from full repository. Severity: 0 : Information Explanation: Update not received for queue , queue manager from full repository for cluster . The repository manager detected a queue that has been used in the last 30 days for which updated information should have been sent from a full repository. However, this has not occurred. The repository manager will keep the information about this queue for a further 60 days. Response: If the queue is still required, check that: 1) The cluster channels to and from the full repository and the queue manager that hosts the queue, are able to run. 2) The repository managers running on these queue managers have not ended abnormally. AMQ9457Repository available, cluster , channel , sender . Severity: 0 : Information Explanation: The repository queue manager received a command from another queue manager, whose identifier is , reporting that it is again a repository for cluster . The cluster-sender channel is changed so that it can be used to access the other queue manager in relation to the the cluster. Response: None. AMQ9491Transmission Queue set to NOSHARE. Severity: 20 : Error Explanation: The channel on queue manager cannot start because this queue manager has a setting for PipeLineLength greater than 1, and so multiple threads will run in this channel's MCA. Only the first thread would be able to open the Transmission Queue because it is set to be non-shareable. Response: Check the definition of the Transmission Queue on queue manager and set it to be SHARE instead of NOSHARE. Alternatively, you can set all channels on this queue manager to use only a single thread, by using the PipeLineLength parameter. AMQ9492The responder program encountered an error. Severity: 30 : Severe error Explanation: The responder program was started but detected an error. Response: Look at previous error messages in the error files to determine the error encountered by the responder program. AMQ9494A protocol error was detected for channel . Severity: 30 : Severe error Explanation: During communications with the remote queue manager, a TCP/IP read and receive call returned EINTR, indicating that it had been interrupted. Immediately after this the channel program detected a protocol error. The failure type was with associated data of . Response: If you are running an AIX client you will avoid problems arising from EINTRs on TCP/IP reads, by writing your application so that system calls interrupted by signals are restarted. You must establish the signal handler with sigaction(2) and set the SA_RESTART flag in the sa_flags field of the new action structure. If you are running on a platform other than AIX, an AIX server, or an AIX client with an application that adheres to the restart guidelines provided above, contact the systems administrator who should examine the error logs to determine the cause of the failure. AMQ9495The CLWL exit is inconsistent with a dynamic cache. Severity: 30 : Severe error Explanation: When the CLWL exit was called for the ExitReason MQXR_INIT, the value was returned in the ExitResponse2 field. This indicates the CLWL exit is incompatible with the Queue Manager cache type which is dynamic. Either change the Queue Manager cache type to static (using the Tuning Parameter, ClusterCacheType=STATIC) or rewrite the CLWL exit to be compatible with a dynamic cache". The CLWL exit has been suppressed. Response: None. AMQ9496Channel ended by a remote exit. Severity: 30 : Severe error Explanation: Channel program was ended because the channel exit at the remote end requested it. Response: Examine the error logs at the remote end of the channel to see the reason why the remote exit ended the channel. AMQ9498The MQCD structure supplied was not valid. Severity: 30 : Severe error Explanation: The value of the field has the value . This value is invalid for the operation requested. Response: Change the parameter and retry the operation. AMQ9499A WebSphere MQ listener will end shortly. Severity: 0 : Information Explanation: One listener detected in the system is scheduled for shutdown. Response: None. AMQ9500No Repository storage Severity: 10 : Warning Explanation: An operation failed because there was no storage available in the repository. An attempt was made to allocate bytes from . Response: Reconfigure the Queue Manager to allocate a larger repository. AMQ9501Usage: [-m QMgrName] -c ChlName. Severity: 10 : Warning Explanation: Values passed to the channel program are not valid. The parameter string passed to this program is as follows :- [-m QMgrName] -c ChlName Default values will be used for parameters not supplied. Response: Correct the parameters passed to the Channel program and retry the operation. AMQ9502Type of channel not suitable for action requested. Severity: 30 : Severe error Explanation: The operation requested cannot be performed on channel . Some operations are only valid for certain channel types. For example, you can only ping a channel from the end sending the message. Response: Check whether the channel name is specified correctly. If it is check that the channel has been defined correctly. AMQ9503Channel negotiation failed. Severity: 30 : Severe error Explanation: Channel between this machine and the remote machine could not be established due to a negotiation failure. Response: Tell the systems administrator, who should attempt to identify the cause of the channel failure using problem determination techniques. For example, look for FFST files, and examine the error logs on the local and remote systems where there may be messages explaining the cause of failure. More information may be obtained by repeating the operation with tracing enabled. AMQ9504A protocol error was detected for channel . Severity: 30 : Severe error Explanation: During communications with the remote queue manager, the channel program detected a protocol error. The failure type was with associated data of . Response: Contact the systems administrator who should examine the error logs to determine the cause of the failure. AMQ9505Channel sequence number wrap values are different. Severity: 30 : Severe error Explanation: The sequence number wrap value for channel is , but the value specified at the remote location is . The two values must be the same before the channel can be started. Response: Change either the local or remote channel definitions so that the values specified for the message sequence number wrap values are the same. AMQ9506Message receipt confirmation failed. Severity: 30 : Severe error Explanation: Channel has ended because the remote queue manager did not accept the last batch of messages. Response: The error log for the channel at the remote site will contain an explanation of the failure. Contact the remote Systems Administrator to resolve the problem. AMQ9507Channel is currently in-doubt. Severity: 30 : Severe error Explanation: The requested operation cannot complete because the channel is in-doubt with host . Response: Examine the status of the channel, and either restart a channel to resolve the in-doubt state, or use the RESOLVE CHANNEL command to correct the problem manually. AMQ9508Program cannot connect to the queue manager. Severity: 30 : Severe error Explanation: The connection attempt to queue manager failed with reason code . Response: Ensure that the queue manager is available and operational. AMQ9509Program cannot open queue manager object. Severity: 30 : Severe error Explanation: The attempt to open either the queue or queue manager object on queue manager failed with reason code . Response: Ensure that the queue is available and retry the operation. AMQ9510Messages cannot be retrieved from a queue. Severity: 30 : Severe error Explanation: The attempt to get messages from queue on queue manager failed with reason code . Response: If the reason code indicates a conversion problem, for example MQRC_SOURCE_CCSID_ERROR, remove the message(s) from the queue. Otherwise, ensure that the required queue is available and operational. AMQ9511Messages cannot be put to a queue. Severity: 30 : Severe error Explanation: The attempt to put messages to queue on queue manager failed with reason code . Response: Ensure that the required queue is available and operational. AMQ9512Ping operation is not valid for channel . Severity: 30 : Severe error Explanation: Ping may only be issued for SENDER, SERVER or CLUSSDR channel types. Also, it may not be issued for an SSL channel on the HP-UX or Linux platforms. Response: If the local channel is a receiver channel, you must issue the ping from the remote queue manager. AMQ9513Maximum number of channels reached. Severity: 30 : Severe error Explanation: The maximum number of channels that can be in use simultaneously has been reached. The number of permitted channels is a configurable parameter in the queue manager configuration file. Response: Wait for some of the operating channels to close. Retry the operation when some channels are available. AMQ9514Channel is in use. Severity: 30 : Severe error Explanation: The requested operation failed because channel is currently active. Response: Either end the channel manually, or wait for it to close, and retry the operation. AMQ9515Channel changed. Severity: 10 : Warning Explanation: The statistics shown are for the channel requested, but it is a new instance of the channel. The previous channel instance has ended. Response: None. AMQ9516File error occurred. Severity: 30 : Severe error Explanation: The filesystem returned error code for file . Response: Record the name of the file and tell the systems administrator, who should ensure that file is correct and available. AMQ9516 (iSeries)File error occurred. Severity: 30 : Severe error Explanation: The filesystem returned error code for file . Response: Record the name of the file and tell the systems administrator, who should ensure that file is correct and available. AMQ9517File damaged. Severity: 30 : Severe error Explanation: The program has detected damage to the contents of file . Response: Record the values and tell the systems administrator who must restore a saved version of file . The return code was and the record length returned was . AMQ9518File not found. Severity: 30 : Severe error Explanation: The program requires that the file is present and available. Response: This may be caused by invalid values for the optional environment variables MQCHLLIB, MQCHLTAB or MQDATA. If these variables are valid or not set then record the name of the file and tell the systems administrator who must ensure that file is available to the program. AMQ9519Channel not found. Severity: 30 : Severe error Explanation: The requested operation failed because the program could not find a definition of channel . Response: Check that the name is specified correctly and the channel definition is available. AMQ9520Channel not defined remotely. Severity: 30 : Severe error Explanation: There is no definition of channel at the remote location. Response: Add an appropriate definition to the remote hosts list of defined channels and retry the operation. AMQ9521Host is not supported by this channel. Severity: 30 : Severe error Explanation: The connection across channel was refused because the remote host did not match the host specified in the channel definition. Response: Update the channel definition, or remove the explicit mention of the remote machine connection name. AMQ9522Error accessing the status table. Severity: 30 : Severe error Explanation: The program could not access the channel status table. Response: A value of was returned from the subsystem when an attempt was made to access the Channel status table. Contact the systems administrator, who should examine the log files to determine why the program was unable to access the status table. AMQ9523Remote host detected a protocol error. Severity: 30 : Severe error Explanation: During communications through channel , the remote queue manager channel program detected a protocol error. The failure type was with associated data of . Response: Tell the systems administrator, who should examine the error files to determine the cause of the failure. AMQ9524Remote queue manager unavailable. Severity: 30 : Severe error Explanation: Channel cannot start because the remote queue manager is not currently available. Response: Either start the remote queue manager, or retry the operation later. AMQ9525Remote queue manager is ending. Severity: 30 : Severe error Explanation: Channel is closing because the remote queue manager is ending. Response: None. AMQ9526Message sequence number error for channel . Severity: 30 : Severe error Explanation: The local and remote queue managers do not agree on the next message sequence number. A message with sequence number has been sent when sequence number was expected. Response: Determine the cause of the inconsistency. It could be that the synchronization information has become damaged, or has been backed out to a previous version. If the situation cannot be resolved, the sequence number can be manually reset at the sending end of the channel using the RESET CHANNEL command. AMQ9527Cannot send message through channel . Severity: 30 : Severe error Explanation: The channel has closed because the remote queue manager cannot receive a message. Response: Contact the systems administrator who should examine the error files of the remote queue manager, to determine why the message cannot be received, and then restart the channel. AMQ9528User requested closure of channel . Severity: 10 : Warning Explanation: The channel is closing because of a request by the user. Response: None. AMQ9529Target queue unknown on remote host. Severity: 30 : Severe error Explanation: Communication using channel has ended because the target queue for a message is unknown at the remote host. Response: Ensure that the remote host contains a correctly defined target queue, and restart the channel. AMQ9530Program could not inquire queue attributes. Severity: 30 : Severe error Explanation: The attempt to inquire the attributes of queue on queue manager failed with reason code . Response: Ensure that the queue is available and retry the operation. AMQ9531Transmission queue specification error. Severity: 30 : Severe error Explanation: Queue identified as a transmission queue in the channel definition is not a transmission queue. Response: Ensure that the queue name is specified correctly. If so, alter the queue usage parameter of the queue to that of a transmission queue. AMQ9532Program cannot set queue attributes. Severity: 30 : Severe error Explanation: The attempt to set the attributes of queue on queue manager failed with reason code . Response: Ensure that the queue is available and retry the operation. AMQ9533Channel is not currently active. Severity: 10 : Warning Explanation: The channel was not stopped because it was not currently active. If attempting to stop a specific instance of a channel by connection name or by remote queue manager name this message indicates that the specified instance of the channel is not running. Response: None. AMQ9534Channel is currently not enabled. Severity: 30 : Severe error Explanation: The channel program ended because the channel is currently not enabled. Response: Issue the START CHANNEL command to re-enable the channel. AMQ9535User exit not valid. Severity: 30 : Severe error Explanation: Channel program ended because user exit is not valid. Response: Ensure that the user exit is specified correctly in the channel definition, and that the user exit program is correct and available. AMQ9536Channel ended by an exit. Severity: 30 : Severe error Explanation: Channel program was ended by exit . Response: None. AMQ9537Usage: [-m QMgrName] [-q InitQ] Severity: 10 : Warning Explanation: Values passed to the Channel Initiator program are not valid. The parameters should be passed as follows: [-m QMgrName] [-q InitQ] Default values are used for parameters that are not supplied. Response: Correct the parameters passed to the program and retry the operation. AMQ9538Commit control error. Severity: 30 : Severe error Explanation: An error occurred when attempting to start commitment control. Either exception was received when querying commitment status, or commitment control could not be started. Response: Refer to the error log for other messages pertaining to this problem. AMQ9539No channels available. Severity: 30 : Severe error Explanation: The channel initiator program received a trigger message to start an MCA program to process queue . The program could not find a defined, available channel to start. Response: Ensure that there is a defined channel, which is enabled, to process the transmission queue. AMQ9540Commit failed. Severity: 30 : Severe error Explanation: The program ended because return code was received when an attempt was made to commit change to the resource managers. The commit ID was . Response: Tell the systems administrator. AMQ9541CCSID supplied for data conversion not supported. Severity: 30 : Severe error Explanation: The program ended because, either the source CCSID or the target CCSID is not valid, or is not currently supported. Response: Correct the CCSID that is not valid, or ensure that the requested CCSID can be supported. AMQ9542Queue manager is ending. Severity: 10 : Warning Explanation: The program will end because the queue manager is quiescing. Response: None. AMQ9543Status table damaged. Severity: 30 : Severe error Explanation: The channel status table has been damaged. Response: End all running channels and issue a DISPLAY CHSTATUS command to see the status of the channels. Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ9544Messages not put to destination queue. Severity: 10 : Warning Explanation: During the processing of channel one or more messages could not be put to the destination queue and attempts were made to put them to a dead-letter queue. The location of the queue is , where 1 is the local dead-letter queue and 2 is the remote dead-letter queue. Response: Examine the contents of the dead-letter queue. Each message is contained in a structure that describes why the message was put to the queue, and to where it was originally addressed. Also look at previous error messages to see if the attempt to put messages to a dead-letter queue failed. The program identifier (PID) of the processing program was . AMQ9545Disconnect interval expired. Severity: 0 : Information Explanation: Channel closed because no messages arrived on the transmission queue within the disconnect interval period. Response: None. AMQ9546Error return code received. Severity: 30 : Severe error Explanation: The program has ended because return code was returned from function Response: Correct the cause of the failure and retry the operation. AMQ9547Type of remote channel not suitable for action requested. Severity: 30 : Severe error Explanation: The operation requested cannot be performed because channel on the remote machine is not of a suitable type. For example, if the local channel is defined as a sender the remote machine must define its channel as either a receiver or requester. Response: Check that the channel name is specified correctly. If it is, check that the remote channel has been defined correctly. AMQ9548Message put to the 'dead-letter queue'. Severity: 10 : Warning Explanation: During processing a message has been put to the dead-letter queue. Response: Examine the contents of the dead-letter queue. Each message is contained in a structure that describes why the message was put to the queue, and to where it was originally addressed. AMQ9549Transmission Queue inhibited for MQGET. Severity: 20 : Error Explanation: An MQGET failed because the transmission queue had been previously inhibited for MQGET. Response: None. AMQ9550Channel program cannot be stopped at this time. Severity: 30 : Severe error Explanation: The channel program can not be terminated immediately but should end shortly. Response: If the channel does not end in a short time issue the STOP CHANNEL command again. AMQ9551Protocol not supported by remote host Severity: 30 : Severe error Explanation: The operation you are performing over Channel to the host at is not supported by the target host. Response: Check that the connection name parameter is specified correctly and that the levels of the products in use are compatible. AMQ9552Security flow not received. Severity: 30 : Severe error Explanation: During communications through channel the local security exit requested security data from the remote machine. The security data has not been received so the channel has been closed. Response: Tell the systems administrator who should ensure that the security exit on the remote machine is defined correctly. AMQ9553The function is not supported. Severity: 30 : Severe error Explanation: The function attempted is not currently supported on this platform. Response: None. AMQ9554User not authorized. Severity: 30 : Severe error Explanation: You are not authorized to perform the Channel operation. Response: Tell the systems administrator who should ensure that the correct access permissions are available to you, and then retry the operation. AMQ9555File format error. Severity: 30 : Severe error Explanation: The file does not have the expected format. Response: Ensure that the file name is specified correctly. AMQ9556Channel synchronization file missing or damaged. Severity: 30 : Severe error Explanation: The channel synchronization file is missing or does not correspond to the stored channel information for queue manager . Response: Rebuild the synchronization file using the rcrmqmobj command rcrmqmobj -t syncfile (-m q-mgr-name) AMQ9556 (iSeries)Channel synchronization file missing or damaged. Severity: 30 : Severe error Explanation: The channel synchronization file is missing or does not correspond to the stored channel information for queue manager . Response: Rebuild the synchronization file using the RCRMQMOBJ command. AMQ9557Queue Manager User ID initialization failed. Severity: 30 : Severe error Explanation: The call to initialize the User ID failed with CompCode and Reason . Response: Correct the error and try again. AMQ9558Remote Channel is not currently available. Severity: 30 : Severe error Explanation: The channel program ended because the channel is not currently available on the remote system. This could be because the channel is disabled or that the remote system does not have sufficient resources to run a further channel. Response: Check the remote system to ensure that the channel is available to run, and retry the operation. AMQ9560Rebuild Synchronization File - program started Severity: 0 : Information Explanation: Rebuilding the Synchronization file for Queue Manager . Response: None. AMQ9561Rebuild Synchronization File - program completed normally Severity: 0 : Information Explanation: Rebuild Synchronization File program completed normally. Response: None. AMQ9562Synchronization file in use. Severity: 30 : Severe error Explanation: The Synchronization file is in use and cannot be recreated. Response: Stop any channel activity and retry the rcrmqmobj command. AMQ9562 (iSeries)Synchronization file in use. Severity: 30 : Severe error Explanation: The Synchronization file is in use and cannot be recreated. Response: Stop any channel activity and retry the RCRMQMOBJ command. AMQ9563Synchronization file cannot be deleted Severity: 30 : Severe error Explanation: The filesystem returned error code for file . Response: Tell the systems administrator who should ensure that file is available and not in use. AMQ9564Synchronization File cannot be created Severity: 30 : Severe error Explanation: The filesystem returned error code for file . Response: Tell the systems administrator. AMQ9565No dead-letter queue defined. Severity: 30 : Severe error Explanation: The queue manager does not have a defined dead-letter queue. Response: Either correct the problem that caused the program to try and write a message to the dead-letter queue or create a dead-letter queue for the queue manager. AMQ9566Invalid MQSERVER value Severity: 30 : Severe error Explanation: The value of the MQSERVER environment variable was . The variable should be in the format 'ChannelName/Protocol/ConnectionName'. Response: Correct the MQSERVER value and retry the operation. AMQ9572Message header is not valid. Severity: 30 : Severe error Explanation: Channel is stopping because a message header is not valid. During the processing of the channel, a message was found that has a header that is not valid. The dead-letter queue has been defined as a transmission queue, so a loop would be created if the message had been put there. Response: Correct the problem that caused the message to have a header that is not valid. AMQ9573Maximum number of active channels reached. Severity: 30 : Severe error Explanation: There are too many channels active to start another. The current defined maximum number of active channels is . Response: Either wait for some of the operating channels to close or use the stop channel command to close some channels. Retry the operation when some channels are available. The maximum number of active channels is a configurable parameter in the queue manager configuration file. AMQ9574Channel can now be started. Severity: 30 : Severe error Explanation: Channel has been waiting to start, but there were no channels available because the maximum number of active channels was running. One, or more, of the active channels has now closed so this channel can start. AMQ9575DCE Security: failed to get the user's login name. Severity: 30 : Severe error Explanation: System call to get the login name of the user running WebSphere MQ client application process failed with error value . This occurred in security exit function create_cred. The exit will now attempt to open channel using the DCE default login context. Response: If you wish to run using the DCE default login context take no action. If you wish to run using the user's login name as the DCE security exit principal examine the documentation for the operating system on which you are running MQ clients and reconfigure the operating system as necessary to allow the call to succeed. AMQ9576DCE Security: an exit could not allocate memory. Severity: 30 : Severe error Explanation: A DCE exit was unsuccessful in obtaining the memory it needed. The failure occurred in exit function . Channel is closed. Response: Make more memory available to the WebSphere MQ system and restart the relevant channel. AMQ9577DCE security exit: no partner name. Severity: 30 : Severe error Explanation: Channel has not been opened because the DCE security exit which initiates the security context was not passed a valid partner name. When the DCE security exit is called to initiate the security context it is essential that the PartnerName field in the MQCXP structure contains a valid partner name. On this call it did not. This can arise as a result of a usage error, for instance only specifying the security exit on one end of the channel. The error was reported from security exit function savePartnerName. Response: Check your usage of the DCE security exit for errors, such as only specifying the exit in one of the matching channel definitions. Correct any errors found and retry. AMQ9578DCE Security: bad return from DCE call. Severity: 30 : Severe error Explanation: Channel has been closed because one of the DCE channel exits received a bad return code from DCE. Response: Consult the appropriate DCE manuals to find out the meaning of major_status and minor_status on call . Then rectify the error. The exit function name is . AMQ9579DCE Security: partner name does not match target. Severity: 30 : Severe error Explanation: The DCE Security exit was requested to perform a trusted channel check: target partner name was specified in the SCYDATA field of channel . The actual partner name associated with channel was , so the security exit suppressed the channel. Response: Examine the channel definition of channel and alter it so that the relevant name on the partner system matches that specified in the SCYDATA field. AMQ9580DCE Security: invalid message received. Severity: 30 : Severe error Explanation: An IBM-supplied DCE exit on channel received a message that was not generated by a matching exit, or was not the expected type of message. The header.mechanism field had value . The header.msgtype field had value . The name of the exit function in which the error was discovered is . Response: Make sure that the exits at both ends of the channel generate compatible flows. AMQ9581DCE Security: wrong exit called. Severity: 30 : Severe error Explanation: Exit on channel was called for use as a WebSphere MQ exit of the wrong type. DCE_SEC_SCY_CHANNELEXIT functions as a security exit; DCE_SEC_SRM_CHANNELEXIT functions as a send, receive or message exit. The ExitId parameter passed to the exit was . Response: Alter the exit definitions to ensure that exit is called correctly. AMQ9582DCE Security: invalid exit function requested. Severity: 30 : Severe error Explanation: Exit on channel was called with an invalid ExitReason (value ). Response: Check that the exit is being run with a compatible release of WebSphere MQ base code. If not then correct it. If it is, contact your IBM support center for help. AMQ9583The DCE security exit was not run. Severity: 30 : Severe error Explanation: The DCE_SEC_SRM_CHANNELEXIT exit was called on channel ; the value of pContext->mechanism () passed was not valid. Response: This is probably because the DCE_SEC_SRM_CHANNELEXIT exit has been called without first calling the DCE_SEC_SCY_CHANNELEXIT security exit. Alter the system so that either both or neither are run. AMQ9584DCE Security: message too short. Severity: 30 : Severe error Explanation: The DCE_SEC_SRM_CHANNELEXIT receive or message exit was called on channel to process an incoming message. The pDataLength parameter supplied to the exit indicated that the message received was too short to be a valid message for the relevant exit. The *pDataLength value was . Response: Configure the system so that compatible send/receive/message exits are run at both ends of the channel. AMQ9585Maximum number of channel initiators reached. Severity: 30 : Severe error Explanation: The maximum number of channels initiators that can be in use simultaneously has been reached. The number of permitted channel initiators is a configurable parameter in the queue manager configuration file. Response: Wait for one or more channel initiators to close and retry the operation or modify the configuration file to allow more initiators and restart the Queue Manager. AMQ9586Program cannot create queue manager object. Severity: 30 : Severe error Explanation: The attempt to create object on queue manager failed with reason code . Response: Use the standard facilities supplied with your system to record the problem identifier. Contact your IBM support center. AMQ9587Program cannot open queue manager object. Severity: 30 : Severe error Explanation: The attempt to open object on queue manager failed with reason code . Response: Use the standard facilities supplied with your system to record the problem identifier. Contact your IBM support center. AMQ9588Program cannot update queue manager object. Severity: 30 : Severe error Explanation: The attempt to update object on queue manager failed with reason code . Response: Use the standard facilities supplied with your system to record the problem identifier. Contact your IBM support center. AMQ9589Program cannot query queue manager object. Severity: 30 : Severe error Explanation: The attempt to query object on queue manager failed with reason code . Response: Use the standard facilities supplied with your system to record the problem identifier. Contact your IBM support center. AMQ9590Program cannot close queue manager object. Severity: 30 : Severe error Explanation: The attempt to close object on queue manager failed with reason code . Response: Use the standard facilities supplied with your system to record the problem identifier. Contact your IBM support center. AMQ9591Program cannot prepare queue manager object. Severity: 30 : Severe error Explanation: The attempt to prepare object on queue manager failed with reason code . Response: Use the standard facilities supplied with your system to record the problem identifier. Contact your IBM support center. AMQ9592Program cannot resolve queue manager object. Severity: 30 : Severe error Explanation: The attempt to resolve object on queue manager failed with reason code . Response: Use the standard facilities supplied with your system to record the problem identifier. Contact your IBM support center. AMQ9593Program cannot delete queue manager object. Severity: 30 : Severe error Explanation: The attempt to delete object on queue manager failed with reason code . Response: Use the standard facilities supplied with your system to record the problem identifier. Contact your IBM support center. AMQ9594Usage: runmqfmt [filename]. Severity: 0 : Information Explanation: Syntax for the usage of runmqfmt. Response: None. AMQ9595Usage: endmqlsr [-w] [-m QMgrName] Severity: 10 : Warning Explanation: The correct usage is shown. Response: Correct the parameters passed to the endmqlsr program and retry the operation. AMQ9596Queue Manager still running Severity: 30 : Severe error Explanation: The requested operation can not complete because queue manager is still running. Response: End the queue manager and retry the operation. AMQ9597No WebSphere MQ listeners for Queue Manager . Severity: 0 : Information Explanation: No listener processes were found in the system for Queue Manager . Response: None. AMQ9598 WebSphere MQ listeners will end shortly. Severity: 0 : Information Explanation: listeners detected in the system are scheduled for shutdown. Response: None. AMQ9599Program could not open queue manager object. Severity: 30 : Severe error Explanation: The attempt to open either the queue or queue manager object on queue manager by user failed with reason code . Response: Ensure that the queue is available and retry the operation. If the message is from a remote Queue Manager, check the Message Channel Agent User Identifier has the correct authority. AMQ9601Program could not inquire on queues on this queue manager. Severity: 30 : Severe error Explanation: The WebSphere MQ clustering repository program was attempting to find out about the queues on queue manager . One of the calls failed with reason code . The repository command was backed out and the repository process went into a timed wait. Response: Correct the error. When the repository process restarts it processes the backed out command again and continues. AMQ9602Maximum number of channel processes reached. Severity: 30 : Severe error Explanation: The channel can not start because the number of channel processes has already reached the maximum allowable value. The maximum number of channels processes is configured as . This value is a configurable parameter in the queue manager configuration file. Response: Wait for some of the operating channels to close. Retry the operation when some channels are available. AMQ9603Error accessing the process pool shared segment. Severity: 30 : Severe error Explanation: The program could not access the process pool shared segment Response: A value of was returned from the subsystem when an attempt was made to access the Channel process pool shared memory. Contact the systems administrator, who should examine the log files to determine why the program was unable to access the process pool shared segment. AMQ9604Channel terminated unexpectedly Severity: 30 : Severe error Explanation: The process or thread executing channel is no longer running. The check process system call returned for process . Response: No immediate action is required because the channel entry has been removed from the list of running channels. Inform the system administrator who should examine the operating system procedures to determine why the channel process has terminated. AMQ9605 WebSphere MQ listeners have been ended. Severity: 0 : Information Explanation: listeners detected in the system have been ended. Response: None. AMQ9606A WebSphere MQ listener has ended. Severity: 0 : Information Explanation: One listener detected in the system has been ended. Response: None. AMQ9608Remote resources in recovery Severity: 30 : Severe error Explanation: Channel could not establish a successful connection with the remote Queue Manager because resources are being recovered. Response: Restart the channel at a later time. If the problem persists then examine the error logs of the remote Queue Manager to see the full explanation of the cause of the problem. AMQ9610AMQ messages suppressed Severity: 0 : Information Explanation: messages of type AMQ were suppressed Response: Message suppression is controlled by MQ_CHANNEL_SUPPRESS_MSGS and MQ_CHANNEL_SUPPRESS_INTERVAL environment variables. AMQ9611Rebuild Client Channel Table - program completed normally Severity: 0 : Information Explanation: Rebuild Client Channel Table program completed normally. Response: None. AMQ9612 WebSphere MQ listeners could not be ended. Severity: 0 : Information Explanation: The request to the end the WebSphere MQ listeners for specified Queue Manager was completed however listeners could not be stopped. Reasons why listener may not be stopped are: The listener process contains channels which are still active. Response: Active channels may be stopped using the 'STOP CHANNEL' command or by ending the Queue Manager, and reissuing the end-listener request. AMQ9614 (iSeries)Certificate is not signed by a trusted Certificate Authority. Severity: 0 : Information Explanation: The attempt to start channel failed because the certificate used in the SSL handshake is not signed by a Certificate Authority (CA) listed in the certificate trust list for this queue manager. This error occurs when the SSL key repository for the queue manager is specified as '*SYSTEM' and the application definition in Digital Certificate Manager has been modified to specify a CA trust list. Response: Use Digital Certificate Manager to add the required Certificate Authority (CA) certificates to the application definitions CA trust list. AMQ9615 (iSeries)Queue Manager is not registered with DCM. Severity: 0 : Information Explanation: The attempt to start channel failed because the queue manager is not registered as a SSL server application with Digital Certificate Manager (DCM). This error occurs when the SSL key repository for the queue manager is specified as '*SYSTEM' but WebSphere MQ cannot register the queue manager as an SSL server application with DCM, or alternatively when the application definition for the queue manager has been manually removed from DCM. Response: Attempt to re-register the queue manager with Digital Certificate Manager by issuing CHGMQM SSLKEYR(*SYSTEM). If this is unsuccessful you may need to manually add the application definition through Digital Certificate Manager, see the WebSphere MQ Security manual for more details. AMQ9616The CipherSpec proposed is not enabled on the SSL server. Severity: 30 : Severe error Explanation: The SSL subsystem at the SSL server end of a channel been configured in such a way that it has rejected the CipherSpec proposed by an SSL client. This rejection occured during the SSL handshake (i.e. it happened before the proposed CipherSpec was compared with the CipherSpec in the SSL server channel definition). This error most commonly occurs when the choice of acceptable CipherSpecs has been limited by setting the SSLFipsRequired attribute on the SSL server queue manager while the SSL client is trying to connect with a CipherSpec which is not FIPS-certified on the SSL server. The channel is ; in some cases its name cannot be determined and so is shown as '????'. The channel did not start. Response: Analyse why the proposed CipherSpec was not enabled on the SSL server. Alter the client CipherSpec, or reconfigure the SSL server to accept the original client CipherSpec. Restart the channel. AMQ9617Parameter requesting FIPS has an invalid value. Severity: 30 : Severe error Explanation: An SSL channel running on an MQ client has failed to start. This is because the value specified for the MQSSLFIPS environment variable, or in the MQSCO FipsRequired field, is invalid. The value specified was ""; valid values are "YES" or "NO". Response: Set the value specified for the MQSSLFIPS environment variable, or in the MQSCO FipsRequired field, to "YES" or "NO". Restart the channel. AMQ9618SSLCRLNL attribute points to a namelist with no names. Severity: 30 : Severe error Explanation: An SSL channel has failed to start because the SSLCRLNL queue manager attribute points to a namelist with an empty list of names. Response: If CRL checking is required, set up the namelist referenced by SSLCRLNL with a non-empty list of authentication information object names. If no CRL checking is required, clear the SSLCRLNL queue manager attribute. Restart the failing channel. AMQ9619SSL cannot be run from an unthreaded HP-UX MQ client. Severity: 30 : Severe error Explanation: On HP-UX, SSL cannot be run from a WebSphere MQ client which was linked with the unthreaded client libraries. Response: Either relink your client application with the threaded client libraries, or do not attempt to use SSL from this application. AMQ9620Internal error on call to SSL function on channel . Severity: 30 : Severe error Explanation: An error indicating a software problem was returned from a function which is used to provide SSL support. The error code returned was . The function call was . The channel is ; in some cases its name cannot be determined and so is shown as '????'. The channel did not start. Response: Collect the items listed in the 'Problem determination' section of the System Administration manual and contact your IBM support center. AMQ9620 (iSeries)Unexpected SSL error on call to . Severity: 0 : Information Explanation: An unexpected SSL error was returned from function for channel . The error code returned was . GSKit error codes are documented in the MQ manuals and also in the GSKSSL member of the H file in library QSYSINC. Response: Collect the items listed in the 'Problem determination' section of the System Administration manual and contact your IBM support center. AMQ9621Error on call to SSL function ignored on channel . Severity: 10 : Warning Explanation: An error indicating a software problem was returned from a function which is used to provide SSL support. The error code returned was . The function call was . The channel is ; in some cases its name cannot be determined and so is shown as '????'. This error is not regarded as sufficiently serious to interrupt channel operation; channel operation was not affected. Response: None. AMQ9622AUTHINFO object does not exist. Severity: 30 : Severe error Explanation: A channel or channel process has failed to start because the namelist of CRL AUTHINFO objects includes the name , but no AUTHINFO object of that name exists. Response: Ensure all the names in the namelist specified on the SSLCRLNL queue manager attribute correspond to AUTHINFO objects which are to be used on the SSL channels. Restart the failing channel or channel process. AMQ9623Error inquiring on AUTHINFO object . Severity: 30 : Severe error Explanation: A channel or channel process has failed to start because reason code was returned when an inquire was performed on AUTHINFO object . Response: Look at the MQRC_ values in the WebSphere MQ Application Programming Reference to determine the meaning of reason code , correct the error, and restart the failing channel or channel process. AMQ9624AUTHINFO object is not of type CRLLDAP. Severity: 30 : Severe error Explanation: A channel or channel process has failed to start because one of the AUTHINFO objects specified in the SSLCRLNL namelist is not of AUTHTYPE CRLLDAP. Instead the type value is . Response: Only include CRLLDAP AUTHINFO objects in the namelist specified on the SSLCRLNL queue manager attribute. Restart the channel or channel process. AMQ9625AUTHINFO object was specified with an invalid CONNAME. Severity: 30 : Severe error Explanation: A channel or channel process has failed to start because one of the AUTHINFO objects specified in the SSLCRLNL namelist has an invalid CONNAME parameter. The invalid value is . Response: Correct the invalid parameter. Restart the channel or channel process. AMQ9626Channel hanging while initializing SSL. Severity: 30 : Severe error Explanation: The current channel cannot start because another channel is hanging while initializing the SSL subsystem. Response: Investigate the reason for the hang on the other channel. Once this is rectified, restart this channel. AMQ9627The path and stem name for the SSL key repository have not been specified. Severity: 30 : Severe error Explanation: The directory path and file stem name for the SSL key repository have not been specified. On a MQ client system there is no default location for this file. SSL connectivity is therefore impossible as this file cannot be accessed. Response: Use the MQSSLKEYR environment variable or MQCONNX API call to specify the directory path and file stem name for the SSL key repository. AMQ9628An LDAP server containing CRLs was specified with an invalid CONNAME. Severity: 30 : Severe error Explanation: The WebSphere MQ client has failed to connect because an invalid CONNAME was found for one of the LDAP servers containing CRLs. The invalid value is . Response: Correct the invalid parameter. If the LDAP details were defined on a queue manager system, regenerate the client definitions. Reconnect. AMQ9629Bad SSL cryptographic hardware parameters. Severity: 30 : Severe error Explanation: The following string was supplied to specify or control use of SSL cryptographic hardware: . This string does not conform to any of the MQ SSL cryptographic parameter formats. The channel is . The channel did not start. Response: Correct your SSL cryptographic hardware parameters and restart the channel. AMQ9630An expired SSL certificate was loaded. Severity: 30 : Severe error Explanation: An SSL certificate that was loaded was not corrupt, but failed validation checks on its date fields. The certificate has either expired, or its date is not valid yet (that is, the from date is later than today), or the validity date range is incorrect (for example, the to date is earlier than the from date). Response: Ensure that the specified SSL certificate has a valid expiry date. AMQ9631The CipherSpecs on the two ends of channel do not match. Severity: 30 : Severe error Explanation: There is a mismatch between the CipherSpecs on the local and remote ends of channel . The channel will not run until this mismatch is resolved. Response: Change the channel definitions for so the two ends have matching CipherSpecs and restart the channel. AMQ9631 (iSeries)The CipherSpecs at the ends of channel do not match. Severity: 30 : Severe error Explanation: There is a mismatch between the CipherSpecs on the local and remote ends of channel . The channel will not run until this mismatch is resolved. The local CipherSpec is and the remote CipherSpec is . Response: Change the channel definition for so that both ends have matching CipherSpecs and restart the channel. AMQ9633Bad SSL certificate for channel . Severity: 30 : Severe error Explanation: A certificate encountered during SSL handshaking is regarded as bad for one of the following reasons: (a) it was formatted incorrectly and could not be validated, or (b) it was formatted correctly but failed validation against the Certification Authority (CA) root and other certificates held on the local system, or (c) it was found in a Certification Revocation List (CRL) on an LDAP server. (d) a CRL was specified but the CRL could not be found on the LDAP server. The channel is ; in some cases its name cannot be determined and so is shown as '????'. The channel did not start. Response: Check which of the three possible causes applies on your system. Correct the error, and restart the channel. AMQ9634SSL security context expired. Severity: 30 : Severe error Explanation: During an SSL operation to encrypt or decrypt a secured message, the SSL security context, which is used to secure communications and was previously established with the remote party, has expired because the remote party has shut down. The secured message has not been encrypted or decrypted. This failure has closed WebSphere MQ channel name . If the name is '????', the name is unknown. The SSL operation was and its completion code was . Response: Determine why the remote party has shut down and if necessary re-start the channel. The shut down might be the result of controlled termination by a system administrator, or the result of an unexpected termination due to an error. The SSL operation is described in the Windows Schannel reference manual. AMQ9635Channel did not specify a valid CipherSpec. Severity: 30 : Severe error Explanation: Channel did not specify a valid CipherSpec. Response: Change channel to specify a valid CipherSpec. AMQ9635 (iSeries)Channel did not specify a valid CipherSpec. Severity: 30 : Severe error Explanation: Channel did not specify a valid CipherSpec, or it specified a CipherSpec that is not available from the IBM Cryptographic Access Provider product installed on this machine. CipherSpecs that use 128-bit encryption algorithms are only available in 5722-AC3 (128-bit) IBM Cryptographic Access Provider. Response: Change channel to specify a valid CipherSpec that is available from the IBM Cryptographic Access Provider product installed on this machine. Check that the CipherSpec you are using is available on this machine in either the 5722-AC2 (56-bit) IBM Cryptographic Access Provider or 5722-AC3 (128-bit) IBM Cryptographic Access Provider licensed program. AMQ9636SSL distinguished name does not match peer name, channel . Severity: 30 : Severe error Explanation: The distinguished name, , contained in the SSL certificate for the remote end of the channel does not match the local SSL peer name for channel . The distinguished name at the remote end must match the peer name specified (which can be generic) before the channel can be started. Response: If this remote system should be allowed to connect, either change the SSL peer name specification for the local channel so that it matches the distinguished name in the SSL certificate for the remote end of the channel, or obtain the correct certificate for the remote end of the channel. Restart the channel. AMQ9637Channel is lacking a certificate. Severity: 30 : Severe error Explanation: The channel is lacking a certificate to use for the SSL handshake. The channel name is (if '????' it is unknown at this stage in the SSL processing). The channel did not start. Response: Make sure the appropriate certificates are correctly configured in the key repositories for both ends of the channel. If you have migrated from WebSphere MQ V5.3 to V6, it is possible that the missing certificate is due to a failure during SSL key repository migration. Check the relevant error logs. If these show that an orphan certificate was encountered then you should obtain the relevant missing certification authority (signer) certificates and then import these and the orphan certificate into the WebSphere MQ V6 key repository, and then re-start the channel. AMQ9638SSL communications error for channel . Severity: 30 : Severe error Explanation: An unexpected SSL communications error occurred for a channel, as reported in the preceding messages. The channel is ; in some cases its name cannot be determined and so is shown as '????'. The channel did not start. Response: Investigate the problem reported in the preceding messages. Review the local and remote console logs for reports of network errors. Correct the errors and restart the channel. AMQ9639Remote channel did not specify a CipherSpec. Severity: 30 : Severe error Explanation: Remote channel did not specify a CipherSpec when the local channel expected one to be specified. The channel did not start. Response: Change the remote channel to specify a CipherSpec so that both ends of the channel have matching CipherSpecs. AMQ9640SSL invalid peer name, channel , attribute . Severity: 30 : Severe error Explanation: The SSL peer name for channel includes a distinguished name attribute key which is invalid or unsupported. The channel did not start. Response: Correct the SSL peer name for the channel. Restart the channel. AMQ9641Remote CipherSpec error for channel . Severity: 30 : Severe error Explanation: The remote end of channel has had a CipherSpec error. The channel did not start. Response: Review the error logs on the remote system to discover the problem with the CipherSpec. AMQ9642No SSL certificate for channel . Severity: 30 : Severe error Explanation: The channel did not supply a certificate to use during SSL handshaking, but a certificate is required by the remote queue manager. The channel did not start. Response: Ensure that the key repository of the local queue manager or MQ client contains an SSL certificate which is associated with the queue manager or client. Alternatively, if appropriate, change the remote channel definition so that its SSLCAUTH attribute is set to OPTIONAL and it has no SSLPEER value set. If you have migrated from WebSphere MQ V5.3 to V6, it is possible that the missing certificate is due to a failure during SSL key repository migration. Check the relevant error logs. If these show that an orphan certificate was encountered then you should obtain the relevant missing certification authority (signer) certificates and then import these and the orphan certificate into the WebSphere MQ V6 key repository, and then re-start the channel. AMQ9642 (iSeries)No SSL certificate for channel . Severity: 0 : Information Explanation: The channel did not supply a certificate to use during SSL handshaking, but a certificate is required by the remote queue manager. The channel did not start. Response: If the SSL key repository for the queue manager has been specified as '*SYSTEM' ensure that a certificate has been associated with the application description for the queue manager in Digital Certificate Manager. Alternatively, if appropriate, change the remote channel definition so that its SSLCAUTH attribute is set to OPTIONAL and it has no SSLPEER value set. AMQ9643Remote SSL peer name error for channel . Severity: 30 : Severe error Explanation: The remote end of channel has had an SSL peer name error. The channel did not start. Response: Review the error logs on the remote system to discover the problem with the peer name. AMQ9645Correctly labelled SSL certificate missing on channel . Severity: 30 : Severe error Explanation: The key database file in use has not been set up with a correctly labelled SSL certificate. The channel is ; in some cases its name cannot be determined and so is shown as '????'. The channel did not start. Response: Add a correctly labelled SSL certificate to the current key database file. Restart the channel. AMQ9646Channel could not connect to any LDAP CRL servers. Severity: 30 : Severe error Explanation: LDAP Certification Revocation List (CRL) servers were specified but a connection could not be established to any of them. The channel is ; in some cases its name cannot be determined and so is shown as '????'. The channel did not start. Response: Check that the LDAP CRL server specifications are correct. If they are, check that the servers are running and that the networking to access them is working correctly. Fix any errors found and restart the channel. AMQ9647I/O error on SSL key repository. Severity: 30 : Severe error Explanation: An I/O error was encountered when attempting to read the SSL key repository. The channel is ; in some cases its name cannot be determined and so is shown as '????'. The channel did not start. Response: Analyse why there is a I/O problem when reading the key repository. Fix the error if one is found, or it may be a temporary problem. Restart the channel. AMQ9648The SSL key repository has an invalid internal format. Severity: 30 : Severe error Explanation: The SSL key repository has an invalid internal format. The channel is ; in some cases its name cannot be determined and so is shown as '????'. The channel did not start. Response: Recreate the SSL key repository and restart the channel. AMQ9649The SSL key repository contains duplicate keys. Severity: 30 : Severe error Explanation: The SSL key repository contains two or more entries with the same key. The channel is ; in some cases its name cannot be determined and so is shown as '????'. The channel did not start. Response: Use your key management tool to remove the duplicate keys. Restart the channel. AMQ9650The SSL key repository contains entries with duplicate labels. Severity: 30 : Severe error Explanation: The SSL key repository contains two or more entries with the same label. The channel is ; in some cases its name cannot be determined and so is shown as '????'. The channel did not start. Response: Use your key management tool to remove the duplicate entries. Restart the channel. AMQ9651The SSL key repository is corrupt or has a bad password. Severity: 30 : Severe error Explanation: The SSL key repository has become corrupted or its password id is incorrect. The channel is ; in some cases its name cannot be determined and so is shown as '????'. The channel did not start. Response: Use your key management tool to recreate the key repository with a new password. Restart the channel. AMQ9652The remote SSL certificate has expired. Severity: 30 : Severe error Explanation: The SSL certificate used by MQ on the remote end of the channel has expired. The channel is ; in some cases its name cannot be determined and so is shown as '????'. The channel did not start. Response: Use your key management tool to provide MQ with a current SSL certificate on the remote end of the channel. Restart the channel. AMQ9653An SSL trace file could not be opened. Severity: 10 : Warning Explanation: An SSL trace file could not be opened. The SSL trace files are created in directory /var/mqm/trace and have names AMQ.SSL.TRC and AMQ.SSL.TRC.1. The channel is ; in some cases its name cannot be determined and so is shown as '????'. This error is not regarded as sufficiently serious to interrupt channel operation; channel operation was not affected. Response: Check that you have a directory called /var/mqm/trace and that the userid under which WebSphere MQ runs has permissions and space to create and open a file in that directory. Fix the problem and you will get SSL trace output. AMQ9654An invalid SSL certificate was received from the remote system. Severity: 30 : Severe error Explanation: An SSL certificate received from the remote system was not corrupt but failed validation checks on something other than its ASN fields and date. The channel is ; in some cases its name cannot be determined and so is shown as '????'. The channel did not start. Response: Ensure that the remote system has a valid SSL certificate. Restart the channel. AMQ9655Problem loading GSKit SSL support. Severity: 30 : Severe error Explanation: MQ SSL support is provided on this platform using a component called GSKit which is installed as part of MQ. GSKit had an internal problem loading one if its dynamic link libraries. The channel is ; in some cases its name cannot be determined and so is shown as '????'. The channel did not start. Response: Uninstall MQ and reinstall. Restart the channel. AMQ9656An invalid SSL certificate was received from the remote system. Severity: 30 : Severe error Explanation: An SSL certificate received from the remote system was not corrupt but failed validation checks on its ASN fields. The channel is ; in some cases its name cannot be determined and so is shown as '????'. The channel did not start. Response: Ensure that the remote system has a valid SSL certificate. Restart the channel. AMQ9657The key repository could not be opened (channel ). Severity: 30 : Severe error Explanation: The key repository could not be opened. The key repository either does not exist or has incorrect permissions associated with it. The channel is ; in some cases its name cannot be determined and so is shown as '????'. The channel did not start. Response: Ensure that the key repository you specify exists and that its permissions are such that the MQ process involved can read from it. Restart the channel. AMQ9658An invalid SSL certificate has been encountered. Severity: 30 : Severe error Explanation: An SSL certificate has been encountered which was not corrupt but which failed validation checks on its date fields. The certificate has either expired, or its date is not valid yet (i.e. the from date is later than today), or the validity date range is incorrect (e.g. the to date is earlier than the from date). The channel is ; in some cases its name cannot be determined and so is shown as '????'. The channel did not start. Response: Ensure that both the local and remote systems have valid, current SSL certificates. Restart the channel. AMQ9659A failure occurred during SSL handshaking. Severity: 30 : Severe error Explanation: During SSL handshaking, or associated activities, a failure occurred. The failure is and has caused WebSphere MQ channel name to be closed. If the name is '????' then the name is unknown. Response: Refer to prior message in the WebSphere MQ error log for information related to this problem. AMQ9660SSL key repository: password stash file absent or unusable. Severity: 30 : Severe error Explanation: The SSL key repository cannot be used because MQ cannot obtain a password to access it. Reasons giving rise to this error include: (a) the key database file and password stash file are not present in the location configured for the key repository, (b) the key database file exists in the correct place but that no password stash file has been created for it, (c) the files are present in the correct place but the userid under which MQ is running does not have permission to read them, (d) one or both of the files are corrupt. The channel is ; in some cases its name cannot be determined and so is shown as '????'. The channel did not start. Response: Ensure that the key repository variable is set to where the key database file is. Ensure that a password stash file has been associated with the key database file in the same directory, and that the userid under which MQ is running has read access to both files. If both are already present and readable in the correct place, delete and recreate them. Restart the channel. AMQ9661Bad SSL data from peer on channel . Severity: 30 : Severe error Explanation: An SSL channel has stopped because bad SSL data was received from the remote end of the channel. More detail on the nature of the corruption can be found from the GSKit return value of (the GSKit return values are documented in the MQ manuals). The channel is ; in some cases its name cannot be determined and so is shown as '????'. Response: Ensure you are connecting to a version of MQ which supports SSL at the remote end of the channel. Check your network between the two ends of the channel, and consider whether any possible causes of message corruption could be present. Fix any problems which may exist and restart the channel. AMQ9661 (iSeries)Bad SSL data from peer on channel . Severity: 0 : Information Explanation: An SSL channel has stopped because bad SSL data was received from the remote end of the channel. More detail on the nature of the corruption can be found from the GSKit return value of (the GSKit return values are documented in the MQ manuals and also in the GSKSSL member of the H file in library QSYSINC). The channel is ; in some cases its name cannot be determined and so is shown as '????'. Response: Ensure the remote queue manager and channel listener are running and that you are connecting to a version of MQ which supports SSL at the remote end of the channel. Check your network between the two ends of the channel, and consider whether any possible causes of message corruption could be present. Fix any problems which may exist and restart the channel. AMQ9662SSL has encountered something it does not support. Severity: 30 : Severe error Explanation: This error can arise for a number of reasons: 1) The platform does not support a given type of cryptographic hardware, e.g. Ncipher and Rainbow are/were not supported on the Linux/390 platform. 2) The cryptographic hardware cryptography has returned an error. 3) Unsupported X509 General Name format when checking the remote certificate. The GSKit SSL provider incorporated in MQ only supports formats rfc822, DNSName, directoryname, uniformResourceID, and IPAddress. The channel is ; in some cases its name cannot be determined and so is shown as '????'. The channel did not start. Response: Check that your cryptographic hardware is supported on your platform and test it to see that it is working correctly. Check that the remote certificates you are using conform to the X509 General Name formats listed. Fix the problem and restart the channel. AMQ9663An invalid SSL certificate was received from the remote system. Severity: 30 : Severe error Explanation: An SSL certificate received from the remote system failed validation checks on its signature. The channel is ; in some cases its name cannot be determined and so is shown as '????'. The channel did not start. Response: Ensure that the remote system has a valid SSL certificate. Restart the channel. AMQ9664Bad userid for CRL LDAP server; SSL channel . Severity: 30 : Severe error Explanation: Certification Revocation List (CRL) checking on an LDAP server or servers has been configured on the local MQ system. The userid information configured for the LDAP server or servers is incorrect. The channel is ; in some cases its name cannot be determined and so is shown as '????'. The channel did not start. Response: Check the userid information for the CRL LDAP server or servers you have configured locally. Correct any problems found and restart the channel. AMQ9665SSL connection closed by remote end of channel . Severity: 30 : Severe error Explanation: The SSL connection was closed by the remote end of the channel during the SSL handshake. The channel is ; in some cases its name cannot be determined and so is shown as '????'. The channel did not start. Response: Check the remote end of the channel for SSL-related errors. Fix them and restart the channel. AMQ9666Error accessing CRL LDAP servers; SSL channel . Severity: 30 : Severe error Explanation: CRL checking on LDAP servers has been configured on the local MQ system. An error was found when trying to access the CRL LDAP servers when validating a certificate from the remote system. Possible causes are: (a) cannot connect to any of the LDAP servers, or (b) invalid login user id or password for an LDAP server, or (c) the certificate issuer's Distinguished Name (DN) is not defined in the DIT of an LDAP server. The channel is ; in some cases its name cannot be determined and so is shown as '????'. The channel did not start. Response: Check access to the CRL LDAP server(s) you have configured locally. Put right any problems found and restart the channel. AMQ9667Bad password for CRL LDAP server; SSL channel . Severity: 30 : Severe error Explanation: Certification Revocation List (CRL) checking on an LDAP server or servers has been configured on the local MQ system. The password information configured for the LDAP server or servers is incorrect. The channel is ; in some cases its name cannot be determined and so is shown as '????'. The channel did not start. Response: Check the password information for the CRL LDAP server or servers you have configured locally. Correct any problems found and restart the channel. AMQ9668The specified PKCS #11 shared library could not be loaded. Severity: 30 : Severe error Explanation: A failed attempt was made to load the PKCS #11 shared library specified to MQ in the PKCS #11 driver path field of the GSK_PKCS11 SSL CryptoHardware parameter. The channel is ; in some cases its name cannot be determined and so is shown as '????'. The channel did not start. Response: Ensure that the PKCS #11 shared library exists and is valid at the location specified. Restart the channel. AMQ9669The PKCS #11 token could not be found. Severity: 30 : Severe error Explanation: The PKCS #11 driver failed to find the token specified to MQ in the PKCS #11 token label field of the GSK_PKCS11 SSL CryptoHardware parameter. The channel is ; in some cases its name cannot be determined and so is shown as '????'. The channel did not start. Response: Ensure that the PKCS #11 token exists with the label specified. Restart the channel. AMQ9670PKCS #11 card not present. Severity: 30 : Severe error Explanation: A PKCS #11 card is not present in the slot. The channel is ; in some cases its name cannot be determined and so is shown as '????'. The channel did not start. Response: Ensure that the correct PKCS #11 card is present in the slot. Restart the channel. AMQ9671The PKCS #11 token password specified is invalid. Severity: 30 : Severe error Explanation: The password to access the PKCS #11 token is invalid. This is specified to MQ in the PKCS #11 token password field of the GSK_PKCS11 SSL CryptoHardware parameter. The channel is ; in some cases its name cannot be determined and so is shown as '????'. The channel did not start. Response: Ensure that the PKCS #11 token password specified on GSK_PKCS11 allows access to the PKCS #11 token specified on GSK_PKCS11. Restart the channel. AMQ9672An SSL security call failed. Severity: 30 : Severe error Explanation: An SSPI call to the Secure Channel (Schannel) SSL provider failed. The failure has caused WebSphere MQ channel name to be closed. If the name is '????' then the name is unknown. Response: Consult the Windows Schannel reference manual to determine the meaning of status for SSPI call . Correct the failure and if necessary re-start the channel. AMQ9673SSL client handshaking failed. Severity: 30 : Severe error Explanation: During an SSL client's handshaking, an SSPI call to the Secure Channel (Schannel) SSL provider failed. The failure has caused WebSphere MQ channel name to be closed. If the name is '????' then the name is unknown. Response: Consult the Windows Schannel reference manual to determine the meaning of status for SSPI call . Correct the failure and if necessary re-start the channel. AMQ9674An unknown error occurred during an SSL security call. Severity: 30 : Severe error Explanation: An unknown error occurred during an SSPI call to the Secure Channel (Schannel) SSL provider. The error may be due to a Windows SSL problem or to a general Windows problem or to invalid WebSphere MQ data being used in the call. The WebSphere MQ error recording routine has been called. The error has caused WebSphere MQ channel name to be closed. If the name is '????' then the name is unknown. Response: Consult the Windows Schannel reference manual to determine the meaning of status for SSPI call . If the problem can be resolved using the manual, correct the failure and if necessary re-start the channel. If the problem cannot be resolved then use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ9675The requested certificate could not be found. Severity: 30 : Severe error Explanation: A request for a certificate identified as in the store has failed, because the certificate could not be found. The Windows error code has been set to . The WebSphere MQ error recording routine has been called. Response: Consult the Windows reference manual to determine the meaning of error if this value is non-zero. Check to see whether the specified certificate has been copied to the correct certificate store and has not been deleted. Use the amqmcert command line utility or the WebSphere MQ Explorer administration application to configure certificate store for use with WebSphere MQ. If the problem cannot be resolved then use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ9676The Windows cryptographic services library could not be loaded. Severity: 30 : Severe error Explanation: WebSphere MQ requires crypt32.dll to be available in order to carry out cryptographic functionality. The attempt to load this library returned the Windows error code . The WebSphere MQ error recording routine has been called. Response: Consult the Windows reference manual to determine the meaning of error code . Check that the crypt32.dll file is available and not corrupt. If the problem cannot be resolved then use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ9677The Windows security services library could not be loaded. Severity: 30 : Severe error Explanation: WebSphere MQ requires to be available in order to run or configure SSL functionality. The attempt to load this library returned the Windows error code . The WebSphere MQ error recording routine has been called. Response: Consult the Windows reference manual to determine the meaning of error code . Check that the file is available and not corrupt. If the problem cannot be resolved then use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ9678The certificate / already exists in the store . Severity: 10 : Warning Explanation: The certificate store already contains the specified certificate, identified by the issuer name of , serial number . The existing certificate has not been replaced. AMQ9679The certificate store could not be opened. Severity: 30 : Severe error Explanation: The certificate store could not be opened, and failed with the Windows error code . The WebSphere MQ error recording routine has been called. Response: Consult the Windows reference manual to determine the meaning of error if this value is non-zero. Check that either your MQSSLKEYR environment variable (for client connections), or SSLKEYR queue manager attribute (for WebSphere MQ queue managers) has been defined correctly, and that the file path specified is valid. If the problem cannot be resolved then use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ9680A problem was encountered with the specified certificate file. Severity: 30 : Severe error Explanation: A problem occurred when attempting to read the certificate from the file . The file may be corrupt or incorrectly formatted. The Windows error code reported is . The WebSphere MQ error recording routine has been called. Response: Ensure that the certificate file is valid and complete, and in one of the file formats supported by WebSphere MQ. If the problem cannot be resolved then use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ9681The requested functionality is not supported on this system. Severity: 30 : Severe error Explanation: An SSL function was attempted that is not supported on this system. a) importing pfx format certificate files with private key data is only supported on Windows 2000 or greater. b) a the security library installed on your system is not of the correct level and does not contain the pre-requisite functions. On pre Windows 2000 systems, Internet Explorer 4.1 or greater must be installed. The WebSphere MQ error recording routine has been called. Response: If pre-requisite software is missing, please install the necessary levels of software and retry the operation. If the problem cannot be resolved then use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ9682The WebSphere MQ SSL library has not been initialized. Severity: 30 : Severe error Explanation: The WebSphere MQ SSL library 'amqcssln.dll' has been called without it first being initialized by the calling process. Response: Ensure that the initialization function has been called prior to issuing any amqcssln function calls. AMQ9683The private key data for this certificate is not exportable. Severity: 30 : Severe error Explanation: An attempt has been made to export the private key data from a certificate, but the properties of the certificate will not allow this. WebSphere MQ needs to be able to export private key data when copying personal certificates between certificate stores. The Windows cryptographic API returned the error code . Response: When requesting the certificate from the certificate authority, the private key data must be marked as exportable to enable WebSphere MQ to be able to copy the certificate and private key data into a WebSphere MQ store. The certificate file may need to be requested again to resolve this problem. If the problem cannot be resolved then use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ9684A problem occurred while attempting to access the certificate's properties. Severity: 30 : Severe error Explanation: The certificate issued by with serial number , or it's private key data, appears to be unusable and may be corrupt. The Windows return code was generated when attempting to use this certificate. The WebSphere MQ error recording routine has been called. Response: Consult the Windows reference manual to determine the meaning of error . Check that the certificate is valid and has not been corrupted. If it is possible that the certificate or private key data is corrupt, try to remove the certificate from your system and re-import it. If the problem cannot be resolved then use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ9685A problem occured while accessing the registry. Severity: 30 : Severe error Explanation: An error occured while attempting to load or unload the personal registry hive (HKEY_LOCAL_USER) for the user who launched this process. The WebSphere MQ error recording routine has been called. Response: If the problem cannot be resolved then use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ9686An unexpected error occured while attempting to manage a certificate store. Severity: 30 : Severe error Explanation: The Windows cryptographic API returned error code when calling the function for certificate store . The error may be due to a certificate store problem or to a general Windows problem or to a problem with a certificate in the store. The WebSphere MQ error recording routine has been called. Response: Consult the Windows reference manual to determine the meaning of error . Check that the certificate store is valid and not corrupt. If the problem cannot be resolved then use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ9687The pfx password provided is invalid. Severity: 30 : Severe error Explanation: The password supplied for importing or copying the certificate is incorrect, and the operation could not be completed. Response: Make sure the password is correct and try again. If the password has been forgotten or lost, the certificate will need to be regenerated or exported from the original source. AMQ9688The private key data for this certificate is unavailable. Severity: 30 : Severe error Explanation: The private key data associated with this certificate is reported as being present on the system, but has failed, returning the Windows error code . The WebSphere MQ error recording routine has been called. Response: Consult the Windows reference manual to determine the meaning of error code . If the problem can be resolved using the manual, correct the failure and if necessary re-try the operation. If the problem cannot be resolved then use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ9689An unknown error occurred deleting the store . Severity: 30 : Severe error Explanation: The WebSphere MQ certificate store for queue manager could not be deleted. The filename for the certificate store is . The Windows error code has been set to . The WebSphere MQ error recording routine has been called. Response: Consult the Windows reference manual to determine the meaning of error . If the problem can be resolved using the manual, correct the failure and if necessary re-try the operation. Check that the store file exists and that other processes (such as queue managers) that may be accessing the store are not running. If the problem cannot be resolved then use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ9690The public key in the issuer's certificate has failed to validate the subject certificate. Severity: 30 : Severe error Explanation: The public key in the issuer's certificate (CA or signer certificate), is used to verify the signature on the subject certificate assigned to channel . This verification has failed, and the subject certificate therefore cannot be used. The WebSphere MQ error recording routine has been called. Response: Check that the issuer's certificate is valid and available, and that it is up to date. Verify with the certificate's issuer that the subject certificate and issuer certificate should still be valid. If the problem cannot be resolved then use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ9691The WebSphere MQ MQI library could not be loaded. Severity: 30 : Severe error Explanation: The library file is expected to be available on your system, but attempts to load it have failed with Windows return code . The WebSphere MQ error recording routine has been called. Response: Ensure that the WebSphere MQ library file exists and is available on your system. Consult the Windows reference manual to determine the meaning of error code . If the problem cannot be resolved then use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ9692The SSL library has already been initialized. Severity: 20 : Error Explanation: The SSL library has already been initialized once for this process, any changes to SSL attributes will not take affect, and the original values will remain in force. Response: If the problem cannot be resolved then use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ9693The password provided for the LDAP server is incorrect. Severity: 30 : Severe error Explanation: One or more of the LDAP servers used for providing CRL information to WebSphere MQ has rejected a login attempt because the password provided is incorrect. The WebSphere MQ error recording routine has been called. The error has caused WebSphere MQ channel name to be closed. If the name is '????' then the name is unknown. Response: Ensure that the passwords specified in the AuthInfo objects are correct for each server name provided. If the problem cannot be resolved then use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ9694The DN syntax provided for an LDAP search is invalid. Severity: 30 : Severe error Explanation: The distinguished name provided in one or more AuthInfo object definitions is invalid, and the request to a CRL LDAP server has been rejected. The WebSphere MQ error recording routine has been called. The error has caused WebSphere MQ channel name to be closed. If the name is '????' then the name is unknown. Response: Verify that the details supplied in the AuthInfo object definitions for this channel are correct. If the problem cannot be resolved then use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ9695The username provided for the LDAP server is incorrect. Severity: 30 : Severe error Explanation: One or more of the LDAP servers used for providing CRL information to WebSphere MQ has rejected a login attempt because the username provided does not exist. The WebSphere MQ error recording routine has been called. The error has caused WebSphere MQ channel name to be closed. If the name is '????' then the name is unknown. Response: Ensure that the usernamed specified in the AuthInfo objects for this channel are correct for each LDAP server name provided. If the problem cannot be resolved then use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ9696Usage: amqmcert [SERVERNAME] [-a handle] [-k SSLKeyR|CA|ROOT|MY] [-m QueueMgr] [-s CertFile] [-p PersonalCertFile] [-z Password] [-x handle] [-l] [-d handle] [-r handle] [-u] [-h] Severity: 0 : Information Explanation: This shows the correct usage. Response: None. AMQ9697WebSphere MQ Services could not be contacted on the target server. Severity: 30 : Severe error Explanation: An attempt was made to contact the WebSphere MQ Services on the target server . The call failed with return code . The WebSphere MQ error recording routine has been called. Response: Ensure that the target server name specified is correct and that you have sufficient access rights on that server to be able to administer WebSphere MQ. If the problem cannot be resolved then use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ9698An SSL security call failed during SSL handshaking. Severity: 30 : Severe error Explanation: An SSPI call to the Secure Channel (Schannel) SSL provider failed during SSL handshaking. The failure has caused WebSphere MQ channel name to be closed. If the name is '????' then the name is unknown. Response: Consult the Windows Schannel reference manual to determine the meaning of status for SSPI call . Correct the failure and if necessary re-start the channel. AMQ9699An unknown error occurred during an SSL security call during SSL handshaking. Severity: 30 : Severe error Explanation: An unknown error occurred during an SSPI call to the Secure Channel (Schannel) SSL provider during SSL handshaking. The error may be due to a Windows SSL problem or to a general Windows problem or to invalid WebSphere MQ data being used in the call. The WebSphere MQ error recording routine has been called. The error has caused WebSphere MQ channel name to be closed. If the name is '????' then the name is unknown. Response: Consult the Windows Schannel reference manual to determine the meaning of status for SSPI call . If the problem can be resolved using the manual, correct the failure and if necessary re-start the channel. If the problem cannot be resolved then use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ9710SSL security refresh failed. Severity: 30 : Severe error Explanation: The request to refresh SSL security was unsuccessful. Response: Look at previous error messages in the error files to determine the cause of the failure. AMQ9711SSL security refresh succeeded but channel restarts failed. Severity: 30 : Severe error Explanation: The SSL environments for this queue manager have been refreshed so current values and certificates are in use for all SSL channels. However, not all the outbound SSL channels which were running when the security refresh was initiated could be restarted after the refresh had completed. Response: Look at previous error messages in the error files to determine which channels could not be restarted. Restart these if necessary. AMQ9712SSL security refresh timed out waiting for channel . Severity: 30 : Severe error Explanation: The system was performing a security refresh for SSL. This function requests all outbound and inbound SSL channels to stop. It then waits for these channels to actually stop. SSL channel did not stop within the timeout period. Response: Investigate why channel is hung. Terminate the hung channel. Rerun the SSL security refresh. AMQ9713Channel ended: SSL refresh in progress. Severity: 0 : Information Explanation: The SSL support on this queue manager is in the middle of a security refresh. An attempt was made to start outbound SSL channel . It cannot start while the SSL security refresh is in progress. The channel is restarted automatically once the SSL security refresh is complete. Response: None. AMQ9714SSL refresh on receiving queue manager: channel did not start. Severity: 30 : Severe error Explanation: An SSL security refresh is in progress on the queue manager at the receiving end of this SSL channel. The channel is ; in some cases its name cannot be determined and so is shown as '????'. The channel did not start. Response: Restart the channel once the SSL refresh is complete. The channel will restart automatically if it is configured to retry the connection. AMQ9715Unexpected error detected in validating SSL session ID. Severity: 30 : Severe error Explanation: This error can arise when the GSKit SSL provider is missing one or more pre-requisite PTFs on the OS/400 platform. The channel is ; in some cases its name cannot be determined and so is shown as '????'. Response: Ensure the GSKit SSL provider is at the latest level of maintenance and restart the channel. AMQ9719Invalid CipherSpec for FIPS mode. Severity: 30 : Severe error Explanation: The user is attempting to start a channel on a queue manager or MQ client which has been configured to run in FIPS mode. The user has specified a CipherSpec which is not FIPS-compliant. The channel is ; in some cases its name cannot be determined and so is shown as '????'. Response: Redefine the channel to run with a FIPS-compliant CipherSpec. Alternatively, the channel may be defined with the correct CipherSpec and the queue manager or MQ client should not be running in FIPS mode; if this is the case, ensure that FIPS mode is not configured. Once the error is corrected, restart the channel. AMQ9720 QUEUE MANAGERS: Severity: 0 : Information Explanation: None. Response: None. AMQ9721 Queue Manager Name: Severity: 0 : Information Explanation: None. Response: None. AMQ9722 CLIENTS: Severity: 0 : Information Explanation: None. Response: None. AMQ9723 Client Certificate Store: Severity: 0 : Information Explanation: None. Response: None. AMQ9724 Expiry Time: Migration Status: To be migrated Password: ******** Severity: 0 : Information Explanation: None. Response: None. AMQ9725 Expiry Time: Migration Status: Failed Password: ******** Severity: 0 : Information Explanation: None. Response: None. AMQ9726A certificate failed to be migrated because it has an invalid date. The certificate's details are: [Microsoft Certificate Store], [Subject], [Issuer], [Serial Number]: . Severity: 30 : Severe error Explanation: During the migration of a certificate, the certificate's date fields have been found to be invalid. The certificate has either expired or its "from" date is later than today's date or its "to" date is earlier than the "from" date. The certificate has not been migrated. Response: If the certificate is required for migration then obtain a valid replacement before importing it into the GSKit key database . AMQ9727A certificate failed to be migrated because it has an incomplete certification path. The certificate's details are: [Microsoft Certificate Store], [Subject], [Issuer], [Serial Number]: . Severity: 30 : Severe error Explanation: During the migration of a certificate, the certificate's certification authority (signer) certificate could not be found. The certificate is therefore regarded as an orphan certificate. A copy of the certificate has been written to the file name . If file name is suffixed ".cer" then the certificate is a certification authority (signer) certificate. If file name is suffixed ".pfx" then the certificate is a personal certificate and it has a password which is the same as that specified for the GSKit key database . The certificate has not been migrated. Response: If the certificate is required for migration then ensure that a complete certification path exists in the GSKit key database before importing the certificate. AMQ9728A certificate failed to be migrated because it could not be imported into the GSKit key database . The certificate's details are: [Microsoft Certificate Store], [Subject], [Issuer], [Serial Number]: . Severity: 30 : Severe error Explanation: A certificate failed to be imported because there was a problem during the migration of the certificate. A copy of the certificate has been written to the file name . If file name is suffixed ".cer" then the certificate is a certification authority (signer) certificate. If file name is suffixed ".pfx" then the certificate is a personal certificate and it has a password which is the same as that specified for the GSKit key database . The certificate has not been migrated. Response: Refer to the previous message in the error log to determine the cause of the failure. If appropriate, refer to the Windows or GSKit reference documentation to determine the cause. AMQ9729Unable to create certificate file . Severity: 30 : Severe error Explanation: A certificate failed to be imported because there was a problem during the migration of the certificate. In addition to this first problem, a second problem occurred when trying to create a copy of the certificate by writing it to the file . The certificate is located in the Microsoft Certificate Store . The certificate is intended for the GSKit key database . If file name is suffixed ".cer" then the certificate is a certification authority (signer) certificate. If file name is suffixed ".pfx" then the certificate is a personal certificate. The certificate has not been migrated. Response: Determine the cause of the 2 problems. Refer to the previous message in the error log to determine the cause of the first failure. If appropriate, refer to the Windows or GSKit reference documentation to determine the cause. The second failure occurred during a call to the Windows 'CreateFile' function with a return code of . For this failure, check that file does not already exist and that you have authority to create this file. AMQ9730Certificate migration has completed with no failures. The number of certificates migrated was . Severity: 0 : Information Explanation: The migration of certificates from the Microsoft Certificate Store to the GSKit key database has completed and there were no migration failures. The number of certificates migrated was . Response: If any certificates were migrated, use the GSKit iKeyman GUI to verify that the GSKit key database contains all the certificates required to support the intended SSL channel. If no certificates were migrated then this is probably because contained only a default set of certification authority (signer) certificates. The default set is not migrated because the newly created GSKit key database will have its own set which will be the same or more up to date. Although there were no failures which caused certificates not to be migrated, there may have been other failures and these must be resolved otherwise the SSL channel may subsequently fail to start. Refer to the error log and check for any failures. AMQ9731The Transfer Certificates (amqtcert) command has completed. Severity: 0 : Information Response: None. AMQ9732A registry entry already exists for . Severity: 30 : Severe error Explanation: The command has been used to request automatic migration for a queue manager's or a client's Microsoft Certificate Store. However, there is already an entry in the registry for this store. If the request was for a queue manager then is the queue manager name, otherwise it is the name of the client's Microsoft Certificate Store. Response: List, and then check, the contents of the registry by running the Transfer Certificates (amqtcert) command with the options "-a -l". If it is necessary to replace the entry then firstly remove it, by using amqtcert with the "-r" option, then use amqtcert to request automatic migration. AMQ9733The request to automatically migrate certificates has completed successfully. Severity: 0 : Information Explanation: A request was made to automatically migrate SSL certificates. This request may have been made during the installation of WebSphere MQ or by using the Transfer Certificates (amqtcert) command. The request has now been performed and the migration has completed successfully. Response: Use the GSKit iKeyman GUI to verify that the GSKit key database contains all the certificates required to support the intended SSL channel. If no certificates were migrated then this is because the Microsoft Certificate Store contained only a default set of certification authority (signer) certificates. The default set is not migrated because the newly created GSKit key database will have its own set which will be the same or more up to date. AMQ9734There was a failure during the automatic migration of certificates. Severity: 30 : Severe error Explanation: A request was made to automatically migrate SSL certificates. This request may have been made during the installation of WebSphere MQ or by using the Transfer Certificates (amqtcert) command. The request has now been performed but there was a failure during the migration process. Response: Refer to previous messages in the error log to determine the cause of the failure. It may be the case that all certificates have successfully migrated and that the failure did not affect this part of the migration process. In this case, use the GSKit iKeyman GUI to verify that the GSKit key database contains all the certificates required to support the intended SSL channel. AMQ9735Certificate migration has terminated unexpectedly. A failure occured during GSKit initialization. Severity: 30 : Severe error Explanation: The certificate migration process has terminated unexpectedly. The migration requires the GSKit environment to be successfully initialized. This involves the GSKit operations of initialization, creation of the key database and stashing of the key database password. There was a failure during one of these operations. No certificates have been migrated. If the stashing of the password failed then the key database will have been created. The failure occurred during the GSKit operation and the GSKit return code was generated. Response: If the key database has been created then, after the cause of the failure has been resolved, delete it, remove the relevant registry state information and then re-try the certificate migration process. Use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ9736The library was not found. Severity: 30 : Severe error Explanation: An attempt to dynamically load the library failed because the library was not found. If this an WebSphere MQ library, it is only available on WebSphere MQ server installations and is required when the Transfer Certificates (amqtcert) command is used to perform a queue manager operation. If this a GSKit library, it should have been installed during the WebSphere MQ installation. Response: Do not use the command to perform a queue manager operation on a WebSphere MQ client-only installation. If the command has been made on a WebSphere MQ server installation, or if it is a GSKit library which is missing, then record the problem identifier, save any generated output files and then contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ9737Unable to allocate memory. Severity: 30 : Severe error Explanation: An attempt to allocate memory failed. Response: Make more memory available to the command. AMQ9738Unable to obtain the MQSSLKEYR environment variable value. Severity: 30 : Severe error Explanation: An attempt to obtain the MQSSLKEYR environment variable value failed. When using the command to specify all clients then the MQSSLKEYR environment variable must be defined with the name of a Microsoft Certificate Store file containing certificates for all clients. Response: Ensure that the MQSSLKEYR environment variable is defined with an appropriate value. AMQ9739The certificate store could not be accessed. Severity: 30 : Severe error Explanation: The certificate store could not be accessed, and failed with Windows error code . If you are using the -c parameter check that the name given to amqtcert is correct. If you are using the -m parameter check the SSLKEYR value on the queue manager specified. Response: Consult the Windows reference manual to determine the meaning of error if this value is non-zero. If the problem cannot be resolved then use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ9740The certificate store could not be opened. Severity: 30 : Severe error Explanation: The certificate store could not be opened, and failed with Windows error code . Response: Consult the Windows reference manual to determine the meaning of error if this value is non-zero. If the problem cannot be resolved then use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ9741A problem occurred during a Windows operation. Severity: 30 : Severe error Explanation: During operation , the Windows return code was generated. Response: Consult the Windows reference manual to determine the meaning of return code for operation . AMQ9742A problem occured during a GSKit operation. Severity: 30 : Severe error Explanation: During operation , the GSKit return code was generated. Response: Use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ9743A certificate failed to be migrated and failed to be logged. The certificate's details are: [Microsoft Certificate Store], [Subject], [Issuer], [Serial Number]: . Severity: 30 : Severe error Explanation: There was a problem trying to migrate a certificate to the GSKit key database . Response: Refer to the previous message in the error log to determine why the migration failed. AMQ9744No matching automatic migration registry entry. Severity: 10 : Warning Explanation: There is no automatic certificate migration entry in the registry which matches the input provided. Response: None, if the entry to be removed was correctly specified. Otherwise, input the command again with correct parameters. AMQ9745amqtcert: insufficient memory to migrate certificates. Severity: 30 : Severe error Explanation: An attempt to allocate memory failed while amqtcert was migrating certificate file .sto'. The migration did not complete successfully. Response: Do not delete .sto', but delete all other files called .*' (these were created as a result of the failed migration). Also, if you want to rerun this migration automatically, use the -r flag on amqtcert to remove the automatic migration registry entry for this .sto file. Then use the -a flag on amqtcert to create a new automatic migration registry entry for this .sto file. Make more memory available. Rerun the migration. AMQ9746File not found. Severity: 30 : Severe error Explanation: The file specified as a command argument has not been found. The characters ".sto" have been automatically appended to the file name. Response: Check that file exists and that it is specified as the absolute (rather than relative) directory path and file name (excluding the .sto suffix) of the Microsoft Certificate Store. AMQ9747Usage: amqtcert [-a] [-c [Filename | *]] [-e ExpirationTime] [-g FileName] [-i ListNumber] [-l] [-m [QMgrName | *]] [-p Password] [-r] [-u ClientLogonID] [-w FileName] Severity: 0 : Information Response: None. AMQ9748A problem occurred accessing the Windows registry. Severity: 30 : Severe error Explanation: An attempt to access a key or value or data field in the Windows registry key failed. The failure may be due to part of the registry being in an invalid state or may be due to insufficient authority to access that part. The WebSphere MQ error recording routine has been called. Response: If includes the name of a Windows call, consult the Windows reference manual to determine the meaning of status for that call. Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ9749Invalid combination of command arguments. Severity: 30 : Severe error Explanation: The command syntax is incorrect because of an invalid combination of arguments. Response: Re-try the command using a valid combination of arguments. AMQ9750File already exists. Severity: 30 : Severe error Explanation: The file cannot be created because it already exists. Response: Ensure that the file does not exist in the directory. If necessary, make a copy of the file before renaming or moving or deleting it. AMQ9751You are not authorized to perform the requested operation. Severity: 30 : Severe error Explanation: You tried to issue a command for which you are not authorized. Response: Contact your system administrator to perform the command for you or to request authority to perform the command. AMQ9752A certificate failed to be migrated because a Windows operation failed. The certificate's details are: [Microsoft Certificate Store], [Subject], [Issuer], [Serial Number]: . Severity: 30 : Severe error Explanation: A personal certificate could not be migrated because there was a failure during the Windows operation with a return code of . A personal certificate is exported, with its private key data, from the Microsoft Certificate Store prior to being imported into the GSKit key database. The failure occurred during the export and is probably due to a problem with accessing or using the private key data assoicated with the personal certificate. Response: Check that the private key data is available and that you have authority to access it. Consult the Windows reference manual to determine the meaning of return code for operation . AMQ9753File is empty. Severity: 30 : Severe error Explanation: The file cannot be used because it is empty. Response: Ensure that the correct file has been used and if necessary investigate the reason for it being empty. AMQ9754A certificate failed to be migrated because a GSKit operation failed. The certificate's details are: [Microsoft Certificate Store], [Subject], [Issuer], [Serial Number]: . Severity: 30 : Severe error Explanation: During operation , the GSKit return code was generated. Response: Use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved. AMQ9755Certificate migration has completed with some failures. The number of certificates migrated was . Severity: 0 : Information Explanation: The migration of certificates from the Microsoft Certificate Store to the GSKit key database has completed but there has been one or more failures. The number of certificates migrated was . Response: If any certificates were migrated, use the GSKit iKeyman GUI to verify that the GSKit key database contains all the certificates required to support the intended SSL channel. The failures must be resolved otherwise the SSL channel may subsequently fail to start. Refer to previous messages in the error log to determine the cause of such failures. AMQ9756The number of certificates in the Microsoft Certificate Store is . Severity: 0 : Information Explanation: Provides a count of the number of certificates in the Microsoft Certificate Store . Response: None. AMQ9757 Certificate Severity: 0 : Information Explanation: None. Response: None. AMQ9758Subject: Severity: 0 : Information Explanation: None. Response: None. AMQ9759Issuer: Severity: 0 : Information Explanation: None. Response: None. AMQ9760Valid From: to Severity: 0 : Information Explanation: None. Response: None. AMQ9761Certificate Usage: Severity: 0 : Information Explanation: None. Response: None. AMQ9762Certificate Usage: Severity: 0 : Information Explanation: None. Response: None. AMQ9763Certificate Type: Personal Severity: 0 : Information Explanation: None. Response: None. AMQ9764Certificate Type: Signer Severity: 0 : Information Explanation: None. Response: None. AMQ9765Personal certificate not found for the command option "-i ". Severity: 30 : Severe error Explanation: The Transfer Certificates (amqtcert) command was executed using the "-i ListNumber" option with a value of . However, no personal certificate was found which corresponded to this value. Certificate migration has failed and no certificates were migrated. Response: Check that the option value corresponds to a correctly identified personal certificate. If it is not correct then run the command using the "-l List" option to determine the correct number. A GSKit key database, and its associated key database files, was created when the command was run using the "-i ListNumber" option. The database and associated files must be deleted before re-trying the command with the "-i" option. AMQ9766A failure occurred creating the GSKit key database . Severity: 30 : Severe error Explanation: GSKit was unable to create the key database and its associated files. During the GSKit operation , the return code was generated. This is probably due to insufficient authority or to insufficient disk space being available. Response: Check that you have sufficient authority and that there is sufficient disk space available. AMQ9767Usage: strmqikm [iKeymanWorkingDirectory] Severity: 0 : Information Response: None. AMQ9768Directory not found. Severity: 30 : Severe error Explanation: The directory specified as a command argument has not been found. Response: Check that the directory exists and that it is specified as an absolute (rather than relative) directory path. AMQ9769Usage: runmqckm -keydb -changepw Change the password for a key database -convert Convert the format of a key database -create Create a key database -delete Delete a key database -stashpw Stash the password of a key database into a file -list Currently supported types of key database. -cert -add Add a CA Certificate -create Create a self-signed certificate -delete Delete a certificate -details Show the details of a specific certificate -export Export a personal certificate and associated private key into a PKCS12 file or a key database -extract Extract a certificate from a key database -getdefault Show the default personal certificate -import Import a certificate from a key database or a PKCS12 file -list List certificates in a key database -modify Modify a certificate (NOTE: the only field that my be modified is the trust field) -receive Receive a certificate -setdefault Set the default personal certificate -sign Sign a certificate -certreq -create Create a certificate request -delete Delete a certificate request from a certificate request database -details Show the details of a specific certificate request -extract Extract a certificate from a certificate request database -list List all certificate requests in a certificate request database -recreate Recreate a certificate request -version Display ikeycmd version information -help Display this help text Severity: 0 : Information Response: None. AMQ9913The specified local address cannot be resolved to an IP address. The return code is . Severity: 30 : Severe error Explanation: An attempt to resolve the local address hostname to an IP address has failed. Response: Check that the local address hostname is correct and has an entry in the DNS database. AMQ9914The type of local address specified is incompatible with the IP protocol () used. Severity: 30 : Severe error Explanation: An attempt to use a local address that is incompatible with the IP protocol used. Response: Make sure that the local address specified is of the same type (IPv4 or IPV6) as the IP Protocol. AMQ9915The IP protocol is not present on the system. Severity: 30 : Severe error Explanation: An attempt to use an IP protocol that is not present on the system has been made. Response: Install the required IP protocol or use an IP protocol that is available on the system. AMQ9920A SOAP Exception has been thrown. Severity: 30 : Severe error Explanation: A SOAP method encountered a problem and has thrown an exception. Details of the exception are: Response: Investigate why the SOAP method threw the exception. AMQ9921An error was encountered writing to the Dead Letter Queue. Severity: 30 : Severe error Explanation: An error was encountered when an attempt was made to write a message to Dead Letter Queue . The message was . Response: Ensure that Dead Letter Queue exists and is put enabled. Ensure that the Queue Manager attribute DEADQ is set up correctly. Resend the SOAP message. AMQ9922Maximum wait time exceeded on queue . Severity: 30 : Severe error Explanation: The maximum time waiting for a message to arrive on queue has been exceeded. Response: Ensure that the queue is not put inhibited. Ensure that messages are being written to the queue. AMQ9923Insufficient parameters on command. Severity: 30 : Severe error Explanation: The SOAP command has been issued with insufficient paramaters. Response: Supply the correct number of parameters and reissue the command. AMQ9924Usage: amqwSOAPNETListener -u wmqUri [-w WebServiceDirectory] [-n MaxThreads] [-d StayAlive] [-i IdContext] [-x TransactionalControl] [-a Integrity] [-? ThisHelp] Severity: 0 : Information Explanation: This shows the correct usage. Response: None. AMQ9925Cannot connect to queue manager . Severity: 30 : Severe error Explanation: A SOAP application or the SOAP listener cannot connect to the queue manager using bindings. Response: Ensure the bindings are set to the correct value and that the queue manager exists. Check any error messages from the Java MQQueueManager class. AMQ9926Null SOAP action specified in a received SOAP message. Severity: 30 : Severe error Explanation: A NULL soap action has been specified in the SOAP message . The message will not be processed. Response: Include the appropriate SOAP action in the SOAP message. AMQ9927MQ queue backout threshold exceeded. Severity: 30 : Severe error Explanation: The WebSphere MQ backout threshold value has been exceeded for queue , processing message . Response: Correct the backout threshold value for queue and resend the SOAP message. AMQ9928Target service or URI is missing from a SOAP message. Severity: 30 : Severe error Explanation: The target service or the target URI is missing from SOAP message . Response: Supply a target service or the target URI in the SOAP message. AMQ9929Message backout for message () failed. Severity: 30 : Severe error Explanation: Backout for a message has failed. Response: Investigate the reason for the backout failure. AMQ9930Required Option missing from command. Severity: 30 : Severe error Explanation: The SOAP command was issued with manadatory option missing. Response: Reissue the SOAP command supplying the missing option. AMQ9931Invalid value specified for option . Severity: 30 : Severe error Explanation: THE SOAP command was issued with an invalid value for an option. Response: Reissue the SOAP command supplying the correct option value. AMQ9932Application host class not found Severity: 30 : Severe error Explanation: Application host class has not been found. Response: Specify the correct application host class in the SOAP message. AMQ9933Options and are mutually exclusive Severity: 30 : Severe error Explanation: The SOAP command was issued with incompatible options and . Response: Reissue the SOAP command supplying compatible options. AMQ9934Could not parse URL . MQCC_FAILED(2) MQRC_SOAP_URL_ERROR(2212). Severity: 30 : Severe error Explanation: .Could not parse URL .MQCC_FAILED(2) MQRC_SOAP_URL_ERROR(2212). Response: Correct the URL and retry. AMQ9935Illegal URL . MQCC_FAILED(2) MQRC_SOAP_URL_ERROR(2212). Severity: 30 : Severe error Explanation: .The URL failed validation.. MQCC_FAILED(2) MQRC_SOAP_URL_ERROR(2212). Response: Correct the URL and retry. AMQ9936Cannot get connection using bindings. MQCC_FAILED(2) MQRC_CONNECTION_ERROR(2273). Severity: 30 : Severe error Explanation: .Cannot get connection using bindings. MQCC_FAILED(2) MQRC_CONNECTION_ERROR(2273). Response: Check that the queue manager is available and running. AMQ9937The asyncResult is null. MQCC_FAILED(2) MQRC_SOAP_DOTNET_ERROR.(2210). Severity: 30 : Severe error Explanation: .The asyncResult is null. MQCC_FAILED(2) MQRC_SOAP_DOTNET_ERROR.(2210). Response: Check why the SOAP responses are not being received. AMQ9938SOAP/WMQ Timeout. Severity: 30 : Severe error Explanation: .The MQGET operation timed out. MQCC_FAILED(2) MQRC_SOAP_DOTNET_ERROR.(2210). Response: Check why the SOAP responses are not being received. MQCC_FAILED(2) MQRC_SOAP_DOTNET_ERROR.(2210). AMQ9939SOAP/WMQ Error. MQCC_FAILED(2) MQRC_SOAP_DOTNET_ERROR.(2210). Severity: 30 : Severe error Explanation: .A SOAP error was detected. MQCC_FAILED(2) MQRC_SOAP_DOTNET_ERROR.(2210). Response: Check the WMQ logs for the reason of the failure. AMQ9940Report message returned in MQWebResponse. MQCC_FAILED(2) MQRC_SOAP_DOTNET_ERROR.(2210). Severity: 30 : Severe error Explanation: .Report message returned in MQWebResponse. MQCC_FAILED(2) MQRC_SOAP_DOTNET_ERROR.(2210). Response: Check the report message for the reason of the failure. AMQ9941No RFH2 header recognised. MQCC_FAILED(2) MQRCCF_MD_FORMAT_ERROR(3023). Severity: 30 : Severe error Explanation: .No RFH2 header recognised. MQCC_FAILED(2) MQRCCF_MD_FORMAT_ERROR(3023). Response: Check why the message is being sent with no RFH2 header. AMQ9942Message format is not MQFMT_NONE. MQCC_FAILED(2) MQRC_RFH_FORMAT_ERROR(2421). Severity: 30 : Severe error Explanation: .Message format is not MQFMT_NONE. MQCC_FAILED(2) MQRC_RFH_FORMAT_ERROR(2421). Response: Correct the message format and retry. AMQ9943Unrecognised RFH2 version. MQCC_FAILED(2) MQRC_RFH_FORMAT_ERROR(2421). Severity: 30 : Severe error Explanation: .Unrecognised RFH2 version. MQCC_FAILED(2) MQRC_RFH_FORMAT_ERROR(2421). Response: Correct the version in the RFH2 message and retry. AMQ9944Invalid RFH2 length. MQCC_FAILED(2) MQRC_RFH_FORMAT_ERROR(2421). Severity: 30 : Severe error Explanation: .Invalid RFH2 length. MQCC_FAILED(2) MQRC_RFH_FORMAT_ERROR(2421). Response: Correct the RFH2 length and retry. AMQ9945Illegal RFH2 folder length. MQCC_FAILED(2) MQRC_RFH_FORMAT_ERROR(2421). Severity: 30 : Severe error Explanation: .Illegal RFH2 folder length. MQCC_FAILED(2) MQRC_RFH_FORMAT_ERROR(2421). Response: Correct the RFH2 message and retry. AMQ9946Invalid actual message length. MQCC_FAILED(2) MQRC_RFH_FORMAT_ERROR(2421). Severity: 30 : Severe error Explanation: .Invalid actual message length. MQCC_FAILED(2) MQRC_RFH_FORMAT_ERROR(2421). Response: Correct the RFH2 message and retry. AMQ9947Illegal RFH2 Folder . MQCC_FAILED(2) MQRC_RFH_FORMAT_ERROR(2421). Severity: 30 : Severe error Explanation: .Illegal RFH2 Folder . MQCC_FAILED(2) MQRC_RFH_FORMAT_ERROR(2421). Response: Correct the RFH2 folder syntax/format and retry. AMQ9948Backout Threshold exceeded. MQCC_FAILED(2) MQRC_BACKOUT_THRESHOLD_REACHED(2362). Severity: 30 : Severe error Explanation: .Backout Threshold exceeded. MQCC_FAILED(2) MQRC_BACKOUT_THRESHOLD_REACHED(2362). Response: Correct the backout threshold limit and retry. AMQ9949 missing from RFH2. MQCC_FAILED(2) MQRC_RFH_PARM_MISSING(2339). Severity: 30 : Severe error Explanation: . missing from RFH2. MQCC_FAILED(2) MQRC_RFH_PARM_MISSING(2339). Response: Correct the RFH2 message and retry. AMQ9950Target service missing from SOAP URL. MQCC_FAILED(2) MQRC_SOAP_URL_ERROR(2212). Severity: 30 : Severe error Explanation: .Target service missing from SOAP URL. MQCC_FAILED(2) MQRC_SOAP_URL_ERROR(2212). Response: Correct the URL and retry. AMQ9951Asynchronous request queued successfully. MQCC_OK(0). Severity: 30 : Severe error Explanation: .Asynchronous request queued successfully. MQCC_OK(0). Response: Wait for response if any is expected. AMQ9952Unexpected message type received. MQCC_FAILED(2) MQRC_UNEXPECTED_MSG_TYPE.(2215). Severity: 30 : Severe error Explanation: .A message of the wrong type was received; for instance, a report message was received when one had not been requested. Response: If you are running WMQ SOAP using the IBM supplied SOAP/WMQ sender, please contact IBM. If you are running WMQ SOAP using a bespoke sender, please check that the SOAP/WMQ request message has the correct options. AMQ9953Either the ContentType or the TransportVersion in the RFH2 header have the wrong value. MQCC_FAILED(2) MQRC_RFH_HEADER_FIELD_ERROR(2228) Severity: 30 : Severe error Explanation: .Either the ContentType or the TransportVersion in the RFH2 header have the wrong value. MQCC_FAILED(2) MQRC_RFH_HEADER_FIELD_ERROR(2228) Response: Correct the message format and retry. AMQ9954ViaTran.Redirect called out of transaction MQCC_FAILED(2) MQRC_SOAP_DOTNET_ERROR(2410) Severity: 30 : Severe error Explanation: .ViaTran.Redirect called out of transaction MQCC_FAILED(2) MQRC_SOAP_DOTNET_ERROR(2410) Response: Make sure ViaTran.Redirect is only called in a transaction. AMQ9955Usage: amqswsdl [?] Uri inputFile outputFile Severity: 0 : Information Explanation: This shows the correct usage. Response: None. AMQ9990 (iSeries)Keyword not valid for this command or the command is incomplete. Severity: 40 : Stop Error Explanation: The command is incomplete, or an invalid keyword was specified, or the parameter value of the keyword was not specified. Response: Complete the command, or correct the keyword, or add the parameter value, and then try the command again. AMQ9991 (iSeries)The value specified is not allowed by the command. Severity: 40 : Stop Error Explanation: not valid for parameter . Response: Enter one of the values that is defined for the parameter, and try the command again. More information on parameters and commands can be found in the CL reference manual or the appropriate licensed program manual. AMQ9992 (iSeries)A matching parenthesis not found. Severity: 40 : Stop Error Explanation: A matching left or right parenthesis is missing. Response: Add the missing parenthesis or remove the extra parenthesis. AMQ9999Channel program ended abnormally. Severity: 30 : Severe error Explanation: Channel program ended abnormally. Response: Look at previous error messages for channel program in the error files to determine the cause of the failure. Reason code list: ================= 0 (X'0000')MQRC_NONE Explanation: The call completed normally. The completion code (CompCode) is MQCC_OK. Completion Code: MQCC_OK Programmer Response: None. 900 (X'0384')MQRC_APPL_FIRST Explanation: This is the lowest value for an application-defined reason code returned by a data-conversion exit. Data-conversion exits can return reason codes in the range MQRC_APPL_FIRST through MQRC_APPL_LAST to indicate particular conditions that the exit has detected. Completion Code: MQCC_WARNING or MQCC_FAILED Programmer Response: As defined by the writer of the data-conversion exit. 999 (X'03E7')MQRC_APPL_LAST Explanation: This is the highest value for an application-defined reason code returned by a data-conversion exit. Data-conversion exits can return reason codes in the range MQRC_APPL_FIRST through MQRC_APPL_LAST to indicate particular conditions that the exit has detected. Completion Code: MQCC_WARNING or MQCC_FAILED Programmer Response: As defined by the writer of the data-conversion exit. 2001 (X'07D1')MQRC_ALIAS_BASE_Q_TYPE_ERROR Explanation: An MQOPEN or MQPUT1 call was issued specifying an alias queue as the destination, but the BaseQName in the alias queue definition resolves to a queue that is not a local queue, a local definition of a remote queue, or a cluster queue. Completion Code: MQCC_FAILED Programmer Response: Correct the queue definitions. 2002 (X'07D2')MQRC_ALREADY_CONNECTED Explanation: An MQCONN or MQCONNX call was issued, but the application is already connected to the queue manager. On z/OS, this reason code occurs for batch and IMS applications only; it does not occur for CICS applications. On AIX, HP-UX, i5/OS, Solaris, Windows, this reason code occurs if the application attempts to create a nonshared handle when a nonshared handle already exists for the thread. A thread can have no more than one nonshared handle. On Windows, MTS objects do not receive this reason code, as additional connections to the queue manager are allowed. Completion Code: MQCC_WARNING Programmer Response: None. The Hconn parameter returned has the same value as was returned for the previous MQCONN or MQCONNX call. An MQCONN or MQCONNX call that returns this reason code does not mean that an additional MQDISC call must be issued in order to disconnect from the queue manager. If this reason code is returned because the application has been called in a situation where the connect has already been done, a corresponding MQDISC should not be issued, because this will cause the application that issued the original MQCONN or MQCONNX call to be disconnected as well. 2003 (X'07D3')MQRC_BACKED_OUT Explanation: The current unit of work encountered a fatal error or was backed out. This occurs in the following cases: On an MQCMIT or MQDISC call, when the commit operation has failed and the unit of work has been backed out. All resources that participated in the unit of work have been returned to their state at the start of the unit of work. The MQCMIT or MQDISC call completes with MQCC_WARNING in this case. On z/OS, this reason code occurs only for batch applications. On an MQGET, MQPUT, or MQPUT1 call that is operating within a unit of work, when the unit of work has already encountered an error that prevents the unit of work being committed (for example, when the log space is exhausted). The application must issue the appropriate call to back out the unit of work. (For a unit of work coordinated by the queue manager, this call is the MQBACK call, although the MQCMIT call has the same effect in these circumstances.) The MQGET, MQPUT, or MQPUT1 call completes with MQCC_FAILED in this case. On z/OS, this case does not occur. Completion Code: MQCC_WARNING or MQCC_FAILED Programmer Response: Check the returns from previous calls to the queue manager. For example, a previous MQPUT call may have failed. 2004 (X'07D4')MQRC_BUFFER_ERROR Explanation: The Buffer parameter is not valid for one of the following reasons: The parameter pointer is not valid. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) The parameter pointer points to storage that cannot be accessed for the entire length specified by BufferLength. For calls where Buffer is an output parameter: the parameter pointer points to read-only storage. Completion Code: MQCC_FAILED Programmer Response: Correct the parameter. 2005 (X'07D5')MQRC_BUFFER_LENGTH_ERROR Explanation: The BufferLength parameter is not valid, or the parameter pointer is not valid. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) This reason can also be returned to an MQ client program on the MQCONN or MQCONNX call if the negotiated maximum message size for the channel is smaller than the fixed part of any call structure. This reason should also be returned by the MQZ_ENUMERATE_AUTHORITY_DATA installable service component when the AuthorityBuffer parameter is too small to accommodate the data to be returned to the invoker of the service component. Completion Code: MQCC_FAILED Programmer Response: Specify a value that is zero or greater. For the mqAddString and mqSetString calls, the special value MQBL_NULL_TERMINATED is also valid. 2006 (X'07D6')MQRC_CHAR_ATTR_LENGTH_ERROR Explanation: CharAttrLength is negative (for MQINQ or MQSET calls), or is not large enough to hold all selected attributes (MQSET calls only). This reason also occurs if the parameter pointer is not valid. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) Completion Code: MQCC_FAILED Programmer Response: Specify a value large enough to hold the concatenated strings for all selected attributes. 2007 (X'07D7')MQRC_CHAR_ATTRS_ERROR Explanation: CharAttrs is not valid. The parameter pointer is not valid, or points to read-only storage for MQINQ calls or to storage that is not as long as implied by CharAttrLength. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) Completion Code: MQCC_FAILED Programmer Response: Correct the parameter. 2008 (X'07D8')MQRC_CHAR_ATTRS_TOO_SHORT Explanation: For MQINQ calls, CharAttrLength is not large enough to contain all of the character attributes for which MQCA_* selectors are specified in the Selectors parameter. The call still completes, with the CharAttrs parameter string filled in with as many character attributes as there is room for. Only complete attribute strings are returned: if there is insufficient space remaining to accommodate an attribute in its entirety, that attribute and subsequent character attributes are omitted. Any space at the end of the string not used to hold an attribute is unchanged. An attribute that represents a set of values (for example, the namelist Names attribute) is treated as a single entity--either all of its values are returned, or none. Completion Code: MQCC_WARNING Programmer Response: Specify a large enough value, unless only a subset of the values is needed. 2009 (X'07D9')MQRC_CONNECTION_BROKEN Explanation: Connection to the queue manager has been lost. This can occur because the queue manager has ended. If the call is an MQGET call with the MQGMO_WAIT option, the wait has been canceled. All connection and object handles are now invalid. For MQ client applications, it is possible that the call did complete successfully, even though this reason code is returned with a CompCode of MQCC_FAILED. Completion Code: MQCC_FAILED Programmer Response: Applications can attempt to reconnect to the queue manager by issuing the MQCONN or MQCONNX call. It may be necessary to poll until a successful response is received. On z/OS for CICS applications, it is not necessary to issue the MQCONN or MQCONNX call, because CICS applications are connected automatically. Any uncommitted changes in a unit of work should be backed out. A unit of work that is coordinated by the queue manager is backed out automatically. 2010 (X'07DA')MQRC_DATA_LENGTH_ERROR Explanation: The DataLength parameter is not valid. Either the parameter pointer is not valid, or it points to read-only storage. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) This reason can also be returned to an MQ client program on the MQGET, MQPUT, or MQPUT1 call, if the BufferLength parameter exceeds the maximum message size that was negotiated for the client channel. Completion Code: MQCC_FAILED Programmer Response: Correct the parameter. If the error occurs for an MQ client program, also check that the maximum message size for the channel is big enough to accommodate the message being sent; if it is not big enough, increase the maximum message size for the channel. 2011 (X'07DB')MQRC_DYNAMIC_Q_NAME_ERROR Explanation: On the MQOPEN call, a model queue is specified in the ObjectName field of the ObjDesc parameter, but the DynamicQName field is not valid, for one of the following reasons: DynamicQName is completely blank (or blank up to the first null character in the field). Characters are present that are not valid for a queue name. An asterisk is present beyond the 33rd position (and before any null character). An asterisk is present followed by characters that are not null and not blank. This reason code can also sometimes occur when a server application opens the reply queue specified by the ReplyToQ and ReplyToQMgr fields in the MQMD of a message that the server has just received. In this case the reason code indicates that the application that sent the original message placed incorrect values into the ReplyToQ and ReplyToQMgr fields in the MQMD of the original message. Completion Code: MQCC_FAILED Programmer Response: Specify a valid name. 2012 (X'07DC')MQRC_ENVIRONMENT_ERROR Explanation: The call is not valid for the current environment. 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 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 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. On HP OpenVMS, OS/2, i5/OS, 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 an MQ client environment. An MQXCLWLN call was issued, but the call did not originate from a cluster workload exit. Completion Code: MQCC_FAILED Programmer Response: Do one of the following (as appropriate): 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. 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. In the other environments: Link the application with the correct libraries (threaded or nonthreaded). Remove from the application the call that is not supported. 2013 (X'07DD')MQRC_EXPIRY_ERROR Explanation: On an MQPUT or MQPUT1 call, the value specified for the Expiry field in the message descriptor MQMD is not valid. Completion Code: MQCC_FAILED Programmer Response: Specify a value that is greater than zero, or the special value MQEI_UNLIMITED. 2014 (X'07DE')MQRC_FEEDBACK_ERROR Explanation: On an MQPUT or MQPUT1 call, the value specified for the Feedback field in the message descriptor MQMD is not valid. The value is not MQFB_NONE, and is outside both the range defined for system feedback codes and the range defined for application feedback codes. Completion Code: MQCC_FAILED Programmer Response: Specify MQFB_NONE, or a value in the range MQFB_SYSTEM_FIRST through MQFB_SYSTEM_LAST, or MQFB_APPL_FIRST through MQFB_APPL_LAST. 2016 (X'07E0')MQRC_GET_INHIBITED Explanation: MQGET calls are currently inhibited for the queue, or for the queue to which this queue resolves. Completion Code: MQCC_FAILED Programmer Response: If the system design allows get requests to be inhibited for short periods, retry the operation later. 2017 (X'07E1')MQRC_HANDLE_NOT_AVAILABLE Explanation: An MQOPEN or MQPUT1 call was issued, but the maximum number of open handles allowed for the current task has already been reached. Be aware that when a distribution list is specified on the MQOPEN or MQPUT1 call, each queue in the distribution list uses one handle. On z/OS, "task" means a CICS task, a z/OS task, or an IMS-dependent region. Completion Code: MQCC_FAILED Programmer Response: Check whether the application is issuing MQOPEN calls without corresponding MQCLOSE calls. If it is, modify the application to issue the MQCLOSE call for each open object as soon as that object is no longer needed. Also check whether the application is specifying a distribution list containing a large number of queues that are consuming all of the available handles. If it is, increase the maximum number of handles that the task can use, or reduce the size of the distribution list. The maximum number of open handles that a task can use is given by the MaxHandles queue manager attribute. 2018 (X'07E2')MQRC_HCONN_ERROR Explanation: The connection handle Hconn is not valid, for one of the following reasons: The parameter pointer is not valid, or (for the MQCONN or MQCONNX call) points to read-only storage. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) The value specified was not returned by a preceding MQCONN or MQCONNX call. The value specified has been made invalid by a preceding MQDISC call. The handle is a shared handle that has been made invalid by another thread issuing the MQDISC call. The handle is a shared handle that is being used on the MQBEGIN call (only nonshared handles are valid on MQBEGIN). The handle is a nonshared handle that is being used a thread that did not create the handle. The call was issued in the MTS environment in a situation where the handle is not valid (for example, passing the handle between processes or packages; note that passing the handle between library packages is supported). Completion Code: MQCC_FAILED Programmer Response: Ensure that a successful MQCONN or MQCONNX call is performed for the queue manager, and that an MQDISC call has not already been performed for it. Ensure that the handle is being used within its valid scope (see the description of MQCONN in the WebSphere MQ Application Programming Guide). On z/OS, also check that the application has been linked with the correct stub; this is CSQCSTUB for CICS applications, CSQBSTUB for batch applications, and CSQQSTUB for IMS applications. Also, the stub used must not belong to a release of the queue manager that is more recent than the release on which the application will run. 2019 (X'07E3')MQRC_HOBJ_ERROR Explanation: The object handle Hobj is not valid, for one of the following reasons: The parameter pointer is not valid, or (for the MQOPEN call) points to read-only storage. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) The value specified was not returned by a preceding MQOPEN call. The value specified has been made invalid by a preceding MQCLOSE call. The handle is a shared handle that has been made invalid by another thread issuing the MQCLOSE call. The handle is a nonshared handle that is being used by a thread that did not create the handle. The call is MQGET or MQPUT, but the object represented by the handle is not a queue. Completion Code: MQCC_FAILED Programmer Response: Ensure that a successful MQOPEN call is performed for this object, and that an MQCLOSE call has not already been performed for it. Ensure that the handle is being used within its valid scope (see the description of MQOPEN in the WebSphere MQ Application Programming Guide). 2020 (X'07E4')MQRC_INHIBIT_VALUE_ERROR Explanation: On an MQSET call, the value specified for either the MQIA_INHIBIT_GET attribute or the MQIA_INHIBIT_PUT attribute is not valid. Completion Code: MQCC_FAILED Programmer Response: Specify a valid value for the InhibitGet or InhibitPut queu attribute. 2021 (X'07E5')MQRC_INT_ATTR_COUNT_ERROR Explanation: On an MQINQ or MQSET call, the IntAttrCount parameter is negative (MQINQ or MQSET), or smaller than the number of integer attribute selectors (MQIA_*) specified in the Selectors parameter (MQSET only). This reason also occurs if the parameter pointer is not valid. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) Completion Code: MQCC_FAILED Programmer Response: Specify a value large enough for all selected integer attributes. 2022 (X'07E6')MQRC_INT_ATTR_COUNT_TOO_SMALL Explanation: On an MQINQ call, the IntAttrCount parameter is smaller than the number of integer attribute selectors (MQIA_*) specified in the Selectors parameter. The call completes with MQCC_WARNING, with the IntAttrs array filled in with as many integer attributes as there is room for. Completion Code: MQCC_WARNING Programmer Response: Specify a large enough value, unless only a subset of the values is needed. 2023 (X'07E7')MQRC_INT_ATTRS_ARRAY_ERROR Explanation: On an MQINQ or MQSET call, the IntAttrs parameter is not valid. The parameter pointer is not valid (MQINQ and MQSET), or points to read-only storage or to storage that is not as long as indicated by the IntAttrCount parameter (MQINQ only). (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) Completion Code: MQCC_FAILED Programmer Response: Correct the parameter. 2024 (X'07E8')MQRC_SYNCPOINT_LIMIT_REACHED Explanation: An MQGET, MQPUT, or MQPUT1 call failed because it would have caused the number of uncommitted messages in the current unit of work to exceed the limit defined for the queue manager (see the MaxUncommittedMsgs queue-manager attribute). The number of uncommitted messages is the sum of the following since the start of the current unit of work: Messages put by the application with the MQPMO_SYNCPOINT option Messages retrieved by the application with the MQGMO_SYNCPOINT option Trigger messages and COA report messages generated by the queue manager for messages put with the MQPMO_SYNCPOINT option COD report messages generated by the queue manager for messages retrieved with the MQGMO_SYNCPOINT option On Compaq NonStop Kernel, this reason code occurs when the maximum number of I/O operations in a single TM/MP transaction has been exceeded. Completion Code: MQCC_FAILED Programmer Response: Check whether the application is looping. If it is not, consider reducing the complexity of the application. Alternatively, increase the queue-manager limit for the maximum number of uncommitted messages within a unit of work. On z/OS, the limit for the maximum number of uncommitted messages can be changed by using the ALTER QMGR command. On i5/OS, the limit for the maximum number of uncommitted messages can be changed by using the CHGMQM command. On Compaq NonStop Kernel, the application should cancel the transaction and retry with a smaller number of operations in the unit of work. See the MQSeries for Tandem NonStop Kernel System Management Guide for more details. 2025 (X'07E9')MQRC_MAX_CONNS_LIMIT_REACHED Explanation: The MQCONN or MQCONNX call was rejected because the maximum number of concurrent connections has been exceeded. On z/OS, connection limits are applicable only to TSO and batch requests. The limits are determined by the customer using the following parameters of the CSQ6SYSP macro: For TSO: IDFORE For batch: IDBACK For more information, see the WebSphere MQ for z/OS System Setup Guide. On HP OpenVMS, OS/2, i5/OS, Compaq NonStop Kernel, UNIX systems, and Windows, this reason code can also occur on the MQOPEN call. When using Java applications, a limit to the number of concurrent connections may be defined by the connection manager. Completion Code: MQCC_FAILED Programmer Response: Either increase the size of the appropriate parameter value, or reduce the number of concurrent connections. 2026 (X'07EA')MQRC_MD_ERROR Explanation: The MQMD structure is not valid, for one of the following reasons: The StrucId field is not MQMD_STRUC_ID. The Version field specifies a value that is not valid or not supported. The parameter pointer is not valid. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) The queue manager cannot copy the changed structure to application storage, even though the call is successful. This can occur, for example, if the pointer points to read-only storage. Completion Code: MQCC_FAILED Programmer Response: Ensure that input fields in the MQMD structure are set correctly. 2027 (X'07EB')MQRC_MISSING_REPLY_TO_Q Explanation: On an MQPUT or MQPUT1 call, the ReplyToQ field in the message descriptor MQMD is blank, but one or both of the following is true: A reply was requested (that is, MQMT_REQUEST was specified in the MsgType field of the message descriptor). A report message was requested in the Report field of the message descriptor. Completion Code: MQCC_FAILED Programmer Response: Specify the name of the queue to which the reply message or report message is to be sent. 2029 (X'07ED')MQRC_MSG_TYPE_ERROR Explanation: Either: On an MQPUT or MQPUT1 call, the value specified for the MsgType field in the message descriptor (MQMD) is not valid. A message processing program received a message that does not have the expected message type. For example, if the WebSphere MQ command server receives a message which is not a request message (MQMT_REQUEST) then it rejects the request with this reason code. Completion Code: MQCC_FAILED Programmer Response: Specify a valid value for the MsgType field. In the case where a request is rejected by a message processing program, refer to the documentation for that program for details of the message types that it supports. 2030 (X'07EE')MQRC_MSG_TOO_BIG_FOR_Q Explanation: An MQPUT or MQPUT1 call was issued to put a message on a queue, but the message was too long for the queue and MQMF_SEGMENTATION_ALLOWED was not specified in the MsgFlags field in MQMD. If segmentation is not allowed, the length of the message cannot exceed the lesser of the queue MaxMsgLength attribute and queue-manager MaxMsgLength attribute. On z/OS, the queue manager does not support the segmentation of messages; if MQMF_SEGMENTATION_ALLOWED is specified, it is accepted but ignored. This reason code can also occur when MQMF_SEGMENTATION_ALLOWED is specified, but the nature of the data present in the message prevents the queue manager splitting it into segments that are small enough to place on the queue: For a user-defined format, the smallest segment that the queue manager can create is 16 bytes. For a built-in format, the smallest segment that the queue manager can create depends on the particular format, but is greater than 16 bytes in all cases other than MQFMT_STRING (for MQFMT_STRING the minimum segment size is 16 bytes). MQRC_MSG_TOO_BIG_FOR_Q can also occur in the Feedback field in the message descriptor of a report message; in this case it indicates that the error was encountered by a message channel agent when it attempted to put the message on a remote queue. Completion Code: MQCC_FAILED Programmer Response: Check whether the BufferLength parameter is specified correctly; if it is, do one of the following: Increase the value of the queue's MaxMsgLength attribute; the queue-manager's MaxMsgLength attribute may also need increasing. Break the message into several smaller messages. Specify MQMF_SEGMENTATION_ALLOWED in the MsgFlags field in MQMD; this will allow the queue manager to break the message into segments. 2031 (X'07EF')MQRC_MSG_TOO_BIG_FOR_Q_MGR Explanation: An MQPUT or MQPUT1 call was issued to put a message on a queue, but the message was too long for the queue manager and MQMF_SEGMENTATION_ALLOWED was not specified in the MsgFlags field in MQMD. If segmentation is not allowed, the length of the message cannot exceed the lesser of the queue-manager MaxMsgLength attribute and queue MaxMsgLength attribute. This reason code can also occur when MQMF_SEGMENTATION_ALLOWED is specified, but the nature of the data present in the message prevents the queue manager splitting it into segments that are small enough for the queue-manager limit: For a user-defined format, the smallest segment that the queue manager can create is 16 bytes. For a built-in format, the smallest segment that the queue manager can create depends on the particular format, but is greater than 16 bytes in all cases other than MQFMT_STRING (for MQFMT_STRING the minimum segment size is 16 bytes). MQRC_MSG_TOO_BIG_FOR_Q_MGR can also occur in the Feedback field in the message descriptor of a report message; in this case it indicates that the error was encountered by a message channel agent when it attempted to put the message on a remote queue. This reason also occurs if a channel, through which the message is to pass, has restricted the maximum message length to a value that is actually less than that supported by the queue manager, and the message length is greater than this value. On z/OS, this return code is issued only if you are using CICS for distributed queuing. Otherwise, MQRC_MSG_TOO_BIG_FOR_CHANNEL is issued. Completion Code: MQCC_FAILED Programmer Response: Check whether the BufferLength parameter is specified correctly; if it is, do one of the following: Increase the value of the queue-manager's MaxMsgLength attribute; the queue's MaxMsgLength attribute may also need increasing. Break the message into several smaller messages. Specify MQMF_SEGMENTATION_ALLOWED in the MsgFlags field in MQMD; this will allow the queue manager to break the message into segments. Check the channel definitions. 2033 (X'07F1')MQRC_NO_MSG_AVAILABLE Explanation: An MQGET call was issued, but there is no message on the queue satisfying the selection criteria specified in MQMD (the MsgId and CorrelId fields), and in MQGMO (the Options and MatchOptions fields). Either the MQGMO_WAIT option was not specified, or the time interval specified by the WaitInterval field in MQGMO has expired. This reason is also returned for an MQGET call for browse, when the end of the queue has been reached. This reason code can also be returned by the mqGetBag and mqExecute calls. mqGetBag is similar to MQGET. For the mqExecute call, the completion code can be either MQCC_WARNING or MQCC_FAILED: If the completion code is MQCC_WARNING, some response messages were received during the specified wait interval, but not all. The response bag contains system-generated nested bags for the messages that were received. If the completion code is MQCC_FAILED, no response messages were received during the specified wait interval. Completion Code: MQCC_WARNING or MQCC_FAILED Programmer Response: If this is an expected condition, no corrective action is required. If this is an unexpected condition, check that: The message was put on the queue successfully. The unit of work (if any) used for the MQPUT or MQPUT1 call was committed successfully. The options controlling the selection criteria are specified correctly. All of the following can affect the eligibility of a message for return on the MQGET call: MQGMO_LOGICAL_ORDER MQGMO_ALL_MSGS_AVAILABLE MQGMO_ALL_SEGMENTS_AVAILABLE MQGMO_COMPLETE_MSG MQMO_MATCH_MSG_ID MQMO_MATCH_CORREL_ID MQMO_MATCH_GROUP_ID MQMO_MATCH_MSG_SEQ_NUMBER MQMO_MATCH_OFFSET Value of MsgId field in MQMD Value of CorrelId field in MQMD Consider waiting longer for the message. 2034 (X'07F2')MQRC_NO_MSG_UNDER_CURSOR Explanation: An MQGET call was issued with either the MQGMO_MSG_UNDER_CURSOR or the MQGMO_BROWSE_MSG_UNDER_CURSOR option. However, the browse cursor is not positioned at a retrievable message. This is caused by one of the following: The cursor is positioned logically before the first message (as it is before the first MQGET call with a browse option has been successfully performed). The message the browse cursor was positioned on has been locked or removed from the queue (probably by some other application) since the browse operation was performed. The message the browse cursor was positioned on has expired. Completion Code: MQCC_FAILED Programmer Response: Check the application logic. This may be an expected reason if the application design allows multiple servers to compete for messages after browsing. Consider also using the MQGMO_LOCK option with the preceding browse MQGET call. 2035 (X'07F3')MQRC_NOT_AUTHORIZED Explanation: The user is not authorized to perform the operation attempted: On an MQCONN or MQCONNX call, the user is not authorized to connect to the queue manager. On z/OS, for CICS applications, MQRC_CONNECTION_NOT_AUTHORIZED is issued instead. On an MQOPEN or MQPUT1 call, the user is not authorized to open the object for the option(s) specified. On z/OS, if the object being opened is a model queue, this reason also arises if the user is not authorized to create a dynamic queue with the required name. On an MQCLOSE call, the user is not authorized to delete the object, which is a permanent dynamic queue, and the Hobj parameter specified on the MQCLOSE call is not the handle returned by the MQOPEN call that created the queue. On a command, the user is not authorized to issue the command, or to access the object it specifies. This reason code can also occur in the Feedback field in the message descriptor of a report message; in this case it indicates that the error was encountered by a message channel agent when it attempted to put the message on a remote queue. Completion Code: MQCC_FAILED Programmer Response: Ensure that the correct queue manager or object was specified, and that appropriate authority exists. 2036 (X'07F4')MQRC_NOT_OPEN_FOR_BROWSE Explanation: An MQGET call was issued with one of the following options: MQGMO_BROWSE_FIRST MQGMO_BROWSE_NEXT MQGMO_BROWSE_MSG_UNDER_CURSOR MQGMO_MSG_UNDER_CURSOR but the queue had not been opened for browse. Completion Code: MQCC_FAILED Programmer Response: Specify MQOO_BROWSE when the queue is opened. 2037 (X'07F5')MQRC_NOT_OPEN_FOR_INPUT Explanation: An MQGET call was issued to retrieve a message from a queue, but the queue had not been opened for input. Completion Code: MQCC_FAILED Programmer Response: Specify one of the following when the queue is opened: MQOO_INPUT_SHARED MQOO_INPUT_EXCLUSIVE MQOO_INPUT_AS_Q_DEF 2038 (X'07F6')MQRC_NOT_OPEN_FOR_INQUIRE Explanation: An MQINQ call was issued to inquire object attributes, but the object had not been opened for inquire. Completion Code: MQCC_FAILED Programmer Response: Specify MQOO_INQUIRE when the object is opened. 2039 (X'07F7')MQRC_NOT_OPEN_FOR_OUTPUT Explanation: An MQPUT call was issued to put a message on a queue, but the queue had not been opened for output. Completion Code: MQCC_FAILED Programmer Response: Specify MQOO_OUTPUT when the queue is opened. 2040 (X'07F8')MQRC_NOT_OPEN_FOR_SET Explanation: An MQSET call was issued to set queue attributes, but the queue had not been opened for set. Completion Code: MQCC_FAILED Programmer Response: Specify MQOO_SET when the object is opened. 2041 (X'07F9')MQRC_OBJECT_CHANGED Explanation: Object definitions that affect this object have been changed since the Hobj handle used on this call was returned by the MQOPEN call. See the description of MQOPEN in the WebSphere MQ Application Programming Guide for more information. This reason does not occur if the object handle is specified in the Context field of the PutMsgOpts parameter on the MQPUT or MQPUT1 call. Completion Code: MQCC_FAILED Programmer Response: Issue an MQCLOSE call to return the handle to the system. It is then usually sufficient to reopen the object and retry the operation. However, if the object definitions are critical to the application logic, an MQINQ call can be used after reopening the object, to obtain the new values of the object attributes. 2042 (X'07FA')MQRC_OBJECT_IN_USE Explanation: An MQOPEN call was issued, but the object in question has already been opened by this or another application with options that conflict with those specified in the Options parameter. This arises if the request is for shared input, but the object is already open for exclusive input; it also arises if the request is for exclusive input, but the object is already open for input (of any sort). MCAs for receiver channels, or the intra-group queuing agent (IGQ agent), may keep the destination queues open even when messages are not being transmitted; this results in the queues appearing to be "in use". Use the MQSC command DISPLAY QSTATUS to find out who is keeping the queue open. On z/OS, this reason can also occur for an MQOPEN or MQPUT1 call, if the object to be opened (which can be a queue, or for MQOPEN a namelist or process object) is in the process of being deleted. Completion Code: MQCC_FAILED Programmer Response: System design should specify whether an application is to wait and retry, or take other action. 2043 (X'07FB')MQRC_OBJECT_TYPE_ERROR Explanation: On the MQOPEN or MQPUT1 call, the ObjectType field in the object descriptor MQOD specifies a value that is not valid. For the MQPUT1 call, the object type must be MQOT_Q. Completion Code: MQCC_FAILED Programmer Response: Specify a valid object type. 2044 (X'07FC')MQRC_OD_ERROR Explanation: On the MQOPEN or MQPUT1 call, the object descriptor MQOD is not valid, for one of the following reasons: The StrucId field is not MQOD_STRUC_ID. The Version field specifies a value that is not valid or not supported. The parameter pointer is not valid. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) The queue manager cannot copy the changed structure to application storage, even though the call is successful. This can occur, for example, if the pointer points to read-only storage. Completion Code: MQCC_FAILED Programmer Response: Ensure that input fields in the MQOD structure are set correctly. 2045 (X'07FD')MQRC_OPTION_NOT_VALID_FOR_TYPE Explanation: On an MQOPEN or MQCLOSE call, an option is specified that is not valid for the type of object or queue being opened or closed. For the MQOPEN call, this includes the following cases: An option that is inappropriate for the object type (for example, MQOO_OUTPUT for an MQOT_PROCESS object). An option that is unsupported for the queue type (for example, MQOO_INQUIRE for a remote queue that has no local definition). One or more of the following options: MQOO_INPUT_AS_Q_DEF MQOO_INPUT_SHARED MQOO_INPUT_EXCLUSIVE MQOO_BROWSE MQOO_INQUIRE MQOO_SET when either: the queue name is resolved through a cell directory, or ObjectQMgrName in the object descriptor specifies the name of a local definition of a remote queue (in order to specify a queue-manager alias), and the queue named in the RemoteQMgrName attribute of the definition is the name of the local queue manager. For the MQCLOSE call, this includes the following case: The MQCO_DELETE or MQCO_DELETE_PURGE option when the queue is not a dynamic queue. This reason code can also occur on the MQOPEN call when the object being opened is of type MQOT_NAMELIST, MQOT_PROCESS, or MQOT_Q_MGR, but the ObjectQMgrName field in MQOD is neither blank nor the name of the local queue manager. Completion Code: MQCC_FAILED Programmer Response: Specify the correct option. For the MQOPEN call, ensure that the ObjectQMgrName field is set correctly. For the MQCLOSE call, either correct the option or change the definition type of the model queue that is used to create the new queue. 2046 (X'07FE')MQRC_OPTIONS_ERROR Explanation: The Options parameter or field contains options that are not valid, or a combination of options that is not valid. For the MQOPEN, MQCLOSE, MQXCNVC, mqBagToBuffer, mqBufferToBag, mqCreateBag, and mqExecute calls, Options is a separate parameter on the call. This reason also occurs if the parameter pointer is not valid. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) For the MQBEGIN, MQCONNX, MQGET, MQPUT, and MQPUT1 calls, Options is a field in the relevant options structure (MQBO, MQCNO, MQGMO, or MQPMO). Completion Code: MQCC_FAILED Programmer Response: Specify valid options. Check the description of the Options parameter or field to determine which options and combinations of options are valid. If multiple options are being set by adding the individual options together, ensure that the same option is not added twice. 2047 (X'07FF')MQRC_PERSISTENCE_ERROR Explanation: On an MQPUT or MQPUT1 call, the value specified for the Persistence field in the message descriptor MQMD is not valid. Completion Code: MQCC_FAILED Programmer Response: Specify one of the following values: MQPER_PERSISTENT MQPER_NOT_PERSISTENT MQPER_PERSISTENCE_AS_Q_DEF 2048 (X'0800')MQRC_PERSISTENT_NOT_ALLOWED Explanation: On an MQPUT or MQPUT1 call, the value specified for the Persistence field in MQMD (or obtained from the DefPersistence queue attribute) specifies MQPER_PERSISTENT, but the queue on which the message is being placed does not support persistent messages. Persistent messages cannot be placed on temporary dynamic queues. This reason code can also occur in the Feedback field in the message descriptor of a report message; in this case it indicates that the error was encountered by a message channel agent when it attempted to put the message on a remote queue. Completion Code: MQCC_FAILED Programmer Response: Specify MQPER_NOT_PERSISTENT if the message is to be placed on a temporary dynamic queue. If persistence is required, use a permanent dynamic queue or predefined queue in place of a temporary dynamic queue. Be aware that server applications are recommended to send reply messages (message type MQMT_REPLY) with the same persistence as the original request message (message type MQMT_REQUEST). If the request message is persistent, the reply queue specified in the ReplyToQ field in the message descriptor MQMD cannot be a temporary dynamic queue. Use a permanent dynamic queue or predefined queue as the reply queue in this situation. 2049 (X'0801')MQRC_PRIORITY_EXCEEDS_MAXIMUM Explanation: An MQPUT or MQPUT1 call was issued, but the value of the Priority field in the message descriptor MQMD exceeds the maximum priority supported by the local queue manager, as shown by the MaxPriority queue-manager attribute. The message is accepted by the queue manager, but is placed on the queue at the queue manager's maximum priority. The Priority field in the message descriptor retains the value specified by the application that put the message. Completion Code: MQCC_WARNING Programmer Response: None required, unless this reason code was not expected by the application that put the message. 2050 (X'0802')MQRC_PRIORITY_ERROR Explanation: An MQPUT or MQPUT1 call was issued, but the value of the Priority field in the message descriptor MQMD is not valid. The maximum priority supported by the queue manager is given by the MaxPriority queue-manager attribute. Completion Code: MQCC_FAILED Programmer Response: Specify a value in the range zero through MaxPriority, or the special value MQPRI_PRIORITY_AS_Q_DEF. 2051 (X'0803')MQRC_PUT_INHIBITED Explanation: MQPUT and MQPUT1 calls are currently inhibited for the queue, or for the queue to which this queue resolves. This reason code can also occur in the Feedback field in the message descriptor of a report message; in this case it indicates that the error was encountered by a message channel agent when it attempted to put the message on a remote queue. Completion Code: MQCC_FAILED Programmer Response: If the system design allows put requests to be inhibited for short periods, retry the operation later. 2052 (X'0804')MQRC_Q_DELETED Explanation: An Hobj queue handle specified on a call refers to a dynamic queue that has been deleted since the queue was opened. (See the description of MQCLOSE in the WebSphere MQ Application Programming Guide for information about the deletion of dynamic queues.) On z/OS, this can also occur with the MQOPEN and MQPUT1 calls if a dynamic queue is being opened, but the queue is in a logically-deleted state. See MQCLOSE for more information about this. Completion Code: MQCC_FAILED Programmer Response: Issue an MQCLOSE call to return the handle and associated resources to the system (the MQCLOSE call will succeed in this case). Check the design of the application that caused the error. 2053 (X'0805')MQRC_Q_FULL Explanation: An MQPUT or MQPUT1 call, or a command, failed because the queue is full, that is, it already contains the maximum number of messages possible, as specified by the MaxQDepth queue attribute. This reason code can also occur in the Feedback field in the message descriptor of a report message; in this case it indicates that the error was encountered by a message channel agent when it attempted to put the message on a remote queue. Completion Code: MQCC_FAILED Programmer Response: Retry the operation later. Consider increasing the maximum depth for this queue, or arranging for more instances of the application to service the queue. 2055 (X'0807')MQRC_Q_NOT_EMPTY Explanation: An MQCLOSE call was issued for a permanent dynamic queue, but the call failed because the queue is not empty or still in use. One of the following applies: The MQCO_DELETE option was specified, but there are messages on the queue. The MQCO_DELETE or MQCO_DELETE_PURGE option was specified, but there are uncommitted get or put calls outstanding against the queue. See the usage notes pertaining to dynamic queues for the MQCLOSE call for more information. This reason code is also returned from a command to clear or delete or move a queue, if the queue contains uncommitted messages (or committed messages in the case of delete queue without the purge option). Completion Code: MQCC_FAILED Programmer Response: Check why there might be messages on the queue. Be aware that the CurrentQDepth queue attribute might be zero even though there are one or more messages on the queue; this can happen if the messages have been retrieved as part of a unit of work that has not yet been committed. If the messages can be discarded, try using the MQCLOSE call with the MQCO_DELETE_PURGE option. Consider retrying the call later. 2056 (X'0808')MQRC_Q_SPACE_NOT_AVAILABLE Explanation: An MQPUT or MQPUT1 call was issued, but there is no space available for the queue on disk or other storage device. This reason code can also occur in the Feedback field in the message descriptor of a report message; in this case it indicates that the error was encountered by a message channel agent when it attempted to put the message on a remote queue. On z/OS, this reason code does not occur. Completion Code: MQCC_FAILED Programmer Response: Check whether an application is putting messages in an infinite loop. If not, make more disk space available for the queue. 2057 (X'0809')MQRC_Q_TYPE_ERROR Explanation: One of the following occurred: On an MQOPEN call, the ObjectQMgrName field in the object descriptor MQOD or object record MQOR specifies the name of a local definition of a remote queue (in order to specify a queue-manager alias), and in that local definition the RemoteQMgrName attribute is the name of the local queue manager. However, the ObjectName field in MQOD or MQOR specifies the name of a model queue on the local queue manager; this is not allowed. See the WebSphere MQ Application Programming Guide for more information. On an MQPUT1 call, the object descriptor MQOD or object record MQOR specifies the name of a model queue. On a previous MQPUT or MQPUT1 call, the ReplyToQ field in the message descriptor specified the name of a model queue, but a model queue cannot be specified as the destination for reply or report messages. Only the name of a predefined queue, or the name of the dynamic queue created from the model queue, can be specified as the destination. In this situation the reason code MQRC_Q_TYPE_ERROR is returned in the Reason field of the MQDLH structure when the reply message or report message is placed on the dead-letter queue. Completion Code: MQCC_FAILED Programmer Response: Specify a valid queue. 2058 (X'080A')MQRC_Q_MGR_NAME_ERROR Explanation: On an MQCONN or MQCONNX call, the value specified for the QMgrName parameter is not valid or not known. This reason also occurs if the parameter pointer is not valid. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) On z/OS for CICS applications, this reason can occur on any call if the original connect specified an incorrect or unrecognized name. This reason code can also occur if an MQ client application attempts to connect to a queue manager within an MQ-client queue-manager group (see the QMgrName parameter of MQCONN), and either: Queue-manager groups are not supported. There is no queue-manager group with the specified name. Completion Code: MQCC_FAILED Programmer Response: Use an all-blank name if possible, or verify that the name used is valid. 2059 (X'080B')MQRC_Q_MGR_NOT_AVAILABLE Explanation: This occurs: On an MQCONN or MQCONNX call, the queue manager identified by the QMgrName parameter is not available for connection. On z/OS: For batch applications, this reason can be returned to applications running in LPARs that do not have a queue manager installed. For CICS applications, this reason can occur on any call if the original connect specified a queue manager whose name was recognized, but which is not available. On i5/OS, this reason can also be returned by the MQOPEN and MQPUT1 calls, when MQHC_DEF_HCONN is specified for the Hconn parameter by an application running in compatibility mode. On an MQCONN or MQCONNX call from an MQ client application: Attempting to connect to a queue manager within an MQ-client queue-manager group when none of the queue managers in the group is available for connection (see the QMgrName parameter of the MQCONN call). If there is an error with the client-connection or the corresponding server-connection channel definitions. On z/OS, if the optional OS/390 Client Attachment feature has not been installed. If a command uses the CommandScope parameter specfying a queue manager that is not active in the queue-sharing group. Completion Code: MQCC_FAILED Programmer Response: Ensure that the queue manager has been started. If the connection is from a client application, check the channel definitions. 2061 (X'080D')MQRC_REPORT_OPTIONS_ERROR Explanation: An MQPUT or MQPUT1 call was issued, but the Report field in the message descriptor MQMD contains one or more options that are not recognized by the local queue manager. The options that cause this reason code to be returned depend on the destination of the message; see the description of REPORT in the WebSphere MQ Application Programming Guide for more details. This reason code can also occur in the Feedback field in the MQMD of a report message, or in the Reason field in the MQDLH structure of a message on the dead-letter queue; in both cases it indicates that the destination queue manager does not support one or more of the report options specified by the sender of the message. Completion Code: MQCC_FAILED Programmer Response: Do the following: Ensure that the Report field in the message descriptor is initialized with a value when the message descriptor is declared, or is assigned a value prior to the MQPUT or MQPUT1 call. Specify MQRO_NONE if no report options are required. Ensure that the report options specified are valid; see the Report field described in the description of MQMD in the WebSphere MQ Application Programming Guide for valid report options. If multiple report options are being set by adding the individual report options together, ensure that the same report option is not added twice. Check that conflicting report options are not specified. For example, do not add both MQRO_EXCEPTION and MQRO_EXCEPTION_WITH_DATA to the Report field; only one of these can be specified. 2062 (X'080E')MQRC_SECOND_MARK_NOT_ALLOWED Explanation: An MQGET call was issued specifying the MQGMO_MARK_SKIP_BACKOUT option in the Options field of MQGMO, but a message has already been marked within the current unit of work. Only one marked message is allowed within each unit of work. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Modify the application so that no more than one message is marked within each unit of work. 2063 (X'080F')MQRC_SECURITY_ERROR Explanation: An MQCONN, MQCONNX, MQOPEN, MQPUT1, or MQCLOSE call was issued, but it failed because a security error occurred. On z/OS, the security error was returned by the External Security Manager. Completion Code: MQCC_FAILED Programmer Response: Note the error from the security manager, and contact your system programmer or security administrator. On i5/OS, the FFST log will contain the error information. 2065 (X'0811')MQRC_SELECTOR_COUNT_ERROR Explanation: On an MQINQ or MQSET call, the SelectorCount parameter specifies a value that is not valid. This reason also occurs if the parameter pointer is not valid. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) Completion Code: MQCC_FAILED Programmer Response: Specify a value in the range 0 through 256. 2066 (X'0812')MQRC_SELECTOR_LIMIT_EXCEEDED Explanation: On an MQINQ or MQSET call, the SelectorCount parameter specifies a value that is larger than the maximum supported (256). Completion Code: MQCC_FAILED Programmer Response: Reduce the number of selectors specified on the call; the valid range is 0 through 256. 2067 (X'0813')MQRC_SELECTOR_ERROR Explanation: An MQINQ or MQSET call was issued, but the Selectors array contains a selector that is not valid for one of the following reasons: The selector is not supported or out of range. The selector is not applicable to the type of object whose attributes are being inquired or set. The selector is for an attribute that cannot be set. This reason also occurs if the parameter pointer is not valid. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) Completion Code: MQCC_FAILED Programmer Response: Ensure that the value specified for the selector is valid for the object type represented by Hobj. For the MQSET call, also ensure that the selector represents an integer attribute that can be set. 2068 (X'0814')MQRC_SELECTOR_NOT_FOR_TYPE Explanation: On the MQINQ call, one or more selectors in the Selectors array is not applicable to the type of the queue whose attributes are being inquired. This reason also occurs when the queue is a cluster queue that resolved to a remote instance of the queue. In this case only a subset of the attributes that are valid for local queues can be inquired. See the usage notes in the description of MQINQ in the WebSphere MQ Application Programming Guide for further details. The call completes with MQCC_WARNING, with the attribute values for the inapplicable selectors set as follows: For integer attributes, the corresponding elements of IntAttrs are set to MQIAV_NOT_APPLICABLE. For character attributes, the appropriate parts of the CharAttrs string are set to a character string consisting entirely of asterisks (*). Completion Code: MQCC_WARNING Programmer Response: Verify that the selector specified is the one that was intended. If the queue is a cluster queue, specifying one of the MQOO_BROWSE, MQOO_INPUT_*, or MQOO_SET options in addition to MQOO_INQUIRE forces the queue to resolve to the local instance of the queue. However, if there is no local instance of the queue the MQOPEN call fails. 2069 (X'0815')MQRC_SIGNAL_OUTSTANDING Explanation: An MQGET call was issued with either the MQGMO_SET_SIGNAL or MQGMO_WAIT option, but there is already a signal outstanding for the queue handle Hobj. This reason code occurs only in the following environments: z/OS, Windows 95, Windows 98. Completion Code: MQCC_FAILED Programmer Response: Check the application logic. If it is necessary to set a signal or wait when there is a signal outstanding for the same queue, a different object handle must be used. 2070 (X'0816')MQRC_SIGNAL_REQUEST_ACCEPTED Explanation: An MQGET call was issued specifying MQGMO_SET_SIGNAL in the GetMsgOpts parameter, but no suitable message was available; the call returns immediately. The application can now wait for the signal to be delivered. On z/OS, the application should wait on the Event Control Block pointed to by the Signal1 field. On Windows 95, Windows 98, the application should wait for the signal Windows message to be delivered. This reason code occurs only in the following environments: z/OS, Windows 95, Windows 98. Completion Code: MQCC_WARNING Programmer Response: Wait for the signal; when it is delivered, check the signal to ensure that a message is now available. If it is, reissue the MQGET call. On z/OS, wait on the ECB pointed to by the Signal1 field and, when it is posted, check it to ensure that a message is now available. On Windows 95, Windows 98, the application (thread) should continue executing its message loop. 2071 (X'0817')MQRC_STORAGE_NOT_AVAILABLE Explanation: The call failed because there is insufficient main storage available. Completion Code: MQCC_FAILED Programmer Response: Ensure that active applications are behaving correctly, for example, that they are not looping unexpectedly. If no problems are found, make more main storage available. On z/OS, if no application problems are found, ask your system programmer to increase the size of the region in which the queue manager runs. 2072 (X'0818')MQRC_SYNCPOINT_NOT_AVAILABLE Explanation: Either MQGMO_SYNCPOINT was specified on an MQGET call or MQPMO_SYNCPOINT was specified on an MQPUT or MQPUT1 call, but the local queue manager was unable to honor the request. If the queue manager does not support units of work, the SyncPoint queue-manager attribute will have the value MQSP_NOT_AVAILABLE. This reason code can also occur on the MQGET, MQPUT, and MQPUT1 calls when an external unit-of-work coordinator is being used. If that coordinator requires an explicit call to start the unit of work, but the application has not issued that call prior to the MQGET, MQPUT, or MQPUT1 call, reason code MQRC_SYNCPOINT_NOT_AVAILABLE is returned. On i5/OS, this reason codes means that i5/OS Commitment Control is not started, or is unavailable for use by the queue manager. On z/OS, this reason code does not occur. Completion Code: MQCC_FAILED Programmer Response: Remove the specification of MQGMO_SYNCPOINT or MQPMO_SYNCPOINT, as appropriate. On i5/OS, ensure that Commitment Control has been started. If this reason code occurs after Commitment Control has been started, contact your system programmer. 2075 (X'081B')MQRC_TRIGGER_CONTROL_ERROR Explanation: On an MQSET call, the value specified for the MQIA_TRIGGER_CONTROL attribute selector is not valid. Completion Code: MQCC_FAILED Programmer Response: Specify a valid value. 2076 (X'081C')MQRC_TRIGGER_DEPTH_ERROR Explanation: On an MQSET call, the value specified for the MQIA_TRIGGER_DEPTH attribute selector is not valid. Completion Code: MQCC_FAILED Programmer Response: Specify a value that is greater than zero. 2077 (X'081D')MQRC_TRIGGER_MSG_PRIORITY_ERR Explanation: On an MQSET call, the value specified for the MQIA_TRIGGER_MSG_PRIORITY attribute selector is not valid. Completion Code: MQCC_FAILED Programmer Response: Specify a value in the range zero through the value of MaxPriority queue-manager attribute. 2078 (X'081E')MQRC_TRIGGER_TYPE_ERROR Explanation: On an MQSET call, the value specified for the MQIA_TRIGGER_TYPE attribute selector is not valid. Completion Code: MQCC_FAILED Programmer Response: Specify a valid value. 2079 (X'081F')MQRC_TRUNCATED_MSG_ACCEPTED Explanation: On an MQGET call, the message length was too large to fit into the supplied buffer. The MQGMO_ACCEPT_TRUNCATED_MSG option was specified, so the call completes. The message is removed from the queue (subject to unit-of-work considerations), or, if this was a browse operation, the browse cursor is advanced to this message. The DataLength parameter is set to the length of the message before truncation, the Buffer parameter contains as much of the message as fits, and the MQMD structure is filled in. Completion Code: MQCC_WARNING Programmer Response: None, because the application expected this situation. 2080 (X'0820')MQRC_TRUNCATED_MSG_FAILED Explanation: On an MQGET call, the message length was too large to fit into the supplied buffer. The MQGMO_ACCEPT_TRUNCATED_MSG option was not specified, so the message has not been removed from the queue. If this was a browse operation, the browse cursor remains where it was before this call, but if MQGMO_BROWSE_FIRST was specified, the browse cursor is positioned logically before the highest-priority message on the queue. The DataLength field is set to the length of the message before truncation, the Buffer parameter contains as much of the message as fits, and the MQMD structure is filled in. Completion Code: MQCC_WARNING Programmer Response: Supply a buffer that is at least as large as DataLength, or specify MQGMO_ACCEPT_TRUNCATED_MSG if not all of the message data is required. 2082 (X'0822')MQRC_UNKNOWN_ALIAS_BASE_Q Explanation: An MQOPEN or MQPUT1 call was issued specifying an alias queue as the target, but the BaseQName in the alias queue attributes is not recognized as a queue name. This reason code can also occur when BaseQName is the name of a cluster queue that cannot be resolved successfully. Completion Code: MQCC_FAILED Programmer Response: Correct the queue definitions. 2085 (X'0825')MQRC_UNKNOWN_OBJECT_NAME Explanation: An MQOPEN or MQPUT1 call was issued, but the object identified by the ObjectName and ObjectQMgrName fields in the object descriptor MQOD cannot be found. One of the following applies: The ObjectQMgrName field is one of the following: Blank The name of the local queue manager The name of a local definition of a remote queue (a queue-manager alias) in which the RemoteQMgrName attribute is the name of the local queue manager but no object with the specified ObjectName and ObjectType exists on the local queue manager. The object being opened is a cluster queue that is hosted on a remote queue manager, but the local queue manager does not have a defined route to the remote queue manager. The object being opened is a queue definition that has QSGDISP(GROUP). Such definitions cannot be used with the MQOPEN and MQPUT1 calls. This can also occur in response to a command that specifies the name of an object or other item that does not exist. Completion Code: MQCC_FAILED Programmer Response: Specify a valid object name. Ensure that the name is padded to the right with blanks if necessary. If this is correct, check the object definitions. 2086 (X'0826')MQRC_UNKNOWN_OBJECT_Q_MGR Explanation: On an MQOPEN or MQPUT1 call, the ObjectQMgrName field in the object descriptor MQOD does not satisfy the naming rules for objects. For more information, see the WebSphere MQ Application Programming Guide. This reason also occurs if the ObjectType field in the object descriptor has the value MQOT_Q_MGR, and the ObjectQMgrName field is not blank, but the name specified is not the name of the local queue manager. Completion Code: MQCC_FAILED Programmer Response: Specify a valid queue manager name. To refer to the local queue manager, a name consisting entirely of blanks or beginning with a null character can be used. Ensure that the name is padded to the right with blanks or terminated with a null character if necessary. 2087 (X'0827')MQRC_UNKNOWN_REMOTE_Q_MGR Explanation: On an MQOPEN or MQPUT1 call, an error occurred with the queue-name resolution, for one of the following reasons: ObjectQMgrName is blank or the name of the local queue manager, ObjectName is the name of a local definition of a remote queue (or an alias to one), and one of the following is true: RemoteQMgrName is blank or the name of the local queue manager. Note that this error occurs even if XmitQName is not blank. XmitQName is blank, but there is no transmission queue defined with the name of RemoteQMgrName, and the DefXmitQName queue-manager attribute is blank. RemoteQMgrName and RemoteQName specify a cluster queue that cannot be resolved successfully, and the DefXmitQName queue-manager attribute is blank. ObjectQMgrName is the name of a local definition of a remote queue (containing a queue-manager alias definition), and one of the following is true: RemoteQName is not blank. XmitQName is blank, but there is no transmission queue defined with the name of RemoteQMgrName, and the DefXmitQName queue-manager attribute is blank. ObjectQMgrName is not: Blank The name of the local queue manager The name of a transmission queue The name of a queue-manager alias definition (that is, a local definition of a remote queue with a blank RemoteQName) but the DefXmitQName queue-manager attribute is blank and the queue manager is not part of a queue-sharing group with intra-group queuing enabled. ObjectQMgrName is the name of a model queue. The queue name is resolved through a cell directory. However, there is no queue defined with the same name as the remote queue manager name obtained from the cell directory, and the DefXmitQName queue-manager attribute is blank. Completion Code: MQCC_FAILED Programmer Response: Check the values specified for ObjectQMgrName and ObjectName. If these are correct, check the queue definitions. 2090 (X'082A')MQRC_WAIT_INTERVAL_ERROR Explanation: On the MQGET call, the value specified for the WaitInterval field in the GetMsgOpts parameter is not valid. Completion Code: MQCC_FAILED Programmer Response: Specify a value greater than or equal to zero, or the special value MQWI_UNLIMITED if an indefinite wait is required. 2091 (X'082B')MQRC_XMIT_Q_TYPE_ERROR Explanation: On an MQOPEN or MQPUT1 call, a message is to be sent to a remote queue manager. The ObjectName or ObjectQMgrName field in the object descriptor specifies the name of a local definition of a remote queue but one of the following applies to the XmitQName attribute of the definition: XmitQName is not blank, but specifies a queue that is not a local queue XmitQName is blank, but RemoteQMgrName specifies a queue that is not a local queue This reason also occurs if the queue name is resolved through a cell directory, and the remote queue manager name obtained from the cell directory is the name of a queue, but this is not a local queue. Completion Code: MQCC_FAILED Programmer Response: Check the values specified for ObjectName and ObjectQMgrName. If these are correct, check the queue definitions. For more information on transmission queues, see the WebSphere MQ Application Programming Guide. 2092 (X'082C')MQRC_XMIT_Q_USAGE_ERROR Explanation: On an MQOPEN or MQPUT1 call, a message is to be sent to a remote queue manager, but one of the following occurred: ObjectQMgrName specifies the name of a local queue, but it does not have a Usage attribute of MQUS_TRANSMISSION. The ObjectName or ObjectQMgrName field in the object descriptor specifies the name of a local definition of a remote queue but one of the following applies to the XmitQName attribute of the definition: XmitQName is not blank, but specifies a queue that does not have a Usage attribute of MQUS_TRANSMISSION XmitQName is blank, but RemoteQMgrName specifies a queue that does not have a Usage attribute of MQUS_TRANSMISSION XmitQName specifies the queue SYSTEM.QSG.TRANSMIT.QUEUE the IGQ queue manager attribute indicates that IGQ is DISABLED. The queue name is resolved through a cell directory, and the remote queue manager name obtained from the cell directory is the name of a local queue, but it does not have a Usage attribute of MQUS_TRANSMISSION. Completion Code: MQCC_FAILED Programmer Response: Check the values specified for ObjectName and ObjectQMgrName. If these are correct, check the queue definitions. For more information on transmission queues, see the WebSphere MQ Application Programming Guide. 2093 (X'082D')MQRC_NOT_OPEN_FOR_PASS_ALL Explanation: An MQPUT call was issued with the MQPMO_PASS_ALL_CONTEXT option specified in the PutMsgOpts parameter, but the queue had not been opened with the MQOO_PASS_ALL_CONTEXT option. Completion Code: MQCC_FAILED Programmer Response: Specify MQOO_PASS_ALL_CONTEXT (or another option that implies it) when the queue is opened. 2094 (X'082E')MQRC_NOT_OPEN_FOR_PASS_IDENT Explanation: An MQPUT call was issued with the MQPMO_PASS_IDENTITY_CONTEXT option specified in the PutMsgOpts parameter, but the queue had not been opened with the MQOO_PASS_IDENTITY_CONTEXT option. Completion Code: MQCC_FAILED Programmer Response: Specify MQOO_PASS_IDENTITY_CONTEXT (or another option that implies it) when the queue is opened. 2095 (X'082F')MQRC_NOT_OPEN_FOR_SET_ALL Explanation: An MQPUT call was issued with the MQPMO_SET_ALL_CONTEXT option specified in the PutMsgOpts parameter, but the queue had not been opened with the MQOO_SET_ALL_CONTEXT option. Completion Code: MQCC_FAILED Programmer Response: Specify MQOO_SET_ALL_CONTEXT when the queue is opened. 2096 (X'0830')MQRC_NOT_OPEN_FOR_SET_IDENT Explanation: An MQPUT call was issued with the MQPMO_SET_IDENTITY_CONTEXT option specified in the PutMsgOpts parameter, but the queue had not been opened with the MQOO_SET_IDENTITY_CONTEXT option. Completion Code: MQCC_FAILED Programmer Response: Specify MQOO_SET_IDENTITY_CONTEXT (or another option that implies it) when the queue is opened. 2097 (X'0831')MQRC_CONTEXT_HANDLE_ERROR Explanation: On an MQPUT or MQPUT1 call, MQPMO_PASS_IDENTITY_CONTEXT or MQPMO_PASS_ALL_CONTEXT was specified, but the handle specified in the Context field of the PutMsgOpts parameter is either not a valid queue handle, or it is a valid queue handle but the queue was not opened with MQOO_SAVE_ALL_CONTEXT. Completion Code: MQCC_FAILED Programmer Response: Specify MQOO_SAVE_ALL_CONTEXT when the queue referred to is opened. 2098 (X'0832')MQRC_CONTEXT_NOT_AVAILABLE Explanation: On an MQPUT or MQPUT1 call, MQPMO_PASS_IDENTITY_CONTEXT or MQPMO_PASS_ALL_CONTEXT was specified, but the queue handle specified in the Context field of the PutMsgOpts parameter has no context associated with it. This arises if no message has yet been successfully retrieved with the queue handle referred to, or if the last successful MQGET call was a browse. This condition does not arise if the message that was last retrieved had no context associated with it. On z/OS, if a message is received by a message channel agent that is putting messages with the authority of the user identifier in the message, this code is returned in the Feedback field of an exception report if the message has no context associated with it. Completion Code: MQCC_FAILED Programmer Response: Ensure that a successful nonbrowse get call has been issued with the queue handle referred to. 2099 (X'0833')MQRC_SIGNAL1_ERROR Explanation: An MQGET call was issued, specifying MQGMO_SET_SIGNAL in the GetMsgOpts parameter, but the Signal1 field is not valid. On z/OS, the address contained in the Signal1 field is not valid, or points to read-only storage. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) On Windows 95, Windows 98, the window handle in the Signal1 field is not valid. This reason code occurs only in the following environments: z/OS, Windows 95, Windows 98. Completion Code: MQCC_FAILED Programmer Response: Correct the setting of the Signal1 field. 2100 (X'0834')MQRC_OBJECT_ALREADY_EXISTS Explanation: An MQOPEN call was issued to create a dynamic queue, but a queue with the same name as the dynamic queue already exists. On z/OS, a rare "race condition" can also give rise to this reason code; see the description of reason code MQRC_NAME_IN_USE for more details. Completion Code: MQCC_FAILED Programmer Response: If supplying a dynamic queue name in full, ensure that it obeys the naming conventions for dynamic queues; if it does, either supply a different name, or delete the existing queue if it is no longer required. Alternatively, allow the queue manager to generate the name. If the queue manager is generating the name (either in part or in full), reissue the MQOPEN call. 2101 (X'0835')MQRC_OBJECT_DAMAGED Explanation: The object accessed by the call is damaged and cannot be used. For example, this may be because the definition of the object in main storage is not consistent, or because it differs from the definition of the object on disk, or because the definition on disk cannot be read. The object can be deleted, although it may not be possible to delete the associated user space. On z/OS, this reason occurs when the DB2 list header or structure number associated with a shared queue is zero. This situation arises as a result of using the MQSC command DELETE CFSTRUCT to delete the DB2 structure definition. The command resets the list header and structure number to zero for each of the shared queues that references the deleted CF strcture. Completion Code: MQCC_FAILED Programmer Response: It may be necessary to stop and restart the queue manager, or to restore the queue-manager data from back-up storage. On HP OpenVMS, OS/2, i5/OS, Compaq NonStop Kernel, and UNIX systems, consult the FFST(TM) record to obtain more detail about the problem. On z/OS, delete the shared queue and redefine it using the MQSC command DEFINE QLOCAL. This will automatically define a CF structure and allocate list headers for it. 2102 (X'0836')MQRC_RESOURCE_PROBLEM Explanation: There are insufficient system resources to complete the call successfully. Completion Code: MQCC_FAILED Programmer Response: Run the application when the machine is less heavily loaded. On z/OS, check the operator console for messages that may provide additional information. On HP OpenVMS, OS/2, i5/OS, Compaq NonStop Kernel, and UNIX systems, consult the FFST record to obtain more detail about the problem. 2103 (X'0837')MQRC_ANOTHER_Q_MGR_CONNECTED Explanation: An MQCONN or MQCONNX call was issued, but the thread or process is already connected to a different queue manager. The thread or process can connect to only one queue manager at a time. On z/OS, this reason code does not occur. On Windows, MTS objects do not receive this reason code, as connections to other queue managers are allowed. Completion Code: MQCC_FAILED Programmer Response: Use the MQDISC call to disconnect from the queue manager that is already connected, and then issue the MQCONN or MQCONNX call to connect to the new queue manager. Disconnecting from the existing queue manager will close any queues that are currently open; it is recommended that any uncommitted units of work should be committed or backed out before the MQDISC call is issued. 2104 (X'0838')MQRC_UNKNOWN_REPORT_OPTION Explanation: An MQPUT or MQPUT1 call was issued, but the Report field in the message descriptor MQMD contains one or more options that are not recognized by the local queue manager. The options are accepted. The options that cause this reason code to be returned depend on the destination of the message; see the description of REPORT in the WebSphere MQ Application Programming Guide for more details. Completion Code: MQCC_WARNING Programmer Response: If this reason code is expected, no corrective action is required. If this reason code is not expected, do the following: Ensure that the Report field in the message descriptor is initialized with a value when the message descriptor is declared, or is assigned a value prior to the MQPUT or MQPUT1 call. Ensure that the report options specified are valid; see the Report field described in the description of MQMD in the WebSphere MQ Application Programming Guide for valid report options. If multiple report options are being set by adding the individual report options together, ensure that the same report option is not added twice. Check that conflicting report options are not specified. For example, do not add both MQRO_EXCEPTION and MQRO_EXCEPTION_WITH_DATA to the Report field; only one of these can be specified. 2105 (X'0839')MQRC_STORAGE_CLASS_ERROR Explanation: The MQPUT or MQPUT1 call was issued, but the storage-class object defined for the queue does not exist. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Create the storage-class object required by the queue, or modify the queue definition to use an existing storage class. The name of the storage-class object used by the queue is given by the StorageClass queue attribute. 2106 (X'083A')MQRC_COD_NOT_VALID_FOR_XCF_Q Explanation: An MQPUT or MQPUT1 call was issued, but the Report field in the message descriptor MQMD specifies one of the MQRO_COD_* options and the target queue is an XCF queue. MQRO_COD_* options cannot be specified for XCF queues. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Remove the relevant MQRO_COD_* option. 2107 (X'083B')MQRC_XWAIT_CANCELED Explanation: An MQXWAIT call was issued, but the call has been canceled because a STOP CHINIT command has been issued (or the queue manager has been stopped, which causes the same effect). Refer to the WebSphere MQ Intercommunication book for details of the MQXWAIT call. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Tidy up and terminate. 2108 (X'083C')MQRC_XWAIT_ERROR Explanation: An MQXWAIT call was issued, but the invocation was not valid for one of the following reasons: The wait descriptor MQXWD contains data that is not valid. The linkage stack level is not valid. The addressing mode is not valid. There are too many wait events outstanding. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Obey the rules for using the MQXWAIT call. Refer to the WebSphere MQ Intercommunication book for details of this call. 2109 (X'083D')MQRC_SUPPRESSED_BY_EXIT Explanation: On any call other than MQCONN or MQDISC, the API crossing exit suppressed the call. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Obey the rules for MQI calls that the exit enforces. To find out the rules, see the writer of the exit. 2110 (X'083E')MQRC_FORMAT_ERROR Explanation: An MQGET call was issued with the MQGMO_CONVERT option specified in the GetMsgOpts parameter, but the message cannot be converted successfully due to an error associated with the message format. Possible errors include: The format name in the message is MQFMT_NONE. A user-written exit with the name specified by the Format field in the message cannot be found. The message contains data that is not consistent with the format definition. The message is returned unconverted to the application issuing the MQGET call, the values of the CodedCharSetId and Encoding fields in the MsgDesc parameter are set to those of the message returned, and the call completes with MQCC_WARNING. If the message consists of several parts, each of which is described by its own CodedCharSetId and Encoding fields (for example, a message with format name MQFMT_DEAD_LETTER_HEADER), some parts may be converted and other parts not converted. However, the values returned in the various CodedCharSetId and Encoding fields always correctly describe the relevant message data. Completion Code: MQCC_WARNING Programmer Response: Check the format name that was specified when the message was put. If this is not one of the built-in formats, check that a suitable exit with the same name as the format is available for the queue manager to load. Verify that the data in the message corresponds to the format expected by the exit. 2111 (X'083F')MQRC_SOURCE_CCSID_ERROR Explanation: The coded character-set identifier from which character data is to be converted is not valid or not supported. This can occur on the MQGET call when the MQGMO_CONVERT option is included in the GetMsgOpts parameter; the coded character-set identifier in error is the CodedCharSetId field in the message being retrieved. In this case, the message data is returned unconverted, the values of the CodedCharSetId and Encoding fields in the MsgDesc parameter are set to those of the message returned, and the call completes with MQCC_WARNING. This reason can also occur on the MQGET call when the message contains one or more MQ header structures (MQCIH, MQDLH, MQIIH, MQRMH), and the CodedCharSetId field in the message specifies a character set that does not have SBCS characters for the characters that are valid in queue names. MQ header structures containing such characters are not valid, and so the message is returned unconverted. The Unicode character set UCS-2 is an example of such a character set. If the message consists of several parts, each of which is described by its own CodedCharSetId and Encoding fields (for example, a message with format name MQFMT_DEAD_LETTER_HEADER), some parts may be converted and other parts not converted. However, the values returned in the various CodedCharSetId and Encoding fields always correctly describe the relevant message data. This reason can also occur on the MQXCNVC call; the coded character-set identifier in error is the SourceCCSID parameter. Either the SourceCCSID parameter specifies a value that is not valid or not supported, or the SourceCCSID parameter pointer is not valid. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) Completion Code: MQCC_WARNING or MQCC_FAILED Programmer Response: Check the character-set identifier that was specified when the message was put, or that was specified for the SourceCCSID parameter on the MQXCNVC call. If this is correct, check that it is one for which queue-manager conversion is supported. If queue-manager conversion is not supported for the specified character set, conversion must be carried out by the application. 2112 (X'0840')MQRC_SOURCE_INTEGER_ENC_ERROR Explanation: On an MQGET call, with the MQGMO_CONVERT option included in the GetMsgOpts parameter, the Encoding value in the message being retrieved specifies an integer encoding that is not recognized. The message data is returned unconverted, the values of the CodedCharSetId and Encoding fields in the MsgDesc parameter are set to those of the message returned, and the call completes with MQCC_WARNING. If the message consists of several parts, each of which is described by its own CodedCharSetId and Encoding fields (for example, a message with format name MQFMT_DEAD_LETTER_HEADER), some parts may be converted and other parts not converted. However, the values returned in the various CodedCharSetId and Encoding fields always correctly describe the relevant message data. This reason code can also occur on the MQXCNVC call, when the Options parameter contains an unsupported MQDCC_SOURCE_* value, or when MQDCC_SOURCE_ENC_UNDEFINED is specified for a UCS-2 code page. Completion Code: MQCC_WARNING or MQCC_FAILED Programmer Response: Check the integer encoding that was specified when the message was put. If this is correct, check that it is one for which queue-manager conversion is supported. If queue-manager conversion is not supported for the required integer encoding, conversion must be carried out by the application. 2113 (X'0841')MQRC_SOURCE_DECIMAL_ENC_ERROR Explanation: On an MQGET call with the MQGMO_CONVERT option included in the GetMsgOpts parameter, the Encoding value in the message being retrieved specifies a decimal encoding that is not recognized. The message data is returned unconverted, the values of the CodedCharSetId and Encoding fields in the MsgDesc parameter are set to those of the message returned, and the call completes with MQCC_WARNING. If the message consists of several parts, each of which is described by its own CodedCharSetId and Encoding fields (for example, a message with format name MQFMT_DEAD_LETTER_HEADER), some parts may be converted and other parts not converted. However, the values returned in the various CodedCharSetId and Encoding fields always correctly describe the relevant message data. Completion Code: MQCC_WARNING Programmer Response: Check the decimal encoding that was specified when the message was put. If this is correct, check that it is one for which queue-manager conversion is supported. If queue-manager conversion is not supported for the required decimal encoding, conversion must be carried out by the application. 2114 (X'0842')MQRC_SOURCE_FLOAT_ENC_ERROR Explanation: On an MQGET call, with the MQGMO_CONVERT option included in the GetMsgOpts parameter, the Encoding value in the message being retrieved specifies a floating-point encoding that is not recognized. The message data is returned unconverted, the values of the CodedCharSetId and Encoding fields in the MsgDesc parameter are set to those of the message returned, and the call completes with MQCC_WARNING. If the message consists of several parts, each of which is described by its own CodedCharSetId and Encoding fields (for example, a message with format name MQFMT_DEAD_LETTER_HEADER), some parts may be converted and other parts not converted. However, the values returned in the various CodedCharSetId and Encoding fields always correctly describe the relevant message data. Completion Code: MQCC_WARNING Programmer Response: Check the floating-point encoding that was specified when the message was put. If this is correct, check that it is one for which queue-manager conversion is supported. If queue-manager conversion is not supported for the required floating-point encoding, conversion must be carried out by the application. 2115 (X'0843')MQRC_TARGET_CCSID_ERROR Explanation: The coded character-set identifier to which character data is to be converted is not valid or not supported. This can occur on the MQGET call when the MQGMO_CONVERT option is included in the GetMsgOpts parameter; the coded character-set identifier in error is the CodedCharSetId field in the MsgDesc parameter. In this case, the message data is returned unconverted, the values of the CodedCharSetId and Encoding fields in the MsgDesc parameter are set to those of the message returned, and the call completes with MQCC_WARNING. This reason can also occur on the MQGET call when the message contains one or more MQ header structures (MQCIH, MQDLH, MQIIH, MQRMH), and the CodedCharSetId field in the MsgDesc parameter specifies a character set that does not have SBCS characters for the characters that are valid in queue names. The Unicode character set UCS-2 is an example of such a character set. This reason can also occur on the MQXCNVC call; the coded character-set identifier in error is the TargetCCSID parameter. Either the TargetCCSID parameter specifies a value that is not valid or not supported, or the TargetCCSID parameter pointer is not valid. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) Completion Code: MQCC_WARNING or MQCC_FAILED Programmer Response: Check the character-set identifier that was specified for the CodedCharSetId field in the MsgDesc parameter on the MQGET call, or that was specified for the SourceCCSID parameter on the MQXCNVC call. If this is correct, check that it is one for which queue-manager conversion is supported. If queue-manager conversion is not supported for the specified character set, conversion must be carried out by the application. 2116 (X'0844')MQRC_TARGET_INTEGER_ENC_ERROR Explanation: On an MQGET call with the MQGMO_CONVERT option included in the GetMsgOpts parameter, the Encoding value in the MsgDesc parameter specifies an integer encoding that is not recognized. The message data is returned unconverted, the values of the CodedCharSetId and Encoding fields in the MsgDesc parameter are set to those of the message being retrieved, and the call completes with MQCC_WARNING. This reason code can also occur on the MQXCNVC call, when the Options parameter contains an unsupported MQDCC_TARGET_* value, or when MQDCC_TARGET_ENC_UNDEFINED is specified for a UCS-2 code page. Completion Code: MQCC_WARNING or MQCC_FAILED Programmer Response: Check the integer encoding that was specified. If this is correct, check that it is one for which queue-manager conversion is supported. If queue-manager conversion is not supported for the required integer encoding, conversion must be carried out by the application. 2117 (X'0845')MQRC_TARGET_DECIMAL_ENC_ERROR Explanation: On an MQGET call with the MQGMO_CONVERT option included in the GetMsgOpts parameter, the Encoding value in the MsgDesc parameter specifies a decimal encoding that is not recognized. The message data is returned unconverted, the values of the CodedCharSetId and Encoding fields in the MsgDesc parameter are set to those of the message returned, and the call completes with MQCC_WARNING. Completion Code: MQCC_WARNING Programmer Response: Check the decimal encoding that was specified. If this is correct, check that it is one for which queue-manager conversion is supported. If queue-manager conversion is not supported for the required decimal encoding, conversion must be carried out by the application. 2118 (X'0846')MQRC_TARGET_FLOAT_ENC_ERROR Explanation: On an MQGET call with the MQGMO_CONVERT option included in the GetMsgOpts parameter, the Encoding value in the MsgDesc parameter specifies a floating-point encoding that is not recognized. The message data is returned unconverted, the values of the CodedCharSetId and Encoding fields in the MsgDesc parameter are set to those of the message returned, and the call completes with MQCC_WARNING. Completion Code: MQCC_WARNING Programmer Response: Check the floating-point encoding that was specified. If this is correct, check that it is one for which queue-manager conversion is supported. If queue-manager conversion is not supported for the required floating-point encoding, conversion must be carried out by the application. 2119 (X'0847')MQRC_NOT_CONVERTED Explanation: An MQGET call was issued with the MQGMO_CONVERT option specified in the GetMsgOpts parameter, but an error occurred during conversion of the data in the message. The message data is returned unconverted, the values of the CodedCharSetId and Encoding fields in the MsgDesc parameter are set to those of the message returned, and the call completes with MQCC_WARNING. If the message consists of several parts, each of which is described by its own CodedCharSetId and Encoding fields (for example, a message with format name MQFMT_DEAD_LETTER_HEADER), some parts may be converted and other parts not converted. However, the values returned in the various CodedCharSetId and Encoding fields always correctly describe the relevant message data. This error may also indicate that a parameter to the data-conversion service is not supported. Completion Code: MQCC_WARNING Programmer Response: Check that the message data is correctly described by the Format, CodedCharSetId and Encoding parameters that were specified when the message was put. Also check that these values, and the CodedCharSetId and Encoding specified in the MsgDesc parameter on the MQGET call, are supported for queue-manager conversion. If the required conversion is not supported, conversion must be carried out by the application. 2120 (X'0848')MQRC_CONVERTED_MSG_TOO_BIG Explanation: On an MQGET call with the MQGMO_CONVERT option included in the GetMsgOpts parameter, the message data expanded during data conversion and exceeded the size of the buffer provided by the application. However, the message had already been removed from the queue because prior to conversion the message data could be accommodated in the application buffer without truncation. The message is returned unconverted, with the CompCode parameter of the MQGET call set to MQCC_WARNING. If the message consists of several parts, each of which is described by its own character-set and encoding fields (for example, a message with format name MQFMT_DEAD_LETTER_HEADER), some parts may be converted and other parts not converted. However, the values returned in the various character-set and encoding fields always correctly describe the relevant message data. This reason can also occur on the MQXCNVC call, when the TargetBuffer parameter is too small too accommodate the converted string, and the string has been truncated to fit in the buffer. The length of valid data returned is given by the DataLength parameter; in the case of a DBCS string or mixed SBCS/DBCS string, this length may be less than the length of TargetBuffer. Completion Code: MQCC_WARNING Programmer Response: For the MQGET call, check that the exit is converting the message data correctly and setting the output length DataLength to the appropriate value. If it is, the application issuing the MQGET call must provide a larger buffer for the Buffer parameter. For the MQXCNVC call, if the string must be converted without truncation, provide a larger output buffer. 2121 (X'0849')MQRC_NO_EXTERNAL_PARTICIPANTS Explanation: An MQBEGIN call was issued to start a unit of work coordinated by the queue manager, but no participating resource managers have been registered with the queue manager. As a result, only changes to MQ resources can be coordinated by the queue manager in the unit of work. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows. Completion Code: MQCC_WARNING Programmer Response: If the application does not require non-MQ resources to participate in the unit of work, this reason code can be ignored or the MQBEGIN call removed. Otherwise consult your system programmer to determine why the required resource managers have not been registered with the queue manager; the queue manager's configuration file may be in error. 2122 (X'084A')MQRC_PARTICIPANT_NOT_AVAILABLE Explanation: An MQBEGIN call was issued to start a unit of work coordinated by the queue manager, but one or more of the participating resource managers that had been registered with the queue manager is not available. As a result, changes to those resources cannot be coordinated by the queue manager in the unit of work. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows. Completion Code: MQCC_WARNING Programmer Response: If the application does not require non-MQ resources to participate in the unit of work, this reason code can be ignored. Otherwise consult your system programmer to determine why the required resource managers are not available. The resource manager may have been halted temporarily, or there may be an error in the queue manager's configuration file. 2123 (X'084B')MQRC_OUTCOME_MIXED Explanation: The queue manager is acting as the unit-of-work coordinator for a unit of work that involves other resource managers, but one of the following occurred: An MQCMIT or MQDISC call was issued to commit the unit of work, but one or more of the participating resource managers backed-out the unit of work instead of committing it. As a result, the outcome of the unit of work is mixed. An MQBACK call was issued to back out a unit of work, but one or more of the participating resource managers had already committed the unit of work. This reason code occurs in the following environments: AIX, HP-UX, OS/2, Solaris, Windows. Completion Code: MQCC_FAILED Programmer Response: Examine the queue-manager error logs for messages relating to the mixed outcome; these messages identify the resource managers that are affected. Use procedures local to the affected resource managers to resynchronize the resources. This reason code does not prevent the application initiating further units of work. 2124 (X'084C')MQRC_OUTCOME_PENDING Explanation: The queue manager is acting as the unit-of-work coordinator for a unit of work that involves other resource managers, and an MQCMIT or MQDISC call was issued to commit the unit of work, but one or more of the participating resource managers has not confirmed that the unit of work was committed successfully. The completion of the commit operation will happen at some point in the future, but there remains the possibility that the outcome will be mixed. This reason code occurs in the following environments: AIX, HP-UX, OS/2, Solaris, Windows. Completion Code: MQCC_WARNING Programmer Response: Use the normal error-reporting mechanisms to determine whether the outcome was mixed. If it was, take appropriate action to resynchronize the resources. This reason code does not prevent the application initiating further units of work. 2125 (X'084D')MQRC_BRIDGE_STARTED Explanation: The IMS bridge has been started. Completion Code: MQCC_WARNING Programmer Response: None. This reason code is only used to identify the corresponding event message. 2126 (X'084E')MQRC_BRIDGE_STOPPED Explanation: The IMS bridge has been stopped. Completion Code: MQCC_WARNING Programmer Response: None. This reason code is only used to identify the corresponding event message. 2127 (X'084F')MQRC_ADAPTER_STORAGE_SHORTAGE Explanation: On an MQCONN call, the adapter was unable to acquire storage. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Notify the system programmer. The system programmer should determine why the system is short on storage, and take appropriate action, for example, increase the region size on the step or job card. 2128 (X'0850')MQRC_UOW_IN_PROGRESS Explanation: An MQBEGIN call was issued to start a unit of work coordinated by the queue manager, but a unit of work is already in existence for the connection handle specified. This may be a global unit of work started by a previous MQBEGIN call, or a unit of work that is local to the queue manager or one of the cooperating resource managers. No more than one unit of work can exist concurrently for a connection handle. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows. Completion Code: MQCC_FAILED Programmer Response: Review the application logic to determine why there is a unit of work already in existence. Move the MQBEGIN call to the appropriate place in the application. 2129 (X'0851')MQRC_ADAPTER_CONN_LOAD_ERROR Explanation: On an MQCONN call, the connection handling module (CSQBCON for batch and CSQQCONN for IMS) could not be loaded, so the adapter could not link to it. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Ensure that the correct library concatenation has been specified in the batch application program execution JCL, and in the queue-manager startup JCL. 2130 (X'0852')MQRC_ADAPTER_SERV_LOAD_ERROR Explanation: On an MQI call, the batch adapter could not load the API service module CSQBSRV, and so could not link to it. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Ensure that the correct library concatenation has been specified in the batch application program execution JCL, and in the queue-manager startup JCL. 2131 (X'0853')MQRC_ADAPTER_DEFS_ERROR Explanation: On an MQCONN call, the subsystem definition module (CSQBDEFV for batch and CSQQDEFV for IMS) does not contain the required control block identifier. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Check your library concatenation. If this is correct, check that the CSQBDEFV or CSQQDEFV module contains the required subsystem ID. 2132 (X'0854')MQRC_ADAPTER_DEFS_LOAD_ERROR Explanation: On an MQCONN call, the subsystem definition module (CSQBDEFV for batch and CSQQDEFV for IMS) could not be loaded. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Ensure that the correct library concatenation has been specified in the application program execution JCL, and in the queue-manager startup JCL. 2133 (X'0855')MQRC_ADAPTER_CONV_LOAD_ERROR Explanation: On an MQGET call, the adapter (batch or IMS) could not load the data conversion services modules. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Ensure that the correct library concatenation has been specified in the batch application program execution JCL, and in the queue-manager startup JCL. 2134 (X'0856')MQRC_BO_ERROR Explanation: On an MQBEGIN call, the begin-options structure MQBO is not valid, for one of the following reasons: The StrucId field is not MQBO_STRUC_ID. The Version field is not MQBO_VERSION_1. The parameter pointer is not valid. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) The queue manager cannot copy the changed structure to application storage, even though the call is successful. This can occur, for example, if the pointer points to read-only storage. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Ensure that input fields in the MQBO structure are set correctly. 2135 (X'0857')MQRC_DH_ERROR Explanation: An MQPUT or MQPUT1 call was issued, but the message data contains an MQDH structure that is not valid. Possible errors include the following: The StrucId field is not MQDH_STRUC_ID. The Version field is not MQDH_VERSION_1. The StrucLength field specifies a value that is too small to include the structure plus the arrays of MQOR and MQPMR records. The CodedCharSetId field is zero, or a negative value that is not valid. The BufferLength parameter of the call has a value that is too small to accommodate the structure (the structure extends beyond the end of the message). This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Check that the fields in the structure are set correctly. Ensure that the application sets the CodedCharSetId field to a valid value (note: MQCCSI_DEFAULT, MQCCSI_EMBEDDED, MQCCSI_Q_MGR, and MQCCSI_UNDEFINED are not valid in this field). 2136 (X'0858')MQRC_MULTIPLE_REASONS Explanation: An MQOPEN, MQPUT or MQPUT1 call was issued to open a distribution list or put a message to a distribution list, but the result of the call was not the same for all of the destinations in the list. One of the following applies: The call succeeded for some of the destinations but not others. The completion code is MQCC_WARNING in this case. The call failed for all of the destinations, but for differing reasons. The completion code is MQCC_FAILED in this case. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_WARNING or MQCC_FAILED Programmer Response: Examine the MQRR response records to identify the destinations for which the call failed, and the reason for the failure. Ensure that sufficient response records are provided by the application on the call to enable the error(s) to be determined. For the MQPUT1 call, the response records must be specified using the MQOD structure, and not the MQPMO structure. 2137 (X'0859')MQRC_OPEN_FAILED Explanation: A queue or other MQ object could not be opened successfully, for one of the following reasons: An MQCONN or MQCONNX call was issued, but the queue manager was unable to open an object that is used internally by the queue manager. As a result, processing cannot continue. The error log will contain the name of the object that could not be opened. An MQPUT call was issued to put a message to a distribution list, but the message could not be sent to the destination to which this reason code applies because that destination was not opened successfully by the MQOPEN call. This reason occurs only in the Reason field of the MQRR response record. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Do one of the following: If the error occurred on the MQCONN or MQCONNX call, ensure that the required objects exist by running the following command and then retrying the application: STRMQM -c qmgrwhere qmgr should be replaced by the name of the queue manager. If the error occurred on the MQPUT call, examine the MQRR response records specified on the MQOPEN call to determine the reason that the queue failed to open. Ensure that sufficient response records are provided by the application on the call to enable the error(s) to be determined. 2138 (X'085A')MQRC_ADAPTER_DISC_LOAD_ERROR Explanation: On an MQDISC call, the disconnect handling module (CSQBDSC for batch and CSQQDISC for IMS) could not be loaded, so the adapter could not link to it. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Ensure that the correct library concatenation has been specified in the application program execution JCL, and in the queue-manager startup JCL. Any uncommitted changes in a unit of work should be backed out. A unit of work that is coordinated by the queue manager is backed out automatically. 2139 (X'085B')MQRC_CNO_ERROR Explanation: On an MQCONNX call, the connect-options structure MQCNO is not valid, for one of the following reasons: The StrucId field is not MQCNO_STRUC_ID. The Version field specifies a value that is not valid or not supported. The parameter pointer is not valid. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) The queue manager cannot copy the changed structure to application storage, even though the call is successful. This can occur, for example, if the parameter pointer points to read-only storage. This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Ensure that input fields in the MQCNO structure are set correctly. 2140 (X'085C')MQRC_CICS_WAIT_FAILED Explanation: On any MQI call, the CICS adapter issued an EXEC CICS WAIT request, but the request was rejected by CICS. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Examine the CICS trace data for actual response codes. The most likely cause is that the task has been canceled by the operator or by the system. 2141 (X'085D')MQRC_DLH_ERROR Explanation: An MQPUT or MQPUT1 call was issued, but the message data contains an MQDLH structure that is not valid. Possible errors include the following: The StrucId field is not MQDLH_STRUC_ID. The Version field is not MQDLH_VERSION_1. The CodedCharSetId field is zero, or a negative value that is not valid. The BufferLength parameter of the call has a value that is too small to accommodate the structure (the structure extends beyond the end of the message). This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Check that the fields in the structure are set correctly. Ensure that the application sets the CodedCharSetId field to a valid value (note: MQCCSI_DEFAULT, MQCCSI_EMBEDDED, MQCCSI_Q_MGR, and MQCCSI_UNDEFINED are not valid in this field). 2142 (X'085E')MQRC_HEADER_ERROR Explanation: An MQPUT or MQPUT1 call was issued, but the message data contains an MQ header structure that is not valid. Possible errors include the following: The StrucId field is not valid. The Version field is not valid. The StrucLength field specifies a value that is too small. The CodedCharSetId field is zero, or a negative value that is not valid. The BufferLength parameter of the call has a value that is too small to accommodate the structure (the structure extends beyond the end of the message). This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Check that the fields in the structure are set correctly. Ensure that the application sets the CodedCharSetId field to a valid value (note: MQCCSI_DEFAULT, MQCCSI_EMBEDDED, MQCCSI_Q_MGR, and MQCCSI_UNDEFINED are not valid in this field). 2143 (X'085F')MQRC_SOURCE_LENGTH_ERROR Explanation: On the MQXCNVC call, the SourceLength parameter specifies a length that is less than zero or not consistent with the string's character set or content (for example, the character set is a double-byte character set, but the length is not a multiple of two). This reason also occurs if the SourceLength parameter pointer is not valid. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) This reason code can also occur on the MQGET call when the MQGMO_CONVERT option is specified. In this case it indicates that the MQRC_SOURCE_LENGTH_ERROR reason was returned by an MQXCNVC call issued by the data conversion exit. Completion Code: MQCC_WARNING or MQCC_FAILED Programmer Response: Specify a length that is zero or greater. If the reason code occurs on the MQGET call, check that the logic in the data-conversion exit is correct. 2144 (X'0860')MQRC_TARGET_LENGTH_ERROR Explanation: On the MQXCNVC call, the TargetLength parameter is not valid for one of the following reasons: TargetLength is less than zero. The TargetLength parameter pointer is not valid. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) The MQDCC_FILL_TARGET_BUFFER option is specified, but the value of TargetLength is such that the target buffer cannot be filled completely with valid characters. This can occur when TargetCCSID is a pure DBCS character set (such as UCS-2), but TargetLength specifies a length that is an odd number of bytes. This reason code can also occur on the MQGET call when the MQGMO_CONVERT option is specified. In this case it indicates that the MQRC_TARGET_LENGTH_ERROR reason was returned by an MQXCNVC call issued by the data conversion exit. Completion Code: MQCC_WARNING or MQCC_FAILED Programmer Response: Specify a length that is zero or greater. If the MQDCC_FILL_TARGET_BUFFER option is specified, and TargetCCSID is a pure DBCS character set, ensure that TargetLength specifies a length that is a multiple of two. If the reason code occurs on the MQGET call, check that the logic in the data-conversion exit is correct. 2145 (X'0861')MQRC_SOURCE_BUFFER_ERROR Explanation: On the MQXCNVC call, the SourceBuffer parameter pointer is not valid, or points to storage that cannot be accessed for the entire length specified by SourceLength. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) This reason code can also occur on the MQGET call when the MQGMO_CONVERT option is specified. In this case it indicates that the MQRC_SOURCE_BUFFER_ERROR reason was returned by an MQXCNVC call issued by the data conversion exit. Completion Code: MQCC_WARNING or MQCC_FAILED Programmer Response: Specify a valid buffer. If the reason code occurs on the MQGET call, check that the logic in the data-conversion exit is correct. 2146 (X'0862')MQRC_TARGET_BUFFER_ERROR Explanation: On the MQXCNVC call, the TargetBuffer parameter pointer is not valid, or points to read-only storage, or to storage that cannot be accessed for the entire length specified by TargetLength. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) This reason code can also occur on the MQGET call when the MQGMO_CONVERT option is specified. In this case it indicates that the MQRC_TARGET_BUFFER_ERROR reason was returned by an MQXCNVC call issued by the data conversion exit. Completion Code: MQCC_WARNING or MQCC_FAILED Programmer Response: Specify a valid buffer. If the reason code occurs on the MQGET call, check that the logic in the data-conversion exit is correct. 2148 (X'0864')MQRC_IIH_ERROR Explanation: An MQPUT or MQPUT1 call was issued, but the message data contains an MQIIH structure that is not valid. Possible errors include the following: The StrucId field is not MQIIH_STRUC_ID. The Version field is not MQIIH_VERSION_1. The StrucLength field is not MQIIH_LENGTH_1. The BufferLength parameter of the call has a value that is too small to accommodate the structure (the structure extends beyond the end of the message). This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Check that the fields in the structure are set correctly. 2149 (X'0865')MQRC_PCF_ERROR Explanation: An MQPUT or MQPUT1 call was issued to put a message containing PCF data, but the length of the message does not equal the sum of the lengths of the PCF structures present in the message. This can occur for messages with the following format names: MQFMT_ADMIN MQFMT_EVENT MQFMT_PCF This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Ensure that the length of the message specified on the MQPUT or MQPUT1 call equals the sum of the lengths of the PCF structures contained within the message data. 2150 (X'0866')MQRC_DBCS_ERROR Explanation: An error was encountered attempting to convert a double-byte character set (DBCS) string. This can occur in the following cases: On the MQXCNVC call, when the SourceCCSID parameter specifies the coded character-set identifier of a double-byte character set, but the SourceBuffer parameter does not contain a valid DBCS string. This may be because the string contains characters that are not valid DBCS characters, or because the string is a mixed SBCS/DBCS string and the shift-out/shift-in characters are not correctly paired. The completion code is MQCC_FAILED in this case. On the MQGET call, when the MQGMO_CONVERT option is specified. In this case it indicates that the MQRC_DBCS_ERROR reason code was returned by an MQXCNVC call issued by the data conversion exit. The completion code is MQCC_WARNING in this case. Completion Code: MQCC_WARNING or MQCC_FAILED Programmer Response: Specify a valid string. If the reason code occurs on the MQGET call, check that the data in the message is valid, and that the logic in the data-conversion exit is correct. 2152 (X'0868')MQRC_OBJECT_NAME_ERROR Explanation: An MQOPEN or MQPUT1 call was issued to open a distribution list (that is, the RecsPresent field in MQOD is greater than zero), but the ObjectName field is neither blank nor the null string. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: If it is intended to open a distribution list, set the ObjectName field to blanks or the null string. If it is not intended to open a distribution list, set the RecsPresent field to zero. 2153 (X'0869')MQRC_OBJECT_Q_MGR_NAME_ERROR Explanation: An MQOPEN or MQPUT1 call was issued to open a distribution list (that is, the RecsPresent field in MQOD is greater than zero), but the ObjectQMgrName field is neither blank nor the null string. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: If it is intended to open a distribution list, set the ObjectQMgrName field to blanks or the null string. If it is not intended to open a distribution list, set the RecsPresent field to zero. 2154 (X'086A')MQRC_RECS_PRESENT_ERROR Explanation: An MQOPEN or MQPUT1 call was issued, but the call failed for one of the following reasons: RecsPresent in MQOD is less than zero. ObjectType in MQOD is not MQOT_Q, and RecsPresent is not zero. RecsPresent must be zero if the object being opened is not a queue. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: If it is intended to open a distribution list, set the ObjectType field to MQOT_Q and RecsPresent to the number of destinations in the list. If it is not intended to open a distribution list, set the RecsPresent field to zero. 2155 (X'086B')MQRC_OBJECT_RECORDS_ERROR Explanation: An MQOPEN or MQPUT1 call was issued to open a distribution list (that is, the RecsPresent field in MQOD is greater than zero), but the MQOR object records are not specified correctly. One of the following applies: ObjectRecOffset is zero and ObjectRecPtr is zero or the null pointer. ObjectRecOffset is not zero and ObjectRecPtr is not zero and not the null pointer. ObjectRecPtr is not a valid pointer. ObjectRecPtr or ObjectRecOffset points to storage that is not accessible. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Ensure that one of ObjectRecOffset and ObjectRecPtr is zero and the other nonzero. Ensure that the field used points to accessible storage. 2156 (X'086C')MQRC_RESPONSE_RECORDS_ERROR Explanation: An MQOPEN or MQPUT1 call was issued to open a distribution list (that is, the RecsPresent field in MQOD is greater than zero), but the MQRR response records are not specified correctly. One of the following applies: ResponseRecOffset is not zero and ResponseRecPtr is not zero and not the null pointer. ResponseRecPtr is not a valid pointer. ResponseRecPtr or ResponseRecOffset points to storage that is not accessible. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Ensure that at least one of ResponseRecOffset and ResponseRecPtr is zero. Ensure that the field used points to accessible storage. 2157 (X'086D')MQRC_ASID_MISMATCH Explanation: On any MQI call, the caller's primary ASID was found to be different from the home ASID. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Correct the application (MQI calls cannot be issued in cross-memory mode). Any uncommitted changes in a unit of work should be backed out. A unit of work that is coordinated by the queue manager is backed out automatically. 2158 (X'086E')MQRC_PMO_RECORD_FLAGS_ERROR Explanation: An MQPUT or MQPUT1 call was issued to put a message, but the PutMsgRecFields field in the MQPMO structure is not valid, for one of the following reasons: The field contains flags that are not valid. The message is being put to a distribution list, and put message records have been provided (that is, RecsPresent is greater than zero, and one of PutMsgRecOffset or PutMsgRecPtr is nonzero), but PutMsgRecFields has the value MQPMRF_NONE. MQPMRF_ACCOUNTING_TOKEN is specified without either MQPMO_SET_IDENTITY_CONTEXT or MQPMO_SET_ALL_CONTEXT. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Ensure that PutMsgRecFields is set with the appropriate MQPMRF_* flags to indicate which fields are present in the put message records. If MQPMRF_ACCOUNTING_TOKEN is specified, ensure that either MQPMO_SET_IDENTITY_CONTEXT or MQPMO_SET_ALL_CONTEXT is also specified. Alternatively, set both PutMsgRecOffset and PutMsgRecPtr to zero. 2159 (X'086F')MQRC_PUT_MSG_RECORDS_ERROR Explanation: An MQPUT or MQPUT1 call was issued to put a message to a distribution list, but the MQPMR put message records are not specified correctly. One of the following applies: PutMsgRecOffset is not zero and PutMsgRecPtr is not zero and not the null pointer. PutMsgRecPtr is not a valid pointer. PutMsgRecPtr or PutMsgRecOffset points to storage that is not accessible. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Ensure that at least one of PutMsgRecOffset and PutMsgRecPtr is zero. Ensure that the field used points to accessible storage. 2160 (X'0870')MQRC_CONN_ID_IN_USE Explanation: On an MQCONN call, the connection identifier assigned by the queue manager to the connection between a CICS or IMS allied address space and the queue manager conflicts with the connection identifier of another connected CICS or IMS system. The connection identifier assigned is as follows: For CICS, the applid For IMS, the IMSID parameter on the IMSCTRL (sysgen) macro, or the IMSID parameter on the execution parameter (EXEC card in IMS control region JCL) For batch, the job name For TSO, the user ID A conflict arises only if there are two CICS systems, two IMS systems, or one each of CICS and IMS, having the same connection identifiers. Batch and TSO connections need not have unique identifiers. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Ensure that the naming conventions used in different systems that might connect to the queue manager do not conflict. 2161 (X'0871')MQRC_Q_MGR_QUIESCING Explanation: An MQI call was issued, but the call failed because the queue manager is quiescing (preparing to shut down). When the queue manager is quiescing, the MQOPEN, MQPUT, MQPUT1, and MQGET calls can still complete successfully, but the application can request that they fail by specifying the appropriate option on the call: MQOO_FAIL_IF_QUIESCING on MQOPEN MQPMO_FAIL_IF_QUIESCING on MQPUT or MQPUT1 MQGMO_FAIL_IF_QUIESCING on MQGET Specifying these options enables the application to become aware that the queue manager is preparing to shut down. On z/OS: For batch applications, this reason can be returned to applications running in LPARs that do not have a queue manager installed. For CICS applications, this reason can be returned when no connection was established. On i5/OS for applications running in compatibility mode, this reason can be returned when no connection was established. Completion Code: MQCC_FAILED Programmer Response: The application should tidy up and end. If the application specified the MQOO_FAIL_IF_QUIESCING, MQPMO_FAIL_IF_QUIESCING, or MQGMO_FAIL_IF_QUIESCING option on the failing call, the relevant option can be removed and the call reissued. By omitting these options, the application can continue working in order to complete and commit the current unit of work, but the application should not start a new unit of work. 2162 (X'0872')MQRC_Q_MGR_STOPPING Explanation: An MQI call was issued, but the call failed because the queue manager is shutting down. If the call was an MQGET call with the MQGMO_WAIT option, the wait has been canceled. No more MQI calls can be issued. For MQ client applications, it is possible that the call did complete successfully, even though this reason code is returned with a CompCode of MQCC_FAILED. On z/OS, the MQRC_CONNECTION_BROKEN reason may be returned instead if, as a result of system scheduling factors, the queue manager shuts down before the call completes. Completion Code: MQCC_FAILED Programmer Response: The application should tidy up and end. If the application is in the middle of a unit of work coordinated by an external unit-of-work coordinator, the application should issue the appropriate call to back out the unit of work. Any unit of work that is coordinated by the queue manager is backed out automatically. 2163 (X'0873')MQRC_DUPLICATE_RECOV_COORD Explanation: On an MQCONN or MQCONNX call, a recovery coordinator already exists for the connection name specified on the connection call issued by the adapter. A conflict arises only if there are two CICS systems, two IMS systems, or one each of CICS and IMS, having the same connection identifiers. Batch and TSO connections need not have unique identifiers. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Ensure that the naming conventions used in different systems that might connect to the queue manager do not conflict. 2173 (X'087D')MQRC_PMO_ERROR Explanation: On an MQPUT or MQPUT1 call, the MQPMO structure is not valid, for one of the following reasons: The StrucId field is not MQPMO_STRUC_ID. The Version field specifies a value that is not valid or not supported. The parameter pointer is not valid. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) The queue manager cannot copy the changed structure to application storage, even though the call is successful. This can occur, for example, if the pointer points to read-only storage. Completion Code: MQCC_FAILED Programmer Response: Ensure that input fields in the MQPMO structure are set correctly. 2183 (X'0887')MQRC_API_EXIT_LOAD_ERROR Explanation: The API crossing exit module could not be linked. If this reason is returned when the API crossing exit is invoked after the call has been executed, the call itself may have executed correctly. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Ensure that the correct library concatenation has been specified, and that the API crossing exit module is executable and correctly named. Any uncommitted changes in a unit of work should be backed out. A unit of work that is coordinated by the queue manager is backed out automatically. 2184 (X'0888')MQRC_REMOTE_Q_NAME_ERROR Explanation: On an MQOPEN or MQPUT1 call, one of the following occurred: A local definition of a remote queue (or an alias to one) was specified, but the RemoteQName attribute in the remote queue definition is entirely blank. Note that this error occurs even if the XmitQName in the definition is not blank. The ObjectQMgrName field in the object descriptor is not blank and not the name of the local queue manager, but the ObjectName field is blank. Completion Code: MQCC_FAILED Programmer Response: Alter the local definition of the remote queue and supply a valid remote queue name, or supply a nonblank ObjectName in the object descriptor, as appropriate. 2185 (X'0889')MQRC_INCONSISTENT_PERSISTENCE Explanation: An MQPUT call was issued to put a message in a group or a segment of a logical message, but the value specified or defaulted for the Persistence field in MQMD is not consistent with the current group and segment information retained by the queue manager for the queue handle. All messages in a group and all segments in a logical message must have the same value for persistence, that is, all must be persistent, or all must be nonpersistent. If the current call specifies MQPMO_LOGICAL_ORDER, the call fails. If the current call does not specify MQPMO_LOGICAL_ORDER, but the previous MQPUT call for the queue handle did, the call succeeds with completion code MQCC_WARNING. This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_WARNING or MQCC_FAILED Programmer Response: Modify the application to ensure that the same value of persistence is used for all messages in the group, or all segments of the logical message. 2186 (X'088A')MQRC_GMO_ERROR Explanation: On an MQGET call, the MQGMO structure is not valid, for one of the following reasons: The StrucId field is not MQGMO_STRUC_ID. The Version field specifies a value that is not valid or not supported. The parameter pointer is not valid. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) The queue manager cannot copy the changed structure to application storage, even though the call is successful. This can occur, for example, if the pointer points to read-only storage. Completion Code: MQCC_FAILED Programmer Response: Ensure that input fields in the MQGMO structure are set correctly. 2187 (X'088B')MQRC_CICS_BRIDGE_RESTRICTION Explanation: It is not permitted to issue MQI calls from user transactions that are run in an MQ/CICS-bridge environment where the bridge exit also issues MQI calls. The MQI call fails. If this occurs in the bridge exit, it will result in a transaction abend. If it occurs in the user transaction, this may result in a transaction abend. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: The transaction cannot be run using the MQ/CICS bridge. Refer to the appropriate CICS manual for information about restrictions in the MQ/CICS bridge environment. 2188 (X'088C')MQRC_STOPPED_BY_CLUSTER_EXIT Explanation: An MQOPEN, MQPUT, or MQPUT1 call was issued to open or put a message on a cluster queue, but the cluster workload exit rejected the call. This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Check the cluster workload exit to ensure that it has been written correctly. Determine why it rejected the call and correct the problem. 2189 (X'088D')MQRC_CLUSTER_RESOLUTION_ERROR Explanation: An MQOPEN, MQPUT, or MQPUT1 call was issued to open or put a message on a cluster queue, but the queue definition could not be resolved correctly because a response was required from the repository manager but none was available. This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Check that the repository manager is operating and that the queue and channel definitions are correct. 2190 (X'088E')MQRC_CONVERTED_STRING_TOO_BIG Explanation: On an MQGET call with the MQGMO_CONVERT option included in the GetMsgOpts parameter, a string in a fixed-length field in the message expanded during data conversion and exceeded the size of the field. When this happens, the queue manager tries discarding trailing blank characters and characters following the first null character in order to make the string fit, but in this case there were insufficient characters that could be discarded. This reason code can also occur for messages with a format name of MQFMT_IMS_VAR_STRING. When this happens, it indicates that the IMS variable string expanded such that its length exceeded the capacity of the 2-byte binary length field contained within the structure of the IMS variable string. (The queue manager never discards trailing blanks in an IMS variable string.) The message is returned unconverted, with the CompCode parameter of the MQGET call set to MQCC_WARNING. If the message consists of several parts, each of which is described by its own character-set and encoding fields (for example, a message with format name MQFMT_DEAD_LETTER_HEADER), some parts may be converted and other parts not converted. However, the values returned in the various character-set and encoding fields always correctly describe the relevant message data. This reason code does not occur if the string could be made to fit by discarding trailing blank characters. Completion Code: MQCC_WARNING Programmer Response: Check that the fields in the message contain the correct values, and that the character-set identifiers specified by the sender and receiver of the message are correct. If they are, the layout of the data in the message must be modified to increase the lengths of the field(s) so that there is sufficient space to allow the string(s) to expand when converted. 2191 (X'088F')MQRC_TMC_ERROR Explanation: An MQPUT or MQPUT1 call was issued, but the message data contains an MQTMC2 structure that is not valid. Possible errors include the following: The StrucId field is not MQTMC_STRUC_ID. The Version field is not MQTMC_VERSION_2. The BufferLength parameter of the call has a value that is too small to accommodate the structure (the structure extends beyond the end of the message). This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Check that the fields in the structure are set correctly. 2192 (X'0890')MQRC_PAGESET_FULL Explanation: Former name for MQRC_STORAGE_MEDIUM_FULL. 2192 (X'0890')MQRC_STORAGE_MEDIUM_FULL Explanation: An MQI call or command was issued to operate on an object, but the call failed because the external storage medium is full. One of the following applies: A page-set data set is full (nonshared queues only). A coupling-facility structure is full (shared queues only). This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Check which queues contain messages and look for applications that might be filling the queues unintentionally. Be aware that the queue that has caused the page set or coupling-facility structure to become full is not necessarily the queue referenced by the MQI call that returned MQRC_STORAGE_MEDIUM_FULL. Check that all of the usual server applications are operating correctly and processing the messages on the queues. If the applications and servers are operating correctly, increase the number of server applications to cope with the message load, or request the system programmer to increase the size of the page-set data sets. 2193 (X'0891')MQRC_PAGESET_ERROR Explanation: An error was encountered with the page set while attempting to access it for a locally defined queue. This could be because the queue is on a page set that does not exist. A console message is issued that tells you the number of the page set in error. For example if the error occurred in the TEST job, and your user identifier is ABCDEFG, the message is: CSQI041I CSQIALLC JOB TEST USER ABCDEFG HAD ERROR ACCESSING PAGE SET 27If this reason code occurs while attempting to delete a dynamic queue with MQCLOSE, the dynamic queue has not been deleted. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Check that the storage class for the queue maps to a valid page set using the DISPLAY Q(xx) STGCLASS, DISPLAY STGCLASS(xx), and DISPLAY USAGE PSID commands. If you are unable to resolve the problem, notify the system programmer who should: Collect the following diagnostic information: A description of the actions that led to the error A listing of the application program being run at the time of the error Details of the page sets defined for use by the queue manager Attempt to re-create the problem, and take a system dump immediately after the error occurs Contact your IBM Support Center 2194 (X'0892')MQRC_NAME_NOT_VALID_FOR_TYPE Explanation: An MQOPEN call was issued to open the queue manager definition, but the ObjectName field in the ObjDesc parameter is not blank. Completion Code: MQCC_FAILED Programmer Response: Ensure that the ObjectName field is set to blanks. 2195 (X'0893')MQRC_UNEXPECTED_ERROR Explanation: The call was rejected because an unexpected error occurred. Completion Code: MQCC_FAILED Programmer Response: Check the application's parameter list to ensure, for example, that the correct number of parameters was passed, and that data pointers and storage keys are valid. If the problem cannot be resolved, contact your system programmer. On z/OS, check whether any information has been displayed on the console. If this error occurs on an MQCONN or MQCONNX call, check that the subsystem named is an active MQ subsystem. In particular, check that it is not a DB2(TM) subsystem. If the problem cannot be resolved, rerun the application with a CSQSNAP DD card (if you have not already got a dump) and send the resulting dump to IBM. On OS/2 and i5/OS, consult the FFST record to obtain more detail about the problem. On HP OpenVMS, Compaq NonStop Kernel, and UNIX systems, consult the FDC file to obtain more detail about the problem. 2196 (X'0894')MQRC_UNKNOWN_XMIT_Q Explanation: On an MQOPEN or MQPUT1 call, a message is to be sent to a remote queue manager. The ObjectName or the ObjectQMgrName in the object descriptor specifies the name of a local definition of a remote queue (in the latter case queue-manager aliasing is being used), but the XmitQName attribute of the definition is not blank and not the name of a locally-defined queue. Completion Code: MQCC_FAILED Programmer Response: Check the values specified for ObjectName and ObjectQMgrName. If these are correct, check the queue definitions. For more information on transmission queues, see the WebSphere MQ Application Programming Guide. 2197 (X'0895')MQRC_UNKNOWN_DEF_XMIT_Q Explanation: An MQOPEN or MQPUT1 call was issued specifying a remote queue as the destination. If a local definition of the remote queue was specified, or if a queue-manager alias is being resolved, the XmitQName attribute in the local definition is blank. Because there is no queue defined with the same name as the destination queue manager, the queue manager has attempted to use the default transmission queue. However, the name defined by the DefXmitQName queue-manager attribute is not the name of a locally-defined queue. Completion Code: MQCC_FAILED Programmer Response: Correct the queue definitions, or the queue-manager attribute. See the WebSphere MQ Application Programming Guide for more information. 2198 (X'0896')MQRC_DEF_XMIT_Q_TYPE_ERROR Explanation: An MQOPEN or MQPUT1 call was issued specifying a remote queue as the destination. Either a local definition of the remote queue was specified, or a queue-manager alias was being resolved, but in either case the XmitQName attribute in the local definition is blank. Because there is no transmission queue defined with the same name as the destination queue manager, the local queue manager has attempted to use the default transmission queue. However, although there is a queue defined by the DefXmitQName queue-manager attribute, it is not a local queue. Completion Code: MQCC_FAILED Programmer Response: Do one of the following: Specify a local transmission queue as the value of the XmitQName attribute in the local definition of the remote queue. Define a local transmission queue with a name that is the same as that of the remote queue manager. Specify a local transmission queue as the value of the DefXmitQName queue-manager attribute. See the WebSphere MQ Application Programming Guide for more information. 2199 (X'0897')MQRC_DEF_XMIT_Q_USAGE_ERROR Explanation: An MQOPEN or MQPUT1 call was issued specifying a remote queue as the destination. Either a local definition of the remote queue was specified, or a queue-manager alias was being resolved, but in either case the XmitQName attribute in the local definition is blank. Because there is no transmission queue defined with the same name as the destination queue manager, the local queue manager has attempted to use the default transmission queue. However, the queue defined by the DefXmitQName queue-manager attribute does not have a Usage attribute of MQUS_TRANSMISSION. Completion Code: MQCC_FAILED Programmer Response: Do one of the following: Specify a local transmission queue as the value of the XmitQName attribute in the local definition of the remote queue. Define a local transmission queue with a name that is the same as that of the remote queue manager. Specify a different local transmission queue as the value of the DefXmitQName queue-manager attribute. Change the Usage attribute of the DefXmitQName queue to MQUS_TRANSMISSION. See the WebSphere MQ Application Programming Guide for more information. 2201 (X'0899')MQRC_NAME_IN_USE Explanation: An MQOPEN call was issued to create a dynamic queue, but a queue with the same name as the dynamic queue already exists. The existing queue is one that is logically deleted, but for which there are still one or more open handles. For more information, see the description of MQCLOSE in the WebSphere MQ Application Programming Guide. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Either ensure that all handles for the previous dynamic queue are closed, or ensure that the name of the new queue is unique; see the description for reason code MQRC_OBJECT_ALREADY_EXISTS. 2202 (X'089A')MQRC_CONNECTION_QUIESCING Explanation: This reason code is issued when the connection to the queue manager is in quiescing state, and an application issues one of the following calls: MQCONN or MQCONNX MQOPEN, with no connection established, or with MQOO_FAIL_IF_QUIESCING included in the Options parameter MQGET, with MQGMO_FAIL_IF_QUIESCING included in the Options field of the GetMsgOpts parameter MQPUT or MQPUT1, with MQPMO_FAIL_IF_QUIESCING included in the Options field of the PutMsgOpts parameter MQRC_CONNECTION_QUIESCING is also issued by the message channel agent (MCA) when the queue manager is in quiescing state. Completion Code: MQCC_FAILED Programmer Response: The application should tidy up and terminate. Any uncommitted changes in a unit of work should be backed out. 2203 (X'089B')MQRC_CONNECTION_STOPPING Explanation: This reason code is issued when the connection to the queue manager is shutting down, and the application issues an MQI call. No more message-queuing calls can be issued. For the MQGET call, if the MQGMO_WAIT option was specified, the wait is canceled. Note that the MQRC_CONNECTION_BROKEN reason may be returned instead if, as a result of system scheduling factors, the queue manager shuts down before the call completes. MQRC_CONNECTION_STOPPING is also issued by the message channel agent (MCA) when the queue manager is shutting down. For MQ client applications, it is possible that the call did complete successfully, even though this reason code is returned with a CompCode of MQCC_FAILED. Completion Code: MQCC_FAILED Programmer Response: The application should tidy up and terminate. Any uncommitted changes in a unit of work should be backed out. A unit of work that is coordinated by the queue manager is backed out automatically. 2204 (X'089C')MQRC_ADAPTER_NOT_AVAILABLE Explanation: This is issued only for CICS applications, if any call is issued and the CICS adapter (a Task Related User Exit) has been disabled, or has not been enabled. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: The application should tidy up and terminate. Any uncommitted changes in a unit of work should be backed out. A unit of work that is coordinated by the queue manager is backed out automatically. 2206 (X'089E')MQRC_MSG_ID_ERROR Explanation: An MQGET call was issued to retrieve a message using the message identifier as a selection criterion, but the call failed because selection by message identifier is not supported on this queue. On z/OS, the queue is a shared queue, but the IndexType queue attribute does not have an appropriate value: If selection is by message identifier alone, IndexType must have the value MQIT_MSG_ID. If selection is by message identifier and correlation identifier combined, IndexType must have the value MQIT_MSG_ID or MQIT_CORREL_ID. On Compaq NonStop Kernel, a key file is required but has not been defined. Completion Code: MQCC_FAILED Programmer Response: Do one of the following: Modify the application so that it does not use selection by message identifier: set the MsgId field to MQMI_NONE and do not specify MQMO_MATCH_MSG_ID in MQGMO. On z/OS, change the IndexType queue attribute to MQIT_MSG_ID. On Compaq NonStop Kernel, define a key file. 2207 (X'089F')MQRC_CORREL_ID_ERROR Explanation: An MQGET call was issued to retrieve a message using the correlation identifier as a selection criterion, but the call failed because selection by correlation identifier is not supported on this queue. On z/OS, the queue is a shared queue, but the IndexType queue attribute does not have an appropriate value: If selection is by correlation identifier alone, IndexType must have the value MQIT_CORREL_ID. If selection is by correlation identifier and message identifier combined, IndexType must have the value MQIT_CORREL_ID or MQIT_MSG_ID. On Compaq NonStop Kernel, a key file is required but has not been defined. Completion Code: MQCC_FAILED Programmer Response: Do one of the following: On z/OS, change the IndexType queue attribute to MQIT_CORREL_ID. On Compaq NonStop Kernel, define a key file. Modify the application so that it does not use selection by correlation identifier: set the CorrelId field to MQCI_NONE and do not specify MQMO_MATCH_CORREL_ID in MQGMO. 2208 (X'08A0')MQRC_FILE_SYSTEM_ERROR Explanation: An unexpected return code was received from the file system, in attempting to perform an operation on a queue. This reason code occurs only on VSE/ESA. Completion Code: MQCC_FAILED Programmer Response: Check the file system definition for the queue that was being accessed. For a VSAM file, check that the control interval is large enough for the maximum message length allowed for the queue. 2209 (X'08A1')MQRC_NO_MSG_LOCKED Explanation: An MQGET call was issued with the MQGMO_UNLOCK option, but no message was currently locked. Completion Code: MQCC_WARNING Programmer Response: Check that a message was locked by an earlier MQGET call with the MQGMO_LOCK option for the same handle, and that no intervening call has caused the message to become unlocked. 2210 (X'08A2')MQRC_SOAP_DOTNET_ERROR Explanation: An exception from the .NET environment (as opposed to WebSphere MQ .NET) has been received and is included as an inner exception. Completion Code: MQCC_FAILED Programmer Response: Refer to the .NET documentation for details about the inner exception. Follow the corrective action recommended there. 2211 (X'08A3')MQRC_SOAP_AXIS_ERROR Explanation: An exception from the Axis environment has been received and is included as a chained exception. Completion Code: MQCC_FAILED Programmer Response: Refer to the Axis documentation for details about the chained exception. Follow the corrective action recommended there. 2212 (X'08A4')MQRC_SOAP_URL_ERROR Explanation: The SOAP URL has been specified incorrectly. Completion Code: MQCC_FAILED Programmer Response: Correct the SOAP URL and rerun. 2217 (X'08A9')MQRC_CONNECTION_NOT_AUTHORIZED Explanation: This reason code arises only for CICS applications. For these, connection to the queue manager is done by the adapter. If that connection fails because the CICS subsystem is not authorized to connect to the queue manager, this reason code is issued whenever an application running under that subsystem subsequently issues an MQI call. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Ensure that the subsystem is authorized to connect to the queue manager. 2218 (X'08AA')MQRC_MSG_TOO_BIG_FOR_CHANNEL Explanation: A message was put to a remote queue, but the message is larger than the maximum message length allowed by the channel. This reason code is returned in the Feedback field in the message descriptor of a report message. On z/OS, this return code is issued only if you are not using CICS for distributed queuing. Otherwise, MQRC_MSG_TOO_BIG_FOR_Q_MGR is issued. Completion Code: MQCC_FAILED Programmer Response: Check the channel definitions. Increase the maximum message length that the channel can accept, or break the message into several smaller messages. 2219 (X'08AB')MQRC_CALL_IN_PROGRESS Explanation: The application issued an MQI call whilst another MQI call was already being processed for that connection. Only one call per application connection can be processed at a time. Concurrent calls can arise when an application uses multiple threads, or when an exit is invoked as part of the processing of an MQI call. For example, a data-conversion exit invoked as part of the processing of the MQGET call may try to issue an MQI call. On z/OS, concurrent calls can arise only with batch or IMS applications; an example is when a subtask ends while an MQI call is in progress (for example, an MQGET that is waiting), and there is an end-of-task exit routine that issues another MQI call. On OS/2 and Windows, concurrent calls can also arise if an MQI call is issued in response to a user message while another MQI call is in progress. If the application is using multiple threads with shared handles, MQRC_CALL_IN_PROGRESS occurs when the handle specified on the call is already in use by another thread and MQCNO_HANDLE_SHARE_NO_BLOCK was specified on the MQCONNX call. Completion Code: MQCC_FAILED Programmer Response: Ensure that an MQI call cannot be issued while another one is active. Do not issue MQI calls from within a data-conversion exit. On z/OS, if you want to provide a subtask to allow an application that is waiting for a message to arrive to be canceled, wait for the message by using MQGET with MQGMO_SET_SIGNAL, rather than MQGMO_WAIT. 2220 (X'08AC')MQRC_RMH_ERROR Explanation: An MQPUT or MQPUT1 call was issued, but the message data contains an MQRMH structure that is not valid. Possible errors include the following: The StrucId field is not MQRMH_STRUC_ID. The Version field is not MQRMH_VERSION_1. The StrucLength field specifies a value that is too small to include the structure plus the variable-length data at the end of the structure. The CodedCharSetId field is zero, or a negative value that is not valid. The BufferLength parameter of the call has a value that is too small to accommodate the structure (the structure extends beyond the end of the message). This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Check that the fields in the structure are set correctly. Ensure that the application sets the CodedCharSetId field to a valid value (note: MQCCSI_DEFAULT, MQCCSI_EMBEDDED, MQCCSI_Q_MGR, and MQCCSI_UNDEFINED are not valid in this field). 2222 (X'08AE')MQRC_Q_MGR_ACTIVE Explanation: This condition is detected when a queue manager becomes active. On z/OS, this event is not generated for the first start of a queue manager, only on subsequent restarts. Completion Code: MQCC_WARNING Programmer Response: None. This reason code is only used to identify the corresponding event message. 2223 (X'08AF')MQRC_Q_MGR_NOT_ACTIVE Explanation: This condition is detected when a queue manager is requested to stop or quiesce. Completion Code: MQCC_WARNING Programmer Response: None. This reason code is only used to identify the corresponding event message. 2224 (X'08B0')MQRC_Q_DEPTH_HIGH Explanation: An MQPUT or MQPUT1 call has caused the queue depth to be incremented to or above the limit specified in the QDepthHighLimit attribute. Completion Code: MQCC_WARNING Programmer Response: None. This reason code is only used to identify the corresponding event message. 2225 (X'08B1')MQRC_Q_DEPTH_LOW Explanation: An MQGET call has caused the queue depth to be decremented to or below the limit specified in the QDepthLowLimit attribute. Completion Code: MQCC_WARNING Programmer Response: None. This reason code is only used to identify the corresponding event message. 2226 (X'08B2')MQRC_Q_SERVICE_INTERVAL_HIGH Explanation: No successful gets or puts have been detected within an interval that is greater than the limit specified in the QServiceInterval attribute. Completion Code: MQCC_WARNING Programmer Response: None. This reason code is only used to identify the corresponding event message. 2227 (X'08B3')MQRC_Q_SERVICE_INTERVAL_OK Explanation: A successful get has been detected within an interval that is less than or equal to the limit specified in the QServiceInterval attribute. Completion Code: MQCC_WARNING Programmer Response: None. This reason code is only used to identify the corresponding event message. 2228 (X'08B4')MQRC_RFH_HEADER_FIELD_ERROR Explanation: An expected RFH header field was not found or had an invalid value. If this error occurs in a WebSphere MQ SOAP listener, the missing or erroneous field is either the contentType field or the transportVersion field or both. Completion Code: MQCC_FAILED Programmer Response: If this error occurs in a WebSphere MQ SOAP listener, and you are using the IBM-supplied sender, contact your IBM Support Center. If you are using a bespoke sender, check the associated error message, and that the RFH2 section of the SOAP/MQ request message contains all the mandatory fields, and that these fields have valid values. 2229 (X'08B5')MQRC_RAS_PROPERTY_ERROR Explanation: There is an error related to the RAS property file. The file may be missing, it may be not accessible, or the commands in the file may be incorrect. Completion Code: MQCC_FAILED Programmer Response: Look at the associated error message, which will explain the error in detail. Correct the error and retry. 2232 (X'08B8')MQRC_UNIT_OF_WORK_NOT_STARTED Explanation: An MQGET, MQPUT or MQPUT1 call was issued to get or put a message within a unit of work, but no TM/MP transaction had been started. If MQGMO_NO_SYNCPOINT is not specified on MQGET, or MQPMO_NO_SYNCPOINT is not specified on MQPUT or MQPUT1 (the default), the call requires a unit of work. Completion Code: MQCC_FAILED Programmer Response: Ensure a TM/MP transaction is available, or issue the MQGET call with the MQGMO_NO_SYNCPOINT option, or the MQPUT or MQPUT1 call with the MQPMO_NO_SYNCPOINT option, which will cause a transaction to be started automatically. 2233 (X'08B9')MQRC_CHANNEL_AUTO_DEF_OK Explanation: This condition is detected when the automatic definition of a channel is successful. The channel is defined by the MCA. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_WARNING Programmer Response: None. This reason code is only used to identify the corresponding event message. 2234 (X'08BA')MQRC_CHANNEL_AUTO_DEF_ERROR Explanation: This condition is detected when the automatic definition of a channel fails; this may be because an error occurred during the definition process, or because the channel automatic-definition exit inhibited the definition. Additional information is returned in the event message indicating the reason for the failure. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_WARNING Programmer Response: Examine the additional information returned in the event message to determine the reason for the failure. 2235 (X'08BB')MQRC_CFH_ERROR Explanation: An MQPUT or MQPUT1 call was issued, but the message data contains an MQCFH structure that is not valid. This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Check that the fields in the structure are set correctly. 2236 (X'08BC')MQRC_CFIL_ERROR Explanation: An MQPUT or MQPUT1 call was issued, but the message data contains an MQCFIL or MQRCFIL64 structure that is not valid. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Check that the fields in the structure are set correctly. 2237 (X'08BD')MQRC_CFIN_ERROR Explanation: An MQPUT or MQPUT1 call was issued, but the message data contains an MQCFIN or MQCFIN64 structure that is not valid. This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Check that the fields in the structure are set correctly. 2238 (X'08BE')MQRC_CFSL_ERROR Explanation: An MQPUT or MQPUT1 call was issued, but the message data contains an MQCFSL structure that is not valid. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Check that the fields in the structure are set correctly. 2239 (X'08BF')MQRC_CFST_ERROR Explanation: An MQPUT or MQPUT1 call was issued, but the message data contains an MQCFST structure that is not valid. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Check that the fields in the structure are set correctly. 2241 (X'08C1')MQRC_INCOMPLETE_GROUP Explanation: An operation was attempted on a queue using a queue handle that had an incomplete message group. This reason code can arise in the following situations: On the MQPUT call, when the application specifies MQPMO_LOGICAL_ORDER and attempts to put a message that is not in a group. The completion code is MQCC_FAILED in this case. On the MQPUT call, when the application does not specify MQPMO_LOGICAL_ORDER, but the previous MQPUT call for the queue handle did specify MQPMO_LOGICAL_ORDER. The completion code is MQCC_WARNING in this case. On the MQGET call, when the application does not specify MQGMO_LOGICAL_ORDER, but the previous MQGET call for the queue handle did specify MQGMO_LOGICAL_ORDER. The completion code is MQCC_WARNING in this case. On the MQCLOSE call, when the application attempts to close the queue that has the incomplete message group. The completion code is MQCC_WARNING in this case. If there is an incomplete logical message as well as an incomplete message group, reason code MQRC_INCOMPLETE_MSG is returned in preference to MQRC_INCOMPLETE_GROUP. This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_WARNING or MQCC_FAILED Programmer Response: If this reason code is expected, no corrective action is required. Otherwise, ensure that the MQPUT call for the last message in the group specifies MQMF_LAST_MSG_IN_GROUP. 2242 (X'08C2')MQRC_INCOMPLETE_MSG Explanation: An operation was attempted on a queue using a queue handle that had an incomplete logical message. This reason code can arise in the following situations: On the MQPUT call, when the application specifies MQPMO_LOGICAL_ORDER and attempts to put a message that is not a segment, or that has a setting for the MQMF_LAST_MSG_IN_GROUP flag that is different from the previous message. The completion code is MQCC_FAILED in this case. On the MQPUT call, when the application does not specify MQPMO_LOGICAL_ORDER, but the previous MQPUT call for the queue handle did specify MQPMO_LOGICAL_ORDER. The completion code is MQCC_WARNING in this case. On the MQGET call, when the application does not specify MQGMO_LOGICAL_ORDER, but the previous MQGET call for the queue handle did specify MQGMO_LOGICAL_ORDER. The completion code is MQCC_WARNING in this case. On the MQCLOSE call, when the application attempts to close the queue that has the incomplete logical message. The completion code is MQCC_WARNING in this case. This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_WARNING or MQCC_FAILED Programmer Response: If this reason code is expected, no corrective action is required. Otherwise, ensure that the MQPUT call for the last segment specifies MQMF_LAST_SEGMENT. 2243 (X'08C3')MQRC_INCONSISTENT_CCSIDS Explanation: An MQGET call was issued specifying the MQGMO_COMPLETE_MSG option, but the message to be retrieved consists of two or more segments that have differing values for the CodedCharSetId field in MQMD. This can arise when the segments take different paths through the network, and some of those paths have MCA sender conversion enabled. The call succeeds with a completion code of MQCC_WARNING, but only the first few segments that have identical character-set identifiers are returned. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_WARNING Programmer Response: Remove the MQGMO_COMPLETE_MSG option from the MQGET call and retrieve the remaining message segments one by one. 2244 (X'08C4')MQRC_INCONSISTENT_ENCODINGS Explanation: An MQGET call was issued specifying the MQGMO_COMPLETE_MSG option, but the message to be retrieved consists of two or more segments that have differing values for the Encoding field in MQMD. This can arise when the segments take different paths through the network, and some of those paths have MCA sender conversion enabled. The call succeeds with a completion code of MQCC_WARNING, but only the first few segments that have identical encodings are returned. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_WARNING Programmer Response: Remove the MQGMO_COMPLETE_MSG option from the MQGET call and retrieve the remaining message segments one by one. 2245 (X'08C5')MQRC_INCONSISTENT_UOW Explanation: One of the following applies: An MQPUT call was issued to put a message in a group or a segment of a logical message, but the value specified or defaulted for the MQPMO_SYNCPOINT option is not consistent with the current group and segment information retained by the queue manager for the queue handle. If the current call specifies MQPMO_LOGICAL_ORDER, the call fails. If the current call does not specify MQPMO_LOGICAL_ORDER, but the previous MQPUT call for the queue handle did, the call succeeds with completion code MQCC_WARNING. An MQGET call was issued to remove from the queue a message in a group or a segment of a logical message, but the value specified or defaulted for the MQGMO_SYNCPOINT option is not consistent with the current group and segment information retained by the queue manager for the queue handle. If the current call specifies MQGMO_LOGICAL_ORDER, the call fails. If the current call does not specify MQGMO_LOGICAL_ORDER, but the previous MQGET call for the queue handle did, the call succeeds with completion code MQCC_WARNING. This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_WARNING or MQCC_FAILED Programmer Response: Modify the application to ensure that the same unit-of-work specification is used for all messages in the group, or all segments of the logical message. 2246 (X'08C6')MQRC_INVALID_MSG_UNDER_CURSOR Explanation: An MQGET call was issued specifying the MQGMO_COMPLETE_MSG option with either MQGMO_MSG_UNDER_CURSOR or MQGMO_BROWSE_MSG_UNDER_CURSOR, but the message that is under the cursor has an MQMD with an Offset field that is greater than zero. Because MQGMO_COMPLETE_MSG was specified, the message is not valid for retrieval. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Reposition the browse cursor so that it is located on a message whose Offset field in MQMD is zero. Alternatively, remove the MQGMO_COMPLETE_MSG option. 2247 (X'08C7')MQRC_MATCH_OPTIONS_ERROR Explanation: An MQGET call was issued, but the value of the MatchOptions field in the GetMsgOpts parameter is not valid, for one of the following reasons: An undefined option is specified. All of the following are true: MQGMO_LOGICAL_ORDER is specified. There is a current message group or logical message for the queue handle. Neither MQGMO_BROWSE_MSG_UNDER_CURSOR nor MQGMO_MSG_UNDER_CURSOR is specified. One or more of the MQMO_* options is specified. The values of the fields in the MsgDesc parameter corresponding to the MQMO_* options specified, differ from the values of those fields in the MQMD for the message to be returned next. On z/OS, one or more of the options specified is not valid for the index type of the queue. This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Ensure that only valid options are specified for the field. 2248 (X'08C8')MQRC_MDE_ERROR Explanation: An MQPUT or MQPUT1 call was issued, but the message data contains an MQMDE structure that is not valid. Possible errors include the following: The StrucId field is not MQMDE_STRUC_ID. The Version field is not MQMDE_VERSION_2. The StrucLength field is not MQMDE_LENGTH_2. The CodedCharSetId field is zero, or a negative value that is not valid. The BufferLength parameter of the call has a value that is too small to accommodate the structure (the structure extends beyond the end of the message). This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Check that the fields in the structure are set correctly. Ensure that the application sets the CodedCharSetId field to a valid value (note: MQCCSI_DEFAULT, MQCCSI_EMBEDDED, MQCCSI_Q_MGR, and MQCCSI_UNDEFINED are not valid in this field). 2249 (X'08C9')MQRC_MSG_FLAGS_ERROR Explanation: An MQPUT or MQPUT1 call was issued, but the MsgFlags field in the message descriptor MQMD contains one or more message flags that are not recognized by the local queue manager. The message flags that cause this reason code to be returned depend on the destination of the message; see the description of REPORT in the WebSphere MQ Application Programming Guide for more details. This reason code can also occur in the Feedback field in the MQMD of a report message, or in the Reason field in the MQDLH structure of a message on the dead-letter queue; in both cases it indicates that the destination queue manager does not support one or more of the message flags specified by the sender of the message. This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Do the following: Ensure that the MsgFlags field in the message descriptor is initialized with a value when the message descriptor is declared, or is assigned a value prior to the MQPUT or MQPUT1 call. Specify MQMF_NONE if no message flags are needed. Ensure that the message flags specified are valid; see the MsgFlags field described in the description of MQMD in the WebSphere MQ Application Programming Guide for valid message flags. If multiple message flags are being set by adding the individual message flags together, ensure that the same message flag is not added twice. On z/OS, ensure that the message flags specified are valid for the index type of the queue; see the description of the MsgFlags field in MQMD for further details. 2250 (X'08CA')MQRC_MSG_SEQ_NUMBER_ERROR Explanation: An MQGET, MQPUT, or MQPUT1 call was issued, but the value of the MsgSeqNumber field in the MQMD or MQMDE structure is less than one or greater than 999 999 999. This error can also occur on the MQPUT call if the MsgSeqNumber field would have become greater than 999 999 999 as a result of the call. This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Specify a value in the range 1 through 999 999 999. Do not attempt to create a message group containing more than 999 999 999 messages. 2251 (X'08CB')MQRC_OFFSET_ERROR Explanation: An MQPUT or MQPUT1 call was issued, but the value of the Offset field in the MQMD or MQMDE structure is less than zero or greater than 999 999 999. This error can also occur on the MQPUT call if the Offset field would have become greater than 999 999 999 as a result of the call. This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Specify a value in the range 0 through 999 999 999. Do not attempt to create a message segment that would extend beyond an offset of 999 999 999. 2252 (X'08CC')MQRC_ORIGINAL_LENGTH_ERROR Explanation: An MQPUT or MQPUT1 call was issued to put a report message that is a segment, but the OriginalLength field in the MQMD or MQMDE structure is either: Less than the length of data in the message, or Less than one (for a segment that is not the last segment), or Less than zero (for a segment that is the last segment) This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Specify a value that is greater than zero. Zero is valid only for the last segment. 2253 (X'08CD')MQRC_SEGMENT_LENGTH_ZERO Explanation: An MQPUT or MQPUT1 call was issued to put the first or an intermediate segment of a logical message, but the length of the application message data in the segment (excluding any MQ headers that may be present) is zero. The length must be at least one for the first or intermediate segment. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Check the application logic to ensure that segments are put with a length of one or greater. Only the last segment of a logical message is permitted to have a length of zero. 2255 (X'08CF')MQRC_UOW_NOT_AVAILABLE Explanation: An MQGET, MQPUT, or MQPUT1 call was issued to get or put a message outside a unit of work, but the options specified on the call required the queue manager to process the call within a unit of work. Because there is already a user-defined unit of work in existence, the queue manager was unable to create a temporary unit of work for the duration of the call. This reason occurs in the following circumstances: On an MQGET call, when the MQGMO_COMPLETE_MSG option is specified in MQGMO and the logical message to be retrieved is persistent and consists of two or more segments. On an MQPUT or MQPUT1 call, when the MQMF_SEGMENTATION_ALLOWED flag is specified in MQMD and the message requires segmentation. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Issue the MQGET, MQPUT, or MQPUT1 call inside the user-defined unit of work. Alternatively, for the MQPUT or MQPUT1 call, reduce the size of the message so that it does not require segmentation by the queue manager. 2256 (X'08D0')MQRC_WRONG_GMO_VERSION Explanation: An MQGET call was issued specifying options that required an MQGMO with a version number not less than MQGMO_VERSION_2, but the MQGMO supplied did not satisfy this condition. This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Modify the application to pass a version-2 MQGMO. Check the application logic to ensure that the Version field in MQGMO has been set to MQGMO_VERSION_2. Alternatively, remove the option that requires the version-2 MQGMO. 2257 (X'08D1')MQRC_WRONG_MD_VERSION Explanation: An MQGET, MQPUT, or MQPUT1 call was issued specifying options that required an MQMD with a version number not less than MQMD_VERSION_2, but the MQMD supplied did not satisfy this condition. This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Modify the application to pass a version-2 MQMD. Check the application logic to ensure that the Version field in MQMD has been set to MQMD_VERSION_2. Alternatively, remove the option that requires the version-2 MQMD. 2258 (X'08D2')MQRC_GROUP_ID_ERROR Explanation: An MQPUT or MQPUT1 call was issued to put a distribution-list message that is also a message in a group, a message segment, or has segmentation allowed, but an invalid combination of options and values was specified. All of the following are true: MQPMO_LOGICAL_ORDER is not specified in the Options field in MQPMO. Either there are too few MQPMR records provided by MQPMO, or the GroupId field is not present in the MQPMR records. One or more of the following flags is specified in the MsgFlags field in MQMD or MQMDE: MQMF_SEGMENTATION_ALLOWED MQMF_*_MSG_IN_GROUP MQMF_*_SEGMENT The GroupId field in MQMD or MQMDE is not MQGI_NONE. This combination of options and values would result in the same group identifier being used for all of the destinations in the distribution list; this is not permitted by the queue manager. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Specify MQGI_NONE for the GroupId field in MQMD or MQMDE. Alternatively, if the call is MQPUT specify MQPMO_LOGICAL_ORDER in the Options field in MQPMO. 2259 (X'08D3')MQRC_INCONSISTENT_BROWSE Explanation: An MQGET call was issued with the MQGMO_BROWSE_NEXT option specified, but the specification of the MQGMO_LOGICAL_ORDER option for the call is different from the specification of that option for the previous call for the queue handle. Either both calls must specify MQGMO_LOGICAL_ORDER, or neither call must specify MQGMO_LOGICAL_ORDER. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Add or remove the MQGMO_LOGICAL_ORDER option as appropriate. Alternatively, to switch between logical order and physical order, specify the MQGMO_BROWSE_FIRST option to restart the scan from the beginning of the queue, omitting or specifying MQGMO_LOGICAL_ORDER as required. 2260 (X'08D4')MQRC_XQH_ERROR Explanation: An MQPUT or MQPUT1 call was issued, but the message data contains an MQXQH structure that is not valid. Possible errors include the following: The StrucId field is not MQXQH_STRUC_ID. The Version field is not MQXQH_VERSION_1. The BufferLength parameter of the call has a value that is too small to accommodate the structure (the structure extends beyond the end of the message). This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Check that the fields in the structure are set correctly. 2261 (X'08D5')MQRC_SRC_ENV_ERROR Explanation: This reason occurs when a channel exit that processes reference messages detects an error in the source environment data of a reference message header (MQRMH). One of the following is true: SrcEnvLength is less than zero. SrcEnvLength is greater than zero, but there is no source environment data. SrcEnvLength is greater than zero, but SrcEnvOffset is negative, zero, or less than the length of the fixed part of MQRMH. SrcEnvLength is greater than zero, but SrcEnvOffset plus SrcEnvLength is greater than StrucLength. The exit returns this reason in the Feedback field of the MQCXP structure. If an exception report is requested, it is copied to the Feedback field of the MQMD associated with the report. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Specify the source environment data correctly. 2262 (X'08D6')MQRC_SRC_NAME_ERROR Explanation: This reason occurs when a channel exit that processes reference messages detects an error in the source name data of a reference message header (MQRMH). One of the following is true: SrcNameLength is less than zero. SrcNameLength is greater than zero, but there is no source name data. SrcNameLength is greater than zero, but SrcNameOffset is negative, zero, or less than the length of the fixed part of MQRMH. SrcNameLength is greater than zero, but SrcNameOffset plus SrcNameLength is greater than StrucLength. The exit returns this reason in the Feedback field of the MQCXP structure. If an exception report is requested, it is copied to the Feedback field of the MQMD associated with the report. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Specify the source name data correctly. 2263 (X'08D7')MQRC_DEST_ENV_ERROR Explanation: This reason occurs when a channel exit that processes reference messages detects an error in the destination environment data of a reference message header (MQRMH). One of the following is true: DestEnvLength is less than zero. DestEnvLength is greater than zero, but there is no destination environment data. DestEnvLength is greater than zero, but DestEnvOffset is negative, zero, or less than the length of the fixed part of MQRMH. DestEnvLength is greater than zero, but DestEnvOffset plus DestEnvLength is greater than StrucLength. The exit returns this reason in the Feedback field of the MQCXP structure. If an exception report is requested, it is copied to the Feedback field of the MQMD associated with the report. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Specify the destination environment data correctly. 2264 (X'08D8')MQRC_DEST_NAME_ERROR Explanation: This reason occurs when a channel exit that processes reference messages detects an error in the destination name data of a reference message header (MQRMH). One of the following is true: DestNameLength is less than zero. DestNameLength is greater than zero, but there is no destination name data. DestNameLength is greater than zero, but DestNameOffset is negative, zero, or less than the length of the fixed part of MQRMH. DestNameLength is greater than zero, but DestNameOffset plus DestNameLength is greater than StrucLength. The exit returns this reason in the Feedback field of the MQCXP structure. If an exception report is requested, it is copied to the Feedback field of the MQMD associated with the report. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Specify the destination name data correctly. 2265 (X'08D9')MQRC_TM_ERROR Explanation: An MQPUT or MQPUT1 call was issued, but the message data contains an MQTM structure that is not valid. Possible errors include the following: The StrucId field is not MQTM_STRUC_ID. The Version field is not MQTM_VERSION_1. The BufferLength parameter of the call has a value that is too small to accommodate the structure (the structure extends beyond the end of the message). This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Check that the fields in the structure are set correctly. 2266 (X'08DA')MQRC_CLUSTER_EXIT_ERROR Explanation: An MQOPEN, MQPUT, or MQPUT1 call was issued to open or put a message on a cluster queue, but the cluster workload exit defined by the queue-manager's ClusterWorkloadExit attribute failed unexpectedly or did not respond in time. Subsequent MQOPEN, MQPUT, and MQPUT1 calls for this queue handle are processed as though the ClusterWorkloadExit attribute were blank. On z/OS, a message giving more information about the error is written to the system log, for example message CSQV455E or CSQV456E. This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Check the cluster workload exit to ensure that it has been written correctly. 2267 (X'08DB')MQRC_CLUSTER_EXIT_LOAD_ERROR Explanation: An MQCONN or MQCONNX call was issued to connect to a queue manager, but the queue manager was unable to load the cluster workload exit. Execution continues without the cluster workload exit. On z/OS, if the cluster workload exit cannot be loaded, a message is written to the system log, for example message CSQV453I. Processing continues as though the ClusterWorkloadExit attribute had been blank. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_WARNING Programmer Response: Ensure that the queue-manager's ClusterWorkloadExit attribute has the correct value, and that the exit has been installed into the correct location. 2268 (X'08DC')MQRC_CLUSTER_PUT_INHIBITED Explanation: An MQOPEN call with the MQOO_OUTPUT and MQOO_BIND_ON_OPEN options in effect was issued for a cluster queue, but the call failed because all of the following are true: All instances of the cluster queue are currently put-inhibited (that is, all of the queue instances have the InhibitPut attribute set to MQQA_PUT_INHIBITED). There is no local instance of the queue. (If there is a local instance, the MQOPEN call succeeds, even if the local instance is put-inhibited.) There is no cluster workload exit for the queue, or there is a cluster workload exit but it did not choose a queue instance. (If the cluster workload exit does choose a queue instance, the MQOPEN call succeeds, even if that instance is put-inhibited.) If the MQOO_BIND_NOT_FIXED option is specified on the MQOPEN call, the call can succeed even if all of the queues in the cluster are put-inhibited. However, a subsequent MQPUT call may fail if all of the queues are still put-inhibited at the time of the MQPUT call. This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: If the system design allows put requests to be inhibited for short periods, retry the operation later. If the problem persists, determine why all of the queues in the cluster are put-inhibited. 2269 (X'08DD')MQRC_CLUSTER_RESOURCE_ERROR Explanation: An MQOPEN, MQPUT, or MQPUT1 call was issued for a cluster queue, but an error occurred whilst trying to use a resource required for clustering. This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Do the following: Check that the SYSTEM.CLUSTER.* queues are not put inhibited or full. Check the event queues for any events relating to the SYSTEM.CLUSTER.* queues, as these may give guidance as to the nature of the failure. Check that the repository queue manager is available. On z/OS, check the console for signs of the failure, such as full page sets. 2270 (X'08DE')MQRC_NO_DESTINATIONS_AVAILABLE Explanation: An MQPUT or MQPUT1 call was issued to put a message on a cluster queue, but at the time of the call there were no longer any instances of the queue in the cluster. The message therefore could not be sent. This situation can occur when MQOO_BIND_NOT_FIXED is specified on the MQOPEN call that opens the queue, or MQPUT1 is used to put the message. This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Check the queue definition and queue status to determine why all instances of the queue were removed from the cluster. Correct the problem and rerun the application. 2271 (X'08DF')MQRC_CONN_TAG_IN_USE Explanation: An MQCONNX call was issued specifying one of the MQCNO_*_CONN_TAG_* options, but the call failed because the connection tag specified by ConnTag in MQCNO is in use by an active process or thread, or there is an unresolved unit of work that references this connection tag. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: The problem is likely to be transitory. The application should wait a short while and then retry the operation. 2272 (X'08E0')MQRC_PARTIALLY_CONVERTED Explanation: On an MQGET call with the MQGMO_CONVERT option included in the GetMsgOpts parameter, one or more MQ header structures in the message data could not be converted to the specified target character set or encoding. In this situation, the MQ header structures are converted to the queue-manager's character set and encoding, and the application data in the message is converted to the target character set and encoding. On return from the call, the values returned in the various CodedCharSetId and Encoding fields in the MsgDesc parameter and MQ header structures indicate the character set and encoding that apply to each part of the message. The call completes with MQCC_WARNING. This reason code usually occurs when the specified target character set is one that causes the character strings in the MQ header structures to expand beyond the lengths of their fields. Unicode character set UCS-2 is an example of a character set that causes this to happen. Completion Code: MQCC_FAILED Programmer Response: If this is an expected situation, no corrective action is required. If this is an unexpected situation, check that the MQ header structures contain valid data. If they do, specify as the target character set a character set that does not cause the strings to expand. 2273 (X'08E1')MQRC_CONNECTION_ERROR Explanation: An MQCONN or MQCONNX call failed for one of the following reasons: The installation and customization options chosen for WebSphere MQ do not allow connection by the type of application being used. The system parameter module is not at the same release level as the queue manager. The channel initiator is not at the same release level as the queue manager. An internal error was detected by the queue manager. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: None, if the installation and customization options chosen for WebSphere MQ do not allow all functions to be used. Otherwise, if this occurs while starting the channel initiator, ensure that the queue manager and the channel initiator are both at the same release level and that their started task JCL procedures both specify the same level of WebSphere MQ program libraries; if this occurs while starting the queue manager, relinkedit the system parameter module (CSQZPARM) to ensure that it is at the correct level. If the problem persists, contact your IBM support center. 2274 (X'08E2')MQRC_OPTION_ENVIRONMENT_ERROR Explanation: An MQGET call with the MQGMO_MARK_SKIP_BACKOUT option specified was issued from a DB2 Stored Procedure. The call failed because the MQGMO_MARK_SKIP_BACKOUT option cannot be used from a DB2 Stored Procedure. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Remove the MQGMO_MARK_SKIP_BACKOUT option from the MQGET call. 2277 (X'08E5')MQRC_CD_ERROR Explanation: An MQCONNX call was issued to connect to a queue manager, but the MQCD channel definition structure addressed by the ClientConnOffset or ClientConnPtr field in MQCNO contains data that is not valid. Consult the error log for more information about the nature of the error. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Ensure that input fields in the MQCD structure are set correctly. 2278 (X'08E6')MQRC_CLIENT_CONN_ERROR Explanation: An MQCONNX call was issued to connect to a queue manager, but the MQCD channel definition structure is not specified correctly. One of the following applies: ClientConnOffset is not zero and ClientConnPtr is not zero and not the null pointer. ClientConnPtr is not a valid pointer. ClientConnPtr or ClientConnOffset points to storage that is not accessible. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. It also occurs in Java applications when a client channel definition table is specified to determine the name of the channel, but the table itself cannot be found. Completion Code: MQCC_FAILED Programmer Response: Ensure that at least one of ClientConnOffset and ClientConnPtr is zero. Ensure that the field used points to accessible storage. Ensure that the URL of the client channel definition table is correct. 2279 (X'08E7')MQRC_CHANNEL_STOPPED_BY_USER Explanation: This condition is detected when the channel has been stopped by an operator. The reason qualifier identifies the reasons for stopping. Completion Code: MQCC_WARNING Programmer Response: None. This reason code is only used to identify the corresponding event message. 2280 (X'08E8')MQRC_HCONFIG_ERROR Explanation: The configuration handle Hconfig specified on the MQXEP call or MQZEP call is not valid. The MQXEP call is issued by an API exit function; the MQZEP call is issued by an installable service. On z/OS, this reason code does not occur. Completion Code: MQCC_FAILED Programmer Response: Specify the configuration handle that was provided by the queue manager: On the MQXEP call, use the handle passed in the Hconfig field of the MQAXP structure. On the MQZEP call, use the handle passed to the installable service's configuration function on the component initialization call. See the WebSphere MQ System Administration Guide book for information about installable services. 2281 (X'08E9')MQRC_FUNCTION_ERROR Explanation: An MQXEP or MQZEP call was issued, but the function identifier Function specified on the call is not valid, or not supported by the installable service being configured. On z/OS, this reason code does not occur. Completion Code: MQCC_FAILED Programmer Response: Do the following: For the MQXEP call, specify one of the MQXF_* values. For the MQZEP call, specify an MQZID_* value that is valid for the installable service being configured. Refer to the description of the MQZEP call in the WebSphere MQ System Administration Guide book to determine which values are valid. 2282 (X'08EA')MQRC_CHANNEL_STARTED Explanation: One of the following has occurred: An operator has issued a Start Channel command. An instance of a channel has been successfully established. This condition is detected when Initial Data negotiation is complete and resynchronization has been performed where necessary such that message transfer can proceed. Completion Code: MQCC_WARNING Programmer Response: None. This reason code is only used to identify the corresponding event message. 2283 (X'08EB')MQRC_CHANNEL_STOPPED Explanation: This condition is detected when the channel has been stopped. The reason qualifier identifies the reasons for stopping. Completion Code: MQCC_WARNING Programmer Response: None. This reason code is only used to identify the corresponding event message. 2284 (X'08EC')MQRC_CHANNEL_CONV_ERROR Explanation: This condition is detected when a channel is unable to do data conversion and the MQGET call to get a message from the transmission queue resulted in a data conversion error. The conversion reason code identifies the reason for the failure. Completion Code: MQCC_WARNING Programmer Response: None. This reason code is only used to identify the corresponding event message. 2285 (X'08ED')MQRC_SERVICE_NOT_AVAILABLE Explanation: This reason should be returned by an installable service component when the requested action cannot be performed because the required underlying service is not available. On z/OS, this reason code does not occur. Completion Code: MQCC_FAILED Programmer Response: Make the underlying service available. 2286 (X'08EE')MQRC_INITIALIZATION_FAILED Explanation: This reason should be returned by an installable service component when the component is unable to complete initialization successfully. On z/OS, this reason code does not occur. Completion Code: MQCC_FAILED Programmer Response: Correct the error and retry the operation. 2287 (X'08EF')MQRC_TERMINATION_FAILED Explanation: This reason should be returned by an installable service component when the component is unable to complete termination successfully. On z/OS, this reason code does not occur. Completion Code: MQCC_FAILED Programmer Response: Correct the error and retry the operation. 2288 (X'08F0')MQRC_UNKNOWN_Q_NAME Explanation: This reason should be returned by the MQZ_LOOKUP_NAME installable service component when the name specified for the QName parameter is not recognized. On z/OS, this reason code does not occur. Completion Code: MQCC_FAILED Programmer Response: None. See the WebSphere MQ System Administration Guide book for information about installable services. 2289 (X'08F1')MQRC_SERVICE_ERROR Explanation: This reason should be returned by an installable service component when the component encounters an unexpected error. On z/OS, this reason code does not occur. Completion Code: MQCC_FAILED Programmer Response: Correct the error and retry the operation. 2290 (X'08F2')MQRC_Q_ALREADY_EXISTS Explanation: This reason should be returned by the MQZ_INSERT_NAME installable service component when the queue specified by the QName parameter is already defined to the name service. On z/OS, this reason code does not occur. Completion Code: MQCC_FAILED Programmer Response: None. See the WebSphere MQ System Administration Guide book for information about installable service. 2291 (X'08F3')MQRC_USER_ID_NOT_AVAILABLE Explanation: This reason should be returned by the MQZ_FIND_USERID installable service component when the user ID cannot be determined. On z/OS, this reason code does not occur. Completion Code: MQCC_FAILED Programmer Response: None. See the WebSphere MQ System Administration Guide book for information about installable services. 2292 (X'08F4')MQRC_UNKNOWN_ENTITY Explanation: This reason should be returned by the authority installable service component when the name specified by the EntityName parameter is not recognized. On z/OS, this reason code does not occur. Completion Code: MQCC_FAILED Programmer Response: Ensure that the entity is defined. 2294 (X'08F6')MQRC_UNKNOWN_REF_OBJECT Explanation: This reason should be returned by the MQZ_COPY_ALL_AUTHORITY installable service component when the name specified by the RefObjectName parameter is not recognized. On z/OS, this reason code does not occur. Completion Code: MQCC_FAILED Programmer Response: Ensure that the reference object is defined. See the WebSphere MQ System Administration Guide book for information about installable services. 2295 (X'08F7')MQRC_CHANNEL_ACTIVATED Explanation: This condition is detected when a channel that has been waiting to become active, and for which a Channel Not Activated event has been generated, is now able to become active because an active slot has been released by another channel. This event is not generated for a channel that is able to become active without waiting for an active slot to be released. Completion Code: MQCC_WARNING Programmer Response: None. This reason code is only used to identify the corresponding event message. 2296 (X'08F8')MQRC_CHANNEL_NOT_ACTIVATED Explanation: This condition is detected when a channel is required to become active, either because it is starting or because it is about to make another attempt to establish connection with its partner. However, it is unable to do so because the limit on the number of active channels has been reached. On z/OS, the maximum number of active channels is given by the ACTCHL queue manager attribute. In other environments, the maximum number of active channels is given by the MaxActiveChannels parameter in the qm.ini file. The channel waits until it is able to take over an active slot released when another channel ceases to be active. At that time a Channel Activated event is generated. Completion Code: MQCC_WARNING Programmer Response: None. This reason code is only used to identify the corresponding event message. 2297 (X'08F9')MQRC_UOW_CANCELED Explanation: An MQI call was issued, but the unit of work (TM/MP transaction) being used for the MQ operation had been canceled. This may have been done by TM/MP itself (for example, due to the transaction running for too long, or exceeding audit trail sizes), or by the application program issuing an ABORT_TRANSACTION. All updates performed to resources owned by the queue manager are backed out. Completion Code: MQCC_FAILED Programmer Response: Refer to the operating system's Transaction Management Operations Guide to determine how the Transaction Manager can be tuned to avoid the problem of system limits being exceeded. 2298 (X'08FA')MQRC_FUNCTION_NOT_SUPPORTED Explanation: The function requested is not available in the current environment. Completion Code: MQCC_FAILED Programmer Response: Remove the call from the application. 2299 (X'08FB')MQRC_SELECTOR_TYPE_ERROR Explanation: The Selector parameter has the wrong data type; it must be of type Long. Completion Code: MQCC_FAILED Programmer Response: Declare the Selector parameter as Long. 2300 (X'08FC')MQRC_COMMAND_TYPE_ERROR Explanation: The mqExecute call was issued, but the value of the MQIASY_TYPE data item in the administration bag is not MQCFT_COMMAND. Completion Code: MQCC_FAILED Programmer Response: Ensure that the MQIASY_TYPE data item in the administration bag has the value MQCFT_COMMAND. 2301 (X'08FD')MQRC_MULTIPLE_INSTANCE_ERROR Explanation: The Selector parameter specifies a system selector (one of the MQIASY_* values), but the value of the ItemIndex parameter is not MQIND_NONE. Only one instance of each system selector can exist in the bag. Completion Code: MQCC_FAILED Programmer Response: Specify MQIND_NONE for the ItemIndex parameter. 2302 (X'08FE')MQRC_SYSTEM_ITEM_NOT_ALTERABLE Explanation: A call was issued to modify the value of a system data item in a bag (a data item with one of the MQIASY_* selectors), but the call failed because the data item is one that cannot be altered by the application. Completion Code: MQCC_FAILED Programmer Response: Specify the selector of a user-defined data item, or remove the call. 2303 (X'08FF')MQRC_BAG_CONVERSION_ERROR Explanation: The mqBufferToBag or mqGetBag call was issued, but the data in the buffer or message could not be converted into a bag. This occurs when the data to be converted is not valid PCF. Completion Code: MQCC_FAILED Programmer Response: Check the logic of the application that created the buffer or message to ensure that the buffer or message contains valid PCF. If the message contains PCF that is not valid, the message cannot be retrieved using the mqGetBag call: If one of the MQGMO_BROWSE_* options was specified, the message remains on the queue and can be retrieved using the MQGET call. In other cases, the message has already been removed from the queue and discarded. If the message was retrieved within a unit of work, the unit of work can be backed out and the message retrieved using the MQGET call. 2304 (X'0900')MQRC_SELECTOR_OUT_OF_RANGE Explanation: The Selector parameter has a value that is outside the valid range for the call. If the bag was created with the MQCBO_CHECK_SELECTORS option: For the mqAddInteger call, the value must be within the range MQIA_FIRST through MQIA_LAST. For the mqAddString call, the value must be within the range MQCA_FIRST through MQCA_LAST. If the bag was not created with the MQCBO_CHECK_SELECTORS option: The value must be zero or greater. Completion Code: MQCC_FAILED Programmer Response: Specify a valid value. 2305 (X'0901')MQRC_SELECTOR_NOT_UNIQUE Explanation: The ItemIndex parameter has the value MQIND_NONE, but the bag contains more than one data item with the selector value specified by the Selector parameter. MQIND_NONE requires that the bag contain only one occurrence of the specified selector. This reason code also occurs on the mqExecute call when the administration bag contains two or more occurrences of a selector for a required parameter that permits only one occurrence. Completion Code: MQCC_FAILED Programmer Response: Check the logic of the application that created the bag. If correct, specify for ItemIndex a value that is zero or greater, and add application logic to process all of the occurrences of the selector in the bag. Review the description of the administration command being issued, and ensure that all required parameters are defined correctly in the bag. 2306 (X'0902')MQRC_INDEX_NOT_PRESENT Explanation: The specified index is not present: For a bag, this means that the bag contains one or more data items that have the selector value specified by the Selector parameter, but none of them has the index value specified by the ItemIndex parameter. The data item identified by the Selector and ItemIndex parameters must exist in the bag. For a namelist, this means that the index parameter value is too large, and outside the range of valid values. Completion Code: MQCC_FAILED Programmer Response: Specify the index of a data item that does exist in the bag or namelist. Use the mqCountItems call to determine the number of data items with the specified selector that exist in the bag, or the nameCount method to determine the number of names in the namelist. 2307 (X'0903')MQRC_STRING_ERROR Explanation: The String parameter is not valid. Either the parameter pointer is not valid, or it points to read-only storage. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) Completion Code: MQCC_FAILED Programmer Response: Correct the parameter. 2308 (X'0904')MQRC_ENCODING_NOT_SUPPORTED Explanation: The Encoding field in the message descriptor MQMD contains a value that is not supported: For the mqPutBag call, the field in error resides in the MsgDesc parameter of the call. For the mqGetBag call, the field in error resides in: The MsgDesc parameter of the call if the MQGMO_CONVERT option was specified. The message descriptor of the message about to be retrieved if MQGMO_CONVERT was not specified. Completion Code: MQCC_FAILED Programmer Response: The value must be MQENC_NATIVE. If the value of the Encoding field in the message is not valid, the message cannot be retrieved using the mqGetBag call: If one of the MQGMO_BROWSE_* options was specified, the message remains on the queue and can be retrieved using the MQGET call. In other cases, the message has already been removed from the queue and discarded. If the message was retrieved within a unit of work, the unit of work can be backed out and the message retrieved using the MQGET call. 2309 (X'0905')MQRC_SELECTOR_NOT_PRESENT Explanation: The Selector parameter specifies a selector that does not exist in the bag. Completion Code: MQCC_FAILED Programmer Response: Specify a selector that does exist in the bag. 2310 (X'0906')MQRC_OUT_SELECTOR_ERROR Explanation: The OutSelector parameter is not valid. Either the parameter pointer is not valid, or it points to read-only storage. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) Completion Code: MQCC_FAILED Programmer Response: Correct the parameter. 2311 (X'0907')MQRC_STRING_TRUNCATED Explanation: The string returned by the call is too long to fit in the buffer provided. The string has been truncated to fit in the buffer. Completion Code: MQCC_FAILED Programmer Response: If the entire string is required, provide a larger buffer. On the mqInquireString call, the StringLength parameter is set by the call to indicate the size of the buffer required to accommodate the string without truncation. 2312 (X'0908')MQRC_SELECTOR_WRONG_TYPE Explanation: A data item with the specified selector exists in the bag, but has a data type that conflicts with the data type implied by the call being used. For example, the data item might have an integer data type, but the call being used might be mqSetString, which implies a character data type. This reason code also occurs on the mqBagToBuffer, mqExecute, and mqPutBag calls when mqAddString or mqSetString was used to add the MQIACF_INQUIRY data item to the bag. Completion Code: MQCC_FAILED Programmer Response: For the mqSetInteger and mqSetString calls, specify MQIND_ALL for the ItemIndex parameter to delete from the bag all existing occurrences of the specified selector before creating the new occurrence with the required data type. For the mqInquireBag, mqInquireInteger, and mqInquireString calls, use the mqInquireItemInfo call to determine the data type of the item with the specified selector, and then use the appropriate call to determine the value of the data item. For the mqBagToBuffer, mqExecute, and mqPutBag calls, ensure that the MQIACF_INQUIRY data item is added to the bag using the mqAddInteger or mqSetInteger calls. 2313 (X'0909')MQRC_INCONSISTENT_ITEM_TYPE Explanation: The mqAddInteger or mqAddString call was issued to add another occurrence of the specified selector to the bag, but the data type of this occurrence differed from the data type of the first occurrence. This reason can also occur on the mqBufferToBag and mqGetBag calls, where it indicates that the PCF in the buffer or message contains a selector that occurs more than once but with inconsistent data types. Completion Code: MQCC_FAILED Programmer Response: For the mqAddInteger and mqAddString calls, use the call appropriate to the data type of the first occurrence of that selector in the bag. For the mqBufferToBag and mqGetBag calls, check the logic of the application that created the buffer or sent the message to ensure that multiple-occurrence selectors occur with only one data type. A message that contains a mixture of data types for a selector cannot be retrieved using the mqGetBag call: If one of the MQGMO_BROWSE_* options was specified, the message remains on the queue and can be retrieved using the MQGET call. In other cases, the message has already been removed from the queue and discarded. If the message was retrieved within a unit of work, the unit of work can be backed out and the message retrieved using the MQGET call. 2314 (X'090A')MQRC_INDEX_ERROR Explanation: An index parameter to a call or method has a value that is not valid. The value must be zero or greater. For bag calls, certain MQIND_* values can also be specified: For the mqDeleteItem, mqSetInteger and mqSetString calls, MQIND_ALL and MQIND_NONE are valid. For the mqInquireBag, mqInquireInteger, mqInquireString, and mqInquireItemInfo calls, MQIND_NONE is valid. Completion Code: MQCC_FAILED Programmer Response: Specify a valid value. 2315 (X'090B')MQRC_SYSTEM_BAG_NOT_ALTERABLE Explanation: A call was issued to add a data item to a bag, modify the value of an existing data item in a bag, or retrieve a message into a bag, but the call failed because the bag is one that had been created by the system as a result of a previous mqExecute call. System bags cannot be modified by the application. Completion Code: MQCC_FAILED Programmer Response: Specify the handle of a bag created by the application, or remove the call. 2316 (X'090C')MQRC_ITEM_COUNT_ERROR Explanation: The mqTruncateBag call was issued, but the ItemCount parameter specifies a value that is not valid. The value is either less than zero, or greater than the number of user-defined data items in the bag. This reason also occurs on the mqCountItems call if the parameter pointer is not valid, or points to read-only storage. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) Completion Code: MQCC_FAILED Programmer Response: Specify a valid value. Use the mqCountItems call to determine the number of user-defined data items in the bag. 2317 (X'090D')MQRC_FORMAT_NOT_SUPPORTED Explanation: The Format field in the message descriptor MQMD contains a value that is not supported: In an administration message, the format value must be one of the following: MQFMT_ADMIN, MQFMT_EVENT, MQFMT_PCF. For the mqPutBag call, the field in error resides in the MsgDesc parameter of the call. For the mqGetBag call, the field in error resides in the message descriptor of the message about to be retrieved. On z/OS, the message was put to the command input queue with a format value of MQFMT_ADMIN, but the version of MQ being used does not support that format for commands. Completion Code: MQCC_FAILED Programmer Response: If the error occurred when putting a message, correct the format value. If the error occurred when getting a message, the message cannot be retrieved using the mqGetBag call: If one of the MQGMO_BROWSE_* options was specified, the message remains on the queue and can be retrieved using the MQGET call. In other cases, the message has already been removed from the queue and discarded. If the message was retrieved within a unit of work, the unit of work can be backed out and the message retrieved using the MQGET call. 2318 (X'090E')MQRC_SELECTOR_NOT_SUPPORTED Explanation: The Selector parameter specifies a value that is a system selector (a value that is negative), but the system selector is not one that is supported by the call. Completion Code: MQCC_FAILED Programmer Response: Specify a selector value that is supported. 2319 (X'090F')MQRC_ITEM_VALUE_ERROR Explanation: The mqInquireBag or mqInquireInteger call was issued, but the ItemValue parameter is not valid. Either the parameter pointer is not valid, or it points to read-only storage. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) Completion Code: MQCC_FAILED Programmer Response: Correct the parameter. 2320 (X'0910')MQRC_HBAG_ERROR Explanation: A call was issued that has a parameter that is a bag handle, but the handle is not valid. For output parameters, this reason also occurs if the parameter pointer is not valid, or points to read-only storage. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) Completion Code: MQCC_FAILED Programmer Response: Correct the parameter. 2321 (X'0911')MQRC_PARAMETER_MISSING Explanation: An administration message requires a parameter that is not present in the administration bag. This reason code occurs only for bags created with the MQCBO_ADMIN_BAG or MQCBO_REORDER_AS_REQUIRED options. Completion Code: MQCC_FAILED Programmer Response: Review the description of the administration command being issued, and ensure that all required parameters are present in the bag. 2322 (X'0912')MQRC_CMD_SERVER_NOT_AVAILABLE Explanation: The command server that processes administration commands is not available. Completion Code: MQCC_FAILED Programmer Response: Start the command server. 2323 (X'0913')MQRC_STRING_LENGTH_ERROR Explanation: The StringLength parameter is not valid. Either the parameter pointer is not valid, or it points to read-only storage. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) Completion Code: MQCC_FAILED Programmer Response: Correct the parameter. 2324 (X'0914')MQRC_INQUIRY_COMMAND_ERROR Explanation: The mqAddInquiry call was used previously to add attribute selectors to the bag, but the command code to be used for the mqBagToBuffer, mqExecute, or mqPutBag call is not recognized. As a result, the correct PCF message cannot be generated. Completion Code: MQCC_FAILED Programmer Response: Remove the mqAddInquiry calls and use instead the mqAddInteger call with the appropriate MQIACF_*_ATTRS or MQIACH_*_ATTRS selectors. 2325 (X'0915')MQRC_NESTED_BAG_NOT_SUPPORTED Explanation: A bag that is input to the call contains nested bags. Nested bags are supported only for bags that are output from the call. Completion Code: MQCC_FAILED Programmer Response: Use a different bag as input to the call. 2326 (X'0916')MQRC_BAG_WRONG_TYPE Explanation: The Bag parameter specifies the handle of a bag that has the wrong type for the call. The bag must be an administration bag, that is, it must be created with the MQCBO_ADMIN_BAG option specified on the mqCreateBag call. Completion Code: MQCC_FAILED Programmer Response: Specify the MQCBO_ADMIN_BAG option when the bag is created. 2327 (X'0917')MQRC_ITEM_TYPE_ERROR Explanation: The mqInquireItemInfo call was issued, but the ItemType parameter is not valid. Either the parameter pointer is not valid, or it points to read-only storage. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) Completion Code: MQCC_FAILED Programmer Response: Correct the parameter. 2328 (X'0918')MQRC_SYSTEM_BAG_NOT_DELETABLE Explanation: An mqDeleteBag call was issued to delete a bag, but the call failed because the bag is one that had been created by the system as a result of a previous mqExecute call. System bags cannot be deleted by the application. Completion Code: MQCC_FAILED Programmer Response: Specify the handle of a bag created by the application, or remove the call. 2329 (X'0919')MQRC_SYSTEM_ITEM_NOT_DELETABLE Explanation: A call was issued to delete a system data item from a bag (a data item with one of the MQIASY_* selectors), but the call failed because the data item is one that cannot be deleted by the application. Completion Code: MQCC_FAILED Programmer Response: Specify the selector of a user-defined data item, or remove the call. 2330 (X'091A')MQRC_CODED_CHAR_SET_ID_ERROR Explanation: The CodedCharSetId parameter is not valid. Either the parameter pointer is not valid, or it points to read-only storage. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) Completion Code: MQCC_FAILED Programmer Response: Correct the parameter. 2331 (X'091B')MQRC_MSG_TOKEN_ERROR Explanation: An MQGET call was issued to retrieve a message using the message token as a selection criterion, but the options specified are not valid, because MQMO_MATCH_MSG_TOKEN was specified with either MQGMO_WAIT or MQGMO_SET_SIGNAL. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Remove the MQMO_MATCH_MSG_TOKEN option from the MQGET call. 2332 (X'091C')MQRC_MISSING_WIH Explanation: An MQPUT or MQPUT1 call was issued to put a message on a queue whose IndexType attribute had the value MQIT_MSG_TOKEN, but the Format field in the MQMD was not MQFMT_WORK_INFO_HEADER. This error occurs only when the message arrives at the destination queue manager. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Modify the application to ensure that it places an MQWIH structure at the start of the message data, and sets the Format field in the MQMD to MQFMT_WORK_INFO_HEADER. Alternatively, change the ApplType attribute of the process definition used by the destination queue to be MQAT_WLM, and specify the required service name and service step name in its EnvData attribute. 2333 (X'091D')MQRC_WIH_ERROR Explanation: An MQPUT or MQPUT1 call was issued, but the message data contains an MQWIH structure that is not valid. Possible errors include the following: The StrucId field is not MQWIH_STRUC_ID. The Version field is not MQWIH_VERSION_1. The StrucLength field is not MQWIH_LENGTH_1. The CodedCharSetId field is zero, or a negative value that is not valid. The BufferLength parameter of the call has a value that is too small to accommodate the structure (the structure extends beyond the end of the message). On z/OS, this error also occurs when the IndexType attribute of the queue is MQIT_MSG_TOKEN, but the message data does not begin with an MQWIH structure. Completion Code: MQCC_FAILED Programmer Response: Check that the fields in the structure are set correctly. Ensure that the application sets the CodedCharSetId field to a valid value (note: MQCCSI_DEFAULT, MQCCSI_EMBEDDED, MQCCSI_Q_MGR, and MQCCSI_UNDEFINED are not valid in this field). On z/OS, if the queue has an IndexType of MQIT_MSG_TOKEN, ensure that the message data begins with an MQWIH structure. 2334 (X'091E')MQRC_RFH_ERROR Explanation: An MQPUT or MQPUT1 call was issued, but the message data contains an MQRFH or MQRFH2 structure that is not valid. Possible errors include the following: The StrucId field is not MQRFH_STRUC_ID. The Version field is not MQRFH_VERSION_1 (MQRFH), or MQRFH_VERSION_2 (MQRFH2). The StrucLength field specifies a value that is too small to include the structure plus the variable-length data at the end of the structure. The CodedCharSetId field is zero, or a negative value that is not valid. The BufferLength parameter of the call has a value that is too small to accommodate the structure (the structure extends beyond the end of the message). Completion Code: MQCC_FAILED Programmer Response: Check that the fields in the structure are set correctly. Ensure that the application sets the CodedCharSetId field to a valid value (note: MQCCSI_DEFAULT, MQCCSI_EMBEDDED, MQCCSI_Q_MGR, and MQCCSI_UNDEFINED are not valid in this field). 2335 (X'091F')MQRC_RFH_STRING_ERROR Explanation: The contents of the NameValueString field in the MQRFH structure are not valid. NameValueString must adhere to the following rules: The string must consist of zero or more name/value pairs separated from each other by one or more blanks; the blanks are not significant. If a name or value contains blanks that are significant, the name or value must be enclosed in double-quote characters. If a name or value itself contains one or more double-quote characters, the name or value must be enclosed in double-quote characters, and each embedded double-quote character must be doubled. A name or value can contain any characters other than the null, which acts as a delimiter. The null and characters following it, up to the defined length of NameValueString, are ignored. The following is a valid NameValueString: Famous_Words "The program displayed ""Hello World"""Completion Code: MQCC_FAILED Programmer Response: Modify the application that generated the message to ensure that it places in the NameValueString field data that adheres to the rules listed above. Check that the StrucLength field is set to the correct value. 2336 (X'0920')MQRC_RFH_COMMAND_ERROR Explanation: The message contains an MQRFH structure, but the command name contained in the NameValueString field is not valid. Completion Code: MQCC_FAILED Programmer Response: Modify the application that generated the message to ensure that it places in the NameValueString field a command name that is valid. 2337 (X'0921')MQRC_RFH_PARM_ERROR Explanation: The message contains an MQRFH structure, but a parameter name contained in the NameValueString field is not valid for the command specified. Completion Code: MQCC_FAILED Programmer Response: Modify the application that generated the message to ensure that it places in the NameValueString field only parameters that are valid for the specified command. 2338 (X'0922')MQRC_RFH_DUPLICATE_PARM Explanation: The message contains an MQRFH structure, but a parameter occurs more than once in the NameValueString field when only one occurrence is valid for the specified command. Completion Code: MQCC_FAILED Programmer Response: Modify the application that generated the message to ensure that it places in the NameValueString field only one occurrence of the parameter. 2339 (X'0923')MQRC_RFH_PARM_MISSING Explanation: The message contains an MQRFH structure, but the command specified in the NameValueString field requires a parameter that is not present. Completion Code: MQCC_FAILED Programmer Response: Modify the application that generated the message to ensure that it places in the NameValueString field all parameters that are required for the specified command. 2340 (X'0924')MQRC_CHAR_CONVERSION_ERROR Explanation: This reason code is returned by the Java MQQueueManager constructor when a required character-set conversion is not available. The conversion required is between two nonUnicode character sets. This reason code occurs in the following environment: MQ Classes for Java on z/OS. Completion Code: MQCC_FAILED Programmer Response: Ensure that the National Language Resources component of the OS/390 Language Environment is installed, and that conversion between the IBM-1047 and ISO8859-1 character sets is available. 2341 (X'0925')MQRC_UCS2_CONVERSION_ERROR Explanation: This reason code is returned by the Java MQQueueManager constructor when a required character-set conversion is not available. The conversion required is between the UCS-2 Unicode character set and the queue-manager's character set. IBM-500 is used for the queue-manager's character set if no specific value is available. This reason code occurs in the following environment: MQ Classes for Java on z/OS. Completion Code: MQCC_FAILED Programmer Response: Ensure that the relevant Unicode conversion tables are installed, and that they are available to the z/OS Language Environment. The conversion tables should be installed as part of the z/OS C/C++ optional feature. Refer to the z/OS C/C++ Programming Guide for more information about enabling UCS-2 conversions. 2342 (X'0926')MQRC_DB2_NOT_AVAILABLE Explanation: An MQOPEN, MQPUT1, or MQSET call, or a command, was issued to access a shared queue, but it failed because the queue manager is not connected to a DB2 subsystem. As a result, the queue manager is unable to access the object definition relating to the shared queue. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Configure the DB2 subsystem so that the queue manager can connect to it. 2343 (X'0927')MQRC_OBJECT_NOT_UNIQUE Explanation: An MQOPEN or MQPUT1 call, or a command, was issued to access a queue, but the call failed because the queue specified cannot be resolved unambiguously. There exists a shared queue with the specified name, and a nonshared queue with the same name. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: One of the queues must be deleted. If the queue to be deleted contains messages, use the MQSC command MOVE QLOCAL to move the messages to a different queue, and then use the command DELETE QLOCAL to delete the queue. 2344 (X'0928')MQRC_CONN_TAG_NOT_RELEASED Explanation: An MQDISC call was issued when there was a unit of work outstanding for the connection handle. For CICS, IMS, and RRS connections, the MQDISC call does not commit or back out the unit of work. As a result, the connection tag associated with the unit of work is not yet available for reuse. The tag becomes available for reuse only when processing of the unit of work has been completed. This reason code occurs only on z/OS. Completion Code: MQCC_WARNING Programmer Response: Do not try to reuse the connection tag immediately. If the MQCONNX call is issued with the same connection tag, and that tag is still in use, the call fails with reason code MQRC_CONN_TAG_IN_USE. 2345 (X'0929')MQRC_CF_NOT_AVAILABLE Explanation: An MQOPEN or MQPUT1 call was issued to access a shared queue, but the allocation of the coupling-facility structure specified in the queue definition failed because there is no suitable coupling facility to hold the structure, based on the preference list in the active CFRM policy. This reason code can also occur when the API call requires a capability that is not supported by the CF level defined in the coupling-facility structure object. For example, this reason code is returned by an attempt to open a shared queue that has a index type of MQIT_GROUP_ID, but the coupling-facility structure for the queue has a CF level lower than three. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Make available a coupling facility with one of the names specified in the CFRM policy, or modify the CFRM policy to specify the names of coupling facilities that are available. 2346 (X'092A')MQRC_CF_STRUC_IN_USE Explanation: An MQI call or command was issued to operate on a shared queue, but the call failed because the coupling-facility structure specified in the queue definition is temporarily unavailable. The coupling-facility structure can be unavailable because a structure dump is in progress, or new connectors to the structure are currently inhibited, or an existing connector to the structure failed or disconnected abnormally and clean-up is not yet complete. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: The problem is temporary; wait a short while and then retry the operation. 2347 (X'092B')MQRC_CF_STRUC_LIST_HDR_IN_USE Explanation: An MQGET, MQOPEN, MQPUT1, or MQSET call was issued to access a shared queue, but the call failed because the list header associated with the coupling-facility structure specified in the queue definition is temporarily unavailable. The list header is unavailable because it is undergoing recovery processing. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: The problem is temporary; wait a short while and then retry the operation. 2348 (X'092C')MQRC_CF_STRUC_AUTH_FAILED Explanation: An MQOPEN or MQPUT1 call was issued to access a shared queue, but the call failed because the user is not authorized to access the coupling-facility structure specified in the queue definition. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Modify the security profile for the user identifier used by the application so that the application can access the coupling-facility structure specified in the queue definition. 2349 (X'092D')MQRC_CF_STRUC_ERROR Explanation: An MQOPEN or MQPUT1 call was issued to access a shared queue, but the call failed because the coupling-facility structure name specified in the queue definition is not defined in the CFRM data set, or is not the name of a list structure. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Modify the queue definition to specify the name of a coupling-facility list structure that is defined in the CFRM data set. 2350 (X'092E')MQRC_CONN_TAG_NOT_USABLE Explanation: An MQCONNX call was issued specifying one of the MQCNO_*_CONN_TAG_* options, but the call failed because the connection tag specified by ConnTag in MQCNO is being used by the queue manager for recovery processing, and this processing is delayed pending recovery of the coupling facility. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: The problem is likely to persist. Consult the system programmer to ascertain the cause of the problem. 2351 (X'092F')MQRC_GLOBAL_UOW_CONFLICT Explanation: An attempt was made to use inside a global unit of work a connection handle that is participating in another global unit of work. This can occur when an application passes connection handles between objects where the objects are involved in different DTC transactions. Because transaction completion is asynchronous, it is possible for this error to occur after the application has finalized the first object and committed its transaction. This error does not occur for nontransactional MQI calls. This reason code occurs only on Windows and z/OS. Completion Code: MQCC_FAILED Programmer Response: Check that the "MTS Transaction Support" attribute defined for the object's class is set correctly. If necessary, modify the application so that the connection handle is not used by objects participating in different units of work. 2352 (X'0930')MQRC_LOCAL_UOW_CONFLICT Explanation: An attempt was made to use inside a global unit of work a connection handle that is participating in a queue-manager coordinated local unit of work. This can occur when an application passes connection handles between objects where one object is involved in a DTC transaction and the other is not. This error does not occur for nontransactional MQI calls. This reason code occurs only on Windows and z/OS. Completion Code: MQCC_FAILED Programmer Response: Check that the "MTS Transaction Support" attribute defined for the object's class is set correctly. If necessary, modify the application so that the connection handle is not used by objects participating in different units of work. 2353 (X'0931')MQRC_HANDLE_IN_USE_FOR_UOW Explanation: An attempt was made to use outside a unit of work a connection handle that is participating in a global unit of work. This error can occur when an application passes connection handles between objects where one object is involved in a DTC transaction and the other is not. Because transaction completion is asynchronous, it is possible for this error to occur after the application has finalized the first object and committed its transaction. This error can also occur when a single object that was created and associated with the transaction loses that association whilst the object is running. The association is lost when DTC terminates the transaction independently of MTS. This might be because the transaction timed out, or because DTC shut down. This error does not occur for nontransactional MQI calls. This reason code occurs only on Windows. Completion Code: MQCC_FAILED Programmer Response: Check that the "MTS Transaction Support" attribute defined for the object's class is set correctly. If necessary, modify the application so that objects executing within different units of work do not try to use the same connection handle. 2354 (X'0932')MQRC_UOW_ENLISTMENT_ERROR Explanation: This reason code can occur for a variety of reasons. The most likely reason is that an object created by a DTC transaction does not issue a transactional MQI call until after the DTC transaction has timed out. (If the DTC transaction times out after a transactional MQI call has been issued, reason code MQRC_HANDLE_IN_USE_FOR_UOW is returned by the failing MQI call.) Another cause of MQRC_UOW_ENLISTMENT_ERROR is incorrect installation; Windows NT Service pack must be installed after the Windows NT Option pack. This reason code occurs only on Windows. Completion Code: MQCC_FAILED Programmer Response: Check the DTC "Transaction timeout" value. If necessary, verify the NT installation order. 2355 (X'0933')MQRC_UOW_MIX_NOT_SUPPORTED Explanation: The mixture of calls used by the application to perform operations within a unit of work is not supported. In particular, it is not possible to mix within the same process a local unit of work coordinated by the queue manager with a global unit of work coordinated by DTC (Distributed Transaction Coordinator). An application may cause this mixture to arise if some objects in a package are coordinated by DTC and others are not. It can also occur if transactional MQI calls from an MTS client are mixed with transactional MQI calls from a library package transactional MTS object. No problem arises if all transactional MQI calls originate from transactional MTS objects, or all transactional MQI calls originate from nontransactional MTS objects. But when a mixture of styles is used, the first style used fixes the style for the unit of work, and subsequent attempts to use the other style within the process fail with reason code MQRC_UOW_MIX_NOT_SUPPORTED. When an application is run twice, scheduling factors in the operating system mean that it is possible for the queue-manager-coordinated transactional calls to fail in one run, and for the DTC-coordinated transactional calls to fail in the other run. This reason code occurs only on Windows when running a version of the queue manager prior to version 5.2. Completion Code: MQCC_FAILED Programmer Response: Check that the "MTS Transaction Support" attribute defined for the object's class is set correctly. If necessary, modify the application so that objects executing within different units of work do not try to use the same connection handle. 2356 (X'0934')MQRC_WXP_ERROR Explanation: An MQXCLWLN call was issued from a cluster workload exit to obtain the address of the next record in the chain, but the workload exit parameter structure ExitParms is not valid, for one of the following reasons: The parameter pointer is not valid. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) The StrucId field is not MQWXP_STRUC_ID. The Version field is not MQWXP_VERSION_2. The CacheContext field does not contain the value passed to the exit by the queue manager. Completion Code: MQCC_FAILED Programmer Response: Ensure that the parameter specified for ExitParms is the MQWXP structure that was passed to the exit when the exit was invoked. 2357 (X'0935')MQRC_CURRENT_RECORD_ERROR Explanation: An MQXCLWLN call was issued from a cluster workload exit to obtain the address of the next record in the chain, but the address specified by the CurrentRecord parameter is not the address of a valid record. CurrentRecord must be the address of a destination record (MQWDR), queue record (MQWQR), or cluster record (MQWCR) residing within the cluster cache. Completion Code: MQCC_FAILED Programmer Response: Ensure that the cluster workload exit passes the address of a valid record residing in the cluster cache. 2358 (X'0936')MQRC_NEXT_OFFSET_ERROR Explanation: An MQXCLWLN call was issued from a cluster workload exit to obtain the address of the next record in the chain, but the offset specified by the NextOffset parameter is not valid. NextOffset must be the value of one of the following fields: ChannelDefOffset field in MQWDR ClusterRecOffset field in MQWDR ClusterRecOffset field in MQWQR ClusterRecOffset field in MQWCR Completion Code: MQCC_FAILED Programmer Response: Ensure that the value specified for the NextOffset parameter is the value of one of the fields listed above. 2359 (X'0937')MQRC_NO_RECORD_AVAILABLE Explanation: An MQXCLWLN call was issued from a cluster workload exit to obtain the address of the next record in the chain, but the current record is the last record in the chain. Completion Code: MQCC_FAILED Programmer Response: None. 2360 (X'0938')MQRC_OBJECT_LEVEL_INCOMPATIBLE Explanation: An MQOPEN or MQPUT1 call, or a command, was issued, but the definition of the object to be accessed is not compatible with the queue manager to which the application has connected. The object definition was created or modified by a different version of the queue manager. If the object to be accessed is a queue, the incompatible object definition could be the object specified, or one of the object definitions used to resolve the specified object (for example, the base queue to which an alias queue resolves, or the transmission queue to which a remote queue or queue-manager alias resolves). This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: The application must be run on a queue manager that is compatible with the object definition. Refer to the WebSphere MQ for z/OS Concepts and Planning Guide and the WebSphere MQ for z/OS System Setup Guide for information about compatibility and migration between different versions of the queue manager. 2361 (X'0939')MQRC_NEXT_RECORD_ERROR Explanation: An MQXCLWLN call was issued from a cluster workload exit to obtain the address of the next record in the chain, but the address specified for the NextRecord parameter is either null, not valid, or the address of read-only storage. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) Completion Code: MQCC_FAILED Programmer Response: Specify a valid address for the NextRecord parameter. 2362 (X'093A')MQRC_BACKOUT_THRESHOLD_REACHED Explanation: This reason code occurs only in the Reason field in an MQDLH structure, or in the Feedback field in the MQMD of a report message. A JMS ConnectionConsumer found a message that exceeds the queue's backout threshold. The queue does not have a backout requeue queue defined, so the message was processed as specified by the disposition options in the Report field in the MQMD of the message. On queue managers that do not support the BackoutThreshold and BackoutRequeueQName queue attributes, JMS ConnectionConsumer uses a value of 20 for the backout threshold. When the BackoutCount of a message reaches this threshold, the message is processed as specified by the disposition options. If the Report field specifies one of the MQRO_EXCEPTION_* options, this reason code appears in the Feedback field of the report message. If the Report field specifies MQRO_DEAD_LETTER_Q, or the disposition report options are left as default, this reason code appears in the Reason field of the MQDLH. Completion Code: None Programmer Response: Investigate the cause of the backout count being greater than the threshold. To correct this, define the backout queue for the queue concerned. 2363 (X'093B')MQRC_MSG_NOT_MATCHED Explanation: This reason code occurs only in the Reason field in an MQDLH structure, or in the Feedback field in the MQMD of a report message. While performing Point-to-Point messaging, JMS encountered a message matching none of the selectors of ConnectionConsumers monitoring the queue. To maintain performance, the message was processed as specified by the disposition options in the Report field in the MQMD of the message. If the Report field specifies one of the MQRO_EXCEPTION_* options, this reason code appears in the Feedback field of the report message. If the Report field specifies MQRO_DEAD_LETTER_Q, or the disposition report options are left as default, this reason code appears in the Reason field of the MQDLH. Completion Code: None Programmer Response: To correct this, ensure that the ConnectionConsumers monitoring the queue provide a complete set of selectors. Alternatively, set the QueueConnectionFactory to retain messages. 2364 (X'093C')MQRC_JMS_FORMAT_ERROR Explanation: This reason code is generated when JMS encounters a message that it is unable to parse. If such a message is encountered by a JMS ConnectionConsumer, the message is processed as specified by the disposition options in the Report field in the MQMD of the message. If the Report field specifies one of the MQRO_EXCEPTION_* options, this reason code appears in the Feedback field of the report message. If the Report field specifies MQRO_DEAD_LETTER_Q, or the disposition report options are left as default, this reason code appears in the Reason field of the MQDLH. Completion Code: None Programmer Response: Investigate the origin of the message. 2365 (X'093D')MQRC_SEGMENTS_NOT_SUPPORTED Explanation: An MQPUT call was issued to put a segment of a logical message, but the queue on which the message is to be placed has an IndexType of MQIT_GROUP_ID. Message segments cannot be placed on queues with this index type. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Modify the application to put messages that are not segments; ensure that the MQMF_SEGMENT and MQMF_LAST_SEGMENT flags in the MsgFlags field in MQMD are not set, and that the Offset is zero. Alternatively, change the index type of the queue. 2366 (X'093E')MQRC_WRONG_CF_LEVEL Explanation: An MQOPEN or MQPUT1 call was issued specifying a shared queue, but the queue requires a coupling-facility structure with a different level of capability. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Ensure that the coupling-facility structure used for the queue is at the level required to support the capabilities that the queue provides. 2367 (X'093F')MQRC_CONFIG_CREATE_OBJECT Explanation: This condition is detected when an object is created. Completion Code: MQCC_WARNING Programmer Response: None. This reason code is only used to identify the corresponding event message. 2368 (X'0940')MQRC_CONFIG_CHANGE_OBJECT Explanation: This condition is detected when an object is changed. Completion Code: MQCC_WARNING Programmer Response: None. This reason code is only used to identify the corresponding event message. 2369 (X'0941')MQRC_CONFIG_DELETE_OBJECT Explanation: This condition is detected when an object is deleted. Completion Code: MQCC_WARNING Programmer Response: None. This reason code is only used to identify the corresponding event message. 2370 (X'0942')MQRC_CONFIG_REFRESH_OBJECT Explanation: This condition is detected when an object is refreshed. Completion Code: MQCC_WARNING Programmer Response: None. This reason code is only used to identify the corresponding event message. 2371 (X'0943')MQRC_CHANNEL_SSL_ERROR Explanation: This condition is detected when a connection cannot be established due to an SSL key-exchange or authentication failure. Completion Code: MQCC_WARNING Programmer Response: None. This reason code is only used to identify the corresponding event message. 2373 (X'0945')MQRC_CF_STRUC_FAILED Explanation: An MQI call or command was issued to access a shared queue, but the call failed because the coupling-facility structure used for the shared queue had failed. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Report the problem to the operator or administrator, who should use the MQSC command RECOVER CFSTRUCT to initiate recovery of the coupling-facility structure 2374 (X'0946')MQRC_API_EXIT_ERROR Explanation: An API exit function returned an invalid response code, or failed in some other way. This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows. Completion Code: MQCC_FAILED Programmer Response: Check the exit logic to ensure that the exit is returning valid values in the ExitResponse and ExitResponse2 fields of the MQAXP structure. Consult the FFST record to see if it contains more detail about the problem. 2375 (X'0947')MQRC_API_EXIT_INIT_ERROR Explanation: The queue manager encountered an error while attempting to initialize the execution environment for an API exit function. This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows. Completion Code: MQCC_FAILED Programmer Response: Consult the FFST record to obtain more detail about the problem. 2376 (X'0948')MQRC_API_EXIT_TERM_ERROR Explanation: The queue manager encountered an error while attempting to terminate the execution environment for an API exit function. This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows. Completion Code: MQCC_FAILED Programmer Response: Consult the FFST record to obtain more detail about the problem. 2377 (X'0949')MQRC_EXIT_REASON_ERROR Explanation: An MQXEP call was issued by an API exit function, but the value specified for the ExitReason parameter is either not valid, or not supported for the specified function identifier Function. This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows. Completion Code: MQCC_FAILED Programmer Response: Modify the exit function to specify a value for ExitReason that is valid for the specified value of Function. 2378 (X'094A')MQRC_RESERVED_VALUE_ERROR Explanation: An MQXEP call was issued by an API exit function, but the value specified for the Reserved parameter is not valid. The value must be the null pointer. This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows. Completion Code: MQCC_FAILED Programmer Response: Modify the exit to specify the null pointer as the value of the Reserved parameter. 2379 (X'094B')MQRC_NO_DATA_AVAILABLE Explanation: This reason should be returned by the MQZ_ENUMERATE_AUTHORITY_DATA installable service component when there is no more authority data to return to the invoker of the service component. On z/OS, this reason code does not occur. Completion Code: MQCC_FAILED Programmer Response: None. 2380 (X'094C')MQRC_SCO_ERROR Explanation: On an MQCONNX call, the MQSCO structure is not valid for one of the following reasons: The StrucId field is not MQSCO_STRUC_ID. The Version field is not MQSCO_VERSION_1. This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows. Completion Code: MQCC_FAILED Programmer Response: Correct the definition of the MQSCO structure. 2381 (X'094D')MQRC_KEY_REPOSITORY_ERROR Explanation: On an MQCONN or MQCONNX call, the location of the key repository is either not specified, not valid, or results in an error when used to access the key repository. The location of the key repository is specified by one of the following: The value of the MQSSLKEYR environment variable (MQCONN or MQCONNX call), or The value of the KeyRepository field in the MQSCO structure (MQCONNX call only). For the MQCONNX call, if both MQSSLKEYR and KeyRepository are specified, the latter is used. This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows. Completion Code: MQCC_FAILED Programmer Response: Specify a valid location for the key repository. 2382 (X'094E')MQRC_CRYPTO_HARDWARE_ERROR Explanation: On an MQCONN or MQCONNX call, the configuration string for the cryptographic hardware is not valid, or results in an error when used to configure the cryptographic hardware. The configuration string is specified by one of the following: The value of the MQSSLCRYP environment variable (MQCONN or MQCONNX call), or The value of the CryptoHardware field in the MQSCO structure (MQCONNX call only). For the MQCONNX call, if both MQSSLCRYP and CryptoHardware are specified, the latter is used. This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows. Completion Code: MQCC_FAILED Programmer Response: Specify a valid configuration string for the cryptographic hardware. 2383 (X'094F')MQRC_AUTH_INFO_REC_COUNT_ERROR Explanation: On an MQCONNX call, the AuthInfoRecCount field in the MQSCO structure specifies a value that is less than zero. This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows. Completion Code: MQCC_FAILED Programmer Response: Specify a value for AuthInfoRecCount that is zero or greater. 2384 (X'0950')MQRC_AUTH_INFO_REC_ERROR Explanation: On an MQCONNX call, the MQSCO structure does not specify the address of the MQAIR records correctly. One of the following applies: AuthInfoRecCount is greater than zero, but AuthInfoRecOffset is zero and AuthInfoRecPtr is the null pointer. AuthInfoRecOffset is not zero and AuthInfoRecPtr is not the null pointer. AuthInfoRecPtr is not a valid pointer. AuthInfoRecOffset or AuthInfoRecPtr points to storage that is not accessible. This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows. Completion Code: MQCC_FAILED Programmer Response: Ensure that one of AuthInfoRecOffset or AuthInfoRecPtr is zero and the other nonzero. Ensure that the field used points to accessible storage. 2385 (X'0951')MQRC_AIR_ERROR Explanation: On an MQCONNX call, an MQAIR record is not valid for one of the following reasons: The StrucId field is not MQAIR_STRUC_ID. The Version field is not MQAIR_VERSION_1. This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows. Completion Code: MQCC_FAILED Programmer Response: Correct the definition of the MQAIR record. 2386 (X'0952')MQRC_AUTH_INFO_TYPE_ERROR Explanation: On an MQCONNX call, the AuthInfoType field in an MQAIR record specifies a value that is not valid. This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows. Completion Code: MQCC_FAILED Programmer Response: Specify MQAIT_CRL_LDAP for AuthInfoType. 2387 (X'0953')MQRC_AUTH_INFO_CONN_NAME_ERROR Explanation: On an MQCONNX call, the AuthInfoConnName field in an MQAIR record specifies a value that is not valid. This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows. Completion Code: MQCC_FAILED Programmer Response: Specify a valid connection name. 2388 (X'0954')MQRC_LDAP_USER_NAME_ERROR Explanation: On an MQCONNX call, an LDAP user name in an MQAIR record is not specified correctly. One of the following applies: LDAPUserNameLength is greater than zero, but LDAPUserNameOffset is zero and LDAPUserNamePtr is the null pointer. LDAPUserNameOffset is nonzero and LDAPUserNamePtr is not the null pointer. LDAPUserNamePtr is not a valid pointer. LDAPUserNameOffset or LDAPUserNamePtr points to storage that is not accessible. This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows. Completion Code: MQCC_FAILED Programmer Response: Ensure that one of LDAPUserNameOffset or LDAPUserNamePtr is zero and the other nonzero. Ensure that the field used points to accessible storage. 2389 (X'0955')MQRC_LDAP_USER_NAME_LENGTH_ERR Explanation: On an MQCONNX call, the LDAPUserNameLength field in an MQAIR record specifies a value that is less than zero. This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows. Completion Code: MQCC_FAILED Programmer Response: Specify a value for LDAPUserNameLength that is zero or greater. 2390 (X'0956')MQRC_LDAP_PASSWORD_ERROR Explanation: On an MQCONNX call, the LDAPPassword field in an MQAIR record specifies a value when no value is allowed. This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows. Completion Code: MQCC_FAILED Programmer Response: Specify a value that is blank or null. 2391 (X'0957')MQRC_SSL_ALREADY_INITIALIZED Explanation: An MQCONN or MQCONNX call was issued with SSL configuration options specified, but the SSL environment had already been initialized. The connection to the queue manager completed successfully, but the SSL configuration options specified on the call were ignored; the existing SSL environment was used instead. This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows. Completion Code: MQCC_WARNING Programmer Response: If the application must be run with the SSL configuration options defined on the MQCONN or MQCONNX call, use the MQDISC call to sever the connection to the queue manager and then terminate the application. Alternatively run the application later when the SSL environment has not been initialized. 2392 (X'0958')MQRC_SSL_CONFIG_ERROR Explanation: On an MQCONNX call, the MQCNO structure does not specify the MQSCO structure correctly. One of the following applies: SSLConfigOffset is nonzero and SSLConfigPtr is not the null pointer. SSLConfigPtr is not a valid pointer. SSLConfigOffset or SSLConfigPtr points to storage that is not accessible. This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows. Completion Code: MQCC_FAILED Programmer Response: Ensure that one of SSLConfigOffset or SSLConfigPtr is zero and the other nonzero. Ensure that the field used points to accessible storage. 2393 (X'0959')MQRC_SSL_INITIALIZATION_ERROR Explanation: An MQCONN or MQCONNX call was issued with SSL configuration options specified, but an error occurred during the initialization of the SSL environment. This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows. Completion Code: MQCC_FAILED Programmer Response: Check that the SSL installation is correct. 2394 (X'095A')MQRC_Q_INDEX_TYPE_ERROR Explanation: An MQGET call was issued specifying one or more of the following options: MQGMO_ALL_MSGS_AVAILABLE MQGMO_ALL_SEGMENTS_AVAILABLE MQGMO_COMPLETE_MSG MQGMO_LOGICAL_ORDER but the call failed because the queue is not indexed by group identifier. These options require the queue to have an IndexType of MQIT_GROUP_ID. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Redefine the queue to have an IndexType of MQIT_GROUP_ID. Alternatively, modify the application to avoid using the options listed above. 2395 (X'095B')MQRC_CFBS_ERROR Explanation: An MQPUT or MQPUT1 call was issued, but the message data contains an MQCFBS structure that is not valid. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Check that the fields in the structure are set correctly. 2396 (X'095C')MQRC_SSL_NOT_ALLOWED Explanation: A connection to a queue manager was requested, specifying SSL encryption. However, the connection mode requested is one that does not support SSL (for example, bindings connect). This reason code occurs only with Java applications. Completion Code: MQCC_FAILED Programmer Response: Modify the application to request client connection mode, or to disable SSL encryption. 2397 (X'095D')MQRC_JSSE_ERROR Explanation: JSSE reported an error (for example, while connecting to a queue manager using SSL encryption). The MQException object containing this reason code references the Exception thrown by JSSE; this can be obtained by using the MQException.getCause() method. From JMS, the MQException is linked to the thrown JMSException. This reason code occurs only with Java applications. Completion Code: MQCC_FAILED Programmer Response: Inspect the causal exception to determine the JSSE error. 2398 (X'095E')MQRC_SSL_PEER_NAME_MISMATCH Explanation: The application attempted to connect to the queue manager using SSL encryption, but the distinguished name presented by the queue manager does not match the specified pattern. This reason code occurs only with Java applications. Completion Code: MQCC_FAILED Programmer Response: Check the certificates used to identify the queue manager. Also check the value of the sslPeerName property specified by the application. 2399 (X'095F')MQRC_SSL_PEER_NAME_ERROR Explanation: The application specified a peer name of incorrect format. This reason code occurs only with Java applications. Completion Code: MQCC_FAILED Programmer Response: Check the value of the sslPeerName property specified by the application. 2400 (X'0960')MQRC_UNSUPPORTED_CIPHER_SUITE Explanation: A connection to a queue manager was requested, specifying SSL encryption. However, JSSE reported that it does not support the CipherSuite specified by the application. This reason code occurs only with Java applications. Completion Code: MQCC_FAILED Programmer Response: Check the CipherSuite specified by the application. Note that the names of JSSE CipherSuites differ from their equivalent CipherSpecs used by the queue manager. Also, check that JSSE is correctly installed. 2401 (X'0961')MQRC_SSL_CERTIFICATE_REVOKED Explanation: A connection to a queue manager was requested, specifying SSL encryption. However, the certificate presented by the queue manager was found to be revoked by one of the specified CertStores. This reason code occurs only with Java applications. Completion Code: MQCC_FAILED Programmer Response: Check the certificates used to identify the queue manager. 2402 (X'0962')MQRC_SSL_CERT_STORE_ERROR Explanation: A connection to a queue manager was requested, specifying SSL encryption. However, none of the CertStore objects provided by the application could be searched for the certificate presented by the queue manager. The MQException object containing this reason code references the Exception encountered when searching the first CertStore; this can be obtained using the MQException.getCause() method. From JMS, the MQException is linked to the thrown JMSException. This reason code occurs only with Java applications. Completion Code: MQCC_FAILED Programmer Response: Inspect the causal exception to determine the underlying error. Check the CertStore objects provided by your application. If the causal exception is a java.lang.NoSuchElementException, ensure that your application is not specifying an empty collection of CertStore objects. 2406 (X'0966')MQRC_CLIENT_EXIT_LOAD_ERROR Explanation: The external user exit required for a client connection could not be loaded because the shared library specified for it cannot be found, or the entry point specified for it cannot be found. This reason code occurs only with Java applications. Completion Code: MQCC_FAILED Programmer Response: Ensure that the correct library has been specified, and that the path variable for the machine environment includes the relevant directory. Ensure also that the entry point has been named properly and that the named library does export it. 2407 (X'0967')MQRC_CLIENT_EXIT_ERROR Explanation: A failure occured while executing a non-Java user exit for a client connection. This reason code occurs only with Java applications. Completion Code: MQCC_FAILED Programmer Response: Check that the non-Java user exit can accept the parameters and message being passed to it and that it can handle error conditions, and that any information that the exit requires, such as user data, is correct and available. 2409 (X'0969')MQRC_SSL_KEY_RESET_ERROR Explanation: On an MQCONN or MQCONNX call, the value of the SSL key reset count is not in the valid range of 0 through 999 999 999. The value of the SSL key reset count is specified by either the value of the MQSSLRESET environment variable (MQCONN or MQCONNX call), or the value of the KeyResetCount field in the MQSCO structure (MQCONNX call only). For the MQCONNX call, if both MQSSLRESET and KeyResetCount are specified, the latter is used. MQCONN or MQCONNX Completion Code: MQCC_FAILED Programmer Response: Check that the fields in the structure and the MQSSLRESET environment variable are set correctly. 2411 (X'096B')MQRC_LOGGER_STATUS Explanation: This condition is detected when a logger event occurs. Completion Code: MQCC_WARNING Programmer Response: None. This reason code is only used to identify the corresponding event message. 2412 (X'096C')MQRC_COMMAND_MQSC Explanation: This condition is detected when an MQSC command is executed. Completion Code: MQCC_WARNING Programmer Response: None. This reason code is only used to identify the corresponding event message. 2413 (X'096D')MQRC_COMMAND_PCF Explanation: This condition is detected when a PCF command is executed. Completion Code: MQCC_WARNING Programmer Response: None. This reason code is only used to identify the corresponding event message. 2414 (X'096E')MQRC_CFIF_ERROR Explanation: An MQPUT or MQPUT1 call was issued, but the message data contains an MQCFIF structure that is not valid. This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Check that the fields in the structure are set correctly. 2415 (X'096F')MQRC_CFSF_ERROR Explanation: An MQPUT or MQPUT1 call was issued, but the message data contains an MQCFSF structure that is not valid. This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Check that the fields in the structure are set correctly. 2416 (X'0970')MQRC_CFGR_ERROR Explanation: An MQPUT or MQPUT1 call was issued, but the message data contains an MQCFGR structure that is not valid. This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Check that the fields in the structure are set correctly. 2417 (X'0971')MQRC_MSG_NOT_ALLOWED_IN_GROUP Explanation: An MQPUT or MQPUT1 call was issued to put a message in a group but it is not valid to put such a message in a group. An example of an invalid message is a PCF message where the Type is MQCFT_TRACE_ROUTE. Completion Code: MQCC_FAILED Programmer Response: Remove the invalid message from the group. 2418 (X'0972')MQRC_FILTER_OPERATOR_ERROR Explanation: The Operator parameter supplied is not valid. If it is an input variable then the value is not one of the MQCFOP_* constant values. If it is an output variable then the parameter pointer is not valid, or it points to read-only storage. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredicatable results occur.) Completion Code: MQCC_FAILED Programmer Response: Correct the parameter. 2419 (X'0973')MQRC_NESTED_SELECTOR_ERROR Explanation: An mqAddBag call was issued, but the bag to be nested contained a data item with an inconsistent selector. This reason only occurs if the bag into which the nested bag was to be added was created with the MQCBO_CHECK_SELECTORS option. Completion Code: MQCC_FAILED Programmer Response: Ensure that all data items within the bag to be nested have selectors that are consistent with the data type implied by the item. 2420 (X'0974')MQRC_EPH_ERROR Explanation: An MQPUT or MQPUT1 call was issued, but the message data contains an MQEPH structure that is not valid. Possible errors include the following: The StrucId field is not MQEPH_STRUC_ID. The Version field is not MQEPH_VERSION_1. The StrucLength field specifies a value that is too small to include the structure plus the variable-length data at the end of the structure. The CodedCharSetId field is zero, or a negative value that is not valid. The Flags field contains an invalid combination of MQEPH_* values. The BufferLength parameter of the call has a value that is too small to accommodate the structure, so the structure extends beyond the end of the message. Completion Code: MQCC_FAILED Programmer Response: Check that the fields in the structure are set correctly. Ensure that the application sets the CodedCharSetId field to a valid value; note that MQCCSI_DEFAULT, MQCCSI_EMBEDDED, MQCCSI_Q_MGR, and MQCCSI_UNDEFINED are not valid in this field. 2421 (X'0975')MQRC_RFH_FORMAT_ERROR Explanation: The message contains an MQRFH structure, but its format is incorrect. If you are using WebSphere MQ SOAP, the error is in an incoming SOAP/MQ request message. Completion Code: MQCC_FAILED Programmer Response: If you are using WebSphere MQ SOAP with the IBM-supplied sender, contact your IBM support center. If you are using WebSphere MQ SOAP with a bespoke sender, check that the RFH2 section of the SOAP/MQ request message is in valid RFH2 format. 2422 (X'0976')MQRC_CFBF_ERROR Explanation: An MQPUT or MQPUT1 call was issued, but the message data contains an MQCFBF structure that is not valid. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Check that the fields in the structure are set correctly. 2423 (X'0977')MQRC_CLIENT_CHANNEL_CONFLICT Explanation: A client channel definition table was specified for determining the name of the channel, but the name has already been defined. This reason code occurs only with Java applications. Completion Code: MQCC_FAILED Programmer Response: Change the channel name to blank and try again. 6100 (X'17D4')MQRC_REOPEN_EXCL_INPUT_ERROR Explanation: An open object does not have the correct ImqObject open options and requires one or more additional options. An implicit reopen is required but closure has been prevented. Closure has been prevented because the queue is open for exclusive input and closure might result in the queue being accessed by another process or thread, before the queue is reopened by the process or thread that presently has access. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED Programmer Response: Set the open options explicitly to cover all eventualities so that implicit reopening is not required. 6101 (X'17D5')MQRC_REOPEN_INQUIRE_ERROR Explanation: An open object does not have the correct ImqObject open options and requires one or more additional options. An implicit reopen is required but closure has been prevented. Closure has been prevented because one or more characteristics of the object need to be checked dynamically prior to closure, and the open options do not already include MQOO_INQUIRE. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED Programmer Response: Set the open options explicitly to include MQOO_INQUIRE. 6102 (X'17D6')MQRC_REOPEN_SAVED_CONTEXT_ERR Explanation: An open object does not have the correct ImqObject open options and requires one or more additional options. An implicit reopen is required but closure has been prevented. Closure has been prevented because the queue is open with MQOO_SAVE_ALL_CONTEXT, and a destructive get has been performed previously. This has caused retained state information to be associated with the open queue and this information would be destroyed by closure. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED Programmer Response: Set the open options explicitly to cover all eventualities so that implicit reopening is not required. 6103 (X'17D7')MQRC_REOPEN_TEMPORARY_Q_ERROR Explanation: An open object does not have the correct ImqObject open options and requires one or more additional options. An implicit reopen is required but closure has been prevented. Closure has been prevented because the queue is a local queue of the definition type MQQDT_TEMPORARY_DYNAMIC, that would be destroyed by closure. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED Programmer Response: Set the open options explicitly to cover all eventualities so that implicit reopening is not required. 6104 (X'17D8')MQRC_ATTRIBUTE_LOCKED Explanation: An attempt has been made to change the value of an attribute of an object while that object is open, or, for an ImqQueueManager object, while that object is connected. Certain attributes cannot be changed in these circumstances. Close or disconnect the object (as appropriate) before changing the attribute value. An object may have been connected and/or opened unexpectedly and implicitly in order to perform an MQINQ call. Check the attribute cross-reference table in the WebSphere MQ Using C++ book to determine whether any of your method invocations result in an MQINQ call. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED Programmer Response: Include MQOO_INQUIRE in the ImqObject open options and set them earlier. 6105 (X'17D9')MQRC_CURSOR_NOT_VALID Explanation: The browse cursor for an open queue has been invalidated since it was last used by an implicit reopen. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED Programmer Response: Set the ImqObject open options explicitly to cover all eventualities so that implicit reopening is not required. 6106 (X'17DA')MQRC_ENCODING_ERROR Explanation: The encoding of the (next) message item needs to be MQENC_NATIVE for pasting. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED 6107 (X'17DB')MQRC_STRUC_ID_ERROR Explanation: The structure id for the (next) message item, which is derived from the 4 characters beginning at the data pointer, is either missing or is inconsistent with the class of object into which the item is being pasted. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED 6108 (X'17DC')MQRC_NULL_POINTER Explanation: A null pointer has been supplied where a nonnull pointer is either required or implied. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED 6109 (X'17DD')MQRC_NO_CONNECTION_REFERENCE Explanation: The connection reference is null. A connection to an ImqQueueManager object is required. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED 6110 (X'17DE')MQRC_NO_BUFFER Explanation: No buffer is available. For an ImqCache object, one cannot be allocated, denoting an internal inconsistency in the object state that should not occur. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED 6111 (X'17DF')MQRC_BINARY_DATA_LENGTH_ERROR Explanation: The length of the binary data is inconsistent with the length of the target attribute. Zero is a correct length for all attributes. The correct length for an accounting token is MQ_ACCOUNTING_TOKEN_LENGTH. The correct length for an alternate security id is MQ_SECURITY_ID_LENGTH. The correct length for a correlation id is MQ_CORREL_ID_LENGTH. The correct length for a facility token is MQ_FACILITY_LENGTH. The correct length for a group id is MQ_GROUP_ID_LENGTH. The correct length for a message id is MQ_MSG_ID_LENGTH. The correct length for an instance id is MQ_OBJECT_INSTANCE_ID_LENGTH. The correct length for a transaction instance id is MQ_TRAN_INSTANCE_ID_LENGTH. The correct length for a message token is MQ_MSG_TOKEN_LENGTH. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED 6112 (X'17E0')MQRC_BUFFER_NOT_AUTOMATIC Explanation: A user-defined (and managed) buffer cannot be resized. A user-defined buffer can only be replaced or withdrawn. A buffer must be automatic (system-managed) before it can be resized. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED Programmer Response: 6113 (X'17E1')MQRC_INSUFFICIENT_BUFFER Explanation: There is insufficient buffer space available after the data pointer to accommodate the request. This might be because the buffer cannot be resized. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED 6114 (X'17E2')MQRC_INSUFFICIENT_DATA Explanation: There is insufficient data after the data pointer to accommodate the request. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED 6115 (X'17E3')MQRC_DATA_TRUNCATED Explanation: Data has been truncated when copying from one buffer to another. This might be because the target buffer cannot be resized, or because there is a problem addressing one or other buffer, or because a buffer is being downsized with a smaller replacement. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED 6116 (X'17E4')MQRC_ZERO_LENGTH Explanation: A zero length has been supplied where a positive length is either required or implied. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED 6117 (X'17E5')MQRC_NEGATIVE_LENGTH Explanation: A negative length has been supplied where a zero or positive length is required. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED 6118 (X'17E6')MQRC_NEGATIVE_OFFSET Explanation: A negative offset has been supplied where a zero or positive offset is required. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED 6119 (X'17E7')MQRC_INCONSISTENT_FORMAT Explanation: The format of the (next) message item is inconsistent with the class of object into which the item is being pasted. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED 6120 (X'17E8')MQRC_INCONSISTENT_OBJECT_STATE Explanation: There is an inconsistency between this object, which is open, and the referenced ImqQueueManager object, which is not connected. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED 6121 (X'17E9')MQRC_CONTEXT_OBJECT_NOT_VALID Explanation: The ImqPutMessageOptions context reference does not reference a valid ImqQueue object. The object has been previously destroyed. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED 6122 (X'17EA')MQRC_CONTEXT_OPEN_ERROR Explanation: The ImqPutMessageOptions context reference references an ImqQueue object that could not be opened to establish a context. This may be because the ImqQueue object has inappropriate open options. Inspect the referenced object reason code to establish the cause. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED 6123 (X'17EB')MQRC_STRUC_LENGTH_ERROR Explanation: The length of a data structure is inconsistent with its content. For an MQRMH, the length is insufficient to contain the fixed fields and all offset data. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED 6124 (X'17EC')MQRC_NOT_CONNECTED Explanation: A method failed because a required connection to a queue manager was not available, and a connection cannot be established implicitly because the IMQ_IMPL_CONN flag of the ImqQueueManager behavior class attribute is FALSE. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED Programmer Response: Establish a connection to a queue manager and retry. 6125 (X'17ED')MQRC_NOT_OPEN Explanation: A method failed because an object was not open, and opening cannot be accomplished implicitly because the IMQ_IMPL_OPEN flag of the ImqObject behavior class attribute is FALSE. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED Programmer Response: Open the object and retry. 6126 (X'17EE')MQRC_DISTRIBUTION_LIST_EMPTY Explanation: An ImqDistributionList failed to open because there are no ImqQueue objects referenced. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED Programmer Response: Establish at least one ImqQueue object in which the distribution list reference addresses the ImqDistributionList object, and retry. 6127 (X'17EF')MQRC_INCONSISTENT_OPEN_OPTIONS Explanation: A method failed because the object is open, and the ImqObject open options are inconsistent with the required operation. The object cannot be reopened implicitly because the IMQ_IMPL_OPEN flag of the ImqObject behavior class attribute is false. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED Programmer Response: Open the object with appropriate ImqObject open options and retry. 6128 (X'17FO')MQRC_WRONG_VERSION Explanation: A method failed because a version number specified or encountered is either incorrect or not supported. For the ImqCICSBridgeHeader class, the problem is with the version attribute. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED Programmer Response: If you are specifying a version number, use one that is supported by the class. If you are receiving message data from another program, ensure that both programs are using consistent and supported version numbers. 6129 (X'17F1')MQRC_REFERENCE_ERROR Explanation: An object reference is invalid. There is a problem with the address of a referenced object. At the time of use, the address of the object is nonnull, but is invalid and cannot be used for its intended purpose. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED Programmer Response: Check that the referenced object is neither deleted nor out of scope, or remove the reference by supplying a null address value. Appendix A. API completion and reason codes: ============================================ The following is a list of the completion codes (MQCC) returned by WebSphere MQ 0: Successful completion (MQCC_OK) The call completed fully; all output parameters have been set. The Reason parameter always has the value MQRC_NONE in this case. 1: Warning (partial completion) (MQCC_WARNING) The call completed partially. Some output parameters might have been set in addition to the CompCode and Reason output parameters. The Reason parameter gives additional information. 2: Call failed (MQCC_FAILED) The processing of the call did not complete, and the state of the queue manager is normally unchanged; exceptions are specifically noted. Only the CompCode and Reason output parameters have been set; all other parameters are unchanged. The reason might be a fault in the application program, or it might be a result of some situation external to the program, for example the application's authority might have been revoked. The Reason parameter gives additional information. Reason codes The reason code parameter (Reason) is a qualification to the completion code parameter (CompCode). If there is no special reason to report, MQRC_NONE is returned. A successful call returns MQCC_OK and MQRC_NONE. If the completion code is either MQCC_WARNING or MQCC_FAILED, the queue manager always reports a qualifying reason; details are given under each call description. Where user exit routines set completion codes and reasons, they should adhere to these rules. In addition, any special reason values defined by user exits should be less than zero, to ensure that they do not conflict with values defined by the queue manager. Exits can set reasons already defined by the queue manager, where these are appropriate. Reason codes also occur in: The Reason field of the MQDLH structure The Feedback field of the MQMD structure Reason code list The following is a list of reason codes, in numeric order, providing detailed information to help you understand them, including: An explanation of the circumstances that have caused the code to be raised The associated completion code Suggested programmer actions in response to the code See Reason code cross reference for a list of reason codes in alphabetic order. Codes in the range 3000 - 4999 (X'0BB8' - X'1387') are specific to PCF and are described in Appendix B. PCF reason codes. 0 (X'0000')MQRC_NONE Explanation: The call completed normally. The completion code (CompCode) is MQCC_OK. Completion Code: MQCC_OK Programmer Response: None. 900 (X'0384')MQRC_APPL_FIRST Explanation: This is the lowest value for an application-defined reason code returned by a data-conversion exit. Data-conversion exits can return reason codes in the range MQRC_APPL_FIRST through MQRC_APPL_LAST to indicate particular conditions that the exit has detected. Completion Code: MQCC_WARNING or MQCC_FAILED Programmer Response: As defined by the writer of the data-conversion exit. 999 (X'03E7')MQRC_APPL_LAST Explanation: This is the highest value for an application-defined reason code returned by a data-conversion exit. Data-conversion exits can return reason codes in the range MQRC_APPL_FIRST through MQRC_APPL_LAST to indicate particular conditions that the exit has detected. Completion Code: MQCC_WARNING or MQCC_FAILED Programmer Response: As defined by the writer of the data-conversion exit. 2001 (X'07D1')MQRC_ALIAS_BASE_Q_TYPE_ERROR Explanation: An MQOPEN or MQPUT1 call was issued specifying an alias queue as the destination, but the BaseQName in the alias queue definition resolves to a queue that is not a local queue, a local definition of a remote queue, or a cluster queue. Completion Code: MQCC_FAILED Programmer Response: Correct the queue definitions. 2002 (X'07D2')MQRC_ALREADY_CONNECTED Explanation: An MQCONN or MQCONNX call was issued, but the application is already connected to the queue manager. On z/OS, this reason code occurs for batch and IMS applications only; it does not occur for CICS applications. On AIX, HP-UX, i5/OS, Solaris, Windows, this reason code occurs if the application attempts to create a nonshared handle when a nonshared handle already exists for the thread. A thread can have no more than one nonshared handle. On Windows, MTS objects do not receive this reason code, as additional connections to the queue manager are allowed. Completion Code: MQCC_WARNING Programmer Response: None. The Hconn parameter returned has the same value as was returned for the previous MQCONN or MQCONNX call. An MQCONN or MQCONNX call that returns this reason code does not mean that an additional MQDISC call must be issued in order to disconnect from the queue manager. If this reason code is returned because the application has been called in a situation where the connect has already been done, a corresponding MQDISC should not be issued, because this will cause the application that issued the original MQCONN or MQCONNX call to be disconnected as well. 2003 (X'07D3')MQRC_BACKED_OUT Explanation: The current unit of work encountered a fatal error or was backed out. This occurs in the following cases: On an MQCMIT or MQDISC call, when the commit operation has failed and the unit of work has been backed out. All resources that participated in the unit of work have been returned to their state at the start of the unit of work. The MQCMIT or MQDISC call completes with MQCC_WARNING in this case. On z/OS, this reason code occurs only for batch applications. On an MQGET, MQPUT, or MQPUT1 call that is operating within a unit of work, when the unit of work has already encountered an error that prevents the unit of work being committed (for example, when the log space is exhausted). The application must issue the appropriate call to back out the unit of work. (For a unit of work coordinated by the queue manager, this call is the MQBACK call, although the MQCMIT call has the same effect in these circumstances.) The MQGET, MQPUT, or MQPUT1 call completes with MQCC_FAILED in this case. On z/OS, this case does not occur. Completion Code: MQCC_WARNING or MQCC_FAILED Programmer Response: Check the returns from previous calls to the queue manager. For example, a previous MQPUT call may have failed. 2004 (X'07D4')MQRC_BUFFER_ERROR Explanation: The Buffer parameter is not valid for one of the following reasons: The parameter pointer is not valid. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) The parameter pointer points to storage that cannot be accessed for the entire length specified by BufferLength. For calls where Buffer is an output parameter: the parameter pointer points to read-only storage. Completion Code: MQCC_FAILED Programmer Response: Correct the parameter. 2005 (X'07D5')MQRC_BUFFER_LENGTH_ERROR Explanation: The BufferLength parameter is not valid, or the parameter pointer is not valid. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) This reason can also be returned to an MQ client program on the MQCONN or MQCONNX call if the negotiated maximum message size for the channel is smaller than the fixed part of any call structure. This reason should also be returned by the MQZ_ENUMERATE_AUTHORITY_DATA installable service component when the AuthorityBuffer parameter is too small to accommodate the data to be returned to the invoker of the service component. Completion Code: MQCC_FAILED Programmer Response: Specify a value that is zero or greater. For the mqAddString and mqSetString calls, the special value MQBL_NULL_TERMINATED is also valid. 2006 (X'07D6')MQRC_CHAR_ATTR_LENGTH_ERROR Explanation: CharAttrLength is negative (for MQINQ or MQSET calls), or is not large enough to hold all selected attributes (MQSET calls only). This reason also occurs if the parameter pointer is not valid. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) Completion Code: MQCC_FAILED Programmer Response: Specify a value large enough to hold the concatenated strings for all selected attributes. 2007 (X'07D7')MQRC_CHAR_ATTRS_ERROR Explanation: CharAttrs is not valid. The parameter pointer is not valid, or points to read-only storage for MQINQ calls or to storage that is not as long as implied by CharAttrLength. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) Completion Code: MQCC_FAILED Programmer Response: Correct the parameter. 2008 (X'07D8')MQRC_CHAR_ATTRS_TOO_SHORT Explanation: For MQINQ calls, CharAttrLength is not large enough to contain all of the character attributes for which MQCA_* selectors are specified in the Selectors parameter. The call still completes, with the CharAttrs parameter string filled in with as many character attributes as there is room for. Only complete attribute strings are returned: if there is insufficient space remaining to accommodate an attribute in its entirety, that attribute and subsequent character attributes are omitted. Any space at the end of the string not used to hold an attribute is unchanged. An attribute that represents a set of values (for example, the namelist Names attribute) is treated as a single entity--either all of its values are returned, or none. Completion Code: MQCC_WARNING Programmer Response: Specify a large enough value, unless only a subset of the values is needed. 2009 (X'07D9')MQRC_CONNECTION_BROKEN Explanation: Connection to the queue manager has been lost. This can occur because the queue manager has ended. If the call is an MQGET call with the MQGMO_WAIT option, the wait has been canceled. All connection and object handles are now invalid. For MQ client applications, it is possible that the call did complete successfully, even though this reason code is returned with a CompCode of MQCC_FAILED. Completion Code: MQCC_FAILED Programmer Response: Applications can attempt to reconnect to the queue manager by issuing the MQCONN or MQCONNX call. It may be necessary to poll until a successful response is received. On z/OS for CICS applications, it is not necessary to issue the MQCONN or MQCONNX call, because CICS applications are connected automatically. Any uncommitted changes in a unit of work should be backed out. A unit of work that is coordinated by the queue manager is backed out automatically. 2010 (X'07DA')MQRC_DATA_LENGTH_ERROR Explanation: The DataLength parameter is not valid. Either the parameter pointer is not valid, or it points to read-only storage. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) This reason can also be returned to an MQ client program on the MQGET, MQPUT, or MQPUT1 call, if the BufferLength parameter exceeds the maximum message size that was negotiated for the client channel. Completion Code: MQCC_FAILED Programmer Response: Correct the parameter. If the error occurs for an MQ client program, also check that the maximum message size for the channel is big enough to accommodate the message being sent; if it is not big enough, increase the maximum message size for the channel. 2011 (X'07DB')MQRC_DYNAMIC_Q_NAME_ERROR Explanation: On the MQOPEN call, a model queue is specified in the ObjectName field of the ObjDesc parameter, but the DynamicQName field is not valid, for one of the following reasons: DynamicQName is completely blank (or blank up to the first null character in the field). Characters are present that are not valid for a queue name. An asterisk is present beyond the 33rd position (and before any null character). An asterisk is present followed by characters that are not null and not blank. This reason code can also sometimes occur when a server application opens the reply queue specified by the ReplyToQ and ReplyToQMgr fields in the MQMD of a message that the server has just received. In this case the reason code indicates that the application that sent the original message placed incorrect values into the ReplyToQ and ReplyToQMgr fields in the MQMD of the original message. Completion Code: MQCC_FAILED Programmer Response: Specify a valid name. 2012 (X'07DC')MQRC_ENVIRONMENT_ERROR Explanation: The call is not valid for the current environment. 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 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 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. On HP OpenVMS, OS/2, i5/OS, 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 an MQ client environment. An MQXCLWLN call was issued, but the call did not originate from a cluster workload exit. Completion Code: MQCC_FAILED Programmer Response: Do one of the following (as appropriate): 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. 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. In the other environments: Link the application with the correct libraries (threaded or nonthreaded). Remove from the application the call that is not supported. 2013 (X'07DD')MQRC_EXPIRY_ERROR Explanation: On an MQPUT or MQPUT1 call, the value specified for the Expiry field in the message descriptor MQMD is not valid. Completion Code: MQCC_FAILED Programmer Response: Specify a value that is greater than zero, or the special value MQEI_UNLIMITED. 2014 (X'07DE')MQRC_FEEDBACK_ERROR Explanation: On an MQPUT or MQPUT1 call, the value specified for the Feedback field in the message descriptor MQMD is not valid. The value is not MQFB_NONE, and is outside both the range defined for system feedback codes and the range defined for application feedback codes. Completion Code: MQCC_FAILED Programmer Response: Specify MQFB_NONE, or a value in the range MQFB_SYSTEM_FIRST through MQFB_SYSTEM_LAST, or MQFB_APPL_FIRST through MQFB_APPL_LAST. 2016 (X'07E0')MQRC_GET_INHIBITED Explanation: MQGET calls are currently inhibited for the queue, or for the queue to which this queue resolves. Completion Code: MQCC_FAILED Programmer Response: If the system design allows get requests to be inhibited for short periods, retry the operation later. 2017 (X'07E1')MQRC_HANDLE_NOT_AVAILABLE Explanation: An MQOPEN or MQPUT1 call was issued, but the maximum number of open handles allowed for the current task has already been reached. Be aware that when a distribution list is specified on the MQOPEN or MQPUT1 call, each queue in the distribution list uses one handle. On z/OS, "task" means a CICS task, a z/OS task, or an IMS-dependent region. Completion Code: MQCC_FAILED Programmer Response: Check whether the application is issuing MQOPEN calls without corresponding MQCLOSE calls. If it is, modify the application to issue the MQCLOSE call for each open object as soon as that object is no longer needed. Also check whether the application is specifying a distribution list containing a large number of queues that are consuming all of the available handles. If it is, increase the maximum number of handles that the task can use, or reduce the size of the distribution list. The maximum number of open handles that a task can use is given by the MaxHandles queue manager attribute. 2018 (X'07E2')MQRC_HCONN_ERROR Explanation: The connection handle Hconn is not valid, for one of the following reasons: The parameter pointer is not valid, or (for the MQCONN or MQCONNX call) points to read-only storage. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) The value specified was not returned by a preceding MQCONN or MQCONNX call. The value specified has been made invalid by a preceding MQDISC call. The handle is a shared handle that has been made invalid by another thread issuing the MQDISC call. The handle is a shared handle that is being used on the MQBEGIN call (only nonshared handles are valid on MQBEGIN). The handle is a nonshared handle that is being used a thread that did not create the handle. The call was issued in the MTS environment in a situation where the handle is not valid (for example, passing the handle between processes or packages; note that passing the handle between library packages is supported). Completion Code: MQCC_FAILED Programmer Response: Ensure that a successful MQCONN or MQCONNX call is performed for the queue manager, and that an MQDISC call has not already been performed for it. Ensure that the handle is being used within its valid scope (see the description of MQCONN in the WebSphere MQ Application Programming Guide). On z/OS, also check that the application has been linked with the correct stub; this is CSQCSTUB for CICS applications, CSQBSTUB for batch applications, and CSQQSTUB for IMS applications. Also, the stub used must not belong to a release of the queue manager that is more recent than the release on which the application will run. 2019 (X'07E3')MQRC_HOBJ_ERROR Explanation: The object handle Hobj is not valid, for one of the following reasons: The parameter pointer is not valid, or (for the MQOPEN call) points to read-only storage. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) The value specified was not returned by a preceding MQOPEN call. The value specified has been made invalid by a preceding MQCLOSE call. The handle is a shared handle that has been made invalid by another thread issuing the MQCLOSE call. The handle is a nonshared handle that is being used by a thread that did not create the handle. The call is MQGET or MQPUT, but the object represented by the handle is not a queue. Completion Code: MQCC_FAILED Programmer Response: Ensure that a successful MQOPEN call is performed for this object, and that an MQCLOSE call has not already been performed for it. Ensure that the handle is being used within its valid scope (see the description of MQOPEN in the WebSphere MQ Application Programming Guide). 2020 (X'07E4')MQRC_INHIBIT_VALUE_ERROR Explanation: On an MQSET call, the value specified for either the MQIA_INHIBIT_GET attribute or the MQIA_INHIBIT_PUT attribute is not valid. Completion Code: MQCC_FAILED Programmer Response: Specify a valid value for the InhibitGet or InhibitPut queu attribute. 2021 (X'07E5')MQRC_INT_ATTR_COUNT_ERROR Explanation: On an MQINQ or MQSET call, the IntAttrCount parameter is negative (MQINQ or MQSET), or smaller than the number of integer attribute selectors (MQIA_*) specified in the Selectors parameter (MQSET only). This reason also occurs if the parameter pointer is not valid. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) Completion Code: MQCC_FAILED Programmer Response: Specify a value large enough for all selected integer attributes. 2022 (X'07E6')MQRC_INT_ATTR_COUNT_TOO_SMALL Explanation: On an MQINQ call, the IntAttrCount parameter is smaller than the number of integer attribute selectors (MQIA_*) specified in the Selectors parameter. The call completes with MQCC_WARNING, with the IntAttrs array filled in with as many integer attributes as there is room for. Completion Code: MQCC_WARNING Programmer Response: Specify a large enough value, unless only a subset of the values is needed. 2023 (X'07E7')MQRC_INT_ATTRS_ARRAY_ERROR Explanation: On an MQINQ or MQSET call, the IntAttrs parameter is not valid. The parameter pointer is not valid (MQINQ and MQSET), or points to read-only storage or to storage that is not as long as indicated by the IntAttrCount parameter (MQINQ only). (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) Completion Code: MQCC_FAILED Programmer Response: Correct the parameter. 2024 (X'07E8')MQRC_SYNCPOINT_LIMIT_REACHED Explanation: An MQGET, MQPUT, or MQPUT1 call failed because it would have caused the number of uncommitted messages in the current unit of work to exceed the limit defined for the queue manager (see the MaxUncommittedMsgs queue-manager attribute). The number of uncommitted messages is the sum of the following since the start of the current unit of work: Messages put by the application with the MQPMO_SYNCPOINT option Messages retrieved by the application with the MQGMO_SYNCPOINT option Trigger messages and COA report messages generated by the queue manager for messages put with the MQPMO_SYNCPOINT option COD report messages generated by the queue manager for messages retrieved with the MQGMO_SYNCPOINT option On Compaq NonStop Kernel, this reason code occurs when the maximum number of I/O operations in a single TM/MP transaction has been exceeded. Completion Code: MQCC_FAILED Programmer Response: Check whether the application is looping. If it is not, consider reducing the complexity of the application. Alternatively, increase the queue-manager limit for the maximum number of uncommitted messages within a unit of work. On z/OS, the limit for the maximum number of uncommitted messages can be changed by using the ALTER QMGR command. On i5/OS, the limit for the maximum number of uncommitted messages can be changed by using the CHGMQM command. On Compaq NonStop Kernel, the application should cancel the transaction and retry with a smaller number of operations in the unit of work. See the MQSeries for Tandem NonStop Kernel System Management Guide for more details. 2025 (X'07E9')MQRC_MAX_CONNS_LIMIT_REACHED Explanation: The MQCONN or MQCONNX call was rejected because the maximum number of concurrent connections has been exceeded. On z/OS, connection limits are applicable only to TSO and batch requests. The limits are determined by the customer using the following parameters of the CSQ6SYSP macro: For TSO: IDFORE For batch: IDBACK For more information, see the WebSphere MQ for z/OS System Setup Guide. On HP OpenVMS, OS/2, i5/OS, Compaq NonStop Kernel, UNIX systems, and Windows, this reason code can also occur on the MQOPEN call. When using Java applications, a limit to the number of concurrent connections may be defined by the connection manager. Completion Code: MQCC_FAILED Programmer Response: Either increase the size of the appropriate parameter value, or reduce the number of concurrent connections. 2026 (X'07EA')MQRC_MD_ERROR Explanation: The MQMD structure is not valid, for one of the following reasons: The StrucId field is not MQMD_STRUC_ID. The Version field specifies a value that is not valid or not supported. The parameter pointer is not valid. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) The queue manager cannot copy the changed structure to application storage, even though the call is successful. This can occur, for example, if the pointer points to read-only storage. Completion Code: MQCC_FAILED Programmer Response: Ensure that input fields in the MQMD structure are set correctly. 2027 (X'07EB')MQRC_MISSING_REPLY_TO_Q Explanation: On an MQPUT or MQPUT1 call, the ReplyToQ field in the message descriptor MQMD is blank, but one or both of the following is true: A reply was requested (that is, MQMT_REQUEST was specified in the MsgType field of the message descriptor). A report message was requested in the Report field of the message descriptor. Completion Code: MQCC_FAILED Programmer Response: Specify the name of the queue to which the reply message or report message is to be sent. 2029 (X'07ED')MQRC_MSG_TYPE_ERROR Explanation: Either: On an MQPUT or MQPUT1 call, the value specified for the MsgType field in the message descriptor (MQMD) is not valid. A message processing program received a message that does not have the expected message type. For example, if the WebSphere MQ command server receives a message which is not a request message (MQMT_REQUEST) then it rejects the request with this reason code. Completion Code: MQCC_FAILED Programmer Response: Specify a valid value for the MsgType field. In the case where a request is rejected by a message processing program, refer to the documentation for that program for details of the message types that it supports. 2030 (X'07EE')MQRC_MSG_TOO_BIG_FOR_Q Explanation: An MQPUT or MQPUT1 call was issued to put a message on a queue, but the message was too long for the queue and MQMF_SEGMENTATION_ALLOWED was not specified in the MsgFlags field in MQMD. If segmentation is not allowed, the length of the message cannot exceed the lesser of the queue MaxMsgLength attribute and queue-manager MaxMsgLength attribute. On z/OS, the queue manager does not support the segmentation of messages; if MQMF_SEGMENTATION_ALLOWED is specified, it is accepted but ignored. This reason code can also occur when MQMF_SEGMENTATION_ALLOWED is specified, but the nature of the data present in the message prevents the queue manager splitting it into segments that are small enough to place on the queue: For a user-defined format, the smallest segment that the queue manager can create is 16 bytes. For a built-in format, the smallest segment that the queue manager can create depends on the particular format, but is greater than 16 bytes in all cases other than MQFMT_STRING (for MQFMT_STRING the minimum segment size is 16 bytes). MQRC_MSG_TOO_BIG_FOR_Q can also occur in the Feedback field in the message descriptor of a report message; in this case it indicates that the error was encountered by a message channel agent when it attempted to put the message on a remote queue. Completion Code: MQCC_FAILED Programmer Response: Check whether the BufferLength parameter is specified correctly; if it is, do one of the following: Increase the value of the queue's MaxMsgLength attribute; the queue-manager's MaxMsgLength attribute may also need increasing. Break the message into several smaller messages. Specify MQMF_SEGMENTATION_ALLOWED in the MsgFlags field in MQMD; this will allow the queue manager to break the message into segments. 2031 (X'07EF')MQRC_MSG_TOO_BIG_FOR_Q_MGR Explanation: An MQPUT or MQPUT1 call was issued to put a message on a queue, but the message was too long for the queue manager and MQMF_SEGMENTATION_ALLOWED was not specified in the MsgFlags field in MQMD. If segmentation is not allowed, the length of the message cannot exceed the lesser of the queue-manager MaxMsgLength attribute and queue MaxMsgLength attribute. This reason code can also occur when MQMF_SEGMENTATION_ALLOWED is specified, but the nature of the data present in the message prevents the queue manager splitting it into segments that are small enough for the queue-manager limit: For a user-defined format, the smallest segment that the queue manager can create is 16 bytes. For a built-in format, the smallest segment that the queue manager can create depends on the particular format, but is greater than 16 bytes in all cases other than MQFMT_STRING (for MQFMT_STRING the minimum segment size is 16 bytes). MQRC_MSG_TOO_BIG_FOR_Q_MGR can also occur in the Feedback field in the message descriptor of a report message; in this case it indicates that the error was encountered by a message channel agent when it attempted to put the message on a remote queue. This reason also occurs if a channel, through which the message is to pass, has restricted the maximum message length to a value that is actually less than that supported by the queue manager, and the message length is greater than this value. On z/OS, this return code is issued only if you are using CICS for distributed queuing. Otherwise, MQRC_MSG_TOO_BIG_FOR_CHANNEL is issued. Completion Code: MQCC_FAILED Programmer Response: Check whether the BufferLength parameter is specified correctly; if it is, do one of the following: Increase the value of the queue-manager's MaxMsgLength attribute; the queue's MaxMsgLength attribute may also need increasing. Break the message into several smaller messages. Specify MQMF_SEGMENTATION_ALLOWED in the MsgFlags field in MQMD; this will allow the queue manager to break the message into segments. Check the channel definitions. 2033 (X'07F1')MQRC_NO_MSG_AVAILABLE Explanation: An MQGET call was issued, but there is no message on the queue satisfying the selection criteria specified in MQMD (the MsgId and CorrelId fields), and in MQGMO (the Options and MatchOptions fields). Either the MQGMO_WAIT option was not specified, or the time interval specified by the WaitInterval field in MQGMO has expired. This reason is also returned for an MQGET call for browse, when the end of the queue has been reached. This reason code can also be returned by the mqGetBag and mqExecute calls. mqGetBag is similar to MQGET. For the mqExecute call, the completion code can be either MQCC_WARNING or MQCC_FAILED: If the completion code is MQCC_WARNING, some response messages were received during the specified wait interval, but not all. The response bag contains system-generated nested bags for the messages that were received. If the completion code is MQCC_FAILED, no response messages were received during the specified wait interval. Completion Code: MQCC_WARNING or MQCC_FAILED Programmer Response: If this is an expected condition, no corrective action is required. If this is an unexpected condition, check that: The message was put on the queue successfully. The unit of work (if any) used for the MQPUT or MQPUT1 call was committed successfully. The options controlling the selection criteria are specified correctly. All of the following can affect the eligibility of a message for return on the MQGET call: MQGMO_LOGICAL_ORDER MQGMO_ALL_MSGS_AVAILABLE MQGMO_ALL_SEGMENTS_AVAILABLE MQGMO_COMPLETE_MSG MQMO_MATCH_MSG_ID MQMO_MATCH_CORREL_ID MQMO_MATCH_GROUP_ID MQMO_MATCH_MSG_SEQ_NUMBER MQMO_MATCH_OFFSET Value of MsgId field in MQMD Value of CorrelId field in MQMD Consider waiting longer for the message. 2034 (X'07F2')MQRC_NO_MSG_UNDER_CURSOR Explanation: An MQGET call was issued with either the MQGMO_MSG_UNDER_CURSOR or the MQGMO_BROWSE_MSG_UNDER_CURSOR option. However, the browse cursor is not positioned at a retrievable message. This is caused by one of the following: The cursor is positioned logically before the first message (as it is before the first MQGET call with a browse option has been successfully performed). The message the browse cursor was positioned on has been locked or removed from the queue (probably by some other application) since the browse operation was performed. The message the browse cursor was positioned on has expired. Completion Code: MQCC_FAILED Programmer Response: Check the application logic. This may be an expected reason if the application design allows multiple servers to compete for messages after browsing. Consider also using the MQGMO_LOCK option with the preceding browse MQGET call. 2035 (X'07F3')MQRC_NOT_AUTHORIZED Explanation: The user is not authorized to perform the operation attempted: On an MQCONN or MQCONNX call, the user is not authorized to connect to the queue manager. On z/OS, for CICS applications, MQRC_CONNECTION_NOT_AUTHORIZED is issued instead. On an MQOPEN or MQPUT1 call, the user is not authorized to open the object for the option(s) specified. On z/OS, if the object being opened is a model queue, this reason also arises if the user is not authorized to create a dynamic queue with the required name. On an MQCLOSE call, the user is not authorized to delete the object, which is a permanent dynamic queue, and the Hobj parameter specified on the MQCLOSE call is not the handle returned by the MQOPEN call that created the queue. On a command, the user is not authorized to issue the command, or to access the object it specifies. This reason code can also occur in the Feedback field in the message descriptor of a report message; in this case it indicates that the error was encountered by a message channel agent when it attempted to put the message on a remote queue. Completion Code: MQCC_FAILED Programmer Response: Ensure that the correct queue manager or object was specified, and that appropriate authority exists. 2036 (X'07F4')MQRC_NOT_OPEN_FOR_BROWSE Explanation: An MQGET call was issued with one of the following options: MQGMO_BROWSE_FIRST MQGMO_BROWSE_NEXT MQGMO_BROWSE_MSG_UNDER_CURSOR MQGMO_MSG_UNDER_CURSOR but the queue had not been opened for browse. Completion Code: MQCC_FAILED Programmer Response: Specify MQOO_BROWSE when the queue is opened. 2037 (X'07F5')MQRC_NOT_OPEN_FOR_INPUT Explanation: An MQGET call was issued to retrieve a message from a queue, but the queue had not been opened for input. Completion Code: MQCC_FAILED Programmer Response: Specify one of the following when the queue is opened: MQOO_INPUT_SHARED MQOO_INPUT_EXCLUSIVE MQOO_INPUT_AS_Q_DEF 2038 (X'07F6')MQRC_NOT_OPEN_FOR_INQUIRE Explanation: An MQINQ call was issued to inquire object attributes, but the object had not been opened for inquire. Completion Code: MQCC_FAILED Programmer Response: Specify MQOO_INQUIRE when the object is opened. 2039 (X'07F7')MQRC_NOT_OPEN_FOR_OUTPUT Explanation: An MQPUT call was issued to put a message on a queue, but the queue had not been opened for output. Completion Code: MQCC_FAILED Programmer Response: Specify MQOO_OUTPUT when the queue is opened. 2040 (X'07F8')MQRC_NOT_OPEN_FOR_SET Explanation: An MQSET call was issued to set queue attributes, but the queue had not been opened for set. Completion Code: MQCC_FAILED Programmer Response: Specify MQOO_SET when the object is opened. 2041 (X'07F9')MQRC_OBJECT_CHANGED Explanation: Object definitions that affect this object have been changed since the Hobj handle used on this call was returned by the MQOPEN call. See the description of MQOPEN in the WebSphere MQ Application Programming Guide for more information. This reason does not occur if the object handle is specified in the Context field of the PutMsgOpts parameter on the MQPUT or MQPUT1 call. Completion Code: MQCC_FAILED Programmer Response: Issue an MQCLOSE call to return the handle to the system. It is then usually sufficient to reopen the object and retry the operation. However, if the object definitions are critical to the application logic, an MQINQ call can be used after reopening the object, to obtain the new values of the object attributes. 2042 (X'07FA')MQRC_OBJECT_IN_USE Explanation: An MQOPEN call was issued, but the object in question has already been opened by this or another application with options that conflict with those specified in the Options parameter. This arises if the request is for shared input, but the object is already open for exclusive input; it also arises if the request is for exclusive input, but the object is already open for input (of any sort). MCAs for receiver channels, or the intra-group queuing agent (IGQ agent), may keep the destination queues open even when messages are not being transmitted; this results in the queues appearing to be "in use". Use the MQSC command DISPLAY QSTATUS to find out who is keeping the queue open. On z/OS, this reason can also occur for an MQOPEN or MQPUT1 call, if the object to be opened (which can be a queue, or for MQOPEN a namelist or process object) is in the process of being deleted. Completion Code: MQCC_FAILED Programmer Response: System design should specify whether an application is to wait and retry, or take other action. 2043 (X'07FB')MQRC_OBJECT_TYPE_ERROR Explanation: On the MQOPEN or MQPUT1 call, the ObjectType field in the object descriptor MQOD specifies a value that is not valid. For the MQPUT1 call, the object type must be MQOT_Q. Completion Code: MQCC_FAILED Programmer Response: Specify a valid object type. 2044 (X'07FC')MQRC_OD_ERROR Explanation: On the MQOPEN or MQPUT1 call, the object descriptor MQOD is not valid, for one of the following reasons: The StrucId field is not MQOD_STRUC_ID. The Version field specifies a value that is not valid or not supported. The parameter pointer is not valid. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) The queue manager cannot copy the changed structure to application storage, even though the call is successful. This can occur, for example, if the pointer points to read-only storage. Completion Code: MQCC_FAILED Programmer Response: Ensure that input fields in the MQOD structure are set correctly. 2045 (X'07FD')MQRC_OPTION_NOT_VALID_FOR_TYPE Explanation: On an MQOPEN or MQCLOSE call, an option is specified that is not valid for the type of object or queue being opened or closed. For the MQOPEN call, this includes the following cases: An option that is inappropriate for the object type (for example, MQOO_OUTPUT for an MQOT_PROCESS object). An option that is unsupported for the queue type (for example, MQOO_INQUIRE for a remote queue that has no local definition). One or more of the following options: MQOO_INPUT_AS_Q_DEF MQOO_INPUT_SHARED MQOO_INPUT_EXCLUSIVE MQOO_BROWSE MQOO_INQUIRE MQOO_SET when either: the queue name is resolved through a cell directory, or ObjectQMgrName in the object descriptor specifies the name of a local definition of a remote queue (in order to specify a queue-manager alias), and the queue named in the RemoteQMgrName attribute of the definition is the name of the local queue manager. For the MQCLOSE call, this includes the following case: The MQCO_DELETE or MQCO_DELETE_PURGE option when the queue is not a dynamic queue. This reason code can also occur on the MQOPEN call when the object being opened is of type MQOT_NAMELIST, MQOT_PROCESS, or MQOT_Q_MGR, but the ObjectQMgrName field in MQOD is neither blank nor the name of the local queue manager. Completion Code: MQCC_FAILED Programmer Response: Specify the correct option. For the MQOPEN call, ensure that the ObjectQMgrName field is set correctly. For the MQCLOSE call, either correct the option or change the definition type of the model queue that is used to create the new queue. 2046 (X'07FE')MQRC_OPTIONS_ERROR Explanation: The Options parameter or field contains options that are not valid, or a combination of options that is not valid. For the MQOPEN, MQCLOSE, MQXCNVC, mqBagToBuffer, mqBufferToBag, mqCreateBag, and mqExecute calls, Options is a separate parameter on the call. This reason also occurs if the parameter pointer is not valid. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) For the MQBEGIN, MQCONNX, MQGET, MQPUT, and MQPUT1 calls, Options is a field in the relevant options structure (MQBO, MQCNO, MQGMO, or MQPMO). Completion Code: MQCC_FAILED Programmer Response: Specify valid options. Check the description of the Options parameter or field to determine which options and combinations of options are valid. If multiple options are being set by adding the individual options together, ensure that the same option is not added twice. 2047 (X'07FF')MQRC_PERSISTENCE_ERROR Explanation: On an MQPUT or MQPUT1 call, the value specified for the Persistence field in the message descriptor MQMD is not valid. Completion Code: MQCC_FAILED Programmer Response: Specify one of the following values: MQPER_PERSISTENT MQPER_NOT_PERSISTENT MQPER_PERSISTENCE_AS_Q_DEF 2048 (X'0800')MQRC_PERSISTENT_NOT_ALLOWED Explanation: On an MQPUT or MQPUT1 call, the value specified for the Persistence field in MQMD (or obtained from the DefPersistence queue attribute) specifies MQPER_PERSISTENT, but the queue on which the message is being placed does not support persistent messages. Persistent messages cannot be placed on temporary dynamic queues. This reason code can also occur in the Feedback field in the message descriptor of a report message; in this case it indicates that the error was encountered by a message channel agent when it attempted to put the message on a remote queue. Completion Code: MQCC_FAILED Programmer Response: Specify MQPER_NOT_PERSISTENT if the message is to be placed on a temporary dynamic queue. If persistence is required, use a permanent dynamic queue or predefined queue in place of a temporary dynamic queue. Be aware that server applications are recommended to send reply messages (message type MQMT_REPLY) with the same persistence as the original request message (message type MQMT_REQUEST). If the request message is persistent, the reply queue specified in the ReplyToQ field in the message descriptor MQMD cannot be a temporary dynamic queue. Use a permanent dynamic queue or predefined queue as the reply queue in this situation. 2049 (X'0801')MQRC_PRIORITY_EXCEEDS_MAXIMUM Explanation: An MQPUT or MQPUT1 call was issued, but the value of the Priority field in the message descriptor MQMD exceeds the maximum priority supported by the local queue manager, as shown by the MaxPriority queue-manager attribute. The message is accepted by the queue manager, but is placed on the queue at the queue manager's maximum priority. The Priority field in the message descriptor retains the value specified by the application that put the message. Completion Code: MQCC_WARNING Programmer Response: None required, unless this reason code was not expected by the application that put the message. 2050 (X'0802')MQRC_PRIORITY_ERROR Explanation: An MQPUT or MQPUT1 call was issued, but the value of the Priority field in the message descriptor MQMD is not valid. The maximum priority supported by the queue manager is given by the MaxPriority queue-manager attribute. Completion Code: MQCC_FAILED Programmer Response: Specify a value in the range zero through MaxPriority, or the special value MQPRI_PRIORITY_AS_Q_DEF. 2051 (X'0803')MQRC_PUT_INHIBITED Explanation: MQPUT and MQPUT1 calls are currently inhibited for the queue, or for the queue to which this queue resolves. This reason code can also occur in the Feedback field in the message descriptor of a report message; in this case it indicates that the error was encountered by a message channel agent when it attempted to put the message on a remote queue. Completion Code: MQCC_FAILED Programmer Response: If the system design allows put requests to be inhibited for short periods, retry the operation later. 2052 (X'0804')MQRC_Q_DELETED Explanation: An Hobj queue handle specified on a call refers to a dynamic queue that has been deleted since the queue was opened. (See the description of MQCLOSE in the WebSphere MQ Application Programming Guide for information about the deletion of dynamic queues.) On z/OS, this can also occur with the MQOPEN and MQPUT1 calls if a dynamic queue is being opened, but the queue is in a logically-deleted state. See MQCLOSE for more information about this. Completion Code: MQCC_FAILED Programmer Response: Issue an MQCLOSE call to return the handle and associated resources to the system (the MQCLOSE call will succeed in this case). Check the design of the application that caused the error. 2053 (X'0805')MQRC_Q_FULL Explanation: An MQPUT or MQPUT1 call, or a command, failed because the queue is full, that is, it already contains the maximum number of messages possible, as specified by the MaxQDepth queue attribute. This reason code can also occur in the Feedback field in the message descriptor of a report message; in this case it indicates that the error was encountered by a message channel agent when it attempted to put the message on a remote queue. Completion Code: MQCC_FAILED Programmer Response: Retry the operation later. Consider increasing the maximum depth for this queue, or arranging for more instances of the application to service the queue. 2055 (X'0807')MQRC_Q_NOT_EMPTY Explanation: An MQCLOSE call was issued for a permanent dynamic queue, but the call failed because the queue is not empty or still in use. One of the following applies: The MQCO_DELETE option was specified, but there are messages on the queue. The MQCO_DELETE or MQCO_DELETE_PURGE option was specified, but there are uncommitted get or put calls outstanding against the queue. See the usage notes pertaining to dynamic queues for the MQCLOSE call for more information. This reason code is also returned from a command to clear or delete or move a queue, if the queue contains uncommitted messages (or committed messages in the case of delete queue without the purge option). Completion Code: MQCC_FAILED Programmer Response: Check why there might be messages on the queue. Be aware that the CurrentQDepth queue attribute might be zero even though there are one or more messages on the queue; this can happen if the messages have been retrieved as part of a unit of work that has not yet been committed. If the messages can be discarded, try using the MQCLOSE call with the MQCO_DELETE_PURGE option. Consider retrying the call later. 2056 (X'0808')MQRC_Q_SPACE_NOT_AVAILABLE Explanation: An MQPUT or MQPUT1 call was issued, but there is no space available for the queue on disk or other storage device. This reason code can also occur in the Feedback field in the message descriptor of a report message; in this case it indicates that the error was encountered by a message channel agent when it attempted to put the message on a remote queue. On z/OS, this reason code does not occur. Completion Code: MQCC_FAILED Programmer Response: Check whether an application is putting messages in an infinite loop. If not, make more disk space available for the queue. 2057 (X'0809')MQRC_Q_TYPE_ERROR Explanation: One of the following occurred: On an MQOPEN call, the ObjectQMgrName field in the object descriptor MQOD or object record MQOR specifies the name of a local definition of a remote queue (in order to specify a queue-manager alias), and in that local definition the RemoteQMgrName attribute is the name of the local queue manager. However, the ObjectName field in MQOD or MQOR specifies the name of a model queue on the local queue manager; this is not allowed. See the WebSphere MQ Application Programming Guide for more information. On an MQPUT1 call, the object descriptor MQOD or object record MQOR specifies the name of a model queue. On a previous MQPUT or MQPUT1 call, the ReplyToQ field in the message descriptor specified the name of a model queue, but a model queue cannot be specified as the destination for reply or report messages. Only the name of a predefined queue, or the name of the dynamic queue created from the model queue, can be specified as the destination. In this situation the reason code MQRC_Q_TYPE_ERROR is returned in the Reason field of the MQDLH structure when the reply message or report message is placed on the dead-letter queue. Completion Code: MQCC_FAILED Programmer Response: Specify a valid queue. 2058 (X'080A')MQRC_Q_MGR_NAME_ERROR Explanation: On an MQCONN or MQCONNX call, the value specified for the QMgrName parameter is not valid or not known. This reason also occurs if the parameter pointer is not valid. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) On z/OS for CICS applications, this reason can occur on any call if the original connect specified an incorrect or unrecognized name. This reason code can also occur if an MQ client application attempts to connect to a queue manager within an MQ-client queue-manager group (see the QMgrName parameter of MQCONN), and either: Queue-manager groups are not supported. There is no queue-manager group with the specified name. Completion Code: MQCC_FAILED Programmer Response: Use an all-blank name if possible, or verify that the name used is valid. 2059 (X'080B')MQRC_Q_MGR_NOT_AVAILABLE Explanation: This occurs: On an MQCONN or MQCONNX call, the queue manager identified by the QMgrName parameter is not available for connection. On z/OS: For batch applications, this reason can be returned to applications running in LPARs that do not have a queue manager installed. For CICS applications, this reason can occur on any call if the original connect specified a queue manager whose name was recognized, but which is not available. On i5/OS, this reason can also be returned by the MQOPEN and MQPUT1 calls, when MQHC_DEF_HCONN is specified for the Hconn parameter by an application running in compatibility mode. On an MQCONN or MQCONNX call from an MQ client application: Attempting to connect to a queue manager within an MQ-client queue-manager group when none of the queue managers in the group is available for connection (see the QMgrName parameter of the MQCONN call). If there is an error with the client-connection or the corresponding server-connection channel definitions. On z/OS, if the optional OS/390 Client Attachment feature has not been installed. If a command uses the CommandScope parameter specfying a queue manager that is not active in the queue-sharing group. Completion Code: MQCC_FAILED Programmer Response: Ensure that the queue manager has been started. If the connection is from a client application, check the channel definitions. 2061 (X'080D')MQRC_REPORT_OPTIONS_ERROR Explanation: An MQPUT or MQPUT1 call was issued, but the Report field in the message descriptor MQMD contains one or more options that are not recognized by the local queue manager. The options that cause this reason code to be returned depend on the destination of the message; see the description of REPORT in the WebSphere MQ Application Programming Guide for more details. This reason code can also occur in the Feedback field in the MQMD of a report message, or in the Reason field in the MQDLH structure of a message on the dead-letter queue; in both cases it indicates that the destination queue manager does not support one or more of the report options specified by the sender of the message. Completion Code: MQCC_FAILED Programmer Response: Do the following: Ensure that the Report field in the message descriptor is initialized with a value when the message descriptor is declared, or is assigned a value prior to the MQPUT or MQPUT1 call. Specify MQRO_NONE if no report options are required. Ensure that the report options specified are valid; see the Report field described in the description of MQMD in the WebSphere MQ Application Programming Guide for valid report options. If multiple report options are being set by adding the individual report options together, ensure that the same report option is not added twice. Check that conflicting report options are not specified. For example, do not add both MQRO_EXCEPTION and MQRO_EXCEPTION_WITH_DATA to the Report field; only one of these can be specified. 2062 (X'080E')MQRC_SECOND_MARK_NOT_ALLOWED Explanation: An MQGET call was issued specifying the MQGMO_MARK_SKIP_BACKOUT option in the Options field of MQGMO, but a message has already been marked within the current unit of work. Only one marked message is allowed within each unit of work. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Modify the application so that no more than one message is marked within each unit of work. 2063 (X'080F')MQRC_SECURITY_ERROR Explanation: An MQCONN, MQCONNX, MQOPEN, MQPUT1, or MQCLOSE call was issued, but it failed because a security error occurred. On z/OS, the security error was returned by the External Security Manager. Completion Code: MQCC_FAILED Programmer Response: Note the error from the security manager, and contact your system programmer or security administrator. On i5/OS, the FFST log will contain the error information. 2065 (X'0811')MQRC_SELECTOR_COUNT_ERROR Explanation: On an MQINQ or MQSET call, the SelectorCount parameter specifies a value that is not valid. This reason also occurs if the parameter pointer is not valid. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) Completion Code: MQCC_FAILED Programmer Response: Specify a value in the range 0 through 256. 2066 (X'0812')MQRC_SELECTOR_LIMIT_EXCEEDED Explanation: On an MQINQ or MQSET call, the SelectorCount parameter specifies a value that is larger than the maximum supported (256). Completion Code: MQCC_FAILED Programmer Response: Reduce the number of selectors specified on the call; the valid range is 0 through 256. 2067 (X'0813')MQRC_SELECTOR_ERROR Explanation: An MQINQ or MQSET call was issued, but the Selectors array contains a selector that is not valid for one of the following reasons: The selector is not supported or out of range. The selector is not applicable to the type of object whose attributes are being inquired or set. The selector is for an attribute that cannot be set. This reason also occurs if the parameter pointer is not valid. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) Completion Code: MQCC_FAILED Programmer Response: Ensure that the value specified for the selector is valid for the object type represented by Hobj. For the MQSET call, also ensure that the selector represents an integer attribute that can be set. 2068 (X'0814')MQRC_SELECTOR_NOT_FOR_TYPE Explanation: On the MQINQ call, one or more selectors in the Selectors array is not applicable to the type of the queue whose attributes are being inquired. This reason also occurs when the queue is a cluster queue that resolved to a remote instance of the queue. In this case only a subset of the attributes that are valid for local queues can be inquired. See the usage notes in the description of MQINQ in the WebSphere MQ Application Programming Guide for further details. The call completes with MQCC_WARNING, with the attribute values for the inapplicable selectors set as follows: For integer attributes, the corresponding elements of IntAttrs are set to MQIAV_NOT_APPLICABLE. For character attributes, the appropriate parts of the CharAttrs string are set to a character string consisting entirely of asterisks (*). Completion Code: MQCC_WARNING Programmer Response: Verify that the selector specified is the one that was intended. If the queue is a cluster queue, specifying one of the MQOO_BROWSE, MQOO_INPUT_*, or MQOO_SET options in addition to MQOO_INQUIRE forces the queue to resolve to the local instance of the queue. However, if there is no local instance of the queue the MQOPEN call fails. 2069 (X'0815')MQRC_SIGNAL_OUTSTANDING Explanation: An MQGET call was issued with either the MQGMO_SET_SIGNAL or MQGMO_WAIT option, but there is already a signal outstanding for the queue handle Hobj. This reason code occurs only in the following environments: z/OS, Windows 95, Windows 98. Completion Code: MQCC_FAILED Programmer Response: Check the application logic. If it is necessary to set a signal or wait when there is a signal outstanding for the same queue, a different object handle must be used. 2070 (X'0816')MQRC_SIGNAL_REQUEST_ACCEPTED Explanation: An MQGET call was issued specifying MQGMO_SET_SIGNAL in the GetMsgOpts parameter, but no suitable message was available; the call returns immediately. The application can now wait for the signal to be delivered. On z/OS, the application should wait on the Event Control Block pointed to by the Signal1 field. On Windows 95, Windows 98, the application should wait for the signal Windows message to be delivered. This reason code occurs only in the following environments: z/OS, Windows 95, Windows 98. Completion Code: MQCC_WARNING Programmer Response: Wait for the signal; when it is delivered, check the signal to ensure that a message is now available. If it is, reissue the MQGET call. On z/OS, wait on the ECB pointed to by the Signal1 field and, when it is posted, check it to ensure that a message is now available. On Windows 95, Windows 98, the application (thread) should continue executing its message loop. 2071 (X'0817')MQRC_STORAGE_NOT_AVAILABLE Explanation: The call failed because there is insufficient main storage available. Completion Code: MQCC_FAILED Programmer Response: Ensure that active applications are behaving correctly, for example, that they are not looping unexpectedly. If no problems are found, make more main storage available. On z/OS, if no application problems are found, ask your system programmer to increase the size of the region in which the queue manager runs. 2072 (X'0818')MQRC_SYNCPOINT_NOT_AVAILABLE Explanation: Either MQGMO_SYNCPOINT was specified on an MQGET call or MQPMO_SYNCPOINT was specified on an MQPUT or MQPUT1 call, but the local queue manager was unable to honor the request. If the queue manager does not support units of work, the SyncPoint queue-manager attribute will have the value MQSP_NOT_AVAILABLE. This reason code can also occur on the MQGET, MQPUT, and MQPUT1 calls when an external unit-of-work coordinator is being used. If that coordinator requires an explicit call to start the unit of work, but the application has not issued that call prior to the MQGET, MQPUT, or MQPUT1 call, reason code MQRC_SYNCPOINT_NOT_AVAILABLE is returned. On i5/OS, this reason codes means that i5/OS Commitment Control is not started, or is unavailable for use by the queue manager. On z/OS, this reason code does not occur. Completion Code: MQCC_FAILED Programmer Response: Remove the specification of MQGMO_SYNCPOINT or MQPMO_SYNCPOINT, as appropriate. On i5/OS, ensure that Commitment Control has been started. If this reason code occurs after Commitment Control has been started, contact your system programmer. 2075 (X'081B')MQRC_TRIGGER_CONTROL_ERROR Explanation: On an MQSET call, the value specified for the MQIA_TRIGGER_CONTROL attribute selector is not valid. Completion Code: MQCC_FAILED Programmer Response: Specify a valid value. 2076 (X'081C')MQRC_TRIGGER_DEPTH_ERROR Explanation: On an MQSET call, the value specified for the MQIA_TRIGGER_DEPTH attribute selector is not valid. Completion Code: MQCC_FAILED Programmer Response: Specify a value that is greater than zero. 2077 (X'081D')MQRC_TRIGGER_MSG_PRIORITY_ERR Explanation: On an MQSET call, the value specified for the MQIA_TRIGGER_MSG_PRIORITY attribute selector is not valid. Completion Code: MQCC_FAILED Programmer Response: Specify a value in the range zero through the value of MaxPriority queue-manager attribute. 2078 (X'081E')MQRC_TRIGGER_TYPE_ERROR Explanation: On an MQSET call, the value specified for the MQIA_TRIGGER_TYPE attribute selector is not valid. Completion Code: MQCC_FAILED Programmer Response: Specify a valid value. 2079 (X'081F')MQRC_TRUNCATED_MSG_ACCEPTED Explanation: On an MQGET call, the message length was too large to fit into the supplied buffer. The MQGMO_ACCEPT_TRUNCATED_MSG option was specified, so the call completes. The message is removed from the queue (subject to unit-of-work considerations), or, if this was a browse operation, the browse cursor is advanced to this message. The DataLength parameter is set to the length of the message before truncation, the Buffer parameter contains as much of the message as fits, and the MQMD structure is filled in. Completion Code: MQCC_WARNING Programmer Response: None, because the application expected this situation. 2080 (X'0820')MQRC_TRUNCATED_MSG_FAILED Explanation: On an MQGET call, the message length was too large to fit into the supplied buffer. The MQGMO_ACCEPT_TRUNCATED_MSG option was not specified, so the message has not been removed from the queue. If this was a browse operation, the browse cursor remains where it was before this call, but if MQGMO_BROWSE_FIRST was specified, the browse cursor is positioned logically before the highest-priority message on the queue. The DataLength field is set to the length of the message before truncation, the Buffer parameter contains as much of the message as fits, and the MQMD structure is filled in. Completion Code: MQCC_WARNING Programmer Response: Supply a buffer that is at least as large as DataLength, or specify MQGMO_ACCEPT_TRUNCATED_MSG if not all of the message data is required. 2082 (X'0822')MQRC_UNKNOWN_ALIAS_BASE_Q Explanation: An MQOPEN or MQPUT1 call was issued specifying an alias queue as the target, but the BaseQName in the alias queue attributes is not recognized as a queue name. This reason code can also occur when BaseQName is the name of a cluster queue that cannot be resolved successfully. Completion Code: MQCC_FAILED Programmer Response: Correct the queue definitions. 2085 (X'0825')MQRC_UNKNOWN_OBJECT_NAME Explanation: An MQOPEN or MQPUT1 call was issued, but the object identified by the ObjectName and ObjectQMgrName fields in the object descriptor MQOD cannot be found. One of the following applies: The ObjectQMgrName field is one of the following: Blank The name of the local queue manager The name of a local definition of a remote queue (a queue-manager alias) in which the RemoteQMgrName attribute is the name of the local queue manager but no object with the specified ObjectName and ObjectType exists on the local queue manager. The object being opened is a cluster queue that is hosted on a remote queue manager, but the local queue manager does not have a defined route to the remote queue manager. The object being opened is a queue definition that has QSGDISP(GROUP). Such definitions cannot be used with the MQOPEN and MQPUT1 calls. This can also occur in response to a command that specifies the name of an object or other item that does not exist. Completion Code: MQCC_FAILED Programmer Response: Specify a valid object name. Ensure that the name is padded to the right with blanks if necessary. If this is correct, check the object definitions. 2086 (X'0826')MQRC_UNKNOWN_OBJECT_Q_MGR Explanation: On an MQOPEN or MQPUT1 call, the ObjectQMgrName field in the object descriptor MQOD does not satisfy the naming rules for objects. For more information, see the WebSphere MQ Application Programming Guide. This reason also occurs if the ObjectType field in the object descriptor has the value MQOT_Q_MGR, and the ObjectQMgrName field is not blank, but the name specified is not the name of the local queue manager. Completion Code: MQCC_FAILED Programmer Response: Specify a valid queue manager name. To refer to the local queue manager, a name consisting entirely of blanks or beginning with a null character can be used. Ensure that the name is padded to the right with blanks or terminated with a null character if necessary. 2087 (X'0827')MQRC_UNKNOWN_REMOTE_Q_MGR Explanation: On an MQOPEN or MQPUT1 call, an error occurred with the queue-name resolution, for one of the following reasons: ObjectQMgrName is blank or the name of the local queue manager, ObjectName is the name of a local definition of a remote queue (or an alias to one), and one of the following is true: RemoteQMgrName is blank or the name of the local queue manager. Note that this error occurs even if XmitQName is not blank. XmitQName is blank, but there is no transmission queue defined with the name of RemoteQMgrName, and the DefXmitQName queue-manager attribute is blank. RemoteQMgrName and RemoteQName specify a cluster queue that cannot be resolved successfully, and the DefXmitQName queue-manager attribute is blank. ObjectQMgrName is the name of a local definition of a remote queue (containing a queue-manager alias definition), and one of the following is true: RemoteQName is not blank. XmitQName is blank, but there is no transmission queue defined with the name of RemoteQMgrName, and the DefXmitQName queue-manager attribute is blank. ObjectQMgrName is not: Blank The name of the local queue manager The name of a transmission queue The name of a queue-manager alias definition (that is, a local definition of a remote queue with a blank RemoteQName) but the DefXmitQName queue-manager attribute is blank and the queue manager is not part of a queue-sharing group with intra-group queuing enabled. ObjectQMgrName is the name of a model queue. The queue name is resolved through a cell directory. However, there is no queue defined with the same name as the remote queue manager name obtained from the cell directory, and the DefXmitQName queue-manager attribute is blank. Completion Code: MQCC_FAILED Programmer Response: Check the values specified for ObjectQMgrName and ObjectName. If these are correct, check the queue definitions. 2090 (X'082A')MQRC_WAIT_INTERVAL_ERROR Explanation: On the MQGET call, the value specified for the WaitInterval field in the GetMsgOpts parameter is not valid. Completion Code: MQCC_FAILED Programmer Response: Specify a value greater than or equal to zero, or the special value MQWI_UNLIMITED if an indefinite wait is required. 2091 (X'082B')MQRC_XMIT_Q_TYPE_ERROR Explanation: On an MQOPEN or MQPUT1 call, a message is to be sent to a remote queue manager. The ObjectName or ObjectQMgrName field in the object descriptor specifies the name of a local definition of a remote queue but one of the following applies to the XmitQName attribute of the definition: XmitQName is not blank, but specifies a queue that is not a local queue XmitQName is blank, but RemoteQMgrName specifies a queue that is not a local queue This reason also occurs if the queue name is resolved through a cell directory, and the remote queue manager name obtained from the cell directory is the name of a queue, but this is not a local queue. Completion Code: MQCC_FAILED Programmer Response: Check the values specified for ObjectName and ObjectQMgrName. If these are correct, check the queue definitions. For more information on transmission queues, see the WebSphere MQ Application Programming Guide. 2092 (X'082C')MQRC_XMIT_Q_USAGE_ERROR Explanation: On an MQOPEN or MQPUT1 call, a message is to be sent to a remote queue manager, but one of the following occurred: ObjectQMgrName specifies the name of a local queue, but it does not have a Usage attribute of MQUS_TRANSMISSION. The ObjectName or ObjectQMgrName field in the object descriptor specifies the name of a local definition of a remote queue but one of the following applies to the XmitQName attribute of the definition: XmitQName is not blank, but specifies a queue that does not have a Usage attribute of MQUS_TRANSMISSION XmitQName is blank, but RemoteQMgrName specifies a queue that does not have a Usage attribute of MQUS_TRANSMISSION XmitQName specifies the queue SYSTEM.QSG.TRANSMIT.QUEUE but the IGQ queue manager attribute indicates that IGQ is DISABLED. The queue name is resolved through a cell directory, and the remote queue manager name obtained from the cell directory is the name of a local queue, but it does not have a Usage attribute of MQUS_TRANSMISSION. Completion Code: MQCC_FAILED Programmer Response: Check the values specified for ObjectName and ObjectQMgrName. If these are correct, check the queue definitions. For more information on transmission queues, see the WebSphere MQ Application Programming Guide. 2093 (X'082D')MQRC_NOT_OPEN_FOR_PASS_ALL Explanation: An MQPUT call was issued with the MQPMO_PASS_ALL_CONTEXT option specified in the PutMsgOpts parameter, but the queue had not been opened with the MQOO_PASS_ALL_CONTEXT option. Completion Code: MQCC_FAILED Programmer Response: Specify MQOO_PASS_ALL_CONTEXT (or another option that implies it) when the queue is opened. 2094 (X'082E')MQRC_NOT_OPEN_FOR_PASS_IDENT Explanation: An MQPUT call was issued with the MQPMO_PASS_IDENTITY_CONTEXT option specified in the PutMsgOpts parameter, but the queue had not been opened with the MQOO_PASS_IDENTITY_CONTEXT option. Completion Code: MQCC_FAILED Programmer Response: Specify MQOO_PASS_IDENTITY_CONTEXT (or another option that implies it) when the queue is opened. 2095 (X'082F')MQRC_NOT_OPEN_FOR_SET_ALL Explanation: An MQPUT call was issued with the MQPMO_SET_ALL_CONTEXT option specified in the PutMsgOpts parameter, but the queue had not been opened with the MQOO_SET_ALL_CONTEXT option. Completion Code: MQCC_FAILED Programmer Response: Specify MQOO_SET_ALL_CONTEXT when the queue is opened. 2096 (X'0830')MQRC_NOT_OPEN_FOR_SET_IDENT Explanation: An MQPUT call was issued with the MQPMO_SET_IDENTITY_CONTEXT option specified in the PutMsgOpts parameter, but the queue had not been opened with the MQOO_SET_IDENTITY_CONTEXT option. Completion Code: MQCC_FAILED Programmer Response: Specify MQOO_SET_IDENTITY_CONTEXT (or another option that implies it) when the queue is opened. 2097 (X'0831')MQRC_CONTEXT_HANDLE_ERROR Explanation: On an MQPUT or MQPUT1 call, MQPMO_PASS_IDENTITY_CONTEXT or MQPMO_PASS_ALL_CONTEXT was specified, but the handle specified in the Context field of the PutMsgOpts parameter is either not a valid queue handle, or it is a valid queue handle but the queue was not opened with MQOO_SAVE_ALL_CONTEXT. Completion Code: MQCC_FAILED Programmer Response: Specify MQOO_SAVE_ALL_CONTEXT when the queue referred to is opened. 2098 (X'0832')MQRC_CONTEXT_NOT_AVAILABLE Explanation: On an MQPUT or MQPUT1 call, MQPMO_PASS_IDENTITY_CONTEXT or MQPMO_PASS_ALL_CONTEXT was specified, but the queue handle specified in the Context field of the PutMsgOpts parameter has no context associated with it. This arises if no message has yet been successfully retrieved with the queue handle referred to, or if the last successful MQGET call was a browse. This condition does not arise if the message that was last retrieved had no context associated with it. On z/OS, if a message is received by a message channel agent that is putting messages with the authority of the user identifier in the message, this code is returned in the Feedback field of an exception report if the message has no context associated with it. Completion Code: MQCC_FAILED Programmer Response: Ensure that a successful nonbrowse get call has been issued with the queue handle referred to. 2099 (X'0833')MQRC_SIGNAL1_ERROR Explanation: An MQGET call was issued, specifying MQGMO_SET_SIGNAL in the GetMsgOpts parameter, but the Signal1 field is not valid. On z/OS, the address contained in the Signal1 field is not valid, or points to read-only storage. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) On Windows 95, Windows 98, the window handle in the Signal1 field is not valid. This reason code occurs only in the following environments: z/OS, Windows 95, Windows 98. Completion Code: MQCC_FAILED Programmer Response: Correct the setting of the Signal1 field. 2100 (X'0834')MQRC_OBJECT_ALREADY_EXISTS Explanation: An MQOPEN call was issued to create a dynamic queue, but a queue with the same name as the dynamic queue already exists. On z/OS, a rare "race condition" can also give rise to this reason code; see the description of reason code MQRC_NAME_IN_USE for more details. Completion Code: MQCC_FAILED Programmer Response: If supplying a dynamic queue name in full, ensure that it obeys the naming conventions for dynamic queues; if it does, either supply a different name, or delete the existing queue if it is no longer required. Alternatively, allow the queue manager to generate the name. If the queue manager is generating the name (either in part or in full), reissue the MQOPEN call. 2101 (X'0835')MQRC_OBJECT_DAMAGED Explanation: The object accessed by the call is damaged and cannot be used. For example, this may be because the definition of the object in main storage is not consistent, or because it differs from the definition of the object on disk, or because the definition on disk cannot be read. The object can be deleted, although it may not be possible to delete the associated user space. On z/OS, this reason occurs when the DB2 list header or structure number associated with a shared queue is zero. This situation arises as a result of using the MQSC command DELETE CFSTRUCT to delete the DB2 structure definition. The command resets the list header and structure number to zero for each of the shared queues that references the deleted CF strcture. Completion Code: MQCC_FAILED Programmer Response: It may be necessary to stop and restart the queue manager, or to restore the queue-manager data from back-up storage. On HP OpenVMS, OS/2, i5/OS, Compaq NonStop Kernel, and UNIX systems, consult the FFST(TM) record to obtain more detail about the problem. On z/OS, delete the shared queue and redefine it using the MQSC command DEFINE QLOCAL. This will automatically define a CF structure and allocate list headers for it. 2102 (X'0836')MQRC_RESOURCE_PROBLEM Explanation: There are insufficient system resources to complete the call successfully. Completion Code: MQCC_FAILED Programmer Response: Run the application when the machine is less heavily loaded. On z/OS, check the operator console for messages that may provide additional information. On HP OpenVMS, OS/2, i5/OS, Compaq NonStop Kernel, and UNIX systems, consult the FFST record to obtain more detail about the problem. 2103 (X'0837')MQRC_ANOTHER_Q_MGR_CONNECTED Explanation: An MQCONN or MQCONNX call was issued, but the thread or process is already connected to a different queue manager. The thread or process can connect to only one queue manager at a time. On z/OS, this reason code does not occur. On Windows, MTS objects do not receive this reason code, as connections to other queue managers are allowed. Completion Code: MQCC_FAILED Programmer Response: Use the MQDISC call to disconnect from the queue manager that is already connected, and then issue the MQCONN or MQCONNX call to connect to the new queue manager. Disconnecting from the existing queue manager will close any queues that are currently open; it is recommended that any uncommitted units of work should be committed or backed out before the MQDISC call is issued. 2104 (X'0838')MQRC_UNKNOWN_REPORT_OPTION Explanation: An MQPUT or MQPUT1 call was issued, but the Report field in the message descriptor MQMD contains one or more options that are not recognized by the local queue manager. The options are accepted. The options that cause this reason code to be returned depend on the destination of the message; see the description of REPORT in the WebSphere MQ Application Programming Guide for more details. Completion Code: MQCC_WARNING Programmer Response: If this reason code is expected, no corrective action is required. If this reason code is not expected, do the following: Ensure that the Report field in the message descriptor is initialized with a value when the message descriptor is declared, or is assigned a value prior to the MQPUT or MQPUT1 call. Ensure that the report options specified are valid; see the Report field described in the description of MQMD in the WebSphere MQ Application Programming Guide for valid report options. If multiple report options are being set by adding the individual report options together, ensure that the same report option is not added twice. Check that conflicting report options are not specified. For example, do not add both MQRO_EXCEPTION and MQRO_EXCEPTION_WITH_DATA to the Report field; only one of these can be specified. 2105 (X'0839')MQRC_STORAGE_CLASS_ERROR Explanation: The MQPUT or MQPUT1 call was issued, but the storage-class object defined for the queue does not exist. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Create the storage-class object required by the queue, or modify the queue definition to use an existing storage class. The name of the storage-class object used by the queue is given by the StorageClass queue attribute. 2106 (X'083A')MQRC_COD_NOT_VALID_FOR_XCF_Q Explanation: An MQPUT or MQPUT1 call was issued, but the Report field in the message descriptor MQMD specifies one of the MQRO_COD_* options and the target queue is an XCF queue. MQRO_COD_* options cannot be specified for XCF queues. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Remove the relevant MQRO_COD_* option. 2107 (X'083B')MQRC_XWAIT_CANCELED Explanation: An MQXWAIT call was issued, but the call has been canceled because a STOP CHINIT command has been issued (or the queue manager has been stopped, which causes the same effect). Refer to the WebSphere MQ Intercommunication book for details of the MQXWAIT call. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Tidy up and terminate. 2108 (X'083C')MQRC_XWAIT_ERROR Explanation: An MQXWAIT call was issued, but the invocation was not valid for one of the following reasons: The wait descriptor MQXWD contains data that is not valid. The linkage stack level is not valid. The addressing mode is not valid. There are too many wait events outstanding. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Obey the rules for using the MQXWAIT call. Refer to the WebSphere MQ Intercommunication book for details of this call. 2109 (X'083D')MQRC_SUPPRESSED_BY_EXIT Explanation: On any call other than MQCONN or MQDISC, the API crossing exit suppressed the call. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Obey the rules for MQI calls that the exit enforces. To find out the rules, see the writer of the exit. 2110 (X'083E')MQRC_FORMAT_ERROR Explanation: An MQGET call was issued with the MQGMO_CONVERT option specified in the GetMsgOpts parameter, but the message cannot be converted successfully due to an error associated with the message format. Possible errors include: The format name in the message is MQFMT_NONE. A user-written exit with the name specified by the Format field in the message cannot be found. The message contains data that is not consistent with the format definition. The message is returned unconverted to the application issuing the MQGET call, the values of the CodedCharSetId and Encoding fields in the MsgDesc parameter are set to those of the message returned, and the call completes with MQCC_WARNING. If the message consists of several parts, each of which is described by its own CodedCharSetId and Encoding fields (for example, a message with format name MQFMT_DEAD_LETTER_HEADER), some parts may be converted and other parts not converted. However, the values returned in the various CodedCharSetId and Encoding fields always correctly describe the relevant message data. Completion Code: MQCC_WARNING Programmer Response: Check the format name that was specified when the message was put. If this is not one of the built-in formats, check that a suitable exit with the same name as the format is available for the queue manager to load. Verify that the data in the message corresponds to the format expected by the exit. 2111 (X'083F')MQRC_SOURCE_CCSID_ERROR Explanation: The coded character-set identifier from which character data is to be converted is not valid or not supported. This can occur on the MQGET call when the MQGMO_CONVERT option is included in the GetMsgOpts parameter; the coded character-set identifier in error is the CodedCharSetId field in the message being retrieved. In this case, the message data is returned unconverted, the values of the CodedCharSetId and Encoding fields in the MsgDesc parameter are set to those of the message returned, and the call completes with MQCC_WARNING. This reason can also occur on the MQGET call when the message contains one or more MQ header structures (MQCIH, MQDLH, MQIIH, MQRMH), and the CodedCharSetId field in the message specifies a character set that does not have SBCS characters for the characters that are valid in queue names. MQ header structures containing such characters are not valid, and so the message is returned unconverted. The Unicode character set UCS-2 is an example of such a character set. If the message consists of several parts, each of which is described by its own CodedCharSetId and Encoding fields (for example, a message with format name MQFMT_DEAD_LETTER_HEADER), some parts may be converted and other parts not converted. However, the values returned in the various CodedCharSetId and Encoding fields always correctly describe the relevant message data. This reason can also occur on the MQXCNVC call; the coded character-set identifier in error is the SourceCCSID parameter. Either the SourceCCSID parameter specifies a value that is not valid or not supported, or the SourceCCSID parameter pointer is not valid. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) Completion Code: MQCC_WARNING or MQCC_FAILED Programmer Response: Check the character-set identifier that was specified when the message was put, or that was specified for the SourceCCSID parameter on the MQXCNVC call. If this is correct, check that it is one for which queue-manager conversion is supported. If queue-manager conversion is not supported for the specified character set, conversion must be carried out by the application. 2112 (X'0840')MQRC_SOURCE_INTEGER_ENC_ERROR Explanation: On an MQGET call, with the MQGMO_CONVERT option included in the GetMsgOpts parameter, the Encoding value in the message being retrieved specifies an integer encoding that is not recognized. The message data is returned unconverted, the values of the CodedCharSetId and Encoding fields in the MsgDesc parameter are set to those of the message returned, and the call completes with MQCC_WARNING. If the message consists of several parts, each of which is described by its own CodedCharSetId and Encoding fields (for example, a message with format name MQFMT_DEAD_LETTER_HEADER), some parts may be converted and other parts not converted. However, the values returned in the various CodedCharSetId and Encoding fields always correctly describe the relevant message data. This reason code can also occur on the MQXCNVC call, when the Options parameter contains an unsupported MQDCC_SOURCE_* value, or when MQDCC_SOURCE_ENC_UNDEFINED is specified for a UCS-2 code page. Completion Code: MQCC_WARNING or MQCC_FAILED Programmer Response: Check the integer encoding that was specified when the message was put. If this is correct, check that it is one for which queue-manager conversion is supported. If queue-manager conversion is not supported for the required integer encoding, conversion must be carried out by the application. 2113 (X'0841')MQRC_SOURCE_DECIMAL_ENC_ERROR Explanation: On an MQGET call with the MQGMO_CONVERT option included in the GetMsgOpts parameter, the Encoding value in the message being retrieved specifies a decimal encoding that is not recognized. The message data is returned unconverted, the values of the CodedCharSetId and Encoding fields in the MsgDesc parameter are set to those of the message returned, and the call completes with MQCC_WARNING. If the message consists of several parts, each of which is described by its own CodedCharSetId and Encoding fields (for example, a message with format name MQFMT_DEAD_LETTER_HEADER), some parts may be converted and other parts not converted. However, the values returned in the various CodedCharSetId and Encoding fields always correctly describe the relevant message data. Completion Code: MQCC_WARNING Programmer Response: Check the decimal encoding that was specified when the message was put. If this is correct, check that it is one for which queue-manager conversion is supported. If queue-manager conversion is not supported for the required decimal encoding, conversion must be carried out by the application. 2114 (X'0842')MQRC_SOURCE_FLOAT_ENC_ERROR Explanation: On an MQGET call, with the MQGMO_CONVERT option included in the GetMsgOpts parameter, the Encoding value in the message being retrieved specifies a floating-point encoding that is not recognized. The message data is returned unconverted, the values of the CodedCharSetId and Encoding fields in the MsgDesc parameter are set to those of the message returned, and the call completes with MQCC_WARNING. If the message consists of several parts, each of which is described by its own CodedCharSetId and Encoding fields (for example, a message with format name MQFMT_DEAD_LETTER_HEADER), some parts may be converted and other parts not converted. However, the values returned in the various CodedCharSetId and Encoding fields always correctly describe the relevant message data. Completion Code: MQCC_WARNING Programmer Response: Check the floating-point encoding that was specified when the message was put. If this is correct, check that it is one for which queue-manager conversion is supported. If queue-manager conversion is not supported for the required floating-point encoding, conversion must be carried out by the application. 2115 (X'0843')MQRC_TARGET_CCSID_ERROR Explanation: The coded character-set identifier to which character data is to be converted is not valid or not supported. This can occur on the MQGET call when the MQGMO_CONVERT option is included in the GetMsgOpts parameter; the coded character-set identifier in error is the CodedCharSetId field in the MsgDesc parameter. In this case, the message data is returned unconverted, the values of the CodedCharSetId and Encoding fields in the MsgDesc parameter are set to those of the message returned, and the call completes with MQCC_WARNING. This reason can also occur on the MQGET call when the message contains one or more MQ header structures (MQCIH, MQDLH, MQIIH, MQRMH), and the CodedCharSetId field in the MsgDesc parameter specifies a character set that does not have SBCS characters for the characters that are valid in queue names. The Unicode character set UCS-2 is an example of such a character set. This reason can also occur on the MQXCNVC call; the coded character-set identifier in error is the TargetCCSID parameter. Either the TargetCCSID parameter specifies a value that is not valid or not supported, or the TargetCCSID parameter pointer is not valid. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) Completion Code: MQCC_WARNING or MQCC_FAILED Programmer Response: Check the character-set identifier that was specified for the CodedCharSetId field in the MsgDesc parameter on the MQGET call, or that was specified for the SourceCCSID parameter on the MQXCNVC call. If this is correct, check that it is one for which queue-manager conversion is supported. If queue-manager conversion is not supported for the specified character set, conversion must be carried out by the application. 2116 (X'0844')MQRC_TARGET_INTEGER_ENC_ERROR Explanation: On an MQGET call with the MQGMO_CONVERT option included in the GetMsgOpts parameter, the Encoding value in the MsgDesc parameter specifies an integer encoding that is not recognized. The message data is returned unconverted, the values of the CodedCharSetId and Encoding fields in the MsgDesc parameter are set to those of the message being retrieved, and the call completes with MQCC_WARNING. This reason code can also occur on the MQXCNVC call, when the Options parameter contains an unsupported MQDCC_TARGET_* value, or when MQDCC_TARGET_ENC_UNDEFINED is specified for a UCS-2 code page. Completion Code: MQCC_WARNING or MQCC_FAILED Programmer Response: Check the integer encoding that was specified. If this is correct, check that it is one for which queue-manager conversion is supported. If queue-manager conversion is not supported for the required integer encoding, conversion must be carried out by the application. 2117 (X'0845')MQRC_TARGET_DECIMAL_ENC_ERROR Explanation: On an MQGET call with the MQGMO_CONVERT option included in the GetMsgOpts parameter, the Encoding value in the MsgDesc parameter specifies a decimal encoding that is not recognized. The message data is returned unconverted, the values of the CodedCharSetId and Encoding fields in the MsgDesc parameter are set to those of the message returned, and the call completes with MQCC_WARNING. Completion Code: MQCC_WARNING Programmer Response: Check the decimal encoding that was specified. If this is correct, check that it is one for which queue-manager conversion is supported. If queue-manager conversion is not supported for the required decimal encoding, conversion must be carried out by the application. 2118 (X'0846')MQRC_TARGET_FLOAT_ENC_ERROR Explanation: On an MQGET call with the MQGMO_CONVERT option included in the GetMsgOpts parameter, the Encoding value in the MsgDesc parameter specifies a floating-point encoding that is not recognized. The message data is returned unconverted, the values of the CodedCharSetId and Encoding fields in the MsgDesc parameter are set to those of the message returned, and the call completes with MQCC_WARNING. Completion Code: MQCC_WARNING Programmer Response: Check the floating-point encoding that was specified. If this is correct, check that it is one for which queue-manager conversion is supported. If queue-manager conversion is not supported for the required floating-point encoding, conversion must be carried out by the application. 2119 (X'0847')MQRC_NOT_CONVERTED Explanation: An MQGET call was issued with the MQGMO_CONVERT option specified in the GetMsgOpts parameter, but an error occurred during conversion of the data in the message. The message data is returned unconverted, the values of the CodedCharSetId and Encoding fields in the MsgDesc parameter are set to those of the message returned, and the call completes with MQCC_WARNING. If the message consists of several parts, each of which is described by its own CodedCharSetId and Encoding fields (for example, a message with format name MQFMT_DEAD_LETTER_HEADER), some parts may be converted and other parts not converted. However, the values returned in the various CodedCharSetId and Encoding fields always correctly describe the relevant message data. This error may also indicate that a parameter to the data-conversion service is not supported. Completion Code: MQCC_WARNING Programmer Response: Check that the message data is correctly described by the Format, CodedCharSetId and Encoding parameters that were specified when the message was put. Also check that these values, and the CodedCharSetId and Encoding specified in the MsgDesc parameter on the MQGET call, are supported for queue-manager conversion. If the required conversion is not supported, conversion must be carried out by the application. 2120 (X'0848')MQRC_CONVERTED_MSG_TOO_BIG Explanation: On an MQGET call with the MQGMO_CONVERT option included in the GetMsgOpts parameter, the message data expanded during data conversion and exceeded the size of the buffer provided by the application. However, the message had already been removed from the queue because prior to conversion the message data could be accommodated in the application buffer without truncation. The message is returned unconverted, with the CompCode parameter of the MQGET call set to MQCC_WARNING. If the message consists of several parts, each of which is described by its own character-set and encoding fields (for example, a message with format name MQFMT_DEAD_LETTER_HEADER), some parts may be converted and other parts not converted. However, the values returned in the various character-set and encoding fields always correctly describe the relevant message data. This reason can also occur on the MQXCNVC call, when the TargetBuffer parameter is too small too accommodate the converted string, and the string has been truncated to fit in the buffer. The length of valid data returned is given by the DataLength parameter; in the case of a DBCS string or mixed SBCS/DBCS string, this length may be less than the length of TargetBuffer. Completion Code: MQCC_WARNING Programmer Response: For the MQGET call, check that the exit is converting the message data correctly and setting the output length DataLength to the appropriate value. If it is, the application issuing the MQGET call must provide a larger buffer for the Buffer parameter. For the MQXCNVC call, if the string must be converted without truncation, provide a larger output buffer. 2121 (X'0849')MQRC_NO_EXTERNAL_PARTICIPANTS Explanation: An MQBEGIN call was issued to start a unit of work coordinated by the queue manager, but no participating resource managers have been registered with the queue manager. As a result, only changes to MQ resources can be coordinated by the queue manager in the unit of work. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows. Completion Code: MQCC_WARNING Programmer Response: If the application does not require non-MQ resources to participate in the unit of work, this reason code can be ignored or the MQBEGIN call removed. Otherwise consult your system programmer to determine why the required resource managers have not been registered with the queue manager; the queue manager's configuration file may be in error. 2122 (X'084A')MQRC_PARTICIPANT_NOT_AVAILABLE Explanation: An MQBEGIN call was issued to start a unit of work coordinated by the queue manager, but one or more of the participating resource managers that had been registered with the queue manager is not available. As a result, changes to those resources cannot be coordinated by the queue manager in the unit of work. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows. Completion Code: MQCC_WARNING Programmer Response: If the application does not require non-MQ resources to participate in the unit of work, this reason code can be ignored. Otherwise consult your system programmer to determine why the required resource managers are not available. The resource manager may have been halted temporarily, or there may be an error in the queue manager's configuration file. 2123 (X'084B')MQRC_OUTCOME_MIXED Explanation: The queue manager is acting as the unit-of-work coordinator for a unit of work that involves other resource managers, but one of the following occurred: An MQCMIT or MQDISC call was issued to commit the unit of work, but one or more of the participating resource managers backed-out the unit of work instead of committing it. As a result, the outcome of the unit of work is mixed. An MQBACK call was issued to back out a unit of work, but one or more of the participating resource managers had already committed the unit of work. This reason code occurs in the following environments: AIX, HP-UX, OS/2, Solaris, Windows. Completion Code: MQCC_FAILED Programmer Response: Examine the queue-manager error logs for messages relating to the mixed outcome; these messages identify the resource managers that are affected. Use procedures local to the affected resource managers to resynchronize the resources. This reason code does not prevent the application initiating further units of work. 2124 (X'084C')MQRC_OUTCOME_PENDING Explanation: The queue manager is acting as the unit-of-work coordinator for a unit of work that involves other resource managers, and an MQCMIT or MQDISC call was issued to commit the unit of work, but one or more of the participating resource managers has not confirmed that the unit of work was committed successfully. The completion of the commit operation will happen at some point in the future, but there remains the possibility that the outcome will be mixed. This reason code occurs in the following environments: AIX, HP-UX, OS/2, Solaris, Windows. Completion Code: MQCC_WARNING Programmer Response: Use the normal error-reporting mechanisms to determine whether the outcome was mixed. If it was, take appropriate action to resynchronize the resources. This reason code does not prevent the application initiating further units of work. 2125 (X'084D')MQRC_BRIDGE_STARTED Explanation: The IMS bridge has been started. Completion Code: MQCC_WARNING Programmer Response: None. This reason code is only used to identify the corresponding event message. 2126 (X'084E')MQRC_BRIDGE_STOPPED Explanation: The IMS bridge has been stopped. Completion Code: MQCC_WARNING Programmer Response: None. This reason code is only used to identify the corresponding event message. 2127 (X'084F')MQRC_ADAPTER_STORAGE_SHORTAGE Explanation: On an MQCONN call, the adapter was unable to acquire storage. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Notify the system programmer. The system programmer should determine why the system is short on storage, and take appropriate action, for example, increase the region size on the step or job card. 2128 (X'0850')MQRC_UOW_IN_PROGRESS Explanation: An MQBEGIN call was issued to start a unit of work coordinated by the queue manager, but a unit of work is already in existence for the connection handle specified. This may be a global unit of work started by a previous MQBEGIN call, or a unit of work that is local to the queue manager or one of the cooperating resource managers. No more than one unit of work can exist concurrently for a connection handle. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows. Completion Code: MQCC_FAILED Programmer Response: Review the application logic to determine why there is a unit of work already in existence. Move the MQBEGIN call to the appropriate place in the application. 2129 (X'0851')MQRC_ADAPTER_CONN_LOAD_ERROR Explanation: On an MQCONN call, the connection handling module (CSQBCON for batch and CSQQCONN for IMS) could not be loaded, so the adapter could not link to it. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Ensure that the correct library concatenation has been specified in the batch application program execution JCL, and in the queue-manager startup JCL. 2130 (X'0852')MQRC_ADAPTER_SERV_LOAD_ERROR Explanation: On an MQI call, the batch adapter could not load the API service module CSQBSRV, and so could not link to it. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Ensure that the correct library concatenation has been specified in the batch application program execution JCL, and in the queue-manager startup JCL. 2131 (X'0853')MQRC_ADAPTER_DEFS_ERROR Explanation: On an MQCONN call, the subsystem definition module (CSQBDEFV for batch and CSQQDEFV for IMS) does not contain the required control block identifier. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Check your library concatenation. If this is correct, check that the CSQBDEFV or CSQQDEFV module contains the required subsystem ID. 2132 (X'0854')MQRC_ADAPTER_DEFS_LOAD_ERROR Explanation: On an MQCONN call, the subsystem definition module (CSQBDEFV for batch and CSQQDEFV for IMS) could not be loaded. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Ensure that the correct library concatenation has been specified in the application program execution JCL, and in the queue-manager startup JCL. 2133 (X'0855')MQRC_ADAPTER_CONV_LOAD_ERROR Explanation: On an MQGET call, the adapter (batch or IMS) could not load the data conversion services modules. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Ensure that the correct library concatenation has been specified in the batch application program execution JCL, and in the queue-manager startup JCL. 2134 (X'0856')MQRC_BO_ERROR Explanation: On an MQBEGIN call, the begin-options structure MQBO is not valid, for one of the following reasons: The StrucId field is not MQBO_STRUC_ID. The Version field is not MQBO_VERSION_1. The parameter pointer is not valid. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) The queue manager cannot copy the changed structure to application storage, even though the call is successful. This can occur, for example, if the pointer points to read-only storage. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Ensure that input fields in the MQBO structure are set correctly. 2135 (X'0857')MQRC_DH_ERROR Explanation: An MQPUT or MQPUT1 call was issued, but the message data contains an MQDH structure that is not valid. Possible errors include the following: The StrucId field is not MQDH_STRUC_ID. The Version field is not MQDH_VERSION_1. The StrucLength field specifies a value that is too small to include the structure plus the arrays of MQOR and MQPMR records. The CodedCharSetId field is zero, or a negative value that is not valid. The BufferLength parameter of the call has a value that is too small to accommodate the structure (the structure extends beyond the end of the message). This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Check that the fields in the structure are set correctly. Ensure that the application sets the CodedCharSetId field to a valid value (note: MQCCSI_DEFAULT, MQCCSI_EMBEDDED, MQCCSI_Q_MGR, and MQCCSI_UNDEFINED are not valid in this field). 2136 (X'0858')MQRC_MULTIPLE_REASONS Explanation: An MQOPEN, MQPUT or MQPUT1 call was issued to open a distribution list or put a message to a distribution list, but the result of the call was not the same for all of the destinations in the list. One of the following applies: The call succeeded for some of the destinations but not others. The completion code is MQCC_WARNING in this case. The call failed for all of the destinations, but for differing reasons. The completion code is MQCC_FAILED in this case. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_WARNING or MQCC_FAILED Programmer Response: Examine the MQRR response records to identify the destinations for which the call failed, and the reason for the failure. Ensure that sufficient response records are provided by the application on the call to enable the error(s) to be determined. For the MQPUT1 call, the response records must be specified using the MQOD structure, and not the MQPMO structure. 2137 (X'0859')MQRC_OPEN_FAILED Explanation: A queue or other MQ object could not be opened successfully, for one of the following reasons: An MQCONN or MQCONNX call was issued, but the queue manager was unable to open an object that is used internally by the queue manager. As a result, processing cannot continue. The error log will contain the name of the object that could not be opened. An MQPUT call was issued to put a message to a distribution list, but the message could not be sent to the destination to which this reason code applies because that destination was not opened successfully by the MQOPEN call. This reason occurs only in the Reason field of the MQRR response record. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Do one of the following: If the error occurred on the MQCONN or MQCONNX call, ensure that the required objects exist by running the following command and then retrying the application: STRMQM -c qmgrwhere qmgr should be replaced by the name of the queue manager. If the error occurred on the MQPUT call, examine the MQRR response records specified on the MQOPEN call to determine the reason that the queue failed to open. Ensure that sufficient response records are provided by the application on the call to enable the error(s) to be determined. 2138 (X'085A')MQRC_ADAPTER_DISC_LOAD_ERROR Explanation: On an MQDISC call, the disconnect handling module (CSQBDSC for batch and CSQQDISC for IMS) could not be loaded, so the adapter could not link to it. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Ensure that the correct library concatenation has been specified in the application program execution JCL, and in the queue-manager startup JCL. Any uncommitted changes in a unit of work should be backed out. A unit of work that is coordinated by the queue manager is backed out automatically. 2139 (X'085B')MQRC_CNO_ERROR Explanation: On an MQCONNX call, the connect-options structure MQCNO is not valid, for one of the following reasons: The StrucId field is not MQCNO_STRUC_ID. The Version field specifies a value that is not valid or not supported. The parameter pointer is not valid. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) The queue manager cannot copy the changed structure to application storage, even though the call is successful. This can occur, for example, if the parameter pointer points to read-only storage. This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Ensure that input fields in the MQCNO structure are set correctly. 2140 (X'085C')MQRC_CICS_WAIT_FAILED Explanation: On any MQI call, the CICS adapter issued an EXEC CICS WAIT request, but the request was rejected by CICS. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Examine the CICS trace data for actual response codes. The most likely cause is that the task has been canceled by the operator or by the system. 2141 (X'085D')MQRC_DLH_ERROR Explanation: An MQPUT or MQPUT1 call was issued, but the message data contains an MQDLH structure that is not valid. Possible errors include the following: The StrucId field is not MQDLH_STRUC_ID. The Version field is not MQDLH_VERSION_1. The CodedCharSetId field is zero, or a negative value that is not valid. The BufferLength parameter of the call has a value that is too small to accommodate the structure (the structure extends beyond the end of the message). This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Check that the fields in the structure are set correctly. Ensure that the application sets the CodedCharSetId field to a valid value (note: MQCCSI_DEFAULT, MQCCSI_EMBEDDED, MQCCSI_Q_MGR, and MQCCSI_UNDEFINED are not valid in this field). 2142 (X'085E')MQRC_HEADER_ERROR Explanation: An MQPUT or MQPUT1 call was issued, but the message data contains an MQ header structure that is not valid. Possible errors include the following: The StrucId field is not valid. The Version field is not valid. The StrucLength field specifies a value that is too small. The CodedCharSetId field is zero, or a negative value that is not valid. The BufferLength parameter of the call has a value that is too small to accommodate the structure (the structure extends beyond the end of the message). This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Check that the fields in the structure are set correctly. Ensure that the application sets the CodedCharSetId field to a valid value (note: MQCCSI_DEFAULT, MQCCSI_EMBEDDED, MQCCSI_Q_MGR, and MQCCSI_UNDEFINED are not valid in this field). 2143 (X'085F')MQRC_SOURCE_LENGTH_ERROR Explanation: On the MQXCNVC call, the SourceLength parameter specifies a length that is less than zero or not consistent with the string's character set or content (for example, the character set is a double-byte character set, but the length is not a multiple of two). This reason also occurs if the SourceLength parameter pointer is not valid. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) This reason code can also occur on the MQGET call when the MQGMO_CONVERT option is specified. In this case it indicates that the MQRC_SOURCE_LENGTH_ERROR reason was returned by an MQXCNVC call issued by the data conversion exit. Completion Code: MQCC_WARNING or MQCC_FAILED Programmer Response: Specify a length that is zero or greater. If the reason code occurs on the MQGET call, check that the logic in the data-conversion exit is correct. 2144 (X'0860')MQRC_TARGET_LENGTH_ERROR Explanation: On the MQXCNVC call, the TargetLength parameter is not valid for one of the following reasons: TargetLength is less than zero. The TargetLength parameter pointer is not valid. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) The MQDCC_FILL_TARGET_BUFFER option is specified, but the value of TargetLength is such that the target buffer cannot be filled completely with valid characters. This can occur when TargetCCSID is a pure DBCS character set (such as UCS-2), but TargetLength specifies a length that is an odd number of bytes. This reason code can also occur on the MQGET call when the MQGMO_CONVERT option is specified. In this case it indicates that the MQRC_TARGET_LENGTH_ERROR reason was returned by an MQXCNVC call issued by the data conversion exit. Completion Code: MQCC_WARNING or MQCC_FAILED Programmer Response: Specify a length that is zero or greater. If the MQDCC_FILL_TARGET_BUFFER option is specified, and TargetCCSID is a pure DBCS character set, ensure that TargetLength specifies a length that is a multiple of two. If the reason code occurs on the MQGET call, check that the logic in the data-conversion exit is correct. 2145 (X'0861')MQRC_SOURCE_BUFFER_ERROR Explanation: On the MQXCNVC call, the SourceBuffer parameter pointer is not valid, or points to storage that cannot be accessed for the entire length specified by SourceLength. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) This reason code can also occur on the MQGET call when the MQGMO_CONVERT option is specified. In this case it indicates that the MQRC_SOURCE_BUFFER_ERROR reason was returned by an MQXCNVC call issued by the data conversion exit. Completion Code: MQCC_WARNING or MQCC_FAILED Programmer Response: Specify a valid buffer. If the reason code occurs on the MQGET call, check that the logic in the data-conversion exit is correct. 2146 (X'0862')MQRC_TARGET_BUFFER_ERROR Explanation: On the MQXCNVC call, the TargetBuffer parameter pointer is not valid, or points to read-only storage, or to storage that cannot be accessed for the entire length specified by TargetLength. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) This reason code can also occur on the MQGET call when the MQGMO_CONVERT option is specified. In this case it indicates that the MQRC_TARGET_BUFFER_ERROR reason was returned by an MQXCNVC call issued by the data conversion exit. Completion Code: MQCC_WARNING or MQCC_FAILED Programmer Response: Specify a valid buffer. If the reason code occurs on the MQGET call, check that the logic in the data-conversion exit is correct. 2148 (X'0864')MQRC_IIH_ERROR Explanation: An MQPUT or MQPUT1 call was issued, but the message data contains an MQIIH structure that is not valid. Possible errors include the following: The StrucId field is not MQIIH_STRUC_ID. The Version field is not MQIIH_VERSION_1. The StrucLength field is not MQIIH_LENGTH_1. The BufferLength parameter of the call has a value that is too small to accommodate the structure (the structure extends beyond the end of the message). This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Check that the fields in the structure are set correctly. 2149 (X'0865')MQRC_PCF_ERROR Explanation: An MQPUT or MQPUT1 call was issued to put a message containing PCF data, but the length of the message does not equal the sum of the lengths of the PCF structures present in the message. This can occur for messages with the following format names: MQFMT_ADMIN MQFMT_EVENT MQFMT_PCF This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Ensure that the length of the message specified on the MQPUT or MQPUT1 call equals the sum of the lengths of the PCF structures contained within the message data. 2150 (X'0866')MQRC_DBCS_ERROR Explanation: An error was encountered attempting to convert a double-byte character set (DBCS) string. This can occur in the following cases: On the MQXCNVC call, when the SourceCCSID parameter specifies the coded character-set identifier of a double-byte character set, but the SourceBuffer parameter does not contain a valid DBCS string. This may be because the string contains characters that are not valid DBCS characters, or because the string is a mixed SBCS/DBCS string and the shift-out/shift-in characters are not correctly paired. The completion code is MQCC_FAILED in this case. On the MQGET call, when the MQGMO_CONVERT option is specified. In this case it indicates that the MQRC_DBCS_ERROR reason code was returned by an MQXCNVC call issued by the data conversion exit. The completion code is MQCC_WARNING in this case. Completion Code: MQCC_WARNING or MQCC_FAILED Programmer Response: Specify a valid string. If the reason code occurs on the MQGET call, check that the data in the message is valid, and that the logic in the data-conversion exit is correct. 2152 (X'0868')MQRC_OBJECT_NAME_ERROR Explanation: An MQOPEN or MQPUT1 call was issued to open a distribution list (that is, the RecsPresent field in MQOD is greater than zero), but the ObjectName field is neither blank nor the null string. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: If it is intended to open a distribution list, set the ObjectName field to blanks or the null string. If it is not intended to open a distribution list, set the RecsPresent field to zero. 2153 (X'0869')MQRC_OBJECT_Q_MGR_NAME_ERROR Explanation: An MQOPEN or MQPUT1 call was issued to open a distribution list (that is, the RecsPresent field in MQOD is greater than zero), but the ObjectQMgrName field is neither blank nor the null string. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: If it is intended to open a distribution list, set the ObjectQMgrName field to blanks or the null string. If it is not intended to open a distribution list, set the RecsPresent field to zero. 2154 (X'086A')MQRC_RECS_PRESENT_ERROR Explanation: An MQOPEN or MQPUT1 call was issued, but the call failed for one of the following reasons: RecsPresent in MQOD is less than zero. ObjectType in MQOD is not MQOT_Q, and RecsPresent is not zero. RecsPresent must be zero if the object being opened is not a queue. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: If it is intended to open a distribution list, set the ObjectType field to MQOT_Q and RecsPresent to the number of destinations in the list. If it is not intended to open a distribution list, set the RecsPresent field to zero. 2155 (X'086B')MQRC_OBJECT_RECORDS_ERROR Explanation: An MQOPEN or MQPUT1 call was issued to open a distribution list (that is, the RecsPresent field in MQOD is greater than zero), but the MQOR object records are not specified correctly. One of the following applies: ObjectRecOffset is zero and ObjectRecPtr is zero or the null pointer. ObjectRecOffset is not zero and ObjectRecPtr is not zero and not the null pointer. ObjectRecPtr is not a valid pointer. ObjectRecPtr or ObjectRecOffset points to storage that is not accessible. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Ensure that one of ObjectRecOffset and ObjectRecPtr is zero and the other nonzero. Ensure that the field used points to accessible storage. 2156 (X'086C')MQRC_RESPONSE_RECORDS_ERROR Explanation: An MQOPEN or MQPUT1 call was issued to open a distribution list (that is, the RecsPresent field in MQOD is greater than zero), but the MQRR response records are not specified correctly. One of the following applies: ResponseRecOffset is not zero and ResponseRecPtr is not zero and not the null pointer. ResponseRecPtr is not a valid pointer. ResponseRecPtr or ResponseRecOffset points to storage that is not accessible. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Ensure that at least one of ResponseRecOffset and ResponseRecPtr is zero. Ensure that the field used points to accessible storage. 2157 (X'086D')MQRC_ASID_MISMATCH Explanation: On any MQI call, the caller's primary ASID was found to be different from the home ASID. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Correct the application (MQI calls cannot be issued in cross-memory mode). Any uncommitted changes in a unit of work should be backed out. A unit of work that is coordinated by the queue manager is backed out automatically. 2158 (X'086E')MQRC_PMO_RECORD_FLAGS_ERROR Explanation: An MQPUT or MQPUT1 call was issued to put a message, but the PutMsgRecFields field in the MQPMO structure is not valid, for one of the following reasons: The field contains flags that are not valid. The message is being put to a distribution list, and put message records have been provided (that is, RecsPresent is greater than zero, and one of PutMsgRecOffset or PutMsgRecPtr is nonzero), but PutMsgRecFields has the value MQPMRF_NONE. MQPMRF_ACCOUNTING_TOKEN is specified without either MQPMO_SET_IDENTITY_CONTEXT or MQPMO_SET_ALL_CONTEXT. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Ensure that PutMsgRecFields is set with the appropriate MQPMRF_* flags to indicate which fields are present in the put message records. If MQPMRF_ACCOUNTING_TOKEN is specified, ensure that either MQPMO_SET_IDENTITY_CONTEXT or MQPMO_SET_ALL_CONTEXT is also specified. Alternatively, set both PutMsgRecOffset and PutMsgRecPtr to zero. 2159 (X'086F')MQRC_PUT_MSG_RECORDS_ERROR Explanation: An MQPUT or MQPUT1 call was issued to put a message to a distribution list, but the MQPMR put message records are not specified correctly. One of the following applies: PutMsgRecOffset is not zero and PutMsgRecPtr is not zero and not the null pointer. PutMsgRecPtr is not a valid pointer. PutMsgRecPtr or PutMsgRecOffset points to storage that is not accessible. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Ensure that at least one of PutMsgRecOffset and PutMsgRecPtr is zero. Ensure that the field used points to accessible storage. 2160 (X'0870')MQRC_CONN_ID_IN_USE Explanation: On an MQCONN call, the connection identifier assigned by the queue manager to the connection between a CICS or IMS allied address space and the queue manager conflicts with the connection identifier of another connected CICS or IMS system. The connection identifier assigned is as follows: For CICS, the applid For IMS, the IMSID parameter on the IMSCTRL (sysgen) macro, or the IMSID parameter on the execution parameter (EXEC card in IMS control region JCL) For batch, the job name For TSO, the user ID A conflict arises only if there are two CICS systems, two IMS systems, or one each of CICS and IMS, having the same connection identifiers. Batch and TSO connections need not have unique identifiers. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Ensure that the naming conventions used in different systems that might connect to the queue manager do not conflict. 2161 (X'0871')MQRC_Q_MGR_QUIESCING Explanation: An MQI call was issued, but the call failed because the queue manager is quiescing (preparing to shut down). When the queue manager is quiescing, the MQOPEN, MQPUT, MQPUT1, and MQGET calls can still complete successfully, but the application can request that they fail by specifying the appropriate option on the call: MQOO_FAIL_IF_QUIESCING on MQOPEN MQPMO_FAIL_IF_QUIESCING on MQPUT or MQPUT1 MQGMO_FAIL_IF_QUIESCING on MQGET Specifying these options enables the application to become aware that the queue manager is preparing to shut down. On z/OS: For batch applications, this reason can be returned to applications running in LPARs that do not have a queue manager installed. For CICS applications, this reason can be returned when no connection was established. On i5/OS for applications running in compatibility mode, this reason can be returned when no connection was established. Completion Code: MQCC_FAILED Programmer Response: The application should tidy up and end. If the application specified the MQOO_FAIL_IF_QUIESCING, MQPMO_FAIL_IF_QUIESCING, or MQGMO_FAIL_IF_QUIESCING option on the failing call, the relevant option can be removed and the call reissued. By omitting these options, the application can continue working in order to complete and commit the current unit of work, but the application should not start a new unit of work. 2162 (X'0872')MQRC_Q_MGR_STOPPING Explanation: An MQI call was issued, but the call failed because the queue manager is shutting down. If the call was an MQGET call with the MQGMO_WAIT option, the wait has been canceled. No more MQI calls can be issued. For MQ client applications, it is possible that the call did complete successfully, even though this reason code is returned with a CompCode of MQCC_FAILED. On z/OS, the MQRC_CONNECTION_BROKEN reason may be returned instead if, as a result of system scheduling factors, the queue manager shuts down before the call completes. Completion Code: MQCC_FAILED Programmer Response: The application should tidy up and end. If the application is in the middle of a unit of work coordinated by an external unit-of-work coordinator, the application should issue the appropriate call to back out the unit of work. Any unit of work that is coordinated by the queue manager is backed out automatically. 2163 (X'0873')MQRC_DUPLICATE_RECOV_COORD Explanation: On an MQCONN or MQCONNX call, a recovery coordinator already exists for the connection name specified on the connection call issued by the adapter. A conflict arises only if there are two CICS systems, two IMS systems, or one each of CICS and IMS, having the same connection identifiers. Batch and TSO connections need not have unique identifiers. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Ensure that the naming conventions used in different systems that might connect to the queue manager do not conflict. 2173 (X'087D')MQRC_PMO_ERROR Explanation: On an MQPUT or MQPUT1 call, the MQPMO structure is not valid, for one of the following reasons: The StrucId field is not MQPMO_STRUC_ID. The Version field specifies a value that is not valid or not supported. The parameter pointer is not valid. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) The queue manager cannot copy the changed structure to application storage, even though the call is successful. This can occur, for example, if the pointer points to read-only storage. Completion Code: MQCC_FAILED Programmer Response: Ensure that input fields in the MQPMO structure are set correctly. 2183 (X'0887')MQRC_API_EXIT_LOAD_ERROR Explanation: The API crossing exit module could not be linked. If this reason is returned when the API crossing exit is invoked after the call has been executed, the call itself may have executed correctly. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Ensure that the correct library concatenation has been specified, and that the API crossing exit module is executable and correctly named. Any uncommitted changes in a unit of work should be backed out. A unit of work that is coordinated by the queue manager is backed out automatically. 2184 (X'0888')MQRC_REMOTE_Q_NAME_ERROR Explanation: On an MQOPEN or MQPUT1 call, one of the following occurred: A local definition of a remote queue (or an alias to one) was specified, but the RemoteQName attribute in the remote queue definition is entirely blank. Note that this error occurs even if the XmitQName in the definition is not blank. The ObjectQMgrName field in the object descriptor is not blank and not the name of the local queue manager, but the ObjectName field is blank. Completion Code: MQCC_FAILED Programmer Response: Alter the local definition of the remote queue and supply a valid remote queue name, or supply a nonblank ObjectName in the object descriptor, as appropriate. 2185 (X'0889')MQRC_INCONSISTENT_PERSISTENCE Explanation: An MQPUT call was issued to put a message in a group or a segment of a logical message, but the value specified or defaulted for the Persistence field in MQMD is not consistent with the current group and segment information retained by the queue manager for the queue handle. All messages in a group and all segments in a logical message must have the same value for persistence, that is, all must be persistent, or all must be nonpersistent. If the current call specifies MQPMO_LOGICAL_ORDER, the call fails. If the current call does not specify MQPMO_LOGICAL_ORDER, but the previous MQPUT call for the queue handle did, the call succeeds with completion code MQCC_WARNING. This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_WARNING or MQCC_FAILED Programmer Response: Modify the application to ensure that the same value of persistence is used for all messages in the group, or all segments of the logical message. 2186 (X'088A')MQRC_GMO_ERROR Explanation: On an MQGET call, the MQGMO structure is not valid, for one of the following reasons: The StrucId field is not MQGMO_STRUC_ID. The Version field specifies a value that is not valid or not supported. The parameter pointer is not valid. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) The queue manager cannot copy the changed structure to application storage, even though the call is successful. This can occur, for example, if the pointer points to read-only storage. Completion Code: MQCC_FAILED Programmer Response: Ensure that input fields in the MQGMO structure are set correctly. 2187 (X'088B')MQRC_CICS_BRIDGE_RESTRICTION Explanation: It is not permitted to issue MQI calls from user transactions that are run in an MQ/CICS-bridge environment where the bridge exit also issues MQI calls. The MQI call fails. If this occurs in the bridge exit, it will result in a transaction abend. If it occurs in the user transaction, this may result in a transaction abend. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: The transaction cannot be run using the MQ/CICS bridge. Refer to the appropriate CICS manual for information about restrictions in the MQ/CICS bridge environment. 2188 (X'088C')MQRC_STOPPED_BY_CLUSTER_EXIT Explanation: An MQOPEN, MQPUT, or MQPUT1 call was issued to open or put a message on a cluster queue, but the cluster workload exit rejected the call. This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Check the cluster workload exit to ensure that it has been written correctly. Determine why it rejected the call and correct the problem. 2189 (X'088D')MQRC_CLUSTER_RESOLUTION_ERROR Explanation: An MQOPEN, MQPUT, or MQPUT1 call was issued to open or put a message on a cluster queue, but the queue definition could not be resolved correctly because a response was required from the repository manager but none was available. This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Check that the repository manager is operating and that the queue and channel definitions are correct. 2190 (X'088E')MQRC_CONVERTED_STRING_TOO_BIG Explanation: On an MQGET call with the MQGMO_CONVERT option included in the GetMsgOpts parameter, a string in a fixed-length field in the message expanded during data conversion and exceeded the size of the field. When this happens, the queue manager tries discarding trailing blank characters and characters following the first null character in order to make the string fit, but in this case there were insufficient characters that could be discarded. This reason code can also occur for messages with a format name of MQFMT_IMS_VAR_STRING. When this happens, it indicates that the IMS variable string expanded such that its length exceeded the capacity of the 2-byte binary length field contained within the structure of the IMS variable string. (The queue manager never discards trailing blanks in an IMS variable string.) The message is returned unconverted, with the CompCode parameter of the MQGET call set to MQCC_WARNING. If the message consists of several parts, each of which is described by its own character-set and encoding fields (for example, a message with format name MQFMT_DEAD_LETTER_HEADER), some parts may be converted and other parts not converted. However, the values returned in the various character-set and encoding fields always correctly describe the relevant message data. This reason code does not occur if the string could be made to fit by discarding trailing blank characters. Completion Code: MQCC_WARNING Programmer Response: Check that the fields in the message contain the correct values, and that the character-set identifiers specified by the sender and receiver of the message are correct. If they are, the layout of the data in the message must be modified to increase the lengths of the field(s) so that there is sufficient space to allow the string(s) to expand when converted. 2191 (X'088F')MQRC_TMC_ERROR Explanation: An MQPUT or MQPUT1 call was issued, but the message data contains an MQTMC2 structure that is not valid. Possible errors include the following: The StrucId field is not MQTMC_STRUC_ID. The Version field is not MQTMC_VERSION_2. The BufferLength parameter of the call has a value that is too small to accommodate the structure (the structure extends beyond the end of the message). This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Check that the fields in the structure are set correctly. 2192 (X'0890')MQRC_PAGESET_FULL Explanation: Former name for MQRC_STORAGE_MEDIUM_FULL. 2192 (X'0890')MQRC_STORAGE_MEDIUM_FULL Explanation: An MQI call or command was issued to operate on an object, but the call failed because the external storage medium is full. One of the following applies: A page-set data set is full (nonshared queues only). A coupling-facility structure is full (shared queues only). This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Check which queues contain messages and look for applications that might be filling the queues unintentionally. Be aware that the queue that has caused the page set or coupling-facility structure to become full is not necessarily the queue referenced by the MQI call that returned MQRC_STORAGE_MEDIUM_FULL. Check that all of the usual server applications are operating correctly and processing the messages on the queues. If the applications and servers are operating correctly, increase the number of server applications to cope with the message load, or request the system programmer to increase the size of the page-set data sets. 2193 (X'0891')MQRC_PAGESET_ERROR Explanation: An error was encountered with the page set while attempting to access it for a locally defined queue. This could be because the queue is on a page set that does not exist. A console message is issued that tells you the number of the page set in error. For example if the error occurred in the TEST job, and your user identifier is ABCDEFG, the message is: CSQI041I CSQIALLC JOB TEST USER ABCDEFG HAD ERROR ACCESSING PAGE SET 27If this reason code occurs while attempting to delete a dynamic queue with MQCLOSE, the dynamic queue has not been deleted. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Check that the storage class for the queue maps to a valid page set using the DISPLAY Q(xx) STGCLASS, DISPLAY STGCLASS(xx), and DISPLAY USAGE PSID commands. If you are unable to resolve the problem, notify the system programmer who should: Collect the following diagnostic information: A description of the actions that led to the error A listing of the application program being run at the time of the error Details of the page sets defined for use by the queue manager Attempt to re-create the problem, and take a system dump immediately after the error occurs Contact your IBM Support Center 2194 (X'0892')MQRC_NAME_NOT_VALID_FOR_TYPE Explanation: An MQOPEN call was issued to open the queue manager definition, but the ObjectName field in the ObjDesc parameter is not blank. Completion Code: MQCC_FAILED Programmer Response: Ensure that the ObjectName field is set to blanks. 2195 (X'0893')MQRC_UNEXPECTED_ERROR Explanation: The call was rejected because an unexpected error occurred. Completion Code: MQCC_FAILED Programmer Response: Check the application's parameter list to ensure, for example, that the correct number of parameters was passed, and that data pointers and storage keys are valid. If the problem cannot be resolved, contact your system programmer. On z/OS, check whether any information has been displayed on the console. If this error occurs on an MQCONN or MQCONNX call, check that the subsystem named is an active MQ subsystem. In particular, check that it is not a DB2(TM) subsystem. If the problem cannot be resolved, rerun the application with a CSQSNAP DD card (if you have not already got a dump) and send the resulting dump to IBM. On OS/2 and i5/OS, consult the FFST record to obtain more detail about the problem. On HP OpenVMS, Compaq NonStop Kernel, and UNIX systems, consult the FDC file to obtain more detail about the problem. 2196 (X'0894')MQRC_UNKNOWN_XMIT_Q Explanation: On an MQOPEN or MQPUT1 call, a message is to be sent to a remote queue manager. The ObjectName or the ObjectQMgrName in the object descriptor specifies the name of a local definition of a remote queue (in the latter case queue-manager aliasing is being used), but the XmitQName attribute of the definition is not blank and not the name of a locally-defined queue. Completion Code: MQCC_FAILED Programmer Response: Check the values specified for ObjectName and ObjectQMgrName. If these are correct, check the queue definitions. For more information on transmission queues, see the WebSphere MQ Application Programming Guide. 2197 (X'0895')MQRC_UNKNOWN_DEF_XMIT_Q Explanation: An MQOPEN or MQPUT1 call was issued specifying a remote queue as the destination. If a local definition of the remote queue was specified, or if a queue-manager alias is being resolved, the XmitQName attribute in the local definition is blank. Because there is no queue defined with the same name as the destination queue manager, the queue manager has attempted to use the default transmission queue. However, the name defined by the DefXmitQName queue-manager attribute is not the name of a locally-defined queue. Completion Code: MQCC_FAILED Programmer Response: Correct the queue definitions, or the queue-manager attribute. See the WebSphere MQ Application Programming Guide for more information. 2198 (X'0896')MQRC_DEF_XMIT_Q_TYPE_ERROR Explanation: An MQOPEN or MQPUT1 call was issued specifying a remote queue as the destination. Either a local definition of the remote queue was specified, or a queue-manager alias was being resolved, but in either case the XmitQName attribute in the local definition is blank. Because there is no transmission queue defined with the same name as the destination queue manager, the local queue manager has attempted to use the default transmission queue. However, although there is a queue defined by the DefXmitQName queue-manager attribute, it is not a local queue. Completion Code: MQCC_FAILED Programmer Response: Do one of the following: Specify a local transmission queue as the value of the XmitQName attribute in the local definition of the remote queue. Define a local transmission queue with a name that is the same as that of the remote queue manager. Specify a local transmission queue as the value of the DefXmitQName queue-manager attribute. See the WebSphere MQ Application Programming Guide for more information. 2199 (X'0897')MQRC_DEF_XMIT_Q_USAGE_ERROR Explanation: An MQOPEN or MQPUT1 call was issued specifying a remote queue as the destination. Either a local definition of the remote queue was specified, or a queue-manager alias was being resolved, but in either case the XmitQName attribute in the local definition is blank. Because there is no transmission queue defined with the same name as the destination queue manager, the local queue manager has attempted to use the default transmission queue. However, the queue defined by the DefXmitQName queue-manager attribute does not have a Usage attribute of MQUS_TRANSMISSION. Completion Code: MQCC_FAILED Programmer Response: Do one of the following: Specify a local transmission queue as the value of the XmitQName attribute in the local definition of the remote queue. Define a local transmission queue with a name that is the same as that of the remote queue manager. Specify a different local transmission queue as the value of the DefXmitQName queue-manager attribute. Change the Usage attribute of the DefXmitQName queue to MQUS_TRANSMISSION. See the WebSphere MQ Application Programming Guide for more information. 2201 (X'0899')MQRC_NAME_IN_USE Explanation: An MQOPEN call was issued to create a dynamic queue, but a queue with the same name as the dynamic queue already exists. The existing queue is one that is logically deleted, but for which there are still one or more open handles. For more information, see the description of MQCLOSE in the WebSphere MQ Application Programming Guide. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Either ensure that all handles for the previous dynamic queue are closed, or ensure that the name of the new queue is unique; see the description for reason code MQRC_OBJECT_ALREADY_EXISTS. 2202 (X'089A')MQRC_CONNECTION_QUIESCING Explanation: This reason code is issued when the connection to the queue manager is in quiescing state, and an application issues one of the following calls: MQCONN or MQCONNX MQOPEN, with no connection established, or with MQOO_FAIL_IF_QUIESCING included in the Options parameter MQGET, with MQGMO_FAIL_IF_QUIESCING included in the Options field of the GetMsgOpts parameter MQPUT or MQPUT1, with MQPMO_FAIL_IF_QUIESCING included in the Options field of the PutMsgOpts parameter MQRC_CONNECTION_QUIESCING is also issued by the message channel agent (MCA) when the queue manager is in quiescing state. Completion Code: MQCC_FAILED Programmer Response: The application should tidy up and terminate. Any uncommitted changes in a unit of work should be backed out. 2203 (X'089B')MQRC_CONNECTION_STOPPING Explanation: This reason code is issued when the connection to the queue manager is shutting down, and the application issues an MQI call. No more message-queuing calls can be issued. For the MQGET call, if the MQGMO_WAIT option was specified, the wait is canceled. Note that the MQRC_CONNECTION_BROKEN reason may be returned instead if, as a result of system scheduling factors, the queue manager shuts down before the call completes. MQRC_CONNECTION_STOPPING is also issued by the message channel agent (MCA) when the queue manager is shutting down. For MQ client applications, it is possible that the call did complete successfully, even though this reason code is returned with a CompCode of MQCC_FAILED. Completion Code: MQCC_FAILED Programmer Response: The application should tidy up and terminate. Any uncommitted changes in a unit of work should be backed out. A unit of work that is coordinated by the queue manager is backed out automatically. 2204 (X'089C')MQRC_ADAPTER_NOT_AVAILABLE Explanation: This is issued only for CICS applications, if any call is issued and the CICS adapter (a Task Related User Exit) has been disabled, or has not been enabled. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: The application should tidy up and terminate. Any uncommitted changes in a unit of work should be backed out. A unit of work that is coordinated by the queue manager is backed out automatically. 2206 (X'089E')MQRC_MSG_ID_ERROR Explanation: An MQGET call was issued to retrieve a message using the message identifier as a selection criterion, but the call failed because selection by message identifier is not supported on this queue. On z/OS, the queue is a shared queue, but the IndexType queue attribute does not have an appropriate value: If selection is by message identifier alone, IndexType must have the value MQIT_MSG_ID. If selection is by message identifier and correlation identifier combined, IndexType must have the value MQIT_MSG_ID or MQIT_CORREL_ID. On Compaq NonStop Kernel, a key file is required but has not been defined. Completion Code: MQCC_FAILED Programmer Response: Do one of the following: Modify the application so that it does not use selection by message identifier: set the MsgId field to MQMI_NONE and do not specify MQMO_MATCH_MSG_ID in MQGMO. On z/OS, change the IndexType queue attribute to MQIT_MSG_ID. On Compaq NonStop Kernel, define a key file. 2207 (X'089F')MQRC_CORREL_ID_ERROR Explanation: An MQGET call was issued to retrieve a message using the correlation identifier as a selection criterion, but the call failed because selection by correlation identifier is not supported on this queue. On z/OS, the queue is a shared queue, but the IndexType queue attribute does not have an appropriate value: If selection is by correlation identifier alone, IndexType must have the value MQIT_CORREL_ID. If selection is by correlation identifier and message identifier combined, IndexType must have the value MQIT_CORREL_ID or MQIT_MSG_ID. On Compaq NonStop Kernel, a key file is required but has not been defined. Completion Code: MQCC_FAILED Programmer Response: Do one of the following: On z/OS, change the IndexType queue attribute to MQIT_CORREL_ID. On Compaq NonStop Kernel, define a key file. Modify the application so that it does not use selection by correlation identifier: set the CorrelId field to MQCI_NONE and do not specify MQMO_MATCH_CORREL_ID in MQGMO. 2208 (X'08A0')MQRC_FILE_SYSTEM_ERROR Explanation: An unexpected return code was received from the file system, in attempting to perform an operation on a queue. This reason code occurs only on VSE/ESA. Completion Code: MQCC_FAILED Programmer Response: Check the file system definition for the queue that was being accessed. For a VSAM file, check that the control interval is large enough for the maximum message length allowed for the queue. 2209 (X'08A1')MQRC_NO_MSG_LOCKED Explanation: An MQGET call was issued with the MQGMO_UNLOCK option, but no message was currently locked. Completion Code: MQCC_WARNING Programmer Response: Check that a message was locked by an earlier MQGET call with the MQGMO_LOCK option for the same handle, and that no intervening call has caused the message to become unlocked. 2210 (X'08A2')MQRC_SOAP_DOTNET_ERROR Explanation: An exception from the .NET environment (as opposed to WebSphere MQ .NET) has been received and is included as an inner exception. Completion Code: MQCC_FAILED Programmer Response: Refer to the .NET documentation for details about the inner exception. Follow the corrective action recommended there. 2211 (X'08A3')MQRC_SOAP_AXIS_ERROR Explanation: An exception from the Axis environment has been received and is included as a chained exception. Completion Code: MQCC_FAILED Programmer Response: Refer to the Axis documentation for details about the chained exception. Follow the corrective action recommended there. 2212 (X'08A4')MQRC_SOAP_URL_ERROR Explanation: The SOAP URL has been specified incorrectly. Completion Code: MQCC_FAILED Programmer Response: Correct the SOAP URL and rerun. 2217 (X'08A9')MQRC_CONNECTION_NOT_AUTHORIZED Explanation: This reason code arises only for CICS applications. For these, connection to the queue manager is done by the adapter. If that connection fails because the CICS subsystem is not authorized to connect to the queue manager, this reason code is issued whenever an application running under that subsystem subsequently issues an MQI call. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Ensure that the subsystem is authorized to connect to the queue manager. 2218 (X'08AA')MQRC_MSG_TOO_BIG_FOR_CHANNEL Explanation: A message was put to a remote queue, but the message is larger than the maximum message length allowed by the channel. This reason code is returned in the Feedback field in the message descriptor of a report message. On z/OS, this return code is issued only if you are not using CICS for distributed queuing. Otherwise, MQRC_MSG_TOO_BIG_FOR_Q_MGR is issued. Completion Code: MQCC_FAILED Programmer Response: Check the channel definitions. Increase the maximum message length that the channel can accept, or break the message into several smaller messages. 2219 (X'08AB')MQRC_CALL_IN_PROGRESS Explanation: The application issued an MQI call whilst another MQI call was already being processed for that connection. Only one call per application connection can be processed at a time. Concurrent calls can arise when an application uses multiple threads, or when an exit is invoked as part of the processing of an MQI call. For example, a data-conversion exit invoked as part of the processing of the MQGET call may try to issue an MQI call. On z/OS, concurrent calls can arise only with batch or IMS applications; an example is when a subtask ends while an MQI call is in progress (for example, an MQGET that is waiting), and there is an end-of-task exit routine that issues another MQI call. On OS/2 and Windows, concurrent calls can also arise if an MQI call is issued in response to a user message while another MQI call is in progress. If the application is using multiple threads with shared handles, MQRC_CALL_IN_PROGRESS occurs when the handle specified on the call is already in use by another thread and MQCNO_HANDLE_SHARE_NO_BLOCK was specified on the MQCONNX call. Completion Code: MQCC_FAILED Programmer Response: Ensure that an MQI call cannot be issued while another one is active. Do not issue MQI calls from within a data-conversion exit. On z/OS, if you want to provide a subtask to allow an application that is waiting for a message to arrive to be canceled, wait for the message by using MQGET with MQGMO_SET_SIGNAL, rather than MQGMO_WAIT. 2220 (X'08AC')MQRC_RMH_ERROR Explanation: An MQPUT or MQPUT1 call was issued, but the message data contains an MQRMH structure that is not valid. Possible errors include the following: The StrucId field is not MQRMH_STRUC_ID. The Version field is not MQRMH_VERSION_1. The StrucLength field specifies a value that is too small to include the structure plus the variable-length data at the end of the structure. The CodedCharSetId field is zero, or a negative value that is not valid. The BufferLength parameter of the call has a value that is too small to accommodate the structure (the structure extends beyond the end of the message). This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Check that the fields in the structure are set correctly. Ensure that the application sets the CodedCharSetId field to a valid value (note: MQCCSI_DEFAULT, MQCCSI_EMBEDDED, MQCCSI_Q_MGR, and MQCCSI_UNDEFINED are not valid in this field). 2222 (X'08AE')MQRC_Q_MGR_ACTIVE Explanation: This condition is detected when a queue manager becomes active. On z/OS, this event is not generated for the first start of a queue manager, only on subsequent restarts. Completion Code: MQCC_WARNING Programmer Response: None. This reason code is only used to identify the corresponding event message. 2223 (X'08AF')MQRC_Q_MGR_NOT_ACTIVE Explanation: This condition is detected when a queue manager is requested to stop or quiesce. Completion Code: MQCC_WARNING Programmer Response: None. This reason code is only used to identify the corresponding event message. 2224 (X'08B0')MQRC_Q_DEPTH_HIGH Explanation: An MQPUT or MQPUT1 call has caused the queue depth to be incremented to or above the limit specified in the QDepthHighLimit attribute. Completion Code: MQCC_WARNING Programmer Response: None. This reason code is only used to identify the corresponding event message. 2225 (X'08B1')MQRC_Q_DEPTH_LOW Explanation: An MQGET call has caused the queue depth to be decremented to or below the limit specified in the QDepthLowLimit attribute. Completion Code: MQCC_WARNING Programmer Response: None. This reason code is only used to identify the corresponding event message. 2226 (X'08B2')MQRC_Q_SERVICE_INTERVAL_HIGH Explanation: No successful gets or puts have been detected within an interval that is greater than the limit specified in the QServiceInterval attribute. Completion Code: MQCC_WARNING Programmer Response: None. This reason code is only used to identify the corresponding event message. 2227 (X'08B3')MQRC_Q_SERVICE_INTERVAL_OK Explanation: A successful get has been detected within an interval that is less than or equal to the limit specified in the QServiceInterval attribute. Completion Code: MQCC_WARNING Programmer Response: None. This reason code is only used to identify the corresponding event message. 2228 (X'08B4')MQRC_RFH_HEADER_FIELD_ERROR Explanation: An expected RFH header field was not found or had an invalid value. If this error occurs in a WebSphere MQ SOAP listener, the missing or erroneous field is either the contentType field or the transportVersion field or both. Completion Code: MQCC_FAILED Programmer Response: If this error occurs in a WebSphere MQ SOAP listener, and you are using the IBM-supplied sender, contact your IBM Support Center. If you are using a bespoke sender, check the associated error message, and that the RFH2 section of the SOAP/MQ request message contains all the mandatory fields, and that these fields have valid values. 2229 (X'08B5')MQRC_RAS_PROPERTY_ERROR Explanation: There is an error related to the RAS property file. The file may be missing, it may be not accessible, or the commands in the file may be incorrect. Completion Code: MQCC_FAILED Programmer Response: Look at the associated error message, which will explain the error in detail. Correct the error and retry. 2232 (X'08B8')MQRC_UNIT_OF_WORK_NOT_STARTED Explanation: An MQGET, MQPUT or MQPUT1 call was issued to get or put a message within a unit of work, but no TM/MP transaction had been started. If MQGMO_NO_SYNCPOINT is not specified on MQGET, or MQPMO_NO_SYNCPOINT is not specified on MQPUT or MQPUT1 (the default), the call requires a unit of work. Completion Code: MQCC_FAILED Programmer Response: Ensure a TM/MP transaction is available, or issue the MQGET call with the MQGMO_NO_SYNCPOINT option, or the MQPUT or MQPUT1 call with the MQPMO_NO_SYNCPOINT option, which will cause a transaction to be started automatically. 2233 (X'08B9')MQRC_CHANNEL_AUTO_DEF_OK Explanation: This condition is detected when the automatic definition of a channel is successful. The channel is defined by the MCA. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_WARNING Programmer Response: None. This reason code is only used to identify the corresponding event message. 2234 (X'08BA')MQRC_CHANNEL_AUTO_DEF_ERROR Explanation: This condition is detected when the automatic definition of a channel fails; this may be because an error occurred during the definition process, or because the channel automatic-definition exit inhibited the definition. Additional information is returned in the event message indicating the reason for the failure. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_WARNING Programmer Response: Examine the additional information returned in the event message to determine the reason for the failure. 2235 (X'08BB')MQRC_CFH_ERROR Explanation: An MQPUT or MQPUT1 call was issued, but the message data contains an MQCFH structure that is not valid. This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Check that the fields in the structure are set correctly. 2236 (X'08BC')MQRC_CFIL_ERROR Explanation: An MQPUT or MQPUT1 call was issued, but the message data contains an MQCFIL or MQCFIL64 structure that is not valid. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Check that the fields in the structure are set correctly. 2237 (X'08BD')MQRC_CFIN_ERROR Explanation: An MQPUT or MQPUT1 call was issued, but the message data contains an MQCFIN or MQCFIN64 structure that is not valid. This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Check that the fields in the structure are set correctly. 2238 (X'08BE')MQRC_CFSL_ERROR Explanation: An MQPUT or MQPUT1 call was issued, but the message data contains an MQCFSL structure that is not valid. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Check that the fields in the structure are set correctly. 2239 (X'08BF')MQRC_CFST_ERROR Explanation: An MQPUT or MQPUT1 call was issued, but the message data contains an MQCFST structure that is not valid. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Check that the fields in the structure are set correctly. 2241 (X'08C1')MQRC_INCOMPLETE_GROUP Explanation: An operation was attempted on a queue using a queue handle that had an incomplete message group. This reason code can arise in the following situations: On the MQPUT call, when the application specifies MQPMO_LOGICAL_ORDER and attempts to put a message that is not in a group. The completion code is MQCC_FAILED in this case. On the MQPUT call, when the application does not specify MQPMO_LOGICAL_ORDER, but the previous MQPUT call for the queue handle did specify MQPMO_LOGICAL_ORDER. The completion code is MQCC_WARNING in this case. On the MQGET call, when the application does not specify MQGMO_LOGICAL_ORDER, but the previous MQGET call for the queue handle did specify MQGMO_LOGICAL_ORDER. The completion code is MQCC_WARNING in this case. On the MQCLOSE call, when the application attempts to close the queue that has the incomplete message group. The completion code is MQCC_WARNING in this case. If there is an incomplete logical message as well as an incomplete message group, reason code MQRC_INCOMPLETE_MSG is returned in preference to MQRC_INCOMPLETE_GROUP. This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_WARNING or MQCC_FAILED Programmer Response: If this reason code is expected, no corrective action is required. Otherwise, ensure that the MQPUT call for the last message in the group specifies MQMF_LAST_MSG_IN_GROUP. 2242 (X'08C2')MQRC_INCOMPLETE_MSG Explanation: An operation was attempted on a queue using a queue handle that had an incomplete logical message. This reason code can arise in the following situations: On the MQPUT call, when the application specifies MQPMO_LOGICAL_ORDER and attempts to put a message that is not a segment, or that has a setting for the MQMF_LAST_MSG_IN_GROUP flag that is different from the previous message. The completion code is MQCC_FAILED in this case. On the MQPUT call, when the application does not specify MQPMO_LOGICAL_ORDER, but the previous MQPUT call for the queue handle did specify MQPMO_LOGICAL_ORDER. The completion code is MQCC_WARNING in this case. On the MQGET call, when the application does not specify MQGMO_LOGICAL_ORDER, but the previous MQGET call for the queue handle did specify MQGMO_LOGICAL_ORDER. The completion code is MQCC_WARNING in this case. On the MQCLOSE call, when the application attempts to close the queue that has the incomplete logical message. The completion code is MQCC_WARNING in this case. This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_WARNING or MQCC_FAILED Programmer Response: If this reason code is expected, no corrective action is required. Otherwise, ensure that the MQPUT call for the last segment specifies MQMF_LAST_SEGMENT. 2243 (X'08C3')MQRC_INCONSISTENT_CCSIDS Explanation: An MQGET call was issued specifying the MQGMO_COMPLETE_MSG option, but the message to be retrieved consists of two or more segments that have differing values for the CodedCharSetId field in MQMD. This can arise when the segments take different paths through the network, and some of those paths have MCA sender conversion enabled. The call succeeds with a completion code of MQCC_WARNING, but only the first few segments that have identical character-set identifiers are returned. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_WARNING Programmer Response: Remove the MQGMO_COMPLETE_MSG option from the MQGET call and retrieve the remaining message segments one by one. 2244 (X'08C4')MQRC_INCONSISTENT_ENCODINGS Explanation: An MQGET call was issued specifying the MQGMO_COMPLETE_MSG option, but the message to be retrieved consists of two or more segments that have differing values for the Encoding field in MQMD. This can arise when the segments take different paths through the network, and some of those paths have MCA sender conversion enabled. The call succeeds with a completion code of MQCC_WARNING, but only the first few segments that have identical encodings are returned. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_WARNING Programmer Response: Remove the MQGMO_COMPLETE_MSG option from the MQGET call and retrieve the remaining message segments one by one. 2245 (X'08C5')MQRC_INCONSISTENT_UOW Explanation: One of the following applies: An MQPUT call was issued to put a message in a group or a segment of a logical message, but the value specified or defaulted for the MQPMO_SYNCPOINT option is not consistent with the current group and segment information retained by the queue manager for the queue handle. If the current call specifies MQPMO_LOGICAL_ORDER, the call fails. If the current call does not specify MQPMO_LOGICAL_ORDER, but the previous MQPUT call for the queue handle did, the call succeeds with completion code MQCC_WARNING. An MQGET call was issued to remove from the queue a message in a group or a segment of a logical message, but the value specified or defaulted for the MQGMO_SYNCPOINT option is not consistent with the current group and segment information retained by the queue manager for the queue handle. If the current call specifies MQGMO_LOGICAL_ORDER, the call fails. If the current call does not specify MQGMO_LOGICAL_ORDER, but the previous MQGET call for the queue handle did, the call succeeds with completion code MQCC_WARNING. This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_WARNING or MQCC_FAILED Programmer Response: Modify the application to ensure that the same unit-of-work specification is used for all messages in the group, or all segments of the logical message. 2246 (X'08C6')MQRC_INVALID_MSG_UNDER_CURSOR Explanation: An MQGET call was issued specifying the MQGMO_COMPLETE_MSG option with either MQGMO_MSG_UNDER_CURSOR or MQGMO_BROWSE_MSG_UNDER_CURSOR, but the message that is under the cursor has an MQMD with an Offset field that is greater than zero. Because MQGMO_COMPLETE_MSG was specified, the message is not valid for retrieval. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Reposition the browse cursor so that it is located on a message whose Offset field in MQMD is zero. Alternatively, remove the MQGMO_COMPLETE_MSG option. 2247 (X'08C7')MQRC_MATCH_OPTIONS_ERROR Explanation: An MQGET call was issued, but the value of the MatchOptions field in the GetMsgOpts parameter is not valid, for one of the following reasons: An undefined option is specified. All of the following are true: MQGMO_LOGICAL_ORDER is specified. There is a current message group or logical message for the queue handle. Neither MQGMO_BROWSE_MSG_UNDER_CURSOR nor MQGMO_MSG_UNDER_CURSOR is specified. One or more of the MQMO_* options is specified. The values of the fields in the MsgDesc parameter corresponding to the MQMO_* options specified, differ from the values of those fields in the MQMD for the message to be returned next. On z/OS, one or more of the options specified is not valid for the index type of the queue. This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Ensure that only valid options are specified for the field. 2248 (X'08C8')MQRC_MDE_ERROR Explanation: An MQPUT or MQPUT1 call was issued, but the message data contains an MQMDE structure that is not valid. Possible errors include the following: The StrucId field is not MQMDE_STRUC_ID. The Version field is not MQMDE_VERSION_2. The StrucLength field is not MQMDE_LENGTH_2. The CodedCharSetId field is zero, or a negative value that is not valid. The BufferLength parameter of the call has a value that is too small to accommodate the structure (the structure extends beyond the end of the message). This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Check that the fields in the structure are set correctly. Ensure that the application sets the CodedCharSetId field to a valid value (note: MQCCSI_DEFAULT, MQCCSI_EMBEDDED, MQCCSI_Q_MGR, and MQCCSI_UNDEFINED are not valid in this field). 2249 (X'08C9')MQRC_MSG_FLAGS_ERROR Explanation: An MQPUT or MQPUT1 call was issued, but the MsgFlags field in the message descriptor MQMD contains one or more message flags that are not recognized by the local queue manager. The message flags that cause this reason code to be returned depend on the destination of the message; see the description of REPORT in the WebSphere MQ Application Programming Guide for more details. This reason code can also occur in the Feedback field in the MQMD of a report message, or in the Reason field in the MQDLH structure of a message on the dead-letter queue; in both cases it indicates that the destination queue manager does not support one or more of the message flags specified by the sender of the message. This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Do the following: Ensure that the MsgFlags field in the message descriptor is initialized with a value when the message descriptor is declared, or is assigned a value prior to the MQPUT or MQPUT1 call. Specify MQMF_NONE if no message flags are needed. Ensure that the message flags specified are valid; see the MsgFlags field described in the description of MQMD in the WebSphere MQ Application Programming Guide for valid message flags. If multiple message flags are being set by adding the individual message flags together, ensure that the same message flag is not added twice. On z/OS, ensure that the message flags specified are valid for the index type of the queue; see the description of the MsgFlags field in MQMD for further details. 2250 (X'08CA')MQRC_MSG_SEQ_NUMBER_ERROR Explanation: An MQGET, MQPUT, or MQPUT1 call was issued, but the value of the MsgSeqNumber field in the MQMD or MQMDE structure is less than one or greater than 999 999 999. This error can also occur on the MQPUT call if the MsgSeqNumber field would have become greater than 999 999 999 as a result of the call. This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Specify a value in the range 1 through 999 999 999. Do not attempt to create a message group containing more than 999 999 999 messages. 2251 (X'08CB')MQRC_OFFSET_ERROR Explanation: An MQPUT or MQPUT1 call was issued, but the value of the Offset field in the MQMD or MQMDE structure is less than zero or greater than 999 999 999. This error can also occur on the MQPUT call if the Offset field would have become greater than 999 999 999 as a result of the call. This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Specify a value in the range 0 through 999 999 999. Do not attempt to create a message segment that would extend beyond an offset of 999 999 999. 2252 (X'08CC')MQRC_ORIGINAL_LENGTH_ERROR Explanation: An MQPUT or MQPUT1 call was issued to put a report message that is a segment, but the OriginalLength field in the MQMD or MQMDE structure is either: Less than the length of data in the message, or Less than one (for a segment that is not the last segment), or Less than zero (for a segment that is the last segment) This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Specify a value that is greater than zero. Zero is valid only for the last segment. 2253 (X'08CD')MQRC_SEGMENT_LENGTH_ZERO Explanation: An MQPUT or MQPUT1 call was issued to put the first or an intermediate segment of a logical message, but the length of the application message data in the segment (excluding any MQ headers that may be present) is zero. The length must be at least one for the first or intermediate segment. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Check the application logic to ensure that segments are put with a length of one or greater. Only the last segment of a logical message is permitted to have a length of zero. 2255 (X'08CF')MQRC_UOW_NOT_AVAILABLE Explanation: An MQGET, MQPUT, or MQPUT1 call was issued to get or put a message outside a unit of work, but the options specified on the call required the queue manager to process the call within a unit of work. Because there is already a user-defined unit of work in existence, the queue manager was unable to create a temporary unit of work for the duration of the call. This reason occurs in the following circumstances: On an MQGET call, when the MQGMO_COMPLETE_MSG option is specified in MQGMO and the logical message to be retrieved is persistent and consists of two or more segments. On an MQPUT or MQPUT1 call, when the MQMF_SEGMENTATION_ALLOWED flag is specified in MQMD and the message requires segmentation. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Issue the MQGET, MQPUT, or MQPUT1 call inside the user-defined unit of work. Alternatively, for the MQPUT or MQPUT1 call, reduce the size of the message so that it does not require segmentation by the queue manager. 2256 (X'08D0')MQRC_WRONG_GMO_VERSION Explanation: An MQGET call was issued specifying options that required an MQGMO with a version number not less than MQGMO_VERSION_2, but the MQGMO supplied did not satisfy this condition. This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Modify the application to pass a version-2 MQGMO. Check the application logic to ensure that the Version field in MQGMO has been set to MQGMO_VERSION_2. Alternatively, remove the option that requires the version-2 MQGMO. 2257 (X'08D1')MQRC_WRONG_MD_VERSION Explanation: An MQGET, MQPUT, or MQPUT1 call was issued specifying options that required an MQMD with a version number not less than MQMD_VERSION_2, but the MQMD supplied did not satisfy this condition. This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Modify the application to pass a version-2 MQMD. Check the application logic to ensure that the Version field in MQMD has been set to MQMD_VERSION_2. Alternatively, remove the option that requires the version-2 MQMD. 2258 (X'08D2')MQRC_GROUP_ID_ERROR Explanation: An MQPUT or MQPUT1 call was issued to put a distribution-list message that is also a message in a group, a message segment, or has segmentation allowed, but an invalid combination of options and values was specified. All of the following are true: MQPMO_LOGICAL_ORDER is not specified in the Options field in MQPMO. Either there are too few MQPMR records provided by MQPMO, or the GroupId field is not present in the MQPMR records. One or more of the following flags is specified in the MsgFlags field in MQMD or MQMDE: MQMF_SEGMENTATION_ALLOWED MQMF_*_MSG_IN_GROUP MQMF_*_SEGMENT The GroupId field in MQMD or MQMDE is not MQGI_NONE. This combination of options and values would result in the same group identifier being used for all of the destinations in the distribution list; this is not permitted by the queue manager. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Specify MQGI_NONE for the GroupId field in MQMD or MQMDE. Alternatively, if the call is MQPUT specify MQPMO_LOGICAL_ORDER in the Options field in MQPMO. 2259 (X'08D3')MQRC_INCONSISTENT_BROWSE Explanation: An MQGET call was issued with the MQGMO_BROWSE_NEXT option specified, but the specification of the MQGMO_LOGICAL_ORDER option for the call is different from the specification of that option for the previous call for the queue handle. Either both calls must specify MQGMO_LOGICAL_ORDER, or neither call must specify MQGMO_LOGICAL_ORDER. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Add or remove the MQGMO_LOGICAL_ORDER option as appropriate. Alternatively, to switch between logical order and physical order, specify the MQGMO_BROWSE_FIRST option to restart the scan from the beginning of the queue, omitting or specifying MQGMO_LOGICAL_ORDER as required. 2260 (X'08D4')MQRC_XQH_ERROR Explanation: An MQPUT or MQPUT1 call was issued, but the message data contains an MQXQH structure that is not valid. Possible errors include the following: The StrucId field is not MQXQH_STRUC_ID. The Version field is not MQXQH_VERSION_1. The BufferLength parameter of the call has a value that is too small to accommodate the structure (the structure extends beyond the end of the message). This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Check that the fields in the structure are set correctly. 2261 (X'08D5')MQRC_SRC_ENV_ERROR Explanation: This reason occurs when a channel exit that processes reference messages detects an error in the source environment data of a reference message header (MQRMH). One of the following is true: SrcEnvLength is less than zero. SrcEnvLength is greater than zero, but there is no source environment data. SrcEnvLength is greater than zero, but SrcEnvOffset is negative, zero, or less than the length of the fixed part of MQRMH. SrcEnvLength is greater than zero, but SrcEnvOffset plus SrcEnvLength is greater than StrucLength. The exit returns this reason in the Feedback field of the MQCXP structure. If an exception report is requested, it is copied to the Feedback field of the MQMD associated with the report. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Specify the source environment data correctly. 2262 (X'08D6')MQRC_SRC_NAME_ERROR Explanation: This reason occurs when a channel exit that processes reference messages detects an error in the source name data of a reference message header (MQRMH). One of the following is true: SrcNameLength is less than zero. SrcNameLength is greater than zero, but there is no source name data. SrcNameLength is greater than zero, but SrcNameOffset is negative, zero, or less than the length of the fixed part of MQRMH. SrcNameLength is greater than zero, but SrcNameOffset plus SrcNameLength is greater than StrucLength. The exit returns this reason in the Feedback field of the MQCXP structure. If an exception report is requested, it is copied to the Feedback field of the MQMD associated with the report. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Specify the source name data correctly. 2263 (X'08D7')MQRC_DEST_ENV_ERROR Explanation: This reason occurs when a channel exit that processes reference messages detects an error in the destination environment data of a reference message header (MQRMH). One of the following is true: DestEnvLength is less than zero. DestEnvLength is greater than zero, but there is no destination environment data. DestEnvLength is greater than zero, but DestEnvOffset is negative, zero, or less than the length of the fixed part of MQRMH. DestEnvLength is greater than zero, but DestEnvOffset plus DestEnvLength is greater than StrucLength. The exit returns this reason in the Feedback field of the MQCXP structure. If an exception report is requested, it is copied to the Feedback field of the MQMD associated with the report. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Specify the destination environment data correctly. 2264 (X'08D8')MQRC_DEST_NAME_ERROR Explanation: This reason occurs when a channel exit that processes reference messages detects an error in the destination name data of a reference message header (MQRMH). One of the following is true: DestNameLength is less than zero. DestNameLength is greater than zero, but there is no destination name data. DestNameLength is greater than zero, but DestNameOffset is negative, zero, or less than the length of the fixed part of MQRMH. DestNameLength is greater than zero, but DestNameOffset plus DestNameLength is greater than StrucLength. The exit returns this reason in the Feedback field of the MQCXP structure. If an exception report is requested, it is copied to the Feedback field of the MQMD associated with the report. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Specify the destination name data correctly. 2265 (X'08D9')MQRC_TM_ERROR Explanation: An MQPUT or MQPUT1 call was issued, but the message data contains an MQTM structure that is not valid. Possible errors include the following: The StrucId field is not MQTM_STRUC_ID. The Version field is not MQTM_VERSION_1. The BufferLength parameter of the call has a value that is too small to accommodate the structure (the structure extends beyond the end of the message). This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Check that the fields in the structure are set correctly. 2266 (X'08DA')MQRC_CLUSTER_EXIT_ERROR Explanation: An MQOPEN, MQPUT, or MQPUT1 call was issued to open or put a message on a cluster queue, but the cluster workload exit defined by the queue-manager's ClusterWorkloadExit attribute failed unexpectedly or did not respond in time. Subsequent MQOPEN, MQPUT, and MQPUT1 calls for this queue handle are processed as though the ClusterWorkloadExit attribute were blank. On z/OS, a message giving more information about the error is written to the system log, for example message CSQV455E or CSQV456E. This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Check the cluster workload exit to ensure that it has been written correctly. 2267 (X'08DB')MQRC_CLUSTER_EXIT_LOAD_ERROR Explanation: An MQCONN or MQCONNX call was issued to connect to a queue manager, but the queue manager was unable to load the cluster workload exit. Execution continues without the cluster workload exit. On z/OS, if the cluster workload exit cannot be loaded, a message is written to the system log, for example message CSQV453I. Processing continues as though the ClusterWorkloadExit attribute had been blank. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_WARNING Programmer Response: Ensure that the queue-manager's ClusterWorkloadExit attribute has the correct value, and that the exit has been installed into the correct location. 2268 (X'08DC')MQRC_CLUSTER_PUT_INHIBITED Explanation: An MQOPEN call with the MQOO_OUTPUT and MQOO_BIND_ON_OPEN options in effect was issued for a cluster queue, but the call failed because all of the following are true: All instances of the cluster queue are currently put-inhibited (that is, all of the queue instances have the InhibitPut attribute set to MQQA_PUT_INHIBITED). There is no local instance of the queue. (If there is a local instance, the MQOPEN call succeeds, even if the local instance is put-inhibited.) There is no cluster workload exit for the queue, or there is a cluster workload exit but it did not choose a queue instance. (If the cluster workload exit does choose a queue instance, the MQOPEN call succeeds, even if that instance is put-inhibited.) If the MQOO_BIND_NOT_FIXED option is specified on the MQOPEN call, the call can succeed even if all of the queues in the cluster are put-inhibited. However, a subsequent MQPUT call may fail if all of the queues are still put-inhibited at the time of the MQPUT call. This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: If the system design allows put requests to be inhibited for short periods, retry the operation later. If the problem persists, determine why all of the queues in the cluster are put-inhibited. 2269 (X'08DD')MQRC_CLUSTER_RESOURCE_ERROR Explanation: An MQOPEN, MQPUT, or MQPUT1 call was issued for a cluster queue, but an error occurred whilst trying to use a resource required for clustering. This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Do the following: Check that the SYSTEM.CLUSTER.* queues are not put inhibited or full. Check the event queues for any events relating to the SYSTEM.CLUSTER.* queues, as these may give guidance as to the nature of the failure. Check that the repository queue manager is available. On z/OS, check the console for signs of the failure, such as full page sets. 2270 (X'08DE')MQRC_NO_DESTINATIONS_AVAILABLE Explanation: An MQPUT or MQPUT1 call was issued to put a message on a cluster queue, but at the time of the call there were no longer any instances of the queue in the cluster. The message therefore could not be sent. This situation can occur when MQOO_BIND_NOT_FIXED is specified on the MQOPEN call that opens the queue, or MQPUT1 is used to put the message. This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Check the queue definition and queue status to determine why all instances of the queue were removed from the cluster. Correct the problem and rerun the application. 2271 (X'08DF')MQRC_CONN_TAG_IN_USE Explanation: An MQCONNX call was issued specifying one of the MQCNO_*_CONN_TAG_* options, but the call failed because the connection tag specified by ConnTag in MQCNO is in use by an active process or thread, or there is an unresolved unit of work that references this connection tag. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: The problem is likely to be transitory. The application should wait a short while and then retry the operation. 2272 (X'08E0')MQRC_PARTIALLY_CONVERTED Explanation: On an MQGET call with the MQGMO_CONVERT option included in the GetMsgOpts parameter, one or more MQ header structures in the message data could not be converted to the specified target character set or encoding. In this situation, the MQ header structures are converted to the queue-manager's character set and encoding, and the application data in the message is converted to the target character set and encoding. On return from the call, the values returned in the various CodedCharSetId and Encoding fields in the MsgDesc parameter and MQ header structures indicate the character set and encoding that apply to each part of the message. The call completes with MQCC_WARNING. This reason code usually occurs when the specified target character set is one that causes the character strings in the MQ header structures to expand beyond the lengths of their fields. Unicode character set UCS-2 is an example of a character set that causes this to happen. Completion Code: MQCC_FAILED Programmer Response: If this is an expected situation, no corrective action is required. If this is an unexpected situation, check that the MQ header structures contain valid data. If they do, specify as the target character set a character set that does not cause the strings to expand. 2273 (X'08E1')MQRC_CONNECTION_ERROR Explanation: An MQCONN or MQCONNX call failed for one of the following reasons: The installation and customization options chosen for WebSphere MQ do not allow connection by the type of application being used. The system parameter module is not at the same release level as the queue manager. The channel initiator is not at the same release level as the queue manager. An internal error was detected by the queue manager. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: None, if the installation and customization options chosen for WebSphere MQ do not allow all functions to be used. Otherwise, if this occurs while starting the channel initiator, ensure that the queue manager and the channel initiator are both at the same release level and that their started task JCL procedures both specify the same level of WebSphere MQ program libraries; if this occurs while starting the queue manager, relinkedit the system parameter module (CSQZPARM) to ensure that it is at the correct level. If the problem persists, contact your IBM support center. 2274 (X'08E2')MQRC_OPTION_ENVIRONMENT_ERROR Explanation: An MQGET call with the MQGMO_MARK_SKIP_BACKOUT option specified was issued from a DB2 Stored Procedure. The call failed because the MQGMO_MARK_SKIP_BACKOUT option cannot be used from a DB2 Stored Procedure. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Remove the MQGMO_MARK_SKIP_BACKOUT option from the MQGET call. 2277 (X'08E5')MQRC_CD_ERROR Explanation: An MQCONNX call was issued to connect to a queue manager, but the MQCD channel definition structure addressed by the ClientConnOffset or ClientConnPtr field in MQCNO contains data that is not valid. Consult the error log for more information about the nature of the error. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Ensure that input fields in the MQCD structure are set correctly. 2278 (X'08E6')MQRC_CLIENT_CONN_ERROR Explanation: An MQCONNX call was issued to connect to a queue manager, but the MQCD channel definition structure is not specified correctly. One of the following applies: ClientConnOffset is not zero and ClientConnPtr is not zero and not the null pointer. ClientConnPtr is not a valid pointer. ClientConnPtr or ClientConnOffset points to storage that is not accessible. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. It also occurs in Java applications when a client channel definition table is specified to determine the name of the channel, but the table itself cannot be found. Completion Code: MQCC_FAILED Programmer Response: Ensure that at least one of ClientConnOffset and ClientConnPtr is zero. Ensure that the field used points to accessible storage. Ensure that the URL of the client channel definition table is correct. 2279 (X'08E7')MQRC_CHANNEL_STOPPED_BY_USER Explanation: This condition is detected when the channel has been stopped by an operator. The reason qualifier identifies the reasons for stopping. Completion Code: MQCC_WARNING Programmer Response: None. This reason code is only used to identify the corresponding event message. 2280 (X'08E8')MQRC_HCONFIG_ERROR Explanation: The configuration handle Hconfig specified on the MQXEP call or MQZEP call is not valid. The MQXEP call is issued by an API exit function; the MQZEP call is issued by an installable service. On z/OS, this reason code does not occur. Completion Code: MQCC_FAILED Programmer Response: Specify the configuration handle that was provided by the queue manager: On the MQXEP call, use the handle passed in the Hconfig field of the MQAXP structure. On the MQZEP call, use the handle passed to the installable service's configuration function on the component initialization call. See the WebSphere MQ System Administration Guide book for information about installable services. 2281 (X'08E9')MQRC_FUNCTION_ERROR Explanation: An MQXEP or MQZEP call was issued, but the function identifier Function specified on the call is not valid, or not supported by the installable service being configured. On z/OS, this reason code does not occur. Completion Code: MQCC_FAILED Programmer Response: Do the following: For the MQXEP call, specify one of the MQXF_* values. For the MQZEP call, specify an MQZID_* value that is valid for the installable service being configured. Refer to the description of the MQZEP call in the WebSphere MQ System Administration Guide book to determine which values are valid. 2282 (X'08EA')MQRC_CHANNEL_STARTED Explanation: One of the following has occurred: An operator has issued a Start Channel command. An instance of a channel has been successfully established. This condition is detected when Initial Data negotiation is complete and resynchronization has been performed where necessary such that message transfer can proceed. Completion Code: MQCC_WARNING Programmer Response: None. This reason code is only used to identify the corresponding event message. 2283 (X'08EB')MQRC_CHANNEL_STOPPED Explanation: This condition is detected when the channel has been stopped. The reason qualifier identifies the reasons for stopping. Completion Code: MQCC_WARNING Programmer Response: None. This reason code is only used to identify the corresponding event message. 2284 (X'08EC')MQRC_CHANNEL_CONV_ERROR Explanation: This condition is detected when a channel is unable to do data conversion and the MQGET call to get a message from the transmission queue resulted in a data conversion error. The conversion reason code identifies the reason for the failure. Completion Code: MQCC_WARNING Programmer Response: None. This reason code is only used to identify the corresponding event message. 2285 (X'08ED')MQRC_SERVICE_NOT_AVAILABLE Explanation: This reason should be returned by an installable service component when the requested action cannot be performed because the required underlying service is not available. On z/OS, this reason code does not occur. Completion Code: MQCC_FAILED Programmer Response: Make the underlying service available. 2286 (X'08EE')MQRC_INITIALIZATION_FAILED Explanation: This reason should be returned by an installable service component when the component is unable to complete initialization successfully. On z/OS, this reason code does not occur. Completion Code: MQCC_FAILED Programmer Response: Correct the error and retry the operation. 2287 (X'08EF')MQRC_TERMINATION_FAILED Explanation: This reason should be returned by an installable service component when the component is unable to complete termination successfully. On z/OS, this reason code does not occur. Completion Code: MQCC_FAILED Programmer Response: Correct the error and retry the operation. 2288 (X'08F0')MQRC_UNKNOWN_Q_NAME Explanation: This reason should be returned by the MQZ_LOOKUP_NAME installable service component when the name specified for the QName parameter is not recognized. On z/OS, this reason code does not occur. Completion Code: MQCC_FAILED Programmer Response: None. See the WebSphere MQ System Administration Guide book for information about installable services. 2289 (X'08F1')MQRC_SERVICE_ERROR Explanation: This reason should be returned by an installable service component when the component encounters an unexpected error. On z/OS, this reason code does not occur. Completion Code: MQCC_FAILED Programmer Response: Correct the error and retry the operation. 2290 (X'08F2')MQRC_Q_ALREADY_EXISTS Explanation: This reason should be returned by the MQZ_INSERT_NAME installable service component when the queue specified by the QName parameter is already defined to the name service. On z/OS, this reason code does not occur. Completion Code: MQCC_FAILED Programmer Response: None. See the WebSphere MQ System Administration Guide book for information about installable service. 2291 (X'08F3')MQRC_USER_ID_NOT_AVAILABLE Explanation: This reason should be returned by the MQZ_FIND_USERID installable service component when the user ID cannot be determined. On z/OS, this reason code does not occur. Completion Code: MQCC_FAILED Programmer Response: None. See the WebSphere MQ System Administration Guide book for information about installable services. 2292 (X'08F4')MQRC_UNKNOWN_ENTITY Explanation: This reason should be returned by the authority installable service component when the name specified by the EntityName parameter is not recognized. On z/OS, this reason code does not occur. Completion Code: MQCC_FAILED Programmer Response: Ensure that the entity is defined. 2294 (X'08F6')MQRC_UNKNOWN_REF_OBJECT Explanation: This reason should be returned by the MQZ_COPY_ALL_AUTHORITY installable service component when the name specified by the RefObjectName parameter is not recognized. On z/OS, this reason code does not occur. Completion Code: MQCC_FAILED Programmer Response: Ensure that the reference object is defined. See the WebSphere MQ System Administration Guide book for information about installable services. 2295 (X'08F7')MQRC_CHANNEL_ACTIVATED Explanation: This condition is detected when a channel that has been waiting to become active, and for which a Channel Not Activated event has been generated, is now able to become active because an active slot has been released by another channel. This event is not generated for a channel that is able to become active without waiting for an active slot to be released. Completion Code: MQCC_WARNING Programmer Response: None. This reason code is only used to identify the corresponding event message. 2296 (X'08F8')MQRC_CHANNEL_NOT_ACTIVATED Explanation: This condition is detected when a channel is required to become active, either because it is starting or because it is about to make another attempt to establish connection with its partner. However, it is unable to do so because the limit on the number of active channels has been reached. On z/OS, the maximum number of active channels is given by the ACTCHL queue manager attribute. In other environments, the maximum number of active channels is given by the MaxActiveChannels parameter in the qm.ini file. The channel waits until it is able to take over an active slot released when another channel ceases to be active. At that time a Channel Activated event is generated. Completion Code: MQCC_WARNING Programmer Response: None. This reason code is only used to identify the corresponding event message. 2297 (X'08F9')MQRC_UOW_CANCELED Explanation: An MQI call was issued, but the unit of work (TM/MP transaction) being used for the MQ operation had been canceled. This may have been done by TM/MP itself (for example, due to the transaction running for too long, or exceeding audit trail sizes), or by the application program issuing an ABORT_TRANSACTION. All updates performed to resources owned by the queue manager are backed out. Completion Code: MQCC_FAILED Programmer Response: Refer to the operating system's Transaction Management Operations Guide to determine how the Transaction Manager can be tuned to avoid the problem of system limits being exceeded. 2298 (X'08FA')MQRC_FUNCTION_NOT_SUPPORTED Explanation: The function requested is not available in the current environment. Completion Code: MQCC_FAILED Programmer Response: Remove the call from the application. 2299 (X'08FB')MQRC_SELECTOR_TYPE_ERROR Explanation: The Selector parameter has the wrong data type; it must be of type Long. Completion Code: MQCC_FAILED Programmer Response: Declare the Selector parameter as Long. 2300 (X'08FC')MQRC_COMMAND_TYPE_ERROR Explanation: The mqExecute call was issued, but the value of the MQIASY_TYPE data item in the administration bag is not MQCFT_COMMAND. Completion Code: MQCC_FAILED Programmer Response: Ensure that the MQIASY_TYPE data item in the administration bag has the value MQCFT_COMMAND. 2301 (X'08FD')MQRC_MULTIPLE_INSTANCE_ERROR Explanation: The Selector parameter specifies a system selector (one of the MQIASY_* values), but the value of the ItemIndex parameter is not MQIND_NONE. Only one instance of each system selector can exist in the bag. Completion Code: MQCC_FAILED Programmer Response: Specify MQIND_NONE for the ItemIndex parameter. 2302 (X'08FE')MQRC_SYSTEM_ITEM_NOT_ALTERABLE Explanation: A call was issued to modify the value of a system data item in a bag (a data item with one of the MQIASY_* selectors), but the call failed because the data item is one that cannot be altered by the application. Completion Code: MQCC_FAILED Programmer Response: Specify the selector of a user-defined data item, or remove the call. 2303 (X'08FF')MQRC_BAG_CONVERSION_ERROR Explanation: The mqBufferToBag or mqGetBag call was issued, but the data in the buffer or message could not be converted into a bag. This occurs when the data to be converted is not valid PCF. Completion Code: MQCC_FAILED Programmer Response: Check the logic of the application that created the buffer or message to ensure that the buffer or message contains valid PCF. If the message contains PCF that is not valid, the message cannot be retrieved using the mqGetBag call: If one of the MQGMO_BROWSE_* options was specified, the message remains on the queue and can be retrieved using the MQGET call. In other cases, the message has already been removed from the queue and discarded. If the message was retrieved within a unit of work, the unit of work can be backed out and the message retrieved using the MQGET call. 2304 (X'0900')MQRC_SELECTOR_OUT_OF_RANGE Explanation: The Selector parameter has a value that is outside the valid range for the call. If the bag was created with the MQCBO_CHECK_SELECTORS option: For the mqAddInteger call, the value must be within the range MQIA_FIRST through MQIA_LAST. For the mqAddString call, the value must be within the range MQCA_FIRST through MQCA_LAST. If the bag was not created with the MQCBO_CHECK_SELECTORS option: The value must be zero or greater. Completion Code: MQCC_FAILED Programmer Response: Specify a valid value. 2305 (X'0901')MQRC_SELECTOR_NOT_UNIQUE Explanation: The ItemIndex parameter has the value MQIND_NONE, but the bag contains more than one data item with the selector value specified by the Selector parameter. MQIND_NONE requires that the bag contain only one occurrence of the specified selector. This reason code also occurs on the mqExecute call when the administration bag contains two or more occurrences of a selector for a required parameter that permits only one occurrence. Completion Code: MQCC_FAILED Programmer Response: Check the logic of the application that created the bag. If correct, specify for ItemIndex a value that is zero or greater, and add application logic to process all of the occurrences of the selector in the bag. Review the description of the administration command being issued, and ensure that all required parameters are defined correctly in the bag. 2306 (X'0902')MQRC_INDEX_NOT_PRESENT Explanation: The specified index is not present: For a bag, this means that the bag contains one or more data items that have the selector value specified by the Selector parameter, but none of them has the index value specified by the ItemIndex parameter. The data item identified by the Selector and ItemIndex parameters must exist in the bag. For a namelist, this means that the index parameter value is too large, and outside the range of valid values. Completion Code: MQCC_FAILED Programmer Response: Specify the index of a data item that does exist in the bag or namelist. Use the mqCountItems call to determine the number of data items with the specified selector that exist in the bag, or the nameCount method to determine the number of names in the namelist. 2307 (X'0903')MQRC_STRING_ERROR Explanation: The String parameter is not valid. Either the parameter pointer is not valid, or it points to read-only storage. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) Completion Code: MQCC_FAILED Programmer Response: Correct the parameter. 2308 (X'0904')MQRC_ENCODING_NOT_SUPPORTED Explanation: The Encoding field in the message descriptor MQMD contains a value that is not supported: For the mqPutBag call, the field in error resides in the MsgDesc parameter of the call. For the mqGetBag call, the field in error resides in: The MsgDesc parameter of the call if the MQGMO_CONVERT option was specified. The message descriptor of the message about to be retrieved if MQGMO_CONVERT was not specified. Completion Code: MQCC_FAILED Programmer Response: The value must be MQENC_NATIVE. If the value of the Encoding field in the message is not valid, the message cannot be retrieved using the mqGetBag call: If one of the MQGMO_BROWSE_* options was specified, the message remains on the queue and can be retrieved using the MQGET call. In other cases, the message has already been removed from the queue and discarded. If the message was retrieved within a unit of work, the unit of work can be backed out and the message retrieved using the MQGET call. 2309 (X'0905')MQRC_SELECTOR_NOT_PRESENT Explanation: The Selector parameter specifies a selector that does not exist in the bag. Completion Code: MQCC_FAILED Programmer Response: Specify a selector that does exist in the bag. 2310 (X'0906')MQRC_OUT_SELECTOR_ERROR Explanation: The OutSelector parameter is not valid. Either the parameter pointer is not valid, or it points to read-only storage. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) Completion Code: MQCC_FAILED Programmer Response: Correct the parameter. 2311 (X'0907')MQRC_STRING_TRUNCATED Explanation: The string returned by the call is too long to fit in the buffer provided. The string has been truncated to fit in the buffer. Completion Code: MQCC_FAILED Programmer Response: If the entire string is required, provide a larger buffer. On the mqInquireString call, the StringLength parameter is set by the call to indicate the size of the buffer required to accommodate the string without truncation. 2312 (X'0908')MQRC_SELECTOR_WRONG_TYPE Explanation: A data item with the specified selector exists in the bag, but has a data type that conflicts with the data type implied by the call being used. For example, the data item might have an integer data type, but the call being used might be mqSetString, which implies a character data type. This reason code also occurs on the mqBagToBuffer, mqExecute, and mqPutBag calls when mqAddString or mqSetString was used to add the MQIACF_INQUIRY data item to the bag. Completion Code: MQCC_FAILED Programmer Response: For the mqSetInteger and mqSetString calls, specify MQIND_ALL for the ItemIndex parameter to delete from the bag all existing occurrences of the specified selector before creating the new occurrence with the required data type. For the mqInquireBag, mqInquireInteger, and mqInquireString calls, use the mqInquireItemInfo call to determine the data type of the item with the specified selector, and then use the appropriate call to determine the value of the data item. For the mqBagToBuffer, mqExecute, and mqPutBag calls, ensure that the MQIACF_INQUIRY data item is added to the bag using the mqAddInteger or mqSetInteger calls. 2313 (X'0909')MQRC_INCONSISTENT_ITEM_TYPE Explanation: The mqAddInteger or mqAddString call was issued to add another occurrence of the specified selector to the bag, but the data type of this occurrence differed from the data type of the first occurrence. This reason can also occur on the mqBufferToBag and mqGetBag calls, where it indicates that the PCF in the buffer or message contains a selector that occurs more than once but with inconsistent data types. Completion Code: MQCC_FAILED Programmer Response: For the mqAddInteger and mqAddString calls, use the call appropriate to the data type of the first occurrence of that selector in the bag. For the mqBufferToBag and mqGetBag calls, check the logic of the application that created the buffer or sent the message to ensure that multiple-occurrence selectors occur with only one data type. A message that contains a mixture of data types for a selector cannot be retrieved using the mqGetBag call: If one of the MQGMO_BROWSE_* options was specified, the message remains on the queue and can be retrieved using the MQGET call. In other cases, the message has already been removed from the queue and discarded. If the message was retrieved within a unit of work, the unit of work can be backed out and the message retrieved using the MQGET call. 2314 (X'090A')MQRC_INDEX_ERROR Explanation: An index parameter to a call or method has a value that is not valid. The value must be zero or greater. For bag calls, certain MQIND_* values can also be specified: For the mqDeleteItem, mqSetInteger and mqSetString calls, MQIND_ALL and MQIND_NONE are valid. For the mqInquireBag, mqInquireInteger, mqInquireString, and mqInquireItemInfo calls, MQIND_NONE is valid. Completion Code: MQCC_FAILED Programmer Response: Specify a valid value. 2315 (X'090B')MQRC_SYSTEM_BAG_NOT_ALTERABLE Explanation: A call was issued to add a data item to a bag, modify the value of an existing data item in a bag, or retrieve a message into a bag, but the call failed because the bag is one that had been created by the system as a result of a previous mqExecute call. System bags cannot be modified by the application. Completion Code: MQCC_FAILED Programmer Response: Specify the handle of a bag created by the application, or remove the call. 2316 (X'090C')MQRC_ITEM_COUNT_ERROR Explanation: The mqTruncateBag call was issued, but the ItemCount parameter specifies a value that is not valid. The value is either less than zero, or greater than the number of user-defined data items in the bag. This reason also occurs on the mqCountItems call if the parameter pointer is not valid, or points to read-only storage. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) Completion Code: MQCC_FAILED Programmer Response: Specify a valid value. Use the mqCountItems call to determine the number of user-defined data items in the bag. 2317 (X'090D')MQRC_FORMAT_NOT_SUPPORTED Explanation: The Format field in the message descriptor MQMD contains a value that is not supported: In an administration message, the format value must be one of the following: MQFMT_ADMIN, MQFMT_EVENT, MQFMT_PCF. For the mqPutBag call, the field in error resides in the MsgDesc parameter of the call. For the mqGetBag call, the field in error resides in the message descriptor of the message about to be retrieved. On z/OS, the message was put to the command input queue with a format value of MQFMT_ADMIN, but the version of MQ being used does not support that format for commands. Completion Code: MQCC_FAILED Programmer Response: If the error occurred when putting a message, correct the format value. If the error occurred when getting a message, the message cannot be retrieved using the mqGetBag call: If one of the MQGMO_BROWSE_* options was specified, the message remains on the queue and can be retrieved using the MQGET call. In other cases, the message has already been removed from the queue and discarded. If the message was retrieved within a unit of work, the unit of work can be backed out and the message retrieved using the MQGET call. 2318 (X'090E')MQRC_SELECTOR_NOT_SUPPORTED Explanation: The Selector parameter specifies a value that is a system selector (a value that is negative), but the system selector is not one that is supported by the call. Completion Code: MQCC_FAILED Programmer Response: Specify a selector value that is supported. 2319 (X'090F')MQRC_ITEM_VALUE_ERROR Explanation: The mqInquireBag or mqInquireInteger call was issued, but the ItemValue parameter is not valid. Either the parameter pointer is not valid, or it points to read-only storage. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) Completion Code: MQCC_FAILED Programmer Response: Correct the parameter. 2320 (X'0910')MQRC_HBAG_ERROR Explanation: A call was issued that has a parameter that is a bag handle, but the handle is not valid. For output parameters, this reason also occurs if the parameter pointer is not valid, or points to read-only storage. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) Completion Code: MQCC_FAILED Programmer Response: Correct the parameter. 2321 (X'0911')MQRC_PARAMETER_MISSING Explanation: An administration message requires a parameter that is not present in the administration bag. This reason code occurs only for bags created with the MQCBO_ADMIN_BAG or MQCBO_REORDER_AS_REQUIRED options. Completion Code: MQCC_FAILED Programmer Response: Review the description of the administration command being issued, and ensure that all required parameters are present in the bag. 2322 (X'0912')MQRC_CMD_SERVER_NOT_AVAILABLE Explanation: The command server that processes administration commands is not available. Completion Code: MQCC_FAILED Programmer Response: Start the command server. 2323 (X'0913')MQRC_STRING_LENGTH_ERROR Explanation: The StringLength parameter is not valid. Either the parameter pointer is not valid, or it points to read-only storage. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) Completion Code: MQCC_FAILED Programmer Response: Correct the parameter. 2324 (X'0914')MQRC_INQUIRY_COMMAND_ERROR Explanation: The mqAddInquiry call was used previously to add attribute selectors to the bag, but the command code to be used for the mqBagToBuffer, mqExecute, or mqPutBag call is not recognized. As a result, the correct PCF message cannot be generated. Completion Code: MQCC_FAILED Programmer Response: Remove the mqAddInquiry calls and use instead the mqAddInteger call with the appropriate MQIACF_*_ATTRS or MQIACH_*_ATTRS selectors. 2325 (X'0915')MQRC_NESTED_BAG_NOT_SUPPORTED Explanation: A bag that is input to the call contains nested bags. Nested bags are supported only for bags that are output from the call. Completion Code: MQCC_FAILED Programmer Response: Use a different bag as input to the call. 2326 (X'0916')MQRC_BAG_WRONG_TYPE Explanation: The Bag parameter specifies the handle of a bag that has the wrong type for the call. The bag must be an administration bag, that is, it must be created with the MQCBO_ADMIN_BAG option specified on the mqCreateBag call. Completion Code: MQCC_FAILED Programmer Response: Specify the MQCBO_ADMIN_BAG option when the bag is created. 2327 (X'0917')MQRC_ITEM_TYPE_ERROR Explanation: The mqInquireItemInfo call was issued, but the ItemType parameter is not valid. Either the parameter pointer is not valid, or it points to read-only storage. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) Completion Code: MQCC_FAILED Programmer Response: Correct the parameter. 2328 (X'0918')MQRC_SYSTEM_BAG_NOT_DELETABLE Explanation: An mqDeleteBag call was issued to delete a bag, but the call failed because the bag is one that had been created by the system as a result of a previous mqExecute call. System bags cannot be deleted by the application. Completion Code: MQCC_FAILED Programmer Response: Specify the handle of a bag created by the application, or remove the call. 2329 (X'0919')MQRC_SYSTEM_ITEM_NOT_DELETABLE Explanation: A call was issued to delete a system data item from a bag (a data item with one of the MQIASY_* selectors), but the call failed because the data item is one that cannot be deleted by the application. Completion Code: MQCC_FAILED Programmer Response: Specify the selector of a user-defined data item, or remove the call. 2330 (X'091A')MQRC_CODED_CHAR_SET_ID_ERROR Explanation: The CodedCharSetId parameter is not valid. Either the parameter pointer is not valid, or it points to read-only storage. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) Completion Code: MQCC_FAILED Programmer Response: Correct the parameter. 2331 (X'091B')MQRC_MSG_TOKEN_ERROR Explanation: An MQGET call was issued to retrieve a message using the message token as a selection criterion, but the options specified are not valid, because MQMO_MATCH_MSG_TOKEN was specified with either MQGMO_WAIT or MQGMO_SET_SIGNAL. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Remove the MQMO_MATCH_MSG_TOKEN option from the MQGET call. 2332 (X'091C')MQRC_MISSING_WIH Explanation: An MQPUT or MQPUT1 call was issued to put a message on a queue whose IndexType attribute had the value MQIT_MSG_TOKEN, but the Format field in the MQMD was not MQFMT_WORK_INFO_HEADER. This error occurs only when the message arrives at the destination queue manager. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Modify the application to ensure that it places an MQWIH structure at the start of the message data, and sets the Format field in the MQMD to MQFMT_WORK_INFO_HEADER. Alternatively, change the ApplType attribute of the process definition used by the destination queue to be MQAT_WLM, and specify the required service name and service step name in its EnvData attribute. 2333 (X'091D')MQRC_WIH_ERROR Explanation: An MQPUT or MQPUT1 call was issued, but the message data contains an MQWIH structure that is not valid. Possible errors include the following: The StrucId field is not MQWIH_STRUC_ID. The Version field is not MQWIH_VERSION_1. The StrucLength field is not MQWIH_LENGTH_1. The CodedCharSetId field is zero, or a negative value that is not valid. The BufferLength parameter of the call has a value that is too small to accommodate the structure (the structure extends beyond the end of the message). On z/OS, this error also occurs when the IndexType attribute of the queue is MQIT_MSG_TOKEN, but the message data does not begin with an MQWIH structure. Completion Code: MQCC_FAILED Programmer Response: Check that the fields in the structure are set correctly. Ensure that the application sets the CodedCharSetId field to a valid value (note: MQCCSI_DEFAULT, MQCCSI_EMBEDDED, MQCCSI_Q_MGR, and MQCCSI_UNDEFINED are not valid in this field). On z/OS, if the queue has an IndexType of MQIT_MSG_TOKEN, ensure that the message data begins with an MQWIH structure. 2334 (X'091E')MQRC_RFH_ERROR Explanation: An MQPUT or MQPUT1 call was issued, but the message data contains an MQRFH or MQRFH2 structure that is not valid. Possible errors include the following: The StrucId field is not MQRFH_STRUC_ID. The Version field is not MQRFH_VERSION_1 (MQRFH), or MQRFH_VERSION_2 (MQRFH2). The StrucLength field specifies a value that is too small to include the structure plus the variable-length data at the end of the structure. The CodedCharSetId field is zero, or a negative value that is not valid. The BufferLength parameter of the call has a value that is too small to accommodate the structure (the structure extends beyond the end of the message). Completion Code: MQCC_FAILED Programmer Response: Check that the fields in the structure are set correctly. Ensure that the application sets the CodedCharSetId field to a valid value (note: MQCCSI_DEFAULT, MQCCSI_EMBEDDED, MQCCSI_Q_MGR, and MQCCSI_UNDEFINED are not valid in this field). 2335 (X'091F')MQRC_RFH_STRING_ERROR Explanation: The contents of the NameValueString field in the MQRFH structure are not valid. NameValueString must adhere to the following rules: The string must consist of zero or more name/value pairs separated from each other by one or more blanks; the blanks are not significant. If a name or value contains blanks that are significant, the name or value must be enclosed in double-quote characters. If a name or value itself contains one or more double-quote characters, the name or value must be enclosed in double-quote characters, and each embedded double-quote character must be doubled. A name or value can contain any characters other than the null, which acts as a delimiter. The null and characters following it, up to the defined length of NameValueString, are ignored. The following is a valid NameValueString: Famous_Words "The program displayed ""Hello World"""Completion Code: MQCC_FAILED Programmer Response: Modify the application that generated the message to ensure that it places in the NameValueString field data that adheres to the rules listed above. Check that the StrucLength field is set to the correct value. 2336 (X'0920')MQRC_RFH_COMMAND_ERROR Explanation: The message contains an MQRFH structure, but the command name contained in the NameValueString field is not valid. Completion Code: MQCC_FAILED Programmer Response: Modify the application that generated the message to ensure that it places in the NameValueString field a command name that is valid. 2337 (X'0921')MQRC_RFH_PARM_ERROR Explanation: The message contains an MQRFH structure, but a parameter name contained in the NameValueString field is not valid for the command specified. Completion Code: MQCC_FAILED Programmer Response: Modify the application that generated the message to ensure that it places in the NameValueString field only parameters that are valid for the specified command. 2338 (X'0922')MQRC_RFH_DUPLICATE_PARM Explanation: The message contains an MQRFH structure, but a parameter occurs more than once in the NameValueString field when only one occurrence is valid for the specified command. Completion Code: MQCC_FAILED Programmer Response: Modify the application that generated the message to ensure that it places in the NameValueString field only one occurrence of the parameter. 2339 (X'0923')MQRC_RFH_PARM_MISSING Explanation: The message contains an MQRFH structure, but the command specified in the NameValueString field requires a parameter that is not present. Completion Code: MQCC_FAILED Programmer Response: Modify the application that generated the message to ensure that it places in the NameValueString field all parameters that are required for the specified command. 2340 (X'0924')MQRC_CHAR_CONVERSION_ERROR Explanation: This reason code is returned by the Java MQQueueManager constructor when a required character-set conversion is not available. The conversion required is between two nonUnicode character sets. This reason code occurs in the following environment: MQ Classes for Java on z/OS. Completion Code: MQCC_FAILED Programmer Response: Ensure that the National Language Resources component of the OS/390 Language Environment is installed, and that conversion between the IBM-1047 and ISO8859-1 character sets is available. 2341 (X'0925')MQRC_UCS2_CONVERSION_ERROR Explanation: This reason code is returned by the Java MQQueueManager constructor when a required character-set conversion is not available. The conversion required is between the UCS-2 Unicode character set and the queue-manager's character set. IBM-500 is used for the queue-manager's character set if no specific value is available. This reason code occurs in the following environment: MQ Classes for Java on z/OS. Completion Code: MQCC_FAILED Programmer Response: Ensure that the relevant Unicode conversion tables are installed, and that they are available to the z/OS Language Environment. The conversion tables should be installed as part of the z/OS C/C++ optional feature. Refer to the z/OS C/C++ Programming Guide for more information about enabling UCS-2 conversions. 2342 (X'0926')MQRC_DB2_NOT_AVAILABLE Explanation: An MQOPEN, MQPUT1, or MQSET call, or a command, was issued to access a shared queue, but it failed because the queue manager is not connected to a DB2 subsystem. As a result, the queue manager is unable to access the object definition relating to the shared queue. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Configure the DB2 subsystem so that the queue manager can connect to it. 2343 (X'0927')MQRC_OBJECT_NOT_UNIQUE Explanation: An MQOPEN or MQPUT1 call, or a command, was issued to access a queue, but the call failed because the queue specified cannot be resolved unambiguously. There exists a shared queue with the specified name, and a nonshared queue with the same name. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: One of the queues must be deleted. If the queue to be deleted contains messages, use the MQSC command MOVE QLOCAL to move the messages to a different queue, and then use the command DELETE QLOCAL to delete the queue. 2344 (X'0928')MQRC_CONN_TAG_NOT_RELEASED Explanation: An MQDISC call was issued when there was a unit of work outstanding for the connection handle. For CICS, IMS, and RRS connections, the MQDISC call does not commit or back out the unit of work. As a result, the connection tag associated with the unit of work is not yet available for reuse. The tag becomes available for reuse only when processing of the unit of work has been completed. This reason code occurs only on z/OS. Completion Code: MQCC_WARNING Programmer Response: Do not try to reuse the connection tag immediately. If the MQCONNX call is issued with the same connection tag, and that tag is still in use, the call fails with reason code MQRC_CONN_TAG_IN_USE. 2345 (X'0929')MQRC_CF_NOT_AVAILABLE Explanation: An MQOPEN or MQPUT1 call was issued to access a shared queue, but the allocation of the coupling-facility structure specified in the queue definition failed because there is no suitable coupling facility to hold the structure, based on the preference list in the active CFRM policy. This reason code can also occur when the API call requires a capability that is not supported by the CF level defined in the coupling-facility structure object. For example, this reason code is returned by an attempt to open a shared queue that has a index type of MQIT_GROUP_ID, but the coupling-facility structure for the queue has a CF level lower than three. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Make available a coupling facility with one of the names specified in the CFRM policy, or modify the CFRM policy to specify the names of coupling facilities that are available. 2346 (X'092A')MQRC_CF_STRUC_IN_USE Explanation: An MQI call or command was issued to operate on a shared queue, but the call failed because the coupling-facility structure specified in the queue definition is temporarily unavailable. The coupling-facility structure can be unavailable because a structure dump is in progress, or new connectors to the structure are currently inhibited, or an existing connector to the structure failed or disconnected abnormally and clean-up is not yet complete. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: The problem is temporary; wait a short while and then retry the operation. 2347 (X'092B')MQRC_CF_STRUC_LIST_HDR_IN_USE Explanation: An MQGET, MQOPEN, MQPUT1, or MQSET call was issued to access a shared queue, but the call failed because the list header associated with the coupling-facility structure specified in the queue definition is temporarily unavailable. The list header is unavailable because it is undergoing recovery processing. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: The problem is temporary; wait a short while and then retry the operation. 2348 (X'092C')MQRC_CF_STRUC_AUTH_FAILED Explanation: An MQOPEN or MQPUT1 call was issued to access a shared queue, but the call failed because the user is not authorized to access the coupling-facility structure specified in the queue definition. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Modify the security profile for the user identifier used by the application so that the application can access the coupling-facility structure specified in the queue definition. 2349 (X'092D')MQRC_CF_STRUC_ERROR Explanation: An MQOPEN or MQPUT1 call was issued to access a shared queue, but the call failed because the coupling-facility structure name specified in the queue definition is not defined in the CFRM data set, or is not the name of a list structure. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Modify the queue definition to specify the name of a coupling-facility list structure that is defined in the CFRM data set. 2350 (X'092E')MQRC_CONN_TAG_NOT_USABLE Explanation: An MQCONNX call was issued specifying one of the MQCNO_*_CONN_TAG_* options, but the call failed because the connection tag specified by ConnTag in MQCNO is being used by the queue manager for recovery processing, and this processing is delayed pending recovery of the coupling facility. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: The problem is likely to persist. Consult the system programmer to ascertain the cause of the problem. 2351 (X'092F')MQRC_GLOBAL_UOW_CONFLICT Explanation: An attempt was made to use inside a global unit of work a connection handle that is participating in another global unit of work. This can occur when an application passes connection handles between objects where the objects are involved in different DTC transactions. Because transaction completion is asynchronous, it is possible for this error to occur after the application has finalized the first object and committed its transaction. This error does not occur for nontransactional MQI calls. This reason code occurs only on Windows and z/OS. Completion Code: MQCC_FAILED Programmer Response: Check that the "MTS Transaction Support" attribute defined for the object's class is set correctly. If necessary, modify the application so that the connection handle is not used by objects participating in different units of work. 2352 (X'0930')MQRC_LOCAL_UOW_CONFLICT Explanation: An attempt was made to use inside a global unit of work a connection handle that is participating in a queue-manager coordinated local unit of work. This can occur when an application passes connection handles between objects where one object is involved in a DTC transaction and the other is not. This error does not occur for nontransactional MQI calls. This reason code occurs only on Windows and z/OS. Completion Code: MQCC_FAILED Programmer Response: Check that the "MTS Transaction Support" attribute defined for the object's class is set correctly. If necessary, modify the application so that the connection handle is not used by objects participating in different units of work. 2353 (X'0931')MQRC_HANDLE_IN_USE_FOR_UOW Explanation: An attempt was made to use outside a unit of work a connection handle that is participating in a global unit of work. This error can occur when an application passes connection handles between objects where one object is involved in a DTC transaction and the other is not. Because transaction completion is asynchronous, it is possible for this error to occur after the application has finalized the first object and committed its transaction. This error can also occur when a single object that was created and associated with the transaction loses that association whilst the object is running. The association is lost when DTC terminates the transaction independently of MTS. This might be because the transaction timed out, or because DTC shut down. This error does not occur for nontransactional MQI calls. This reason code occurs only on Windows. Completion Code: MQCC_FAILED Programmer Response: Check that the "MTS Transaction Support" attribute defined for the object's class is set correctly. If necessary, modify the application so that objects executing within different units of work do not try to use the same connection handle. 2354 (X'0932')MQRC_UOW_ENLISTMENT_ERROR Explanation: This reason code can occur for a variety of reasons. The most likely reason is that an object created by a DTC transaction does not issue a transactional MQI call until after the DTC transaction has timed out. (If the DTC transaction times out after a transactional MQI call has been issued, reason code MQRC_HANDLE_IN_USE_FOR_UOW is returned by the failing MQI call.) Another cause of MQRC_UOW_ENLISTMENT_ERROR is incorrect installation; Windows NT Service pack must be installed after the Windows NT Option pack. This reason code occurs only on Windows. Completion Code: MQCC_FAILED Programmer Response: Check the DTC "Transaction timeout" value. If necessary, verify the NT installation order. 2355 (X'0933')MQRC_UOW_MIX_NOT_SUPPORTED Explanation: The mixture of calls used by the application to perform operations within a unit of work is not supported. In particular, it is not possible to mix within the same process a local unit of work coordinated by the queue manager with a global unit of work coordinated by DTC (Distributed Transaction Coordinator). An application may cause this mixture to arise if some objects in a package are coordinated by DTC and others are not. It can also occur if transactional MQI calls from an MTS client are mixed with transactional MQI calls from a library package transactional MTS object. No problem arises if all transactional MQI calls originate from transactional MTS objects, or all transactional MQI calls originate from nontransactional MTS objects. But when a mixture of styles is used, the first style used fixes the style for the unit of work, and subsequent attempts to use the other style within the process fail with reason code MQRC_UOW_MIX_NOT_SUPPORTED. When an application is run twice, scheduling factors in the operating system mean that it is possible for the queue-manager-coordinated transactional calls to fail in one run, and for the DTC-coordinated transactional calls to fail in the other run. This reason code occurs only on Windows when running a version of the queue manager prior to version 5.2. Completion Code: MQCC_FAILED Programmer Response: Check that the "MTS Transaction Support" attribute defined for the object's class is set correctly. If necessary, modify the application so that objects executing within different units of work do not try to use the same connection handle. 2356 (X'0934')MQRC_WXP_ERROR Explanation: An MQXCLWLN call was issued from a cluster workload exit to obtain the address of the next record in the chain, but the workload exit parameter structure ExitParms is not valid, for one of the following reasons: The parameter pointer is not valid. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) The StrucId field is not MQWXP_STRUC_ID. The Version field is not MQWXP_VERSION_2. The CacheContext field does not contain the value passed to the exit by the queue manager. Completion Code: MQCC_FAILED Programmer Response: Ensure that the parameter specified for ExitParms is the MQWXP structure that was passed to the exit when the exit was invoked. 2357 (X'0935')MQRC_CURRENT_RECORD_ERROR Explanation: An MQXCLWLN call was issued from a cluster workload exit to obtain the address of the next record in the chain, but the address specified by the CurrentRecord parameter is not the address of a valid record. CurrentRecord must be the address of a destination record (MQWDR), queue record (MQWQR), or cluster record (MQWCR) residing within the cluster cache. Completion Code: MQCC_FAILED Programmer Response: Ensure that the cluster workload exit passes the address of a valid record residing in the cluster cache. 2358 (X'0936')MQRC_NEXT_OFFSET_ERROR Explanation: An MQXCLWLN call was issued from a cluster workload exit to obtain the address of the next record in the chain, but the offset specified by the NextOffset parameter is not valid. NextOffset must be the value of one of the following fields: ChannelDefOffset field in MQWDR ClusterRecOffset field in MQWDR ClusterRecOffset field in MQWQR ClusterRecOffset field in MQWCR Completion Code: MQCC_FAILED Programmer Response: Ensure that the value specified for the NextOffset parameter is the value of one of the fields listed above. 2359 (X'0937')MQRC_NO_RECORD_AVAILABLE Explanation: An MQXCLWLN call was issued from a cluster workload exit to obtain the address of the next record in the chain, but the current record is the last record in the chain. Completion Code: MQCC_FAILED Programmer Response: None. 2360 (X'0938')MQRC_OBJECT_LEVEL_INCOMPATIBLE Explanation: An MQOPEN or MQPUT1 call, or a command, was issued, but the definition of the object to be accessed is not compatible with the queue manager to which the application has connected. The object definition was created or modified by a different version of the queue manager. If the object to be accessed is a queue, the incompatible object definition could be the object specified, or one of the object definitions used to resolve the specified object (for example, the base queue to which an alias queue resolves, or the transmission queue to which a remote queue or queue-manager alias resolves). This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: The application must be run on a queue manager that is compatible with the object definition. Refer to the WebSphere MQ for z/OS Concepts and Planning Guide and the WebSphere MQ for z/OS System Setup Guide for information about compatibility and migration between different versions of the queue manager. 2361 (X'0939')MQRC_NEXT_RECORD_ERROR Explanation: An MQXCLWLN call was issued from a cluster workload exit to obtain the address of the next record in the chain, but the address specified for the NextRecord parameter is either null, not valid, or the address of read-only storage. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) Completion Code: MQCC_FAILED Programmer Response: Specify a valid address for the NextRecord parameter. 2362 (X'093A')MQRC_BACKOUT_THRESHOLD_REACHED Explanation: This reason code occurs only in the Reason field in an MQDLH structure, or in the Feedback field in the MQMD of a report message. A JMS ConnectionConsumer found a message that exceeds the queue's backout threshold. The queue does not have a backout requeue queue defined, so the message was processed as specified by the disposition options in the Report field in the MQMD of the message. On queue managers that do not support the BackoutThreshold and BackoutRequeueQName queue attributes, JMS ConnectionConsumer uses a value of 20 for the backout threshold. When the BackoutCount of a message reaches this threshold, the message is processed as specified by the disposition options. If the Report field specifies one of the MQRO_EXCEPTION_* options, this reason code appears in the Feedback field of the report message. If the Report field specifies MQRO_DEAD_LETTER_Q, or the disposition report options are left as default, this reason code appears in the Reason field of the MQDLH. Completion Code: None Programmer Response: Investigate the cause of the backout count being greater than the threshold. To correct this, define the backout queue for the queue concerned. 2363 (X'093B')MQRC_MSG_NOT_MATCHED Explanation: This reason code occurs only in the Reason field in an MQDLH structure, or in the Feedback field in the MQMD of a report message. While performing Point-to-Point messaging, JMS encountered a message matching none of the selectors of ConnectionConsumers monitoring the queue. To maintain performance, the message was processed as specified by the disposition options in the Report field in the MQMD of the message. If the Report field specifies one of the MQRO_EXCEPTION_* options, this reason code appears in the Feedback field of the report message. If the Report field specifies MQRO_DEAD_LETTER_Q, or the disposition report options are left as default, this reason code appears in the Reason field of the MQDLH. Completion Code: None Programmer Response: To correct this, ensure that the ConnectionConsumers monitoring the queue provide a complete set of selectors. Alternatively, set the QueueConnectionFactory to retain messages. 2364 (X'093C')MQRC_JMS_FORMAT_ERROR Explanation: This reason code is generated when JMS encounters a message that it is unable to parse. If such a message is encountered by a JMS ConnectionConsumer, the message is processed as specified by the disposition options in the Report field in the MQMD of the message. If the Report field specifies one of the MQRO_EXCEPTION_* options, this reason code appears in the Feedback field of the report message. If the Report field specifies MQRO_DEAD_LETTER_Q, or the disposition report options are left as default, this reason code appears in the Reason field of the MQDLH. Completion Code: None Programmer Response: Investigate the origin of the message. 2365 (X'093D')MQRC_SEGMENTS_NOT_SUPPORTED Explanation: An MQPUT call was issued to put a segment of a logical message, but the queue on which the message is to be placed has an IndexType of MQIT_GROUP_ID. Message segments cannot be placed on queues with this index type. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Modify the application to put messages that are not segments; ensure that the MQMF_SEGMENT and MQMF_LAST_SEGMENT flags in the MsgFlags field in MQMD are not set, and that the Offset is zero. Alternatively, change the index type of the queue. 2366 (X'093E')MQRC_WRONG_CF_LEVEL Explanation: An MQOPEN or MQPUT1 call was issued specifying a shared queue, but the queue requires a coupling-facility structure with a different level of capability. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Ensure that the coupling-facility structure used for the queue is at the level required to support the capabilities that the queue provides. 2367 (X'093F')MQRC_CONFIG_CREATE_OBJECT Explanation: This condition is detected when an object is created. Completion Code: MQCC_WARNING Programmer Response: None. This reason code is only used to identify the corresponding event message. 2368 (X'0940')MQRC_CONFIG_CHANGE_OBJECT Explanation: This condition is detected when an object is changed. Completion Code: MQCC_WARNING Programmer Response: None. This reason code is only used to identify the corresponding event message. 2369 (X'0941')MQRC_CONFIG_DELETE_OBJECT Explanation: This condition is detected when an object is deleted. Completion Code: MQCC_WARNING Programmer Response: None. This reason code is only used to identify the corresponding event message. 2370 (X'0942')MQRC_CONFIG_REFRESH_OBJECT Explanation: This condition is detected when an object is refreshed. Completion Code: MQCC_WARNING Programmer Response: None. This reason code is only used to identify the corresponding event message. 2371 (X'0943')MQRC_CHANNEL_SSL_ERROR Explanation: This condition is detected when a connection cannot be established due to an SSL key-exchange or authentication failure. Completion Code: MQCC_WARNING Programmer Response: None. This reason code is only used to identify the corresponding event message. 2373 (X'0945')MQRC_CF_STRUC_FAILED Explanation: An MQI call or command was issued to access a shared queue, but the call failed because the coupling-facility structure used for the shared queue had failed. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Report the problem to the operator or administrator, who should use the MQSC command RECOVER CFSTRUCT to initiate recovery of the coupling-facility structure 2374 (X'0946')MQRC_API_EXIT_ERROR Explanation: An API exit function returned an invalid response code, or failed in some other way. This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows. Completion Code: MQCC_FAILED Programmer Response: Check the exit logic to ensure that the exit is returning valid values in the ExitResponse and ExitResponse2 fields of the MQAXP structure. Consult the FFST record to see if it contains more detail about the problem. 2375 (X'0947')MQRC_API_EXIT_INIT_ERROR Explanation: The queue manager encountered an error while attempting to initialize the execution environment for an API exit function. This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows. Completion Code: MQCC_FAILED Programmer Response: Consult the FFST record to obtain more detail about the problem. 2376 (X'0948')MQRC_API_EXIT_TERM_ERROR Explanation: The queue manager encountered an error while attempting to terminate the execution environment for an API exit function. This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows. Completion Code: MQCC_FAILED Programmer Response: Consult the FFST record to obtain more detail about the problem. 2377 (X'0949')MQRC_EXIT_REASON_ERROR Explanation: An MQXEP call was issued by an API exit function, but the value specified for the ExitReason parameter is either not valid, or not supported for the specified function identifier Function. This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows. Completion Code: MQCC_FAILED Programmer Response: Modify the exit function to specify a value for ExitReason that is valid for the specified value of Function. 2378 (X'094A')MQRC_RESERVED_VALUE_ERROR Explanation: An MQXEP call was issued by an API exit function, but the value specified for the Reserved parameter is not valid. The value must be the null pointer. This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows. Completion Code: MQCC_FAILED Programmer Response: Modify the exit to specify the null pointer as the value of the Reserved parameter. 2379 (X'094B')MQRC_NO_DATA_AVAILABLE Explanation: This reason should be returned by the MQZ_ENUMERATE_AUTHORITY_DATA installable service component when there is no more authority data to return to the invoker of the service component. On z/OS, this reason code does not occur. Completion Code: MQCC_FAILED Programmer Response: None. 2380 (X'094C')MQRC_SCO_ERROR Explanation: On an MQCONNX call, the MQSCO structure is not valid for one of the following reasons: The StrucId field is not MQSCO_STRUC_ID. The Version field is not MQSCO_VERSION_1. This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows. Completion Code: MQCC_FAILED Programmer Response: Correct the definition of the MQSCO structure. 2381 (X'094D')MQRC_KEY_REPOSITORY_ERROR Explanation: On an MQCONN or MQCONNX call, the location of the key repository is either not specified, not valid, or results in an error when used to access the key repository. The location of the key repository is specified by one of the following: The value of the MQSSLKEYR environment variable (MQCONN or MQCONNX call), or The value of the KeyRepository field in the MQSCO structure (MQCONNX call only). For the MQCONNX call, if both MQSSLKEYR and KeyRepository are specified, the latter is used. This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows. Completion Code: MQCC_FAILED Programmer Response: Specify a valid location for the key repository. 2382 (X'094E')MQRC_CRYPTO_HARDWARE_ERROR Explanation: On an MQCONN or MQCONNX call, the configuration string for the cryptographic hardware is not valid, or results in an error when used to configure the cryptographic hardware. The configuration string is specified by one of the following: The value of the MQSSLCRYP environment variable (MQCONN or MQCONNX call), or The value of the CryptoHardware field in the MQSCO structure (MQCONNX call only). For the MQCONNX call, if both MQSSLCRYP and CryptoHardware are specified, the latter is used. This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows. Completion Code: MQCC_FAILED Programmer Response: Specify a valid configuration string for the cryptographic hardware. 2383 (X'094F')MQRC_AUTH_INFO_REC_COUNT_ERROR Explanation: On an MQCONNX call, the AuthInfoRecCount field in the MQSCO structure specifies a value that is less than zero. This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows. Completion Code: MQCC_FAILED Programmer Response: Specify a value for AuthInfoRecCount that is zero or greater. 2384 (X'0950')MQRC_AUTH_INFO_REC_ERROR Explanation: On an MQCONNX call, the MQSCO structure does not specify the address of the MQAIR records correctly. One of the following applies: AuthInfoRecCount is greater than zero, but AuthInfoRecOffset is zero and AuthInfoRecPtr is the null pointer. AuthInfoRecOffset is not zero and AuthInfoRecPtr is not the null pointer. AuthInfoRecPtr is not a valid pointer. AuthInfoRecOffset or AuthInfoRecPtr points to storage that is not accessible. This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows. Completion Code: MQCC_FAILED Programmer Response: Ensure that one of AuthInfoRecOffset or AuthInfoRecPtr is zero and the other nonzero. Ensure that the field used points to accessible storage. 2385 (X'0951')MQRC_AIR_ERROR Explanation: On an MQCONNX call, an MQAIR record is not valid for one of the following reasons: The StrucId field is not MQAIR_STRUC_ID. The Version field is not MQAIR_VERSION_1. This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows. Completion Code: MQCC_FAILED Programmer Response: Correct the definition of the MQAIR record. 2386 (X'0952')MQRC_AUTH_INFO_TYPE_ERROR Explanation: On an MQCONNX call, the AuthInfoType field in an MQAIR record specifies a value that is not valid. This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows. Completion Code: MQCC_FAILED Programmer Response: Specify MQAIT_CRL_LDAP for AuthInfoType. 2387 (X'0953')MQRC_AUTH_INFO_CONN_NAME_ERROR Explanation: On an MQCONNX call, the AuthInfoConnName field in an MQAIR record specifies a value that is not valid. This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows. Completion Code: MQCC_FAILED Programmer Response: Specify a valid connection name. 2388 (X'0954')MQRC_LDAP_USER_NAME_ERROR Explanation: On an MQCONNX call, an LDAP user name in an MQAIR record is not specified correctly. One of the following applies: LDAPUserNameLength is greater than zero, but LDAPUserNameOffset is zero and LDAPUserNamePtr is the null pointer. LDAPUserNameOffset is nonzero and LDAPUserNamePtr is not the null pointer. LDAPUserNamePtr is not a valid pointer. LDAPUserNameOffset or LDAPUserNamePtr points to storage that is not accessible. This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows. Completion Code: MQCC_FAILED Programmer Response: Ensure that one of LDAPUserNameOffset or LDAPUserNamePtr is zero and the other nonzero. Ensure that the field used points to accessible storage. 2389 (X'0955')MQRC_LDAP_USER_NAME_LENGTH_ERR Explanation: On an MQCONNX call, the LDAPUserNameLength field in an MQAIR record specifies a value that is less than zero. This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows. Completion Code: MQCC_FAILED Programmer Response: Specify a value for LDAPUserNameLength that is zero or greater. 2390 (X'0956')MQRC_LDAP_PASSWORD_ERROR Explanation: On an MQCONNX call, the LDAPPassword field in an MQAIR record specifies a value when no value is allowed. This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows. Completion Code: MQCC_FAILED Programmer Response: Specify a value that is blank or null. 2391 (X'0957')MQRC_SSL_ALREADY_INITIALIZED Explanation: An MQCONN or MQCONNX call was issued with SSL configuration options specified, but the SSL environment had already been initialized. The connection to the queue manager completed successfully, but the SSL configuration options specified on the call were ignored; the existing SSL environment was used instead. This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows. Completion Code: MQCC_WARNING Programmer Response: If the application must be run with the SSL configuration options defined on the MQCONN or MQCONNX call, use the MQDISC call to sever the connection to the queue manager and then terminate the application. Alternatively run the application later when the SSL environment has not been initialized. 2392 (X'0958')MQRC_SSL_CONFIG_ERROR Explanation: On an MQCONNX call, the MQCNO structure does not specify the MQSCO structure correctly. One of the following applies: SSLConfigOffset is nonzero and SSLConfigPtr is not the null pointer. SSLConfigPtr is not a valid pointer. SSLConfigOffset or SSLConfigPtr points to storage that is not accessible. This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows. Completion Code: MQCC_FAILED Programmer Response: Ensure that one of SSLConfigOffset or SSLConfigPtr is zero and the other nonzero. Ensure that the field used points to accessible storage. 2393 (X'0959')MQRC_SSL_INITIALIZATION_ERROR Explanation: An MQCONN or MQCONNX call was issued with SSL configuration options specified, but an error occurred during the initialization of the SSL environment. This reason code occurs in the following environments: AIX, HP-UX, Solaris, Windows. Completion Code: MQCC_FAILED Programmer Response: Check that the SSL installation is correct. 2394 (X'095A')MQRC_Q_INDEX_TYPE_ERROR Explanation: An MQGET call was issued specifying one or more of the following options: MQGMO_ALL_MSGS_AVAILABLE MQGMO_ALL_SEGMENTS_AVAILABLE MQGMO_COMPLETE_MSG MQGMO_LOGICAL_ORDER but the call failed because the queue is not indexed by group identifier. These options require the queue to have an IndexType of MQIT_GROUP_ID. This reason code occurs only on z/OS. Completion Code: MQCC_FAILED Programmer Response: Redefine the queue to have an IndexType of MQIT_GROUP_ID. Alternatively, modify the application to avoid using the options listed above. 2395 (X'095B')MQRC_CFBS_ERROR Explanation: An MQPUT or MQPUT1 call was issued, but the message data contains an MQCFBS structure that is not valid. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Check that the fields in the structure are set correctly. 2396 (X'095C')MQRC_SSL_NOT_ALLOWED Explanation: A connection to a queue manager was requested, specifying SSL encryption. However, the connection mode requested is one that does not support SSL (for example, bindings connect). This reason code occurs only with Java applications. Completion Code: MQCC_FAILED Programmer Response: Modify the application to request client connection mode, or to disable SSL encryption. 2397 (X'095D')MQRC_JSSE_ERROR Explanation: JSSE reported an error (for example, while connecting to a queue manager using SSL encryption). The MQException object containing this reason code references the Exception thrown by JSSE; this can be obtained by using the MQException.getCause() method. From JMS, the MQException is linked to the thrown JMSException. This reason code occurs only with Java applications. Completion Code: MQCC_FAILED Programmer Response: Inspect the causal exception to determine the JSSE error. 2398 (X'095E')MQRC_SSL_PEER_NAME_MISMATCH Explanation: The application attempted to connect to the queue manager using SSL encryption, but the distinguished name presented by the queue manager does not match the specified pattern. This reason code occurs only with Java applications. Completion Code: MQCC_FAILED Programmer Response: Check the certificates used to identify the queue manager. Also check the value of the sslPeerName property specified by the application. 2399 (X'095F')MQRC_SSL_PEER_NAME_ERROR Explanation: The application specified a peer name of incorrect format. This reason code occurs only with Java applications. Completion Code: MQCC_FAILED Programmer Response: Check the value of the sslPeerName property specified by the application. 2400 (X'0960')MQRC_UNSUPPORTED_CIPHER_SUITE Explanation: A connection to a queue manager was requested, specifying SSL encryption. However, JSSE reported that it does not support the CipherSuite specified by the application. This reason code occurs only with Java applications. Completion Code: MQCC_FAILED Programmer Response: Check the CipherSuite specified by the application. Note that the names of JSSE CipherSuites differ from their equivalent CipherSpecs used by the queue manager. Also, check that JSSE is correctly installed. 2401 (X'0961')MQRC_SSL_CERTIFICATE_REVOKED Explanation: A connection to a queue manager was requested, specifying SSL encryption. However, the certificate presented by the queue manager was found to be revoked by one of the specified CertStores. This reason code occurs only with Java applications. Completion Code: MQCC_FAILED Programmer Response: Check the certificates used to identify the queue manager. 2402 (X'0962')MQRC_SSL_CERT_STORE_ERROR Explanation: A connection to a queue manager was requested, specifying SSL encryption. However, none of the CertStore objects provided by the application could be searched for the certificate presented by the queue manager. The MQException object containing this reason code references the Exception encountered when searching the first CertStore; this can be obtained using the MQException.getCause() method. From JMS, the MQException is linked to the thrown JMSException. This reason code occurs only with Java applications. Completion Code: MQCC_FAILED Programmer Response: Inspect the causal exception to determine the underlying error. Check the CertStore objects provided by your application. If the causal exception is a java.lang.NoSuchElementException, ensure that your application is not specifying an empty collection of CertStore objects. 2406 (X'0966')MQRC_CLIENT_EXIT_LOAD_ERROR Explanation: The external user exit required for a client connection could not be loaded because the shared library specified for it cannot be found, or the entry point specified for it cannot be found. This reason code occurs only with Java applications. Completion Code: MQCC_FAILED Programmer Response: Ensure that the correct library has been specified, and that the path variable for the machine environment includes the relevant directory. Ensure also that the entry point has been named properly and that the named library does export it. 2407 (X'0967')MQRC_CLIENT_EXIT_ERROR Explanation: A failure occured while executing a non-Java user exit for a client connection. This reason code occurs only with Java applications. Completion Code: MQCC_FAILED Programmer Response: Check that the non-Java user exit can accept the parameters and message being passed to it and that it can handle error conditions, and that any information that the exit requires, such as user data, is correct and available. 2409 (X'0969')MQRC_SSL_KEY_RESET_ERROR Explanation: On an MQCONN or MQCONNX call, the value of the SSL key reset count is not in the valid range of 0 through 999 999 999. The value of the SSL key reset count is specified by either the value of the MQSSLRESET environment variable (MQCONN or MQCONNX call), or the value of the KeyResetCount field in the MQSCO structure (MQCONNX call only). For the MQCONNX call, if both MQSSLRESET and KeyResetCount are specified, the latter is used. MQCONN or MQCONNX Completion Code: MQCC_FAILED Programmer Response: Check that the fields in the structure and the MQSSLRESET environment variable are set correctly. 2411 (X'096B')MQRC_LOGGER_STATUS Explanation: This condition is detected when a logger event occurs. Completion Code: MQCC_WARNING Programmer Response: None. This reason code is only used to identify the corresponding event message. 2412 (X'096C')MQRC_COMMAND_MQSC Explanation: This condition is detected when an MQSC command is executed. Completion Code: MQCC_WARNING Programmer Response: None. This reason code is only used to identify the corresponding event message. 2413 (X'096D')MQRC_COMMAND_PCF Explanation: This condition is detected when a PCF command is executed. Completion Code: MQCC_WARNING Programmer Response: None. This reason code is only used to identify the corresponding event message. 2414 (X'096E')MQRC_CFIF_ERROR Explanation: An MQPUT or MQPUT1 call was issued, but the message data contains an MQCFIF structure that is not valid. This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Check that the fields in the structure are set correctly. 2415 (X'096F')MQRC_CFSF_ERROR Explanation: An MQPUT or MQPUT1 call was issued, but the message data contains an MQCFSF structure that is not valid. This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Check that the fields in the structure are set correctly. 2416 (X'0970')MQRC_CFGR_ERROR Explanation: An MQPUT or MQPUT1 call was issued, but the message data contains an MQCFGR structure that is not valid. This reason code occurs in the following environments: AIX, HP-UX, z/OS, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Check that the fields in the structure are set correctly. 2417 (X'0971')MQRC_MSG_NOT_ALLOWED_IN_GROUP Explanation: An MQPUT or MQPUT1 call was issued to put a message in a group but it is not valid to put such a message in a group. An example of an invalid message is a PCF message where the Type is MQCFT_TRACE_ROUTE. Completion Code: MQCC_FAILED Programmer Response: Remove the invalid message from the group. 2418 (X'0972')MQRC_FILTER_OPERATOR_ERROR Explanation: The Operator parameter supplied is not valid. If it is an input variable then the value is not one of the MQCFOP_* constant values. If it is an output variable then the parameter pointer is not valid, or it points to read-only storage. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredicatable results occur.) Completion Code: MQCC_FAILED Programmer Response: Correct the parameter. 2419 (X'0973')MQRC_NESTED_SELECTOR_ERROR Explanation: An mqAddBag call was issued, but the bag to be nested contained a data item with an inconsistent selector. This reason only occurs if the bag into which the nested bag was to be added was created with the MQCBO_CHECK_SELECTORS option. Completion Code: MQCC_FAILED Programmer Response: Ensure that all data items within the bag to be nested have selectors that are consistent with the data type implied by the item. 2420 (X'0974')MQRC_EPH_ERROR Explanation: An MQPUT or MQPUT1 call was issued, but the message data contains an MQEPH structure that is not valid. Possible errors include the following: The StrucId field is not MQEPH_STRUC_ID. The Version field is not MQEPH_VERSION_1. The StrucLength field specifies a value that is too small to include the structure plus the variable-length data at the end of the structure. The CodedCharSetId field is zero, or a negative value that is not valid. The Flags field contains an invalid combination of MQEPH_* values. The BufferLength parameter of the call has a value that is too small to accommodate the structure, so the structure extends beyond the end of the message. Completion Code: MQCC_FAILED Programmer Response: Check that the fields in the structure are set correctly. Ensure that the application sets the CodedCharSetId field to a valid value; note that MQCCSI_DEFAULT, MQCCSI_EMBEDDED, MQCCSI_Q_MGR, and MQCCSI_UNDEFINED are not valid in this field. 2421 (X'0975')MQRC_RFH_FORMAT_ERROR Explanation: The message contains an MQRFH structure, but its format is incorrect. If you are using WebSphere MQ SOAP, the error is in an incoming SOAP/MQ request message. Completion Code: MQCC_FAILED Programmer Response: If you are using WebSphere MQ SOAP with the IBM-supplied sender, contact your IBM support center. If you are using WebSphere MQ SOAP with a bespoke sender, check that the RFH2 section of the SOAP/MQ request message is in valid RFH2 format. 2422 (X'0976')MQRC_CFBF_ERROR Explanation: An MQPUT or MQPUT1 call was issued, but the message data contains an MQCFBF structure that is not valid. This reason code occurs in the following environments: AIX, HP-UX, OS/2, i5/OS, Solaris, Windows, plus WebSphere MQ clients connected to these systems. Completion Code: MQCC_FAILED Programmer Response: Check that the fields in the structure are set correctly. 2423 (X'0977')MQRC_CLIENT_CHANNEL_CONFLICT Explanation: A client channel definition table was specified for determining the name of the channel, but the name has already been defined. This reason code occurs only with Java applications. Completion Code: MQCC_FAILED Programmer Response: Change the channel name to blank and try again. 6100 (X'17D4')MQRC_REOPEN_EXCL_INPUT_ERROR Explanation: An open object does not have the correct ImqObject open options and requires one or more additional options. An implicit reopen is required but closure has been prevented. Closure has been prevented because the queue is open for exclusive input and closure might result in the queue being accessed by another process or thread, before the queue is reopened by the process or thread that presently has access. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED Programmer Response: Set the open options explicitly to cover all eventualities so that implicit reopening is not required. 6101 (X'17D5')MQRC_REOPEN_INQUIRE_ERROR Explanation: An open object does not have the correct ImqObject open options and requires one or more additional options. An implicit reopen is required but closure has been prevented. Closure has been prevented because one or more characteristics of the object need to be checked dynamically prior to closure, and the open options do not already include MQOO_INQUIRE. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED Programmer Response: Set the open options explicitly to include MQOO_INQUIRE. 6102 (X'17D6')MQRC_REOPEN_SAVED_CONTEXT_ERR Explanation: An open object does not have the correct ImqObject open options and requires one or more additional options. An implicit reopen is required but closure has been prevented. Closure has been prevented because the queue is open with MQOO_SAVE_ALL_CONTEXT, and a destructive get has been performed previously. This has caused retained state information to be associated with the open queue and this information would be destroyed by closure. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED Programmer Response: Set the open options explicitly to cover all eventualities so that implicit reopening is not required. 6103 (X'17D7')MQRC_REOPEN_TEMPORARY_Q_ERROR Explanation: An open object does not have the correct ImqObject open options and requires one or more additional options. An implicit reopen is required but closure has been prevented. Closure has been prevented because the queue is a local queue of the definition type MQQDT_TEMPORARY_DYNAMIC, that would be destroyed by closure. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED Programmer Response: Set the open options explicitly to cover all eventualities so that implicit reopening is not required. 6104 (X'17D8')MQRC_ATTRIBUTE_LOCKED Explanation: An attempt has been made to change the value of an attribute of an object while that object is open, or, for an ImqQueueManager object, while that object is connected. Certain attributes cannot be changed in these circumstances. Close or disconnect the object (as appropriate) before changing the attribute value. An object may have been connected and/or opened unexpectedly and implicitly in order to perform an MQINQ call. Check the attribute cross-reference table in the WebSphere MQ Using C++ book to determine whether any of your method invocations result in an MQINQ call. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED Programmer Response: Include MQOO_INQUIRE in the ImqObject open options and set them earlier. 6105 (X'17D9')MQRC_CURSOR_NOT_VALID Explanation: The browse cursor for an open queue has been invalidated since it was last used by an implicit reopen. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED Programmer Response: Set the ImqObject open options explicitly to cover all eventualities so that implicit reopening is not required. 6106 (X'17DA')MQRC_ENCODING_ERROR Explanation: The encoding of the (next) message item needs to be MQENC_NATIVE for pasting. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED 6107 (X'17DB')MQRC_STRUC_ID_ERROR Explanation: The structure id for the (next) message item, which is derived from the 4 characters beginning at the data pointer, is either missing or is inconsistent with the class of object into which the item is being pasted. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED 6108 (X'17DC')MQRC_NULL_POINTER Explanation: A null pointer has been supplied where a nonnull pointer is either required or implied. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED 6109 (X'17DD')MQRC_NO_CONNECTION_REFERENCE Explanation: The connection reference is null. A connection to an ImqQueueManager object is required. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED 6110 (X'17DE')MQRC_NO_BUFFER Explanation: No buffer is available. For an ImqCache object, one cannot be allocated, denoting an internal inconsistency in the object state that should not occur. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED 6111 (X'17DF')MQRC_BINARY_DATA_LENGTH_ERROR Explanation: The length of the binary data is inconsistent with the length of the target attribute. Zero is a correct length for all attributes. The correct length for an accounting token is MQ_ACCOUNTING_TOKEN_LENGTH. The correct length for an alternate security id is MQ_SECURITY_ID_LENGTH. The correct length for a correlation id is MQ_CORREL_ID_LENGTH. The correct length for a facility token is MQ_FACILITY_LENGTH. The correct length for a group id is MQ_GROUP_ID_LENGTH. The correct length for a message id is MQ_MSG_ID_LENGTH. The correct length for an instance id is MQ_OBJECT_INSTANCE_ID_LENGTH. The correct length for a transaction instance id is MQ_TRAN_INSTANCE_ID_LENGTH. The correct length for a message token is MQ_MSG_TOKEN_LENGTH. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED 6112 (X'17E0')MQRC_BUFFER_NOT_AUTOMATIC Explanation: A user-defined (and managed) buffer cannot be resized. A user-defined buffer can only be replaced or withdrawn. A buffer must be automatic (system-managed) before it can be resized. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED Programmer Response: 6113 (X'17E1')MQRC_INSUFFICIENT_BUFFER Explanation: There is insufficient buffer space available after the data pointer to accommodate the request. This might be because the buffer cannot be resized. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED 6114 (X'17E2')MQRC_INSUFFICIENT_DATA Explanation: There is insufficient data after the data pointer to accommodate the request. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED 6115 (X'17E3')MQRC_DATA_TRUNCATED Explanation: Data has been truncated when copying from one buffer to another. This might be because the target buffer cannot be resized, or because there is a problem addressing one or other buffer, or because a buffer is being downsized with a smaller replacement. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED 6116 (X'17E4')MQRC_ZERO_LENGTH Explanation: A zero length has been supplied where a positive length is either required or implied. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED 6117 (X'17E5')MQRC_NEGATIVE_LENGTH Explanation: A negative length has been supplied where a zero or positive length is required. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED 6118 (X'17E6')MQRC_NEGATIVE_OFFSET Explanation: A negative offset has been supplied where a zero or positive offset is required. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED 6119 (X'17E7')MQRC_INCONSISTENT_FORMAT Explanation: The format of the (next) message item is inconsistent with the class of object into which the item is being pasted. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED 6120 (X'17E8')MQRC_INCONSISTENT_OBJECT_STATE Explanation: There is an inconsistency between this object, which is open, and the referenced ImqQueueManager object, which is not connected. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED 6121 (X'17E9')MQRC_CONTEXT_OBJECT_NOT_VALID Explanation: The ImqPutMessageOptions context reference does not reference a valid ImqQueue object. The object has been previously destroyed. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED 6122 (X'17EA')MQRC_CONTEXT_OPEN_ERROR Explanation: The ImqPutMessageOptions context reference references an ImqQueue object that could not be opened to establish a context. This may be because the ImqQueue object has inappropriate open options. Inspect the referenced object reason code to establish the cause. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED 6123 (X'17EB')MQRC_STRUC_LENGTH_ERROR Explanation: The length of a data structure is inconsistent with its content. For an MQRMH, the length is insufficient to contain the fixed fields and all offset data. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED 6124 (X'17EC')MQRC_NOT_CONNECTED Explanation: A method failed because a required connection to a queue manager was not available, and a connection cannot be established implicitly because the IMQ_IMPL_CONN flag of the ImqQueueManager behavior class attribute is FALSE. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED Programmer Response: Establish a connection to a queue manager and retry. 6125 (X'17ED')MQRC_NOT_OPEN Explanation: A method failed because an object was not open, and opening cannot be accomplished implicitly because the IMQ_IMPL_OPEN flag of the ImqObject behavior class attribute is FALSE. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED Programmer Response: Open the object and retry. 6126 (X'17EE')MQRC_DISTRIBUTION_LIST_EMPTY Explanation: An ImqDistributionList failed to open because there are no ImqQueue objects referenced. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED Programmer Response: Establish at least one ImqQueue object in which the distribution list reference addresses the ImqDistributionList object, and retry. 6127 (X'17EF')MQRC_INCONSISTENT_OPEN_OPTIONS Explanation: A method failed because the object is open, and the ImqObject open options are inconsistent with the required operation. The object cannot be reopened implicitly because the IMQ_IMPL_OPEN flag of the ImqObject behavior class attribute is false. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED Programmer Response: Open the object with appropriate ImqObject open options and retry. 6128 (X'17FO')MQRC_WRONG_VERSION Explanation: A method failed because a version number specified or encountered is either incorrect or not supported. For the ImqCICSBridgeHeader class, the problem is with the version attribute. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED Programmer Response: If you are specifying a version number, use one that is supported by the class. If you are receiving message data from another program, ensure that both programs are using consistent and supported version numbers. 6129 (X'17F1')MQRC_REFERENCE_ERROR Explanation: An object reference is invalid. There is a problem with the address of a referenced object. At the time of use, the address of the object is nonnull, but is invalid and cannot be used for its intended purpose. This reason code occurs in the WebSphere MQ C++ environment. Completion Code: MQCC_FAILED Programmer Response: Check that the referenced object is neither deleted nor out of scope, or remove the reference by supplying a null address value. Reason code cross reference The following is a list of reason codes, in alphabetic order, cross referenced to the full description in numeric order. 2129 (X'0851') MQRC_ADAPTER_CONN_LOAD_ERROR 2133 (X'0855') MQRC_ADAPTER_CONV_LOAD_ERROR 2131 (X'0853') MQRC_ADAPTER_DEFS_ERROR 2132 (X'0854') MQRC_ADAPTER_DEFS_LOAD_ERROR 2138 (X'085A') MQRC_ADAPTER_DISC_LOAD_ERROR 2204 (X'089C') MQRC_ADAPTER_NOT_AVAILABLE 2130 (X'0852') MQRC_ADAPTER_SERV_LOAD_ERROR 2127 (X'084F') MQRC_ADAPTER_STORAGE_SHORTAGE 2385 (X'0951') MQRC_AIR_ERROR 2001 (X'07D1') MQRC_ALIAS_BASE_Q_TYPE_ERROR 2002 (X'07D2') MQRC_ALREADY_CONNECTED 2103 (X'0837') MQRC_ANOTHER_Q_MGR_CONNECTED 2374 (X'0946') MQRC_API_EXIT_ERROR 2375 (X'0947') MQRC_API_EXIT_INIT_ERROR 2183 (X'0887') MQRC_API_EXIT_LOAD_ERROR 2376 (X'0948') MQRC_API_EXIT_TERM_ERROR 900 (X'0384') MQRC_APPL_FIRST 999 (X'03E7') MQRC_APPL_LAST 2157 (X'086D') MQRC_ASID_MISMATCH 6104 (X'17D8') MQRC_ATTRIBUTE_LOCKED 2387 (X'0953') MQRC_AUTH_INFO_CONN_NAME_ERROR 2383 (X'094F') MQRC_AUTH_INFO_REC_COUNT_ERROR 2384 (X'0950') MQRC_AUTH_INFO_REC_ERROR 2386 (X'0952') MQRC_AUTH_INFO_TYPE_ERROR 2003 (X'07D3') MQRC_BACKED_OUT 2362 (X'093A') MQRC_BACKOUT_THRESHOLD_REACHED 2303 (X'08FF') MQRC_BAG_CONVERSION_ERROR 2326 (X'0916') MQRC_BAG_WRONG_TYPE 6111 (X'17DF') MQRC_BINARY_DATA_LENGTH_ERROR 2134 (X'0856') MQRC_BO_ERROR 2125 (X'084D') MQRC_BRIDGE_STARTED 2126 (X'084E') MQRC_BRIDGE_STOPPED 2004 (X'07D4') MQRC_BUFFER_ERROR 2005 (X'07D5') MQRC_BUFFER_LENGTH_ERROR 6112 (X'17E0') MQRC_BUFFER_NOT_AUTOMATIC 2219 (X'08AB') MQRC_CALL_IN_PROGRESS 2277 (X'08E5') MQRC_CD_ERROR 2345 (X'0929') MQRC_CF_NOT_AVAILABLE 2348 (X'092C') MQRC_CF_STRUC_AUTH_FAILED 2349 (X'092D') MQRC_CF_STRUC_ERROR 2373 (X'0945') MQRC_CF_STRUC_FAILED 2346 (X'092A') MQRC_CF_STRUC_IN_USE 2347 (X'092B') MQRC_CF_STRUC_LIST_HDR_IN_USE 2422 (X'0976') MQRC_CFBF_ERROR 2395 (X'095B') MQRC_CFBS_ERROR 2416 (X'0970') MQRC_CFGR_ERROR 2235 (X'08BB') MQRC_CFH_ERROR 2414 (X'096E') MQRC_CFIF_ERROR 2236 (X'08BC') MQRC_CFIL_ERROR 2237 (X'08BD') MQRC_CFIN_ERROR 2415 (X'096F') MQRC_CFSF_ERROR 2238 (X'08BE') MQRC_CFSL_ERROR 2239 (X'08BF') MQRC_CFST_ERROR 2295 (X'08F7') MQRC_CHANNEL_ACTIVATED 2234 (X'08BA') MQRC_CHANNEL_AUTO_DEF_ERROR 2233 (X'08B9') MQRC_CHANNEL_AUTO_DEF_OK 2284 (X'08EC') MQRC_CHANNEL_CONV_ERROR 2296 (X'08F8') MQRC_CHANNEL_NOT_ACTIVATED 2371 (X'0943') MQRC_CHANNEL_SSL_ERROR 2282 (X'08EA') MQRC_CHANNEL_STARTED 2283 (X'08EB') MQRC_CHANNEL_STOPPED 2279 (X'08E7') MQRC_CHANNEL_STOPPED_BY_USER 2006 (X'07D6') MQRC_CHAR_ATTR_LENGTH_ERROR 2007 (X'07D7') MQRC_CHAR_ATTRS_ERROR 2008 (X'07D8') MQRC_CHAR_ATTRS_TOO_SHORT 2340 (X'0924') MQRC_CHAR_CONVERSION_ERROR 2187 (X'088B') MQRC_CICS_BRIDGE_RESTRICTION 2140 (X'085C') MQRC_CICS_WAIT_FAILED 2423 (X'0977') MQRC_CLIENT_CHANNEL_CONFLICT 2278 (X'08E6') MQRC_CLIENT_CONN_ERROR 2407 (X'0967') MQRC_CLIENT_EXIT_ERROR 2406 (X'0966') MQRC_CLIENT_EXIT_LOAD_ERROR 2266 (X'08DA') MQRC_CLUSTER_EXIT_ERROR 2267 (X'08DB') MQRC_CLUSTER_EXIT_LOAD_ERROR 2268 (X'08DC') MQRC_CLUSTER_PUT_INHIBITED 2189 (X'088D') MQRC_CLUSTER_RESOLUTION_ERROR 2269 (X'08DD') MQRC_CLUSTER_RESOURCE_ERROR 2322 (X'0912') MQRC_CMD_SERVER_NOT_AVAILABLE 2139 (X'085B') MQRC_CNO_ERROR 2106 (X'083A') MQRC_COD_NOT_VALID_FOR_XCF_Q 2330 (X'091A') MQRC_CODED_CHAR_SET_ID_ERROR 2412 (X'096C') MQRC_COMMAND_MQSC 2413 (X'096D') MQRC_COMMAND_PCF 2300 (X'08FC') MQRC_COMMAND_TYPE_ERROR 2368 (X'0940') MQRC_CONFIG_CHANGE_OBJECT 2367 (X'093F') MQRC_CONFIG_CREATE_OBJECT 2369 (X'0941') MQRC_CONFIG_DELETE_OBJECT 2370 (X'0942') MQRC_CONFIG_REFRESH_OBJECT 2160 (X'0870') MQRC_CONN_ID_IN_USE 2271 (X'08DF') MQRC_CONN_TAG_IN_USE 2344 (X'0928') MQRC_CONN_TAG_NOT_RELEASED 2350 (X'092E') MQRC_CONN_TAG_NOT_USABLE 2009 (X'07D9') MQRC_CONNECTION_BROKEN 2273 (X'08E1') MQRC_CONNECTION_ERROR 2217 (X'08A9') MQRC_CONNECTION_NOT_AUTHORIZED 2202 (X'089A') MQRC_CONNECTION_QUIESCING 2203 (X'089B') MQRC_CONNECTION_STOPPING 2097 (X'0831') MQRC_CONTEXT_HANDLE_ERROR 2098 (X'0832') MQRC_CONTEXT_NOT_AVAILABLE 6121 (X'17E9') MQRC_CONTEXT_OBJECT_NOT_VALID 6122 (X'17EA') MQRC_CONTEXT_OPEN_ERROR 2120 (X'0848') MQRC_CONVERTED_MSG_TOO_BIG 2190 (X'088E') MQRC_CONVERTED_STRING_TOO_BIG 2207 (X'089F') MQRC_CORREL_ID_ERROR 2382 (X'094E') MQRC_CRYPTO_HARDWARE_ERROR 2357 (X'0935') MQRC_CURRENT_RECORD_ERROR 6105 (X'17D9') MQRC_CURSOR_NOT_VALID 2010 (X'07DA') MQRC_DATA_LENGTH_ERROR 6115 (X'17E3') MQRC_DATA_TRUNCATED 2150 (X'0866') MQRC_DBCS_ERROR 2342 (X'0926') MQRC_DB2_NOT_AVAILABLE 2198 (X'0896') MQRC_DEF_XMIT_Q_TYPE_ERROR 2199 (X'0897') MQRC_DEF_XMIT_Q_USAGE_ERROR 2263 (X'08D7') MQRC_DEST_ENV_ERROR 2264 (X'08D8') MQRC_DEST_NAME_ERROR 2135 (X'0857') MQRC_DH_ERROR 6126 (X'17EE') MQRC_DISTRIBUTION_LIST_EMPTY 2141 (X'085D') MQRC_DLH_ERROR 2163 (X'0873') MQRC_DUPLICATE_RECOV_COORD 2011 (X'07DB') MQRC_DYNAMIC_Q_NAME_ERROR 6106 (X'17DA') MQRC_ENCODING_ERROR 2308 (X'0904') MQRC_ENCODING_NOT_SUPPORTED 2012 (X'07DC') MQRC_ENVIRONMENT_ERROR 2420 (X'0974') MQRC_EPH_ERROR 2377 (X'0949') MQRC_EXIT_REASON_ERROR 2013 (X'07DD') MQRC_EXPIRY_ERROR 2014 (X'07DE') MQRC_FEEDBACK_ERROR 2208 (X'08A0') MQRC_FILE_SYSTEM_ERROR 2418 (X'0972') MQRC_FILTER_OPERATOR_ERROR 2110 (X'083E') MQRC_FORMAT_ERROR 2317 (X'090D') MQRC_FORMAT_NOT_SUPPORTED 2281 (X'08E9') MQRC_FUNCTION_ERROR 2298 (X'08FA') MQRC_FUNCTION_NOT_SUPPORTED 2016 (X'07E0') MQRC_GET_INHIBITED 2351 (X'092F') MQRC_GLOBAL_UOW_CONFLICT 2186 (X'088A') MQRC_GMO_ERROR 2258 (X'08D2') MQRC_GROUP_ID_ERROR 2353 (X'0931') MQRC_HANDLE_IN_USE_FOR_UOW 2017 (X'07E1') MQRC_HANDLE_NOT_AVAILABLE 2320 (X'0910') MQRC_HBAG_ERROR 2280 (X'08E8') MQRC_HCONFIG_ERROR 2018 (X'07E2') MQRC_HCONN_ERROR 2142 (X'085E') MQRC_HEADER_ERROR 2019 (X'07E3') MQRC_HOBJ_ERROR 2148 (X'0864') MQRC_IIH_ERROR 2241 (X'08C1') MQRC_INCOMPLETE_GROUP 2242 (X'08C2') MQRC_INCOMPLETE_MSG 2259 (X'08D3') MQRC_INCONSISTENT_BROWSE 2243 (X'08C3') MQRC_INCONSISTENT_CCSIDS 2244 (X'08C4') MQRC_INCONSISTENT_ENCODINGS 6119 (X'17E7') MQRC_INCONSISTENT_FORMAT 2313 (X'0909') MQRC_INCONSISTENT_ITEM_TYPE 6120 (X'17E8') MQRC_INCONSISTENT_OBJECT_STATE 6127 (X'17EF') MQRC_INCONSISTENT_OPEN_OPTIONS 2185 (X'0889') MQRC_INCONSISTENT_PERSISTENCE 2245 (X'08C5') MQRC_INCONSISTENT_UOW 2314 (X'090A') MQRC_INDEX_ERROR 2306 (X'0902') MQRC_INDEX_NOT_PRESENT 2020 (X'07E4') MQRC_INHIBIT_VALUE_ERROR 2286 (X'08EE') MQRC_INITIALIZATION_FAILED 2324 (X'0914') MQRC_INQUIRY_COMMAND_ERROR 6113 (X'17E1') MQRC_INSUFFICIENT_BUFFER 6114 (X'17E2') MQRC_INSUFFICIENT_DATA 2021 (X'07E5') MQRC_INT_ATTR_COUNT_ERROR 2022 (X'07E6') MQRC_INT_ATTR_COUNT_TOO_SMALL 2023 (X'07E7') MQRC_INT_ATTRS_ARRAY_ERROR 2246 (X'08C6') MQRC_INVALID_MSG_UNDER_CURSOR 2316 (X'090C') MQRC_ITEM_COUNT_ERROR 2327 (X'0917') MQRC_ITEM_TYPE_ERROR 2319 (X'090F') MQRC_ITEM_VALUE_ERROR 2364 (X'093C') MQRC_JMS_FORMAT_ERROR 2397 (X'095D') MQRC_JSSE_ERROR 2381 (X'094D') MQRC_KEY_REPOSITORY_ERROR 2390 (X'0956') MQRC_LDAP_PASSWORD_ERROR 2388 (X'0954') MQRC_LDAP_USER_NAME_ERROR 2389 (X'0955') MQRC_LDAP_USER_NAME_LENGTH_ERR 2352 (X'0930') MQRC_LOCAL_UOW_CONFLICT 2411 (X'096B') MQRC_LOGGER_STATUS 2247 (X'08C7') MQRC_MATCH_OPTIONS_ERROR 2025 (X'07E9') MQRC_MAX_CONNS_LIMIT_REACHED 2026 (X'07EA') MQRC_MD_ERROR 2248 (X'08C8') MQRC_MDE_ERROR 2027 (X'07EB') MQRC_MISSING_REPLY_TO_Q 2332 (X'091C') MQRC_MISSING_WIH 2249 (X'08C9') MQRC_MSG_FLAGS_ERROR 2206 (X'089E') MQRC_MSG_ID_ERROR 2417 (X'0971') MQRC_MSG_NOT_ALLOWED_IN_GROUP 2363 (X'093B') MQRC_MSG_NOT_MATCHED 2250 (X'08CA') MQRC_MSG_SEQ_NUMBER_ERROR 2331 (X'091B') MQRC_MSG_TOKEN_ERROR 2218 (X'08AA') MQRC_MSG_TOO_BIG_FOR_CHANNEL 2030 (X'07EE') MQRC_MSG_TOO_BIG_FOR_Q 2031 (X'07EF') MQRC_MSG_TOO_BIG_FOR_Q_MGR 2029 (X'07ED') MQRC_MSG_TYPE_ERROR 2301 (X'08FD') MQRC_MULTIPLE_INSTANCE_ERROR 2136 (X'0858') MQRC_MULTIPLE_REASONS 2201 (X'0899') MQRC_NAME_IN_USE 2194 (X'0892') MQRC_NAME_NOT_VALID_FOR_TYPE 6117 (X'17E5') MQRC_NEGATIVE_LENGTH 6118 (X'17E6') MQRC_NEGATIVE_OFFSET 2325 (X'0915') MQRC_NESTED_BAG_NOT_SUPPORTED 2419 (X'0973') MQRC_NESTED_SELECTOR_ERROR 2358 (X'0936') MQRC_NEXT_OFFSET_ERROR 2361 (X'0939') MQRC_NEXT_RECORD_ERROR 6110 (X'17DE') MQRC_NO_BUFFER 6109 (X'17DD') MQRC_NO_CONNECTION_REFERENCE 2379 (X'094B') MQRC_NO_DATA_AVAILABLE 2270 (X'08DE') MQRC_NO_DESTINATIONS_AVAILABLE 2121 (X'0849') MQRC_NO_EXTERNAL_PARTICIPANTS 2033 (X'07F1') MQRC_NO_MSG_AVAILABLE 2209 (X'08A1') MQRC_NO_MSG_LOCKED 2034 (X'07F2') MQRC_NO_MSG_UNDER_CURSOR 2359 (X'0937') MQRC_NO_RECORD_AVAILABLE 0 (X'0000') MQRC_NONE 2035 (X'07F3') MQRC_NOT_AUTHORIZED 6124 (X'17EC') MQRC_NOT_CONNECTED 2119 (X'0847') MQRC_NOT_CONVERTED 6125 (X'17ED') MQRC_NOT_OPEN 2036 (X'07F4') MQRC_NOT_OPEN_FOR_BROWSE 2037 (X'07F5') MQRC_NOT_OPEN_FOR_INPUT 2038 (X'07F6') MQRC_NOT_OPEN_FOR_INQUIRE 2039 (X'07F7') MQRC_NOT_OPEN_FOR_OUTPUT 2093 (X'082D') MQRC_NOT_OPEN_FOR_PASS_ALL 2094 (X'082E') MQRC_NOT_OPEN_FOR_PASS_IDENT 2040 (X'07F8') MQRC_NOT_OPEN_FOR_SET 2095 (X'082F') MQRC_NOT_OPEN_FOR_SET_ALL 2096 (X'0830') MQRC_NOT_OPEN_FOR_SET_IDENT 6108 (X'17DC') MQRC_NULL_POINTER 2100 (X'0834') MQRC_OBJECT_ALREADY_EXISTS 2041 (X'07F9') MQRC_OBJECT_CHANGED 2101 (X'0835') MQRC_OBJECT_DAMAGED 2042 (X'07FA') MQRC_OBJECT_IN_USE 2360 (X'0938') MQRC_OBJECT_LEVEL_INCOMPATIBLE 2152 (X'0868') MQRC_OBJECT_NAME_ERROR 2343 (X'0927') MQRC_OBJECT_NOT_UNIQUE 2153 (X'0869') MQRC_OBJECT_Q_MGR_NAME_ERROR 2155 (X'086B') MQRC_OBJECT_RECORDS_ERROR 2043 (X'07FB') MQRC_OBJECT_TYPE_ERROR 2044 (X'07FC') MQRC_OD_ERROR 2251 (X'08CB') MQRC_OFFSET_ERROR 2137 (X'0859') MQRC_OPEN_FAILED 2274 (X'08E2') MQRC_OPTION_ENVIRONMENT_ERROR 2045 (X'07FD') MQRC_OPTION_NOT_VALID_FOR_TYPE 2046 (X'07FE') MQRC_OPTIONS_ERROR 2252 (X'08CC') MQRC_ORIGINAL_LENGTH_ERROR 2310 (X'0906') MQRC_OUT_SELECTOR_ERROR 2123 (X'084B') MQRC_OUTCOME_MIXED 2124 (X'084C') MQRC_OUTCOME_PENDING 2193 (X'0891') MQRC_PAGESET_ERROR 2192 (X'0890') MQRC_PAGESET_FULL 2321 (X'0911') MQRC_PARAMETER_MISSING 2272 (X'08E0') MQRC_PARTIALLY_CONVERTED 2122 (X'084A') MQRC_PARTICIPANT_NOT_AVAILABLE 2149 (X'0865') MQRC_PCF_ERROR 2047 (X'07FF') MQRC_PERSISTENCE_ERROR 2048 (X'0800') MQRC_PERSISTENT_NOT_ALLOWED 2173 (X'087D') MQRC_PMO_ERROR 2158 (X'086E') MQRC_PMO_RECORD_FLAGS_ERROR 2050 (X'0802') MQRC_PRIORITY_ERROR 2049 (X'0801') MQRC_PRIORITY_EXCEEDS_MAXIMUM 2051 (X'0803') MQRC_PUT_INHIBITED 2159 (X'086F') MQRC_PUT_MSG_RECORDS_ERROR 2290 (X'08F2') MQRC_Q_ALREADY_EXISTS 2052 (X'0804') MQRC_Q_DELETED 2224 (X'08B0') MQRC_Q_DEPTH_HIGH 2225 (X'08B1') MQRC_Q_DEPTH_LOW 2053 (X'0805') MQRC_Q_FULL 2394 (X'095A') MQRC_Q_INDEX_TYPE_ERROR 2222 (X'08AE') MQRC_Q_MGR_ACTIVE 2058 (X'080A') MQRC_Q_MGR_NAME_ERROR 2223 (X'08AF') MQRC_Q_MGR_NOT_ACTIVE 2059 (X'080B') MQRC_Q_MGR_NOT_AVAILABLE 2161 (X'0871') MQRC_Q_MGR_QUIESCING 2162 (X'0872') MQRC_Q_MGR_STOPPING 2055 (X'0807') MQRC_Q_NOT_EMPTY 2226 (X'08B2') MQRC_Q_SERVICE_INTERVAL_HIGH 2227 (X'08B3') MQRC_Q_SERVICE_INTERVAL_OK 2056 (X'0808') MQRC_Q_SPACE_NOT_AVAILABLE 2057 (X'0809') MQRC_Q_TYPE_ERROR 2229 (X'08B5') MQRC_RAS_PROPERTY_ERROR 2154 (X'086A') MQRC_RECS_PRESENT_ERROR 6129 (X'17F1') MQRC_REFERENCE_ERROR 2184 (X'0888') MQRC_REMOTE_Q_NAME_ERROR 6100 (X'17D4') MQRC_REOPEN_EXCL_INPUT_ERROR 6101 (X'17D5') MQRC_REOPEN_INQUIRE_ERROR 6102 (X'17D6') MQRC_REOPEN_SAVED_CONTEXT_ERR 6103 (X'17D7') MQRC_REOPEN_TEMPORARY_Q_ERROR 2061 (X'080D') MQRC_REPORT_OPTIONS_ERROR 2378 (X'094A') MQRC_RESERVED_VALUE_ERROR 2102 (X'0836') MQRC_RESOURCE_PROBLEM 2156 (X'086C') MQRC_RESPONSE_RECORDS_ERROR 2336 (X'0920') MQRC_RFH_COMMAND_ERROR 2338 (X'0922') MQRC_RFH_DUPLICATE_PARM 2334 (X'091E') MQRC_RFH_ERROR 2421 (X'0975') MQRC_RFH_FORMAT_ERROR 2228 (X'08B4') MQRC_RFH_HEADER_FIELD_ERROR 2337 (X'0921') MQRC_RFH_PARM_ERROR 2339 (X'0923') MQRC_RFH_PARM_MISSING 2335 (X'091F') MQRC_RFH_STRING_ERROR 2220 (X'08AC') MQRC_RMH_ERROR 2380 (X'094C') MQRC_SCO_ERROR 2062 (X'080E') MQRC_SECOND_MARK_NOT_ALLOWED 2063 (X'080F') MQRC_SECURITY_ERROR 2253 (X'08CD') MQRC_SEGMENT_LENGTH_ZERO 2365 (X'093D') MQRC_SEGMENTS_NOT_SUPPORTED 2065 (X'0811') MQRC_SELECTOR_COUNT_ERROR 2067 (X'0813') MQRC_SELECTOR_ERROR 2066 (X'0812') MQRC_SELECTOR_LIMIT_EXCEEDED 2068 (X'0814') MQRC_SELECTOR_NOT_FOR_TYPE 2309 (X'0905') MQRC_SELECTOR_NOT_PRESENT 2318 (X'090E') MQRC_SELECTOR_NOT_SUPPORTED 2305 (X'0901') MQRC_SELECTOR_NOT_UNIQUE 2304 (X'0900') MQRC_SELECTOR_OUT_OF_RANGE 2299 (X'08FB') MQRC_SELECTOR_TYPE_ERROR 2312 (X'0908') MQRC_SELECTOR_WRONG_TYPE 2289 (X'08F1') MQRC_SERVICE_ERROR 2285 (X'08ED') MQRC_SERVICE_NOT_AVAILABLE 2069 (X'0815') MQRC_SIGNAL_OUTSTANDING 2070 (X'0816') MQRC_SIGNAL_REQUEST_ACCEPTED 2099 (X'0833') MQRC_SIGNAL1_ERROR 2211 (X'08A3') MQRC_SOAP_AXIS_ERROR 2210 (X'08A2') MQRC_SOAP_DOTNET_ERROR 2212 (X'08A4') MQRC_SOAP_URL_ERROR 2145 (X'0861') MQRC_SOURCE_BUFFER_ERROR 2111 (X'083F') MQRC_SOURCE_CCSID_ERROR 2113 (X'0841') MQRC_SOURCE_DECIMAL_ENC_ERROR 2114 (X'0842') MQRC_SOURCE_FLOAT_ENC_ERROR 2112 (X'0840') MQRC_SOURCE_INTEGER_ENC_ERROR 2143 (X'085F') MQRC_SOURCE_LENGTH_ERROR 2261 (X'08D5') MQRC_SRC_ENV_ERROR 2262 (X'08D6') MQRC_SRC_NAME_ERROR 2391 (X'0957') MQRC_SSL_ALREADY_INITIALIZED 2402 (X'0962') MQRC_SSL_CERT_STORE_ERROR 2401 (X'0961') MQRC_SSL_CERTIFICATE_REVOKED 2392 (X'0958') MQRC_SSL_CONFIG_ERROR 2409 (X'0969') MQRC_SSL_KEY_RESET_ERROR 2393 (X'0959') MQRC_SSL_INITIALIZATION_ERROR 2396 (X'095C') MQRC_SSL_NOT_ALLOWED 2399 (X'095F') MQRC_SSL_PEER_NAME_ERROR 2398 (X'095E') MQRC_SSL_PEER_NAME_MISMATCH 2188 (X'088C') MQRC_STOPPED_BY_CLUSTER_EXIT 2105 (X'0839') MQRC_STORAGE_CLASS_ERROR 2192 (X'0890') MQRC_STORAGE_MEDIUM_FULL 2071 (X'0817') MQRC_STORAGE_NOT_AVAILABLE 2307 (X'0903') MQRC_STRING_ERROR 2323 (X'0913') MQRC_STRING_LENGTH_ERROR 2311 (X'0907') MQRC_STRING_TRUNCATED 6107 (X'17DB') MQRC_STRUC_ID_ERROR 6123 (X'17EB') MQRC_STRUC_LENGTH_ERROR 2109 (X'083D') MQRC_SUPPRESSED_BY_EXIT 2024 (X'07E8') MQRC_SYNCPOINT_LIMIT_REACHED 2072 (X'0818') MQRC_SYNCPOINT_NOT_AVAILABLE 2315 (X'090B') MQRC_SYSTEM_BAG_NOT_ALTERABLE 2328 (X'0918') MQRC_SYSTEM_BAG_NOT_DELETABLE 2302 (X'08FE') MQRC_SYSTEM_ITEM_NOT_ALTERABLE 2329 (X'0919') MQRC_SYSTEM_ITEM_NOT_DELETABLE 2146 (X'0862') MQRC_TARGET_BUFFER_ERROR 2115 (X'0843') MQRC_TARGET_CCSID_ERROR 2117 (X'0845') MQRC_TARGET_DECIMAL_ENC_ERROR 2118 (X'0846') MQRC_TARGET_FLOAT_ENC_ERROR 2116 (X'0844') MQRC_TARGET_INTEGER_ENC_ERROR 2144 (X'0860') MQRC_TARGET_LENGTH_ERROR 2287 (X'08EF') MQRC_TERMINATION_FAILED 2265 (X'08D9') MQRC_TM_ERROR 2191 (X'088F') MQRC_TMC_ERROR 2075 (X'081B') MQRC_TRIGGER_CONTROL_ERROR 2076 (X'081C') MQRC_TRIGGER_DEPTH_ERROR 2077 (X'081D') MQRC_TRIGGER_MSG_PRIORITY_ERR 2078 (X'081E') MQRC_TRIGGER_TYPE_ERROR 2079 (X'081F') MQRC_TRUNCATED_MSG_ACCEPTED 2080 (X'0820') MQRC_TRUNCATED_MSG_FAILED 2341 (X'0925') MQRC_UCS2_CONVERSION_ERROR 2195 (X'0893') MQRC_UNEXPECTED_ERROR 2232 (X'08B8') MQRC_UNIT_OF_WORK_NOT_STARTED 2082 (X'0822') MQRC_UNKNOWN_ALIAS_BASE_Q 2197 (X'0895') MQRC_UNKNOWN_DEF_XMIT_Q 2292 (X'08F4') MQRC_UNKNOWN_ENTITY 2085 (X'0825') MQRC_UNKNOWN_OBJECT_NAME 2086 (X'0826') MQRC_UNKNOWN_OBJECT_Q_MGR 2288 (X'08F0') MQRC_UNKNOWN_Q_NAME 2294 (X'08F6') MQRC_UNKNOWN_REF_OBJECT 2087 (X'0827') MQRC_UNKNOWN_REMOTE_Q_MGR 2104 (X'0838') MQRC_UNKNOWN_REPORT_OPTION 2196 (X'0894') MQRC_UNKNOWN_XMIT_Q 2400 (X'0960') MQRC_UNSUPPORTED_CIPHER_SUITE 2297 (X'08F9') MQRC_UOW_CANCELED 2354 (X'0932') MQRC_UOW_ENLISTMENT_ERROR 2128 (X'0850') MQRC_UOW_IN_PROGRESS 2355 (X'0933') MQRC_UOW_MIX_NOT_SUPPORTED 2255 (X'08CF') MQRC_UOW_NOT_AVAILABLE 2291 (X'08F3') MQRC_USER_ID_NOT_AVAILABLE 2090 (X'082A') MQRC_WAIT_INTERVAL_ERROR 2333 (X'091D') MQRC_WIH_ERROR 2366 (X'093E') MQRC_WRONG_CF_LEVEL 2256 (X'08D0') MQRC_WRONG_GMO_VERSION 2257 (X'08D1') MQRC_WRONG_MD_VERSION 6128 (X'17FO') MQRC_WRONG_VERSION 2356 (X'0934') MQRC_WXP_ERROR 2091 (X'082B') MQRC_XMIT_Q_TYPE_ERROR 2092 (X'082C') MQRC_XMIT_Q_USAGE_ERROR 2260 (X'08D4') MQRC_XQH_ERROR 2107 (X'083B') MQRC_XWAIT_CANCELED 2108 (X'083C') MQRC_XWAIT_ERROR 6116 (X'17E4') MQRC_ZERO_LENGTH MQRC_* (Reason Codes) ===================== MQRC_NONE 0 X'00000000' MQRC_APPL_FIRST 900 X'00000384' MQRC_APPL_LAST 999 X'000003E7' MQRC_ALIAS_BASE_Q_TYPE_ERROR 2001 X'000007D1' MQRC_ALREADY_CONNECTED 2002 X'000007D2' MQRC_BACKED_OUT 2003 X'000007D3' MQRC_BUFFER_ERROR 2004 X'000007D4' MQRC_BUFFER_LENGTH_ERROR 2005 X'000007D5' MQRC_CHAR_ATTR_LENGTH_ERROR 2006 X'000007D6' MQRC_CHAR_ATTRS_ERROR 2007 X'000007D7' MQRC_CHAR_ATTRS_TOO_SHORT 2008 X'000007D8' MQRC_CONNECTION_BROKEN 2009 X'000007D9' MQRC_DATA_LENGTH_ERROR 2010 X'000007DA' MQRC_DYNAMIC_Q_NAME_ERROR 2011 X'000007DB' MQRC_ENVIRONMENT_ERROR 2012 X'000007DC' MQRC_EXPIRY_ERROR 2013 X'000007DD' MQRC_FEEDBACK_ERROR 2014 X'000007DE' MQRC_GET_INHIBITED 2016 X'000007E0' MQRC_HANDLE_NOT_AVAILABLE 2017 X'000007E1' MQRC_HCONN_ERROR 2018 X'000007E2' MQRC_HOBJ_ERROR 2019 X'000007E3' MQRC_INHIBIT_VALUE_ERROR 2020 X'000007E4' MQRC_INT_ATTR_COUNT_ERROR 2021 X'000007E5' MQRC_INT_ATTR_COUNT_TOO_SMALL 2022 X'000007E6' MQRC_INT_ATTRS_ARRAY_ERROR 2023 X'000007E7' MQRC_SYNCPOINT_LIMIT_REACHED 2024 X'000007E8' MQRC_MAX_CONNS_LIMIT_REACHED 2025 X'000007E9' MQRC_MD_ERROR 2026 X'000007EA' MQRC_MISSING_REPLY_TO_Q 2027 X'000007EB' MQRC_MSG_TYPE_ERROR 2029 X'000007ED' MQRC_MSG_TOO_BIG_FOR_Q 2030 X'000007EE' MQRC_MSG_TOO_BIG_FOR_Q_MGR 2031 X'000007EF' MQRC_NO_MSG_AVAILABLE 2033 X'000007F1' MQRC_NO_MSG_UNDER_CURSOR 2034 X'000007F2' MQRC_NOT_AUTHORIZED 2035 X'000007F3' MQRC_NOT_OPEN_FOR_BROWSE 2036 X'000007F4' MQRC_NOT_OPEN_FOR_INPUT 2037 X'000007F5' MQRC_NOT_OPEN_FOR_INQUIRE 2038 X'000007F6' MQRC_NOT_OPEN_FOR_OUTPUT 2039 X'000007F7' MQRC_NOT_OPEN_FOR_SET 2040 X'000007F8' MQRC_OBJECT_CHANGED 2041 X'000007F9' MQRC_OBJECT_IN_USE 2042 X'000007FA' MQRC_OBJECT_TYPE_ERROR 2043 X'000007FB' MQRC_OD_ERROR 2044 X'000007FC' MQRC_OPTION_NOT_VALID_FOR_TYPE 2045 X'000007FD' MQRC_OPTIONS_ERROR 2046 X'000007FE' MQRC_PERSISTENCE_ERROR 2047 X'000007FF' MQRC_PERSISTENT_NOT_ALLOWED 2048 X'00000800' MQRC_PRIORITY_EXCEEDS_MAXIMUM 2049 X'00000801' MQRC_PRIORITY_ERROR 2050 X'00000802' MQRC_PUT_INHIBITED 2051 X'00000803' MQRC_Q_DELETED 2052 X'00000804' MQRC_Q_FULL 2053 X'00000805' MQRC_Q_NOT_EMPTY 2055 X'00000807' MQRC_Q_SPACE_NOT_AVAILABLE 2056 X'00000808' MQRC_Q_TYPE_ERROR 2057 X'00000809' MQRC_Q_MGR_NAME_ERROR 2058 X'0000080A' MQRC_Q_MGR_NOT_AVAILABLE 2059 X'0000080B' MQRC_REPORT_OPTIONS_ERROR 2061 X'0000080D' MQRC_SECOND_MARK_NOT_ALLOWED 2062 X'0000080E' MQRC_SECURITY_ERROR 2063 X'0000080F' MQRC_SELECTOR_COUNT_ERROR 2065 X'00000811' MQRC_SELECTOR_LIMIT_EXCEEDED 2066 X'00000812' MQRC_SELECTOR_ERROR 2067 X'00000813' MQRC_SELECTOR_NOT_FOR_TYPE 2068 X'00000814' MQRC_SIGNAL_OUTSTANDING 2069 X'00000815' MQRC_SIGNAL_REQUEST_ACCEPTED 2070 X'00000816' MQRC_STORAGE_NOT_AVAILABLE 2071 X'00000817' MQRC_SYNCPOINT_NOT_AVAILABLE 2072 X'00000818' MQRC_TRIGGER_CONTROL_ERROR 2075 X'0000081B' MQRC_TRIGGER_DEPTH_ERROR 2076 X'0000081C' MQRC_TRIGGER_MSG_PRIORITY_ERR 2077 X'0000081D' MQRC_TRIGGER_TYPE_ERROR 2078 X'0000081E' MQRC_TRUNCATED_MSG_ACCEPTED 2079 X'0000081F' MQRC_TRUNCATED_MSG_FAILED 2080 X'00000820' MQRC_UNKNOWN_ALIAS_BASE_Q 2082 X'00000822' MQRC_UNKNOWN_OBJECT_NAME 2085 X'00000825' MQRC_UNKNOWN_OBJECT_Q_MGR 2086 X'00000826' MQRC_UNKNOWN_REMOTE_Q_MGR 2087 X'00000827' MQRC_WAIT_INTERVAL_ERROR 2090 X'0000082A' MQRC_XMIT_Q_TYPE_ERROR 2091 X'0000082B' MQRC_XMIT_Q_USAGE_ERROR 2092 X'0000082C' MQRC_NOT_OPEN_FOR_PASS_ALL 2093 X'0000082D' MQRC_NOT_OPEN_FOR_PASS_IDENT 2094 X'0000082E' MQRC_NOT_OPEN_FOR_SET_ALL 2095 X'0000082F' MQRC_NOT_OPEN_FOR_SET_IDENT 2096 X'00000830' MQRC_CONTEXT_HANDLE_ERROR 2097 X'00000831' MQRC_CONTEXT_NOT_AVAILABLE 2098 X'00000832' MQRC_SIGNAL1_ERROR 2099 X'00000833' MQRC_OBJECT_ALREADY_EXISTS 2100 X'00000834' MQRC_OBJECT_DAMAGED 2101 X'00000835' MQRC_RESOURCE_PROBLEM 2102 X'00000836' MQRC_ANOTHER_Q_MGR_CONNECTED 2103 X'00000837' MQRC_UNKNOWN_REPORT_OPTION 2104 X'00000838' MQRC_STORAGE_CLASS_ERROR 2105 X'00000839' MQRC_COD_NOT_VALID_FOR_XCF_Q 2106 X'0000083A' MQRC_XWAIT_CANCELED 2107 X'0000083B' MQRC_XWAIT_ERROR 2108 X'0000083C' MQRC_SUPPRESSED_BY_EXIT 2109 X'0000083D' MQRC_FORMAT_ERROR 2110 X'0000083E' MQRC_SOURCE_CCSID_ERROR 2111 X'0000083F' MQRC_SOURCE_INTEGER_ENC_ERROR 2112 X'00000840' MQRC_SOURCE_DECIMAL_ENC_ERROR 2113 X'00000841' MQRC_SOURCE_FLOAT_ENC_ERROR 2114 X'00000842' MQRC_TARGET_CCSID_ERROR 2115 X'00000843' MQRC_TARGET_INTEGER_ENC_ERROR 2116 X'00000844' MQRC_TARGET_DECIMAL_ENC_ERROR 2117 X'00000845' MQRC_TARGET_FLOAT_ENC_ERROR 2118 X'00000846' MQRC_NOT_CONVERTED 2119 X'00000847' MQRC_CONVERTED_MSG_TOO_BIG 2120 X'00000848' MQRC_TRUNCATED 2120 X'00000848' MQRC_NO_EXTERNAL_PARTICIPANTS 2121 X'00000849' MQRC_PARTICIPANT_NOT_AVAILABLE 2122 X'0000084A' MQRC_OUTCOME_MIXED 2123 X'0000084B' MQRC_OUTCOME_PENDING 2124 X'0000084C' MQRC_BRIDGE_STARTED 2125 X'0000084D' MQRC_BRIDGE_STOPPED 2126 X'0000084E' MQRC_ADAPTER_STORAGE_SHORTAGE 2127 X'0000084F' MQRC_UOW_IN_PROGRESS 2128 X'00000850' MQRC_ADAPTER_CONN_LOAD_ERROR 2129 X'00000851' MQRC_ADAPTER_SERV_LOAD_ERROR 2130 X'00000852' MQRC_ADAPTER_DEFS_ERROR 2131 X'00000853' MQRC_ADAPTER_DEFS_LOAD_ERROR 2132 X'00000854' MQRC_ADAPTER_CONV_LOAD_ERROR 2133 X'00000855' MQRC_BO_ERROR 2134 X'00000856' MQRC_DH_ERROR 2135 X'00000857' MQRC_MULTIPLE_REASONS 2136 X'00000858' MQRC_OPEN_FAILED 2137 X'00000859' MQRC_ADAPTER_DISC_LOAD_ERROR 2138 X'0000085A' MQRC_CNO_ERROR 2139 X'0000085B' MQRC_CICS_WAIT_FAILED 2140 X'0000085C' MQRC_DLH_ERROR 2141 X'0000085D' MQRC_HEADER_ERROR 2142 X'0000085E' MQRC_SOURCE_LENGTH_ERROR 2143 X'0000085F' MQRC_TARGET_LENGTH_ERROR 2144 X'00000860' MQRC_SOURCE_BUFFER_ERROR 2145 X'00000861' MQRC_TARGET_BUFFER_ERROR 2146 X'00000862' MQRC_IIH_ERROR 2148 X'00000864' MQRC_PCF_ERROR 2149 X'00000865' MQRC_DBCS_ERROR 2150 X'00000866' MQRC_OBJECT_NAME_ERROR 2152 X'00000868' MQRC_OBJECT_Q_MGR_NAME_ERROR 2153 X'00000869' MQRC_RECS_PRESENT_ERROR 2154 X'0000086A' MQRC_OBJECT_RECORDS_ERROR 2155 X'0000086B' MQRC_RESPONSE_RECORDS_ERROR 2156 X'0000086C' MQRC_ASID_MISMATCH 2157 X'0000086D' MQRC_PMO_RECORD_FLAGS_ERROR 2158 X'0000086E' MQRC_PUT_MSG_RECORDS_ERROR 2159 X'0000086F' MQRC_CONN_ID_IN_USE 2160 X'00000870' MQRC_Q_MGR_QUIESCING 2161 X'00000871' MQRC_Q_MGR_STOPPING 2162 X'00000872' MQRC_DUPLICATE_RECOV_COORD 2163 X'00000873' MQRC_PMO_ERROR 2173 X'0000087D' MQRC_API_EXIT_NOT_FOUND 2182 X'00000886' MQRC_API_EXIT_LOAD_ERROR 2183 X'00000887' MQRC_REMOTE_Q_NAME_ERROR 2184 X'00000888' MQRC_INCONSISTENT_PERSISTENCE 2185 X'00000889' MQRC_GMO_ERROR 2186 X'0000088A' MQRC_CICS_BRIDGE_RESTRICTION 2187 X'0000088B' MQRC_STOPPED_BY_CLUSTER_EXIT 2188 X'0000088C' MQRC_CLUSTER_RESOLUTION_ERROR 2189 X'0000088D' MQRC_CONVERTED_STRING_TOO_BIG 2190 X'0000088E' MQRC_TMC_ERROR 2191 X'0000088F' MQRC_PAGESET_FULL 2192 X'00000890' MQRC_STORAGE_MEDIUM_FULL 2192 X'00000890' MQRC_PAGESET_ERROR 2193 X'00000891' MQRC_NAME_NOT_VALID_FOR_TYPE 2194 X'00000892' MQRC_UNEXPECTED_ERROR 2195 X'00000893' MQRC_UNKNOWN_XMIT_Q 2196 X'00000894' MQRC_UNKNOWN_DEF_XMIT_Q 2197 X'00000895' MQRC_DEF_XMIT_Q_TYPE_ERROR 2198 X'00000896' MQRC_DEF_XMIT_Q_USAGE_ERROR 2199 X'00000897' MQRC_NAME_IN_USE 2201 X'00000899' MQRC_CONNECTION_QUIESCING 2202 X'0000089A' MQRC_CONNECTION_STOPPING 2203 X'0000089B' MQRC_ADAPTER_NOT_AVAILABLE 2204 X'0000089C' MQRC_MSG_ID_ERROR 2206 X'0000089E' MQRC_CORREL_ID_ERROR 2207 X'0000089F' MQRC_FILE_SYSTEM_ERROR 2208 X'000008A0' MQRC_NO_MSG_LOCKED 2209 X'000008A1' MQRC_SOAP_DOTNET_ERROR 2210 X'000008A2' MQRC_SOAP_AXIS_ERROR 2211 X'000008A3' MQRC_SOAP_URL_ERROR 2212 X'000008A4' MQRC_FILE_NOT_AUDITED 2216 X'000008A8' MQRC_CONNECTION_NOT_AUTHORIZED 2217 X'000008A9' MQRC_MSG_TOO_BIG_FOR_CHANNEL 2218 X'000008AA' MQRC_CALL_IN_PROGRESS 2219 X'000008AB' MQRC_RMH_ERROR 2220 X'000008AC' MQRC_Q_MGR_ACTIVE 2222 X'000008AE' MQRC_Q_MGR_NOT_ACTIVE 2223 X'000008AF' MQRC_Q_DEPTH_HIGH 2224 X'000008B0' MQRC_Q_DEPTH_LOW 2225 X'000008B1' MQRC_Q_SERVICE_INTERVAL_HIGH 2226 X'000008B2' MQRC_Q_SERVICE_INTERVAL_OK 2227 X'000008B3' MQRC_RFH_HEADER_FIELD_ERROR 2228 X'000008B4' MQRC_RAS_PROPERTY_ERROR 2229 X'000008B5' MQRC_UNIT_OF_WORK_NOT_STARTED 2232 X'000008B8' MQRC_CHANNEL_AUTO_DEF_OK 2233 X'000008B9' MQRC_CHANNEL_AUTO_DEF_ERROR 2234 X'000008BA' MQRC_CFH_ERROR 2235 X'000008BB' MQRC_CFIL_ERROR 2236 X'000008BC' MQRC_CFIN_ERROR 2237 X'000008BD' MQRC_CFSL_ERROR 2238 X'000008BE' MQRC_CFST_ERROR 2239 X'000008BF' MQRC_INCOMPLETE_GROUP 2241 X'000008C1' MQRC_INCOMPLETE_MSG 2242 X'000008C2' MQRC_INCONSISTENT_CCSIDS 2243 X'000008C3' MQRC_INCONSISTENT_ENCODINGS 2244 X'000008C4' MQRC_INCONSISTENT_UOW 2245 X'000008C5' MQRC_INVALID_MSG_UNDER_CURSOR 2246 X'000008C6' MQRC_MATCH_OPTIONS_ERROR 2247 X'000008C7' MQRC_MDE_ERROR 2248 X'000008C8' MQRC_MSG_FLAGS_ERROR 2249 X'000008C9' MQRC_MSG_SEQ_NUMBER_ERROR 2250 X'000008CA' MQRC_OFFSET_ERROR 2251 X'000008CB' MQRC_ORIGINAL_LENGTH_ERROR 2252 X'000008CC' MQRC_SEGMENT_LENGTH_ZERO 2253 X'000008CD' MQRC_UOW_NOT_AVAILABLE 2255 X'000008CF' MQRC_WRONG_GMO_VERSION 2256 X'000008D0' MQRC_WRONG_MD_VERSION 2257 X'000008D1' MQRC_GROUP_ID_ERROR 2258 X'000008D2' MQRC_INCONSISTENT_BROWSE 2259 X'000008D3' MQRC_XQH_ERROR 2260 X'000008D4' MQRC_SRC_ENV_ERROR 2261 X'000008D5' MQRC_SRC_NAME_ERROR 2262 X'000008D6' MQRC_DEST_ENV_ERROR 2263 X'000008D7' MQRC_DEST_NAME_ERROR 2264 X'000008D8' MQRC_TM_ERROR 2265 X'000008D9' MQRC_CLUSTER_EXIT_ERROR 2266 X'000008DA' MQRC_CLUSTER_EXIT_LOAD_ERROR 2267 X'000008DB' MQRC_CLUSTER_PUT_INHIBITED 2268 X'000008DC' MQRC_CLUSTER_RESOURCE_ERROR 2269 X'000008DD' MQRC_NO_DESTINATIONS_AVAILABLE 2270 X'000008DE' MQRC_CONN_TAG_IN_USE 2271 X'000008DF' MQRC_PARTIALLY_CONVERTED 2272 X'000008E0' MQRC_CONNECTION_ERROR 2273 X'000008E1' MQRC_OPTION_ENVIRONMENT_ERROR 2274 X'000008E2' MQRC_CD_ERROR 2277 X'000008E5' MQRC_CLIENT_CONN_ERROR 2278 X'000008E6' MQRC_CHANNEL_STOPPED_BY_USER 2279 X'000008E7' MQRC_HCONFIG_ERROR 2280 X'000008E8' MQRC_FUNCTION_ERROR 2281 X'000008E9' MQRC_CHANNEL_STARTED 2282 X'000008EA' MQRC_CHANNEL_STOPPED 2283 X'000008EB' MQRC_CHANNEL_CONV_ERROR 2284 X'000008EC' MQRC_SERVICE_NOT_AVAILABLE 2285 X'000008ED' MQRC_INITIALIZATION_FAILED 2286 X'000008EE' MQRC_TERMINATION_FAILED 2287 X'000008EF' MQRC_UNKNOWN_Q_NAME 2288 X'000008F0' MQRC_SERVICE_ERROR 2289 X'000008F1' MQRC_Q_ALREADY_EXISTS 2290 X'000008F2' MQRC_USER_ID_NOT_AVAILABLE 2291 X'000008F3' MQRC_UNKNOWN_ENTITY 2292 X'000008F4' MQRC_UNKNOWN_AUTH_ENTITY 2293 X'000008F5' MQRC_UNKNOWN_REF_OBJECT 2294 X'000008F6' MQRC_CHANNEL_ACTIVATED 2295 X'000008F7' MQRC_CHANNEL_NOT_ACTIVATED 2296 X'000008F8' MQRC_UOW_CANCELED 2297 X'000008F9' MQRC_FUNCTION_NOT_SUPPORTED 2298 X'000008FA' MQRC_SELECTOR_TYPE_ERROR 2299 X'000008FB' MQRC_COMMAND_TYPE_ERROR 2300 X'000008FC' MQRC_MULTIPLE_INSTANCE_ERROR 2301 X'000008FD' MQRC_SYSTEM_ITEM_NOT_ALTERABLE 2302 X'000008FE' MQRC_BAG_CONVERSION_ERROR 2303 X'000008FF' MQRC_SELECTOR_OUT_OF_RANGE 2304 X'00000900' MQRC_SELECTOR_NOT_UNIQUE 2305 X'00000901' MQRC_INDEX_NOT_PRESENT 2306 X'00000902' MQRC_STRING_ERROR 2307 X'00000903' MQRC_ENCODING_NOT_SUPPORTED 2308 X'00000904' MQRC_SELECTOR_NOT_PRESENT 2309 X'00000905' MQRC_OUT_SELECTOR_ERROR 2310 X'00000906' MQRC_STRING_TRUNCATED 2311 X'00000907' MQRC_SELECTOR_WRONG_TYPE 2312 X'00000908' MQRC_INCONSISTENT_ITEM_TYPE 2313 X'00000909' MQRC_INDEX_ERROR 2314 X'0000090A' MQRC_SYSTEM_BAG_NOT_ALTERABLE 2315 X'0000090B' MQRC_ITEM_COUNT_ERROR 2316 X'0000090C' MQRC_FORMAT_NOT_SUPPORTED 2317 X'0000090D' MQRC_SELECTOR_NOT_SUPPORTED 2318 X'0000090E' MQRC_ITEM_VALUE_ERROR 2319 X'0000090F' MQRC_HBAG_ERROR 2320 X'00000910' MQRC_PARAMETER_MISSING 2321 X'00000911' MQRC_CMD_SERVER_NOT_AVAILABLE 2322 X'00000912' MQRC_STRING_LENGTH_ERROR 2323 X'00000913' MQRC_INQUIRY_COMMAND_ERROR 2324 X'00000914' MQRC_NESTED_BAG_NOT_SUPPORTED 2325 X'00000915' MQRC_BAG_WRONG_TYPE 2326 X'00000916' MQRC_ITEM_TYPE_ERROR 2327 X'00000917' MQRC_SYSTEM_BAG_NOT_DELETABLE 2328 X'00000918' MQRC_SYSTEM_ITEM_NOT_DELETABLE 2329 X'00000919' MQRC_CODED_CHAR_SET_ID_ERROR 2330 X'0000091A' MQRC_MSG_TOKEN_ERROR 2331 X'0000091B' MQRC_MISSING_WIH 2332 X'0000091C' MQRC_WIH_ERROR 2333 X'0000091D' MQRC_RFH_ERROR 2334 X'0000091E' MQRC_RFH_STRING_ERROR 2335 X'0000091F' MQRC_RFH_COMMAND_ERROR 2336 X'00000920' MQRC_RFH_PARM_ERROR 2337 X'00000921' MQRC_RFH_DUPLICATE_PARM 2338 X'00000922' MQRC_RFH_PARM_MISSING 2339 X'00000923' MQRC_CHAR_CONVERSION_ERROR 2340 X'00000924' MQRC_UCS2_CONVERSION_ERROR 2341 X'00000925' MQRC_DB2_NOT_AVAILABLE 2342 X'00000926' MQRC_OBJECT_NOT_UNIQUE 2343 X'00000927' MQRC_CONN_TAG_NOT_RELEASED 2344 X'00000928' MQRC_CF_NOT_AVAILABLE 2345 X'00000929' MQRC_CF_STRUC_IN_USE 2346 X'0000092A' MQRC_CF_STRUC_LIST_HDR_IN_USE 2347 X'0000092B' MQRC_CF_STRUC_AUTH_FAILED 2348 X'0000092C' MQRC_CF_STRUC_ERROR 2349 X'0000092D' MQRC_CONN_TAG_NOT_USABLE 2350 X'0000092E' MQRC_GLOBAL_UOW_CONFLICT 2351 X'0000092F' MQRC_LOCAL_UOW_CONFLICT 2352 X'00000930' MQRC_HANDLE_IN_USE_FOR_UOW 2353 X'00000931' MQRC_UOW_ENLISTMENT_ERROR 2354 X'00000932' MQRC_UOW_MIX_NOT_SUPPORTED 2355 X'00000933' MQRC_WXP_ERROR 2356 X'00000934' MQRC_CURRENT_RECORD_ERROR 2357 X'00000935' MQRC_NEXT_OFFSET_ERROR 2358 X'00000936' MQRC_NO_RECORD_AVAILABLE 2359 X'00000937' MQRC_OBJECT_LEVEL_INCOMPATIBLE 2360 X'00000938' MQRC_NEXT_RECORD_ERROR 2361 X'00000939' MQRC_BACKOUT_THRESHOLD_REACHED 2362 X'0000093A' MQRC_MSG_NOT_MATCHED 2363 X'0000093B' MQRC_JMS_FORMAT_ERROR 2364 X'0000093C' MQRC_SEGMENTS_NOT_SUPPORTED 2365 X'0000093D' MQRC_WRONG_CF_LEVEL 2366 X'0000093E' MQRC_CONFIG_CREATE_OBJECT 2367 X'0000093F' MQRC_CONFIG_CHANGE_OBJECT 2368 X'00000940' MQRC_CONFIG_DELETE_OBJECT 2369 X'00000941' MQRC_CONFIG_REFRESH_OBJECT 2370 X'00000942' MQRC_CHANNEL_SSL_ERROR 2371 X'00000943' MQRC_CF_STRUC_FAILED 2373 X'00000945' MQRC_API_EXIT_ERROR 2374 X'00000946' MQRC_API_EXIT_INIT_ERROR 2375 X'00000947' MQRC_API_EXIT_TERM_ERROR 2376 X'00000948' MQRC_EXIT_REASON_ERROR 2377 X'00000949' MQRC_RESERVED_VALUE_ERROR 2378 X'0000094A' MQRC_NO_DATA_AVAILABLE 2379 X'0000094B' MQRC_SCO_ERROR 2380 X'0000094C' MQRC_KEY_REPOSITORY_ERROR 2381 X'0000094D' MQRC_CRYPTO_HARDWARE_ERROR 2382 X'0000094E' MQRC_AUTH_INFO_REC_COUNT_ERROR 2383 X'0000094F' MQRC_AUTH_INFO_REC_ERROR 2384 X'00000950' MQRC_AIR_ERROR 2385 X'00000951' MQRC_AUTH_INFO_TYPE_ERROR 2386 X'00000952' MQRC_AUTH_INFO_CONN_NAME_ERROR 2387 X'00000953' MQRC_LDAP_USER_NAME_ERROR 2388 X'00000954' MQRC_LDAP_USER_NAME_LENGTH_ERR 2389 X'00000955' MQRC_LDAP_PASSWORD_ERROR 2390 X'00000956' MQRC_SSL_ALREADY_INITIALIZED 2391 X'00000957' MQRC_SSL_CONFIG_ERROR 2392 X'00000958' MQRC_SSL_INITIALIZATION_ERROR 2393 X'00000959' MQRC_Q_INDEX_TYPE_ERROR 2394 X'0000095A' MQRC_CFBS_ERROR 2395 X'0000095B' MQRC_SSL_NOT_ALLOWED 2396 X'0000095C' MQRC_JSSE_ERROR 2397 X'0000095D' MQRC_SSL_PEER_NAME_MISMATCH 2398 X'0000095E' MQRC_SSL_PEER_NAME_ERROR 2399 X'0000095F' MQRC_UNSUPPORTED_CIPHER_SUITE 2400 X'00000960' MQRC_SSL_CERTIFICATE_REVOKED 2401 X'00000961' MQRC_SSL_CERT_STORE_ERROR 2402 X'00000962' MQRC_CLIENT_EXIT_LOAD_ERROR 2406 X'00000966' MQRC_CLIENT_EXIT_ERROR 2407 X'00000967' MQRC_SSL_KEY_RESET_ERROR 2409 X'00000969' MQRC_UNKNOWN_COMPONENT_NAME 2410 X'0000096A' MQRC_LOGGER_STATUS 2411 X'0000096B' MQRC_COMMAND_MQSC 2412 X'0000096C' MQRC_COMMAND_PCF 2413 X'0000096D' MQRC_CFIF_ERROR 2414 X'0000096E' MQRC_CFSF_ERROR 2415 X'0000096F' MQRC_CFGR_ERROR 2416 X'00000970' MQRC_MSG_NOT_ALLOWED_IN_GROUP 2417 X'00000971' MQRC_FILTER_OPERATOR_ERROR 2418 X'00000972' MQRC_NESTED_SELECTOR_ERROR 2419 X'00000973' MQRC_EPH_ERROR 2420 X'00000974' MQRC_RFH_FORMAT_ERROR 2421 X'00000975' MQRC_CFBF_ERROR 2422 X'00000976' MQRC_CLIENT_CHANNEL_CONFLICT 2423 X'00000977' MQRC_REOPEN_EXCL_INPUT_ERROR 6100 X'000017D4' MQRC_REOPEN_INQUIRE_ERROR 6101 X'000017D5' MQRC_REOPEN_SAVED_CONTEXT_ERR 6102 X'000017D6' MQRC_REOPEN_TEMPORARY_Q_ERROR 6103 X'000017D7' MQRC_ATTRIBUTE_LOCKED 6104 X'000017D8' MQRC_CURSOR_NOT_VALID 6105 X'000017D9' MQRC_ENCODING_ERROR 6106 X'000017DA' MQRC_STRUC_ID_ERROR 6107 X'000017DB' MQRC_NULL_POINTER 6108 X'000017DC' MQRC_NO_CONNECTION_REFERENCE 6109 X'000017DD' MQRC_NO_BUFFER 6110 X'000017DE' MQRC_BINARY_DATA_LENGTH_ERROR 6111 X'000017DF' MQRC_BUFFER_NOT_AUTOMATIC 6112 X'000017E0' MQRC_INSUFFICIENT_BUFFER 6113 X'000017E1' MQRC_INSUFFICIENT_DATA 6114 X'000017E2' MQRC_DATA_TRUNCATED 6115 X'000017E3' MQRC_ZERO_LENGTH 6116 X'000017E4' MQRC_NEGATIVE_LENGTH 6117 X'000017E5' MQRC_NEGATIVE_OFFSET 6118 X'000017E6' MQRC_INCONSISTENT_FORMAT 6119 X'000017E7' MQRC_INCONSISTENT_OBJECT_STATE 6120 X'000017E8' MQRC_CONTEXT_OBJECT_NOT_VALID 6121 X'000017E9' MQRC_CONTEXT_OPEN_ERROR 6122 X'000017EA' MQRC_STRUC_LENGTH_ERROR 6123 X'000017EB' MQRC_NOT_CONNECTED 6124 X'000017EC' MQRC_NOT_OPEN 6125 X'000017ED' MQRC_DISTRIBUTION_LIST_EMPTY 6126 X'000017EE' MQRC_INCONSISTENT_OPEN_OPTIONS 6127 X'000017EF' MQRC_WRONG_VERSION 6128 X'000017F0' MQRC_REFERENCE_ERROR 6129 X'000017F1' Reason code cross reference =========================== 3091 (X'0C13') MQRCCF_ACTION_VALUE_ERROR 3166 (X'0C5E') MQRCCF_ALLOC_FAST_TIMER_ERROR 3164 (X'0C5C') MQRCCF_ALLOC_RETRY_ERROR 3165 (X'0C5D') MQRCCF_ALLOC_SLOW_TIMER_ERROR 4009 (X'0FA9') MQRCCF_ALLOCATE_FAILED 3157 (X'0C55') MQRCCF_ALREADY_JOINED 4005 (X'0FA5') MQRCCF_ATTR_VALUE_ERROR 3213 (X'0C8D') MQRCCF_ATTR_VALUE_FIXED 3171 (X'0C63') MQRCCF_AUTH_VALUE_ERROR 3172 (X'0C64') MQRCCF_AUTH_VALUE_MISSING 4086 (X'0FF6') MQRCCF_BATCH_INT_ERROR 4087 (X'0FF7') MQRCCF_BATCH_INT_WRONG_TYPE 3037 (X'0BDD') MQRCCF_BATCH_SIZE_ERROR 4024 (X'0FB8') MQRCCF_BIND_FAILED 3094 (X'0C16') MQRCCF_BROKER_COMMAND_FAILED 3070 (X'0BFE') MQRCCF_BROKER_DELETED 3049 (X'0BE9') MQRCCF_CCSID_ERROR 4068 (X'0FE4') MQRCCF_CELL_DIR_NOT_AVAILABLE 3236 (X'0CA4') MQRCCF_CF_STRUC_ERROR 3266 (X'0CC2') MQRCCF_CFBF_FILTER_VAL_LEN_ERR 3264 (X'0CC0') MQRCCF_CFBF_LENGTH_ERROR 3267 (X'0CC3') MQRCCF_CFBF_OPERATOR_ERROR 3265 (X'0CC1') MQRCCF_CFBF_PARM_ID_ERROR 3254 (X'0CB6') MQRCCF_CFBS_DUPLICATE_PARM 3255 (X'0CB7') MQRCCF_CFBS_LENGTH_ERROR 3256 (X'0CB8') MQRCCF_CFBS_PARM_ID_ERROR 3257 (X'0CB9') MQRCCF_CFBS_STRING_LENGTH_ERR 3258 (X'0CBA') MQRCCF_CFGR_LENGTH_ERROR 3259 (X'0CBB') MQRCCF_CFGR_PARM_COUNT_ERROR 3240 (X'0CA8') MQRCCF_CFGR_PARM_ID_ERROR 3007 (X'0BBF') MQRCCF_CFH_COMMAND_ERROR 3005 (X'0BBD') MQRCCF_CFH_CONTROL_ERROR 3002 (X'0BBA') MQRCCF_CFH_LENGTH_ERROR 3004 (X'0BBC') MQRCCF_CFH_MSG_SEQ_NUMBER_ERR 3006 (X'0BBE') MQRCCF_CFH_PARM_COUNT_ERROR 3001 (X'0BB9') MQRCCF_CFH_TYPE_ERROR 3003 (X'0BBB') MQRCCF_CFH_VERSION_ERROR 3241 (X'0CA9') MQRCCF_CFIF_LENGTH_ERROR 3242 (X'0CAA') MQRCCF_CFIF_OPERATOR_ERROR 3243 (X'0CAB') MQRCCF_CFIF_PARM_ID_ERROR 3027 (X'0BD3') MQRCCF_CFIL_COUNT_ERROR 3026 (X'0BD2') MQRCCF_CFIL_DUPLICATE_VALUE 3028 (X'0BD4') MQRCCF_CFIL_LENGTH_ERROR 3047 (X'0BE7') MQRCCF_CFIL_PARM_ID_ERROR 3017 (X'0BC9') MQRCCF_CFIN_DUPLICATE_PARM 3009 (X'0BC1') MQRCCF_CFIN_LENGTH_ERROR 3014 (X'0BC6') MQRCCF_CFIN_PARM_ID_ERROR 3244 (X'0CAC') MQRCCF_CFSF_FILTER_VAL_LEN_ERR 3245 (X'0CAD') MQRCCF_CFSF_LENGTH_ERROR 3246 (X'0CAE') MQRCCF_CFSF_OPERATOR_ERROR 3247 (X'0CAF') MQRCCF_CFSF_PARM_ID_ERROR 3068 (X'0BFC') MQRCCF_CFSL_COUNT_ERROR 3066 (X'0BFA') MQRCCF_CFSL_DUPLICATE_PARM 3024 (X'0BD0') MQRCCF_CFSL_LENGTH_ERROR 3033 (X'0BD9') MQRCCF_CFSL_PARM_ID_ERROR 3069 (X'0BFD') MQRCCF_CFSL_STRING_LENGTH_ERR 3067 (X'0BFB') MQRCCF_CFSL_TOTAL_LENGTH_ERROR 3095 (X'0C17') MQRCCF_CFST_CONFLICTING_PARM 3018 (X'0BCA') MQRCCF_CFST_DUPLICATE_PARM 3010 (X'0BC2') MQRCCF_CFST_LENGTH_ERROR 3015 (X'0BC7') MQRCCF_CFST_PARM_ID_ERROR 3011 (X'0BC3') MQRCCF_CFST_STRING_LENGTH_ERR 4079 (X'0FEF') MQRCCF_CHAD_ERROR 4081 (X'0FF1') MQRCCF_CHAD_EVENT_ERROR 4082 (X'0FF2') MQRCCF_CHAD_EVENT_WRONG_TYPE 4083 (X'0FF3') MQRCCF_CHAD_EXIT_ERROR 4084 (X'0FF4') MQRCCF_CHAD_EXIT_WRONG_TYPE 4080 (X'0FF0') MQRCCF_CHAD_WRONG_TYPE 4042 (X'0FCA') MQRCCF_CHANNEL_ALREADY_EXISTS 4090 (X'0FFA') MQRCCF_CHANNEL_CLOSED 4038 (X'0FC6') MQRCCF_CHANNEL_DISABLED 3235 (X'0CA3') MQRCCF_CHANNEL_ERROR 4031 (X'0FBF') MQRCCF_CHANNEL_IN_USE 4025 (X'0FB9') MQRCCF_CHANNEL_INDOUBT 3218 (X'0C93') MQRCCF_CHANNEL_INITIATOR_ERROR 4044 (X'0FCC') MQRCCF_CHANNEL_NAME_ERROR 4064 (X'0FE0') MQRCCF_CHANNEL_NOT_ACTIVE 4032 (X'0FC0') MQRCCF_CHANNEL_NOT_FOUND 3062 (X'0BF6') MQRCCF_CHANNEL_TABLE_ERROR 3034 (X'0BDA') MQRCCF_CHANNEL_TYPE_ERROR 3064 (X'0BF8') MQRCCF_CHL_INST_TYPE_ERROR 3065 (X'0BF9') MQRCCF_CHL_STATUS_NOT_FOUND 3168 (X'0C60') MQRCCF_CHL_SYSTEM_NOT_ACTIVE 3088 (X'0C10') MQRCCF_CLUSTER_NAME_CONFLICT 3090 (X'0C12') MQRCCF_CLUSTER_Q_USAGE_ERROR 3008 (X'0BC0') MQRCCF_COMMAND_FAILED 3204 (X'0C84') MQRCCF_COMMAND_INHIBITED 3230 (X'0C9E') MQRCCF_COMMAND_LENGTH_ERROR 3222 (X'0C96') MQRCCF_COMMAND_LEVEL_CONFLICT 3231 (X'0C9F') MQRCCF_COMMAND_ORIGIN_ERROR 3226 (X'0C9A') MQRCCF_COMMAND_REPLY_ERROR 3225 (X'0C99') MQRCCF_COMMAND_SCOPE_ERROR 4040 (X'0FC8') MQRCCF_COMMIT_FAILED 3092 (X'0C14') MQRCCF_COMMS_LIBRARY_ERROR 4011 (X'0FAB') MQRCCF_CONFIGURATION_ERROR 4062 (X'0FDE') MQRCCF_CONN_NAME_ERROR 3260 (X'0CBC') MQRCCF_CONN_NOT_STOPPED 4017 (X'0FB1') MQRCCF_CONNECTION_CLOSED 3174 (X'0C66') MQRCCF_CONNECTION_ID_ERROR 4012 (X'0FAC') MQRCCF_CONNECTION_REFUSED 3080 (X'0C08') MQRCCF_CORREL_ID_ERROR 3052 (X'0BEC') MQRCCF_DATA_CONV_VALUE_ERROR 4043 (X'0FCB') MQRCCF_DATA_TOO_LARGE 3087 (X'0C0F') MQRCCF_DEL_OPTIONS_ERROR 3038 (X'0BDE') MQRCCF_DISC_INT_ERROR 4054 (X'0FD6') MQRCCF_DISC_INT_WRONG_TYPE 3163 (X'0C5B') MQRCCF_DISC_RETRY_ERROR 3211 (X'0C8B') MQRCCF_DISPOSITION_CONFLICT 3078 (X'0C06') MQRCCF_DUPLICATE_IDENTITY 3152 (X'0C50') MQRCCF_DUPLICATE_SUBSCRIPTION 4067 (X'0FE3') MQRCCF_DYNAMIC_Q_SCOPE_ERROR 3050 (X'0BEA') MQRCCF_ENCODING_ERROR 3169 (X'0C61') MQRCCF_ENTITY_NAME_MISSING 4013 (X'0FAD') MQRCCF_ENTRY_ERROR 3054 (X'0BEE') MQRCCF_ESCAPE_TYPE_ERROR 3224 (X'0C98') MQRCCF_EVENTS_DISABLED 3162 (X'0C5A') MQRCCF_FILE_NOT_AVAILABLE 3150 (X'0C4E') MQRCCF_FILTER_ERROR 3012 (X'0BC4') MQRCCF_FORCE_VALUE_ERROR 3227 (X'0C9B') MQRCCF_FUNCTION_RESTRICTED 4077 (X'0FED') MQRCCF_HB_INTERVAL_ERROR 4078 (X'0FEE') MQRCCF_HB_INTERVAL_WRONG_TYPE 4010 (X'0FAA') MQRCCF_HOST_NOT_AVAILABLE 3079 (X'0C07') MQRCCF_INCORRECT_Q 3075 (X'0C03') MQRCCF_INCORRECT_STREAM 3053 (X'0BED') MQRCCF_INDOUBT_VALUE_ERROR 4003 (X'0FA3') MQRCCF_LIKE_OBJECT_WRONG_TYPE 3232 (X'0CA0') MQRCCF_LISTENER_CONFLICT 4020 (X'0FB4') MQRCCF_LISTENER_NOT_STARTED 3249 (X'0CB1') MQRCCF_LISTENER_RUNNING 3233 (X'0CA1') MQRCCF_LISTENER_STARTED 3268 (X'0CC4') MQRCCF_LISTENER_STILL_ACTIVE 3234 (X'0CA2') MQRCCF_LISTENER_STOPPED 3175 (X'0C67') MQRCCF_LOG_TYPE_ERROR 3041 (X'0BE1') MQRCCF_LONG_RETRY_ERROR 4057 (X'0FD9') MQRCCF_LONG_RETRY_WRONG_TYPE 3042 (X'0BE2') MQRCCF_LONG_TIMER_ERROR 4058 (X'0FDA') MQRCCF_LONG_TIMER_WRONG_TYPE 3250 (X'0CB2') MQRCCF_LSTR_STATUS_NOT_FOUND 3044 (X'0BE4') MQRCCF_MAX_MSG_LENGTH_ERROR 4047 (X'0FCF') MQRCCF_MCA_NAME_ERROR 4053 (X'0FD5') MQRCCF_MCA_NAME_WRONG_TYPE 3063 (X'0BF7') MQRCCF_MCA_TYPE_ERROR 3023 (X'0BCF') MQRCCF_MD_FORMAT_ERROR 4061 (X'0FDD') MQRCCF_MISSING_CONN_NAME 3029 (X'0BD5') MQRCCF_MODE_VALUE_ERROR 4026 (X'0FBA') MQRCCF_MQCONN_FAILED 4028 (X'0FBC') MQRCCF_MQGET_FAILED 4036 (X'0FC4') MQRCCF_MQINQ_FAILED 4027 (X'0FBB') MQRCCF_MQOPEN_FAILED 4029 (X'0FBD') MQRCCF_MQPUT_FAILED 4063 (X'0FDF') MQRCCF_MQSET_FAILED 4069 (X'0FE5') MQRCCF_MR_COUNT_ERROR 4070 (X'0FE6') MQRCCF_MR_COUNT_WRONG_TYPE 4071 (X'0FE7') MQRCCF_MR_EXIT_NAME_ERROR 4072 (X'0FE8') MQRCCF_MR_EXIT_NAME_WRONG_TYPE 4073 (X'0FE9') MQRCCF_MR_INTERVAL_ERROR 4074 (X'0FEA') MQRCCF_MR_INTERVAL_WRONG_TYPE 4050 (X'0FD2') MQRCCF_MSG_EXIT_NAME_ERROR 3016 (X'0BC8') MQRCCF_MSG_LENGTH_ERROR 3030 (X'0BD6') MQRCCF_MSG_SEQ_NUMBER_ERROR 3048 (X'0BE8') MQRCCF_MSG_TRUNCATED 3215 (X'0C8F') MQRCCF_NAMELIST_ERROR 4088 (X'0FF8') MQRCCF_NET_PRIORITY_ERROR 4089 (X'0FF9') MQRCCF_NET_PRIORITY_WRONG_TYPE 3093 (X'0C15') MQRCCF_NETBIOS_NAME_ERROR 3217 (X'0C91') MQRCCF_NO_CHANNEL_INITIATOR 4019 (X'0FB3') MQRCCF_NO_COMMS_MANAGER 3077 (X'0C05') MQRCCF_NO_RETAINED_MSG 3262 (X'0CBE') MQRCCF_NO_START_CMD 3263 (X'0CBF') MQRCCF_NO_STOP_CMD 4018 (X'0FB2') MQRCCF_NO_STORAGE 3239 (X'0CA7') MQRCCF_NO_XCF_PARTNER 3200 (X'0C80') MQRCCF_NONE_FOUND 3081 (X'0C09') MQRCCF_NOT_AUTHORIZED 3073 (X'0C01') MQRCCF_NOT_REGISTERED 4037 (X'0FC5') MQRCCF_NOT_XMIT_Q 4075 (X'0FEB') MQRCCF_NPM_SPEED_ERROR 4076 (X'0FEC') MQRCCF_NPM_SPEED_WRONG_TYPE 4001 (X'0FA1') MQRCCF_OBJECT_ALREADY_EXISTS 3205 (X'0C85') MQRCCF_OBJECT_BEING_DELETED 3160 (X'0C58') MQRCCF_OBJECT_IN_USE 3209 (X'0C89') MQRCCF_OBJECT_LIMIT_EXCEEDED 4008 (X'0FA8') MQRCCF_OBJECT_NAME_ERROR 3208 (X'0C88') MQRCCF_OBJECT_NAME_RESTRICTED 4004 (X'0FA4') MQRCCF_OBJECT_OPEN 3210 (X'0C8A') MQRCCF_OBJECT_OPEN_FORCE 3173 (X'0C65') MQRCCF_OBJECT_TYPE_MISSING 4002 (X'0FA2') MQRCCF_OBJECT_WRONG_TYPE 3203 (X'0C83') MQRCCF_PARM_CONFLICT 3020 (X'0BCC') MQRCCF_PARM_COUNT_TOO_BIG 3019 (X'0BCB') MQRCCF_PARM_COUNT_TOO_SMALL 3228 (X'0C9C') MQRCCF_PARM_MISSING 3035 (X'0BDB') MQRCCF_PARM_SEQUENCE_ERROR 3097 (X'0C19') MQRCCF_PARM_SYNTAX_ERROR 3229 (X'0C9D') MQRCCF_PARM_VALUE_ERROR 3096 (X'0C18') MQRCCF_PATH_NOT_VALID 3032 (X'0BD8') MQRCCF_PING_DATA_COMPARE_ERROR 3031 (X'0BD7') MQRCCF_PING_DATA_COUNT_ERROR 4030 (X'0FBE') MQRCCF_PING_ERROR 3167 (X'0C5F') MQRCCF_PORT_NUMBER_ERROR 3170 (X'0C62') MQRCCF_PROFILE_NAME_ERROR 3177 (X'0C69') MQRCCF_PROGRAM_AUTH_FAILED 3176 (X'0C68') MQRCCF_PROGRAM_NOT_AVAILABLE 3084 (X'0C0C') MQRCCF_PUB_OPTIONS_ERROR 3046 (X'0BE6') MQRCCF_PURGE_VALUE_ERROR 3045 (X'0BE5') MQRCCF_PUT_AUTH_ERROR 4059 (X'0FDB') MQRCCF_PUT_AUTH_WRONG_TYPE 3098 (X'0C1A') MQRCCF_PWD_LENGTH_ERROR 3021 (X'0BCD') MQRCCF_Q_ALREADY_IN_CELL 3223 (X'0C97') MQRCCF_Q_ATTR_CONFLICT 3086 (X'0C0E') MQRCCF_Q_MGR_CCSID_ERROR 3074 (X'0C02') MQRCCF_Q_MGR_NAME_ERROR 3212 (X'0C8C') MQRCCF_Q_MGR_NOT_IN_QSG 3076 (X'0C04') MQRCCF_Q_NAME_ERROR 3022 (X'0BCE') MQRCCF_Q_TYPE_ERROR 4007 (X'0FA7') MQRCCF_Q_WRONG_TYPE 3029 (X'0BD5') MQRCCF_QUIESCE_VALUE_ERROR 4051 (X'0FD3') MQRCCF_RCV_EXIT_NAME_ERROR 4016 (X'0FB0') MQRCCF_RECEIVE_FAILED 4015 (X'0FAF') MQRCCF_RECEIVED_DATA_ERROR 3083 (X'0C0B') MQRCCF_REG_OPTIONS_ERROR 4035 (X'0FC3') MQRCCF_REMOTE_QM_TERMINATING 4034 (X'0FC2') MQRCCF_REMOTE_QM_UNAVAILABLE 3025 (X'0BD1') MQRCCF_REPLACE_VALUE_ERROR 3089 (X'0C11') MQRCCF_REPOS_NAME_CONFLICT 4095 (X'0FFF') MQRCCF_RETAINED_NOT_SUPPORTED 4049 (X'0FD1') MQRCCF_SEC_EXIT_NAME_ERROR 3202 (X'0C82') MQRCCF_SECURITY_REFRESH_FAILED 3201 (X'0C81') MQRCCF_SECURITY_SWITCH_OFF 4048 (X'0FD0') MQRCCF_SEND_EXIT_NAME_ERROR 4014 (X'0FAE') MQRCCF_SEND_FAILED 3043 (X'0BE3') MQRCCF_SEQ_NUMBER_WRAP_ERROR 3252 (X'0CB4') MQRCCF_SERV_STATUS_NOT_FOUND 3261 (X'0CBD') MQRCCF_SERVICE_REQUEST_PENDING 3251 (X'0CB3') MQRCCF_SERVICE_RUNNING 3253 (X'0CB5') MQRCCF_SERVICE_STOPPED 3039 (X'0BDF') MQRCCF_SHORT_RETRY_ERROR 4055 (X'0FD7') MQRCCF_SHORT_RETRY_WRONG_TYPE 3040 (X'0BE0') MQRCCF_SHORT_TIMER_ERROR 4056 (X'0FD8') MQRCCF_SHORT_TIMER_WRONG_TYPE 4092 (X'0FFC') MQRCCF_SSL_CIPHER_SPEC_ERROR 4094 (X'0FFE') MQRCCF_SSL_CLIENT_AUTH_ERROR 4093 (X'0FFD') MQRCCF_SSL_PEER_NAME_ERROR 3207 (X'0C87') MQRCCF_STORAGE_CLASS_IN_USE 3071 (X'0BFF') MQRCCF_STREAM_ERROR 3013 (X'0BC5') MQRCCF_STRUCTURE_TYPE_ERROR 3154 (X'0C52') MQRCCF_SUB_IDENTITY_ERROR 3153 (X'0C51') MQRCCF_SUB_NAME_ERROR 3155 (X'0C53') MQRCCF_SUBSCRIPTION_IN_USE 3156 (X'0C54') MQRCCF_SUBSCRIPTION_LOCKED 4085 (X'0FF5') MQRCCF_SUPPRESSED_BY_EXIT 4065 (X'0FE1') MQRCCF_TERMINATED_BY_SEC_EXIT 3248 (X'0CB0') MQRCCF_TOO_MANY_FILTERS 3072 (X'0C00') MQRCCF_TOPIC_ERROR 3238 (X'0CA6') MQRCCF_UNEXPECTED_ERROR 3085 (X'0C0D') MQRCCF_UNKNOWN_BROKER 3161 (X'0C59') MQRCCF_UNKNOWN_FILE_NAME 4006 (X'0FA6') MQRCCF_UNKNOWN_Q_MGR 4033 (X'0FC1') MQRCCF_UNKNOWN_REMOTE_CHANNEL 3082 (X'0C0A') MQRCCF_UNKNOWN_STREAM 3237 (X'0CA5') MQRCCF_UNKNOWN_USER_ID 4039 (X'0FC7') MQRCCF_USER_EXIT_NOT_AVAILABLE 4041 (X'0FC9') MQRCCF_WRONG_CHANNEL_TYPE 3151 (X'0C4F') MQRCCF_WRONG_USER 3036 (X'0BDC') MQRCCF_XMIT_PROTOCOL_TYPE_ERR 4045 (X'0FCD') MQRCCF_XMIT_Q_NAME_ERROR 4052 (X'0FD4') MQRCCF_XMIT_Q_NAME_WRONG_TYPE Secure Sockets Layer (SSL) return codes 1 Handle is not valid. 3 An internal error has occured. 4 Insufficient storage is available 5 Handle is in the incorrect state. 6 Key label is not found. 7 No certificates available. 8 Certificate validation error. 9 Cryptographic processing error. 10 ASN processing error. 11 LDAP processing error. 12 An unexpected error has occurred. 102 Error detected while reading key database or SAF key ring. 103 Incorrect key database record format. 106 Incorrect key database password. 109 No certification authority certificates. 201 No key database password supplied. 202 Error detected while opening the key database. 203 Unable to generate temporary key pair 204 Key database password is expired. 302 Connection is active. 401 Certificate is expired or is not valid yet. 402 No SSL cipher specifications. 403 No certificate received from partner. 405 Certificate format is not supported. 406 Error while reading or writing data. 407 Key label does not exist. 408 Key database password is not correct. 410 SSL message format is incorrect. 411 Message authentication code is incorrect. 412 SSL protocol or certificate type is not supported. 413 Certificate signature is incorrect. 414 Certificate is not valid. 415 SSL protocol violation. 416 Permission denied. 417 Self-signed certificate cannot be validated. 420 Socket closed by remote partner. 421 SSL V2 cipher is not valid. 422 SSL V3 cipher is not valid. 427 LDAP is not available. 428 Key entry does not contain a private key. 429 SSL V2 header is not valid. 431 Certificate is revoked. 432 Session renegotiation is not allowed. 433 Key exceeds allowable export size. 434 Certificate key is not compatible with cipher suite. 435 Certification authority is unknown. 436 Certificate revocation list cannot be processed. 437 Connection closed. 438 Internal error reported by remote partner. 439 Unknown alert received from remote partner. 501 Buffer size is not valid. 502 Socket request would block. 503 Socket read request would block. 504 Socket write request would block. 505 Record overflow. 601 Protocol is not SSL V3 or TLS V1. 602 Function identifier is not valid. 701 Attribute identifier is not valid. z/OS and MQ related messages: ============================= Other notes: ============ ------- Note ------- Location of WebSphere MQ error logs: ------------------------------------ Technote (troubleshooting) Problem(Abstract) Directions to find WebSpherer MQ and MQSeriesr error logs. Note: The MQ error logs are by default located in the following directories, however it may have been changed at install time: Resolving the problem The messages that are recorded in the error logs and job logs are the most important information that you can provide when reporting an MQ problem. . Select one of the following platforms to find the location of the MQ error logs: HP NSS i5/OSr OpenVMS UNIXr and Linuxr VSE Windowsr z/OSr HP NSS The WebSphere MQ for HP NSS error logs are located in the following directories: /var/mqm/errors /var/mqm/qmgrs//errors The error log files are named; AMQERR01.LOG, AMQERR02.LOG and AMQERR03.LOG. Notes: If the queue manager name is not known then the error message is written to an error log file in the errors subdirectory. For example, if the default prefix is /usr/ibm/wmq/GA/var/mqm, the error message is written to an error log file in the directory /usr/ibm/wmq/GA/var/mqm/errors If the queue manager name is known, then the error message is written to an error log file in the queue manager's errors directory. i5/OS The WebSphere MQ for i5/OS error logs are located in the following directories: /QIBM/UserData/mqm/qmgrs//errors /QIBM/UserData/mqm/qmgrs/&SYSTEM The error log files are named; AMQERR01.LOG, AMQERR02.LOG and AMQERR03.LOG. OpenVMS The WebSphere MQ HP OpenVMS error logs are located in the following directories: MQS_ROOT:[MQM.ERRORS]AMQERR01.LOG MQS_ROOT:[MQM.QMGRS.QMgrName.ERRORS]AMQERR01.LOG MQS_ROOT:[MQM.QMGRS.$SYSTEM.ERRORS]AMQERR01.LOG The error log files are named; AMQERR01.LOG, AMQERR02.LOG and AMQERR03.LOG. Notes: If an error has occurred with a client application: MQS_ROOT:[MQM.ERRORS]AMQERR01.LOG If the queue manager name is known and the queue manager is available: MQS_ROOT:[MQM.QMGRS.QMgrName.ERRORS]AMQERR01.LOG If the queue manager is not available: MQS_ROOT:[MQM.QMGRS.$SYSTEM.ERRORS]AMQERR01.LOG UNIX and Linux The WebSphere MQ for UNIX error logs are located in the following directories: /var/mqm/errors /var/mqm/qmgrs//errors /var/mqm/qmgrs/@SYSTEM/errors (not used at V6 and higher) The error log files are named; AMQERR01.LOG, AMQERR02.LOG and AMQERR03.LOG. VSE MQSeriesr uses the SYSTEM.LOG queue defined in the global system definition as its primary message log and additional informational messages are output to the VSE console. Typically, these detail starting, stopping, and initializing MQSeries for VSE If the SYSTEM.LOG queue is unavailable, the messages are directed to the CICS CSMT log. These messages should always be reviewed carefully for any error messages. The type of messages included in the SYSTEM.LOG queue can now be controlled by using the 'Log and Trace Settings'. Refer to the MQSeries for VSE System Management Guide, "Queue Manager Log and Trace Settings" on page 74 for details. Note that the types of messages put to the SYSTEM.LOG queue can be controlled using the LOG SETTINGS. When trying to resolve problems, ensure that all messages of all severity are selected to be logged. You can view the contents of the system log using the Master Terminal transaction (MQMT) option 4 (Browse Queue Records). Windows The WebSphere MQ for Windows error logs are located in the following directories. This is the default directory path, however it may have been changed at install time: c:\Program Files\IBM\WebSphere MQ\errors c:\Program Files\IBM\WebSphere MQ\qmgrs\\errors c:\Program Files\IBM\WebSphere MQ\qmgrs\@SYSTEM\errors (not used at V6 and higher) The error log files are named; AMQERR01.LOG, AMQERR02.LOG and AMQERR03.LOG. z/OS The WebSphere MQ for OS/390 and z/OS job logs are located in the following: Syslog MSTR job log CHIN job log The job logs are named; xxxxMSTR, and xxxxCHIN. Where xxxx is the WMQ subsystem identifier (ssid). ------- Note: ------- Article: AMQ9209 and AMQ9228 messages flooding the error log Technote (troubleshooting) Problem(Abstract) Your WebSphere MQ queue manager records many AMQ9209 and AMQ9228 messages despite the fact all of the channels and clients were running normally. Symptom The system error log messages were: AMQ9209: Connection to host 'jtf (9.27.32.32)' closed. AMQ9228: The TCP/IP responder program could not be started. Cause The error messages were caused by a port scanning tool, that runs on the user's network. Each time the scanner connected to the MQ port, the listener would assume a new MQ connection was being established. When the scanner disconnected without sending any data, then MQ wrote the AMQ9209 message to record the error. Because the listener did not know what channel the connection was for, it followed up with a generic AMQ9228 message rather than the more usual AMQ9999 message ("Channel ended abnormally"). Resolving the problem Prevent the port scanner from accessing the WebSphere MQ ports. Historical Number 88709999 Product Alias/Synonym WebSphere MQ WMQ MQSeries ------- Note: ------- ------- Note: ------- thread: Q: Why do I get this error and why do my MDBs quit processing when I get this error? 2008-09-28 00:51:21,859 WARN [org.jboss.mq.server.BasicQueue] Caught unusual exception sending message to receiver. org.jboss.util.threadpool.ThreadPoolFullException: java.lang.InterruptedException at org.jboss.util.threadpool.BasicThreadPool.execute(BasicThreadPool.java:417) at org.jboss.util.threadpool.BasicThreadPool.runTaskWrapper(BasicThreadPool.java:192) at org.jboss.util.threadpool.BasicThreadPool.run(BasicThreadPool.java:212) at org.jboss.util.threadpool.BasicThreadPool.run(BasicThreadPool.java:206) at org.jboss.mq.server.ClientConsumer.queueMessageForSending(ClientConsumer.java:125) at org.jboss.mq.server.BasicQueue.queueMessageForSending(BasicQueue.java:1161) at org.jboss.mq.server.BasicQueue.internalAddMessage(BasicQueue.java:1132) at org.jboss.mq.server.BasicQueue.access $000(BasicQueue.java:76) at org.jboss.mq.server.BasicQueue $AddMessagePostCommitTask.run(BasicQueue.java:1399) at org.jboss.mq.pm.Tx.commit(Tx.java:217) at org.jboss.mq.pm.TxManager.commitTx(TxManager.java:113) at org.jboss.mq.server.JMSDestinationManager.transact(JMSDestinationManager.java:468) at org.jboss.mq.server.ClientMonitorInterceptor.transact(ClientMonitorInterceptor.java:168) at org.jboss.mq.server.JMSServerInterceptorSupport.transact(JMSServerInterceptorSupport.java:126) at org.jboss.mq.security.ServerSecurityInterceptor.transact(ServerSecurityInterceptor.java:197) at org.jboss.mq.server.TracingInterceptor.transact(TracingInterceptor.java:352) at org.jboss.mq.server.JMSServerInvoker.transact(JMSServerInvoker.java:132) at org.jboss.mq.il.uil2.ServerSocketManagerHandler.handleMsg(ServerSocketManagerHandler.java:194) at org.jboss.mq.il.uil2.SocketManager $ReadTask.handleMsg(SocketManager.java:417) at org.jboss.mq.il.uil2.msgs.BaseMsg.run(BaseMsg.java:398) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor $Worker.run(PooledExecutor.java:761) at java.lang.Thread.run()V(Unknown Source) A: You get this error becuase of a bug in the Oswego concurrent libraries. This is an issue that we have worked around in JBoss mq. It is fixed in the community 4.2.3 and it will be fixed in EAP 4.2 CP06. ------- Note: ------- thread: Q: Hi, When I run a java program that connects to MQSeries through a shell script from qsh I get an MQSeries invalid environment error (reason code 2012). 1) Here is the call and results from the shell script: > send.sh MQJE001: Completion Code 2, Reason 2012 JS_LoadAccounts: MQ exception occurred - Completeion code: 2 Reason code: 2012 com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2012 2) When I copy the contents of the shell script (send.sh) and make the call outside of the shell script (still in qsh), it works fine: ===> java -classpath ".:$CLASSPATH:/QIBM/ProdData/mqm/java/lib/com.ibm.mq.jar:/QIBM/P rodData/mqm/java/lib" com.services.JS_LoadAccounts testmsg POD1 POD_TEST œ 3) When I call the class from a CL it also works fine. QMQM and QMQMJAVA are in the library list. Any ideas? Thanks in advance A: What version of operating system are you on? I had this problem on some V5R1 systems, but not all. On a very fast system it would do exactly this, run in QSH as individual commands, but in the .sh it would fail, both in QSH and submitted as a QSH. Frank K. at IBM advised me that it might be a timing level error on the system. When the system was upgraded to V5R2, the problem disappeared. ------- Note: ------- thread: Q: How disable the MQ error 2033 to the stc_lh and stc_is log file on 2/6/2009 7:48 AM Hi all, With Ican 505, we have multiple log MQ error 2033 to the stc_lh log file and to the stc_is log files. Is it possible to disable this error or have you got any ideas to don't log this error, because it's not really an error ? Thanks for your help. A: hi, You can try this code: MQException.logExclude(new Integer(MQException.MQRC_NO_MSG_AVAILABLE)) found here: http://mqseries.net/phpBB2/viewtopic.php?t&H33479&hi ghlight=stderr&sid=8a7f7ccfa56d954da55e3447330eecd 2 Regards A: Hi , this is a faulty logging statement. As far as i know this has never been addressed in any of the update releases. If Eric's suggestion does not work, then there's no way around it.. ------- Note: ------- thread: Q: am accessing MQ via .NET and I get 2059 errors using the conncetion code: ---- MQEnvironment.Hostname = txtMQHost.Text; MQEnvironment.Channel = txtMQChan.Text; MQEnvironment.Port = Convert.ToInt32("1413"); MQEnvironment.UserId = "rhorn"; mqQMgr = new MQQueueManager(txtMQMgr.Text); ---- 2059 error occurs when I try to connect above. Checked all inputs and they are correct. A: Setting UserId may not do what you think it does. Specifying a qmgr name in the MQQueueManager constructor may not do what you think it does. Specifying a qmgr name in the wrong cAsE may not do what you think it does. A: Thanks for the response. But after persisting to the admin., he found that I had the wrong IP address. Knew something wasn't right because I never got a 2059 before. ------- Note: ------- thread: Q: 19-Jul-07 10:32:04 I'm trying to use the MQSC or MQ Series client adapter and am getting the following error when trying to send a message. Any ideas? Thanks, Event Type: Warning Event Source: BizTalk Server 2006 Event Category: BizTalk Server 2006 Event ID: 5740 Date: 07/19/2007 Time: 9:13:16 AM User: N/A Computer: 13694L Description: The adapter "MQSC" raised an error message. Details "The specified module could not be found. (Exception from HRESULT: 0x8007007E)". A: ------- Note: ------- thread: Q: As a very green installer of WebSphere, I am customizing WebSphere MQ 5.3.1 with z/OS 1.6s. I've done very little to change the basic installation. QMGR comes up without any errors. When I start the channel initiator, it fails immediately with the following series of messages on the console: +CSQX090I %CSQ1 CSQXGIP CHINIT parameters ... +CSQX091I %CSQ1 CSQXGIP TRAXSTR=YES, TRAXTBL=2, ADAPS=8, DISPS=5 +CSQX092I %CSQ1 CSQXGIP CURRCHL=200, ACTCHL=200, LSTRTMR=60 CSQX093I +%CSQ1 CSQXGIP TCPCHL=200, TCPKEEP=NO, TCPNAME=TCPIP, 280 TCPTYPE=OESOCKET, OPORTMIN=0, OPORTMAX=0 +CSQX094I %CSQ1 CSQXGIP LU62CHL=200, LUNAME= , LU62ARM= CSQX095I %CSQ1 +CSQXGIP ADOPTMCA=NO, ADOPTCHK=ALL, RCVTIME=X0, RCVTMIN=0 CSQX096I %CSQ1 +CSQXGIP DNSWLM=NO, DNSGROUP= , LUGROUP= CSQX099I %CSQ1 CSQXGIP Client +attachment feature available CSQX007E %CSQ1 CSQXADPI Unable to connect +to queue manager CSQ1, 285 MQCC=2 MQRC=2009 +CSQX140E %CSQ1 CSQXADPI Adapter failed to start CSQX005E %CSQ1 CSQXJST +Channel initiator failed to start IEF402I CSQ1CHIN FAILED IN ADDRESS SPACE 0044 288 SYSTEM ABEND S6C6 - REASON CODE F30905 $HASP310 CSQ1CHIN TERMINATED AT END OF MEMORY I've searched IBMLINK, the MQ manuals, the ques, the logs, the internet, the list... nothing or at least nothing I understand well enough to resolve whatever is wrong. Nothing else is using the port. Security is turned off. All the necessary libraries are APF auth'd and linklisted. It has been a long search and a long day; any ideas would be greatly appreciated. A: Your abend seems to indicate that you have run out of memory as others have pointed out. If it's having problems with ESTAE, the memory in question is likely LSQA memory and probably "below the line" memory. Message "$HASP310 CSQ1CHIN TERMINATED AT END OF MEMORY" hints at this. Go talk with your MVS systems programmer and have him set a slip on the abend to get an SVC dump (if you didn't already get one), and ask him/her to take a look at the dump for/with you. What's likely needed, is a modification to an MVS user exit called IEFUSI. Again, your MVS systems programmer can help. He can code the exit in such a way that slack space "below the line" is left for LSQA. IEFUSI can also limit the amout of storage available "above the line" and that may be the problem as well. Good luck! ------- Note: ------- thread: Q: Hi, I have just installed the Websphere MQSeries 5.3 on Solaris 8. I am trying to verify whether the installation is proper. To do that, I created a created a queue manager using crtmqm Q1.q.manager. After successfully executing that step, that I followed these steps. bash-2.03$ strmqm Q1.QUEUE.MANAGER WebSphere MQ was unable to display an error message 893. bash-2.03$ runmqsc Q1.QUEUE.MANAGER 5724-B41 (C) Copyright IBM Corp. 1994, 2002. ALL RIGHTS RESERVED. AMQ8146: WebSphere MQ queue manager not available. No MQSC commands read. No commands have a syntax error. All valid MQSC commands were processed. bash-2.03$ Can anyone please suggest the reason for getting AMQ8146 ERROR. A: AMQ6119: An internal WebSphere MQ error has occurred (Failed to attach shared memory segment: shmat(ShmId 0x00000e80) [rc=-1 errno=24] Too many open files) EXPLANATION: MQ detected an unexpected error when calling the operating system. The MQ error recording routine has been called. ACTION: Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved. ----- amqxfdcx.c : 671 -------------------------------------------------------- 08/30/06 07:23:58 AM AMQ6184: An internal WebSphere MQ error has occurred on queue manager Q1.QUEUE.MANAGER. EXPLANATION: An error has been detected, and the WebSphere MQ error recording routine has been called. The failing process is process 26050. ACTION: Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved. ----- amqxfdcx.c : 705 -------------------------------------------------------- 08/30/06 07:23:59 AM AMQ6119: An internal WebSphere MQ error has occurred () EXPLANATION: MQ detected an unexpected error when calling the operating system. The MQ error recording routine has been called. ACTION: Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved. ----- amqxfdcx.c : 671 -------------------------------------------------------- 08/30/06 07:23:59 AM AMQ6184: An internal WebSphere MQ error has occurred on queue manager Q1.QUEUE.MANAGER. EXPLANATION: An error has been detected, and the WebSphere MQ error recording routine has been called. The failing process is process 26050. ACTION: Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved. May be this error log help you in resolution of problem. Thanks, ------- Note: ------- thread: Q: > My system send messages to a queue. However, the size of the message > over the default max message size limit(64K). I want to increase the > max message size limit, but I am wondering the impact to the system. > Is there any one have try to increase the max message size of a > queue? A: The default maximum message size is 4 MiB in recent versions of MQ, and I routinely use messages up to 2 MiB without problems. Your MQ administrators have probably set a lower size limit to help them with their capacity planning; I suggest you ask them whether they're happy for you to change it. Regards, ------- Note: ------- thread: Q: Dear All, facing following error :Our IBM WebSphere Work Flow client whenever communicates with AIX server which has the QMGR gives following errors:- MQ Error Log: AMQ6109: An internal WebSphere MQ error has occurred. EXPLANATION: An error has been detected, and the WebSphere MQ error recording routine has been called. ACTION: Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved. ----- amqxfdcx.c : 688 -------------------------------------------------------- 01/05/07 15:54:18 AMQ6183: An internal WebSphere MQ error has occurred. EXPLANATION: An error has been detected, and the WebSphere MQ error recording routine has been called. The failing process is process 975078. ACTION: Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved. QMGR LOG: AMQ9208: Error on receive from host 10.16.17.194. EXPLANATION: An error occurred receiving data from 10.16.17.194 over TCP/IP. This may be due to a communications failure. ACTION: The return code from the TCP/IP (read) call was 73 (X'49'). Record these values and tell the systems administrator. According to above AMQ**** errors we have done the changes in AIX server But we are still getting the above errors Step:1 In /etc/services: add lines: mqseries_1 1460/tcp # MQSeries QM1 mqseries_2 14002/tcp # MQSeries QM2 Step2: In /etc/inetd.conf add lines: mqseries_1 stream tcp nowait mqm /usr/mqm/bin/amcrsta amqcrsta mqseries_2 stream tcp nowait mqm /usr/mqm/bin/amcrsta amqcrsta Step3: Run the inetd super-daemon to recognize the update: inetimp refresh -s inetd ------- Note: ------- article: Recommended Fixes for WebSphere MQ http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg27006037 ------- Note: ------- Display MQ installed, which version dspmqver (pre V6: mqver) Display QueueManagers on a machine dspmq Display QueueManager settings MQSC: DIS QMGR Display Queues, name and type or ALL attributes [optional] MQSC: DIS Q(*) [ALL] Display Queues, specific attribute(s) MQSC: DIS Q(*) CURDEPTH often used attributes: CURDEPTH IPPROCS OPPROCS GET PUT MAXDEPTH MAXMSGL Display non empty Queues MQSC: DIS Q(*) CURDEPTH WHERE(CURDEPTH GT 0) Display Channels, name and type or ALL attributes [optional] MQSC: DIS CHL(*) [ALL] Display Channels, specific attribute(s) MQSC: DIS CHL(*) CONNAME Display Services, name and type or ALL attributes [optional] MQSC: DIS SERVICE(*) [ALL] Display Listener, name and type or ALL attributes [optional] MQSC: DIS LSTR(*) [ALL] Display Log Settings (Windows) amqmdain reg QmgrName -c display -s Log -v * Display Queue Filenames for Queues dspmqfls -m QmgrName -t qlocal * Start / Stop Starting QueueManager strmqm QmgrName Stopping QueueManager endmqm QmgrName return control after end: endmqm -w QmgrName end immediately: endmqm -i QmgrName if all else fails (use with caution!): endmqm -p QmgrName Starting Channel MQSC: START CHL(ChannelName) Stopping Channel MQSC: STOP CHL(ChannelName) set inactive: STOP CHL(ChannelName) mode(quiesce) status(inactive) Starting Service MQSC: START SERVICE(ServiceName) Stopping Service MQSC: STOP SERVICE(ServiceName) Starting Listener MQSC: START LSTR(ListenerName) Stopping Listener MQSC: STOP LSTR(ListenerName) Status Display Channel status or ALL status information [optional] MQSC: DIS CHS(*) [SAVED] [ALL] Display Queue status or ALL status information [optional] MQSC: DIS QS(*) [TYPE(HANDLE)] [ALL] Display Service status or ALL status information [optional] MQSC: DIS SVSTATUS(*) [SAVED] [ALL] Display Listener status or ALL status information [optional] MQSC: DIS LSTATUS(*) [SAVED] [ALL] ------- Note: ------- A access control list (ACL) In computer security, a list associated with an object that identifies all the subjects that can access the object that it is associated with. The list also defines their access rights. Subjects are principals that have explicit permissions (to publish, to subscribe to, and to request persistent delivery of, a publication message) against a topic in the topic tree. The ACLs define the implementation of topic-based security. ACL See access control list. AMI See Application Messaging Interface. Application Messaging Interface (AMI) The programming interface, provided by WebSphere MQ, that defines a high level interface to message queuing services. See also Message Queue Interface (MQI) and Java Message Service (JMS). Applications that use the AMI connect to the broker using WebSphere MQ Enterprise Transport. TOP B bar file See broker archive file. bend point A point that is introduced in a connection between two message flow nodes at which the line that represents the connection changes direction. A bend point can be used to make node alignment and processing logic clearer and more effectively displayed. binary large object (BLOB) A block of bytes of data (for example, the body of a message) that has no discernible meaning, but is treated as one solid entity that cannot be interpreted. BLOB See binary large object. broker A set of execution processes that host one or more message flows. Also known as message broker. broker archive file The unit of deployment to the broker; also known as a bar file. It contains any number of different files, including compiled message flows (.cmf). It can also contain any additional files that you might need, provided that the extension does not overlap the .cmf extensions. broker domain A collection of brokers that share a common configuration, together with the Configuration Manager that controls them. broker schema A symbol space that defines the scope of uniqueness of the names of resources (message flows) that are defined within it. built-in node A message flow node that is supplied by the product. Some of the supplied nodes provide basic processing such as input and output. TOP C cmf See compiled message flow. collective A set of brokers that are fully interconnected and form part of a multi-broker network for publish/subscribe applications. compiled message flow (cmf) A message flow that has been compiled to prepare it for deployment to the broker. A cmf file is sent to the broker within a bar file. component A set of runtime processes that perform a specific set of functions. A component is a broker, a Configuration Manager, a Database Instance Manager, or a User Name Server. component directory In z/OS, the root directory of the component's runtime environment. component name The external name of a component. Each component requires a name, which is used, for example, in the workbench and in commands. component PDSE In a z/OS environment, a PDSE that contains jobs to define resources to DB2, WebSphere MQ, and the WebSphere Event Broker started task. See partitioned data set. configuration In a broker domain, the brokers, execution groups, deployed message flows, and defined topics and access control lists. Configuration Manager The component that provides an interface between the workbench and a set of runtime brokers. It provides brokers with their initial configuration, and updates them with any subsequent changes. It maintains the broker domain configuration. Configuration Manager Proxy An application programming interface that your applications can use to control broker domains through a remote interface to the Configuration Manager. connection See message flow node connection. For broker-to-broker connections, see publish/subscribe topology. content-based filter In publish/subscribe, an expression that is included as part of a subscription to determine whether a publication message is received based on its content. The expression can include wild cards. TOP D Database Instance Manager On Windows, a network server that supports the creation, maintenance, and deletion of databases used by brokers in all installations on a single computer. Database support is limited to Derby and DB2. The Database Instance Manager is associated with a Windows service. DataFlowEngine (DFE) See execution group. datagram A form of asynchronous messaging in which an application sends a message, but does not want a response. Also known as send-and-forget. Contrast with request/reply. deploy The process of transferring data to an execution group on a broker so that it can take effect in the broker domain. For deploying message flows and associated resources, the data is packaged in a broker archive (bar) file before being sent to the Configuration Manager, from where it is unpackaged and distributed appropriately. Derby The database based on the Apache Derby open source project from Apache Software Foundation. Derby database support is embedded in the broker component on Windows only. distribution list A list of WebSphere MQ queues to which a message can be put with a single statement. TOP E editor area The area in the workbench window where files are opened for editing. ESM See external security manager. execution group A named grouping of message flows that have been assigned to a broker. The broker enforces a degree of isolation between message flows in distinct execution groups by ensuring that they execute in separate address spaces, or as unique processes. An execution group process is also known as a DataFlowEngine (DFE); this term is typically used in problem determination scenarios (trace contents, diagnostic messages, and so on). A DFE is created as an operating system process, and has a one-to-one relationship with the named execution group. If more than one message flow runs within an execution group, multiple threads are created within the DFE process. Extensible Markup Language (XML) A standard metalanguage for defining markup languages that is based on Standard Generalized Markup Language (SGML). External Security Manager (ESM) In a z/OSr environment, a security product that performs security checking on users and resources. RACF is an example of an ESM. TOP G graphical user interface (GUI) A type of computer interface that presents a visual metaphor of a real-world scene, often of a desktop, by combining high-resolution graphics, pointing devices, menu bars and other menus, overlapping windows, icons, and the object-action relationship. GUI See graphical user interface. TOP I IBM Runtime Environment for Java A subset of the IBM Developer Kit for the Java Platform that contains the core executable files and other files that constitute the standard Java platform. The IBM Runtime Environment includes the Java virtual machine (JVM), core classes, and supporting files. IBM Software Developer Kit for Java A software package that can be used to write, compile, debug, and run Java applets and applications. input node A message flow node that represents a source of messages for a message flow or subflow. See also output node. install_dir The location in the local file system in which product components have been installed. For example, the default location for runtime components on Windows is C:\Program Files\IBM\6.0. installation directory In a z/OS environment, a file system into which all product data is installed, and from which it is referenced and retrieved during the customization phase. TOP J Java Database Connectivity (JDBC) An industry standard for database-independent connectivity between the Java platform and a wide range of databases. The JDBC interface provides a call-level API for SQL-based and XQuery-based database access. See also Open Database Connectivity. Java Message Service (JMS) An application programming interface that provides Java language functions for handling messages. See also Application Messaging Interface (AMI) and Message Queue Interface (MQI). Applications using JMS connect to the broker using either WebSphere MQ Real-time Transport or WebSphere MQ Multicast Transport. JCL See Job Control Language JDBC See Java Database Connectivity. JMS See Java Message Service. Job Control Language Job Control Language (JCL) comprises a set of Job Control Statements that are used to define work requests called jobs. JCL tells the operating system what program to run, and defines its inputs and outputs. TOP L local error log A generic term that refers to the logs to which WebSphere Event Broker writes records on the local system. Also known as the system log. TOP M message A communication that is sent from a person or program to another person or program. In WebSphere Event Broker, messages must have a structure and format which is agreed by the sending and receiving applications. message broker See broker. Message Brokers Toolkit The WebSphere Event Broker development environment that integrates with Rational Application Developer which is based on the IBM WebSphere Eclipse Platform. Also known as the workbench. message flow A sequence of processing steps that run in the broker when an input message is received. A message flow is created in the workbench by including a number of message flow nodes that each represents a set of actions that define a processing step. The connections in the flow determine which processing steps are carried out, in which order, and under which conditions. A message flow must include an input node that provides the source of the messages that are processed. Message flows are then ready to deploy to a broker for execution. See also subflow. message flow node A processing step in a message flow, also called a message processing node. A message flow node can be a built-in node, a user-defined node, or a subflow node. message flow node connection An entity that connects an output terminal of one message flow node to an input terminal of another. A message flow node connection represents the flow of control and data between two message flow nodes. message parser A program that interprets an incoming message and creates an internal representation of the message in a tree structure, and that regenerates a bit stream for an outgoing message from the internal representation. message processing node See message flow node. Message Queue Interface (MQI) The programming interface that is provided by WebSphere MQ queue managers. The programming interface allows application programs to access message queuing services. See also Application Messaging Interface (AMI) and Java Message Service (JMS). Applications that use the MQI, connect to the broker using WebSphere MQ Enterprise Transport. metadata The data that describes the characteristic of stored data. MQI See Message Queue Interface. MQIsdp See SCADA device protocol. MQRFH An architected message header that is used to provide metadata for the processing of a message. This header is supported by the WebSphere MQ (MQSeriesr) Publish/Subscribe SupportPac. MQRFH2 An extended version of MQRFH, providing enhanced function in message processing. multilevel wild card A wild card that can be specified in subscriptions to match any number of levels in a topic. TOP N node An endpoint or junction used in a message flow. See message flow node. TOP O ODBC See Open Database Connectivity. Open Database Connectivity (ODBC) A standard application programming interface (API) for accessing data in both relational and non-relational database management systems. Using this API, database applications can access data stored in database management systems on a variety of computers even if each database management system uses a different data storage format and programming interface. output node A message flow node that represents a point at which messages leave the message flow or subflow. See also input node. TOP P parser See message parser. partitioned data set (PDS, PDSE) In a z/OS environment, a data set in direct-access storage that is divided into partitions, which are called members. A partitioned data set (extended) (PDSE) is an extension to a PDS that contains an indexed directory in addition to the members. PDS, PDSE See partitioned data set. perspective A group of views that show various aspects of the resources in the workbench. See also view. point-to-point A style of messaging application in which the sending application knows the destination of the message. Contrast with publish/subscribe. principal An individual user ID (for example, a login ID) or a group. A group can contain individual user IDs and other groups, to the level of nesting that is supported by the underlying facility. property A characteristic that, as one of a set of characteristics, defines the values and behaviors of objects in the workbench. For example, message flow nodes and deployed message flows have properties. publication A piece of information about a specified topic that is available to a broker in a publish/subscribe system. publication node An end point of a specific path through a message flow to which a client application subscribes, identified to the client by its subscription point. publisher An application that makes information about a specified topic available to a broker in a publish/subscribe system. publish/subscribe A style of messaging application in which the providers of information (publishers) are de-coupled from the consumers of that information (subscribers) using a broker. See also topic. Contrast with point-to-point messaging. publish/subscribe topology The brokers, the collectives, and the connections between them, that support publish/subscribe applications in the broker domain. TOP Q queue A WebSphere MQ object to which message queuing applications can put messages, and from which message queuing applications can get messages. queue manager A system program that provides queuing services to applications. A queue manager provides an application programming interface (the MQI) that enables programs to access messages on the queues that the queue manager owns. TOP R request/reply A type of messaging application in which a request message is used to request a reply from another application. Contrast with datagram. resource A file of any type that exists in the workbench. You can view and edit a resource in the Broker Development view (previously called the Resource Navigator view) in the workbench. Resource Recovery Services (RRS) A z/OS facility that provides two-phase sync point support across participating resource managers. retained publication A published message that is kept at the broker for propagation to clients that subscribe in the future. RRS See Resource Recovery Services. TOP S SCADA See Supervisory, Control, And Data Acquisition. SCADA device protocol (MQIsdp) A protocol that implements the WebSphere MQ Telemetry Transport to connect SCADA devices to the broker. send-and-forget See datagram. single-level wild card A wild card that can be specified in subscriptions to match a single level in a topic. stream A method of topic partitioning that is used by applications that connect to WebSphere MQ Publish/Subscribe brokers. subflow A sequence of processing steps, implemented by message flow nodes, that is designed to be embedded in a message flow or in another subflow. A subflow must include at least one Input or Output node. A subflow can be started by a broker only as part of the message flow in which it is embedded, and therefore cannot be deployed. subflow node A message flow node that represents a subflow. subscriber An application that requests information about a specified topic from a publish/subscribe broker. subscription A record that contains the information that a subscriber passes to its local broker to describe the publications that it wants to receive. subscription filter A predicate that specifies the subset of messages that are to be delivered to a particular subscriber. subscription point The name that a subscriber uses to request publications from a particular set of publication nodes. It is the property of a publication node that differentiates that publication node from other publication nodes in the same message flow. Supervisory, Control, And Data Acquisition (SCADA) A term used to describe any form of remote telemetry system that is used to gather data from remote sensor devices (for example, flow rate meters on an oil pipeline) and for the near real time control of remote equipment (for example, pipeline valves). These devices communicate with the broker using the SCADA device protocol (MQIsdp). system log See local error log. TOP T terminal The point at which one node in a message flow is connected to another node. You can connect terminals to control the route that a message takes, dependent on the outcome of the operation that is performed on that message by the node. topic A character string that describes the nature of the data that is published in a publish/subscribe system. topic based subscription A subscription specified by a subscribing application that includes a topic that filters publications. topic security The application of ACLs to one or more topics to control subscriber access to published messages. topology See publish/subscribe topology. TOP U Unicode Transformation Format, 8-bit encoding form (UTF-8) A transformation format that is designed for ease of use with existing ASCII-based systems. UTF-8 is an encoding of Unicode character strings that optimizes the encoding of ASCII characters in support of text-based communication. uniform resource identifier (URI) An encoded address that represents any resource, such as an HTML document, image, video clip, or program, on the Web; a URI is an abstract superclass compared with a Uniform resource locator or a Uniform resource name, which are concrete entities. uniform resource locator (URL) A sequence of characters that represent information resources on a computer or in a network such as the Internet. This sequence of characters includes: The abbreviated name of the protocol that is used to access the information resource The information that is used by the protocol to locate the information resource A Web server typically maps the request portion of the URL to a path and file name. Also known as universal resource locator. uniform resource name (URN) A name that uniquely identifies a Web service to a client. URI See uniform resource identifier. URL See uniform resource locator. URN See uniform resource name. user-defined node An extension to the broker that provides a new message flow node in addition to those that are supplied with the product. A user-defined node cannot be developed in WebSphere Event Broker, but can be imported and deployed. User Name Server A component that interfaces with operating system facilities to determine valid users and groups. UTF-8 See Unicode Transformation Format. TOP V view In Eclipse-based user interfaces, a pane that is outside the editor area, which can be used to look at or work with the resources in the workbench. For example, you can view and edit your project files in the Broker Development view (previously called the Resource Navigator view). See also perspective. TOP W WebSphere MQ Enterprise Transport A transport protocol supported by WebSphere Event Broker that enables WebSphere MQ application clients to connect to brokers. WebSphere MQ Everyplace A generally available WebSphere MQ product that provides proven WebSphere MQ reliability and security for mobile and wireless devices. WebSphere MQ Everyplacer applications connect to the broker using WebSphere MQ Mobile Transport. WebSphere MQ Mobile Transport A transport protocol supported by WebSphere Event Broker that enables WebSphere MQ Everyplace application clients to connect to brokers. WebSphere MQ Multicast Transport A transport protocol supported by WebSphere Event Broker that enables dedicated JMS application clients to connect to brokers. This protocol is optimized for high volume, one-to-many publish/subscribe topologies. WebSphere MQ Real-time Transport A transport protocol supported by WebSphere Event Broker that enables dedicated JMS application clients to connect to brokers. WebSphere MQ Telemetry Transport A transport protocol supported by WebSphere Event Broker that enables SCADA devices to connect to brokers. This protocol is a lightweight publish/subscribe protocol that flows over TCP/IP that uses a subset of UTF-8. wild card A character that can be specified in subscriptions to match a range of topics. See also multilevel wild card and single-level wild card. workbench See Message Brokers Toolkit. work_path The location in the local file system in which the component stores internal and working data. For example, the default location on Windows systems is C:\Documents and Settings\All Users\Application Data\IBM\MQSI\. World Wide Web Consortium (W3C) An international industry consortium set up to develop common protocols to promote the evolution and interoperability of the World Wide Web. W3C See World Wide Web Consortium. TOP X XML See Extensible Markup Language. ------- Note: ------- thread: Q: Hi all I'm resending this as I haven't seen it arrive on the list so if you get it twice, please accept my apologies. We're having a problem here connecting an app written for MQ V6.0 on Sun to a V5.3 QMGR running on Z/OS that hopefully someone can give us some advice on. The developers have used "the MQ Java plug-in", by which I assume they mean JMS. The problem is that the command server has to be running as the plug-in apparently uses PCF commands. We're considering implementing a policy in which no app will be allowed to issue PCF commands unless they can give us a very good idea of why. My question is what kind of PCF commands would the Java plug-in be issuing? As they are trying to connect to a remote queue pointing to a Z/OS queue, obviously it would be rejected by the V5.3 QMGR on that side but I can't figure out what PCF command they are even trying to issue or why. When they connect just to a local queue on Sun, whether MQ is on V5.3 or V6.0, the PUT happens successfully. However, when the attempt to connect to a remote queue, once again, on either V.3 or V6.0, they get the following error, assumedly because Z/OS doesn't support PCF commands yet. [lcs-server.log] 2005-10-14 15:37:01,497 INFO [LCS] SocketHandler:No socket listener started. [lcs-server.log] 15:37:03.0098 main.Server(Exception): Object CISACA.MVS.INPUT0 not found on queue manager ZANC000. GODZILLA [trace] BUILD FAILED /main/software/Documentum/aca_interfaces/jlib/apps/lcs/build.xml:42: LCS Startup Failed: Exception occured during s tartup The MQ error we get is: "10/14/05 03:37:03 PM - Process(10684.8) User(mqm) Program(amqrmppa) AMQ9209: Connection to host 'godzilla (10.58.1.40)' closed. EXPLANATION: An error occurred receiving data from 'godzilla (10.58.1.40)' over TCP/IP. The connection to the remote host has unexpectedly terminated. ACTION: Tell the systems administrator." Godzilla is the name of the server both the V6.0 QMGR and the app are running. Also, we don't have the upgrade of Z/OS to V6.0 on the cards until 1Q next year, so it looks like we're going to have to find a workaround until then. A: ------- Note: ------- thread: Q: Hi! I have some interessting errormessage occuring in my application-eventlog. 1.) AMQ9519 'The requested operation failed because the program could not find a definition of channel.' 2.) AMQ9999 'Channel program ended abnormally.' Both entries refert to 'Sys1.Sys2' and occur pairwise every 1 to 5 minutes. The error itself in this case is absolutely correct as Sys1 has been shut down, Channel-definitions were deleted. New channel was created. - So current productive channel is 'Sys3.Sys2'. Everything worked fine without errors. After applying a windows-security update (some time ago, no-one really can remember) the errormessage about old channel 'sys1.sys2' started. System is still working fine - expect from the 'annoying entry' in applicationlog. Has anyone some idea how to get this error stopped? Regards A: What type of channel is Sys1.Sys2? both systems are 'MQ servers' - so Sys3 is sending data to Sys2, Sys2 is processing the data and sends some result-data back to Sys3. If the terminology is correct, i would name it as 'bidirectional'. Sys1 is the predecessor of Sys3. If the terminology is correct, i would name it as 'bidirectional'. The terminology is not correct. On one machine, you are receiving this error. On that machine, there will be a uniquely named MQ object called 'Sys1.Sys2'. That object will be a channel object, and it will have a specific channel type - a sender, a receiver, etc. MQ channels are never bi-directional. They are always uni-directional. Bi-directional communication is accomplished with two sets of uni-directional channels (each of which has a channel object on each side - so *four* channel objects). OK. I'm sitting at 'QM.Sys2'. Sys3.Sys2 - Receiver Sys2.Sys3 - Server So if I understand correctly, somehow the 'old Sys1-MQserver' tries to send something to this 'Sys2-MQserver' old settings, and this machine fails, as the according settings are deleted? go into runmqsc on both QM.Sys2 and QM.Sys3 and enter: Code: display channel('Sys1.Sys2') and tell us what you see.... and you're sure 'QM.Sys1' qmgr has been deleted? System2 is telling me: Code: display channel ('Sys1.Sys2') 3: display channel ('Sys1.Sys2') AMQ8147: WebSphere MA object Sys1.Sys2 not found. I look for someone with access to System3... did you also delete the xmitq or qremote to sys2, it should'nt really matter but just in case. what i am guessing is probably chad is enabled for your queue manager, which i think auto defines channels,try disabling that and see if the error goes off. you can see that in the Q.M properties what i am guessing is probably chad is enabled for your queue manager, which i think auto defines channels, try disabling that and see if the error goes off. you can see that in the Q.M properties except simply setting "chad(disabled)" doesn't make any autodefined channels go away..... OK, problem solved: The channel was still active on remote site (at least it tried to be). Thanks for the idea. :) ------- Note: ------- IC31952: THE RECOREY OF THE CHANNEL FAILED DUE TO AMQ9999. A fix is available MQSeries for HP NonStop Kernel, V5.1 - Fix Pack 03 (CSD03) APAR status Closed as program error. Error description When this customer performed takeover the queue server process to backup process from primary process during sending the message to remote queue, the recovery of the channel failed due to AMQ9999 although takeover of the process was completed. So that, sending of the message was also terminated. This problem occurred about 4 times per 5 operations. Moreover,though trying to stop/start the channel after the above problem, ever could not recover the channel due to AMQ9999 too. Local fix Problem summary primary process failed (cpu failure or TACL stop) and the backup process took over. The most serious error was that messages could no longer be dequeued as noted with a FFST with component qslReadQRec. Problem conclusion of the Compaq NSK Open TMF features in the backup process. This allows the reporting of TM/MP transaction completion status to the backup process. Prior to this implementation the backup process had to check the status of every TM/MP transaction that was stored in its internal list. However there was still a window of transactions that where started but the outcome was unknown. A routine was added to check for persistent messages there physical presenseon disk. If found approriate action was taken to adjust the Qserver. In the case of a non-persistent message we don't know if it was commited or aborted and there is no physical disk record to check, NPM are memory based within the QServer, so we leave as is. Other problems with checkpointing were addressed that caused errors. The major one being the opener context was not using the correct process. Others include the sync of the new backup process was not storing reply data, get checkpointing had some windows, improve reliability od SET_SIGNAL get, order of checkpoint for no syncpoint operations Many other changes to handle failed TM/MP transactions and MQI operations for large messages using multiple IPCs where implemented. Reason codes turned to applications were corrected. No syncpoint failure due to local TM/MP transaction abort will return UOW_CANCELED. Syncpoint failure due to global transaction abort BACKED_OUT is returned. Temporary fix Comments APAR information APAR number IC31952 Reported component name MQSERIES COMPAQ Reported component ID 5724A3900 Reported release 510 Status CLOSED PER PE NoPE HIPER NoHIPER Special Attention NoSpecatt Submitted date 2001-10-19 Closed date 2002-06-21 Last modified date 2002-06-21 APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros MQQSSVR MQSRLLIB Publications Referenced Fix information Fixed component name MQSERIES COMPAQ Fixed component ID 5724A3900 ------- Note: ------- Fix list for WebSphere MQ Version 6.0 Product readme Abstract WebSpherer MQ provides periodic fixes for release 6.0. The following is a complete listing of available and scheduled fixes for Version 6.0 with the most recent fix at the top, for WebSphere MQ 6.0 on iSeriesr, UNIXr and Windowsr. Content Back to all versions -------------------------------------------------------------------------------- Fix Pack 6.0.2.6 (V6.0.2.6) Fix Pack 6.0.2.5 (V6.0.2.5) Fix Pack 6.0.2.4 (V6.0.2.4) Fix Pack 6.0.2.3 (V6.0.2.3) Fix Pack 6.0.2.2 (V6.0.2.2) Fix Pack 6.0.2.1 (V6.0.2.1) Refresh Pack (V6.0.2.0) Fix Pack 6.0.1.1 (V6.0.1.1) Refresh Pack 6.0.1.0 (V6.0.1.0) Recent and planned Fix Pack content summary Glossary of Terms -------------------------------------------------------------------------------- Note: To download WebSphere MQ Fix and Refresh Packs follow this link. http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037 Fix Pack 6.0.2.6 (V6.0.2.6) Fix release date: 1Q 2009 Last modified: 01 October 2008 Status: Scheduled Fix Pack (V6.0.2.5) iSeries Fix release date: 30 October 2008 Last modified: 30 October 2008 Status: Available Windows and UNIX fix release date: 06 October 2008 Last modified: 01 October 2008 Status: Available Download information APAR Description IC54772 Mqjms publish subscribe applications MQ channel and tcpip resources are not freed under some circumstances IC54941 Usage of ccdt to connect to queue managers from .NET interface IC55048 Application using SOAP transport for WMQ fail to connect to target services in client binding mode IC55141 Mqconnx does not check mqcno and mqcd versions and lengths under com+ IC55154 Correction in WMQ system admin guide for availability of runmqtmc command on Windows and UNIX clients. IC55175 Domain nested groups documentation is ambiguous and misleading. IC55218 Customer unable to start a channel. error message AMQ9587 found in log. may also get FDC with probe AD004001 on QM termination. IC55259 MQJAVA: Java native memory leak when using MQINQ or MQSET in a bindings mode application with Java J9VM5.x IC55390 Sequence number on queue stats msg is always 1 IC55482 WMQ explorer does not end the svrconn channel instance if browsing a remote queue fails. IC55548 Wmqjms: JMS applications unexpectedly disconnected from message broker IC55611 Hang in com+ client applications when connection to queue manager has been lost or the queue manager is restarted IC56006 Wmqjava: incorrect put time and date is displayed when looking at messages on a queue IC56009 Comphdr and compmsg channel attributes can't have spaces around their values when being accessed by runmqsc IC56068 WebSphere MQ queue statistics data field browsefailcount is incorrectly incremented IC56133 Mqrc_api_exit_not_found reason code not found when compiling WebSphere MQ V6 Java applications IC56151 Error code 2354 missing in return code translation table in ActiveX code. IC56170 Implement setclonesupport in resource adapter IC56264 A sta .NET application (eg. vb.net) suffers memory leaks due to a hung finalizer thread. IC56279 Explorer writes incorrect put/get authority to setmqaut dump IC56327 A WebSphere MQ .NET application fails to get or put a message to a z/OS queue manager IC56352 Mqrc_uow_enlistment_error (2354) when using extended transactional client IC56408 AMQ9245 message generated without authority event message being put onto the system.admin.qmgr.event queue IC56432 Misleading statements in WMQ V6 info-center regarding support formessage grouping & segmentation when using pub/sub IC56461 When using xms.net to connect to an LDAP server, connection factory lookups reports that 'tcm' has already been added IC56649 Installing the MQ client causes the javawebstart registration information to be overridden. IC56662 Hang in AMQZMUC0 process following the 'disk not ready' error IC56709 Maximum logfilepages displayed in WebSphere MQ explorer GUI is 16384 instead of the V6 maximum of 65535 IC56754 WebSphere MQ API exerciser doubles the number of bytes when using MQPut in DBCS locales IC56858 Mqexception message method is missing from the .NET libraries INV6+ IC57918 Delay in delivering large messages to message-driven beans when using WebSphere MQ with WebSphere application server IC57931 WebSphere MQ version 6 SOAP ivt fails when using Java 5 IZ05857 WebSphere MQ responds with incorrect XA error code in a global XA transaction. IZ13144 Cluster workload is affected due to change in netprty behaviour IZ13921 GSK7CAPICMD crash when incorrect command syntax is used IZ14005 Probe XC130003 FDC (sigsegv) in runmqlsr process with function rppconnectpool on the mqm stack. IZ15456 Very slow initial access to deep queues holding large numbers of grouped messages. IZ15677 Jms: application thread hangs when exception thrown by mqthread. IZ16357 Conversion table 819 to 284 missing for WebSphere MQ installation on AIX IZ16620 Conversion table entries for ccsid 284 missing for WebSphere MQ installation on AIX IZ16645 Probe RM554010 rrce_file_corrupt. client program mqconn fails, reason code 2058. clntconn defns missing from runmqsc output. IZ17062 Jvm userid is not passed while creating an xaconnection if no userid is specified by the JMS application IZ17156 Strmqm incorrectly displays error code during failure IZ17158 Setting errorlogsize does not take effect for queue managers whose name contain a "." and/or "/" IZ17303 Cluster channel ping fails with segmentation violation and core dump IZ17313 System.cluster.repository.queue damaged, strmqm failed with an exception in AMQZXMA0 from rfxqueryclqmgr. IZ17341 WMQ may start a user-defined service with all signals blocked, so a stop service that sends e.g. sigterm would be ineffective IZ18103 Problem during the truncation of a "ghost" queue file which is marked for reuse. IZ18142 Endmqm can take many minutes to end the queue manager if there are active svrconn channels IZ18716 Errors may not be propagated from early stanzas during processing of qm.ini and mqs.ini files. IZ18954 Delay in sending messages when pipelining is used with SSL IZ19009 Arce_object_damaged and probe ID AQ143011 after migrating from MQ 5.3 to MQ 6 IZ19168 Probe RM400001 FFST using pipelined channels at 6.0.2.3 IZ19249 WMQ quick beginnings guides should be updated to clarify queue manager shutdown by root user when applying maintenance IZ19340 Mqjms: deadlock condition may occur when an application thread attempts to close session used by asynchronous messageconsumer. IZ19555 Probes XY179010 and XY180010 from AMQZMGR0. IZ20546 High cpu usage in the amqrrmfa process on an hourly basis for several minutes. applications unable to issue MQ API calls. IZ20672 WMQ trace generates incorrect thread ID when pipelining is used with SSL IZ20758 XC034002 AMQZLAA0 unexpected response to a pthread_cond_timedwait() request causes waiter chain corruption IZ20974 Broken symbolic link can cause MQ queue manager data loss IZ21318 WebSphere MQ failure to reserve log space in a queue manager restart scenario. IZ21552 SSL ping channel fails on hp Itanium IZ21977 MQRC_OBJECT_CHANGED(2041), AMQ9511 SYSTEM.CLUSTER.TRANSMIT.QUEUE,AMQ9448, repository manager ends IZ22019 Data conversion performance problems after multiple unsupported or invalid conversions have been requested IZ22198 AMQ4048 error when browsing messages using the MQ explorer. an FDC with an access violation is also produced. IZ22272 AMQ9526 and 'scratchpad in use' errors are seen when two identically named qmgrs are connecting to same receiving QM IZ22725 Incorrect statement in manual: queue manager configuration maxchannels attribute IZ22727 Correct reason code when cluster alias sub is not acknowledged IZ23058 Workload balancing does not round robin the messages as expected in a clustered environment. IZ23230 Mqjava: unable to use WebSphere MQ Java client to connect to a tpf queue manager with gmo matching options. IZ23438 Cluster cache look ups are taking too long causing clustered object resolution errors. IZ23756 Function abstime does not always send a value less than 1000000000 as an argument to cond_timedwait(). IZ23780 Channel status stopped not migrated to V6 IZ23789 Queue manager terminated abruptly and an FDC with probe ID AT004007 is generated. IZ23839 Address alignment exception with the log formatter when formatting an MQGet log record IZ23943 Hang in duow (pipelined) channel process following forced termination of a channel xppthreadmutex IZ24069 PCF mqcmd_inquire_auth_recs response messages all have msgseqnumber 1 in the mqcfh IZ24178 Fdc's produced by synchronous signal handler incomplete on hp/ipf (hp itanium) IZ24186 Cluster workload exit sample amqswlm does not load in MQ6.0. IZ24193 WebSphere MQ does not generate AIX trace on AIX V6. IZ24362 Core dump and truncated FDC in WebSphere MQ whilst writing an FDC during the very early stages of a process startup. IZ24944 Wmqjms: JMS pub/sub cleanup thread (pub/sub) fails to utilize the username/password specified by the application. IZ25171 During channel termination, an FDC with probe ID RM409000 followed by many with probe ID RM409001 is produced. IZ25614 WebSphere MQ channels terminate with AMQ9604 and AMQ9208 and get FDCs with XC130003 and RM031101 IZ25622 Error 2185 putting group msgs to cluster queue with persistence as queue definition IZ28942 Incorrect warnings during install of 6.0.2.4 mqm-javasdk and mqm-keyman on HP-UX IZ31327 Defects fixed in WebSphere MQ fix pack 6.0.2.5 on AIX V6.0 SE28827 MQM400 SDR(1256) to RCVR(420) fails to start with AMQ9520 SE28896 MQM400 testfix for APAR SE28113 on refreshpack 6.0.2.1 SE29574 MQM400 testfix for APAR SE28838 on WMQ6.0.2.1 SE30937 MQM400 mdv V6.0.2.2 (mqrc) testfix for IZ08829 SE31046 MQM400 mdv V6.0.2.2 (mqcs) testfix for IZ07206 SE31087 MQM400 mdv V6.0.2.2 (mqqm) testfix for IC53974 SE31088 MQM400 mdv V6.0.2.2 (mqrc) testfix for SE30754 SE31252 MQM400 mdv V6.0.2.2 (mqjb) testfix for SE28838 SE31779 MQM400 validateauth=no does not maintain error log permissions SE31994 MQM400 mqoa crtmqmprc/chgmqmprc fails to save values with * SE32112 Osp-perfm MQM400-DELAY when using SSL with MQ V6 SE32282 MQM400 cannot successfully remove a queue manager from a clusterwith the spdmqmclqm followed by chgmqmchl .. chltype(*clusrcvr) SE32853 MQM400 it is not possible to create teraspace enabled c++ program so we see CPD5CCF similar to SA96347 SE33397 MQM400 *public authority change for content in directory /qibm/proddata/mqm/inq in WMQV6 from WMQV5.3 SE33722 MQM400-INCORROUT MQ 6.0.2.3 may fail to start AMQ7432 SE34580 MQM400 56-BIT export cipherspecs do not work in WMQ 6.0 and I5/OS SE34587 MQM400 strmqm fails with probe AL008000 on OS400 with OS version V6R1M0 SE34588 MQM400 dspmqmsts and AMQ7460, AMQ7462 in the queue manager error log shows as ******** on V6R1M0 OS Fix Pack (V6.0.2.4) iSeries fix release date: 26 June 2008 Last modified: 26 June 2008 Status: Available iSeries download information Windows and UNIX fix release date: 30 May 2008 Last modified: 30 May 2008 Status: Available UNIX and Windows download information APAR Description IC53540 Queue manager fails to start up and FDC with probe ID XY338011 is generated after amqzmgr.exe is terminated. IC53578 WMQ explorer displays invalid date/time for a message having blank putdate or puttime IC53819 "mq java/jms application gives a peer name mismatch error when the exit-list length is greater than 8" IC53960 Channel shortretry count will not fall after moving into retry state even though many attempts were made to restart IC54088 Automatic startup settings for command server are lost when migrating from MQ V5.3 to MQ V6 in an MSCS configuration IC54095 FDC with probe ID XC368002 and error 'winnt error 5 from duplicatehandle' is generated when a queue manager is ended. IC54182 Access denied error on an openprocess call during an mqconn by a customer application. IC54292 WebSphere MQ queue manager in MSCS cluster ends unexpectedly IC54346 Closing a jca session does not close its producers and consumers IC54459 Channel stays in binding state for a long time when it contains an invalid conname value IC54584 PCF message write method does not set MQMD fields to default values for PCF messages IC54585 Jca: wmq.jmsra.ivt.ear contains an invalid value in wmq.jmsra.ivt.ear file ejb-jar.xml IC54608 Channel statistics messages have queue manager name padded with zeros instead of blanks IC54678 Display conn command in runmqsc failing to find any matches whenfiltering by conname IC54711 PCF escape command with dis lsstatus for a listener of 48 chars returns additional chars in listener name error message IC54888 Queue manager restart fails with HL080077 following outage when system has been under severe resource constraints IC56162 "dspmqras.exe folder" file is incorrect. should be dspmqras.exe IZ04683 JMS client connections not closed in asynchronous mode when queue is manager stopped. IZ05023 FDC with probe ID XC348015 from xlsrecoverthread on hpux IZ05045 FDC generated with probeid ZC004063 when using single threaded agent IZ06097 Mqconnx fails with reason code 2409 when version 1 mqsco is usedwith WMQ 6 IZ06131 Setmqaut fails when authority records are not yet created or are missing IZ06425 The WebSphere MQ signal handler is exiting when a sigsegv occurs, preventing a WMQ application from producing a core file. IZ07198 Queue manager unresponsive, with a probe XY441020 FDC from function xstaddconnectedthreads. IZ07206 An application connect during queue manager startup may cause startup failure with likely FDCs ZF095010 and RM185002 IZ07297 Improved error handling during refresh cluster command when clusnl() attribute points to a namelist that doesn't exist. IZ07778 The runmqsc changes to amqclchl.tab may not be inserted in the correct ascii-order. also, amqclchl.tab will never shrink. IZ07803 Following the installation of 6.0.2.2 the customer may experience java.lang.classnotfoundexception problems IZ07905 Delays in getting messages when using the WebSphere MQ JMS client in bindings mode. IZ08014 Illegalstateexception calling createconsumer IZ08018 Strmqm fails for single threaded MQ queue manager on Linux IZ08180 Qmgr not reporting the appropriate warning if amqrsyna.dat file is corrupted. IZ08596 XC034002 in xcswaiteventsem shortly after zlaperformhealthcheck returns xecp_e_invalid_pid. IZ08748 Deleting queues while PCF inquirequeuenames command is executing, causes an FDC with probe PC024010 IZ08754 Failing publish not retried correctly, stream repeatedly restarts without republishing. IZ08783 Probe AD028004 FDC from adiopenfile (RC=24 from open) in AMQZXMA0, when migrating to V6. this is a file descriptor leak. IZ08829 Pcf: mqcmd_inquire_channel_names fails if more than 628 channels. can cause probe XC006001 FDC or hang command server. IZ09144 WMQ 6.0.2.2 FFST RM056000 from riitriggermessage with error rrcw_already_started IZ09338 In the case of queue manager recycled infrequently, the number of accumulated channel stats records becomes very large. IZ09419 Improve AMQ9565 error message IZ09519 Improving queue manager's robustness when application is using non-unique groupid/msgseqnumber/offset/report-type combinations IZ09591 Endmqlsr fails with 'no WebSphere MQ listeners for queue manager' if listener launched using runmqlsr IZ09658 AMQZMGR0 does not clean up shared memory in a timely fashion when it is the last process to reference that memory IZ10060 Inconsistent treatment of cluster qmgr alias 2087 mqrc_unknown_remote_q_mgr IZ10757 Amqrrmfa terminates with error rrci_clus_no_clusrcvr_defined IZ10800 Rare command server sigsegv in function pcmbuildmsgparms when executing PCF command mqcmd_inquire_q_status. IZ10832 Jca: a nosuchmethod exception is thrown when using WebSphere jca with sun application ee IZ10869 Occasional deadlock when issuing stop conn runmqsc command (or PCF equivalent). IZ11153 WebSphere V6 may not always consider the mqmaxerrorlogsize environment variable when writing error log messages IZ11458 Dis qs uncom is not a boolean value IZ11718 Sigsegv on Linux inquire listener status IZ12149 Cleanup code mistakes socket files as directories and does not delete them appropriately. IZ12159 Receiver channel might not decompress message when message is sent in multiple segments IZ12208 MQOpen fails with 2042, if the MQ application had previously failed with unexpected error, holding the object handle open. IZ12274 Unable to determine the exit status of internal processes started as queue manager services. IZ12283 Command server returning 2017 ( mqrc_handle_not_available ) IZ12497 Probe KN272002 FDC reported from function kqiputaccountingqueue when a connection has a large number of open objects IZ12536 Incorrect output can be given by PCF mqcmd_inquire_auth_recs command. bad output can also be given by dmpmqaut and amqoamd. IZ12700 Very large FDC produced including an extremely large dump area entitled "active shared memory heap". IZ12739 Readme for WebSphere MQ maintenance did not clearly state product version and migration information IZ12795 Inquirechannel PCF command with channeltype parameter does not return complete channel details, only the channel description. IZ12796 Jms: a non thread safe JDK class is declared as a static IZ12827 FDC written by WebSphere MQ explorer if mqs.ini file has stanzasthat refer to unavailable locations in filesystem. IZ13135 The JMS message.setjmsreplyto() method does not work correctly when using WebSphere MQ resource adapter (ra). IZ13247 Imqqueuemanager::connect() fails when mqcsp authentication is used even when IY92447 is applied. IZ13512 WebSphere MQ loops when queue manager ini file is corrupted IZ14279 Queue manager time calculations must use thread-safe system calls IZ14399 Queue managers rejoining clusters with IY99051 have incorrect sequence numbers, changes may not be published in the clusters IZ14732 WebSphere MQ slow performance on HP-UX 11.31 IZ14812 Sigsegv in xcsreleasemutexsem called from rrxreporterror when using mq_channel_suppress_msgs. IZ14977 Missing cluster information when namelists are used to add and remove queue managers from multiple clusters at once. IZ15279 Jmsreplyto field in the MQRFH2 header does not specify replytoqmgr name unless it has been manually set IZ18598 Client mqconn can cause program to end if already connected or in a variety of error conditions IZ23320 Defects fixed in WebSphere MQ Fix Pack 6.0.2.4 SE29894 MQM400-RC545284153-MSGAMQ5011 WMQ V6 strmqm fails to start SE30113 MQM400 - WMQ listener jobs started before queue manager start are not terminated when queue manager is quiesced SE30379 MQM400 inconsistencies noticed for the sslpeer attribute of chgmqmchl SE30398 MQM400 unable to use clrmqmq command without *altusr authority SE30649 OSP-MSGAMQ9507 MQM400-AMQ9507 for *sdr channel after V6 SE30754 MQM400- MSGMCH3402 amqrrmfa abend during queue manager startup SE30965 MQM400 WMQ channel problems with hrtbtint > 999999 SE31023 MQM400 - V6 installation grants ownership of objects to SE31209 MQM400-INCORROUT wrkmqmq - filtering the type of queue - F11 SE31214 MQM400 ile RPG copy book contains duplicate entries SE31933 MQM400 runmqchl joblog do not contain any useful error message. SE31958 MQM400 dspmqmlsr output(*print) does not output spoolfile Fix Pack6.0.2.3 (V6.0.2.3) iSeries fix release date: 11 March 2008 Last modified: 11 March 2008 Status: Available iSeries download information Windows and UNIX fix release date: 1 February 2008 Last modified: 31 January 2008 Status: Available UNIX and Windows download information APAR Description IC52223 Access violation FDC XC130031 in the amqfcxba process. IC52320 FDC with probe XY470022 is incorrectly cut if connectnamedpipe returns zero and the getlasterror returns error_pipe_connected. IC52378 MSCS times out in lookalive checks leading to failover of cluster resources through mqmterminate. IC52523 Resolve channel action(commit) fails to resolve a manually defined clussdr channel. IC52603 Amqrmppa thread calls mqback instead of xa_rollback in an XA environment IC52619 Executing stop connection leads to an access violation in the execution controller and the queue manager crashes. IC52632 Inquire queue status PCF command incomplete response IC52674 Error AMQ7017 occurs when trying to start a queue manager and anfdc is generated with probe ID ZX000001 IC52684 Channel compression from z/OS to Windows results in message data with 4 extra bytes IC52709 Qmgr is reporting the following probes: HL008001 hlgsetlogrestartlsn and AL020000 almsetoldesttranlsn IC52770 New schemes defined in WebSphere MQ explorer are lost when the WebSphere MQ explorer restarts. IC52821 Client side exits cannot be loaded through MQExplorer using a CCDT IC52823 "the handle is invalid" error appears in the file specified as stderr in WebSphere MQ custom service definitions. IC52862 WebSphere MQ explorer fails to import scheme settings that have been previously exported. IC52873 Automatic refresh of the queue manager cannot be disabled in explorer. IC52954 SSL channels defined with sslpeername do not start after migration from MQV5.3 IC52989 Clussdr channel can be deleted even though channel is in-doubt IC53034 Japanese characters are corrupted in fix pack 6.0.2.1 installation dialogs IC53065 WebSphere MQ queue manager fails with probe XC037003 when started IC53107 Migration failure if incorrect backup folder is selected during fix pack installation. IC53158 Gskit fails to open key database correctly when invoked from explorer using a non administrative user ID. IC53189 The accumulated authority records displayed in WebSphere MQ explorer through find authority sub-menu are incorrect IC53192 Mqwin-wmq services performance counter fails to restore with AMQH0001.H not found IC53204 WebSphere MQ V6: repeated queue damaged instances IC53255 MQ SSL migration from V5.3 to V6 results in 'chain incomplete' during 'check WMQ store cert wizard' IC53266 Listener process does not end on queue manager termination despite using a listener object configured with control(qmgr) IC53286 Unable to compute putdate and puttime when any one of the fields is set to blank IC53291 Runmqdnm process fails with mqrc_options_error when monitoring a queue on tpf IC53318 Queue manager fails to start on MSCS with FDC MC033007 IC53368 WMQ explorer fails to display queue manager objects during it's startup due to the error in creating the navigator view IC53379 Memory access violation errors seen in mqconn IC53384 Channel status data displayed incorrectly in WMQ explorer IC53403 Performance slow on mqput/mqgets and AMQZLAA0 cpu usage is high when running 100'S of application threads/processes. IC53429 Amqsmon shows 0 in putbytes field despite having put messages with MQPUT1 call IC53457 Changes to preofflinecommand and postonlinecommand parameters for an MSCS resource result in 'the data is invalid' IC53508 Environment variable name containing special symbol is not added through service.env file IC53514 XA client hangs while connecting to the queue manager IC53533 MQ explorer fails to browse the queues of a queue manager which is connected through SSL client channel definition table IC53545 The recommended method for removing oam entries IC53651 Handle leak when exclude or suppress messages is set IC53676 Error messages AMQ7315 or AMQ7316 are logged when any accountingor statistics message is put to the accounting/statistics queue. IC53716 Amqoamd command displays inconsistent results for '+none' authority. IC53764 Nullpointerexception error received when tracing level set to 5 and messageid is null IC53782 Amqrrmfa terminates when the queue manager object configuration contains an invalid value IC53817 Setmqprd silently fails to convert a trial version of MQ into a production version. IC53842 Queue manager terminates unexpectedly with FDC AD031001 and error_invalid_user_buffer from adiwritefile. IC53936 FDC with probe ID RM400001 and error code rrce_bad_parameter generated upon termination of a client channel. IC53962 Application successfully opens cluster queue object on remote queue manager despite specifying an invalid user ID as altusr IC53967 Poor performance with large messages on Windows clients using non-blocking tcp model IC53974 MQSeries service fails to start with error 1053. strmqm hangs. FDC with probe ID ZX005025 generated. IC54121 Cluster channel in retrying state would not start after command: stop channel() mode(quiesce) status(inactive) IC54142 Thread handle leak from MQ com+ (mts) layer IY92377 Destseqfactor incremented for clusrcvr on remote queue manager causes unexpected results in workload balancing IY93129 MQ is not honoring the value specified for errorlogsize in the qm.ini file. IY95538 2080 is issued when MCA agent is trying to get messages from system.cluster.transmit.queue. no messages are written to the log. IY96630 A deleted damaged object prevents advancement of WMQ logs. it further causes dltmqm to loop consuming log space. IY96836 Environment variable for changing the order during a 2 phase commit IY96879 Messages can arrive in incorrect order via cluster channel IY97159 Repository manager process tries to access the cache while restoring the cache, resulting in a hang. IY97173 Amqiclen failure when there is a non-mq file in qmgrs directory IY97428 SSL peer name in client channel table can fail to be matched correctly against SSL peer name in server-side certificate. IY97558 Agent process does not return from a MQGet call for a period of time significantly larger than the time-out specified IY97580 FFST probe XC130003 in ccxsend on server side of SSL channel IY97736 Channel fails to start with error AMQ9519 (rrce_channel_not_found) IY98258 Not setting user name in MQEnvironment gives 2035 error for WMQ v6 IY98550 Customer user exit gives security exception when Java2 security is enabled IY98585 Lower case userid being passed to z/OS v1.6 with Websphere MQ 6 IY98620 Queue manager hang during define object when an API exit is installed. IY98777 WebSphere MQ hangs after rc=stop from a call to xlllistenselectacceptandclose IY98973 Memory deallocation failure due to thread mismatch when pipelining is used IY99050 Rcdmqimg fails with AMQ7084 for a queue containing segmented messages IY99051 Queue manager unable to re-establish cluster membership IY99057 MQ error handling in XA protocol violations where xa_end() called for transaction not associated with current thread IY99181 Amqrfdm at WMQ 6.0 does not work when using isolated bindings IY99200 If the execution controller fails to create a new agent process, it will sigsegv (from WMQ 5.3 CSD13 or 6.0.1.1). IY99415 Extra validation for data received from tcp/ip to handle case where tsh header overwritten during transit IY99425 32-BIT applications reserving large amount of heap memory and/or shared memory segments fail to connect to WMQ V6.X qmgr IY99591 Highly intermittent probe XC271004 FDC, reported from very short-running processes such as dspmq. IY99598 An extremely intermittent probe ZI032002 FDC from function ziistophealththread is reported. IY99683 Corrupted message header in dead letter messages produced by JMS Client IY99847 WMQ error log file rollover is incorrect for some non-mqm applications on UNIX IY99912 MQ adds too many log extents to the log file header at MQ shutdown resulting in subsequent qmgr restart failure. IZ00315 Mqmessage class in .NET API does not allow the offset and originallength fields to be set. IZ00349 Locking problem where we try to write an accounting record whilst already holding a lock on a non-queue object. IZ00380 Correct parsing of MQ exception handler override commands. IZ00609 XC034071 in xcswaiteventsem with error code einval (22) IZ00896 WebSphere MQ messages occasionally delivered out of sequence under stress on MQ V6 IZ00993 SYSTEM.BROKER.IQ.1.4 been referred to as a stream queue by a user application. IZ01058 XC130004 sigsegv when restoring cluster objects during queue manager start up IZ01151 Probe XC015010 raised by checkpoint task during endmqm processing IZ01402 Broker fails to start or publish or subscribe. IZ01512 A failure to start a timer thread when waiting for a critical mutex causes queue manager failure. IZ01580 A timing window results in two threads using the same semaphore to suspend/resume leading to hangs and unpredictable results. IZ01599 Sigsegv in kqiwakeupwaiter when waiter state reset during stop channel command IZ01794 WebSphere MQ queue manager fails to start when transaction's first lsn is not in active log after disk space issue. IZ01835 WebSphere MQ performance is poor when querying xqmsgsa at a time when system.cluster.transmit.queue is deep. IZ02442 Child broker fails to restart after breaking parent relationship IZ02497 Receive() with unified factories fails to find messages IZ02512 Migration to WMQ 6.0 may corrupt clustering information IZ02573 WMQ 6.0.2.1 and 6.0.2.2 Solaris install sets erroneous 777 file permissions in /var/sadm/pkg IZ02777 Queue manager fails to start. FDC with probe AT013011 IZ02915 XC130004 FFST in apiunlockexclusive, when attempting to record a media image of a damaged queue. IZ03090 Dis qs does not show userid after appltype(system) IZ03209 When message is gotten by application with RC=2079, lgettime/lgetdate fields do not get updated. IZ03678 Mqcmit for a long running transaction generating an mqrc_unexpected_error return code. IZ04163 WMQ channel connection fails with AMQ9213 error 22 over IPV6 IZ04394 Queue file corrupted crossing 4MB boundary and no space avail. IZ04523 Amqiclen does not clear trace control shared memory IZ04767 Tcf_last with no tcf_first should be detected by WebSphere MQ IZ04821 Crtmqm fails on WMQ 6.0.2.2 when mqsprefix is set or if mqs.ini defaultprefix is set to a location other than /var/mqm IZ04971 Missing attributes in the queue manager log stanza causes queue manager restart to fail. IZ05005 AT004018 possible when simultaneous activity from separate threads attempt to complete an XA transaction concurrently IZ05013 Using data compression on a channel, channel ends with FDC with probe ID CO052100 generated on receiving side qmgr IZ05057 Qdphiev event messages sent to system.admin.perfm.event queue incorrectly IZ05176 Websphere MQ resource adapter IVT ear file not shipped on UNIX IZ05307 Dspmqtrn formats XA xids incorrectly IZ05527 When browsing a queue with mqgmo_browse_next the first message ever put to the queue can be skipped. IZ05653 AMQZMUR0 fails with XC006001 and xecs_i_private_memory_error IZ05792 MQRC_NO_CONTEXT_AVAILABLE returned from attempted MQPUT to dead letter queue after queue backout threshold reached IZ05950 Generating non-unique groupid's when using message segmentation,can cause a queue manager to crash. IZ06614 No authority event generated after mqrc_not_authorized returned to mqconn, despite enabling authority events. IZ06672 WMQ queue manager error log locking can be briefly compromised, but with typically no impact. IZ07210 Abstract 2035 if client user name > 12 chars and valid mcauser IZ07794 Defbind not honoured when alias queue resolves to a cluster queue IZ09339 Averagequeuetime (mqiamo_avg_q_time) displays negative values IZ09383 Occasional fdc's with probe KN072085 when applications specify mqgmo_msg_under_cursor with mqgmo_wait. IZ10294 Incorrect authorization check when putting directly to an MQ transmit queue. IZ13990 Defects fixed in WebSphere MQ fix pack 6.0.2.3 IZ14160 Defects fixed in WebSphere MQ fix pack 6.0.2.3 SE28711 MQM400 - MSGMCH3601 when attempting to display message AMQ6106 for xcsdisplaymessage SE28838 MQM400-THREADS-UNPRED MULTITHREADED JAVA APPLICATIONINTERMITTENT FAILURE SE28867 MQM400 wrkmqm option 22 receives msg CPF3C53. SE28943 MQM400: improve diagnostics when strmqm hangs with X'00000D49' SE28955 MQM400 queue becomes damaged at least 2 to 3 times a week. SE29272 MQM400 AMQ6903 received on install of fp 6.0.2.1 SE29323 MQM400 chgmqmprc or crtmqmprc fails to record values of usrdata starting with asterisk ( * ) SE29410 MQM400 strmqm fails with AMQ7432 arce_log_recd_not_found SE29414 MQM400 - P0000* and/or S0000* files in qmqm library not removed when queue manager quiesced SE29524 MQM400 amqcrsta job does not run under user-defined subsystem SE29638 MQM400 - command server for clustered queue manager failing with MCH0601 on starting up MQ explorer SE29710 MQM400: rcdmqmimg does not log messages AMQ7460 and AMQ7462 in the queue manager message queue (qmqmmsg) SE29770 MQM400 : queue manager migration failed with MCH0601 and channels are missing. SE29795 MQM400 mdv V6.0.2.2 testfix for IY99050 and SE28955 SE29796 MQM400 mdv V6.0.2.2 testfix for IY99050 and SE28955 SE29844 MQM400 lodptf of fixpack 6.0.2.2 fails with AMQ6903 SE30262 MQM400-QUEUE manager with pending transaction fails to start SE32195 MQM400 MCAUSER *PUBLIC NOT RECOGNIZED IN CRTMQMCHL or CHGMQMCHL - FOLLOW ON FROM THE APAR SE27576 Fix Pack 6.0.2.2 (V6.0.2.2) iSeries fix release date: 14 September 2007 Last modified: 14 September 2007 Status: Available iSeries download information Windows and UNIX fix release date: 24 August 2007 Last modified: 22 August 2007 Status: Available Windows and UNIX download information APAR Description IC50588 FDC AQ109001 from aqhlogicalmsglock during browse,lock of a segmented message. IC51002 WebSphere MQ explorer tests plug-in displays incorrect attribute and refers to a non-existent channel object. IC51005 Mqrc_security_error returned on a PCF inquire authority records command submitted with invalid parameters. IC51054 "mqrc_storage_not_available error due to the invalid data length returned from the MQGet of the message. IC51126 MQ explorer does not accept symbols @,#,$ when trying to connect queue-sharing group. IC51315 WebSphere MQ rolls back prepared transactions if msdtc goes down. IC51322 Code changes for optimization of default conversion. IC51324 WMQ invokes enlistwithdtc to enlist with the transaction leading to a number of calls in msdtcprx.dll causing a deadlock. IC51350 Warning AMQ8075 logged when a user with an ID of more than 12 characters issues the change channel command. IC51397 Server file transfer application does not display remote queues of the queue manager. IC51404 Windows MQ fails to shutdown if shared memory server dies. IC51408 FDC with probe ID JP707000 generated when running test plug-in of V6 MQ explorer. IC51434 WMQ V6 explorer fails to refresh after queue manager is stopped and restarted from command line. IC51439 Log write operations do not retry when an error_lock_violation return code is returned on Windows. IC51451 Access violation occurs when printing out the object descriptor and associated object records in trace of MQOpen IC51472 XC090001 and xecf_e_invalid_parameter IC51497 Get complete msg fails with mqrc_match_options_error. IC51589 Runmqdlq suffers XC130031 access violation when it encounters a null message on the dead letter queue. IC51598 Damaged object following log errors caused by a sharing violation on the log itself. IC51667 XA_PROTO errors occur when WebSphere MQ is used as a JMS provider with WebSphere application server. IC51721 Unable to rebuild a syncfile using rcrmqobj if using circular logging IC51889 Soap/WMQ client C0000005 access violation. IC51904 An FDC with probeid XC130031 is generated in amqrmppa process. IC51952 Mqrc_truncated_msg_failed error from MQGET call even though enough buffer is supplied. IC52019 Optimize code where MQ reads the sync file to get the saved channel status. IC52177 Channel process reports incomplete error messages if it encounters a TCP error during connect, send and receive. IC52193 AMQ9519 when starting auto-defined clussdr channel. IC52257 Access violation FDC XC130031 in the command server (amqpcsea.exe) IC52322 Queuemanager service does not start a program with extension .cmd or .bat if the stdout parameter is not set. IC52411 6.0.2.1 install fails on 64 bit Windows under terminal services. IC52445 MQ .NET client applications cannot put or get messages greater than 4MB. IC52687 SSL certificate import or migration fails on 6.0.2.1 Windows. IC52757 WMQ V6.0.2.1 client installation fails with error code AMQ4739. IY87626 Resolve channel on an auto cluster sender channel ( in indoubt state ) fails with xecl_e_invalid_param. IY88024 The API exit structure ID is blank and version is 0. IY89755 Very small timing window whereby pipelined channels ("dual unit of work", duow) can fail with probe CO000002 FDCs IY90059 Clwlprty value changes if namelist is changed. IY90521 WMQ listener on hpux stops when an accept call fails with return code 233 enobufs. IY90873 FFST with probeid KN111000 continually generated reports mqrc_stopped_by_cluster_exit IY91269 FFST with probe XC006001 when using channel exits IY91348 Reset non-existent channel in runmqsc results in memory fault and SIGSEGV. IY91385 Man pages for crtmqm don't reflect new V6 values for logfilesizeand number of logfiles. IY91510 MQJMS2002 jmsexception thrown when using multiple consumers with selectors on a transacted session. IY92011 Runmqsc "dis q(*)" doesn't display all queues if one or more of the queues are damaged. IY92016 PCF inquirequeuenames command does not handle damaged objects gracefully. IY92051 Amqoamd command generates an erroneous attribute for setmqaut. IY92141 Load exit fails with error 'cannot open shared object file: no such file or directory'. IY92192 .NET client argumentoutofrangeexception when compression is used. IY92194 Dis chs fails on clusrcvr channels when using conname limiter. IY92196 Xstdisconnectextent causes FFST for applications using fork without exec. IY92390 The malformed or unexpected message handling fails with 2098 error in asynchronous message delivery scenario. IY92441 Bothresh ignored in JMS applications when using alias queues. IY92447 Userid and password not passed across channel. IY92471 Nullpointerexception when using MQ JMS client in mqjms_tp_direct_tcpip mode with SSL IY92929 Logger process amqhasmx (AMQZMUC0 in V6) could eventually run out of file descriptors some time after a disk full condition. IY92963 SIGSEGV in preparedumpareas during crtmqm and resulting core file. IY93155 Channel triggering fails due to object_already_exists error. IY93324 MQJMS2003 gets generated with a nullpointerexception. IY93408 Mqbegin fails with SIGSEGV or SIGBUS when an Oracle session is killed. FDC file contains probe ZM008001 and XC130003 IY93415 MQ explorer could hang when selecting services and the reply queue fill up if multiple messages are returned from AMQZMGR0 IY93506 SIGBUS from dmpmqlog commands. IY93655 Performance problems related to resolving high lock contention. IY93707 Wmq/cics application returns 2035 (mqrc_not_authorized) error from mqconn call in isolated bindings mode. IY93752 Excessive DNS lookups. IY93881 Potential SIGSEGV if AIX is very slow at scheduling. IY94013 Poor performance loading deep queues containing both persistent and non-persistent messages. IY94250 Setting a zero interval via the mq_channel_suppress_interval environment variable causes SIGFPE FDCs in channel processes. IY94267 JVM crash when using MQ JMS XA in bindings mode in was 6.1 IY94451 Queue manager alias definitions with alteration date more than 1 month old not successfully deleted from a cluster. IY94625 Amqfcxba suffering a SIGSEGV in function fkirestoresubscription or in function fkxderegistersubscriber. IY94674 Client applications continuously cycling thread connections may re-read mqs.ini many times. IY94700 Hang in channel processes such as runmqlsr, amqrmppa, runmqchl. IY94811 Nullpointer exception occurs if WebSphere application server trace is disabled. IY94832 Duplicate subscriptions with different subname's cause SIGSEGV in amqfcxba process. IY94876 UNIX file descriptors being left open while generating FDC for asynchronous signals. IY94977 Queue manager fails to start throwing log not available error following an abrupt failure. IY95005 Windows client channel compression settings ignored. IY95078 Long delays in multi-threaded puts in WMQ c++ client. IY95181 JMS null valued causes exception in MQ JMS application. IY95255 Probe: XC130004, SIGSEGV: address not mapped, function: aqhaddmsg. problem writing temporary dynamic queue object. IY95370 Synchronization issue with the jmsconnection hangs shutdown of application server. IY95485 Queue manager is ignoring requests for more than 253 secondary log files on UNIX. IY95508 Channel statistics getting collected at the end of the configured statint after having turned off the statchl attribute. IY95513 Probe XC130004 FDC (SIGBUS or SIGSEGV) in xcsendgrent function. IY95544 SSL enabled channel will not run because MQ code is not able to access the channel status table. IY95555 WebSphere MQ authority event message incorrectly shows mqm as the user ID. IY95566 Runmqsc ctrl/ctrlx auth not honoured for non-mqm users. IY95706 Sigsegv immediately following return from zfudoesobjectexist XC130004 from amqzlaa0, amqrmppa, or amqfcxba. IY96055 Messages due to expire do not expire after a queue manager crash/restart or an HA failover. IY96066 MQ JMS publish/subscribe clean up does not process all applicable messages. IY96150 AMQ9509 and RC=2009 errors during endmqm -i, causing channels to fail abnormally. IY96282 Two threads have been concurrently allocated the same semaphore. IY96442 Message expiry report not resolved to cluster queue. IY96689 FDC's produced by asynchronous signal handler incomplete on HP/IPF (HP Itanium). IY96924 JMS applications hang when multiple threads try to connect to a queue manager which is not running. IY96959 Exitbuffer parameters not passed to mqxr_sec_parms. IY97755 SIGSEGV in function rfxaddclqmgr during queue manager startup IY98002 MDB listener port gives error with custom property CCDT URL set. IZ01272 Potential security exposure in MQ client channels. IZ03429 Defects fixed in Websphere MQ Fix Pack 6.0.2.2 IZ13291 WMQ SSL Channel hangs in binding state. Stackit shows a hang in META_GENERATERANDOMSEED. SE26233 MQM400 PNGMQMCHL fails with MSGMCH3601, if user profile locale attribute is /qsys.lib/de_de.locale. (germany) SE26739 MQM400:PROBE CO052000 gets reported on server side for SSL enabled channels. SE27177 MQM400 dead letter queue handler fails with CPF0001 AMQ8750. SE27576 MQM400 MCAUSER *PUBLIC not recognised in CHGMQMCHL or CRTMQMCHL SE27700 MQM400 STRMQM fails to start queue manager with probe ZF089070. SE27911 MQM400 - MSGAMQ5522 and MSGCPF1151 generated on STRMQM for queuemanager when library QMQM in system portion of library list. SE28113 MQM400 jobs not ended after shutdown of MQ V6 queue manager. SE28167 MQM400 ENDMQM *ALL generates FDC with probe ID XY043007. SE28535 MQM400 - runmqbrk may suffer MCH3601 and reports probe XY353001. SE29192 MQM400 RSTLICPGM halts with AMQ6233. Fix Pack (V6.0.2.1) iSeries fix release date: 20 April 2007 Last modified: 20 April 2007 Status: Available iSeries download information Windows and UNIX fix release date: 30 March 2007 Last modified: 28 March 2007 Status: Available Windows and UNIX download information APAR Description IC49453 Alert monitor task bar icon not getting hidden when "alert monitor icon added to task bar" is set to "no" IC49520 When running with WebSphere application server, a complete list of the indoubts are not passed on a resynchronization IC49616 FDCs with AT040010 and AT003001 while reusing the agent connection IC49717 MQ external (native) exits called by the Java client incorrectly IC49767 Sigsegv in amqrrmfa when processing rrmreallocmsgs, causing the amqrrmfa (repository manager) to terminate. IC49826 Compile error "byref argument type mismatch" in WMQV6 VB sample program amqscnxb IC49857 MQ rc = 2354 mqrc_uow_enlistment_error when using msdtc in MSCS environment IC49914 IP address not shown properly in the error logs when 'localhost' is used in conname of the channel definition. IC49977 WebSphere MQ V6 explorer unable to show queues for remote z/OS queue managers connected via an intermediate queue manager IC50201 MQExplorer security failure connecting to z/OS IC50215 Access violation in dllhost with VB or STA application component using WMQ IC50309 MSCS hang when restart threshold has been set. IC50327 FDC with probe KN101001 from kqicloseit during mqdisc IC50415 WebSphere MQV6 explorer crashes while updating repository information under queue manager properties IC50431 WebSphere MQ XA client exposes security hole in MTS and com+ environments IC50448 Unable to deserialize object (JMS1061) IC50453 AMQSTRG0 comments say it is using MQTMC2 but the sample says memcpy(&trig.version, " 1", 4): AMQSTRG0.C IC50499 Amqidnet.exe unable to locate component when installing only the WMQ Java client on Windows IC50536 Queue handle leak when accessing alias or remote queues on z/OS IC50734 Access violation in the amqmtsxatm.dll when msdtc.exe is interacting with MQ. IC50882 Runmqsc or PCF cannot match channel status entries to a supplied conname for inbound channels after 6.0.1.1. IC50901 Amqxssvn process prevents queue manager restarting under MSCS control. IC50958 Amqrspin.dll and amqsspin.c sample source do not handle exit reason mqxr_sec_parms leading to channel termination by exit. IC50992 Deadlock during queue manager shutdown if a service stopcmd is launched. IC51090 AMQ6119 access violation with FDC probe ID XC130031 when MQ client is connecting to queue manager using SSL channels. IC51145 Regression in 6.0.2.0 of apars IC48024, IC48213 and IC4746 IC51658 Application fails to launch under Visual studio with 'the application failed to initialize PROPERLY(0XC0000008)' IY84659 Unusual sequence of requests on a thread currently associated with another transaction causes SIGSEGV. IY84998 Agent looping inside zlahealththread producing repeated probe XC330005 IY85622 Sigsegv FDC with xpprundestructors on function stack. IY85632 Netprty ignored in workload balancing within MQ clustering. IY85679 Unending series of xecl_w_long_lock_wait FDCs from function xllosspinlockwaitlock, e.g. probe XY086003 IY86287 Sigsegv in atxassociationcheckidle called (indirectly) from atxassociationremoveall. IY86322 Failure in "strmqm -r" during log replay IY86343 Connectionname passed to exit or conname displayed in runmqsc is 0.0.0.0 IY86361 WebSphere MQ V6.0 accounting messages display incorrect info. IY86365 XC130003 SIGSEGV in WebSphere MQ conversion routine xcsconvertstring IY86395 WMQ messages written to AIX error log have a resource name that is not quite right IY86541 WebSphere MQ message returned even though correlid does not match IY86600 Accounting messages are not generated after exceeding account count interval. IY86701 MQJE082 exception after installing WebSphere MQ 6.0 extended transactional client IY86822 Timeonqavg, timeonqmin and timeonqmax accounting messages values are always set to zero (0). IY86827 Queue manager is not able to write to queue manager log files. IY86828 Delivery problem with two listeners on same-name MQ destinations IY86994 WebSphere MQ clussdr channel does not start for messages committed via xa_commit IY87162 Problems with stop channel mode(force|terminate) calls. IY87173 Memory leak within WebSphere MQ cluster repository process amqrrmfa IY87192 Mqrc_connection_broken and recursive imq_impl_disc_backout IY87310 FFST by xcssimplepipecleanup with probe ID XY490002. IY87523 Corrections to ensure proper mapping between euro-enabled CCSIDs and respective codesets IY87638 Queue handle leak when using producer.send(destination, message). IY87702 Sigsegv e.g. in amqicdir, due to a getpwnam failure (e.g. if LDAP fails). IY87749 Hang in malloc inside WMQ signal handler while handling exception in malloc. IY87797 MQ runmqsc creates FDC with probe ID XC267011 showing SIGPIPE. IY87802 Output of the amqoamd utility may have spurious trailing characters for any 48-character queue names IY87804 WMQ acting as an XA resource manager calls ax_unreg in some exceptional cases disallowed by the XA spec IY87834 A base Java application works fine on MQ 5.3, but when run on MQ6.0 the application returns mqrc_iih_error. IY87844 Avoid caching password entry lookup for the UID of a process, until a connect successfully obtains it. IY88140 MQ JMS map/stream/text messages publish with blank rfh.format IY88151 Problem supplying the userid information via the mqenvironment when using client channel tables. IY88246 A WMQ semaphore set with a semid of 0 may be created with wrong ownership/permissions, which can hang WMQ processes IY88283 Channels would not start after upgrading to WMQ V6 IY88509 Channel with SSL enabled never goes to retry even when remote end is not reachable IY88514 Connections left open when an XA create session fails IY88551 Queue manager can fail to start without producing FFST failure report IY88573 Third quadrant enabled applications on HP-UX fail with FDC XY079022 IY88873 Memory leak in queue session when creating message consumers. IY88948 WMQ channel fails to start with AMQ9202 on Windows IY88954 Poolscavenger is never started and so connections are not closed in a running JVM. IY89259 Nullpointerexception in getconnectionccsid() or spiget() IY89374 JMS clients should not assume the default persistence (defpsist)on the system.broker.control.queue is yes. IY89484 ZL000128 zlamain during endmqm after probe XC037008 xcsexecprogram from AMQZMGR0 AMQ6026 IY89548 Java / JMS client native user supplied send/receive exits core dump on close channel, and also fail when resizing buffer. IY89674 Mqrc_dbcs_error returned to client when clustering used. IY89729 Passing a blank as a selector causes the listener to fail reporting invalid parameter. IY90046 Messageconsumer.close() may block indefinitely if there are many messages on the queue that do not meet selection criteria. IY90227 Client channel definition file created from WMQ 5.3 gives error when read from a WMQ V6.0 Java client when CRL is configured IY90244 Heap corruption can cause MQ exception handler to hang. IY90460 Amqrmppa process will not release threads causing high resource utilization. IY90548 Not being able to modify the 5000MS timeout period used while retrieving messages (internal chunktime value) IY90566 Cluster workload algorithm excludes local instances of cluster queues when putting via alias queues IY90707 Get(disabled) on an alias queue does not wake up "waiting" gets IY90712 Sigsegv in function rfxaddclqmgr during queue manager startup when migrating to WebSphere MQ V6.0 IY90995 An FDC reporting a SIGSEGV occurs if the queue manager attempts to obtain the group entry for a group ID that is undefined IY91959 If the clusrcvr channel is stopped, when it is re-started the repository cache is not properly updated causing workload issues IY93095 Performance hit when user generated msgIDs are used rather than MQ generated msgIDs. IY93381 Incorrect DST information in Java SDK 1.4.2SR5 included in MQ 6.0.2.0 refresh pack for HP-UX on PA-RISC and HP-UX on Itanium IY94369 A SIGSEGV can occur in function xtrestablishtracestatus when an application makes MQ C API calls using JNI SE25512 MQM400 -service program MQJBDF02 and MQJBND05 are built with terespace attribute set to *none SE25969 OSP-MSGAMQ8135-PAR AMQ8135 not authorized when using *allobj profiles with hash ( # ) character SE26291 MQM400 duplicate SSWC entries in cmqcfg rpgle copy file. the customer cannot compile their PCF/ILE RPG applications. SE26751 MQM400 wrkmqm option 22 results in CPF3C53 SE26780 MQM400 - strmqmlsr with IP address specified fails with AMQ9248 message. SE26805 MQM400 ship new PTF exit program amqiptfx SE26834 MQM400-OWNERSHIP of error logs incorrect after the batch submission (sbmjob) of ENDMQMLSR. SE26835 MQM400 Checking 'WMQ is active' during un-install deos not happen. SE27019 MQM400 STRMQM fails when the SYNCQ is damaged. SE28140 MQM400 STRMQM of V6 queue manager fails with CPF706D in AMQZXMAX SE28286 MQM400-WRKMQM remains inputminhibited when enduser has primary group profile (QPGMR) > 4000 endusers SE28327 MQM400 : RCRMQMOBJ fails with unexpected error on WMQ V6.0.2.0 SE28421 MQM400-ENDMQM MQMNAME(*ALL) fails with error number 3027 (operation not permitted) after WMQ V6 installation/migration. IY93389 Defects fixed in WebSphere MQ fix pack 6.0.2.1. Refresh Pack (V6.0.2.0) iSeries fix release date: 07 November 2006 Last modified: 07 November 2006 Status: Available iSeries download information Windows and UNIX fix release date: 16 October 2006 Last modified: 27 October 2006 Status: Available Windows and UNIX download information APAR Description IC48241 Messages received using messagelistener with durable subscribers are getting backed out once the application ends IC48295 Mqwindows-incorrect output for user-defined filter based on the overall channel status attribute for channels IC48397 Exits are deleted when migrating from WebSphere MQ V5.3 to V6.0 on Windows platforms. IC48478 MQJMS3023 in pub sub application after quiescing and restarting the queue manager. IC48512 FDC probe KY322000 indicates incorrect configuration of DCOM object IC48555 JMS pub/sub cleanup utility fails with 2009 in SSL environment IC48576 Program exceptions in Visual BASIC (vb) applications using the administration API. IC48662 Convert chained header to UCS-2 returns wrong reason code IC48678 Listener status inquire fails if the listener name length is 48 IC48680 Stopping the first instance of a receiver channel which is connected to multiple sender channel throws AMQ9533 error. IC48696 Java .lang . nullpointerexception is received when the path specified for explorer Java trace is incorrect IC48705 WebSphere MQ creates FDC with probe ZF165008 from wasreceivedata IC48711 Registry key wrong for explorer excludemessages IC48721 WebSphere MQ explorer message browser tool does not display some Japanese character sets IC48727 WebSphere MQ message AMQ7227 does not clearly define possible causes. IC48775 MQ Java classes when run as a client fail to negotiate to an MQ server running pre-fap 4 level, and incorrectly use hbint value. IC48795 Message browser included in WebSphere MQ explorer (V6) limits browsing to first 500 messages on queue IC48803 AMQ9207 invalid data received on a channel following a timeout on the Windows platform. FDC with probe ID CO052000 is created. IC48880 Custom services fail to migrate during migration to MQ 6.0. IC48908 Channel name changed by exit is not picked up when using the MQ explorer. IC48913 Performance problem getting message from a large queue IC48914 Conversion from CCSID 819 to 912 fails on get/convert IC48919 Locking errors when attempting to delete an in-doubt channel IC48920 Repeated resrcmon.exe FDC's following MSCS related errors IC49003 Multi threaded C++ application hangs IC49005 Mqtcpsdrport environment variable not working with WebSphere MQ version 6.0 IC49024 Explorer cannot connect to queue manager on HP-UX with CCSID 923 IC49051 WebSphere MQ explorer fails to display queues when run as a non-mqm user IC49084 .NET sample code (for cs & cpp files) supplied with WMQ V5.3/V6 is missing close and disconnect methods. IC49093 WMQ Java client change in the response expected from a negotiation call which occurred around fap 4 IC49150 DCOM security corruption on Windows 2003 SP1, XP SP2 and later IC49167 Data conversion error causes segmented messages to be dead letter queued (or return mqrc_format_error from mqget) IC49197 Performance problem on machines where MQ fails to calculate a required accuracy from the performance counters. IC49409 Clusrcvr disappearing at queue manager startup time. IC49431 Z or z in the mqmd.useridentifier field is incorrectly transcoded to j, causing authentication failures. IC49533 Mqrc_not_authorized received on mqconnx for a user ID passed in a mqcsp structure. IC49569 The extended transactional client receives FDCs with probe ID ZSL33001 and subsequently with probe ID ZS129001. IC49782 Mqwindows-incorrout memory leak when using a managed MQ dotnet client IC50156 Need one certificate to authenticate multiple clients IC50265 Java.lang.nosuchmethoderror: append" when processing JMS stream messages with WMQ 6.0.1.1 and was 5.0.2. IY80410 MQJMS2013 error when connecting to WebSphere MQ in bindings mode IY80806 MQ looping during startup when invalid attribute logbufferpager is located in the log stanza of the qm.ini file. IY80952 Memory leaks in clustered channels, and (V6) PCF filtering. IY81353 AMQ8135 mqrc_not_authorized errors when manually starting or stopping auto-defined clussdr channels. IY81358 Changes to MCAuseridentifier made by security exits not reflected in channel definitions IY81533 Connectionname is often not included in "channel SSL error" event messages. IY81628 MQJMS2005 reason code 2102 when 2035 mqrc_not_authorized occurred IY81661 Channel created using auto-definition exit has incorrect fields IY81671 XC308090 when xa_start and xa_rollback or xa_commit are issued concurrently for same xid. IY81714 MQMD userid put in upper case by V6 rcvr channel IY81774 WebSphere MQ as JMS provider not adhering to JMS specifications as per section "4.3.8 exceptionlistener". IY81875 Trace improvements for 'stop channels' functionality during queue manager ending IY81906 Migration to WMQ V6 sets new clwluseq queue attribute incorrectly IY81941 Very frequent channel starting and ending may cause excessive CPU usage in amqrmppa (channel pooling) processes IY81945 Hang in function kqiwakeupwaiter e.g. during quiesce endmqm IY82078 Sigsegv in aqpcopydatabuffers during MQPut to a dynamic queue. IY82241 If a correlid has been set as text, retrieving it as bytes returns null. IY82297 Rcdmqimg records image of damaged object leading to subsequent rcrmqobj failure. IY82419 Probe id's XC332070 and XC034071 from xlswaitevent. IY82629 Reset_iconv_table not found when installing client on HP-UX IY82779 Rcrmqobj of syncfile can result in misleading AMQ7047 message; also, references to rcrmqmobj should be to rcrmqobj. IY82806 Npmclass on local queue is not inherited from 'like' object. IY82834 When one or more /tmp/mqseries.[pid] files are deleted then endmqm can hang. IY82889 When using cross domain connection factory definitions in was V6 the TCPIP connection is not released during the cleanup. IY83093 Workload balancing temporarily unbalanced after a lot balancing IY83272 Amqsstop does not work on big endian machines. IY83321 Error messages logged by an application not in mqm group, may cause the system error log file to exceed the specified maximum IY83372 Xcsfreequickcell reports xecs_e_block_already_free in error. IY83535 MQ V6 can attempt to create more than logprimary + logsecondary log extents. IY83588 Extremely long running channel exits cause channels to end due to hbint not taking the exit time into account. IY83698 WebSphere MQ clussdr channels do not start if messages are put in a XA transaction, and xa_commit is called after mqdisc IY83704 Java.lang.unsatisfiedlinkerror trying to load LIBMQJEXITSTUB01.SO for MQ client only installations. IY83775 C++ client disconnect causes mqrc_hconn_error in non-C++ applications IY83778 Messages do not get rolled back in point to point domain when exceptions occurs in MDB IY84127 When QM runs out of resource and error logic is being exercised,mq calls xcsfreequickcellblock() instead of xcsfreequickcell() IY84356 Possible loss of queue manager data area if strmqm detects a problem with files or directories during startup IY84410 FDC with probe AT002001 is generated when atm.rmidgenerator reaches 2147483647 IY84479 Code change for function "strptr" at line 541 of AMQSAXE0.C IY84777 A probe ZX033006 FDC with errorcode xecs_e_seg_in_use may be dumped from function zxccleanupwlmserver during endmqm IY84934 FDC showing SIGSEGV in function rrxconvertchannelfromdiskver or zxcrestoreobject when migrating from WMQ V5.2 to V6.0 IY85202 2017 mqrc_handle_not_available is reported in WMQ at service levels 6.0.1.0 and 6.0.1.1 IY85203 WebSphere MQ script reset_iconv_table may cause blank file name or incorrect permissions on conversion tables IY85541 AMQ9426 queue manager unable to rejoin cluster IY85542 Reset cluster does not remove deleted repository entry IY85562 A tcp send failure may retry indefinitely as of MQ5.3 CSD11. IY85620 Sigsegv in zxcrestoreobject on starting a WMQ 5.2 queue manager under WMQ V6. IY86606 Cluster subscriptions made for non-cluster queues SE24179 MQM400-AMQ8059 RC2292 (Unknown entity) on CRTMQM SE24271 MQM400 abnormal end of MQ application program may hang queue manager SE24477 MQM400 MCH0601 after multiple strmqmchl SE25214 MQM400 rfrmqmaut removes group members authorities SE27124 MQM400-AMQ8059 RC2292 (unknown entity) on crtmqm IY89836 Defects fixed in WebSphere MQ refresh pack 6.0.2.0. Fix Pack 6.0.1.1 (V6.0.1.1) Fix release date: 8 May 2006 Last modified: 13 October 2006 Status: Available iSeries download information Windows and UNIX download information APAR Description IC45004 Performance slow downs and timeouts whilst using a queue status monitor IC46861 V5.3 to V6: cannot update API exit definitions for migrated queue manager using the eclipse explorer GUI. IC47255 When message selector is used with durable subscriber and application terminates abruptly, the messages are lost. IC47289 Deadlock on object catalog caused by performance events on system.auth.data.queue IC47462 Probe PC082099 from pcminquireclusterqueuemanager IC47466 WMQ version 6 explorer client SSL key stores remote administration IC47481 Multi-threaded client return mqrc_already_connected IC47528 Rcdmqimg taking long time to complete IC47557 Unable to start/stop auto-defined cluster sender channels using MQ explorer IC47595 Duplicate listeners in output of runmqsc dis lsstatus command IC47771 Channel terminated FFST RM487001 with memory access violation XC130031. IC47804 MQ MSCS resource fails to apply local mqm group permissions to the directories containing the queue manager data even after IC43947 IC47879 When the MQ V6 explorer is used to manage a z/OS queue manager any lowercase userids are rejected. IC47881 XY324190 (getsubpoolslock) winnt error 6 from createmutex when debugging application under Windows terminal services IC47974 Trap due to a stack underflow in a COM+/MTS environment whilst continually connecting to a non-running queue manager IC47978 Timing problem may cause WebSphere MQ for Windows queue manager not to start in auto mode. IC48024 Error messages AMQ6125 & AMQ6183 are logged when displaying context menu of a remote queue manager. IC48031 .NET WMQ transport for SOAP client application receives no response when connected as MQ client to z/OS queue manager. IC48046 Mqmessageconsumer.receive(timeout) does not honour the timeout value when message selectors are used IC48069 Install of 6.0 client fails on XP without service pack 1 installed. Error message incorrectly reports AMQ4366. IC48143 Queue list incomplete from mqcmd_inquire_q if include mqiacf_cluster_info and cluster queues IC48156 AMQ9210: remote attachment failed IC48213 Max active channels displays misleading value IC48217 EOFexception occurs when calling mqmessage.readstring() IC48243 Unable to add remote queue manager where host-name contains under-bar character. IC48309 Com+ application hangs when connecting to queue manager IC48310 Xcsrefreshmtime cuts an FDC with probe ID XC457010 IC48596 WebSphere MQ using incorrect user ID, and receiving mqrc_not_authorised (2035) errors, in a com+ environment IC48699 Deadlock within the MQ com+ layer following a connection broken return code in the extended transactional client IC49065 Using PCF, a non-mqm user can start/stop channels without having +ctrl authority IC49148 WMQ V6 hashtable port number property returns exception 'system.invalidcastexception' in amqmdnet.dll IY73649 Mqcmd_inquire_q_names, mqcmd_inquire_channel_names, AMQ2035 mqrc_not_authorized IY76063 Channels in stopping/binding state which cannot be stopped using stop chl(chlname) mode(force) IY76845 Failure to perform data conversion of an MQRFH2 which contains namevaluedata which is not aligned on a 4 byte boundary. IY77059 Probe id's MQ000010 and XY180010 following application of IY74420. IY77246 Mqchllib and mqchltab not honored by WebSphere MQ server. IY77448 Rare deadlock possibilities involving FDC reporting IY77769 Messages remain on the system.cluster.transmit.queue after the channel is suppressed by a chadexit. IY78390 Incorrectly built GCC 2.95.2 libraries shipped with WMQ V6.0 for Linux X86 platform IY78429 Channel process (amqrmppa) may fail due to bad data from pre- CSD10 Java client IY78438 Clustering: large numbers of subscriptions cause slowdown of repository cache creation (during strmqm); or recreation IY78634 MQExplorer does not retain 'automatic refresh' disablement. IY78636 In MQ explorer date and time are sorted as string IY78788 Sigsegv in aqsreleasebclist during queue manager shutdown. IY78836 Jmsadmin cannot find its configuration file IY79100 Clustering uneven message distribution during workload balancing IY79142 Channels fail with AMQ9631 when using a global server certificate IY79158 Rare timing condition in mqconn causes hang IY79226 Some processes (e.g. amqrmppa) may not recreate a trace file (.trc) if it has been deleted and trace restarted. IY79234 Xaer_rmerr returned by extended transaction client XA calls, following mqrc_another_q_mgr_connected from mqconn or mqconnx IY79288 FDC probe XC130003 reporting sigbus or sigsegv in broker function fkirestoresubscription IY79301 Incorrect installation of refresh pack 6.0.1.0 on HP-UX if /var/adm/sw/save does not exist IY79414 SSL distinguished name does not match peer name IY79457 WMQ V6.0 client channel fails when a mqcsp structure is specified on the mqcno passed into a mqconnx call. IY79616 Linux: small timing window can result in spurious semaphore unlock, giving FDC probes such as XC346012. IY79663 XC130004 sigsegv out of kpisyncpoint during an xa_commit call IY79668 AMQ9661: bad SSL data from peer on channel IY79906 After FDC with probe ID AD031001, component adiwritefile with comment RC=0 from write, the queue manager can fail to restart. IY79915 Write FFST if deleting a cluster object with a live subscription IY80064 Applications fail to connect to a queue manager. FFSTs with probe ID XY029001 dumped. IY80142 Amqoamd -s fails with mqrc_hconn_error on WMQ V6.0 IY80247 Subscription to full repository manager object is deleted if there is a problem when the subscription is renewed IY80428 Amqrrmfa can end abruptly when two or more cluster receivers are defined with the same name within the same cluster. IY80596 RM550000 + XC130003 FFSTs in mqconn from 64-bit WMQ V6.0 client application using a ccdt containing old channel definitions. IY80863 WMQ V6 HP-UX (itanium) performance problems related to high workload. IY81580 Cluster workload exit reason not set for cluster PCF message IY81696 WebSphere MQ V6 on Solaris X86-64 connect or other MQ APIs hang when some MQ of the applications are 32 bit. IY81993 SNA channels fail at WMQ V6.0 due to missing library LIB64/AMQCC62A_R IY82062 Deadlock in COM+ when one thread issues an mqconn which fails, at the same time as another issues mqdisc IY82071 Wrong MQMD passed to the pre data conversion MQGet API crossing exit IY82794 Unable to set mapnamestyle (mnst) when defining connectionfactory using the jmsadmin tool. SE21231 MQM400 agent jobs are not being ended after FDC probe ZL000028 has been logged SE21437 MQM400 unable to restart queue manager. AMQ8041 on strmqm SE22928 MQM400 V6.0 - FDC probe XY353002 doing external commit - job AMQZLAA0 - MCH3601 *escape in libmqml_r zsqverifypcd seq #7 SE23096 MQM400-MSGMCH3601 exception occurs in LoadExit when MQCD structure supplied by CHAD exit is not valid. SE23098 OSP qmname can't be defined in MQ clntconn channel with CL commands SE23241 MQM400 strmqmmqsc fails with -MCH3601 and CEE9901 exception for *DFT queue manager. SE23550 MQM400 crtmqm or strmqm receives MSGAMQ7155 and MSGAMQ7128 SE24862 Strmqmmqsc under a profile authorized with qmqmadm group authority on iSeries fails IY89815 Defects fixed in WebSphere MQ fix pack 6.0.1.1. (part 1 of 3) IY90003 Defects fixed in WebSphere MQ fix pack 6.0.1.1. (part 2 of 3) IY90004 Defects fixed in WebSphere MQ fix pack 6.0.1.1. (part 3 of 3) Refresh Pack 6.0.1.0 (V6.0.1.0) Fix release date: 18 October 2005 Last modified: 13 October 2006 Status: Available iSeries download information Windows and UNIX download information APAR Description IC45799 Probe XY051025 reporting duplicate AMQXCS2.DLL found. no duplicate exists. the path to the duplicate copy is empty. IC45816 FDC files with probe ids XC130031 and HL081010 but no message when the logpath is set incorrectly. IC45869 MQ service fails to stop, and trap occurs if a queue manager is deleted. IC45894 Cluster administrator or MQ MMCs hangs when an MSCS cluster contains more than queue manager resource or custom service. IC46074 Client channel to z/OS never times out after a connection drop IC46145 Mqrc_no_msg_available MQRC2033 when getting locked segments IC46192 RFH2 errors when attempting to connect WebSphere MQ V6 SOAP to a CICS SOAP client or a CICS SOAP service. IC46301 MC011057 when stopping Windows while MSCS controlled queue manager is still running. IC46407 Incorrect truncation of queue file during log full caused a damaged queue IC46433 MQ .net classes need +inq authority to get dynamic queue name IC46530 AMQ2018 .net mqbegin IC46539 .net dotnet dynamic queue name mqrc_dynamic_q_name_error 2011 accessqueue IC46548 Mqrc_options_error is returned if qpmo_alternate_user_authority is specified with mqqueuemanager.put() call. IC46653 Mqqueuemanager constructor does a connect to the QM, but it does not check to see if it is connected already before reconnecting. IC46666 FDCs while deleting a stopped channel IC46698 Local cluster queue not listed in display qcluster, or in WMQ explorer, after refresh cluster(clname) repos(yes) IC46766 Putdatetime property in 'mqmessage' MQ .net class is read only and cannot be altered or set. IC46774 MMC shows incorrect status information, overlapping/multiple amqmsrvn processes IC46920 Windows, information center fails to start. IC46955 Various setmqscp problems IC46965 Was V6 connectionfactories not bound with WMQ V6 IC46987 Coinitialize failure rpc_e_changed_mode (-2147417850) with MSCS IC47013 Traps or XC130031 with any MQ call stack but O/S stack dump shows xcssynchronizecountertime. IC47032 JMS client support for the pgm multicast protocol IC47044 SSL authentication with JMS realtime node fails from JMS client when JDK1.4.2 is used at client side with legalargumentexception IC47181 Problem in linking COBOL programs with Visual Age COBOL compiler on Windows with MQ 6.0 IC47224 Multiple poolscavenger threads created when using either WebSphere application server version 5.X or WebSphere MQ. IC47236 Mqrc_context_handle_error (2097 error)- when pass_all_context option is used with Java distribution list. IC47275 Message browser fails to show list of MQ messages for a queue. IC47332 MQ client AMQ9691 error when trying to add a certificate using amqmcert -a when the certificate is already present in the store IC47343 Mqerrorpath variable no longer sets path for error logs in WebSphere MQ V6.0 IC47443 JMS messageproducer memory leak. IC47447 Messages not acknowledged when using connectionbrowsers with auto_ack or dups_ok sessions IY60843 Message selectors that contain the <> (not equal) operator do not work. IY66331 When mqpmo.recspresent is set in a client application MQPUT1 fails with 2154 (mqrc_recs_present_error). IY69753 Hang in xihquerythreadentry on Solaris IY70366 FDC ZD008040 from zdmopendeferredq when starting queue manager IY70415 Incorrect message may be returned to MQGet with mqgmo_wait and mqgmo_msg_under_cursor IY71004 MQ logs fill up and the queue manager will not restart after many AO084010 FDCs. IY71204 Damaged temporary dynamic queue inadvertently added to pool of reusable queues at startup IY71335 Channel remains in stopping status after stop channel mode (terminate) command has been issued IY72218 Mqdisc fails with mqrc_hconn_error (2018 0X7E2) and the CICS application returns abnormal termination U8035. IY72519 AMQ9652 error message generated incorrectly when the cryptographic store / key repository password has expired. IY72714 Failure of LDAP server providing O/S user identification data to WMQ through the getgrent interface observed on Solaris IY72844 Queue manager cannot restart: FDC with probe ID HL083114. IY72981 Truncated was FDCs (probes ZF178* to ZF216*) IY73045 Set logbufferpages default to 128, as documented (was 64) IY73062 Selector ignored on connectionconsumer IY73149 Japanese message catalog contains invalid DBCS characters also Traditional Chinese - AIX only IY73202 Software may get permissions failure reading amqcap.inf file IY73543 Probe XC307004 FDC from xlsrequestmutex (Linux only) IY73548 MQ may write a XC130003 FDC under zcpqueryterminus when using XA IY73907 FDC with probe XC006001 from xcsfreemem from the repository manager process. IY74045 RM409000 FFST from rriwaitsecondary IY74094 User-level object type name inconsistencies IY74339 Sigbus/sigsegv in kqiinquirequeuehandlestatus IY74420 MQ hang following pthread_cancel on Solaris. xcskillthread, xlslockmutexfn mcatype(thread) IY74705 Queue managers hang when using event messages and may see probe XY337080 from xlllonglockrequest. IY74818 WMQ not rolling back a transaction after XA calls return xaer_nota IY74915 Performance impact on AIX when an API exit is invoked IY75237 Migrating queue manager to WMQV6 sets MCA type of all the channels to process. IY75252 MQ commands fail if the MQ files path is specified at the end of the path string and is not terminated with a colon (:). IY75467 WMQ broker dies with probe XC130003 FDC in function faiadderrortag IY75589 MQJMS1061: unable to deserialize object message due to java.lang.classnotfoundexception when using WebSphere MQ IY75854 Publishing applications are delayed by up to 60 seconds when publishing. Error 2033 msg_not_available return code is seen. IY76101 Sigsegv in amqfcxba after MQRFH2 message sent to system.broker.control.queue IY76118 MQ explorer V6.0, broker V6.0, empty object tables, Linux. IY76314 XA client ending abruptly leaves outstanding units of work locked until they span the active log, when they are backed out. IY76712 Unpredictable results when the topic associated with a durable subscription changes when using the MQ broker. IY76799 Failed call to getpeername leaks file descriptor in amqrmppa IY77233 Object catalog corruption during resource exhaustion IY77282 Version 6 channels do not trigger start IY79428 Probe XC307010 when attempting to raise a COD report message in response to a transactional MQGet on MQ V6. SE19791 MQM400 channel pair remains in retrying/binding status after a network change and does not recover. SE20571 MQM400- AMQ6993 message incorrectly generated when endmqm submitted in batch SE21176 MQM400 wrkmqm generates MSGMCH6902 and MSGCZM1212 when more than nine queue managers to be displayed SE21259 MQM400 security audit journal entries produced when using OS V5R3 with user *USER with no special authorities SE21565 MQM400 - verifying MQ V6 using chkprdopt returns error CPF0C20 with programs AMQI0XRL, AMQI0XVL, AMQI0X1L. IY89814 Defects fix in WebSphere MQ refresh pack 6.0.1.0. (part 1 of 5) IY89954 Defects fixed in WebSphere MQ refresh pack 6.0.1.0. (part 2 of 5) IY89970 Defects fixed in WebSphere MQ refresh pack 6.0.1.0. (part 3 of 5) IY90006 Defects fixed in WebSphere MQ refresh pack 6.0.1.0. (part 4 of 5) IY90007 Defects fixed in WebSphere MQ refresh pack 6.0.1.0. (part 5 of 5) Recent and planned Fix Pack content summary To show the APARs flagged for the combination of fix pack and platform select the appropriate link. Fix Pack 6.0.2.1 Fix pack 6.0.2.2 Fix pack 6.0.2.3 All for this platform Windows List List List List AIX List List List List HP-UX (PA-RISC) List List List List HP-UX (Itanium) List List List List Solaris (SPARC) List List List List Solaris (x86-64) List List List List Linux (x86) List List List List Linux (x86-64) List List List List Linux (zSeries) List List List List Linux (s390x) List List List List Linux (Power) List List List List iSeries List List List List All in Fix or Refresh Pack List List List * Note this Fix Pack has not been delivered. The APARs listed are planned content but this could change before the Fix Pack is made available. Change history Last modified: 30 October 2008 30 October 2008: Added information on availability of WMQ v6.0.2.5 for iSeries. 06 October 2008: Added information on availability and content for WMQ v6.0.2.5. 26 June 2008: Added information on availability of WMQ v6.0.2.4 for iSeries. 30 May 2008: Added information on availability and content for WMQ v6.0.2.4 11 March 2008: Added information on the availability of WMQ v6.0.2.3 for iSeries. 01 February 2008: Added information of availability and content for WMQ v6.0.2.3 14 September 2007: Added information of availability of WMQ v6.0.2.2 for iSeries. 22 August 2007: Added 6.0.2.2 availability and content. The next fix pack is planned to be 6.0.2.3. 19 July 2007: Add target date for fix pack 6.0.2.3. Add cross reference table by fix pack and platform to the end of the document. 20 April 2007: Updated availability date of 6.0.2.1 for iSeries 28 March 2007: Add Fix pack 6.0.2.1 is available and content. The next fix pack is planned to be 6.0.2.2. 27 February 2007: Modify fix pack 6.0.2.1 release date to 1Q2007 07 November 2006: Add refresh pack 6.0.2.0 for iSeries 13 October 2006: Add refresh pack 6.0.2.0. 08 May 2006: Created fix list page. ------- Note: ------- Recommended Fixes for WebSphere MQ Abstract This page provides links to the latest available maintenance for the WebSphere MQ and MQSeries products. Content IBM WebSphere MQ Version 7.0 IBM WebSphere MQ Version 6.0 IBM WebSphere MQ Version 5.3 and 5.3.1 IBM MQSeries Link for R/3 V1.2 IBM MQSeries Version 5.1 IBM MQSeries for VSE IBM WebSphere MQ ESE v6.0 A list of the planned release dates for future maintenance can be found at the following link. Product & Version Latest Maintenance Pack Info. All Platform Downloads IBM WebSphere MQ Version 7.0 AIX Fix Pack 7.0.0.1 Platform downloads HP-UX Itanium Fix Pack 7.0.0.1 Platform downloads HP-UX PA-RISC Fix Pack 7.0.0.1 Platform downloads i5/OS Fix Pack 7.0.0.1 - Linux on POWER Fix Pack 7.0.0.1 Platform downloads Linux on x86 Fix Pack 7.0.0.1 Platform downloads Linux on zSeries s390x Fix Pack 7.0.0.1 Platform downloads Linux x86-64 Fix Pack 7.0.0.1 Platform downloads Solaris SPARC Fix Pack 7.0.0.1 Platform downloads Solaris x86-64 Fix Pack 7.0.0.1 Platform downloads Windows Fix Pack 7.0.0.1 Platform downloads z/OS - - Note: The "Platform downloads" contain all Refresh Packs, Fix Packs and Interim Fixes for each platform. Product & Version Latest Maintenance Pack Info. All Platform Downloads IBM WebSphere MQ Version 6.0 AIX Fix Pack 6.0.2.5 Platform downloads HP-UX Itanium Fix Pack 6.0.2.5 Platform downloads HP-UX PA-RISC Fix Pack 6.0.2.5 Platform downloads i5/OS Fix Pack 6.0.2.5 - Linux on POWER Fix Pack 6.0.2.5 Platform downloads Linux on x86 Fix Pack 6.0.2.5 Platform downloads Linux on zSeries Fix Pack 6.0.2.5 Platform downloads Linux on zSeries s390x Fix Pack 6.0.2.5 Platform downloads Linux x86-64 Fix Pack 6.0.2.5 Platform downloads Solaris SPARC Fix Pack 6.0.2.5 Platform downloads Solaris x86-64 Fix Pack 6.0.2.5 Platform downloads Windows Fix Pack 6.0.2.5 Platform downloads z/OS - - Note: The "Platform downloads" contain all Refresh Packs, Fix Packs and Interim Fixes for each platform. More information about V6 maintenance can be found in the Maintenance Strategy for V6.0 document. Product & Version Latest Fix Pack Release Date Comments IBM WebSphere MQ Version 5.3 IBM WebSphere MQ Version 5.3.1 IBM WebSphere MQ Express Version 5.3 Download to all Fix Packs for Multiplatforms Fix Pack 14 Dec. 2007 for i5/OS Fix Pack 14 Feb. 2008 for z/OS - - for OpenVMS - Alpha Fix Pack 14 Sep 2008 for OpenVMS - Itanium Fix Pack 14 Sep 2008 for HP NonStop Server V5.3.1.4 Oct 2008 Product & Version Latest Fix Pack Release Date Comments IBM MQSeries Link for R/3 V1.2 CSD03 March 2005 Only available from your IBM Service Representative Product & Version Latest Fix Pack Release Date Comments IBM MQSeries Version 5.1 MQSeries for Compaq NSK CSD03 Oct 2004 MQSeries for Compaq OVMS Alpha CSD05 Feb 2006 MQSeries for Compaq Tru64 UNIX CSD09 Mar 2003 MQSeries for Sun Solaris on Intel CSD09 Aug 2002 Product & Version Latest Fix Pack Release Date Comments IBM MQSeries for VSE Only available from your IBM Service Representative Version 2.1.0 - EOS 30 Sep 2005 - - Version 2.1.2 - - Change History Last updated: 30 January 2009 11 November 2005: Added WebSphere MQ v6 Refresh Pack 1. 16 November 2005: Added WebSphere MQ v6 for z/OS link. 17 November 2005: Released WebSphere MQ v5.3 for OpenVMS Fix Pack 8. 5 December 2005: Minor modifications, included V6 maintenance strategy link. 25 January 2006: Released WebSphere MQ v5.3 Fix Pack 12. 27 January 2006: Changed releases dates for WebSphere MQ 5.3 Fix Pack 12 to Jan 2006. 16 February 2006: Released MQSeries for Compaq OVMS Alpha 5.1 Fix Pack 5. 4 April 2006: Released MQSeries for Compaq OVMS Alpha/Itanium 5.3 Fix Pack 9. 7 April 2006: Changed the recommended download for WebSphere MQ 5.3 for i5/OS from Fix Pack 12 to Fix Pack 11. 13 April 2006: Changed the recommended download for WebSphere MQ 5.3 for i5/OS from Fix Pack 11 to Fix Pack 12. 17 May 2006: Released 6.0.1.1. 13 October 2006: Released 6.0.2.0 for Windows and UNIX 17 October 2006: Released MQSeries for Compaq OVMS Alpha/Itanium 5.3 Fix Pack 10. 27 October 2006: Released 6.0.2.0 for i5/OS. 26 December 2006: Released 5.3.0.13. 9 February 2007: Released 5.3.0.13 for i5/OS 30 March 2007: Released WebSphere MQ v6.0.2.1 for AIX, Linux, Solaris and Windows 30 March 2007: Released WebSphere MQ v5.3 FP 11 for Open VMS 13 April 2007: Released WebSphere MQ v6.0.2.1 for HP-UX PA-RISC and HP-UX for Itanium 20 April 2007: Released WebSphere MQ v6.0.2.1 for i5/OS 8 May 2007: Removed reference to V2.2.1 products as these are no longer in service. 23 August 2007: Released WebSphere MQ v6.0.2.2 for UNIX and Windows. 24 August 2007: Released WebSphere MQ v5.3 FP12 for Open VMS 14 September 2007: Released WebSphere MQ v6.0.2.2 for i5/OS 8 October 2007: Released WebSphere MQ v5.3.1.1 for NSS 28 December 2007: Released WebSphere MQ v5.3 FP14 for UNIX and Windows 01 February 2008: Released WebSphere MQ v6.0.2.3 for AIX, Linux and Windows. 07 February 2008: Released WebSphere MQ v6.0.2.3 for HPUX and Solaris. 28 February 2008: Released WebSphere MQ v5.3. FP14 for i5/OS. 06 March 2008: Released WebSphere MQ v5.3 FP13 for Open VMS. 11 March 2008: Released WebSphere MQ v6.0.2.3 for i5/OS. 03 April 2008: Released WebSphere MQ v5.3.1.2 for HP NonStop Server. 30 May 2008: Released WebSphere MQ v6.0.2.4 for UNIX and Windows. 20 June 2008: Released WebSphere MQ v6.0.2.4 for i5/OS. 09 July 2008: Removed WebSphere MQ v5.2 & v5.2.1 details. 10 July 2008: Released WebSphere MQ v5.3.1.3 for HP NonStop Server. 11 September 2008: Released WebSphere MQ v5.3 FP14 for Open VMS. 03 October 2008: Released WebSphere MQ v5.3.1.4 for HP NonStop Server. 06 October 2008: Released Websphere MQ v6.0.2.5 for UNIX and Windows. 30 October 2008: Released Websphere MQ v6.0.2.5 for i5/OS. 20 January 2009: Released WebSphere MQ v7.0.0.1 for UNIX and Windows 30 January 2009: Released Websphere MQ v7.0.0.1 for i5/OS. ------- Note: ------- thread: Q: Hi, Presently one of my production server is having the MQ 6.0.2.0, We are planning to install latest FIX Pack MQ 6.2.0.5 For installing the latest fix pack do i need to un-install and install the whole MQ or it's ok if i install directly MQ Fix pack A: Short answer: NO, you do not have to uninstall - it's a FixPack - logic says it's there to fix something, which it can't do if that 'something' has been uninstalled. ------- Note: ------- Title: IBM WebSphere MQ Security Bypass Vulnerability Severity: MODERATE Description: IBM WebSphere MQ is a commercially available messaging engine for enterprises. IBM WebSphere MQ is prone to a security-bypass vulnerability because the application fails to properly restrict access to certain functionality. Specifically, attackers can access a queue manager through a SVRCONN (MQ client) channel even if it is secured with a security exit or 'mcauser'. Attackers can exploit this issue to bypass certain security restrictions, connect to a queue manager in an unauthorized manner, and obtain potentially sensitive information; other attacks are also possible. This issue affects versions prior to: 5.3 Fix Pack 14 6.0 Fix Pack 6.0.2.2 Affected Products: IBM WebSphere MQ 5.3.0 IBM WebSphere MQ 6 References: ------- Note: ------- IBM WebSphere MQ Commands Local Privilege Escalation Issues Title : IBM WebSphere MQ Commands Local Privilege Escalation Issues VUPEN ID : VUPEN/ADV-2009-0511 CVE ID : CVE-2009-0439 Rated as : Moderate Risk Remotely Exploitable : No Locally Exploitable : Yes Release Date : 2009-02-24 Technical Description Multiple vulnerabilities have been identified in IBM WebSphere MQ, which could be exploited by local attackers to gain elevated privileges. These issues are caused by unspecified errors in the command line tools "setmqaut", "dmpmqaut" and "dspmqaut", which could allow malicious users to execute arbitrary code with elevated privileges on a vulnerable UNIX system. No further details have been disclosed. Affected Products IBM WebSphere MQ 5.x IBM WebSphere MQ 6.x IBM WebSphere MQ 7.x Solution IBM WebSphere MQ 6.0 - Apply the latest Fix Pack (6.0.2.6 or later) or APAR IZ40824 : http://www-01.ibm.com/support/docview.wss?uid=swg24022268 IBM WebSphere MQ 7.0 - Apply the latest Fix Pack (7.0.0.2 or later) or APAR IZ40824 : http://www-01.ibm.com/support/docview.wss?uid=swg27006037 References http://www.vupen.com/english/advisories/2009/0511 http://www-01.ibm.com/support/docview.wss?uid=swg21376107 http://xforce.iss.net/xforce/xfdb/48529 Credits Vulnerability reported by the vendor. ChangeLog 2009-02-24 : Initial release ------- Note: ------- thread: Q: Hello, I work on EDI and do not have much experience in handling Java and MQ Errors. I was working to configure JMS messaging and encountered the following error while running JMSAdmin. $ ./JMSAdmin -v 5724-H72, 5655-L82, 5724-L26 (c) Copyright IBM Corp. 2002,2005. All Rights Reserved. Starting Websphere MQ classes for Java(tm) Message Service Administration Initializing JNDI Context... INITIAL_CONTEXT_FACTORY: com.ibm.ejs.ns.jndi.CNInitialContextFactory PROVIDER_URL: iiop://localhost:900/ Class specified by INITIAL_CONTEXT_FACTORY not found in CLASSPATH Here is a snapshot of the JMSAdmin.config file #INITIAL_CONTEXT_FACTORY=com.sun.jndi.ldap.LdapCtxFactory #INITIAL_CONTEXT_FACTORY=com.sun.jndi.fscontext.RefFSContextFactory INITIAL_CONTEXT_FACTORY=com.ibm.ejs.ns.jndi.CNInitialContextFactory #INITIAL_CONTEXT_FACTORY=com.ibm.websphere.naming.WsnInitialContextFactory #PROVIDER_URL=ldap://polaris/o=ibm,c=us #PROVIDER_URL=file://localhost/ PROVIDER_URL=iiop://localhost:900/ Here is the content of the JMSAdmin file : java -classpath /usr/mqm/java/lib/com.ibm.mqjms.jar -Djava.ext.dirs="$libpaths" -DMQJMS_LOG_DIR=$MQ_JAVA_INSTALL_PATH/log -DM QJMS_TRACE_DIR=$MQ_JAVA_INSTALL_PATH/trace -DMQJMS_INSTALL_PATH=$MQ_JAVA_INSTALL_PATH com.ibm.mq.jms.admin.JMSAdmin $* Can you please let me know if I am doing anything wrong, or what is needed to run the JMSAdmin utility in AIX .. ------- Note: ------- thread: Q: when i compiling my api exit, i got the error: ld: 0711-317 ERROR: Undefined symbol: .MQXEP ld: 0711-345 Use the -bloadmap or -bnoquiet option to obtain more information. collect2: ld returned 8 exit status make: 1254-004 The error code from the last command is 1. anybody can help me? A: You are missing the "-lmqmzf" in the line xlc -q64 -e MQStart -bE:mirrorq.exp -bM:SRE -o mirrorq mirrorq.c -I/usr/mqm/inc -L/usr/mqm/lib64 -lmqm -lmqmzf ------- Note: ------- thread: Q: Hi, Can someone please confirm what is the deafult maximum disk queue size on AIX (MQ is v6.0.2.5) - I cannot find it documented anywhere. Also there seems to be little documentation on the impacts of increasing it via theDefaultQFileSize setting in qm.ini to a large value (eg. 2Gb) - can it be set to this size ? I ask because we had a Production problem today where messages were being written to the Dead Letter queue with a reason code 2056 (Queue Space Not Available). All applications connected to the QMgr were reporting problems. The /var/mqm/ directory was only using 18% disk space. I discovered that the actual queue refered to in the 2056 Dead Letter messages was holding 75,000 for a system that had only reads the messages 3 times a day. The actual queue file in /var/mqm/qmgrs/QMGR/queues/queue_name was 1.07Gb, after clearing 20,000 messages from the queue the QMgr was OK and no more messages were going to the Dead Letter Queue. We're looking at getting the application to process the messages more often but it would be good to have a bigger buffer on the queue size if I can. A: AFAIK it's the same as the maximum size of a file on your OS/hardware combination. http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/topic/com.ibm.mq.amqaac.doc/aq10270_.htm Also there seems to be little documentation on the impacts of increasing it via theDefaultQFileSize setting in qm.ini to a large value (eg. 2Gb) - can it be set to this size ?[/quote] Yes - see here for details. IIRC you have to enable large file support in AIX as well; not entirely certain I'm right on that.... Don't forget that no matter how much space you supply, the queue will consider itself full when it hits MaxDepth. If the queue's only read 3 times a day ensure this value is high enough. But of course you knew that. A: for your problem, focus on the queue's Max Message Size and Max Depth parameters, as well as enabling the largefiles option on your server. DefaultQFileSize is only for performance tuning and trying to keep messages in memory versus spilling over to disk, for queues that are contantly being drained of new messages. That is not your problem. Going to disk is OK for you. A: Thanks for your help. I'll document the real problem here for reference. The operating system file limit was 1Gb (1048575 blocks * 1024 bytes)... [mqm@xxxxxx:/data/home/mqm]> ulimit -a core file size (blocks, -c) 1048575 data seg size (kbytes, -d) 131072 file size (blocks, -f) 1048575 <--- max memory size (kbytes, -m) 32768 open files (-n) 2000 pipe size (512 bytes, -p) 64 stack size (kbytes, -s) 32768 cpu time (seconds, -t) unlimited max user processes (-u) 128 virtual memory (kbytes, -v) unlimited ------- Note: ------- arcticle: In the AIX error log, there are errors with label AMQFFSTx, such as AMQFFST1 AMQFFST2 AMQFFST3 AMQFFST4 Technote (troubleshooting) This document applies only to the following language version(s): English Problem(Abstract) You see in the AIXr error log, errors with a label format of AMQFFSTx, such as AMQFFST1, AMQFFST3, AMQFFST4. Symptom An example is shown below: LABEL: AMQFFST3 IDENTIFIER: 8xxxxxxx Date/Time: Sun Dec 31 11:31:18 EST Sequence Number: 3770 Machine Id: 00FFFFFF Node Id: pppppdc Class: S Type: UNKN Resource Name: MQSeries NONE Description SOFTWARE PROGRAM ABNORMALLY TERMINATED Probable Causes UNDETERMINED Failure Causes SOFTWARE PROGRAM Recommended Actions REVIEW DETAILED DATA CONTACT APPROPRIATE SERVICE REPRESENTATIVE Detail Data DETECTING MODULE xcsCloseEventSem SOFTWARE ERROR CODE 0000 0001 FILE NAME /var/mqm/errors/AMQ30656.0.FDC Cause Sometimes, WebSpherer MQ errors will cause the AIX operating system to put entries into the AIX errort log that have the label of AMQFFSTx, such as AMQFFST1, AMQFFST3, AMQFFST4. Resolving the problem For more details on the MQ problem, review the file mentioned at the end of the error entry in the AIX errpt, such as: FILE NAME /var/mqm/errors/AMQ30656.0.FDC When an abnormal situation happens, MQ creates an FDC (First Data Capture) file using FFST (First Failure Support Technology) in /var/mqm/errors and it is important to view this FDC file to find out more information on the abnormal situation. For more information on FDC files, see: http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg21176953 MustGather: Documentation required by the WebSphere MQ support team for an ABEND or FFST http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg21173468 MustGather: WebSphere MQ Dumps and FFSTs are written to the following locations http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/topic/com.ibm.mq.amqzag.doc/fa15410_.htm WebSphere MQ 6 Information Center System Administration Guide First-failure support technology (FFST) ------- Note: ------- thread: Q: [MQ Series Error Code : 2059 AIX] Asked by abrobit.roy on 1/8/2007 6:04 AM Hi All, I am getting the shared memory issues on AIX Box. We come across the below errors :: Unable to connect to MQSeries Queue Manager 'QM_sdcb80a023' MQSeries Error Code: 2059 Please check your MQSeries configuration and verify that the queue manager is running. (SBL-EAI-04233) We have tried the below workaround mentioned in the supportweb. 1. Shut down the queue manager(s) ./endmqm QM_sdcb80a023 2. Edit the file /var/mqm/mqs.ini. In the `QueueManager' stanza, for ea ch queue manager of interest, add an additional line for IPCCBaseAddress explicitly specifying the shared memory segment to use. For example: QueueManager: Name=myQueueManager Prefix=/var/mqm Directory=myQueueManager IPCCBaseAddress&H12 (We have tried with all the relevant shared memory segment) 3. Restart the queue manager(s). 4. To configure the AIX environment to run Siebel Server with less memory setenv LDR_CNTRL MAXDATA=0x30000000 5. Restart Siebel Server The error is still reproducible. Could anyone assist me to resolve the issue. Note :: QM is Running and we are able to get/put the messages. Regards, A: ------- Note: ------- Article: HPUX HP-UX Kernel parameters HP-UX for MQ: Kernel configuration WebSpherer MQ uses semaphores and shared memory. It is possible, therefore, that the default kernel configuration is not adequate. Before installation, review the machine's configuration and increase the values if necessary. The minimum recommended values of the tunable kernel parameters are given in Figure 1. These values might need to be increased if you obtain any First Failure Support TechnologyT (FFSTT) records. Note: On platforms earlier than HP-UX 11i v1.6 (11.22), if you intended to run a high number of concurrent connections to WebSphere MQ, you were required to configure the number of kernel timers (CALLOUTS) by altering the NCALLOUT kernel parameter. On HP-UX 11i v1.6 (11.22) platforms or later, the NCALLOUT parameter is obsolete as the kernel automatically adjusts the data structures. Semaphore and swap usage does not vary significantly with message rate or message persistence. WebSphere MQ queue managers are generally independent of each other. Therefore system tunable kernel parameters, for example shmmni, semmni, semmns, and semmnu need to allow for the number of queue managers in the system. See the HP-UX documentation for information about changing these values. Figure 1. Minimum recommended tunable kernel parameters values shmmax 536870912 shmseg 1024 shmmni 1024 semaem 16384 semvmx 32767 semmns 16384 semmni 1024 (semmni < semmns) semmnu 16384 semume 256 max_thread_proc 66 maxfiles 10000 maxfiles_lim 10000 nfile 10000 Note: For HP-UX 11.23 (11i V2) and later operating systems, the tunable kernel parameters: shmem, sema, semmap, and maxusers, are obsolete. This applies to the Itanium and PA-RISC platforms. You must restart the system once you have made any changes to the tunable kernel parameters. System resource limits You can set global limits for the size of process data segments and the size of process stack segments for the whole system by altering the tunable kernel parameters. The tunable kernel parameters are: Parameter What it controls Recommended minimum value maxdsiz Maximum size of the data segment for 32-bit processes 1073741824 maxdsiz_64bit Maximum size of the data segment for 64-bit processes 1073741824 maxssiz Maximum size of the stack segment for 32-bit processes 8388608 maxssiz_64bit Maximum size of the stack segment for 64-bit processes 8388608 If other software on the same machine recommends higher values, then the operation of WebSphere MQ will not be adversely affected if those higher values are used. For the full documentation for these parameters see the HP-UX product documentation. To apply the settings to an HP-UX 11i system which has the System Administration Manager (SAM) utility, you can use SAM to achieve the following steps: Select and alter the parameters Process the new kernel Apply the changes and restart the system It is possible that other releases of HP-UX provide different facilities to set the tunable kernel parameters. If so, then please consult your HP-UX product documentation for the relevant information. The ulimit shell command On a per-shell basis the available limits can be tuned down from the values stored for the System resource limits parameters above. Use the ulimit shell command to tune the values of the parameters with a combination of the following switches: Switch Meaning -H The hard limit -S The soft limit -d The data segments size -s The stack segment size Verifying that the kernel settings are applied To verify that the resource limits have not been lowered by a ulimit command and that the queue manager will experience the correct limits, go to the shell from which the queue manager will be started and enter: ulimit -Ha ulimit -SaAmongst the console output you should see: data(kbytes) 1048576 stack(kbytes) 8192If lower numbers are returned, then a ulimit command has been issued in the current shell to lower the limits. You should consult with your system administrator to resolve the issue. ------- Note: ------- Article: Kernel parameters Solaris and MQ (1): Resource limit configuration Configure Solaris systems with the resource limits required by WebSpherer MQ. WebSphere MQ uses semaphores, shared memory, and file descriptors, and it is probable that the default resource limits are not adequate. The configuration required by WebSphere MQ depends on the version of Solaris you are using. >> If you are using Solaris 10: You must change the default resource limits for each zone WebSphere MQ will be installed in. To set new default limits for all users in the mqm group, set up a project for the mqm group in each zone. To find out if you already have a project for the mqm group, log in as root and enter the following command: projects -lIf you do not already have a group.mqm project defined, enter the following command: projadd -c "WebSphere MQ default settings" -K "process.max-file-descriptor=(basic,10000,deny)" -K "project.max-shm-memory=(priv,4GB,deny)" -K "project.max-shm-ids=(priv,1024,deny)" -K "project.max-sem-ids=(priv,1024,deny)" group.mqm If a project called group.mqm is listed, review the attributes for that project. The attributes must include the following minimum values: process.max-file-descriptor=(basic,10000,deny) project.max-sem-ids=(priv,1024,deny) project.max-shm-ids=(priv,1024,deny)" project.max-shm-memory=(priv,4294967296,deny) If you need to change any of these values, enter the following command: projmod -s -K "process.max-file-descriptor=(basic,10000,deny)" -K "project.max-shm-memory=(priv,4GB,deny)" -K "project.max-shm-ids=(priv,1024,deny)" -K "project.max-sem-ids=(priv,1024,deny)" group.mqm Note that you can omit any attributes from this command that are already correct. For example, to change only the number of file descriptors, enter the following command: projmod -s -K "process.max-file-descriptor=(basic,10000,deny)" group.mqm (To set only the limits for starting the queue manager under the mqm user, login as mqm and enter the command projects. The first listed project is likely to be default, and so you can use default instead of group.mqm, with the projmod command.) You can find out what the file descriptor limits for the current project are, by compiling and running the following program: #include #include #include #include int main () { int fd; for (;;) { fd = open ("./tryfd", O_RDONLY); printf ("fd is %d\n", fd); if (fd == -1) break; } } To ensure that the attributes for the project group.mqm are used by a user session when running Websphere MQ, make sure that the primary group of that user ID is mqm. In the above examples, the group.mqm project ID will be used. For further information on how projects are associated with user sessions, see Sun's System Administration Guide: Solaris Containers-Resource Management and Solaris Zones for your release of Solaris. >>> If you are using Solaris 8 or Solaris 9: Review the system's current resource limit configuration. As the root user, load the relevant kernel modules into the running system by typing the following commands: modload -p sys/msgsys modload -p sys/shmsys modload -p sys/semsysThen display your current settings by typing the following command: sysdef Check that the following parameters are set to the minimum values required by WebSphere MQ, or higher. The minimum values required by WebSphere MQ are documented in the tables below. Table 1. Minimum values for semaphores required by WebSphere MQ Parameter Minimum value SEMMNI 1024 SEMAEM 16384 SEMVMX 32767 SEMMNS 16384 SEMMSL 100 SEMOPM 100 SEMMNU 16384 SEMUME 256 Table 2. Minimum values for shared memory required by WebSphere MQ Parameter Minimum value SHMMAX 4294967295 SHMMNI 1024 SHMSEG (Solaris 8 only) 1024 Table 3. Minimum values for file descriptors required by WebSphere MQ Parameter Minimum value rlim_fd_cur 10000 rlim_fd_max 10000 To change any parameters that are lower than the minimum value required by WebSphere MQ, edit your /etc/system file to include the relevant lines from the following list: set shmsys:shminfo_shmmax=4294967295 set shmsys:shminfo_shmmni=1024 set semsys:seminfo_semmni=1024 set semsys:seminfo_semaem=16384 set semsys:seminfo_semvmx=32767 set semsys:seminfo_semmns=16384 set semsys:seminfo_semmsl=100 set semsys:seminfo_semopm=100 set semsys:seminfo_semmnu=16384 set semsys:seminfo_semume=256 set shmsys:shminfo_shmseg=1024 set rlim_fd_cur=10000 set rlim_fd_max=10000Note: These values are suitable for running WebSphere MQ, other products on the system might require higher values. Do not change the value of shmmin from the system default value. Semaphore and swap usage does not vary significantly with message rate or persistence. WebSphere MQ queue managers are generally independent of each other. Therefore system kernel parameters, for example shmmni, semmni, semmns, and semmnu need to allow for the number of queue managers in the system. After saving the /etc/system file, you must reboot your system ------- Note: ------- Article: Kernel parameters Solaris and MQ (2): A lot of people in the past have run into this problem, namely, the kernel configuration on solaris is not sufficient to run MQSeries. Add the following values to the /etc/system file and be sure to reboot. Make sure you do all of this before creating a queue manager on the box. /etc/system set shmsys:shminfo_shmmax = 4294967295 set shmsys:shminfo_shmseg = 1024 set shmsys:shminfo_shmmni = 1024 set semsys:seminfo_semaem = 16384 set shmsys:shminfo_semmni = 1024 set semsys:seminfo_semmap = 1026 set semsys:seminfo_semmns = 16384 set semsys:seminfo_semmsl = 100 set semsys:seminfo_semopm = 100 set semsys:seminfo_semmnu = 2048 set semsys:seminfo_semume = 256 set msgsys:msginfo_msgmap = 1026 set msgsys:msginfo_msgmax = 4096 _________________ The recommendation on /etc/system is in the Quick Start guide, but is critical, and worth reiterating. However, the values given are suitable for one queue manager which is not too busy. In environments with multiple queue managers, or where queue managers are busy, you may need to increase these values. IBM has not been able to provide good guidelines (to my knowledge) on how to tune these values. The manual also completely leaves out any mention of two importamt parameters. set rlim_fd_max = 1024 set rlim_fd_cur = 1024 Prior to solaris 2.7, the maximum values for these was 1024. It is now maxint at 2.7 and above. IBM has records on IBMLink referencing these parameters as fixes to various reported problems, but they don't seem to have made it into the manuals yet. The other thing to note is that the values listed allow for MQSeries usage of shared memory and semaphores, but if you have other users of these resources (such as BMC Patrol) then these values may not be sufficient. thanks for the additional info. The point you made about other services using these same resources is important, because some products, require even more of these resources than MQSeries. For instance, on one sun ultra we had, we were running MQSeries without a problem (after updating /etc/system according to the quick beginnings guide) and then installed Oracle and everything broke. Turns out that Oracle needs even more of certain resources than MQSeries, so we had to go back and increase values in /etc/system beyond what we required for MQSeries... This might help - it's from IBM: Solaris Kernel Parameters for MQ MQSeries makes extensive use of IPC (Inter-Process Communication) resources, including shared memory, semaphores, and message queues (the IPC kind). Many Solaris systems will require some adjustment of the kernel parameters which govern these resources in order to able to run MQSeries comfortably, or to support heavily-used MQSeries installations. Indications that MQSeries lacks enough IPC resources may be an inability to start MQSeries, or difficulty in running many MQSeries programs concurrently. Furthermore, MQSeries may generate FDC files in /var/mqm/errors which contain error messages from IPC-related functions like semget, shmget, or shmat. In order to make more IPC resources available to MQSeries, it is necessary to modify the kernel parameters on your machine using facilities like configure and idtune. Use the values given in this note in preference over those listed in the MQSeries Quick Beginnings for Solaris book. In cases where this note mentions new parameters, or overlooks some listed in the Quick Beginnings book, again give preference to this note. For more information on modifying your kernel, refer to your Solaris documentation or contact Solaris support. We strongly urge you to save your current kernel configuration before trying to make any changes. When you make changes, realize that other programs (databases, for example) which make much use of IPC resources may force you to modify these parameters so that both MQSeries and those programs will run. The values msgmax, msgmnb, msgssz, semaem, semume, semvmx, shmmax, and shmseg should not in general require augmentation if you are running databases or other IPC-intensive programs. The values msgmap, msgmni, msgseg, msgtql, semmap, semmni, semmns, semmnu, and shmmni may require augmentation depending on the other programs running on the system. Refer to the meaning of each parameter listed below and other vendors' instructions to help you with that determination. In general, the values that follow are only policing values. In other words, they can usually be over-allocated without causing harm to your system. This means that if your existing programs are not already running up against the limits you have specified, they will not use more kernel resources after modifying your kernel parameters. Note: The parameters for Shared Memory and Semaphores tend to be more important than the parameters for Message Queues. Note: The correct way of getting kernel parameters on a Solaris box is with the following command... /usr/sbin/sysdef -i > kernel.txt Please do not ask for the /etc/system file from customers to get kernel parameters. This file is used to set/tune kernel parameters and the parameters in this file will not be picked up until the box is rebooted. So getting the /etc/system file from the customer box might not give you the correct information as to what kernel parameters the operating system is actually running with. These are the recommended MINIMUM parameters... ________________________________________________________ IPC Message Queue Parameters _____________________________________________ mesg 1 This should not be changed, and is generally hard-coded. msgmap 1026 This is the number of entries in the kernel's message map table. This value should equal msgtql+2, and is should always be less than msgseg. A value roughly half of msgseg should be good. msgmax 4096 This is the maximum size of a single message in bytes. msgmnb 4096 This is the maximum number of bytes that all the messages on a single message queue can occupy. msgmni 50 This is the maximum number of message queues allowed on the system at any time. msgseg 2048 This is the number of memory segments allocated by the kernel at system startup to hold messages. Each system will have a limit on the total memory allocated (msgseg*msgssz), often 128KB. msgssz 8 This is the size in bytes of the memory segments used for storing messages. Valid values must be multiples of 4. msgtql 1024 This is the number of system messages headers which the kernel can store, which is effectively the maximum number of unread messages at any time. _____________________________________________ IPC Semaphore Parameters _____________________________________________ sema 1 This should not be changed, and is generally hard-coded. semaem 16384 This is the maximum adjust-on-exit value for a semaphore. It must be less than or equal to semvmx. semmap 1026 This is the size of the kernel's map of semaphore sets. This value should equal but never exceed semmni+2. semmni 1024 This is the maximum number of semaphore sets that can exist on the system at any time. HP-UX hard-codes the number of semaphores per set (semmsl on Solaris systems) to 500, so if only "full" semaphore sets are going to be allocated, this value should be roughly semmns/500. MQSeries generally allocates 64 semaphores per set, so if most of the semaphore usage on the system is due to MQSeries, a more ideal number would be semmns/64. semmns 32767 This is the maximum number of semaphores in the system. A value of 16384 will generally work for a small MQSeries installation, but setting it to 32767 is advisable for larger systems. semmnu 2048 This is the number of semaphore undo structures allocated by the system. It must be less than or equal to nproc-4. semmsl 128 This is the maximum number of semaphores per semaphore set semopm 128 This is the maximum number of semaphore operations that can be done by one semop() call. If this is set to semmsl, one semop() call can operate on every semaphore in a semaphore set, although MQSeries does not require this. semume 256 This is the number of semaphore undo entries for each process. semvmx 32767 This is the maximum value that a semaphore can have. _____________________________________________ IPC Shared Memory Parameters _____________________________________________ shmem 1 This should not be changed, and is generally hard-coded. shmmax 4194304 This is the maximum size in bytes of a shared memory segment. shmmni 1024 This is the maximum number of shared memory segments that can exist on the system at any time. 1024 is the maximum on many systems. shmseg 1024 This is the maximum number of shared memory segments that a single process can have at any time. It should always be less than or equal to shmmni. _____________________________________________ Miscellaneous Parameters ____________________________________________ maxusers 32 This controls the number of users which can log in to the system. More importantly, it controls other system values which limit the number of processes that can run at once. ... Rather than changing maxusers, we would recommend that you alter the nproc and maxuprc values as follows: nproc: The maximum number of processes on the system. 1 for each non-MQSeries process on the system PLUS 3 for each MQSeries queue manager (strmqm) PLUS 2 for each MQSeries receiver or svrconn channel PLUS 1 for each MQSeries sender channel PLUS 1 for each other MQSeries process (runmqtrm, etc.) maxuprc: The maximum number of processes for a single user. 1 for each non-MQSeries process run by 'mqm' PLUS 3 for each MQSeries queue manager (strmqm) PLUS 2 for each MQSeries receiver or svrconn channel PLUS 1 for each MQSeries sender channel PLUS 1 for each other MQSeries process (runmqtrm, etc.) Users of Sun Solaris 2.5.1 or better may wish to verify that they are not in fact using more than 25% of their kernel resources for semaphore structures. In order to calculate this in bytes, use the formula given below. Also, if you are letting the kernel determine nproc for you, you can find this value by typing 'sysdef | grep v_proc': kernel_memory = semmns * 16 + nproc * 16 + semmni * 92 + semmnu * ((semume + 1) * 16) * 4 Solaris 2.5.1 users must also be certain that they are not using more than 25% of their kernel resources for shared memory structures. In order to calculate this in bytes, use the formula given below: kernel_memory = shmmni * 120 Of course, simply calculating the bytes needed for shared memory and semaphore structures is not terribly useful if you don't know what the overall kernel resources are. Kernel memory is limited by your kernel architecture as well as by your available RAM. Type 'uname -m' to see what your kernel architecture is. The maximum kernel memory that common Sun architectures can use today is given below: Kernel Resources Machines Sun4m 256 MB ------ Sun4d 576 MB SS1000, SC2000 Sun4u 4 GB UltraSPARC Just a minor thing - BMC Patrol does not use IPCS stuff DIRECTLY - it consumes IPC resources via. the MMA clients it uses to communicate with MQ. Please find the following link for docs on "Solaris Tunable Parameters Ref." Man." http://docs.sun.com/ab2/coll.707.1/SOLTUNEPARAMREF/@Ab2TocView?Ab2Lang=C&Ab2Enc=iso-8859-1 excuse my ignorance, but I presume the recommended kernel settings are only for MQSeries Server, and not applicable to Client only installation? Excuse my ignorance as well but I'd love to have "andystone"'s previous point clarified if possible. It's not stated clearly in any of the IBM documentation whether it's necessary to alter kernel parameters when performing a Client-only installation on Solaris ... in fact the documentation gives the impression that these kernel changes are associated with the Server installation only. However when installing the Client product on Sloaris I received the following : =============================================== Checking kernel configuration... 33554432 max shared memory segment size (SHMMAX) 24 max attached shm segments per process (SHMSEG) 100 shared memory identifiers (SHMMNI) 300 semaphore identifiers (SEMMNI) 300 semaphores in system (SEMMNS) 25 max semaphores per id (SEMMSL) 10 max operations per semop call (SEMOPM) 600 undo structures in system (SEMMNU) 10 max undo entries per process (SEMUME) 2048 max message size (MSGMAX) ADVISORY WARNING - You may need to alter the kernel parameters listed above to run WebSphere MQ. See the Quick Beginnings manual for more information. =============================================== Does anyone have a definite yes or no response to this query? In addition, this is my first posting. I'd like to say that I've found this site to be of invaluable assistance over the past 3 months as I've begun to explore the world of MQ. I could n't see these values in my sysdef file. Where I could find these values?. set rlim_fd_max = 1024 set rlim_fd_cur = 1024 Sysdef is the utility to display the system settings. You should put the rlim_fd parameters in the file /etc/system . For some reason sysdef doesn't display these params, but if use ulimit -a you should see: nofiles(descriptors) 1024 Just an update regarding my previously posted question. The answer is, that you must change the kernel parameters only if you install a MQ Server. If you install a MQ Client you can ignore the message that you should change the kernel configuration. Many thanks to Carsten Scheunemann for emailing me this information which he received from IBM support. For some recent information on MQ Solaris kernel changes, in particular msgmap, msgseg, msgssz and msgtql see: http://www-1.ibm.com/support/docview.wss?rs=172&context=SW900&q1=msgseg&uid=swg21116351&loc=en_US&cs=utf-8&lang=en - you said about 'Solaris Kernel Parameters for MQ ': "it's from IBM: " - is it an official answer from IBM support or some information documented somewhere? thanks in advance ------- Note: ------- Article: Kernel parameters Linux and MQ: Kernel configuration WebSpherer MQ makes use of System V IPC resources, in particular shared memory and semaphores. The default configuration of these resources, supplied with your installation, is probably adequate for WebSphere MQ but if you have a large number of queues or connected applications, you might need to increase this configuration. You can determine the amount of System V IPC resources available by looking at the contents of the following files: /proc/sys/kernel/shmmax - The maximum size of a shared memory segment. /proc/sys/kernel/shmmni - The maximum number of shared memory segments. /proc/sys/kernel/shmall - The maximum amount of shared memory that can be allocated. /proc/sys/kernel/sem - The maximum number and size of semaphore sets that can be allocated. For example, to view the maximum size of a shared memory segment that can be created enter: cat /proc/sys/kernel/shmmax To change the maximum size of a shared memory segment to 256 MB enter: echo 268435456 > /proc/sys/kernel/shmmax To view the maximum number of semaphores and semaphore sets which can be created enter: cat /proc/sys/kernel/sem This returns 4 numbers indicating: SEMMSL - The maximum number of semaphores in a sempahore set SEMMNS - The maximum number of sempahores in the system SEMOPM - The maximum number of operations in a single semop call SEMMNI - The maximum number of sempahore sets For WebSphere MQ: the SEMMSL value must be 128 or greater the SEMOPM value must be 5 or greater the SEMMNS value must be 16384 or greater the SEMMNI value must be 1024 or greater To increase the maximum number of semaphores available to WebSphere MQ, you should update the SEMMNS and SEMMNI values. To configure these values every time the machine is restarted you are recommended to add these commands to a startup script in /etc/rc.d/... ------- Note: ------- Article: AIX requirements and MQ: Checking the operating environment Before you install WebSpherer MQ Version 6.0, you must check that your system meets the hardware and operating system software requirements set for this product and the particular components you intend to install on it. Note: WebSphere MQ does not support host names that contain spaces. If you install WebSphere MQ on a computer with a host name that contains spaces, you will be unable to create any queue managers. Hardware WebSphere MQ for AIXr, Version 6.0 runs on any machine that supports the AIX5L V5.2 or AIX5L V5.3 operating systems capable of running 64-bit programs whether from IBMr or other vendors. Operating System The operating systems supported by WebSphere MQ for AIX, Version 6.0 are: AIX5L V5.2 (plus maintenance Level 3) AIX5L V5.3 Use the oslevel -r command to determine the level of the operating system you are running, including the maintenance level. Connectivity Requirements Check that the system has 64-bit compatible communications hardware that supports at least one of the following: TCP/IP SNA LU6.2: If you want to use the SNA LU6.2 support on WebSphere MQ you need the IBM Communications Server for AIX Version 6.1. UDP is no longer supported, existing channels should either be deleted or migrated to one of the supported protocols listed above. To migrate UDP channels to an alternative protocol alter the channel TRPTYPE attribute. For information about this channel attribute see the Intercommunication book. Storage Requirements The storage requirements for the WebSphere MQ for AIX, Version 6.0 depend on which components you install, and how much working space you need. This, in turn, depends on the number of queues that you use, the number and size of the messages on the queues, and whether the messages are persistent. You also require archiving capacity on disk, tape or other media. The approximate amount of storage space required for a server installation is detailed in the table below. Table 1. Storage requirements for a WebSphere MQ server Storage Requirements Storage Requirement in MB in /opt WebSphere MQ Server installation 325 You can use the df command to determine the amount of free space on your system. Disk storage is also required for Prerequisite software Optional software Your application programs File descriptors When running a multi-threaded process such as the agent process, you might reach the soft limit for file descriptors. This gives you the WebSphere MQ reason code MQRC_UNEXPECTED_ERROR (2195) and, if there are enough file descriptors, a WebSphere MQ FFSTT file. To avoid this problem, you can increase the process limit for the number of file descriptors. To do this, alter the nofiles attribute in /etc/security/limits to 10,000 for the mqm user id or in the default stanza. For information about the mqm user id see, Setting up the user ID and group ID. System Resource Limits Set the system resource limit for data segment and stack segment to unlimited using the following commands in a command prompt: ulimit -d unlimited ulimit -s unlimited ------- Note: ------- article: IY92929: Logger process amqhasmx (amqzmuc0 in V6) could eventually run out of file descriptors some time after a disk full condition Fixes are available WebSphere MQ V5.3 and WebSphere MQ Express V5.3 - Fix Pack 14 (CSD14) WebSphere MQ V5.3 for iSeries - Fix Pack 14 (CSD14) WebSphere MQ V6.0 Fix Pack 6.0.2.2 WebSphere MQ V6.0 for iSeries Fix Pack 6.0.2.2 WebSphere MQ 5.3 for HP OpenVMS Alpha and Itanium - Fix Pack 14 APAR status Closed as program error. Error description If the disk holding the log files for a queue manager becomes full, then the log formatting process amqharmx (amqzmuc0 in V6) may (correctly) report probe HL062054, HL049110 and HL062054 FDCs (erorr code hrcE_MQLO_DISK), with FDCs also from the logger process amqhasmx (amqzmuc0 in V6). This condition may introduce a permanent state within the logger whereby log files need to be renamed. Each rename leaks a file descriptor, leading to eventual file descriptor exhaustion within the logger, which will get reported via a large variety of FDCs, depending on where it is encountered. Note that log files do not normally need to be renamed. A workaround is to ensure that the queue manager is recycled if the log formatter ever reports disk full (hrcE_MQLO_DISK) FDCs. Local fix Recycled asap if the logger ever reports lack of disk space (the hrcE_MQLO_DISK error code). Problem summary **************************************************************** USERS AFFECTED: Users running out of disk space during log formatting leading to hrcE_MQLO_DISK FDCs from the amqharmx (amqzmuc0 in V6) process. But only if the queue manager is not recycled after such an event. Platforms affected: All Unix **************************************************************** PROBLEM SUMMARY: File descriptor leak in the little-used log file renaming function. Problem conclusion Ensured that the log file renaming function does not leak any file descriptors. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: v5.3 Platform Fix Pack 14 -------- -------------------- AIX U808477 HP-UX (PA-RISC) U808478 Solaris (SPARC) U808480 Linux (x86) U808481 Linux (zSeries) U808483 v6.0 Platform Fix Pack 6.0.2.2 -------- -------------------- AIX U809895 HP-UX (PA-RISC) U809898 HP-UX (Itanium) U810084 Solaris (SPARC) U809913 Solaris (x86-64) U810362 Linux (x86) U809950 Linux (x86-64) U810178 Linux (zSeries) U810081 Linux (Power) U810083 Linux (s390x) U810110 The latest available maintenance can be obtained from 'WebSphere MQ Recommended Fixes' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037 If the maintenance level is not yet available, information on its planned availability can be found in 'WebSphere MQ Planned Maintenance Release Dates' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309 --------------------------------------------------------------- Temporary fix Comments APAR information APAR number IY92929 Reported component name WEBS MQ FOR SUN Reported component ID 5724B4103 Reported release 530 Status CLOSED PER PE NoPE HIPER NoHIPER Special Attention NoSpecatt Submitted date 2006-12-18 Closed date 2007-01-03 Last modified date 2007-07-27 APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros Publications Referenced Fix information Fixed component name WEBS MQ FOR SUN Fixed component ID 5724B4103 Applicable component levels R530 PSY UP ------- Note: ------- article: IC56662: HANG IN AMQZMUC0 PROCESS FOLLOWING THE 'DISK NOT READY' ERROR A fix is available WebSphere MQ V6.0 Fix Pack 6.0.2.5 APAR status Closed as program error. Error description: When customer attempts to initiate a failover from node1 to node2 in an MSCS environment by failing the shared disk resource, the resource manager issues an 'endmqm' to terminate the queue manager resource. As part of queue manager termination the utility manager process amqzmuc0 attempts to write the buffered log records to the disk. However, this fails with DISK_NOT_READY error as the disk is unavailable for performing the write operation. Following this the amqzmuc0 process goes in a loop for a while consuming significant amount of CPU until it is terminated by the queue manager. The FDC with probe HL166091 is cut by the component WriteLogPages2 when the buffer write fails with hrcE_MQLO_DNRD error. Local fix Problem summary **************************************************************** USERS AFFECTED: WMQ users who has a potentially failing or offline disk during a write operation. Platforms affected: All Distributed (iSeries, all Unix and Windows) **************************************************************** PROBLEM SUMMARY: When the amqzmuc0 process encounters the error hrcE_MQLO_DNRD while attempting to write data to the log file, it runs in to a infinite loop in the function mqlpgasn causing the delay in the termination of the queue manager. Problem conclusion The code is altered to handle this error condition. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: v6.0 Platform Fix Pack 6.0.2.5 -------- -------------------- Windows U200292 AIX U815929 HP-UX (PA-RISC) U815636 HP-UX (Itanium) U815818 Solaris (SPARC) U815659 Solaris (x86-64) U815928 iSeries tbc Linux (x86) U815767 Linux (x86-64) U815808 Linux (zSeries) U815805 Linux (Power) U815806 Linux (s390x) U815807 The latest available maintenance can be obtained from 'Websphere MQ Recommended Fixes' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037 If the maintenance level is not yet available, information on its planned availability can be found in 'Websphere MQ Planned Maintenance Release Dates' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309 --------------------------------------------------------------- Temporary fix Comments APAR information APAR number IC56662 Reported component name WMQ WINDOWS V6 Reported component ID 5724H7200 Reported release 602 Status CLOSED PER PE NoPE HIPER NoHIPER Special Attention NoSpecatt Submitted date 2008-05-27 Closed date 2008-06-16 Last modified date 2008-06-16 ------- Note: ------- thread: Q: Hi, I've got a problem with WebSphere MQ Demo 6.0.1.0 on a Windows 2003 Server running in a Virtual PC. Allmost at all times amqzlaa0 is consuming all the CPU cycles. With sysinternals process explorer we traced it down to a thread which is calling from AMQXCS2.dll!xcsSynchronizeCounterTime+0xf2 into Windows kernel. Somtimes it is amqzmuc0 which calls xcsSynchronizeCounterTime as well. I found some hints that this routine has to do with logging/tracing. So: Does anyone know of a patch or how to disable logging so that routine doesn't get called? Thanks, A: Trace is disabled by running: endmqtrc You should also try making sure that event monitoring is not configured on your queue manager -- run DIS QMGR in runmqsc and check that everything that ends EV is (DISABLED). Also make sure you aren't using the Windows Performance Monitor to monitor your queues, as that implicitly enables some of the logging functionality. The underlying problem is probably that your emulator isn't emulating the function that the Windows QueryPerformanceCounter() and/or GetSystemTimeAsFileTime() APIs require, or at least is not emulating the hardware correctly and efficiently. Regards, ------- Note: ------- article: Recently I have been trying to determine what the impact of using MQ message persistence is on disk subsystem performance. There is alot of literature from IBM recommending ideal configurations to support MQ persistence, so I won't turn this into a post that recommends ideal settings. What I did want to achieve though, was to get a better understanding of how MQ interacts with the disk subsystem when using message persistence, so that I could plan for capacity and make better recommendations for tuning on a production SAN environment. The first behaviour I wanted to describe, was whether the use of MQ persistence creates random or sequential disk activity, on the assumption that random disk access to block locations on the disk would incur a greater time penalty than sequential access. In order to setup a test environment, I installed MQ version 6 on winXP platform using the default settings. This test was setup using a custom java load harness to put/get messages from a default queue which had persistence enabled with DEFPSIST(YES). File and disk statistics were collected on a Win32 platform using filemon and diskmon respectively. The following graphs depict the block size written over time (x axis) relative to the sector position (y axis) of the disk drive being monitored. I was trying to achieve a similar effect to the Solaris internals TAZ disk trace utility, albeit in a Windows environment. File stats such as number and size of write operations were collected using filemon. Transaction throughput was measured by dividing the total amount of transactions (1,000) by the total processing time. A number of different configurations were tested, but I chose to present a common setup which uses circular logging with single write, and a file page size of 16,384 x 4KB = 64MB per primary log file. The two variations I have presented are writes (MQPUT) only as well as writes (MQPUT) and reads (MQGET) concurrently. The latter being a more familiar situation for me in the workplace. It can be determined from the previous test results that MQ accesses the disk in a sequential behaviour. On windows, depending on the concurrent load, it will tend to allocate 16 - 32 x 512B blocks ranging from 8 - 16KB in size, although smaller less frequent writes will favour smaller 8 x 512B blocks 4KB in size. As a result, a high number of disk write IOs are observed. The environment used to test was virtual (parallels), so limited disk cacacity was available, however the change in amplitude for trans/sec is considered relative. As a result, over an 80% reduction in throughput was observed when reading (MQGET) and writing (MQPUT) to the same queue. This will have significant impact on disk subsystem performance in a production environment. I was unable to perform this test on a Solaris environment due to lack of privileged access, so would be keen to see what the results are there. I believe Solaris uses the same 512B block size, so am expecting similar results. Although analysing an MQ server's impact on disk performance using sar, produces the following information: sar -d 1 10 | egrep 'md72' md72 60 0.7 1867 16749 0.0 0.4 md72 58 0.6 1955 17272 0.0 0.3 md72 52 0.6 1768 15619 0.0 0.3 md72 52 0.6 1764 15577 0.0 0.3 md72 54 0.6 1817 16045 0.0 0.3 md72 56 0.6 1861 16447 0.0 0.3 From that information I can then infer that the total reads + writes/sec (r+w/s) divided by the number of 512B blocks per second (blk/s) would give me an average size of around 8-9KB/sec being written to the filesystem, which correlates my assumptions on block/file sizes. Using sar and other tools like iostat though is thought to be fraught with danger, especially when monitoring a rather complex SAN subsystem; but without access to any other tools, I'm stuck with the basics. To date I've been relying on perceived throughput (Mr+Mw/s) reported by iostat -xM Worth noting, is that when MQ performs an MQGET on a persistent queue, it also causes a write IO to update the active log file, so the number of total write IOs effectively doubles. Out of all this I'm working on the following assumptions: 1. MQ uses sequential disk access for persistence logging. 2. The OS is typically allocating between 16 - 32 x 512B blocks ranging between 8 - 16KB in size. 3. MQGETs are a contributor to overall writes (I'm assuming o remove the transactions from the log files) 4. Transaction throughput is significantly reduced when an application is reading (MQGET) and writing (MQPUT) to the same queue. Attached below is a copy of the qm.ini I am working with, which is based on recommended performance tuning considerations from IBM #*******************************************************************# #* Module Name: qm.ini *# #*******************************************************************# #ExitPath: ExitsDefaultPath=/var/mqm/exits/ ExitsDefaultPath64=/var/mqm/exits64/ #Log: LogPrimaryFiles=15 LogSecondaryFiles=15 LogFilePages=16384 LogType=CIRCULAR LogBufferPages=512 LogPath=/var/mqm/log/QUEUEMANGERNAME/ LogWriteIntegrity=SingleWrite #Service: Name=AuthorizationService EntryPoints=13 #ServiceComponent: Service=AuthorizationService Name=MQSeries.UNIX.auth.service Module=/opt/mqm/lib64/amqzfu ComponentDataSize=0 #Channels: MaxChannels=400 MaxActiveChannels=400 #TCP: KeepAlive=Yes #TuningParameters: DefaultQBufferSize=1048576 DefaultPQBufferSize=1048576 LogFilePages is set to the maximum 16384 x 4KB making each S0000[n].log file about 64MB in size. You must set this parameter as part of your Queue Manager creation i.e. crtmqm -lf 16384 Hopefully that decreases the frequency MQ needs to loop around the ring of log files. LogPrimaryFiles and LogSecondary files are set to 15, and I haven't run out of space in my circular log files yet. It is worth reading up on the MQ system administration manual for this, in terms of planning how much space you need. As a planning figure I add the size of MQPUT messages with DEFPSIST + 750B overhead as IBM state, then multiply that amount by my expected throughput. Checkpoint behaviour as part of circular logging activity should hopefully release space as it checkpoints (once every 10,000 transactions I believe), so if you plan properly, you shouldn't hit the tail end of your ring too soon The DefaultQBufferSize is 64KB which I increased to 1MB (1048576). Apparently this increases the size of the buffer before writing to the file system, but I haven't seen the evidence of that with the tools I'm using to monitor disk writes. This area is a little cloudy for me. I have also modified the LogBufferPages to 512 x 4KB giving me a 2MB buffer for similar reasons. And finally, I've been using a combination of either MQ, a custom perl script, or EMC iorate to benchmark message persistence on different mounts/filesystems etc which has been useful. Especially when you don't have one or the other available, and you need to determine if the space you've been allocated is up to the task of supporting MQ persistence. In order to truss the process on a Solaris 9 environment, we first had to establish which pid was writing to the log mount. Our sysadmin was able to do this for me with the following: # fuser -cu /var/mqm/log /var/mqm/log: 27306c(root) 27197c(root) 19735o(sr123456) In this case the sr user was the account under which mqm was running, so we were then able to determine the corresponding process name: # top -s sr123456 2756 sr123456 11 59 0 0K 0K sleep 313:05 12.08% amqzlaa0_nd 20162 sr123456 10 59 0 0K 0K cpu45 406:47 9.49% amqrmppa 19735 sr123456 6 59 0 0K 0K sleep 718:45 3.47% amqzmuc0 19742 sr123456 14 59 0 0K 0K sleep 22:22 0.00% amqzlaa0_nd 19744 sr123456 1 59 0 0K 0K sleep 1:36 0.00% amqpcsea 19752 sr123456 3 59 0 0K 0K sleep 0:16 0.00% runmqlsr_nd 19734 sr123456 2 59 0 0K 0K sleep 0:10 0.00% amqzfuma 19733 sr123456 14 59 0 0K 0K sleep 0:06 0.00% amqzxma0_nd 19751 sr123456 1 59 0 0K 0K sleep 0:00 0.00% runmqtrm 19749 sr123456 1 59 0 0K 0K sleep 0:00 0.00% runmqtrm 19739 sr123456 4 59 0 0K 0K sleep 0:00 0.00% amqzmgr0 19746 sr123456 1 59 0 0K 0K sleep 0:00 0.00% runmqtrm 19747 sr123456 1 59 0 0K 0K sleep 0:00 0.00% runmqtrm 19737 sr123456 2 59 0 0K 0K sleep 0:00 0.00% amqrrmfa 19738 sr123456 2 59 0 0K 0K sleep 0:00 0.00% amqzdmaa So in this case, the process named amqzmuc0 was the process performing the logging. For reference, here is a list of processes and what they typically control for MQ: 1. RUNMQLSR - MQ TCP listener (multi-threaded) 2. AMQCLMAA - MQ TCP listener (single-threaded) 3. AMQRMPPA - Channel process pooling job 4. RUNMQCHI - MQ channel initiator 5. AMQCRSTA - MQ receiving MCA jobs 6. RUNMQCHL - MQ sending MCA jobs 7. AMQCRS6B - LU62 receiver channel 8. AMQPCSEA - MQ command server 9. RUNMQTRM - Application trigger monitor 10. RUNMQDLQ - Dead letter queue handler 11. AMQFCXBA - MQ Broker Worker Job 12. RUNMQBRK - MQ Broker Control Job 13. AMQZMUC0 - MQ Utility Manager 14. AMQZMUR0 - MQ Utility Manager 15. AMQZMGR0 - MQ Process Controller 16. AMQRRMFA - MQ cluster repository manager 17. AMQZDMAA - MQ deferred message manager 18. AMQALMPX - MQ Log Manager 19. AMQZFUMA - MQ Object Authority Manager 20. AMQZLAS0 - MQ Local Queue Manager agents 21. AMQZLAA0 - MQ Local Queue Manager agents 22. AMQZXMA0 - MQ Execution Controller With this info at hand we could then truss the process as per the following: # truss -D -p 19735 Which produces the following output: 12677624.0012 lseek(18, 2543616, SEEK_SET) = 2543616 12677624.0017 write(18, "0FEE0315\001\0\0\0D6A4 f".., 4096) = 4096 12677624.0018 lwp_cond_broadcast(0xFFFFFFFF7B46CAC0) = 0 12677624.0018 lwp_mutex_wakeup(0xFFFFFFFF7B46CAA8) = 0 12677624.0019 lseek(18, 2547712, SEEK_SET) = 2547712 12677624.0023 write(18, "0FEE02FD\001\0\0\0D6A4 f".., 4096) = 4096 12677624.0024 lwp_cond_broadcast(0xFFFFFFFF7B46C3D8) = 0 12677624.0024 lwp_mutex_wakeup(0xFFFFFFFF7B46C3C0) = 0 12677624.0024 lwp_cond_broadcast(0xFFFFFFFF7B46CCE0) = 0 12677624.0025 lwp_mutex_wakeup(0xFFFFFFFF7B46CCC8) = 0 12677624.0025 lwp_cond_broadcast(0xFFFFFFFF7B46BE88) = 0 12677624.0026 lwp_mutex_wakeup(0xFFFFFFFF7B46BE70) = 0 12677624.0026 lseek(18, 2551808, SEEK_SET) = 2551808 12677624.0030 write(18, "\tD10206\001\0\0\0D6A4 f".., 4096) = 4096 What we can see from this test case is that Solaris is writing 4KB sized blocks of data to the file system in support of MQ persistent logging. I would prefer a higher size (say 8 - 16KB) as the SAN under test would be more efficient and capable of higher throughput, but I guess that is a limitation of the size of messages I am writing (185B per message) and the way Solaris breaks up the IO. There is a comment from an IBM performance tuning guide for message persistence that states:It is unlikely that poor persistent message throughput will be attributed to the 2MB limit of the queue manager log. It is possible to fill and empty the log buffer several times each second and reach a CPU limit writing data into the log buffer, before a log disk bandwidth limit is reached. In this, they are referring to the LogBufferPages parameter which I have increased to its maximum configurable size of 512 x 4K pages = 2MB. At this point in time I am still working with the sysadmin in an effort to prove this statement provided by IBM. For the time being we are investigating the seemingly high number of s yscalls and context switching which is evident from vmstat: # vmstat 1 kthr memory page disk faults cpu r b w swap free re mf pi po fr de sr m0 m1 m3 m4 in sy cs us sy id 0 1 0 27901544 13821744 0 6 8 0 0 0 0 0 0 0 0 11369 173717 83335 16 24 60 0 1 0 27901544 13821688 0 0 8 0 0 0 0 0 0 0 0 11201 175563 84711 14 20 66 0 1 0 27901536 13821648 635 4573 0 0 0 0 0 0 0 0 0 11841 179265 84000 14 26 59 0 0 0 27900496 13821472 847 6045 8 8 8 0 0 0 0 0 0 13003 178012 82634 17 25 58 2 0 0 27901552 13821528 0 0 8 0 0 0 0 0 0 0 0 10994 174223 83744 15 20 64 0 1 0 27901544 13821480 0 0 0 0 0 0 0 0 0 0 0 11210 175509 83986 15 18 66 0 1 0 27901544 13821440 0 0 8 0 0 0 0 0 0 0 0 11178 174778 83952 17 19 63 Another aspect I am investigating is the use of threads my the amqzmuc0 process. It would seem that for a given load amqzmuc0 is spawns around XX threads for that process. Looking at the prstat for that process confirms the following: # prstat -mL -p 29314 PID USERNAME USR SYS TRP TFL DFL LCK SLP LAT VCX ICX SCL SIG PROCESS/LWPID 29314 sr53186 0.4 0.7 - - - - 3.2 - 564 157 1K 0 amqzmuc0/3 29314 sr53186 0.0 0.0 - - - - 0.4 - 1 0 1 0 amqzmuc0/4 29314 sr53186 0.0 0.0 - - - - 0.0 - 0 0 0 0 amqzmuc0/6 29314 sr53186 0.0 0.0 - - - - 0.0 - 0 0 0 0 amqzmuc0/5 29314 sr53186 0.0 0.0 - - - - 100 - 0 0 0 0 amqzmuc0/2 29314 sr53186 0.0 0.0 - - - - 0.0 - 0 0 0 0 amqzmuc0/1 ------- Note: ------- IY47735: QUEUE MANAGER HAD A SEGV IN AN AMQZLLP0 PROCESS Fixes are available WebSphere MQ V5.3 and WebSphere MQ Express V5.3 - Fix Pack 14 (CSD14) WebSphere MQ v5.3 and WebSphere MQ Express v5.3 - Fix Pack 6 (CSD06) WebSphere MQ V5.3 and WebSphere MQ Express V5.3 - Fix Pack 9 (CSD09) WebSphere MQ V5.3 and WebSphere MQ Express V5.3 - Fix Pack 12 (CSD12) WebSphere MQ v5.3 for iSeries - Fix Pack 10 (CSD10) WebSphere MQ V5.3 for iSeries - Fix Pack 12 (CSD12) WebSphere MQ V5.3 for iSeries - Fix Pack 11 (CSD11) WebSphere MQ V5.3 & WebSphere MQ Express V5.3 - Fix Pack 7 (CSD07) WebSphere MQ v5.3 for iSeries - Fix Pack 8 (CSD08) WebSphere MQ V5.3 and WebSphere MQ Express V5.3 - Fix Pack 11 (CSD11) WebSphere MQ V5.3 and WebSphere MQ Express V5.3 - Fix Pack 13 (CSD13) WebSphere MQ V5.3 & WebSphere MQ Express V5.3 - Fix Pack 10 (CSD10) WebSphere MQ v5.3 for iSeries - Fix Pack 6 (CSD06) WebSphere MQ V5.3 & WebSphere MQ Express V5.3 - Fix Pack 8 (CSD08) APAR status Closed as program error. Error description amqzllp0 received SIGSEGV caused by a queue having buffers with non-zero write counts on buffers that are NULL. Local fix Zero write counts at the time the buffers are freed. Problem summary amqzllp0 received SIGSEGV caused by a queue having buffers with non-zero write counts on buffers that are NULL. It's not clear what the full set of conditions are that are necessary for this problem to be encountered. It is certainly a rare problem, but potentially any MQ5.3 user is affected. The problem is caused by dirty write counts on queue buffers.This causes a subsequent checkpoint to fail with a SIGSEGV in MQ function aqhIdxToPtrFn called from aqpFlushCache whilst checkpointing. Problem conclusion The problem was fixed by ensuring that queue buffer write counts are zeroed at the time that the queue buffers are freed. It will be shiped into: WebSphere MQ V5.3 CSD06 . Windows U200202 AIX U489863 HP-UX U489864 Linux on Intel U489967 Linux on zSeries U489972 Sun Solaris U489865 Temporary fix Comments APAR information APAR number IY47735 Reported component name WEBS MQ FOR LIN Reported component ID 5724B4104 Reported release 530 Status CLOSED PER PE NoPE HIPER NoHIPER Special Attention NoSpecatt Submitted date 2003-08-20 Closed date 2003-08-26 Last modified date 2004-03-10 APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: ------- Note: ------- Queue Manager fails unexpectedly but is able to restart Technote (FAQ) Problem Queue manager fails with several FDCs containing probes: XC130004 AQ051000, AO084010, AL047011. These FDCs indicate that the queue manager failed while doing a checkpoint.. See details bellow. Cause The checkpoint processor (amqzllp0) received SIGSEGV caused by a queue having buffers with non-zero write counts on buffers that are NULL. It is not clear what conditions are necessary for this problem to be encountered. It is certainly a rare problem, but any MQ v5.3 user may be affected. Solution APAR IY47735 addresses this problem. Apply CSD06 or higher. Additional information Probe Id :- XC130004 Component :- xehExceptionHandler Program Name :- amqzllp0 Major Errorcode :- STOP Probe Type :- HALT6109 Arith1 :- 11 b MQM Function Stack zllpMain alsCheckPointLoop aocPerformCheckpoint aqmCheckPointQueue aqpCheckPointQ aqpFlushCache aqhIdxToPtrFn xcsFFST ***************************** Probe Id :- AQ051000 Component :- aqsStartQOp Program Name :- amqzllp0 Major Errorcode :- STOP_ALL Probe Type :- HALT6110 MQM Function Stack zllpMain alsCheckPointLoop aocPerformCheckpoint aqmCheckPointQueue xcsFFST **************************** Probe Id :- AO084010 Component :- aocPerformCheckpoint Program Name :- amqzllp0 MQM Function Stack zllpMain alsCheckPointLoop aocPerformCheckpoint xcsFFST *************************** Probe Id :- AL047011 Component :- alsCheckPointLoop Program Name :- amqzllp0 Major Errorcode :- STOP_ALL MQM Function Stack zllpMain alsCheckPointLoop xcsFFST We reviewed the FDCs closely and see the first FDC to be fired is the XC130004 FDC from the checkpoint process. This is a segmentation violation that has occurred in aqhIdxToPtrFn(). This function is called to dereference an index and return a pointer. The pointer seems to be corrupted resulting in this FDC. The other FDCs are the after effect of this FDC. In one case the qm error log showed - 08/15/03 03:30:16 AMQ7472: Object QS.CALC.REPLY.3F19889F21A08101, type queue damaged. 08/15/03 03:30:23 AMQ9542: Queue manager is ending. In another case there was no corrupt queue reported but the fdc's and the problem were the same. Related information APAR IY47735 Historical Number 22199 7td 000 Product Alias/Synonym MQ WMQ ------- Note: ------- SE16730: MQM400 QUEUE MANAGER AGENT JOB (AMQZLAA0) CONSUMES HIGH CPU IN RFIALLOCCACHE/RFXLINK WHEN MQOPEN FAILS CONTINUALLY Fixes are available WebSphere MQ 5.3 for HP OpenVMS Alpha and Itanium - Fix Pack 13 WebSphere MQ v5.3 for iSeries - Fix Pack 9 (CSD09) APAR status Closed as program error. Error description Using WebSphere MQ V5.3 with CSD 06 under OS/400 5.1, the job AMQZLAA0 has a very high CPU usage. Local fix Problem summary **************************************************************** USERS AFFECTED: All users of WebSphere MQ v5.3 Platforms affected: All Distributed **************************************************************** PROBLEM SUMMARY: API calls such as MQOPEN will search the cluster repository cache when the MQ object does not exist on the local Queue Manager. Each search will attempt to allocate, and subsequently free, a registration entry (of 320 bytes) in the cluster cache memory block. A problem with pointer/offset arithmetic made each freed entry appear to have size zero, causing each new allocate to request a new entry from the memory block. After a few hours, the number of freed entries had grown so large that rfiAllocateCache was consuming high CPU scanning the chain of freed cache entries. Problem conclusion The problem has been fixed; rfiAllocateCache will re-use a freed registration entry, instead of continually allocating new registration entries. Temporary fix TEST FIX Comments The problem has been fixed; rfiAllocateCache will re-use a freed registration entry, instead of continually allocating new registration entries. APAR information APAR number SE16730 Reported component name WEB MQ FOR ISER Reported component ID 5724B4106 Reported release 530 Status CLOSED PER PE NoPE HIPER NoHIPER Special Attention NoSpecatt Submitted date 2004-07-23 Closed date 2004-08-24 Last modified date 2007-05-14 APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros ROCSMGR Publications Referenced Fix information Fixed component name WEB MQ FOR ISER Fixed component ID 5724B4106 Applicable component levels R530 PSY SI16678 UP07/05/14 P 7121 ------- Note: ------- IC45414: AMQZLAA0 USES 100% CPU WHILE LOADING A QUEUE WITH PERSISTENT AND NON-PERSISTENT MESSAGES Fixes are available WebSphere MQ V5.3 and WebSphere MQ Express V5.3 - Fix Pack 14 (CSD14) WebSphere MQ V5.3 and WebSphere MQ Express V5.3 - Fix Pack 12 (CSD12) WebSphere MQ V5.3 for iSeries - Fix Pack 12 (CSD12) WebSphere MQ V5.3 for iSeries - Fix Pack 11 (CSD11) WebSphere MQ V5.3 and WebSphere MQ Express V5.3 - Fix Pack 11 (CSD11) WebSphere MQ V5.3 and WebSphere MQ Express V5.3 - Fix Pack 13 (CSD13) WebSphere MQ 5.3 for HP OpenVMS Alpha and Itanium - Fix Pack 12 APAR status Closed as program error. Error description Customer reporting 100% CPU usage each morning in amqzlaa0.exe. Slow queue loading - persistent and non-persistent messages. Applications hang while load completes. Local fix Speed up loading queue with mixture of persistent and non-persistent messages. Problem summary **************************************************************** USERS AFFECTED: All users of WebSphere MQ who mix persistent and non persistent messages on the same queue Platforms affected: All Distributed (iSeries, all Unix and Windows) **************************************************************** PROBLEM SUMMARY: When a queue is not used for a period of time, it may get unloaded. If it does, it will be reloaded on the next access, and the load will restore all the persistent messages first and then add in the non persistent messages. The algorithm for reloading the non-persistent messages was not optimal, and resulted in frequent walks through the complete message chain, which consumed disk i/o and CPU resource. Problem conclusion The algorithm for reloading a queue has been modified to optimize the reloading when the queue contains a mixture of persistent and non persistent messages. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: v5.3 Platform Fix Pack 11 -------- -------------------- Windows U200236 AIX U802047 HP-UX (PA-RISC) U802131 Solaris (SPARC) U802142 iSeries SI18375 Linux (x86) U802143 Linux (zSeries) U802146 Linux (Power) Not applicable The latest available maintenance can be obtained from 'WebSphere MQ Recommended Fixes' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037 If the maintenance level is not yet available, information on its planned availability can be found in 'WebSphere MQ Planned Maintenance Release Dates' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309 --------------------------------------------------------------- Temporary fix Comments APAR information APAR number IC45414 Reported component name WEB MQ FOR WINS Reported component ID 5724B4100 Reported release 530 Status CLOSED PER PE NoPE HIPER NoHIPER Special Attention NoSpecatt Submitted date 2005-03-16 Closed date 2005-03-24 Last modified date 2007-08-02 APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros Publications Referenced Fix information Applicable component levels R530 PSY UP ------- Note: ------- SE10932: MQM400 XY324192 GETSUBPOOLSLOCK IN JOB AMQZXMA0 XECF_E_UNEXPECTE APAR status Closed as program error. Error description ========================================= Date/Time :- Thursday May 22 08:23:00 2003 Host Name :- mvalxxxx.xxx.xxxxxxxxx.xxx.au PIDS :- 5724B4106 LVLS :- 530.3 CSD03 Product Long Name :- WebSphere MQ for iSeries Vendor :- IBM Probe Id :- XY043007 Application Name :- MQM Component :- xllSemGetVal Build Date :- Mar 19 2003 UserID :- 00001186 (QMQM) Job Name :- 086731/QMQM/AMQZXMA0 Job Description :- QMQM/AMQZXMA0 Submitted By :- 086730/MQADMIN/STRMQM_R Activation Group :- 99 (QMQM) (QMQM/AMQZXMA0) Process :- 00002416 Thread :- 00000003 QueueManager :- MQaaaannnnx Major Errorcode :- xecF_E_UNEXPECTED_SYSTEM_RC Minor Errorcode :- OK Probe Type :- MSGAMQ6119 Probe Severity :- 2 Probe Description :- AMQ6119: An internal WebSphere MQ error has occurred ('3021 - The value specified for the argument is not correc' from semctl.) MQM Function Stack xstSubpoolSubtask xcsWaitEventSem xcsRecoverSubpoolsLockForThread xllSemGetVal xcsFFST . ..simialr another FDC in the same file:- . ================================================================ in amqerr01.log see similar messages:- AMQ6184: An internal WebSphere MQ error has occurred.The failing process is process 2416. AMQ6119: An internal WebSphere MQ error has occurred ('3021 - The value specified for the argument is not correc' from semctl.) AMQ6184: An internal WebSphere MQ error has occurred. . ============================================================ May 2003 -Date/Time- --- Filename - -Probe- ---Tid-- --- Component 21 22:45:43 AMQ2416.0.FDC XY324192 00000001 GetSubpoolsLock 'AMQ6119: An internal WebSphere MQ error has occurred',''3021 - The value specified for the argument is not', '3021 bcd' 22 08:23:00 AMQ2416.0.FDC XY043007 00000003 xllSemGetVal 'AMQ6119: An internal WebSphere MQ error has occurred',''3021 - The value specified for the argument is not', '3021 bcd' 22 08:23:01 AMQ2416.0.FDC XY043007 00000001 xllSemGetVal 'AMQ6119: An internal WebSphere MQ error has occurred',''3021 - The value specified for the argument is not', '3021 bcd' :- this is defect 73655 Local fix Problem summary IPC semaphore set being blown away by either ipcrm or two asynchronous ENDMQM MQMNAME(*ALL) ENDCCTJOB(*YES) in two simultaneous sessions. Problem conclusion The failure to handle semaphore reporting EINVAL has been added. The handler will try access the semaphore again to recreate it. If still unsuccessful after 5 retry attempts then a new FDC with probe XY324195 will be logged. Temporary fix Comments APAR information APAR number SE10932 Reported component name WEB MQ FOR ISER Reported component ID 5724B4106 Reported release 530 Status CLOSED PER PE NoPE HIPER NoHIPER Special Attention NoSpecatt Submitted date 2003-07-03 Closed date 2003-09-24 Last modified date 2007-05-14 APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros Publications Referenced Fix information Fixed component name WEB MQ FOR ISER Fixed component ID 5724B4106 Applicable component levels R530 PSY SI10092 UP04/06/06 P 4083 ------- Note: ------- Abstract MQM400-MSGAMQ5615 STRMQM FAILS WITH AMQ5615 AFTER AMQZXMA0 Pre/Co-Requisite PTF / Fix List REQ LICENSED PTF/FIX LEVEL TYPE PROGRAM REL NUMBER MIN/MAX OPTION ---- -------- --- ------- ------- ------ PRE 5724B41 530 SI13613 NONE 0000 PRE 5724B41 530 SI13881 NONE 0000 CO 5724B41 530 SI13906 NONE 0000 CO 5724B41 530 SI13612 NONE 0000 DIST 5724B41 530 SI13926 NONE 0001 DIST 5724B41 530 SI11234 NONE 0001 DIST 5724B41 530 SI10120 NONE 0001 NOTICE: ------- Application of this PTF may disable or render ineffective programs that use system memory addresses not generated by the IBM translator, including programs that circumvent control technology designed to limit interactive capacity to purchased levels. This PTF may be a prerequisite for future PTFs. By applying this PTF you authorize and agree to the foregoing. APAR Error Description / Circumvention DESCRIPTION OF PROBLEM FIXED FOR APAR SE10763 : ----------------------------------------------- The Queue Manager fails to start because the automatic migration of cluster channel objects from MQ R520 to MQ R530 has corrupted the repository - due to an error in computing the size of the MQCD data area which needs to be migrated. CORRECTION FOR APAR SE10763 : ----------------------------- The problem of startup after migration has been corrected. The Queue Manager will be successfully started by ignoring corrupted entries in the cluster repository, and logging a new FDC record with Probe Id ZX054040 or ZX054060 in function zxcRestoreObject. The FDC will identify those cluster objects which need to be deleted and recreated after the Queue Manager has become active. CIRCUMVENTION FOR APAR SE10763 : -------------------------------- None. DESCRIPTION OF PROBLEM FIXED FOR APAR SE13524 : ----------------------------------------------- When rflOpen detects error rflRC_INCORRECT_FORMAT, the hFile handle is being freed and changed to NULL before closing the fildes in (hFile->fildes) - causing a pointer exception. CORRECTION FOR APAR SE13524 : ----------------------------- The condition causing the pointer exception whilst processing data in the Channel file and/or the Sync file has been fixed. CIRCUMVENTION FOR APAR SE13524 : -------------------------------- None. DESCRIPTION OF PROBLEM FIXED FOR APAR SE14146 : ----------------------------------------------- After applying CSD06, the CHGMQMQ command (or option 2 of the WRKMQMQ panel) does not work. When a change is attempted, the AMQ8008 message is displayed stating that the change has occured, but a display of the queue shows the attributes have not been changed. This problem is not reported when using the ALTER MQSC command to change the queue attributes. A similar problem happens with commands CPYMQMQ and CHGMQM. CORRECTION FOR APAR SE14146 : ----------------------------- The problem has been fixed in CSD07. The MQSeries command processor will correctly parse the parameters specified in the CHGMQMQ, CPYMQMQ and CHGMQM commands. CIRCUMVENTION FOR APAR SE14146 : -------------------------------- As a workaround :- Attributes of the queue can be changed using alter on mqsc command. DESCRIPTION OF PROBLEM FIXED FOR APAR SE13837 : ----------------------------------------------- This APAR describes two problems: i) a small timing window in ENDMQM with ENDCCTJOB(*YES) which prevents the tidy-up of shared memory files in /QIBM/UserData/mqm/qmgrs//&qmpersist after all Listener jobs have been ended. ii) none of the shared memory files are tidied up by ENDMQM with ENDCCTJOB(*YES) when the user of the ENDMQM command does not have sufficient authority to access the directory /QIBM/UserData/mqm/qmgrs/ CORRECTION FOR APAR SE13837 : ----------------------------- Both problems have been fixed. The program AMQICLEN, will operate with the authority of the QMQM profile, when it is used by ENDMQM with ENDCCTJOB(*YES). There is an extra delay of 2 seconds before starting the shared memory tidy-up. In addition, ENDCCTJOB(*YES) will log a QPRINT history file (for user QMQM) which will list all the Queue Manager directories which have been processed, and when MQMNAME(*ALL) is specified the process has been optimised to invoke AMQICLEN once only. This problem has been fixed in WMQ v5.3 CSD07. CIRCUMVENTION FOR APAR SE13837 : -------------------------------- None DESCRIPTION OF PROBLEM FIXED FOR APAR SE14672 : ----------------------------------------------- Tracing functions in the Command Server is controlled by flags YTRC_DATA_ADMIN and YTRC_FLOWS_ADMIN, but there is no corresponding TRCTYPE value which allows the user to set these flags. CORRECTION FOR APAR SE14672 : ----------------------------- Tracing functions in the Command Server will be controlled by flags YTRC_DATA_OTHER and YTRC_FLOWS_OTHER. The user can set these flags using TRCTYPE values *OTHDATA and *OTHFLOW respectively. This problem has been fixed in WMQ v5.3 CSD07 CIRCUMVENTION FOR APAR SE14672 : -------------------------------- Use TRCTYPE value *ALL. DESCRIPTION OF PROBLEM FIXED FOR APAR SE15656 : ----------------------------------------------- Collective Service Delivery for CSD07 CORRECTION FOR APAR SE15656 : ----------------------------- Collective service delivery for the set of CSD07 PTFs . - which contains fixes for all the problems listed below: . . . SE10763 - MQM400-MSGAMQ5615 STRMQM FAILS WITH AMQ5615 AFTER . AMQZXMA0 FAILS MCH0601 IN FUNCTION RFXADDCLQMGR . STRMQM fails after quiescing the QMANAGER with an . MSGAMQ5615. >> Default objects cannot be created: . CompCode = 0 Reason = 0. It was found that procedure . rfxAddCLQMGR had been called many times resulting in . the reported failure. The Queue Manager fails to start because the automatic migration of cluster channel . objects from MQ R520 to MQ R530 has corrupted the . repository - due to an error in computing the size of the MQCD data area which needs to be migrated. . . . SE12660 - MQM400-MSGMCH3601 AMQZXMAX DURING AN FPRINT STATEMENT 4 RECEIVES ON THE STRMQM. - AMQAPICA NEEDS TO CHECK . FOR NULL POINTER. . A failure occurs in AMQZXMAX which receives MCH3601 on STRMQM: To module . . . . . . . . : AMQAPICA_N To . procedure . . . . . . : lclPrintLogStats Statement . . . . . . . . : 4 Message . . . : Pointer not set . for location referenced. referenced. referenced. . SE13288 - MQM400-MSGAMQ9592 PROGRAM CANNOT RESOLVE QUEUE MANAGER OBJECT - THE ATTEMPT TO RESOLVE OBJECT '%CHLBATCH.18' FAILS RC 2195 . After migrating from MQ 5.2 to 5.3, one of our . channels will not start. Start fails, and Resolve . fails with: AMQ9592: Program can not resolve . queuemanager object. The attempt to resolve object . '%CHLBATCH.18' failed with reason code 2195. . SE13524 - MQM400 USING MQ CLIENT TO VIEW CHANNELS ON A SERVER . CAUSES THE CMD SERVER JOB (AMQPCSEA) TO FAIL WITH . MSGAMQ9604 AND MSGMCH3601 . Customers have a problem viewing channels via the . client using a svrconn (ILSMQP1.PRCMQP1) channel. On the client side message AMQ4032 is being generated and on the server (iSeries) side the AMQPCSEA job is . failing with a AMQ9604. . SE13837 - MQM400 - SHARED MEMORY IS BEING LEFT BEHIND IN &SYSTEM AND &QMPERSIST AFTER ENDMQMLSR IN OUR SHUTDOWN PROGRAM Shared memory is being left behind in &system and . &qmpersist if the user does not have *ALLOBJ . authority. . SE14146 - MQM400-MSGAMQ8008 CHGMQMQ COMMAND OR OPTION 2 OF THE . WRKMQM PANEL DOES NOT WORK AS EXPECTED (same as . SA96283 at R520) . The CHGMQMQ command or option 2 of the WRKMQM panel . does not work. When a change is attempted, message . AMQ8008 is displayed stating that the change has . occured, but a display of the queue shows the . attributes have not been changed. . SE14601 - MQM400-CHANNEL REMAINS IN STOPPED STATUS AFTER QUEUE . MANAGER . Enduser has migrated a V5.2 queue manager to V5.3. . The sender channels where placed in STOPPED status. . Now, when the migrated queue manager is started the . channels remain in STOPPED status, forcing the enduser to manually start the channels. (see also IY53917) . SE14672 - MQM400-MSGAMQ9554 ALLOW TRCTYPE(*OTHDATA *OTHFLOW) TO APPLY TO THE COMMAND SERVER COMPONENT . With the current TRCMQM, the only way to trace the . Command Server component is to use TRCTYPE(*ALL). We . can take an APAR which will allow us to deliver a . circumvention at R530, namely to allow . TRCTYPE(*OTHDATA *OTHFLOW) to trace the Command . Server. . SE15311 - MQM400 - TEST FIX FOR IY51907 AT CSD06 . SE15657 - MQM400 QUEUE MANAGER ENDS WHEN DAMAGED OBJECT IS . DETECTED AFTER FDC WITH PROBE ID AQ066010 IN . AQHALLOCATESPACE . Queue manager ends when damaged object is encountered, and object cannot be recovered using RCRMQMOBJ after . Queue Manager restart. . SA96202 - MQM400 USER MANAGED JOURNAL RECEIVER DOES NOT SWITCH . A User Managed Journal Reciever doesn't switch when a journal receiver size has exceeded its THRESHOLD value and if the RCDMQMIMG *ALL *ALL *YES command is run, . before the checkpoint has run on its own. . SA96224 - MQM400 RPG APPLICATION FAILS WITH ERROR CODE RC2023 . In RPG programs, MQINQ returns RC 2023 . (MQRC_INT_ATTRS_ARRAY_ERROR) when IACNT (IntAttrCount) is 0. . SA96333 - MQM400 - AMQALMP4 DOES NOT LOG NEW AMQ7460 OR AMQ7462 AND THE AMQERR01.LOG DOES NOT UPDATE THE JOURNAL . RECEIVER NAME . RCDMQMIMG with DSPJRNDTA(*YES), AMQ7460 or AMQ7462 . does not update the journal receiver name. . IC38202 - FDC file indicating a sigsegv exception in component . rrxReportError. . IC38311 - An API Exit puts a message within the BEFORE CMIT . entry using MQPUT with SYNCPOINT which fails when . runmqchl is a SENDER or SERVER channel type. Then it gets a 2195, thereby failing the channel. An FDC file is created with a Probe Id of AT032010, from component atmStartOp. . IC38907 - If the queue manager name passed to amqiclen contains a .(dot), for example MY.QMGR, amqiclen does not . produce any output (see also IY52444). . IC39552 - SDR & CLUSSDR CHANNELS CAN BECOME STUCK IN . INITIALIZING STATUS . IC39916 - When RCDMQMIMG reaches a temporary dynamic queue while recording the objects, it creates an AMQ7087 msg: . Object AMQ.xxxxxx , type queue is a temporary object . and fails to record the rest of the objects. . IY29028 - SDR channels stay in INITIALIZING state during . start-up. . IY35297 - Clustering: MQSeries did not return an error when an . MQCOMMIT was not successful in a clustering . environment. . IY47766 - After enabling pipelining on a channel that sends . messages larger then 4MB, regular AMQ9514 'Channel . is in use' and AMQ9558 'Remote Channel is not . currently available' messages are reported. . IY49438 - MQBEGIN fails with RC= 2128 ( MQRC_UOW_IN_PROGRESS ). Two applications connect to the same queue manager and they run transactions using two phase commit at the . same time. If one of them executes a transaction (not using two phase commit) without an MQBEGIN after an . MQBACK, the next MQBEGIN of the other application . fails with 2128. . IY50293 - An FDC file was produced for a read error - disk full on a model queue with enough disk space: The probes in the FDC are: AD030001 adiReadFile . xecF_E_UNEXPECTED_SYSTEM_RC and AQ168001 aqpReadData . arcE_PAST_EOF . IY50439 - An FDC file is created with probe CO052000, claiming . to have received invalid data. This is seen when the sending end violates the TSH protocol. A new FDC . (probe CO000044) is created to directly report the . protocol violation and to dump the received data. . IY50795 - An MQ application takes a long time to do its . processing and the transaction monitor software . assumes the transaction has timed out. The queue . manager fails to complete the xa_rollback call it . receives from the transaction monitor and program . amqzlaa0 creates FDC files with probe IDs of XC304020 from xlsDestroyMutex and XY398007 from . xcsFreeMemBlock. . IY51152 - An FDC file with probe RM409000 from rriWaitSecondary is followed by XC130003 from rriSendThread2 from the . same process (runmqchi), causing the channel initiator to die. This stops all channels running as threads in runmqchi, and stops channels from restarting, and the channel state stays as RETRYING. . IY51386 - Pubsub keeps sending messages to queue after . MQRC_Q_FULL, rc2053, is returned. Messages are put to the dead letter queue, until it reaches its maximum . queue depth. . IY51907 - Checkpointing for users with large queues of . persistent messages takes along time and locks out . other operations. RUNMQSC is not able to execute. . IY51992 - When creating a queue manager using the application . group option, for example crtmqm -g groupname qmgrname the permissions are not created properly for . /var/mqm/qmgrs//zsocketapp. The zsocketapp . directory is being created with universal access . (drwxrwxrwx) which is incorrect. . IY52011 - Channels create an FDC file with a channel in use . message. . IY52182 - Channel name is missing from message AMQ9514 when . displayed by runmqsc. . IY52344 - amqiclen -p qmgr prefix does not work; it fails to . find mqs.ini. Create a queue manager with MQSPREFIX . set so that the queue manager data is in a separate . directory, for example: # export . MQSPREFIX=/var/mqm/QMGRDIR # crtmqm NEWQMGR amqiclen . -c -m NEWQMGR -v -p QMGRDIR gives the error . message: Unable to get subpool lock. mqs.ini does not exist. . IY52444 - If the queue manager name passed to amqiclen contains a .(dot), for example MY.QMGR, amqiclen does not . produce any output (see also IC38907). . IY52569 - dis q(*) and dis ql(*) runmqsc commands hang . unexpectedly while a large queue is being loaded. . IY52572 - runmqsc is connected to a remote qmgr and the DIS QS . command is issued with a wild card specified in the . queue name. After the end of the list, runmqsc always displays AMQ8416: MQSC timed out waiting for a . response from the command server. . IY52575 - Improvements to amqiclen utility: 1. SEM: -1 -1 is . output if the semaphore set associated with the queue manager QMGR directory is not found. 2. Add -h flag to print headings in the amqiclen output. 3. Add -t flag to work with the -x flag to remove the trace control . SEM and SHM IPC resources associated with . /var/mqm/errors. 4. Add the description of the errno . (strerror) to error output. . IY52676 - SIGSEGV in zfu_as_SearchPrincipalList, while . authenticating the user ID passed from the client. . IY52951 - When strmqcsv is started repeatedly without stopping . after approximately 8182 times the strmqcsv command . creates an FDC file (probe-id XC307010 from . xlsRequestMutex). Also with each restart of strmqcsv (after 8182 times) strmqcsv returns with AMQ8101 error code. . IY53065 - An FDC file (Probe ID:ZL043050) is generated with a . segmentation violation(SIGSEGV). The customer uses . group messages. This problem is generated only when . the receiving process is completed without getting a . part of the messages. . IY53173 - Improve parameters traced on API exits. . IY53481 - Return value from rcrmqobj is incorrectly set to 71 . (Unexpected error) when -z option is used. . IY53668 - High CPU use in a threaded MCA process, for exmaple: . amqrmppa, runmqlsr, or runmqchi, when a channel runs . an exit which creates a thread which persists after . the exit is called for MQXR_TERM. . IY53700 - Clustering: There is an alias queue defined on QMGR_A whose target queue (targq) is a queue on QMGR_B. The queue on QMGR_B is a CLUSTER queue. The alias queue . on QMGR_A is not in the cluster. When putting a . message to the alias queue, the message goes to the . Dead Letter Queue with a reason of 2082 0x00000822 . MQRC_UNKNOWN_ALIAS_BASE_Q. . IY53907 - Clustering: During MQSET a user who has all . permissions for the cluster queue, but does not have a put permissions to the SYSTEM.CLUSTER.COMMAND.QUEUE. The agent fails with a 2035 error and creates an FDC . file with probe KN204020 from function . KqiDoPendingChangeCLQ. . IY53917 - Sender or server channels went into STOPPED state . after migrating from WMQ 5.2 to WMQ 5.3 (see also . SE14601) . 70541 - If the user issues a SysReq#2 to cancel an MQSC . session, subsequent MQSC sessions end imediately . with the message '0 MQSC commands completed . successfully'. . 75119.1 - Add trace into atmReplayComplete . 78045 - CURDEPTH value does not reset after restart of . queue manager . 78248 - Add trace into aqhLoadMsgChain . 78424 - alsReleaseGlobalHeap uses wrong FDC component name . 79209 - RUNMQCHI joblog does not record INITQ name. . 79805 - DSPMQMCHL with *CLTCN and *SVRCN channels shows wrong field data . 79958 - Add new #defines into copyfile CMQC . #define MQCIH_PASS_EXPIRATION 0x00000001 . #define MQCIH_UNLIMITED_EXPIRATION 0x00000000 . #define MQCIH_REPLY_WITHOUT_NULLS 0x00000002 . #define MQCIH_REPLY_WITH_NULLS 0x00000000 . #define MQCIH_SYNC_ON_RETURN 0x00000004 . #define MQCIH_NO_SYNC_ON_RETURN 0x00000000 . #define MQIIH_PASS_EXPIRATION 0x00000001 . #define MQIIH_UNLIMITED_EXPIRATION 0x00000000 . #define MQIIH_REPLY_FORMAT_NONE 0x00000008 . 80382 - CSD07J: Large message put/retrieve failed with FDC . probe AO107010 in aomRecordMediaImage. . CIRCUMVENTION FOR APAR SE15656 : -------------------------------- None. DESCRIPTION OF PROBLEM FIXED FOR APAR SE12660 : ----------------------------------------------- The fatal failure occurs in the AMQZXMAX job during an fprint statement because there was no checking for a NULL pointer being passed in as an argument. CORRECTION FOR APAR SE12660 : ----------------------------- The problem is caused by the unexpected exception when trying to open file /QIBM/UserData/mqm/Qmgrs//startprm/ZXMAXSTAT has been fixed. If the 'fopen' fails then a new FDC will be logged with probe 0 in function apiStartup (Probe Id AO000000), and the STRMQM task will continue to completion without logging any start-up statistics. CIRCUMVENTION FOR APAR SE12660 : -------------------------------- None. DESCRIPTION OF PROBLEM FIXED FOR APAR SE13288 : ----------------------------------------------- The receiver in-doubt problem is caused by a very small timing window which is allowing simultaneous updates of the channel status data. CORRECTION FOR APAR SE13288 : ----------------------------- Improvements have been made which maintain the integrity of the status data channel name, and a new FDC with probe RM351000 in rriAdoptMCA will be logged if an inconsistency is detected. CIRCUMVENTION FOR APAR SE13288 : -------------------------------- None DESCRIPTION OF PROBLEM FIXED FOR APAR SE14601 : ----------------------------------------------- EThe SYNC record structure is changed in WebSphereMQ R530. During the first start-up after migration from an earlier release, the Queue Manager will automatically convert all the messages in SYSTEM.CHANNEL.SYNCQ and save them back to the same queue. The problem is caused by this conversion process saving duplicate records for the same channel. One correct record, with channel status saved by channel process, and one erroneous record with corrupted message id and wrong channel status. During Queue Manager restart, the erroneous record will always be read(because it is at the beginning of the queue) and the wrong status restored. CORRECTION FOR APAR SE14601 : ----------------------------- The problem has been fixed. After Queue Manager restart, channels migrated from an earlier release will show status INACTIVE instead of status STOPPED. CIRCUMVENTION FOR APAR SE14601 : -------------------------------- None. DESCRIPTION OF PROBLEM FIXED FOR APAR SE15311 : ----------------------------------------------- When very stressed, MQ dumps long lock wait FDCs as a warning. MQ could sometimes deadlock dumping one of these FDCs. CORRECTION FOR APAR SE15311 : ----------------------------- The possible deadlock when dumping a long lock wait FFST has been fixed. CIRCUMVENTION FOR APAR SE15311 : -------------------------------- none DESCRIPTION OF PROBLEM FIXED FOR APAR SE15657 : ----------------------------------------------- When a damaged queue object was encountered, the aqhAllocateSpace routine generated an FDC with probe id AQ066010 and retcode = STOP_ALL. This caused the queue manager to end. The retcode should be set to lrcE_OBJECT_DAMAGED to makr the object as damaged and prevent the queue manager from ending aburptly. CORRECTION FOR APAR SE15657 : ----------------------------- Changes has been done for aqhAllocateSpace probe AQ066010 to set retcode = lrcE_OBJECT_DAMAGED and not STOP_ALL. The object would be marked as object damaged. The Object could be recovered from a media image using the RCRMQMOBJ provided RCDMQMIMG of the object has been successful, and that the journal containing the media image of the object is available The problem has been fixed in WMQ vresion 5.3 CSD07. CIRCUMVENTION FOR APAR SE15657 : -------------------------------- None. Activation Instructions None. Special Instructions Whether or not you have experienced this problem, it is recommended that you apply this PTF, following the instructions given below. This PTF, for WebSphere MQ for iSeries (5724B4106) Version 5 Release 3, is of type *IMMED. Before applying this PTF, you MUST stop ALL Queue Manager activity and FULLY quiesce WebSphere MQ :- 1. Use F12 (Cancel) to return to your initial MENU. Note: If you have WebSphere MQ Commands (CMDMQM) as your initial menu, change the initial menu in your user profile, sign off and sign on again. 2. Warn all users that you are going to shut down WebSphere MQ, and that they should not restart their Queue Managers or their MQI applications until all PTFs have been loaded and applied. 3. Quiesce all queue managers in a controlled manner: ... ENDMQM MQMNAME(*ALL) OPTION(*CNTRLD) ENDCCTJOB(*YES) TIMEOUT(15) 4. If step 3 does NOT log AMQ6154 ("Queue manager '*ALL' has been quiesced") then shut down WebSphere MQ using the *IMMED option: ... ENDMQM MQMNAME(*ALL) OPTION(*IMMED) ENDCCTJOB(*YES) TIMEOUT(15) 5. Shut down the default WebSphere MQ subsystem (QMQM) and also any user-defined WebSphere MQ subsystems: ... ENDSBS SBS(QMQM) OPTION(*IMMED) 6. Sign off, then sign on again. 7. Load and apply this PTF - using the OS/400 menu of PTF commands. 8. Load and apply other WebSphere MQ PTFs which are requisites for this PTF. 9. If steps 3 or 4 did NOT log AMQ6154 ("Queue manager '*ALL' has been quiesced") then you MUST clear WebSphere shared memory by repeating: ... ENDMQM MQMNAME(*ALL) OPTION(*IMMED) ENDCCTJOB(*YES) TIMEOUT(15) 10. Restart the WebSphere MQ subsystem: ... STRSBS SBSD(QMQM/QMQM) 11. Restart one or more Queue Managers, using either the STRMQM command or option 14 from the WRKMQM panel. All users who were actively using WebSphere MQ before it was quiesced should sign off and sign on again before restarting their Queue Managers or restarting their MQI applications. Default Instructions THIS PTF CAN BE APPLIED IMMEDIATE OR DELAYED. Supersedes PTF/FIX NO(S). APAR TITLE LINE -------------- ------------------------------------------------------------ SI13026 MQM400 Additional Service on CSD6 SI11236 MQM400 XSTCONNECTEXTENT FAILS WITH MSGMCH3601 SI11236 WHEN USING STRMQM, IF HE SYSTEM.CHANNEL.SYNCQ IS DAMAGED, SI11236 MQM400 Test Fix for SE12052 SI11236 MQM400 CSD06 CUMULATIVE SERVICE (WMQ 5.3 COMMANDS & OPS) SI11236 MQM400 XSTCONNECTEXTENT FAILS WITH MSGMCH3601 SI11236 MQM400 INTERMITTENT AMQ6125 PROBE ID AL029008 FOLLOWING SI10092 MQM400 CSD05 CUMULATIVE SERVICE (WMQ 5.3 COMMANDS & OPS) SI10092 MQM400 WAMQZDMAA CONSUMES HIGH CUP WHILE OPENING DOING SI10092 MQM400 QUEUE MANAGER DOES NOT END *IMMED WHEN RCDMQMIMG SI10092 MQM400 XY324192 GETSUBPOOLSLOCK XECF_E_UNEXPECTED_SYSTEM_RC SI10092 MQM400 MSGMCH3601 RECEIVED IN AQHRESIZESPACEMAP SI10092 MQM400 - STRMQM FAILS WITH AMQ7432 AFTER A SYSTEM FAILURE SI09428 MQM400 CSD04 CUMULATIVE SERVICE (MQSERIES OPS & CONTROLS) SI08397 MQM400 WMQ53 CSD03 CODE CHANGES FOR COMMANDS & OPERATIONS SI07469 MQM400 WMQ53 QMQM used when NO user id is specified for the Summary Information System.............................................. iSeries Models.............................................. Release............................................ V5R3M0 Recompile........................................ N Library................................................ QMQM MRI Feature...................................... NONE Cum Level...................................... C4209530 ------- Note: ------- IY36646: AN AMQPCSEA PROCESS DUMPED AN FDC DESCRIBING A CHANNEL THAT HAD UNEXPECTEDLY TERMINATED. EVEN THOUGH THE CHANNEL IS RUNNING FINE Fixes are available WebSphere MQ V5.3 Fix Pack 3 (CSD03) WebSphere MQ V5.3 and WebSphere MQ Express V5.3 - Fix Pack 14 (CSD14) WebSphere MQ v5.3 and WebSphere MQ Express v5.3 - Fix Pack 6 (CSD06) WebSphere MQ V5.3 and WebSphere MQ Express V5.3 - Fix Pack 9 (CSD09) WebSphere MQ V5.3 and WebSphere MQ Express V5.3 - Fix Pack 12 (CSD12) WebSphere MQ v5.3 for iSeries - Fix Pack 10 (CSD10) WebSphere MQ V5.3 for iSeries - Fix Pack 12 (CSD12) WebSphere MQ V5.3 for iSeries - Fix Pack 11 (CSD11) WebSphere MQ V5.3 & WebSphere MQ Express V5.3 - Fix Pack 7 (CSD07) WebSphere MQ v5.3 for iSeries - Fix Pack 8 (CSD08) WebSphere MQ V5.3 and WebSphere MQ Express V5.3 - Fix Pack 11 (CSD11) WebSphere MQ V5.3 and WebSphere MQ Express V5.3 - Fix Pack 13 (CSD13) WebSphere MQ V5.3 & WebSphere MQ Express V5.3 - Fix Pack 10 (CSD10) WebSphere MQ v5.3 and WebSphere MQ Express v5.3 - Fix Pack 05 (CSD05) WebSphere MQ V5.3 & WebSphere MQ Express V5.3 - Fix Pack 8 (CSD08) APAR status Closed as program error. Error description An amqpcsea process dumped an FDC describing a channel that had unexpectedly terminated. Even though the channel is running fine . It's possible that the pid info has got overwritten very briefly the rriAccessSync function. Local fix Eliminate the possibility by avoiding the temporary overwriting of the PID. Problem summary The problem has been fixed. Problem conclusion This problem has been fixed and the fix will be shipped in the following PTFs: . A) WebSphere MQ V5.3 CSD03 . Windows U200187 AIX U485561 HP-UX U485562 Linux on Intel U485563 Linux on zSeries U485646 Sun Solaris U485560 . Temporary fix Comments APAR information APAR number IY36646 Reported component name WEBS MQ FOR SUN Reported component ID 5724B4103 Reported release 530 Status CLOSED PER PE NoPE HIPER NoHIPER Special Attention NoSpecatt Submitted date 2002-11-04 Closed date 2002-11-20 Last modified date 2006-01-10 APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros Publications Referenced Fix information Fixed component name WEBS MQ FOR SUN Fixed component ID 5724B4103 Applicable component levels R530 PSY UP ------- Note: ------- IY47486: WEBSPHERE MQ PROCESSES RUNMQSC AND AMQPCSEA HANG ACCESSING CLUSTER OBJECTS Fixes are available WebSphere MQ V5.3 and WebSphere MQ Express V5.3 - Fix Pack 14 (CSD14) WebSphere MQ v5.3 and WebSphere MQ Express v5.3 - Fix Pack 6 (CSD06) WebSphere MQ V5.3 and WebSphere MQ Express V5.3 - Fix Pack 9 (CSD09) WebSphere MQ V5.3 and WebSphere MQ Express V5.3 - Fix Pack 12 (CSD12) WebSphere MQ v5.3 for iSeries - Fix Pack 10 (CSD10) WebSphere MQ V5.3 for iSeries - Fix Pack 12 (CSD12) WebSphere MQ V5.3 for iSeries - Fix Pack 11 (CSD11) WebSphere MQ V5.3 & WebSphere MQ Express V5.3 - Fix Pack 7 (CSD07) WebSphere MQ v5.3 for iSeries - Fix Pack 8 (CSD08) WebSphere MQ V5.3 and WebSphere MQ Express V5.3 - Fix Pack 11 (CSD11) WebSphere MQ V5.3 and WebSphere MQ Express V5.3 - Fix Pack 13 (CSD13) WebSphere MQ V5.3 & WebSphere MQ Express V5.3 - Fix Pack 10 (CSD10) WebSphere MQ v5.3 for iSeries - Fix Pack 6 (CSD06) WebSphere MQ v5.3 for iSeries - Fix Pack 9 (CSD09) WebSphere MQ V5.3 & WebSphere MQ Express V5.3 - Fix Pack 8 (CSD08) APAR status Closed as program error. Error description The problem is caused by a deadlock between amqrrmfa and amqzlaa0, and was introduced in CSD03 by defect 72223. Internal Reference Only:see prb 1441 Local fix Problem summary The problem is caused by a deadlock between amqrrmfa and amqzlaa0, and was introduced in CSD03 by defect 72223. Internal Reference Only:see prb 1441 Problem conclusion The problem has been fixed and will be inclu ded in: WebSphere MQ V5.3 CSD06 Windows U200202 AIX U489863 HP-UX U489864 Linux on Intel U489967 Linux on zSeries U489972 Sun Solaris U489865 Temporary fix Comments APAR information APAR number IY47486 Reported component name WEBS MQ FOR SUN Reported component ID 5724B4103 Reported release 530 Status CLOSED PER PE NoPE HIPER NoHIPER Special Attention NoSpecatt Submitted date 2003-08-12 Closed date 2003-08-13 Last modified date 2004-02-12 APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros Publications Referenced Fix information Fixed component name WEBS MQ FOR SUN Fixed component ID 5724B4103 Applicable component levels R530 PSY UP ------- Note: ------- AMQ9213 AMQCRSTA fails Technote (troubleshooting) Problem(Abstract) You start your sender channel and receive the following error: AMQ9213 from ioctl for TCP/IP giving rc=22(x'16'). This is EINVAL, which means that one of the parameters for ioctl is invalid. Cause The inetd configuration file did not have the correct information or syntax. Resolving the problem Receive on TCP using either of the following: Use the runmqlsr command See Using the WebSphere MQ listener Use the inet daemon See Using the inet daemon (INETD) Additional information The inetd configuration settings are detailed in the following manual starting with Chapter 12. Refer to the manual for the details regarding inetd configuration on your platform. WebSphere MQ Intercommunication (SC34-6587-00) Keywords: listener inetd fails RRCE_COMMUNICATIONS_ERROR COMMUNICATIONS ERROR AMQ9213 Cross Reference information Segment Product Component Platform Version Edition Business Integration WebSphere MQ Express Channel Linux, Windows 5.3 Product Alias/Synonym WebSphere MQ WMQ MQ ------- Note: ------- Using the inet daemon (INETD) To establish a TCP connection, follow these steps. Edit the file /etc/services. If you do not have the following line in the file, add it as shown: MQSeries 1414/tcp # MQSeries channel listenerNote: To edit this file, you must be logged in as a superuser or root. Edit the file /etc/inetd.conf. If you do not have the following line in that file, add it as shown: MQSeries stream tcp nowait mqm /opt/mqm/bin/amqcrsta amqcrsta [-m queue.manager.name]Find the process ID of the inetd with the command: ps -ef | grep inetdRun the command: kill -1 inetd processidIf you have more than one queue manager on your system, and therefore require more than one service, you must add a line for each additional queue manager to both /etc/services and inetd.conf. For example: MQSeries1 1414/tcp MQSeries2 1822/tcpMQSeries1 stream tcp nowait mqm /mqmtop/bin/amqcrsta amqcrsta -m QM1 MQSeries2 stream tcp nowait mqm /mqmtop/bin/amqcrsta amqcrsta -m QM2This avoids error messages being generated if there is a limitation on the number of outstanding connection requests queued at a single TCP port. For information about the number of outstanding connection requests, see Using the TCP listener backlog option. The inetd process on Linuxr can limit the rate of inbound connections on a TCP port. The default is 40 connections in a 60 second interval. If you need a higher rate, specify a new limit on the number of inbound connections in a 60 second interval by appending a period (.) followed by the new limit to the nowait parameter of the appropriate service in inetd.conf. For example, for a limit of 500 connections in a 60 second interval use: MQSeries stream tcp nowait.500 mqm /mqmtop/bin/amqcrsta amqcrsta -m QM1 ------- Note: ------- Using the extended inet daemon (XINETD) The following instructions describe how the extended inet daemon is implemented on Red Hat Linuxr. If you are using a different Linux distribution, you might have to adapt these instructions. To establish a TCP connection, follow these steps. Edit the file /etc/services. If you do not have the following line in the file, add it as shown: MQSeries 1414/tcp # MQSeries channel listenerNote: To edit this file, you must be logged in as a superuser or root. Create a file called MQSeriesr in the XINETD configuration directory, /etc/xinetd.d. Add the following stanza to the file: # WebSphere MQ service for XINETD service MQSeries { disable = no flags = REUSE socket_type = stream wait = no user = mqm server = /opt/mqm/bin/amqcrsta server_args = -m queue.manager.name log_on_failure += USERID } Restart the extended inet daemon by issuing the following command: /etc/rc.d/init.d/xinetd restart If you have more than one queue manager on your system, and therefore require more than one service, you must add a line to /etc/services for each additional queue manager. You can create a file in the /etc/xinetd.d directory for each service, or you can add additional stanzas to the MQSeries file you created previously. The xinetd process on Linux can limit the rate of inbound connections on a TCP port. The default is 50 connections in a 10 second interval. If you need a higher rate, specify a new limit on the rate of inbound connections by specifying the 'cps' attribute in the xinetd configuration file. For example, for a limit of 500 connections in a 60 second interval use: cps = 500 60 ------- Note: ------- SE31933 - MQM400 RUNMQCHL JOBLOG DO NOT CONTAIN ANY USEFUL ERROR MESSAGE. APAR (Authorized Program Analysis Report) Abstract MQM400 RUNMQCHL JOBLOG DO NOT CONTAIN ANY USEFUL ERROR MESSAGE. Error Description The RUNMQCHL joblog contents are different from v5 to v6. For example, at v5.3 the RUNMQCHL joblog contains: CPF1124 CPI1125 AMQ7163 AMQ9002 AMQ9558 AMQ9999 AMQ6993 CPF1164 . And at v6.0 the RUNMQCHL joblog contains: CPF1124 CPI1125 AMQ7163 CPF1164 . At v6 the messages are being written to the AMQZMUR0 process joblog instead of the RUNMQCHL joblog. Problem Summary **************************************************************** USERS AFFECTED: Users having channels on iSeries Platforms affected: iSeries **************************************************************** PROBLEM SUMMARY: In WMQv6, the task of writing messages to AMQERR01.LOG is handed off outside the RUNMQCHL process by the error log daemon and messages are also written to the joblog of AMQZMUR0. Problem Conclusion Changes has been carried out for logging the message locally to the RUNMQCHL joblog instead of logging in AMQZMUR0 joblog. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: v6.0 Platform Fix Pack 6.0.2.4 -------- -------------------- iSeries SI31813 The latest available maintenance can be obtained from 'Websphere MQ Recommended Fixes' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037 If the maintenance level is not yet available, information on its planned availability can be found in 'Websphere MQ Planned Maintenance Release Dates' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309 --------------------------------------------------------------- Temporary Fix Comments Circumvention Refer Queue manager error log for channel related errors. PTFs Available R600 SI33280 1000 Affected Modules Affected Publications Summary Information Status............................................ CLOSED PER HIPER........................................... No Component.................................. 5724H7206 Failing Module.......................... RCHMGR Reported Release................... R600 Duplicate Of.............................. ------- Note: ------- IY94700: Hang in channel processes such as runmqlsr, amqrmppa, runmqchl. Fixes are available WebSphere MQ V5.3 and WebSphere MQ Express V5.3 - Fix Pack 14 (CSD14) WebSphere MQ V5.3 for iSeries - Fix Pack 14 (CSD14) WebSphere MQ V6.0 Fix Pack 6.0.2.2 WebSphere MQ V6.0 for iSeries Fix Pack 6.0.2.2 APAR status Closed as program error. Error description A channel process hangs. This can be diagnosed by obtaining SIGUSR2 FDCs from channel processes (or all processes if you aren't sure which are channel processes). You obtain a SIGUSR2 FDC from a process by sending it the SIGUSR2 signal, e.g. as root: "kill -s SIGUSR2 PID" or "kill -s USR2 PID", where PID is the pid of a channel process. If the following sequence is seen towards the end of the traceback info in the FDC, then you've most likely encountered this problem. --{ cccProcessReceive ---{ recv ---} recv rc=Unknown(FFFF) Local fix Problem summary **************************************************************** USERS AFFECTED: Users of channels. The likelihood of a hang is very small. The queue manager needs to be recycled if this occurs. Platforms affected: All Unix **************************************************************** PROBLEM SUMMARY: This problem shows up when a recvmsg function is interrupted and returns with an errno of EINTR. This causes the WMQ internal inter-process communications link to stall. Problem conclusion Corrected the handling of EINTR from the recvmsg function. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: v5.3 Platform Fix Pack 14 -------- -------------------- AIX U808477 HP-UX (PA-RISC) U808478 Solaris (SPARC) U808480 Linux (x86) U808481 Linux (zSeries) U808483 v6.0 Platform Fix Pack 6.0.2.2 -------- -------------------- AIX U809895 HP-UX (PA-RISC) U809898 HP-UX (Itanium) U810084 Solaris (SPARC) U809913 Solaris (x86-64) U810362 Linux (x86) U809950 Linux (x86-64) U810178 Linux (zSeries) U810081 Linux (Power) U810083 Linux (s390x) U810110 The latest available maintenance can be obtained from 'WebSphere MQ Recommended Fixes' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037 If the maintenance level is not yet available, information on its planned availability can be found in 'WebSphere MQ Planned Maintenance Release Dates' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309 --------------------------------------------------------------- Temporary fix Comments APAR information APAR number IY94700 Reported component name WMQ AIX V6 Reported component ID 5724H7201 Reported release 600 Status CLOSED PER PE NoPE HIPER NoHIPER Special Attention NoSpecatt Submitted date 2007-02-09 Closed date 2007-02-14 Last modified date 2007-07-27 APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros Publications Referenced Fix information Fixed component name WMQ AIX V6 Fixed component ID 5724H7201 ------- Note: ------- thread: Q: I follow WebSphere MQ Client v6.0 manual to verify my MQ installation. AFter define QM, QLOCAL and CHANNEL then start server connection by enter below runmqlsr command runmqlsr -t tcp -m queue.manager.1 -p 1414 -i 192.168.1.2 Besides '5274-H72 (C) Copyright IBM corp. 1994, 2004. ALL RIGHT RESERVED.' then nothing else is continue to display. I have to press CTRL+C to break it. Can anyone tell me what did I miss? A: You are doing it right at first. By pressing Ctrl-C you are actually killing your listener. You can start your listener in the background so that your command window is available for use. On any Unix flavour, use runmqlsr -t tcp -m queue.manager.1 -p 1414 -i 192.168.1.2 & And on Windows start /b runmqlsr -t tcp -m queue.manager.1 -p 1414 -i 192.168.1.2 ------- Note: ------- runmqlsr (run listener) Purpose Use the runmqlsr command to start a listener process. This command is run synchronously and will wait until the listener process has finished before returning to the caller. Syntax >>-runmqlsr-- -t -----------------------------------------------> >--+- tcp --+------------+--+--------------+--+---------------+-+--> | '- -p --Port-' '- -i --IPAddr-' '- -b --Backlog-' | +- lu62 -- -n --TpName---------------------------------------+ | .---------------------. | | V | | +- netbios ----+-----------------+-+-------------------------+ | +- -a --Adapter---+ | | +- -l --LocalName-+ | | +- -e --Names-----+ | | +- -s --Sessions--+ | | '- -o --Commands--' | | .-------------------. | | V | | '- spx ----+---------------+-+-------------------------------' +- -x --Socket--+ '- -b --Backlog-' >--+----------------+------------------------------------------>< '- -m --QMgrName-' Required parameters -t The transmission protocol to be used: tcp Transmission Control Protocol / Internet Protocol (TCP/IP) lu62 SNA LU 6.2 (Windowsr only) netbios NetBIOS (Windows only) spx SPX (Windows only) Optional parameters -p Port The port number for TCP/IP. This flag is valid for TCP only. If you omit the port number, it is taken from the queue manager configuration information, or from defaults in the program. The default value is 1414. -i IPAddr The IP address for the listener, specified in one of the following formats: IPv4 dotted decimal IPv6 hexadecimal notation Alphanumeric format This flag is valid for TCP/IP only. On systems that are both IPv4 and IPv6 capable you can split the traffic by running two separate listeners, one listening on all IPv4 addresses and one listening on all IPv6 addresses. If you omit this parameter, the listener listens on all configured IPv4 and IPv6 addresses. -n TpName The LU 6.2 transaction program name. This flag is valid only for the LU 6.2 transmission protocol. If you omit the name, it is taken from the queue manager configuration information. -a Adapter The adapter number on which NetBIOS listens. By default the listener uses adapter 0. -l LocalName The NetBIOS local name that the listener uses. The default is specified in the queue manager configuration information. -e Names The number of names that the listener can use. The default value is specified in the queue manager configuration information. -s Sessions The number of sessions that the listener can use. The default value is specified in the queue manager configuration information. -o Commands The number of commands that the listener can use. The default value is specified in the queue manager configuration information. -x Socket The SPX socket on which SPX listens. The default value is hexadecimal 5E86. -m QMgrName The name of the queue manager. By default the command operates on the default queue manager. -b Backlog The number of concurrent connection requests that the listener supports. See LU62, NETBIOS, TCP, and SPX for a list of default values and further information. Return codes 0 Command completed normally 10 Command completed with unexpected results 20 An error occurred during processing Examples The following command runs a listener on the default queue manager using the NetBIOS protocol. The listener can use a maximum of five names, five commands, and five sessions. These resources must be within the limits set in the queue manager configuration information. runmqlsr -t netbios -e 5 -s 5 -o 5 ------- Note: ------- IC35473: APAR TO DESCRIBE AND DOCUMENT DEFECT 54255.1REGARDING RUNMQCHI IS NOT HANDLING SIGCHLD RESULTINGIN DEFUNCT PROCESSES APAR status Closed as program error. Error description Runmqchi is not correctly handling the SIGCHLD signal from channelprocesses which results inthe the DEFUNCT processes. this has been fixed via internal defect 54255.1 Local fix fix exists via defect 54255.1 Problem summary The problem has been fixed. Problem conclusion This problem has been fixed and the fix will be shipped in PTFs U200155 and U200156. Temporary fix Comments APAR information APAR number IC35473 Reported component name MQSERIES FOR CO Reported component ID 5765E3800 Reported release 510 Status CLOSED PER PE NoPE HIPER NoHIPER Special Attention NoSpecatt Submitted date 2003-01-20 Closed date 2003-01-28 Last modified date 2003-01-28 APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros Publications Referenced Fix information Fixed component name MQSERIES FOR CO Fixed component ID 5765E3800 Applicable component levels R510 PSY UP ------- Note: ------- SE29898: MQM400 - Unexpected job descriptions for AMQPCSEA and APAR status Closed as documentation error. Error description Enduser has created a job description for the AMQPCSEA. RUNMCHL, RUNMQMLSR jobs in the queue manager library, not referenced when WMQ tasked started. In enduser environment the QMQMJOBD job description in the QMQM library. . Steps to recreate: . 1. CRTMQM MQMNAME(COMMON) . 2. Create job descriptions for queue manager jobs: . CRTDUPOBJ OBJ(QMQMJOBD) FROMLIB(QMQM) OBJTYPE(*JOBD) TOLIB(QMCOMMON) NEWOBJ(AMQALMPX) CRTDUPOBJ OBJ(QMQMJOBD) FROMLIB(QMQM) OBJTYPE(*JOBD) TOLIB(QMCOMMON) NEWOBJ(AMQRRMFA) CRTDUPOBJ OBJ(QMQMJOBD) FROMLIB(QMQM) OBJTYPE(*JOBD) TOLIB(QMCOMMON) NEWOBJ(AMQZDMAA) CRTDUPOBJ OBJ(QMQMJOBD) FROMLIB(QMQM) OBJTYPE(*JOBD) TOLIB(QMCOMMON) NEWOBJ(AMQZFUMA) CRTDUPOBJ OBJ(QMQMJOBD) FROMLIB(QMQM) OBJTYPE(*JOBD) TOLIB(QMCOMMON) NEWOBJ(AMQZLAA0) CRTDUPOBJ OBJ(QMQMJOBD) FROMLIB(QMQM) OBJTYPE(*JOBD) TOLIB(QMCOMMON) NEWOBJ(AMQZMGR0) CRTDUPOBJ OBJ(QMQMJOBD) FROMLIB(QMQM) OBJTYPE(*JOBD) TOLIB(QMCOMMON) NEWOBJ(AMQZMUC0) CRTDUPOBJ OBJ(QMQMJOBD) FROMLIB(QMQM) OBJTYPE(*JOBD) TOLIB(QMCOMMON) NEWOBJ(AMQZMUR0) CRTDUPOBJ OBJ(QMQMJOBD) FROMLIB(QMQM) OBJTYPE(*JOBD) OLIB(QMCOMMON) NEWOBJ(AMQZXMA0) CRTDUPOBJ OBJ(QMQMJOBD) FROMLIB(QMQM) OBJTYPE(*JOBD) TOLIB(QMCOMMON) NEWOBJ(RUNMQCHL) CRTDUPOBJ OBJ(QMQMJOBD) FROMLIB(QMQM) OBJTYPE(*JOBD) TOLIB(QMCOMMON) NEWOBJ(RUNMQCHI) CRTDUPOBJ OBJ(QMQMJOBD) FROMLIB(QMQM) OBJTYPE(*JOBD) TOLIB(QMCOMMON) NEWOBJ(RUNMQLSR) CRTDUPOBJ OBJ(QMQMJOBD) FROMLIB(QMQM) OBJTYPE(*JOBD) TOLIB(QMCOMMON) NEWOBJ(QMQMJOBD) . 3. STRMQM MQMNAME(COMMON) 4. CRTMQMLSR LSRNAME(LISTENER1516) MQMNAME(COMMON) CONTROL(*QMGR) PORT(1516) NOTE: This will create the *NEW* WMQ V6 Listener object, which will automatically starts and terminates with the queue manager. 5. ENDMQM MQMNAME(COMMON) OPTION(*IMMED) ENDCCTJOB(*YES) RCDMQMIMG(*YES) TIMEOUT(15) 6. STRMQM MQMNAME(COMMON) 7. STRMQMLSR PORT(1818) MQMNAME(COMMON) NOTE: This is the pre-WMQ V6 way of starting the queue manager. . . NOTE: Command server and channel initiator configured to start with the queue manager. . With queue manager active, use option 22 from the WRKMQM panel to display list of queue manager jobs. . Name Application 069981/QMQM/AMQALMPX Checkpoint Job 069988/QMQM/AMQPCSEA Command Server 069983/QMQM/AMQRRMFA Repository Manager 069984/QMQM/AMQZDMAA Deferred Message Handler 069978/QMQM/AMQZFUMA Object Authority Manager 069986/QMQM/AMQZLAA0 Queue Manager Agent 069985/QMQM/AMQZMGR0 Process Controller 069979/QMQM/AMQZMUC0 Utility Manager 069982/QMQM/AMQZMUR0 Utility Manager 069977/QMQM/AMQZXMA0 Execution Controller 069997/QMQM/PUTXMSGSX2 PUTXMSGS 069987/QMQM/RUNMQCHI Channel Initiator 069989/QMQM/RUNMQLSR Threaded Listener <-- STRMQMLSR 1515 069990/QMQM/RUNMQLSR Threaded Listener <-- STTMQMLSR 1516 Listener object . Use option 5 (Display), then option 2 (Display job definition attributes) for job AMQPCSEA, RUNMQCHI and RUNMQLSR. . Job: AMQPCSEA User: QMQM Number: 068777 Job description . . . . . . . . . . : AMQZMGR0 Library . . . . . . . . . . . . . : QMCOMMON Job queue . . . . . . . . . . . . . : Library . . . . . . . . . . . . . : . Job: RUNMQCHI User: QMQM Number: 068776 Job description . . . . . . . . . . : AMQZMGR0 Library . . . . . . . . . . . . . : QMCOMMON Job queue . . . . . . . . . . . . . : Library . . . . . . . . . . . . . : . Job: RUNMQLSR User: QMQM Number: 069990 Job description . . . . . . . . . . : AMQZMGR0 Library . . . . . . . . . . . . . : QMCOMMON Job queue . . . . . . . . . . . . . : Library . . . . . . . . . . . . . : NOTE: This job represents the listener object . Job: PUTXMSGSX2 User: QMQM Number: 070000 Job description . . . . . . . . . . : AMQZMGR0 Library . . . . . . . . . . . . . : QMCOMMON Job queue . . . . . . . . . . . . . : Library . . . . . . . . . . . . . : NOTE: This job represents the user-defined application . These jobs are spawned via AMQZMGR0, which is the name of job description being referenced. Local fix Enduser will create a job description AMQZMGR0 in the queue manager library. Informed the customer with WebSphere MQ V6 these jobs are now spawned from AMQZMGR0 and they can control the job attributes via this job description. Problem summary When the jobs AMQPCSEA and RUNMQCHI are started, they do not pick up the job descriptions created by the same name in queue manager library or QMQM library, but instead takes the job description used by AMQZMGR0 job. Users affected: WMQ users on iSeries platform defining the job descriptions AMQPCSEA and RUNMQCHI. Platforms affected: iSeries The jobs AMQPCSEA and RUNMQCHI are spawned by the parent job AMQZMGR0 rather than started as a batch job. While spawning, the parent job passes all the attributes to the child job. Hence AMQPCSEA and RUNMQCHI job adopts the job description of AMQZMGR0. Problem conclusion In the "WebSphere MQ for iSeries System Administration Guide" Version 6.0 manual, in chapter "Chapter 4. Work management" on section "How WebSphere MQ uses the work management objects" pg 46, the following text needs to be corrected. "Note: If WebSphere MQ jobs do not appear to be starting, make sure that the subsystem is running and the job queue is not held," The corrected text is "Note: 1. If WebSphere MQ jobs do not appear to be starting, make sure that the subsystem is running and the job queue is not held. 2. The AMQPCSEA and RUNMQCHI jobs are spawned from the parent job AMQZMGR0 and hence they inherit the job attributes of AMQZMGR0, including the job descriptions." Temporary fix Comments APAR information APAR number SE29898 Reported component name WMQ ISERIES V6 Reported component ID 5724H7206 Reported release 600 Status CLOSED DOC PE NoPE HIPER NoHIPER Special Attention NoSpecatt Submitted date 2007-10-03 Closed date 2007-10-30 Last modified date 2007-10-30 APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros Publications Referenced SC34658600 Fix information Applicable component levels R600 PSY UP ------- Note: ------- ------- Note: ------- ------- Note: ------- ------- Note: ------- ------- Note: ------- ------- Note: ------- ------- Note: ------- ------- Note: ------- ------- Note: ------- ------- Note: ------- ------- Note: ------- ------- Note: ------- ------- Note: ------- ------- Note: ------- ------- Note: ------- ------- Note: ------- Installing MQ on AIX: 1. Some Definitions first: ========================== 1.1: Websphere MQ, formerly known as MQ (message queue) series, is an IBM standard for program-to-program messaging across multiple platforms. Websphere MQ is sometimes referred to as message-oriented middleware (MOM). 1.2: MQSeries is an IBM software family whose components are used to tie together other software applications so that they can work together. This type of application is often known as business integration software or middleware. 2. Some Important characteristics: ================================== MQ is asynchronous messaging, which means that the sending process doesn't have to wait until the receiving process handles the data before it continues processing. Additionally, the content of the data doesn't have to be defined up front (although obviously the receiver needs to know what to do with it when it arrives). 3. Sample installation on unix (AIX): ===================================== On AIX, you can use smitty, or use the setup program on the media. WebSpherer MQ is supplied as a set of filesets that are installed using AIX's standard installation tools. The procedure below uses the smit tool, but you may chose to use installp, geninstall or the Web-based System Manager. You may select which components you want to install. The components and filesets are listed (partially) below; you must install at least the Runtime, and Server components. WebSphere MQ for AIXr can be installed as a server or a client. A WebSphere MQ server is an installation of one or more queue managers that provide queueing services to one or more clients. All the WebSphere MQ objects, for example queues, exist only on the queue manager machine (the WebSphere MQ server machine), and not the client. A WebSphere MQ server can also support local WebSphere MQ applications. A WebSphere MQ client is a component that allows an application running on one system to communicate with a queue manager running on another system. The output from the call is sent back to the client, which passes it back to the application. To install a WebSphere MQ client see, Installing a WebSphere MQ client. It is possible to have both a server and a client installation on the same machine, for instructions on how to do this see, Installing a client on the same machine as a server. File descriptors When running a multi-threaded process such as the agent process, you might reach the soft limit for file descriptors. This gives you the WebSphere MQ reason code MQRC_UNEXPECTED_ERROR (2195) and, if there are enough file descriptors, a WebSphere MQ FFSTT file. To avoid this problem, you can increase the process limit for the number of file descriptors. To do this, alter the nofiles attribute in /etc/security/limits to 10,000 for the mqm user id or in the default stanza. System Resource Limits Set the system resource limit for data segment and stack segment to unlimited using the following commands in a command prompt: ulimit -d unlimited ulimit -s unlimited Create the filesystems and userid and group before installation. Filesystems: ----------- The installation directory for the WebSpherer MQ product code is /usr/mqm. Working data is stored in /var/mqm. You cannot change these locations. The GSKit must also be installed into its default location. You can also create separate file systems for your log data (/var/mqm/log) and error files (/var/mqm/errors). If possible, store log files on a different physical volume from the WebSpherer MQ queues (/var/mqm). If you create separate file systems: The /var/mqm and /var/mqm/log directories must be on a local file system. The /var/mqm/errors directory can be NFS mounted. However, if you choose to NFS-mount /var/mqm/errors, the error logs might be lost if the network fails. WebSphere MQ libraries are in the following locations: /usr/mqm/lib (32-bit libraries) and /usr/mqm/lib64 (64-bit libraries). User account: ------------- WebSpherer MQ requires a user ID of the name mqm, with a primary group of mqm. The mqm user ID owns the directories and files that contain the resources associated with the product. If you want to run administration commands, for example crtmqm (create queue manager) or strmqm (start queue manager), your user ID must be a member of the mqm group. Users do not need mqm group authority to run applications that use the queue manager; it is needed only for the administration commands. You can use smitty to add an existing user ID to the mqm group. --------- Language: --------- To select messages in a different language, use the following command with the identifier for the language you want to install: export LANG=message identifier The message identifiers for the message catalogs are as follows: de_DE (German) es_ES (Spanish) etc.. -------------------------- Most important components: -------------------------- Component: Description: Fileset: Runtime Mandatory component. Needed for application development and provides support for mqm.base.runtime external applications. SDK Required for compiling applications. mqm.base.sdk Server The server feature allows you to run queue managers on your computer and connect mqm.server.rte to other computers over a network. Provides messaging and queuing services to applications, and support for WebSphere MQ client connections. Client The WebSphere MQ client is a small subset of WebSphere MQ, without a queue manager. mqm.client.rte Provides remote access to WebSphere MQ. Must be connected to a server. To install a client on the same machine as a server, use the Server CD-ROM; otherwise use the Clients CD-ROM. Sample programs Sample application programs. Needed if you want to check your WebSphere MQ installation mqm.base.samples using the verification procedures described in Verifying the installation using the JMS Postcard application. JavaT messaging The files needed for messaging using Java (includes Java Messaging Service). mqm.java.rte Man pages UNIXr man pages, in U.S. English, for the following: mqm.man.en_US.data Control commands Message Queue Interface (MQI) commands MQSC commands And a number of "message catalogs", such as the French Message catalogs mqm.msg.fr_FR,mqm.msg.Fr_FR ---------------- Filesets on AIX: ---------------- Fileset Component mqm.base.runtime Runtime mqm.base.samples Sample programs mqm.base.sdk Base Kit mqm.Client.Bnd Client Bundle (for Easy Installation) mqm.client.rte Client for AIX mqm.dce.samples DCE samples mqm.dce.server DCE support mqm.java.rte Java and JMS support mqm.keyman.rte Support for SSL key management mqm.server.rte Server mqm.Server.Bnd Server Bundle (for Easy Installation) gskak.rte IBM Global Security Kit V6 mqm.man.en_US.data Man pages (US English) mqm.msg.de_DE Message catalog (German) mqm.msg.De_DE Message catalog (German) mqm.msg.en_US Message catalog (US English) mqm.msg.es_ES Message catalog (Spanish) etc.. ------------- Installation: ------------- Log in as root. Insert the WebSphere MQ Server CD-ROM into the CD-ROM drive. Enter the following command to mount the CD-ROM: mount /cdrom Select the required smit window using the following sequence: Software Installation and Maintenance Install and Update Software Install and Update from ALL Available Software Alternatively you can use a fastpath command (smitty install_latest), however this does not give you the opportunity to install the language filesets. Click List to display the input device or directory for the software, select the location that contains the installation images. Use the SOFTWARE to install field to obtain a list of available filesets, and select the filesets you want to install. Ensure that you include the appropriate message catalog if you require a messages in a language different than that specified by the locale selected on your machine. Make sure that "Include corresponding LANGUAGE filesets?" is set to yes. Change "Preview new LICENSE agreements?" to yes and press Enter to view the license agreements. Change "ACCEPT new license agreements?" to yes and press Enter to accept the license agreements and install WebSphere MQ. ----------------------------- Testing a Local Installation: ----------------------------- >>> SETUP: ---------- To verify your installation you must first perform this task. From a shell window, use these steps to create a queue manager and a queue: -Log in as a user in the mqm group -Create a default queue manager called venus.queue.manager by entering the following command: $ crtmqm -q venus.queue.manager You will see messages telling you that the queue manager has been created, and that the default WebSpherer MQ objects have been created. To start the queue manager, type: $ strmqm A message tells you when the queue manager has started. - Enable MQSC commands by typing: $ runmqsc A message tells you that an MQSC session has started. - Define a local queue called ORANGE.QUEUE by entering the following command: define qlocal (orange.queue) A message tells you when the queue has been created. - Stop MQSC by typing: end You will see some messages, followed by the command prompt. You have now defined: -- A default queue manager called venus.queue.manager -- A queue called ORANGE.QUEUE Note: Use the runmqsc command to issue MQSC "Message Queue Script Command" commands to a queue manager. MQSC commands enable you to perform administration tasks, for example defining, altering, or deleting a local queue object. >> TEST: -------- Before completing this task you must have created a queue manager called venus.queue.manager and a local queue called ORANGE.QUEUE. For instructions on how to do this see Setting up the installation. To test the queue manager and queue, use the "amqsput" sample program to put a message on the queue, and the "amqsget" sample program to get the message back from the queue: - Log on as a user in group mqm, if you are not already. - Change into the /usr/mqm/samp/bin directory, which contains the sample programs. - Put a message on the queue using the following command: ./amqsput ORANGE.QUEUE The following messages are displayed: Sample AMQSPUT0 start target queue is ORANGE.QUEUE - Type some message text, on one or more lines, followed by a blank line. The following message is displayed: Sample AMQSPUT0 end Your message is now on the queue and the command prompt is displayed again. - To get the message from the queue, use the following command: ./amqsget ORANGE.QUEUE The sample program starts, and your message is displayed. After a pause, the sample ends and the command prompt is displayed again. You have now successfully verified your local installation. ---------------------------------------- Testing a Server to Server Installation: ---------------------------------------- To verify a server-to-server installation using two servers, one as a sender and one as a receiver, complete the following tasks. -Setting up the sender server -Setting up the receiver server -Testing communication between the servers >>> Setting up the sender server In order to verify a server-to-server installation you must first set up a sender server. From a shell window, follow these steps to set up the sender server. Log in as a user in the mqm group. Create a default queue manager called saturn.queue.manager with the following command: $ crtmqm -q saturn.queue.manager Messages tell you that the queue manager has been created, and that the default WebSpherer MQ objects have been created. To start the queue manager, type: $ strmqm A message tells you when the queue manager has started. Start MQSC commands by typing: $ runmqsc A message tells you that an MQSC session has started. Define a local queue called TRANSMIT1.QUEUE (to be used as a transmission queue) by entering the following command: define qlocal (transmit1.queue) usage (xmitq) A message tells you when the queue has been created. Define a local definition of the remote queue with the following command: define qremote (local.def.of.remote.queue) rname (orange.queue) rqmname ('venus.queue.manager') xmitq (transmit1.queue) The name specified by the rname parameter must be the same as the name of the queue to which you are sending the message (ORANGE.QUEUE on the receiver workstation). Define a sender channel with the following command: define channel (first.channel) chltype (sdr) conname ('con-name(port)') xmitq (transmit1.queue) trptype (tcp) The value con-name is the TCP address of the receiver workstation, and port is the port number, port 1414 is the default port number. End MQSC by typing: end Some messages are displayed, followed by the shell prompt. You have now defined the following objects: A default queue manager called saturn.queue.manager A transmission queue called TRANSMIT1.QUEUE A local definition of a remote queue called LOCAL.DEF.OF.REMOTE.QUEUE A sender channel called FIRST.CHANNEL Now to set up the receiver server so that you can verify your server-to-server installation, see Setting up the receiver server. >>> Setting up the receiver server: After you have completed the task, Setting up the sender server, follow these steps to set up the receiver server: Log in as a user in the mqm group. Create a default queue manager called venus.queue.manager by entering the following command: $ crtmqm -q venus.queue.manager Messages tell you that the queue manager has been created, and that the default WebSpherer MQ objects have been created. To start the queue manager, type: $ strmqm A message tells you when the queue manager has started. Enable MQSC commands by typing: $ runmqsc A message tells you that an MQSC session has started. Define a local queue called ORANGE.QUEUE by entering the following command: define qlocal (orange.queue) A message tells you when the queue has been created. Define a listener by entering the following command: Note: If you do not specify the port that the listener should listen on, the default of 1414 is used. If you specified a port other than 1414 in step 7 of Setting up the sender server, you must include the port parameter in the command, as shown below. define listener (listener1) trptype (tcp) control (qmgr) port (port_number) Where port_number is the name of the port the listener should run on. This must be the same as the number used when defining your sender channel. Start the listener by entering the following command: start listener (listener1) Note: It is not recommended to start the listener in the background from any shell that automatically lowers the priority of background processes. Define a receiver channel with the following command: define channel (first.channel) chltype (rcvr) trptype (tcp) A message tells you when the channel has been created. End MQSC by typing: end Some messages are displayed, followed by the shellprompt. You have now defined the following objects: A default queue manager called venus.queue.manager A queue called ORANGE.QUEUE A receiver channel called FIRST.CHANNEL Now to test communications between your sender and receiver workstations, see Testing communication between the servers. >>> Testing communication between the servers After completing, Setting up the sender server, and Setting up the receiver server, use this topic to test communications between sender and receiver workstations using sample programs. Use the amqsput sample program to put a message from the sender server to a queue at the receiver server, and the amqsget sample program on the receiver server to get the message from the queue: Log in to both servers as a user in the mqm group. If the queue managers on the two servers have stopped, restart them now by typing the following on both servers: $ strmqm On the sender server, start the sender channel using the MQSC START CHANNEL command and specify the channel name: START CHANNEL(FIRST.CHANNEL) The receiver channel on the receiver server starts automatically when the sender channel starts. On the sender server, change into the /usr/mqm/samp/bin directory, which contains the sample programs. To put a message on the local definition of the remote queue (which in turn specifies the name of the remote queue), use the following command: ./amqsput LOCAL.DEF.OF.REMOTE.QUEUE You will see the following messages: Sample amqsput0 start target queue is LOCAL.DEF.OF.REMOTE.QUEUE Type some message text on one or more lines, followed by a blank line. You will see the following message: Sample amqsput0 end Your message is now on the queue and the command prompt is displayed again. On the receiver server, change into the /usr/mqm/samp/bin directory, which contains the sample programs. To get the message from the queue at the receiver, enter the following command: ./amqsget ORANGE.QUEUE The sample program starts, and your message is displayed. After a pause, the sample ends and the command prompt is displayed again. You have now successfully verified the server-to-server installation. ------- Note: ------- runmqsc (run MQSC commands) Purpose Use the runmqsc command to issue MQSC commands to a queue manager. MQSC commands enable you to perform administration tasks, for example defining, altering, or deleting a local queue object. MQSC commands and their syntax are described in the WebSphere MQ Script (MQSC) Command Reference. Syntax .------------------------------. V | >>-runmqsc----+--------------------------+-+--+----------+----->< +- -e ---------------------+ '-QMgrName-' +- -v ---------------------+ '- -w --WaitTime--+------+-' '- -x -' Description You can invoke the runmqsc command in three ways: Verify command Verify MQSC commands but do not run them. An output report is generated indicating the success or failure of each command. This mode is available on a local queue manager only. Run command directly Send MQSC commands directly to a local queue manager. Run command indirectly Run MQSC commands on a remote queue manager. These commands are put on the command queue on a remote queue manager and run in the order in which they were queued. Reports from the commands are returned to the local queue manager. Indirect mode operation is performed through the default queue manager. The runmqsc command takes its input from stdin. When the commands are processed, the results and a summary are put into a report that is sent to stdout. By taking stdin from the keyboard, you can enter MQSC commands interactively. By redirecting the input from a file, you can run a sequence of frequently-used commands contained in the file. You can also redirect the output report to a file. Optional parameters -e Prevents source text for the MQSC commands from being copied into a report. This is useful when you enter commands interactively. -v Verifies the specified commands without performing the actions. This mode is only available locally. The -w and -x flags are ignored if they are specified at the same time. -w WaitTime Run the MQSC commands on another queue manager. You must have the required channel and transmission queues set up for this. See Preparing channels and transmission queues for remote administration for more information. WaitTime The time, in seconds, that runmqsc waits for replies. Any replies received after this are discarded, but the MQSC commands still run. Specify a time between 1 and 999 999 seconds. Each command is sent as an Escape PCF to the command queue (SYSTEM.ADMIN.COMMAND.QUEUE) of the target queue manager. The replies are received on queue SYSTEM.MQSC.REPLY.QUEUE and the outcome is added to the report. This can be defined as either a local queue or a model queue. Indirect mode operation is performed through the default queue manager. This flag is ignored if the -v flag is specified. -x The target queue manager is running under z/OSr. This flag applies only in indirect mode. The -w flag must also be specified. In indirect mode, the MQSC commands are written in a form suitable for the WebSpherer MQ for z/OS command queue. QMgrName The name of the target queue manager on which to run the MQSC commands, by default, the default queue manager. Return codes 00 MQSC command file processed successfully 10 MQSC command file processed with errors; report contains reasons for failing commands 20 Error; MQSC command file not run Examples Enter this command at the command prompt: runmqscNow you can enter MQSC commands directly at the command prompt. No queue manager name is specified, so the MQSC commands are processed on the default queue manager. Use one of these commands, as appropriate in your environment, to specify that MQSC commands are to be verified only: runmqsc -v BANK < "/u/users/commfile.in" runmqsc -v BANK < "c:\users\commfile.in"This command verifies the MQSC commands in file commfile.in. The queue manager name is BANK. The output is displayed in the current window. These commands run the MQSC command file mqscfile.in against the default queue manager. runmqsc < "/var/mqm/mqsc/mqscfile.in" > "/var/mqm/mqsc/mqscfile.out" runmqsc < "c:\Program Files\IBM\WebSphere MQ\mqsc\mqscfile.in" > "c:\Program Files\IBM\WebSphere MQ\mqsc\mqscfile.out"In this example, the output is directed to file mqscfile.out.