z/OS Communications Server: CMIP Services and Topology Agent Guide
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Synchronous and asychronous functions

z/OS Communications Server: CMIP Services and Topology Agent Guide
SC27-3646-00

The return codes from synchronous functions indicate whether the function completed successfully. MIBConnect and MIBDisconnect are synchronous functions.

The return codes from asynchronous functions indicate only whether CMIP services received the request or response. All API functions, except MIBConnect and MIBDisconnect, are asynchronous functions.

All of the API functions that return an invoke identifier are asynchronous functions. The invoke identifier can be used to correlate the response to the original request. A return code of zero from the API function indicates that the request was successfully sent to CMIP services. The confirmation from the target of the request serves as the acknowledgement.

On confirmed requests, the object sending the request receives a MIB.ServiceError message or a CMIP message (ROIVapdu, RORSapdu, or ROERapdu). On unconfirmed requests, the object sending the request receives a MIB.ServiceAccept message or a MIB.ServiceError message.

Because responses are never confirmed, the object sending the response receives a MIB.ServiceAccept message or a MIB.ServiceError message.

Return codes are integers. A value of 0 always indicates success with no errors to report. The actual confirmation or error report is returned by CMIP services by one of the following methods:

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014