Messages and codes
Use the information in these messages to help you diagnose and solve IMS Connect Extensions problems.
Return codes
The
following return codes are set by IMS Connect Extensions:
Return and reason codes supplied in the RSM
When IMS Connect Extensions rejects messages, it gives its return and reason code to the client in these RSM fields:
OMUSR reason code | RSM (decimal value) | Description |
---|---|---|
SECFAIL | 40 | Security failure: access denied |
DESTUNA | 72 | Transaction routing: destination unavailable |
PACELMT | 150 | Transaction pacing: pacing threshold exceeded |
N/A | 153 | Message exit not active |
SECINOP | 154 | Security failure: user ID, password, or group information missing or invalid |
N/A | 156 | Message exit deleted |
IPBLOCK | 157 | Blocked by IP address rule |
Reason codes in internal error messages
Internal reason codes are used by IBM® to debug internal errors. Only IBM can interpret these codes. Internal reason codes consist of 8 hexadecimal digits:
mmmmcccc
where:
Message format
Messages
begin with a unique identifier, followed by message text which may
contain symbol information to identify the circumstance which caused
the message:
CEXnnnnx Message text with symbol information
The message identifier has the format CEXnnnnx or FUNnnnnx where:
Each message also includes the following information:
Messages written to SYSLOG
The following IMS Connect Extensions messages are written to SYSLOG:
- CEX5006-5011
- CEX5019
- CEX5029-5030
- CEX5034-5036
- CEX5041-5042
- CEX5048-5050
- CEX5058, CEX5067, CEX5097
- CEX5112-5113
- CEX5131-5135
- CEX5189-5190
- CEX5192
- CEX5194-5195
- CEX5198-5199
- CEX5400, CEX5404, CEX5407
- CEX5587-5588
- CEX5594
- FUN1011-1012
- FUN1015-1016
- FUN2539
- FUN2596
- FUN2604
- FUN2702
- FUN2708-2711
Controlling which messages are written to SYSLOG
You can use the MESSAGE control option to control which messages are written to SYSLOG. The ADD_WTO suboption writes additional messages to SYSLOG. The DROP_CEXPRINT suboption stops specified CEX and FUN messages being written to CEXPRINT.REXX messages written to SYSTPRT
To ensure that messages are written to SYSTPRT, include theOPTION MSGLVL=VERBOSE
statement in the REXX exec after initializing the IMS Connect Extensions host command environment for REXX.