RE: IPL Startup and Odd Changes?

I have a few lpars. One of my newest ones has very minimal customization. I've not even changed the controlling subsystem, etc.
WRKOBJLCK OBJ(QSYS/QZHQSRVD) OBJTYPE(*PGM)
Job: QZHQSRVD User: QUSER Number: 631361
DSPJOBLOG JOB(631361/QUSER/QZHQSRVD)
Job 631361/QUSER/QZHQSRVD submitted to job queue QSYSNOMAX in QSYS from job 631288/QTCP/QTCPSTSVRS.
DSPJOBLOG JOB(631288/QTCP/QTCPSTSVRS), but the job was already gone.
DSPLOG PERIOD((*AVAIL *BEGIN)) JOB(631288/QTCP/QTCPSTSVRS)
...
Dsplog...
Job 631222/QSYS/QTCPWRK started on 11/19/20 at 08:39:00
Job 631221/QSYS/QTCPCTL started on 11/19/20 at 08:39:00
...
Subsystem QSYSWRK in library QSYS starting.
Job 631228/QSYS/QSYSWRK started on 11/19/20 at 08:39:04
...
Subsystem QSYSWRK started.
Job 631226/QPGMR/QSTRTCP started on 11/19/20 at 08:39:05
...
Job 631311/QPGMR/QSTRUPJD started on 11/19/20 at 08:39:11
...
Job 631314/QSYS/QSERVER started on 11/19/20 at 08:39:11
...

The QTCPCTL job is a 'system' job. It has to be running before you can even do STRTCP.
Basically STRTCP runs BEFORE QSTRUPJD.
crtsrcpf qtemp/qclsrc
dspsysval qstruppgm
RTVCLSRC PGM(QSTRUP) SRCFILE(QTEMP/QCLSRC)
CL source retrieved for *PGM QSTRUP in QSYS.
DSPPFM FILE(QTEMP/QCLSRC) MBR(QSTRUP)
Find . . . . . . . TCP
String not found in file.
So, if it is in your startup, you're starting it up twice! Again, this is not an AS/400!

I'm not yet sure what starts QTCPCTL but you may want to check out
DSPMSGD RANGE(TCP9533) MSGF(QTCPMSG)
As this is in the joblog.



Rob Berendt