Previous Topic: Source CodeNext Topic: Arguments


Purpose

The processing of a given cooperative flow is broken up into two large grain activities. The first is setupComm, which is invoked to insure a connection to the target server is available. This exit is invoked at the completion of the setupComm processing to expose that processing results. The setupComm will either be successful (indicated by the input parameter completionCode having a value of SETUPCOMM_OK) or not successful (indicated by the completionCode parameter having a value of SETUPCOMM_NOT_OK).

The return from this exit indicates if the processing of the cooperative flow should continue (zero lets the process continue, non-zero causes the processing of the flow to be terminated). If the completionCode has a value of SETUPCOMM_NOT_OK, this exit has the opportunity to indicate if the setupComm processing should be attempted by returning a value of zero (0). The number of connection retries attempted is passed into this exit using the numberOfAttempts parameter. Thus, this exit can control the number of retry attempts by testing the value of numberOfAttempts and returning one (1) when the number of retries has reached a predetermined threshold.