OSI/AS Programming Manual

APS_DISCARD_
APS Procedure Calls
3–70 056783 Tandem Computers Incorporated
APS_DISCARD_ This procedure allows you to delete the API context information for a connection.
After APS_DISCARD_ has completed successfully, you can no longer use the CEPI.
In normal circumstances, call APS_DISCARD_ after the connection has been released
or aborted by your application, by the remote application, or by the service provider.
In exceptional circumstances, you may wish to call APS_DISCARD_ without
previously releasing or aborting the connection. Doing this provides the most abrupt
disconnection possible.
For further information about the use of this procedure, see “Discarding a Connection
Context” in Section 2.
status := APS_DISCARD_ ( cepi ); ! I
status returned value
INT
indicates the outcome of the call. For the possible values of ZAPS-VAL-STATUS-
xxx, see “Status Codes” in Appendix B.
cepi input
INT:value
is the connection endpoint identifier (CEPI) for this connection. Note that after
this procedure has completed successfully, no further APS procedures can be
called for this CEPI.
Considerations
In nowait mode, do not call MFM_AWAITIOX_ to complete this procedure.
You can call APS_DISCARD_ at any time, even when APS procedures are
awaiting completion.
When you are using dynamic subdevices, APS_DISCARD_ deletes the subdevice
as it discards the connection context. After a subdevice is deleted, it can no longer
be referenced through the DSM interfaces. If a connection problem occurs and
you call APS_DISCARD_ , the source of the problem might therefore be difficult or
impossible to determine if you are using dynamic subdevices.
If you use static subdevices instead, they are not deleted by APS_DISCARD_.
This enables you to investigate the connection problem using the DSM interfaces
and later remove the subdevice using SCF commands.
For information about troubleshooting, refer to the Tandem OSI/AS Configuration
and Management Manual.