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:
- 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.
- 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 and Codes.
- 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'.
This section explains the error codes for the third category of errors
that is described above. 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 below.
Values for all trace points
The following error codes can occur for the 0B12, 0B19, 0B1A, 0B29, and
0B2A exception trace points:
- X'01'
- A function was specified that requires the caller to be authorized via
the CICS AFCB (authorized function control block), but the caller was not
authorized.
- X'0A'
- The caller passed an invalid function code.
- X'0B'
- The caller specified an invalid format of SVC call.
- X'0C'
- An invalid parameter list address was passed to the SVC.
- X'0D'
- A function was specified that requires the value passed in register
1 to be 0, but it was not. The additional information contains the low-order
three bytes of the value passed.
- X'12'
- A function was specified that requires the caller to be in Key 0 supervisor
state, but the caller was not.
Values for 0B12 trace point
The 0B12 exception trace point is issued if an error is returned by the
SVC on adding or deleting an access list entry when a shared data table is
being closed. In addition to the errors that can occur at all trace points,
the following are possible:
- X'02'
- The CICS region has not yet performed SDT initialization (an anchor
block for the region has not been created).
- X'0E'
- The specified data space STOKEN is invalid or the caller is not authorized
to use it.
- X'0F'
- The CICS region has not completed initialization as a server.
- X'13'
- An attempt to delete an access list entry failed because the specified
entry was not created by the data tables SVC.
All other errors result in a message being issued that contains the error
code.
Values for 0B19 trace point
The 0B19 exception trace point is issued if an error is returned by the
SVC on initializing as a shared data table server. In addition to the errors
that can occur at all trace points, the following are possible:
- X'02'
- An attempt was being made to add an access list entry before the CICS
region had performed SDT initialization (an anchor block for the region had
not yet been created).
- X'0E'
- The specified data space STOKEN is invalid or the caller is not authorized
to use it.
- X'0F'
- An attempt was being made to add an access list entry before the CICS
region had completed server initialization.
All other errors result in a message being issued that contains the error
code.
Values for 0B1A trace point
The 0B1A exception trace point is issued if an error is returned by the
SVC on initializing a shared data table requester. In addition to the errors
that can occur at all trace points, the following is possible:
- X'05'
- The CICS region has already initialized as a shared data table requester,
but is now running under a different request block from when it originally
initialized.
All other errors result in a message being issued that contains the error
code.
Values for 0B29 trace point
The 0B29 exception trace point is issued if an error is returned by the
SVC on logging on as a shared data table server. In addition to the errors
that can occur at all trace points, the following are possible:
- X'02'
- The CICS region that is attempting to register (logon) as a server has
not yet been initialized (an anchor block for the region has not been created).
- X'04'
- This CICS region has already registered (logged on) as a shared data
tables server.
- X'0F'
- The CICS region has not completed server initialization.
- X'14'
- The AFCS anchor block does not exist.
- X'15'
- The CICS security block does not exist.
- X'16'
- Either the caller is not running in a user protection key (its PSW key
is less than 8), or the caller’s TCB does not normally execute in a user
protection key (TCBPKF is less than 8).
All other errors result in a message being issued that contains the error
code.
Values for 0B2A trace point
If the function code field contains X'15', the 0B2A exception trace
point indicates an error on CONNECT (that is, on attempting to establish a
connection to a remote file). In addition to the errors that can occur at
all trace points, the following are possible:
- X'02'
- The requesting region has not performed SDT initialization (an anchor
block for the region has not been created).
- X'03'
- The requesting region has not completed initialization as a shared data
tables requester.
- X'05'
- The CICS region is running under a different request block (RB) from
when it initialized as a data table requester. The additional information
part of the error code contains the RB address the call was made under.
- X'72'
- The LINK to the user-replaceable DFHACEE module to find the home address
space’s security userid has failed. The additional information part of
the error code contains two bytes of the ABEND code from the LINK. The response
and reason field accompanying this error is X'020B'.
All other errors result in a message being issued that contains the error
code.
If the function code field contains X'16', the 0B2A exception trace
point indicates an error on DISCONNECT (that is, on attempting to break the
connection to a remote file). In addition to the errors that can occur at
all trace points, the following are possible:
- X'02'
- The requesting region has not performed SDT initialization (an anchor
block for the region has not been created).
- X'03'
- The requesting region has not completed initialization as a shared data
tables requester.
- X'05'
- The CICS region is running under a different request block (RB) from
when it initialized as a data table requester. The additional information
part of the error code contains the RB address the call was made under.
- X'07'
- The caller has supplied an invalid index into the vector of file connections.
The additional information part of the error code contains the low-order three
bytes of the caller’s index.
- X'10'
- The specified connection was broken previously and no longer exists.
The additional information part of the error code contains the low-order three
bytes of the caller’s index into the vector of file connections.
All other errors result in a message being issued that contains the error
code.
[[ Contents Previous Page | Next Page Index ]]