SNAX/APC Application Programming Manual

ManualsBrandsHP ManualsServerHP NonStop G-Series

231

232

233

234

235

236

237

238

239

240

Application Prototype Simulator

SNAX/APC Application Programming Manual—138786

4-47

MC-DEALLOCATE (F3)

specifies an MC-DEALLOCATE (ABEND) request. The contents of the

SNAX/APC buffer are sent to the partner TP, and the conversation is terminated

abnormally. APS can use this type of deallocation request when it is in either

the Send or Receive state. Using it in the Send state could cause record

truncation. Using it in the Receive state could cause loss of data.

specifies an MC-DEALLOCATE (CONFIRM) request. Confirmation is

requested from the partner TP. If the request is confirmed, the conversation is

terminated normally (with an MC-DEALLOCATE return code of OK). If the

request is not confirmed, the return code will indicate the new state of the

conversation. The TP must be in the Send state to issue an MC-DEALLOCATE

(CONFIRM) request. Note that if a TP issues an MC-DEALLOCATE

(CONFIRM) request and its synchronization level is NONE, SNAX/APC rejects

the request.

specifies an MC-DEALLOCATE (FLUSH) request. The contents of the

SNAX/APC buffer are sent to the partner TP and the conversation is terminated

normally. APS must be in Send state to issue a MC-DEALLOCATE (FLUSH)

request.

specifies an MC-DEALLOCATE (LOCAL) request. The conversation is

deallocated locally, which releases local resources. This type of deallocation

request can only be used when the conversation is in the Deallocate state. A TP

enters the Deallocate state when it receives any of the following values in the

reply Header Return Code:

Deallocate Normal

Deallocate Abend Prog (for REP-RETURN-CODE-DETAIL value “0”)

Resource Fail No Retry

Resource Fail Retry

Allocation Error

If APS receives CONFIRM-DEALLOCATE, it enters the Confirm state. Once

the local TP issues the MC-CONFIRMED verb, it enters the Deallocate state

and can issue an MC-DEALLOCATE (LOCAL) request.

specifies an MC-DEALLOCATE (SYNC-LEVEL) request. If the

synchronization level is SYNCPT, the MC-DEALLOCATE will be rejected. If

the synchronization level is CONFIRM, confirmation is requested from the

partner TP. If confirmation is successful, the conversation is terminated

normally (with an MC-DEALLOCATE return code of OK). If the confirmation

is not successful, the return code will indicate the new state of the conversation.