Re: TCP9106 - No response received from NTP server since 7/6 IPL - (2) QTOTNTP server jobs active causing the issue

If the jobs still exist then I would check both of their joblogs to see if
they started the same way.
If they do not exist then you're down to DSPLOG for that job.

TCP has changed how many things autostart. For example an autostart job
entry on one subsystem to another autostart job entry on another
subsystem. If you are in the habit of restoring a subsystem from backup
after an upgrade that could have some stuff start from multiple places.

For example VERY EARLY on in (like back on AS/400's) we used to do this
for fear of an upgrade removing our hundreds of job queue entries on a
subsystem description. However IBM does a good job of not losing these
during an upgrade. But, if you've been doing so for so long that the
subsystem description goes back to V1 or V2 then it cannot update the
subsystem description during an upgrade (there's some little attribute
there which puts a halt to it). We had to recreate it and stop restoring
it after an upgrade and it's no longer been a concern.


Rob Berendt