Hi,
I have a jal script that executes a database stored proc.
This proc may take 10 mins or so to finish, it then produces a file.
my next line in the jal looks for the existence of this file if it is there it processes it.
I am worried that the jal may issue the database command but not wait until it has finished processing and
go straight onto the next jal statement in which case the file will not be found.
Is there a way to stop this happening or am i supposed to create 2 jobs - one that runs the database command and the other
a file watch job that looks for the file ?

thanks.

24x7 normally waits for database commands to complete before returning control back to the script or job notification action. Only in a few rare cases it continues without waiting and only if the "Asynchronous operations" option is checked in the database profile properties. Uncheck this option to play it safe.
: Hi,
: I have a jal script that executes a database stored proc.
: This proc may take 10 mins or so to finish, it then produces a file.
: my next line in the jal looks for the existence of this file if it is there
: it processes it.
: I am worried that the jal may issue the database command but not wait until
: it has finished processing and
: go straight onto the next jal statement in which case the file will not be
: found.
: Is there a way to stop this happening or am i supposed to create 2 jobs - one
: that runs the database command and the other
: a file watch job that looks for the file ?

: thanks.

: 24x7 normally waits for database commands to complete before returning
: control back to the script or job notification action. Only in a few rare
: cases it continues without waiting and only if the "Asynchronous
: operations" option is checked in the database profile properties.
: Uncheck this option to play it safe.
OK Cheers