Analyzing errors from the data tables SVC

Following an error from a call to the data tables SVC, an exception trace point is always made, including an error code field to identify the reason for the error. These trace points are AP 0B12, 0B19, 0B1A, 0B29 and 0B2A.

There are three categories of SVC error:
  1. Conditions that are expected to occur, such as the remote file on a connect attempt not being a data table, or the remote system not having logged on as a shared data tables server. CICS® takes the appropriate action for such conditions, and no diagnostic information is needed.
  2. Errors that could be caused by problems in the environment that might be possible to correct. For these errors, a message is issued with the reason code for the error. The explanation of the reason code is included in the explanation of the message in CICS messages.
  3. Errors that indicate some sort of logic problem, or a misuse of the routines, possibly in an attempt to circumvent integrity or security checks. These errors are treated by CICS file control as disastrous errors, resulting in a system dump (if you have enabled such dumping) and, in most cases, in the transaction being abended with an AFCZ ABEND. For these, the value of the response and reason field is normally X'0215'.

The following topics explain the error codes for the third category of errors. These error codes are seen only in the exception trace entry. The format of the error code is X'ffaaaaaa', where ff identifies the type of failure, and aaaaaa is additional information provided for some of the failures. The possible values of ff for each trace point are described in the following topics.