Lars wrote:

        Have you considered to use Java only for the Web Voodoo and retain
        the (slightly modified) COBOL code for the heads-down business code
        and transactions? For example by running the COBOL code as a child
        process of the Java VM or in a separate server job?

Actually, that was how the 'system' was going to operate in the beginning, a
JAVA prog was to call a COBOL prog.  However, we are not JAVA folks, recall
that we have a product that converts COBOL to JAVA (it needs some tweaking).
So, when the COBOL code that was to call a COBOL subprogram was converted to
JAVA, we ran into a buffer problem where we could only transmit 32756 bytes
to the COBOL subprog from the JAVA code, and worse yet, we could only
receive back 1024 from the COBOL prog to the JAVA prog (very ugly to try to
break the data into 32756/1024 chunks).  The company that sold us the COBOL
to JAVA product has to get this <ahem> little buffer issue resolved, but
until then, we had to do a work around...now we're working on a work around
to the work around...:-).

I don't want to start a thread on how to fix the buffer problem because we
have already beat that to death, I simply mentioned it, so that all had a
better understanding of where we are, and where we've been.

Thanks,

R.S.
        -----Original Message-----
        From:   Lars Appel [SMTP:[log in to unmask]]
        Sent:   Saturday, March 03, 2001 4:06 AM
        To:     [log in to unmask]
        Subject:        Re: Java and MR

        > We are converting ... some COBOL programs to JAVA to do some WEB
voodoo.

        Have you considered to use Java only for the Web Voodoo and retain
        the (slightly modified) COBOL code for the heads-down business code
        and transactions? For example by running the COBOL code as a child
        process of the Java VM or in a separate server job?

        Lars "just a thought"


        PS... I've even been lazy enough to use the telnet protocol to have
        Java code invoke and "remote control" native code programs "behind
the
        scenes". This way, the modifications on the native side were
marginal
        (e.g. no need to add NetIPC or socket routines or somesuch).