Re: Tomcat Startup with SBMJOB -- JAVA400-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: Re: Tomcat Startup with SBMJOB
From: David Gibbs <david@xxxxxxxxxxxx>
Date: Tue, 19 Oct 2004 10:58:42 -0500
List-archive: <http://archive.midrange.com/java400-l>
List-help: <mailto:java400-l-request@midrange.com?subject=help>
List-id: Java Programming on and around the iSeries / AS400 <java400-l.midrange.com>
List-post: <mailto:java400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/java400-l>, <mailto:java400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/java400-l>, <mailto:java400-l-request@midrange.com?subject=unsubscribe>

Chu, Denny wrote:

But when I look into subsystem QBATCH, two jobs are running: QBATCH QSYS SBS .0 DEQW QP0ZSPWT MYUSERID BCI 8.4 PGM-SYSTEM TIMW TEST MYUSERID BCH .0 CMD-QSH TIMW
I expect the Tomcat instance of QP0ZSPWT is running but the submitted job
TEST never ends. It just sits there with TIMW status.

Notice the two different job types? BCH and BCI. The TEST job is a normal OS400 submitted job that is processing the command line you specified. The other job is the actual java process (or, in this case, the qshell process) which has to run in a different environment. I'm sure others can give more technical information as to why the two jobs are necessary.

When your java process ends, it will return control to the submitted job which will end normally.

david

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.