Re: Java as a batch language on System i ?

Hi David,

Sockets are optimal when you aren't guaranteed of always running
ON the System i.

I don't really have any problems with your statement, but the thread
title I saw was "Java as a batch language on System i ?" and I answered in
that context. So, I stand by my statement, in that context. And I would
advise the original requester (remembering that free advice is guaranteed
to be worth what you paid for it) to keep context and needs in focus when
trying to decide if Java is appropriate for his purpose.

I figured out a long time ago that there are typically multiple
"efficiencies" involved in a project, and that a large part of my value,
possibly the single largest, is choosing those most important to the
specific project. If a goal of the project is running on multiple,
possibly disparate, machines, OK, but in a typical batch processing
environment, I, to repeat myself, wouldn't add Yet Another Layer.

If you or anyone else wants to discuss that further, let's do it on a
separate thread, and focus on the stated need on this one, please.

I would also endorse data queue's for this purpose ... but they have
some of their own bugaboos.

I also agree with that. I tend to use native messaging instead.
However, since most people on this list are hot on data queues, I haven't
seen the point in arguing about it.


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: "David Gibbs" <david@xxxxxxxxxxxx>
To: "Java Programming on and around the iSeries / AS400"
<java400-l@xxxxxxxxxxxx>
Sent: Thursday, March 20, 2008 8:22 AM
Subject: Re: Java as a batch language on System i ?

Joe Sam Shirah wrote:

although I'd be very surprised if sockets were optimal, for the same
reasons
that a type 2 JDBC driver typically outperforms a type 4: TCP/IP ends up
being another Yet Another layer.

Sockets are optimal when you aren't guaranteed of always running ON the
System i. My server run's on the System i, but it can also run on a PC
or *nix box near the system (in some cases it's not even near the
system, but that's a different story). Sockets to connect an RPG app to
a java app is a very efficient and performant (is that a word?) mechanism.

I would also endorse data queue's for this purpose ... but they have
some of their own bugaboos.

david