The processing of a given cooperative flow is broken up into two large grain activities. The second is handleComm, which is invoked to send/receive data over an already active connection. This exit is invoked at the completion of the handleComm processing to expose that processing results. The handleComm will either be successful (indicated by the input parameter completionCode having a value of HANDLECOMM_OK) or not successful (indicated by the completionCode parameter having a value of HANDLECOMM_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). Therefore, if a completion code of HANDLECOMM_OK is received as input, the return value from this exit should be set to zero to let the processing of the flow continue.
If the completionCode has a value of HANDLECOMM_NOT_OK, this exit has the opportunity to indicate if the handleComm processing should be attempted by returning a value of zero (0). The number of flow attempts 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.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|