From:	SMTP%"RELAY-INFO-VAX@CRVAX.SRI.COM" 29-APR-1994 15:48:49.64
To:	EVERHART
CC:	
Subj:	Universal Time in VMS 6.0

From: shibuya@process.com (Hiroto Shibuya)
X-Newsgroups: comp.os.vms
Subject: Universal Time in VMS 6.0
Message-ID: <1994Apr28.164306.499@process.com>
Date: 28 Apr 94 16:43:06 -0400
Organization: Process Software Corporation
Lines: 60
To: Info-VAX@CRVAX.SRI.COM
X-Gateway-Source-Info: USENET

In OpenVMS 6.1 (may be 6.0 too), I came across the following system 
services.

System_Services

  $ASCUTC

       Converts an absolute time from 128-bit UTC format to an ASCII
       string.

       Format

         SYS$ASCUTC  [timlen] ,timbuf ,[utcadr] ,[cvtflg]
     
  $BINUTC

       Converts an ASCII string to an absolute time value in the 128-bit
       UTC format.

       Format

         SYS$BINUTC  timbuf ,utcadr

  $GETUTC

       Returns the current time in 128-bit UTC format.

       Format

         SYS$GETUTC  utcadr
     
  $NUMUTC_

       Converts an absolute 128-bit binary time into its numeric
       components. The numeric components are returned in local time.

       Format

         SYS$NUMUTC  timbuf ,[utcadr]
     
  $TIMCON

       Converts 128-bit Coordinated Universal Time (UTC) to 64-bit
       system format or 64-bit system format to 128-bit UTC based on
       the value of the convert flag.

       Format

         SYS$TIMCON  [timadr] ,[utcadr] ,cvtflg
     

Lookes like finally VMS clock is going Universal, but are they really
being used?  You would expect that something like SET TIME would have
new qualifier, but I cannot find anything above the system service level
which seems to be using this.  After all, there is no $SETUTC call.  Looks
quite useless at this point.  Anybody have any insight on DEC's plan 
for this?  
--
Hiroto Shibuya
Process Software Corporation