|
|
|
|
The ABORT_ATTACH verb is used to end the processing of the attach by this TP server after the attach has been accepted using an ACCEPT_ATTACH verb because the TP server or TP has encountered an error during further processing. For example, the TP server was unable to fork to the TP. The ABORT_ATTACH verb can be issued by both the TP server and the TP processes.
The definition of the VCB structure for the ABORT_ATTACH verb is as follows:
typedef struct abort_attach
{
AP_UINT16 opcode;
unsigned char rsrvd1; /* Reserved */
unsigned char rsrvd2; /* Reserved */
AP_UINT16 primary_rc;
AP_UINT32 secondary_rc;
AP_UINT32 tps_id;
unsigned char attach_id[8];
AP_UINT32 reason;
} ABORT_ATTACH;
The TP supplies the following parameters to APPC:
The ID of the TP server, as returned on a previous REGISTER_TP_SERVER verb.
The ID of the attach to be aborted, as returned by the attach notification callback.
The reason the automatic start is being aborted. The value is an SNA sense code as shown in SNA Sense Codes.
After the verb executes, APPC returns parameters to indicate whether the execution was successful and, if not, to indicate the reason the execution was not successful.
If the verb executes successfully, APPC returns the following parameter:
AP_OK
If the verb does not execute successfully, APPC returns a primary return code parameter to indicate the type of error and a secondary return code parameter to provide specific details about the reason for unsuccessful execution.
If the verb does not execute because of a parameter error, APPC returns the following parameters:
AP_PARAMETER_CHECK
Possible values are:
The value specified for the attach_id parameter was not recognized.
The value specified for the tps_id parameter was not recognized.
If the verb does not execute because other conditions exist, APPC returns the following primary return code. For a list of return codes common to all verbs, see Common Return Codes.
|
|
|
 |
|