Re: What's your favorite way to find out if TCP/IP is started in CL?

My steps after an IPL include:

DSPMSG QSYSOPR ASTLVL(*BASIC)
Look for messages stuck in MSGW.
A popular message is from MXSTARTUP “Collector Communications Error”.
Commonly a reply of R to retry resolves it. I think it jumps the gun
before enough of TCP/IP is running.
I will have this DSPMSG multiple times here. Sometimes answering one
frees up another. Please do it at least as often as directed.
Write down time. __________________

Make sure system is not in restricted state.
WRKSBS
F11=Display system data
Write down status of QCTL __________
If it is RSTD for Restricted then perform orderly shutdown steps and IPL
it again.
WRKSBSJOB QSYSWRK should show numerous jobs.
Write down time. __________________

WRKJOBQ QSYSNOMAX
Write down status (see far upper right, should say RLS/SBS).
__________________
If status is held, release it with RLSJOBQ QSYSNOMAX
(I was finding that sometimes people were holding all job queues before
the IPL.)

PING ‘127.0.0.1’
To verify that TCP/IP is running. Stop until it is. Normally it should
be, unless QSYSNOMAX was held or some such thing.
Write down time. __________________

After many steps I have them record the time. Sometimes it's just to slow
them down enough to get them to actually do it. Sometimes it's
confirmation that they did do it. Sometimes a step, which may only take a
second, can take an hour. For example on the above, if it doesn't work
you could be in the soup because this IPL was because of a unload/reload
and you forgot a lan card.

So, do you want to cover all that in CL?

Rob Berendt