Hello, we have some discussions in our shop about how to handle Java batch jobs in JCL.
You have to know that our operating decided some decades ago that they want to use the abend-disposition for cleaning up if the executed COBOL program gets an error. This means they force an abend within the COBOL program code if the program detects some error. So instead of evaluating the RC within the JCL and executing the necessary steps for cleaning up they just rely on the abend-disposition for a rollback of GDGs etc.. This seems to work fine. I'm working for some months only at this company, but everybody from the operating says that they're pretty happy with this kind of cleanup procedure. I'm relatively new to the mainframe system programming (coming from the Unix world), but from my point of view this is 'untidy/dirty', and want to know if this practice is common to you. The conrete problem is that now we get some Java programs, means they're executed by the JVM which isn't so easy to force to abend. Of course we can do it by including some COBOL code or similar via JNI but at all I'm quite unsatisfied going this way because I think the correct way is to evaluate the RCs (which of course requires some additional work for our operating as they can't use anymore the easy to use abend-disposition for cleanup). However, I'm interrested in your opinions/experience. Thanks & Regards Daniel Erdmann ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
