Re: Cobol to Java communication

[NGay@xxxxxxxxxxxxx]

Tim,

For doing synchronous calls from Cobol to Java, you can just execute the
JAVA command just as if you were running the class from the iSeries command
line, e.g. JAVA CLASS(com.company.class) PARM('ABC' '123')
CLASSPATH('/MyClasses/myarchive.jar') (your ILE programmers will know how
to do this in COBOL, I'm used to doing an 'execute message' to run iSeries
CL commands from COBOL but they may have another way).  Getting return
values is a little tricky since the parameters are input-only, we use data
queues to get return values out like this.

For doing synchronous calls from Java to Cobol, you can use PCML.  This is
way of describing the parameters of a Cobol/RPG/2E/etc program using XML.
Its far far simpler than any other way I've seen of calling these types of
programs from Java.  Just look up the javadoc for ProgramCallDocument in
the toolbox website at:

http://publib.boulder.ibm.com/iseries/v5r1/ic2924/index.htm?info/rzahh/page1.htm

Actually its making calls asynchronous which is usually harder :-)  We use
MQ as well (to do calls between multiple systems, not necessary because we
care about synchronous or asynchronous).  If you have MQ working,
everything else by comparison is a piece of cake!

Hope this helps,

Nigel Gay.



|---------+------------------------------------------------->
|         |           Tim Gosnell <tgosnell@xxxxxxxxxxxx>   |
|         |           Sent by:                              |
|         |           java400-l-bounces+ngay=cpaglobal.com@m|
|         |           idrange.com                           |
|         |                                                 |
|         |                                                 |
|         |           24/03/2004 13:09                      |
|         |           Please respond to Java Programming on |
|         |           and around the iSeries / AS400        |
|         |                                                 |
|---------+------------------------------------------------->
  
>--------------------------------------------------------------------------------------------------------------|
  |                                                                             
                                 |
  |       To:       java400-l@xxxxxxxxxxxx                                      
                                 |
  |       cc:                                                                   
                                 |
  |       Subject:  Cobol to Java communication                                 
                                 |
  
>--------------------------------------------------------------------------------------------------------------|





I'm a java developer with very little experience on the 400 or with COBOL
so
please be kind.

I'm putting together some preliminary documentation for our new project.
I'm currently exploring the ways that ILE COBOL (lots of ILE programmers in
house) and Java can communicate in a bi-directional manner.

We have transactions that must be synchronous, but not every transaction
must.

So far the only synchronous method I've found is via stored procedures.
Are
there additional synchronous methods of bi-directional communication?

For the asynchronous transactions, we're looking into data queues and
MQSeries.  Is there anything else I should consider here?

Just looking for a little input/guidance...

Tim





---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.620 / Virus Database: 399 - Release Date: 3/11/2004

_______________________________________________
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.








********************************************************************************
The information in this message is confidential and may be legally
privileged. It is intended solely for the addressee; access to this
email by anyone else is unauthorised.

If you are not the intended recipient: (1) you are kindly requested
to return a copy of this message to the sender indicating that you
have received it in error, and to destroy the received copy; and (2)
any disclosure or distribution of this message, as well as any action
taken or omitted to be taken in reliance on its content, is prohibited
and may be unlawful.
********************************************************************************