I'm really confused here. Isn't commitment control started by a STRCMTCTL
command? I don't understand why java changes anything. Can't you just call
STRCMTCTL from your java driver using CommandCall.run and then call your
slave COBOL programs from java using ProgramCallDocument.callProgram?

What am I missing?


-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx [mailto:java400-l-
bounces@xxxxxxxxxxxx] On Behalf Of Kiran Kumar
Sent: Wednesday, June 25, 2008 6:36 PM
To: java400-l@xxxxxxxxxxxx
Cc: kiran; kiran bathi

We are in the process of application migration from COBOL on System I
to Java. In the transition phase we would like to call some of the
complex COBOL programs from Java using PCML. I have few questions
related to commitment control.

Most of the applications follow a template where a master program
having start commitment control calls suite of child slave COBOL
programs. Based on the return code from the suite of slave COBOL
programs, a commit or a rollback is issue.

Most of the application will be re-written in java, but there are
scenario where the complex slave COBOL programs need to be called from
java. Is it possible to call a slave COBOL program without commitment
control from Java usingPCML? If so, where do we establish a commitment

If I need to call set of different slave COBOL programs from java, how
do I set the commitment boundary. The slave programs do not have
Startcommitment control?

This is the Java Programming on and around the iSeries / AS400
(JAVA400-L) mailing list
To post a message email: JAVA400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/java400-l.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].