S
Sasha Kraljevic
Guest
If you read further in the same place you will see that there is another environment variable called SUPER-PROC. If you define : SUPER-PROC=mybatch.p and in the mybatch.p you put the following code: mybatch.p code procedure init-batch: RUN my-init-batch.p . end. procedure run-batch-object: RUN my-run-batch-object.p . end. procedure end-batch: RUN my-end-batch.p . end. /mybatch.p code You will execute these procedures at the end of the specified BATCH_INTERVAL. In other words, you can place any RUN statement that you need in one of these internal procedures and they will get executed - therefore no need to change Progress supplied source code. This in combination with other environment variables, should you choose not to use standard WebSpeed built-in db connectivity, will you give you exactly what you want: checking db connectivity within procedure every BATCH_INTERVAL. I've used this to manage the session/context information cleanup within WebSpeed application. Hope this helps...
Continue reading...
Continue reading...