Table 57 summarizes the IIOP domain’s specific gates.
It shows the level-1 trace point IDs of the modules providing the functions
for the gates, the functions provided by the gates, and whether or not the
functions are available through the exit programming interface (XPI).
Table 57. IIOP domain’s specific gates
Gate |
Trace |
Function |
XPI |
IIRR |
II 0100
II 0101
|
PROCESS_REQUESTS
|
NO
|
IIRH |
II 0200
II 0201
|
FIND_REQUEST_STREAM
PARSE
|
NO
NO
|
IIMM |
II 0300
II 0301
|
ADD_REPLACE_RQMODEL
DELETE_RQMODEL
COMMIT_RQMODELS
|
NO
NO
NO
|
IIRQ |
II 0400
II 0401
|
INQUIRE_RQMODEL
START_BROWSE
GET_NEXT
END_BROWSE
MATCH_RQMODEL
|
NO
NO
NO
NO
NO
|
IIRP |
II 0700
II 0701
|
GET_INITIAL_DATA
RECEIVE_REQUEST
INVOKE
SEND_REPLY
RECEIVE_REPLY
INITIALISE
TERMINATE
|
NO
NO
NO
NO
NO
NO
NO
|
IIRS |
II 0900
II 0901
|
HANDLE_SECURITY_CONTEXT
DESTROY_VAULT
|
NO
NO
|
IICP |
II 0800
II 0801
|
ABSTRACT
|
NO
|
The ADD_LOGICAL_SERVER function of the IILS gate is used to invoke JAVA
code to add a logical server.
Input parameters
- logical_server
- Name of the logical server to be added.
- shelf
- Name of the shelf to which the logical server is to be added.
Output parameters
- RESPONSE
- is the domain’s response to the call. It can have any of these
values:
OK|EXCEPTION|DISASTER|INVALID|KERNERROR|PURGED
- [REASON]
- is returned when RESPONSE is EXCEPTION. Possible values are:
RESPONSE |
Possible REASON values |
EXCEPTION |
SHELF_ACCESS_ERROR |
The DELETE_LOGICAL_SERVER function of the IILS gate is used to invoke JAVA
code to delete a logical server.
Input parameters
- logical_server
- Name of the logical server to be deleted.
- shelf
- Name of the shelf to which the logical server is to be deleted.
Output parameters
- RESPONSE
- is the domain’s response to the call. It can have any of these
values:
OK|EXCEPTION|DISASTER|INVALID|KERNERROR|PURGED
- [REASON]
- is returned when RESPONSE is EXCEPTION. Possible values are:
RESPONSE |
Possible REASON values |
EXCEPTION |
NOT_FOUND
SHELF_ACCESS_ERROR
|
The PUBLISH_LOGICAL_SERVER function of the IILS gate is used to invoke
JAVA code to publish a logical server to JNDI.
Input parameters
- logical_server
- Name of the logical server to be published.
Output parameters
- RESPONSE
- is the domain’s response to the call. It can have any of these
values:
OK|EXCEPTION|DISASTER|INVALID|KERNERROR|PURGED
- [REASON]
- is returned when RESPONSE is EXCEPTION. Possible values are:
RESPONSE |
Possible REASON values |
EXCEPTION |
NOT_FOUND
JNDI_ERROR
|
The RETRACT_LOGICAL_SERVER function of the IILS gate is used to invoke
JAVA code to retract a logical server from the JNDI.
Input parameters
- logical_server
- Name of the logical server to be retracted.
Output parameters
- RESPONSE
- is the domain’s response to the call. It can have any of these
values:
OK|EXCEPTION|DISASTER|INVALID|KERNERROR|PURGED
- [REASON]
- is returned when RESPONSE is EXCEPTION. Possible values are:
RESPONSE |
Possible REASON values |
EXCEPTION |
NOT_FOUND
JNDI_ERROR
|
The ADD_REPLACE_RQMODEL function of the IIMM gate is used to install or
delete and install a request model.
Input parameters
- rqmodel_name
- Name of the request model to be installed.
- corbaserver
- Name of the corbaserver for this request model.
- model_type
- can be any of the following values: EJB | CORBA | GENERIC
- [module_pattern]
- If CORBA - name of the module.
- [interface_pattern]
- If CORBA - name of the interface.
- [bean_pattern]
- If EJB - name of the bean.
- [interface_type]
- If EJB - HOME | REMOTE | BOTH
- operation_pattern
- name of the operation.
- tranid
- Transaction name.
- catalog
- YES | NO. If YES the request model is added to the catalogue.
Output parameters
- duplicate_model_name
- Name of a model with the same parameters if DUPLICATE_PATTERN set.
- RESPONSE
- is the domain’s response to the call. It can have any of these
values:
OK|EXCEPTION|DISASTER|INVALID|KERNERROR|PURGED
- [REASON]
- is returned when RESPONSE is EXCEPTION. Possible values are:
RESPONSE |
Possible REASON values |
EXCEPTION |
INVALID_NAME
DUPLICATE_PATTERN
|
The DELETE_RQMODEL function of the IIMM gate is used to delete an installed
request model.
Input parameters
- rqmodel_name
- Name of the request model to be deleted.
Output parameters
- RESPONSE
- is the domain's response to the call it can have any of these values
OK|EXCEPTION|DISASTER|INVALID|KERNERROR|PURGED
- [REASON]
- is returned when RESPONSE is EXCEPTION. Possible values are:
RESPONSE |
Possible REASON values |
EXCEPTION |
NOT_FOUND |
The COMMIT_RQMODELS function of the IIMM gate is used to commit the request
model to the catalogue.
input parameters
- commit_token
- Token for catalogue writes.
Output parameters
- RESPONSE
- is the domain's response to the call it can have any of these values
OK|EXCEPTION|DISASTER|INVALID|KERNERROR|PURGED
- [REASON]
- is returned when RESPONSE is EXCEPTION. Possible values are:
RESPONSE |
Possible REASON values |
EXCEPTION |
NOT_FOUND |
The FIND_REQUEST_STREAM function of the IIRH gate is used to examine the
incoming GIOP request and to find a new or existing request stream using request
models and the directory.
It
also handles any incoming security contexts.
Input parameters
- request_block
- Address and length of the GIOP Request - the block must contain the
whole of the request header. It need not contain the body.
- [urm_commarea_block]
- Storage used as input to the security user-replaceable program.
- [urmname]
- Name of the security user-replaceable program.
- [userid]
- userid to be used by the ORB.
- [force_create]
- YES | NO - YES indicates that IIRH must CREATE a new request stream.
NO indicates that normal logic is used to see if a request stream exists and
to JOIN it if it does or CREATE a new one if it does not.
- [vault_ptr_addr]
- The address of the vault pointer, updated in DFHIIRS.
- [authentication_type]
- An enumerated type set from the AUTHENTICATION attribute of the TCPIPSERVICE
definition. Values are
NONE|BASIC|ASSERTED|CERTIFICATE
Output parameters
- request_stream_token
- The token, representing the request stream, to be used as input for
the SEND_REQUEST.
- result
- JOINED | CREATED - whether the request stream was joined or created.
- RESPONSE
- is the domain's response to the call it can have any of these values
OK|EXCEPTION|DISASTER|INVALID|KERNERROR|PURGED
- [REASON]
- is returned when RESPONSE is DISASTER or EXCEPTION. Possible values
are:
RESPONSE |
Possible REASON values |
DISASTER |
ABEND |
EXCEPTION |
URM_DENIED_PERMISSION
URM_USERID_NOTAUTH
INVALID_OBJECT_KEY
REQUEST_ERROR
|
The PARSE function of the IIRH gate is used to examine the incoming GIOP
request or reply and to return selected information in the output parameters.
Input parameters
- request_block
- Address and length of the GIOP Request/reply - the block must contain
the whole of the request/reply header. It need not contain the body.
Output parameters
- [response_expected]
- YES | NO - YES is set if the response_expected bit is on in the request
header.
- [reply_status]
- NO_EXCEPTION | USER_EXCEPTION | SYSTEM_EXCEPTION | LOCATION_FORWARD
This extracts the reply status from a reply header.
- [codeset_context]
- This is a block containing a pointer to and the length of the named
context if it exists within the request or reply. The pointer and length are
set to 0 if the context does not exist.
- [sending_context]
- This is a block containing a pointer to and the length of the named
context if it exists within the request or reply. The pointer and length are
set to 0 if the context does not exist.
- [tracking_context]
- This is a block containing a pointer to and the length of the named
context if it exists within the request or reply. The pointer and length are
set to 0 if the context does not exist.
- [connection_context]
- This is a block containing a pointer to and the length of the named
context if it exists within the request or reply. The pointer and length are
set to 0 if the context does not exist.
- [redirection_context]
- This is a block containing a pointer to and the length of the named
context if it exists within the request or reply. The pointer and length are
set to 0 if the context does not exist.
- [requestId]
- is the requestId extracted from the request or reply header.
- RESPONSE
- is the domain's response to the call it can have any of these values
OK|EXCEPTION|DISASTER|INVALID|KERNERROR|PURGED
- [REASON]
- is returned when RESPONSE is DISASTER or EXCEPTION. Possible values
are:
RESPONSE |
Possible REASON values |
DISASTER |
ABEND |
EXCEPTION |
REQUEST_ERROR |
The GET_INITIAL_DATA function of the IIRP gate is used by the ORB program
DFJIIRP (or its CICS-key equivalent DFJIIRQ) to set up an environment to allow
it to issue further IIRP requests and to return the output parameters below.
Input parameters
- none
-
Output parameters
- rp_token
- token to allow further calls for the same Request Processor
- server_name
- name of the corba server held by the request stream for the incoming
request.
- public_id
- The public_id that identifies the request stream for the incoming request.
- RESPONSE
- is the domain’s response to the call. It can have any of these
values:
OK|EXCEPTION|DISASTER|INVALID|KERNERROR|PURGED
- [REASON]
- is returned when RESPONSE is DISASTER or EXCEPTION. Possible values
are:
RESPONSE |
Possible REASON values |
DISASTER |
ERROR_REENTERED
ABEND
|
EXCEPTION |
REQUEST_STREAM_NOT_CURRENT
NO_SERVER_DATA
NO_PUBLIC_ID
|
The RECEIVE_REQUEST function of the IIRP gate is used by the ORB program
DFJIIRP (or its CICS-key equivalent DFJIIRQ) to receive a request via a request
stream from a Request Receiver. This is for INBOUND requests.
Input parameters
- RP_TOKEN
- Token supplied by GET_INITIAL_DATA or INITIALISE representing state
storage.
- CONTINUE
- YES | NO - YES is set if RECEIVE_REQUEST is to listen for a further
request.
- REQUEST_BUF
- A buffer, into which the received request is to be placed.
- RECEIVE_TYPE
- FULL | OVERFLOW - FULL is set for the first receive_request. OVERFLOW
is set if the buffer supplied to the first receive_request was too small.
Output parameters
- correlation_id
- The correlation id returned by the request stream receive_request.
- bytes_available
- Set if BUFFER_TOO_SMALL is set. It contains the actual size of of the
buffer needed which is obtained from the GIOP header received by receive_request.
- RESPONSE
- is the domain’s response to the call. It can have any of these
values:
OK|EXCEPTION|DISASTER|INVALID|KERNERROR|PURGED
- [REASON]
- is returned when RESPONSE is DISASTER, EXCEPTION, or INVALID. Possible
values are:
RESPONSE |
Possible REASON values |
DISASTER |
ERROR_REENTERED
ABEND
|
EXCEPTION |
RECEIVE_REQUEST_FAILED
LISTEN_FAILED
MESSAGE_NOT_RECEIVABLE
BUFFER_TOO_SMALL
TIMEOUT_NOTIFIED
GIOP_REQ_HEADER_INVALID
REQUEST_INVALID
|
INVALID |
INVALID_RP_TOKEN |
The INVOKE function of the IIRP gate is used by the ORB program DFJIIRP
(or its CICS-key equivalent DFJIIRQ) to send an outbound request and to receive
its reply.
Input parameters
- RP_TOKEN
- Token supplied by GET_INITIAL_DATA or INITIALISE representing state
storage.
- RS_TOKEN
- Token representing the outbound request stream.
- CONTINUE
- YES | NO - YES is set if RECEIVE_REQUEST is to listen for a further
request.
- REQUEST_BUF
- A block holding the request to be sent.
- REPLY_BUF
- A buffer, into which the reply is to be placed.
Output parameters
- bytes_available
- Set if BUFFER_TOO_SMALL is set. It contains the actual size of of the
buffer needed for the reply which is obtained from the GIOP reply header received
by INVOKE
- RESPONSE
- is the domain’s response to the call. It can have any of these
values:
OK|EXCEPTION|DISASTER|INVALID|KERNERROR|PURGED
- [REASON]
- is returned when RESPONSE is DISASTER, EXCEPTION, or INVALID. Possible
values are:
RESPONSE |
Possible REASON values |
DISASTER |
ERROR_REENTERED
ABEND
|
EXCEPTION |
REQUEST_RECEIVED
LISTEN_FAILED
MESSAGE_NOT_RECEIVABLE
RECEIVE_REPLY_FAILED
SEND_REQUEST_FAILED
BUFFER_TOO_SMALL
TIMEOUT_NOTIFIED
GIOP_REP_HEADER_INVALID
GIOP_FRAGMENT_NOT_EXPECTED
GIOP_CLOSE_CONN_RECEIVED
GIOP_FRAGMENT_EXPECTED
GIOP_INVALID_VERSION
GIOP_INVALID_MESSAGE_TYPE
GIOP_MESSAGE_ERROR_RCVD
REQUEST_INVALID
REDIRECTION_RECEIVED
|
INVALID |
INVALID_RP_TOKEN |
The RECEIVE_REPLY function of the IIRP gate is used by the ORB program
DFJIIRP (or its CICS-key equivalent DFJIIRQ) to receive an outbound reply
to an outbound request. It is used, following INVOKE, if INVOKE indicated
that a further request was ready before the reply was available (loopback)
or if the reply buffer supplied by INVOKE was too small.
Input parameters
- RP_TOKEN
- Token supplied by GET_INITIAL_DATA or INITIALISE representing state
storage.
- RS_TOKEN
- Token representing the outbound request stream.
- RECEIVE_TYPE
- FULL | OVERFLOW. FULL is set if all of the reply is to be received.
OVERFLOW is set if the previous INVOKE or RECEIVE_REPLY ended in BUFFER_TOO_SMALL.
- REPLY_BUF
- A buffer, into which the reply is to be placed.
Output parameters
- bytes_available
- Set if BUFFER_TOO_SMALL is set. It contains the actual size of of the
buffer needed for the reply which is obtained from the GIOP reply header received
by INVOKE.
- RESPONSE
- is the domain’s response to the call. It can have any of these
values:
OK|EXCEPTION|DISASTER|INVALID|KERNERROR|PURGED
- [REASON]
- is returned when RESPONSE is DISASTER, EXCEPTION, or INVALID. Possible
values are:
RESPONSE |
Possible REASON values |
DISASTER |
ERROR_REENTERED
ABEND
|
EXCEPTION |
REQUEST_RECEIVED
LISTEN_FAILED
MESSAGE_NOT_RECEIVABLE
RECEIVE_REPLY_FAILED
SEND_REQUEST_FAILED
BUFFER_TOO_SMALL
TIMEOUT_NOTIFIED
GIOP_REP_HEADER_INVALID
GIOP_FRAGMENT_NOT_EXPECTED
GIOP_CLOSE_CONN_RECEIVED
GIOP_FRAGMENT_EXPECTED
GIOP_INVALID_VERSION
GIOP_INVALID_MESSAGE_TYPE
GIOP_MESSAGE_ERROR_RCVD
REQUEST_INVALID
REDIRECTION_RECEIVED
|
INVALID |
INVALID_RP_TOKEN |
The SEND_REPLY function of the IIRP gate is used by the ORB program DFJIIRP
(or its CICS-key equivalent DFJIIRQ) to send a reply via a request stream
to an inbound request.
Input parameters
- RP_TOKEN
- Token supplied by GET_INITIAL_DATA or INITIALISE representing state
storage.
- REPLY_BUF
- A buffer containing the reply to be sent.
- CORRELATION_ID
- of the request returned by IIRP RECEIVE_REQUEST.
Output parameters
- RESPONSE
- is the domain’s response to the call. It can have any of these
values:
OK|EXCEPTION|DISASTER|INVALID|KERNERROR|PURGED
- [REASON]
- is returned when RESPONSE is DISASTER, EXCEPTION, or INVALID. Possible
values are:
RESPONSE |
Possible REASON values |
DISASTER |
ABEND |
EXCEPTION |
SEND_REPLY_FAILED |
INVALID |
INVALID_RP_TOKEN |
The INITIALISE function of the IIRP gate is used by the ORB
program DFJIIRP (or its CICS-key equivalent DFJIIRQ) to set up an environment
to allow it to issue further IIRP requests. This is used during COMMAND PROCESSING.
For example when DFJIIRQ is processing an ADD_CORBASERVER command.
Input parameters
- rp_token
- token to allow further calls for the same Request Processor.
Output parameters
- RESPONSE
- is the domain’s response to the call. It can have any of these
values:
OK|EXCEPTION|DISASTER|INVALID|KERNERROR|PURGED
- [REASON]
- is returned when RESPONSE is DISASTER. Possible values are:
RESPONSE |
Possible REASON values |
DISASTER |
ERROR_REENTERED
ABEND
|
The TERMINATE function of the IIRP gate is used by the ORB program DFJIIRP
(or its CICS-key equivalent DFJIIRQ) in normal and command processing mode
to free any storage obtained by GET_INITIAL_DATA or INITIALISE. If necessary,
it will also leave the request stream.
Input parameters
- rp_token
- token to allow further calls for the same Request Processor. If rp_token
is 0 then TERMINATE checks to see if this task has any state storage to be
freed.
Output parameters
- RESPONSE
- is the domain’s response to the call. It can have any of these
values:
OK|EXCEPTION|DISASTER|INVALID|KERNERROR|PURGED
- [REASON]
- is returned when RESPONSE is DISASTER. Possible values are:
RESPONSE |
Possible REASON values |
DISASTER |
ERROR_REENTERED
ABEND
|
The INQUIRE_RQMODEL function of the IIRQ gate is used to inquire on a particular
model, returning the output parameters below.
Input parameters
- rqmodel_name
- Name of the request model for which information is needed.
Output parameters
- [corbaserver]
- Name of the corbaserver for this request model.
- [model_type]
- EJB | CORBA | GENERIC
- [module_pattern]
- If CORBA - name of the module.
- [interface_pattern]
- If CORBA - name of the interface.
- [bean_pattern]
- If EJB - name of the bean.
- [interface_type]
- If EJB - HOME | REMOTE | BOTH
- [operation_pattern]
- name of the operation.
- [tranid]
- Transaction name.
- RESPONSE
- is the domain's response to the call it can have any of these values
OK|EXCEPTION|DISASTER|INVALID|KERNERROR|PURGED
- [REASON]
- is returned when RESPONSE is DISASTER or EXCEPTION. Possible values
are:
RESPONSE |
Possible REASON values |
DISASTER |
ABEND |
EXCEPTION |
NOT_FOUND |
The START_BROWSE function of the IIMM gate is used to return a token to
allow all the request models to be browsed.
Input parameters
- none
-
Output parameters
- browse_token
- token to be used by get_next and end_browse.
- RESPONSE
- is the domain’s response to the call. It can have any of these
values:
OK|EXCEPTION|DISASTER|INVALID|KERNERROR|PURGED
- [REASON]
- is returned when RESPONSE is EXCEPTION. Possible values are:
RESPONSE |
Possible REASON values |
EXCEPTION |
NONE |
The GET_NEXT function of the IIMM gate is used to pass back the output
parameters for the next request model.
Input parameters
- browse_token
- token created by start_browse representing the next request model
Output parameters
- rqmodel_name
- Name of the request model to be installed.
- [corbaserver]
- Name of the corbaserver for this request model.
- [model_type]
- EJB | CORBA | GENERIC
- [module_pattern]
- If CORBA - name of the module.
- [interface_pattern]
- If CORBA - name of the interface.
- [bean_pattern]
- If EJB - name of the bean.
- [interface_type]
- If EJB - HOME | REMOTE | BOTH
- [operation_pattern]
- name of the operation.
- [tranid]
- Transaction name.
- RESPONSE
- is the domain’s response to the call. It can have any of these
values:
OK|EXCEPTION|DISASTER|INVALID|KERNERROR|PURGED
- [REASON]
- is returned when RESPONSE is EXCEPTION. Possible values are:
RESPONSE |
Possible REASON values |
EXCEPTION |
BROWSE_END |
The END_BROWSE function of the IIMM gate is used to end the browse session.
Input parameters
- browse_token
- token created by start_browse.
Output parameters
- RESPONSE
- is the domain’s response to the call. It can have any of these
values:
OK|EXCEPTION|DISASTER|INVALID|KERNERROR|PURGED
- [REASON]
- is returned when RESPONSE is EXCEPTION. Possible values are:
RESPONSE |
Possible REASON values |
EXCEPTION |
none |
The MATCH_RQMODEL function of the IIRQ gate is used to find the most specific
request model that matches the input parameters.
Input parameters
- corbaserver
- Name of the corbaserver for this request model.
- [module_name_block]
- If CORBA - name of the module.
- [interface_name_block]
- If CORBA - name of the interface.
- [bean_name_block]
- If EJB - name of the bean.
- [interface_type]
- If EJB - HOME | REMOTE | BOTH
- operation_pattern
- name of the operation.
Output parameters
- [tranid]
- Transaction name from the matching model. If no match is found the default
of CIRP is returned.
- RESPONSE
- is the domain's response to the call it can have any of these values
OK|EXCEPTION|DISASTER|INVALID|KERNERROR|PURGED
- [REASON]
- is returned when RESPONSE is DISASTER or EXCEPTION. Possible values
are:
RESPONSE |
Possible REASON values |
DISASTER |
ABEND |
EXCEPTION |
none |
The PROCESS_REQUESTS function of the IIRR gate is used to receive a GIOP
request from a socket, find a request stream, send the request over the request
stream, optionally receive a reply and send the reply to the socket. This
process continues until the socket is closed or no further data is available.
Input parameters
- none
-
Output parameters
- RESPONSE
- is the domain’s response to the call. It can have any of these
values:
OK|EXCEPTION|DISASTER|INVALID|KERNERROR|PURGED
- [REASON]
- is returned when RESPONSE is DISASTER or EXCEPTION. Possible values
are:
RESPONSE |
Possible REASON values |
DISASTER |
ERROR_REENTERED
ABEND
|
EXCEPTION |
RESCHEDULE
NO_PERMISSION
GIOP_FRAGMENT_NOT_EXPECTED
GIOP_CLOSE_CONN_RECEIVED
GIOP_FRAGMENT_EXPECTED
GIOP_INVALID_HEADER
GIOP_INVALID_VERSION
GIOP_INVALID_MESSAGE_TYPE
GIOP_MESSAGE_ERROR_RCVD
GIOP_REPLY_RECEIVED
IIRH_FIND_EXCEPTION
SOCK_RECEIVE_TIMEOUT
|
The HANDLE_SECURITY_CONTEXT function of the IIRS gate is used by the Request
Handler to check that any relevant security context in an incoming request
is the correct one one and to validate the parameters therein
This function is handed a security context which it verifies (depending
on the msgType) and extracts the userid and password etc..If an error is found
it sets msgType and ErrorCode into the security context and returns information
to allow DFHIIRR to build a system exception.
Input parameters
- SECURITY_CONTEXT
- A buffer containing the address and length of the security context to
be checked.
If an exception response is returned the security context will
have been updated to be an error security context.
- AUTHENTICATION_TYPE
- An enumerated type containing the TCPIPSERVICE AUTHENTICATION value
- in other words, what sort of security context is expected. This may be
BASIC|ASSERTED
- VAULT_PTR_ADDR
- The address of the start of the vault chain. The vault contains sessionID
to userid mappings and is added to, looked up in if the security context is
BASIC.
- CORBASERVER
- ASSERTED IDENTITY needs the corbaserver name as input to a security
check.
Output parameters
- USERID
- The main aim of this module is to return a USERID for the ORB (DFJIIRP)
task to run under. Only returned with an OK response.
- STRING
- If an exception response is returned, STRING contains an enumerated
type to be used in the STRING section of the system exception written to the
client by DFHIIRR: for example, if the STRING returned is NO_PERMISSION, then
the string NO_PERMISSION is added to the system_exception reply. Values are
NO_PERMISSION|INTERNAL|MARSHAL
- RESPONSE
- is the domain's response to the call. It can have any of these values:
OK|EXCEPTION|DISASTER|INVALID|KERNERROR|PURGED
- [REASON]
- AUTHENTICATION_TYPEis returned when RESPONSE is DISASTER or EXCEPTION.
Possible values are:
RESPONSE |
Possible REASON values |
DISASTER |
ABEND |
EXCEPTION |
SECURITY_CHECK_FAILED |
The DESTROY_VAULT function of the IIRS gate is used by the Request Receiver
to delete any security vault entries that have built up for this connection.
Input parameters
- VAULT_PTR_ADDR
- The address of the start of the vault entry chain to be destroyed when
the socket is closed - either normally or in an error situation.
Output parameters
- RESPONSE
- is the domain's response to the call. It can have any of these values:
OK|EXCEPTION|DISASTER|INVALID|KERNERROR|PURGED
- [REASON]
- is returned when RESPONSE is DISASTER. Possible values are:
RESPONSE |
Possible REASON values |
DISASTER |
ABEND |
. :dt.:dd.is returned when RESPONSE is DISASTER, EXCEPTION, or INVALID.
Possible values are: :table refid='rsntab'. :thd. :c.RESPONSE :c.Possible
REASON values :ethd. :row. :c. DISASTER :c. ABEND :row. :c. EXCEPTION :c.
:etable. :edl.
[[ Contents Previous Page | Next Page Index ]]