PPM Support Tip: SYNCH_EXEC_INIT_WAIT_TIME server parameter
KCS article: KM00615420
The Admin Guide discusses some parameters for the look-ahead page on execution steps. These are the following:
SYNCH_EXEC_INIT_WAIT_TIME (default: 4 secs)
SYNC_EXEC_POLL_INTERVAL (default: 4 secs)
SYNC_EXEC_MAX_POLL_TRIES (default: 15 secs)
There have been some misunderstandings on how this is supposed to work.
The general understanding seems to be that when set, the *INIT_WAIT_TIME-parameter will kick in after a certain wait time if the request workflow step execution has then not finished and will then wait for the given value amount of time to check by the poll interval if the execution has finished.
If the execution step is triggered and finishes after two seconds – no wait page is shown
If the execution step is triggered and would potentially finish after six seconds – the wait page kicks in after four seconds and after an interval of another four seconds, the *POLL_INTERVAL checks for completion.
However, this is not the correct. The design is as follows:
With the *INIT_WAIT_TIME-parameter set to four seconds, then when you click the workflow button on the request detail page, the page will wait for 4 seconds; during these 4 seconds nothing is done, it will not execute the execution step. What happens is that the execution step (including ksc_store command) will start execution after or four seconds if SYNCH_EXEC_INIT_WAIT_TIME=4, thus after this time the page will go to the wait page (intermediate Request Working page), and the execution step is active and starts executing.
Once this has happened and with the *POLL_INTERVAL on default value of four seconds, the wait page will check if the execution step has completed after four seconds. If yes, it will return to the request details page in the next status (if the step completed successfully); if not, if will again poll for four seconds for completion. With the default settings, it will continue to poll for a total of 15 times before timing out.