× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



ok.
can you post more of the error or joblog.

On Mon, Mar 7, 2011 at 10:34 AM, Jason Abreu <
jason.abreu@xxxxxxxxxxxxxxxxxxxx> wrote:

HTTP is up and running. It falls earlier in the job log and starts
successfully. However, HTTP is not required to run Tomcat; Tomcat is a
stand-alone server. I am just using HTTP for simplification for the
end-user, with an AJP bind.

Jason Abreu
Abreu Innovations, Inc.
jason.abreu@xxxxxxxxxxxxxxxxxxxx
http://www.abreuinnovations.com/

On 3/7/2011 9:51 AM, Jack Kingsley wrote:
Sounds like HTTP would be required to be up and running to support the
TOMCAT. I would try and track down the the steps on the joblog to maybe
the
dsplog and see what might be going on. Maybe in this case you need to
wait
a little longer after the 21 save etc to start your tomcat job
submission.

On Mon, Mar 7, 2011 at 9:23 AM, Vern Hamberg<vhamberg@xxxxxxxxxxx>
wrote:

>> Jason

Where are you seeing the CPF1338 error? In a job log? In the system
operator message queue? That almost always means you need to look
earlier in the job log - the "real" errors will be there - these "error
notification" messages are the bane of my existence when supporting our
customers - they think we should know what it's about. NO! You have to
go look for WHAT the error was.

Sorry, just my rant at the start of the week! The rest had better be
better!

Verh

On 3/7/2011 8:09 AM, Jason Abreu wrote:
Apologies, I forgot to mention the error...

I'm getting a generic error:
CPF1338 - Errors occurred on SBMJOB command.

According to DSPLOG:
The HTTP server is starting perfectly fine at 04:06:37, so I am
assuming
that TCP is up and running. The Tomcat job is failing at 04:07:35,
right
between the time the Directory Server and iSeries NetServer are
successfully started.

However, not all TCP servers are started after this error occurs
because
there are login issues afterwards, in the morning. We had to run
"STRHOSTSVR SERVER(*SIGNON *SVRMAP)" manually to allow logins.

Jason Abreu
Abreu Innovations, Inc.
jason.abreu@xxxxxxxxxxxxxxxxxxxx
http://www.abreuinnovations.com/

On 3/7/2011 8:43 AM, Jack Kingsley wrote:
What error are you getting?? How soon after your 21 is completed does
this
run, is the IP stack back active when this is launched.

On Mon, Mar 7, 2011 at 8:05 AM, Jason Abreu<
jason.abreu@xxxxxxxxxxxxxxxxxxxx> wrote:

I have a CL program that I use to define a Custom TCPSRV for starting
Tomcat 6.0.30. When the machine is up and running, the STRTCPSVR
*TOMCAT runs with no errors.
After the machine leaves a restricted state (IPL/ Opt 21 Backup),
however, the command fails and prevents other startup jobs from
running.
Those startup jobs have to manually be executed.

Any ideas why this may occur? I have included my CL code below.

==============================
PGM PARM(&COMMAND)
DCL VAR(&COMMAND) TYPE(*CHAR) LEN(10)
DCL VAR(&JOBNAME) TYPE(*CHAR) LEN(10)
DCL VAR(&QSHCMD) TYPE(*CHAR) LEN(255) +
VALUE('cd /Apache/apache-tomcat-6.0.30/bin;')


IF COND((&COMMAND *EQ '*START')) THEN(DO)
CHGVAR VAR(&JOBNAME) VALUE('STRTOMCAT')
CHGVAR VAR(&QSHCMD) VALUE(&QSHCMD *TCAT './startup.sh')
ENDDO


IF COND((&COMMAND *EQ '*END')) THEN(DO)
CHGVAR VAR(&JOBNAME) VALUE('ENDTOMCAT')
CHGVAR VAR(&QSHCMD) VALUE(&QSHCMD *TCAT
'./shutdown.sh')
ENDDO


OVRDBF FILE(STDOUT) TOFILE(QSYS/QPRINT)
OVRDBF FILE(STDERR) TOFILE(QSYS/QPRINT)

SBMJOB CMD(QSH CMD(&QSHCMD)) JOB(&JOBNAME) +
JOBQ(QSYSNOMAX) USER(TOMCAT) +
MSGQ(QUSRSYS/TOMCAT)

ENDPGM
==============================
--
Jason Abreu
Abreu Innovations, Inc.
jason.abreu@xxxxxxxxxxxxxxxxxxxx
http://www.abreuinnovations.com/
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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.