Handling an incomplete posting

The association batch feature depends on the integration being called at the end of a batch to process the log, usually after the last checkout or checkin completes. If this last event is missed, for example, the last checkin failed because the file was identical, the log is not processed and the Rational® ClearQuest® operations are not posted. The data is not lost and is posted on the next successful DevOps Code ClearCase® operation that can begin processing the log. But the log may stay in the stored location for some time before the processing starts. You or the developer can force the log to be processed by using the following command from a command shell in the original VOB context:

cqcc_launch -vob -op batch

The batch operation processes any transactions that are in the log.