Error message example

Error messages have severity E or S. There are three general classes of error:
  • Errors caused by incorrect user input, such as incorrect password (SLR0071E) or filter did not find any data sets (CSI0051E). Such errors can be rectified by correcting the input and retrying the action. Some of these error messages can only occur due to incorrect input to the set of z/Server APIs, typically from an Eclipse client.
  • Errors that indicate problems in the configuration file, such as EMC0011E (port is not available). Such errors may be corrected by changing the configuration (a task for the system administrator), although they can also indicate some other error that needs to be investigated (also a task for the system administrator).
  • Errors that indicate an internal z/Server error, such as API0007E (error during call to EZASOKET). If the message information provided does not help to identify the problem, please contact Customer Care.

As an example, the CSI0051E message is issued by the CSI facility (CSI prefix) and has a severity of E (=error).

The message is shown as follows in this book:

CSI0051E [001] No data sets for filter [002] found

This message has two placeholders: [001] and [002]. The placeholders are replaced with the timestamp and the associated filter. An actual CSI0051E error message would look like this:

CSI0051E 07:48:53.935 No data sets for filter SYS2 found

The two placeholders have been replaced with the time (07:48) and the filter (SYS2) that could not be resolved. In this case, using a filter that covers available data sets would prevent the error message.