Only if you code an sproc that executes the shell scripts, though that's rather a clumsy solution.
Other options, code java sprocs to do the work (instead of writing in shell script), or if you must use shell scripts for some reason then schedule with cron or with an enterprise-scheduling-tool if your site uses such a thing.
if the shell scripts already invoke sprocs , what stops you from invoking those same sprocs from ATS ? any non-sproc logic in those shell scripts would need recoding appropriately, which may require wrapper sprocs.
"Only if you code an sproc that executes the shell scripts, though that's rather a clumsy solution."
as per your statement above in the same thread earlier (i agree with this).
i am trying below strategy..
Compile the java program:
2. Create a jar file:
jar cvf dsc_expiry_update.jar dsc_expiry_update.class
3. Register the jar file with DB2:
4. Trying to create a external db2 procedure calling this jar.
CREATE PROCEDURE EPROC.TEST_DSC_PROC()
DYNAMIC RESULT SETS 0
PARAMETER STYLE JAVA
MODIFIES SQL DATA
PROGRAM TYPE SUB
EXTERNAL NAME 'dsc_expiry_update!dsc_expiry_update'
Please suggest is this approach is better ?
Also i am getting error at step 4 above (already posted in forum "Sub: java sp in db2 procedures - error")