Re: Cobol to Java communication

["Joe Sam Shirah" <jshirah@xxxxxxxxxxxxx>]

    Hi Tim,

    The ILE COBOL Programmers' Guide has info on using JNI from COBOL.  In
general, I stay away from native language to Java calls, especially on the
AS/400, but there are times when it is appropriate and the best way to go.
Unless you have a single or very few calls, you probably ( from a
performance and resource perspective ) don't want to execute the Java
command.

    Stored procedures are good in that they work, but bad for portability.
It's always interesting to me that programmers are happy about portability
*to* their platform, but dismiss it the other way.

    If you already have MQ Series, JMS is a great way to go.  If not, the
built in message queues on the AS/400 offer some real and inexpensive
advantages.

    As always, the goal should be what's best for your application(s),
while understanding what you are doing, why you are doing it and any
consequences, so you aren't backed into a corner later.  HTH,


                                                  Joe Sam

Joe Sam Shirah -        http://www.conceptgo.com
conceptGO         -        Consulting/Development/Outsourcing
Java Filter Forum:       http://www.ibm.com/developerworks/java/
Just the JDBC FAQs: http://www.jguru.com/faq/JDBC
Going International?    http://www.jguru.com/faq/I18N
Que Java400?             http://www.jguru.com/faq/Java400


----- Original Message -----
From: "Tim Gosnell" <tgosnell@xxxxxxxxxxxx>
To: <java400-l@xxxxxxxxxxxx>
Sent: Wednesday, March 24, 2004 11:39 AM
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
>