I have a shell script that looks like this:
echo Starting Deployment Manager
cd
/QIBM/UserData/WebSphere/Appserver/v7/SametimeWAS/profiles/STSCDMgrProfile/bin
startManager dmgr
echo Starting Node Agent
cd
/QIBM/UserData/WebSphere/Appserver/v7/SametimeWAS/profiles/STSCAppProfile/bin
startNode
echo Starting Sametime Console Server
startServer STConsoleServer
And now it pauses at the "Press ENTER to end terminal session.". I
wouldn't mind seeing the rest of the terminal session data, I just want to
eliminate that pause.
Real output:
Starting Deployment Manager
CPC1221: Job 255127/QEJBSVR/DMGR submitted to job queue QWASJOBQ in
library
QWAS7.
CWNATV00I: Application server dmgr in profile STSCDMgrProfile has started
and
is ready to accept connections on admin port 9060.
Starting Node Agent
CPC1221: Job 255138/QEJBSVR/NODEAGENT submitted to job queue QWASJOBQ in
library QWAS7.
CWNATV01I: Application server nodeagent in profile STSCAppProfile has
started.
Starting Sametime Console Server
CPC1221: Job 255149/QEJBSVR/STCONSOLES submitted to job queue QWASJOBQ in
library QWAS7.
CWNATV01I: Application server STConsoleServer in profile STSCAppProfile
has started.
Press ENTER to end terminal session.
I read something about the following:
ADDENVVAR ENVVAR(QIBM_QSH_CMD_OUTPUT) VALUE(NONE)
MONMSG MSGID(CPFA980) EXEC(DO)
CHGENVVAR ENVVAR(QIBM_QSH_CMD_OUTPUT) VALUE(NONE)
ENDDO
But when I tried that it suppressed everything. Perhaps I can get used to
that. Is that what I should do? Should I be monitoring some other
environment variable, message id or log file generated by the above
instead of reading the screen? Really, all I got when I ran it that way
was
Command ended normally with exit status 0.
which is QSH0005.
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
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.