- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- application programming and NTP
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-10-2005 07:14 AM
тАО08-10-2005 07:14 AM
application programming and NTP
Thanks
Don
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-10-2005 08:23 AM
тАО08-10-2005 08:23 AM
Re: application programming and NTP
The simplest would be to call out to DCL with LIB$DO_COMMAND to submit a batch job to run the SYS$STARTUP:TCPIP$NTP_SHUTDOWN.COM and the SYS$STARTUP:TCPIP$NTP_STARTUP.COM procedures.
Of course if you want to get fancier, you could call the $SNDJBC service directly as well.
Robert
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-10-2005 09:23 AM
тАО08-10-2005 09:23 AM
Re: application programming and NTP
We were looking more for a direct control of NTP as through a system service call to avoid the overhead and more importantly, the time delay of spawning a process as through LIB$SPAWN and the DCL commands.
As we need to continue the application, the call LIB$DO_COMMAND would not be appropriate as it does not return control to the calling program upon completion of the command. Instead, we would use LIB$SPAWN.
Thanks
Don
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-10-2005 09:47 AM
тАО08-10-2005 09:47 AM
Re: application programming and NTP
LIB$SPAWN would work just fine of course -- you might want to try reading through what the TCPIP$NTP_SHUTDOWN and TCPIP$NTP_STARTUP command procedures actually do to see if it is even feasible to find some sort of API call to trigger the same behaviors.
Robert
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-10-2005 09:46 PM
тАО08-10-2005 09:46 PM
Re: application programming and NTP
if I remember, LIB$SPAWN is able to execute dcl command file.
Antonio Vigliotti
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-12-2005 07:34 AM
тАО08-12-2005 07:34 AM
Re: application programming and NTP
Yes, it can. As mentioned above, we were trying not to use it to avoid the time required to spawn another process and run the DCL procedure.
Don
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-12-2005 08:37 AM
тАО08-12-2005 08:37 AM
Re: application programming and NTP
I have been busy dealing with a client problem, so my response is not research as thoroughly as I would like, but I wanted to put a few thoughts in.
First, I would like to point everybody at the RFC for NTP, which is available at the IETF www site at http://www.ietf.org/rfc/rfc1305.txt?number=1305
Doing a quick read of this raises the question of "What time zone is NTP operating in?" Scanning it quickly, the references to multi-time zone sources such as WWV imply (I did not find an explicit reference, but it was a quick scan) the use of UTC (aka GMT, Zulu) as the standard for overall transmissions.
WADR (with all due respect), I suggest that the best procedure is probably to keep the NTP feed on UTC at all times, and change the timezone offset used when the time is converted for printing. IMHO, consistency strongly suggests ignoring local time offsets in logs and using UTC for logs (which is why Air Traffic Control and other applications eschew local time in favor of UTC/GMT/Z). From a systems standpoint, this totally elimates the skew problem.
In the case of changing the formatting, all you need to at the appointed time, if it is not done automatically for you by the system, is do a call to the logical name services to redefine the logical name indicating standard or daylight time.
I hope that this is helpful.
- Bob Gezelter, http://www.rlgsc.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-25-2005 09:58 AM
тАО08-25-2005 09:58 AM
Re: application programming and NTP
Unfortunately our application was designed over a decade ago when we used GOES satelite clock receivers with a customized interface. Our software used standard system service calls to handle the receiver. We now are switching out to NTP and do not want to (cannot) redesign the architecture so we are stuck switching back and forth twice a year to keep the readable TOD clock on local time.
Don