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:
0
Operation was successful.
4
Operation completed, but a warning (W) message was issued during processing.
8
Operation may be incomplete. A failure (F) message was issued and IMS Connect Extensions continues processing.
12
Operation may be incomplete. An error (E) condition occurred.
16
Operation is incomplete. A severe error (S) condition occurred.

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:

RSM_RETCOD
The return code is always 8, meaning the message was rejected.
RSM_RSNCOD
Possible reason codes are shown in the following table.
Table 1. Reason codes generated by IMS Connect Extensions
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:

mmmm (the first four digits)
Identifies the internal function or module that reported the error.
cccc (the last four digits)
Identifies the condition that triggered the internal error. Different modules may use the same four digits to indicate different error conditions.

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:

CEX
Identifies the message as an IMS Connect Extensions product message.
FUN
Identifies the message as a Common Services Library functional support message.
nnnn
A unique four-digit message identification number.
x
Indicates the severity of the message and the return code. The severity levels, from least to most severe, are:
I
Information. No action required.

(Corresponds to a return code 0.)

W
Warning. Possible problems occurred that you should evaluate.

(Corresponds to a return code 4.)

F
Failure. Your action may be required as processing is incomplete.

(Corresponds to a return code 8.)

E
Error. Your action required. Processing is incomplete.

(Corresponds to a return code 12.)

S
Severe. Internal logic error requiring your attention.

(Corresponds to a return code 16.)

Each message also includes the following information:
Explanation:
The Explanation section explains what the message text means, why it occurred, and what its variables represent.
System action:
The System action section explains what the system will do in response to the event that triggered this message.
User response:
The User response section describes whether a response is necessary, what the appropriate response is, and how the response will affect the system or program.

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 the OPTION MSGLVL=VERBOSE statement in the REXX exec after initializing the IMS Connect Extensions host command environment for REXX.