× 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.



Rob,

They were both started during the IPL process, set to start when TCP/IP starts.

Job 879597/QNTP/QTOTNTP started on 07/06/17 at 00:33:12 in subsystem QSYSWRK
Job 879598/QNTP/QTOTNTP started on 07/06/17 at 00:33:12 in subsystem QSYSWRK

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rob Berendt
Sent: Tuesday, July 25, 2017 5:57 PM
To: Midrange Systems Technical Discussion
Subject: 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
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: "Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>
To: "'midrange-l@xxxxxxxxxxxx'" <midrange-l@xxxxxxxxxxxx>
Date: 07/25/2017 03:40 PM
Subject: TCP9106 - No response received from NTP server since 7/6
IPL - (2) QTOTNTP server jobs active causing the issue
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



V7R1, Latest CUM and groups.
TCP9106 - No response received from NTP server has been occurring every 3
to 4 hours since 7/6 IPL.
The SNTP (Simple Network Time Protocol Service) is running.
This is only occurring on Production LPAR.
R&D LPAR is fine.
Both LPARS configured equally, both pointed to same remote systems.
Remote system . . . . . . . . . 'us.pool.ntp.org'

+ for more values '198.60.73.8'

When checking the Production LPAR, I found that there were (2) QTOTNTP
server jobs active.
I stopped both, started one new QTOTNTP server job.
Issue resolved.

Why would an IPL have started (2) QTOTNTP server jobs?

Any thoughts from the group.

Thank You
_____
Paul Steinmetz
IBM i Systems Administrator

Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071

610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home

psteinmetz@xxxxxxxxxx
http://www.pencor.com/

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.