Overview of API functions

Table 1 lists the API functions and indicates the name of the module that must be loaded before invoking an API function. Although logical names such as MIBConnect and MIBSendRegister are used in the table, the physical names of the API functions are the module entry point names.

The abbreviation N/A in the Module Entry Point column indicates that these are the data space modules used for dequeueing or releasing the messages from the data space. The addresses of these modules are returned on the MIBConnect function. Refer to the data space vector format and the interface control block (ISTNMICB) format in the MIBConnect—MIB connection function.

The Type column indicates whether the function is synchronous or asynchronous. For a description of these types, see Synchronous and asychronous functions.

Table 1. API functions: module entry point, type, and where to find more information
API function	Module entry point	Type	More information
MIBConnect	ACYAPCNP	Synchronous	Page MIBConnect—MIB connection function
MIBDisconnect	ACYAPD1P	Synchronous	Page MIBDisconnect—MIB disconnection function
MIBSendRegister	ACYAPRGP	Asynchronous	Page MIBSendRegister—MIB asynchronous registration function
MIBSendDeleteRegistration	ACYAPDRP	Asynchronous	Page MIBSendDeleteRegistration—Deregistration function
MIBSendRequest	ACYAPQRP	Asynchronous	Page MIBSendRequest—MIB queue request function
MIBSendCmipRequest	ACYAPQCP	Asynchronous	Page MIBSendCmipRequest—CMIP request function
MIBSendResponse	ACYAPRSP	Asynchronous	Page MIBSendRequest—MIB queue request function
MIBSendCmipResponse	ACYAPCPP	Asynchronous	Page MIBSendCmipResponse—CMIP response function
Data space dequeue routine	N/A	Synchronous	Page Dequeueing a buffer with the dequeue routine
Data space release routine	N/A	Synchronous	Page Releasing a buffer with the release routine