I think there must be a distiction between calling a module and another
transaction. E.g. with IMS you can do a program to program switch from
a IMS Java tran to an IMS COBOL tran, but these are separate
transactions (Units of work). I don't know enough about CICS but I
guess a COMMAREA call will be another transaction instance and is not
really calling a single module with a Parameter List. You might have a
wrapper that creates the Parameter List from the COMMAREA to call the
COBOL module.
The only way calling old COBOL from Java I know is using an OO COBOL or
C Wrapper (JNI) to stay within the UOW scope of the calling TCB. There
are other methods possible if there is a protocol in between (TCPIP
Listener, MQ, Java calls a DB2 Stored Proc that calls the Procedural
COBOL). Most of them are usable for small amounts of invokation, but do
not scale. Only some of them stay within the UOW of the caller, some to
not even support that. Most of them are a nightmare from the
performance point of view (Think of some applications having more than
100 modules).
For the other way around (COBOL calls Java), with some restrictions,
Java Objects can be instanciated and methods called/parameters passed
from procedural COBOL, I tried that with Enterprise COBOL for z/OS
V3R4. Some of the restrictions are Linked Module in a PDSE, XPLINK(ON),
POSIX(ON) to name the most significant.
Denis.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
