On 09-16-1999, Jonathan de Boyne Pollard wrote to Darren Hamilton
about Os2clu02 & Utc.

JP>  DH> This includes OS/2 Warp v3.0 (FP 40) time and date functions, [...]
JP> 
JP> You have something to look forward to.
JP> 
JP> Not only do the DATE and TIME commands supplied with the 32-bit
JP> CMD command  interpreter display the current timezone and support
JP> the /N  switch (which IBM's documentation describes, you will find, 
JP> but which the 16-bit CMD does not actually implement), but  they
JP> *also* operate correctly when it comes to timezone  support and the
JP> TZ environment variable.  So, too,  incidentally, do the various
JP> date and time sequences in the  PROMPT environment variable.
JP> 
JP> Cut and pasted from another window:
JP> 
JP>         [C:\]ver
JP>         CMD 0.1.14   OS/2 2.40.0
JP>         [C:\]set TZ
JP>         TZ=GMT0BST,M3.5/1,M10.5/1
JP>         [C:\]prompt $D $T $u [$P]
JP>         Wed 1999-09-15 22:18:01 BST [C:\]date /n
JP>         Current date is: Wed 1999-09-15 22:18:01 +0100
JP>         Wed 1999-09-15 22:18:01 BST [C:\]set TZ=EST-10EDT,M10.5,M3.5
JP>         Thu 1999-09-16 07:18:01 EST [C:\]date /n
JP>         Current date is: Thu 1999-09-16 07:18:01 +1000
JP>         Thu 1999-09-16 07:18:02 EST [C:\]set TZ=GMT0BST,M3.5/1,M10.5/1
JP>         Wed 1999-09-15 22:18:02 BST [C:\]date
JP>         Current date is: Wed 1999-09-15 22:18:02 +0100
JP>         Enter a new date:
JP> 
JP>  > JdeBP <
JP> 
JP> --- FleetStreet 1.22 NR
JP>                                                                            
            

Is the 32-bit command interpreter specific to OS/2 v4.0? I tried the
DATE /N command with OS/2 v3.0 (FP 40 and 32-bit CMD.EXE file) and
received an error message:

SYS1036: The system cannot accept the date entered.

Regards,

Darren

Internet e-mail: darrenah@interchange.ubc.ca

 * KWQ/2 1.2i * AMD Athlon: Proof that Intel isn't working hard enough.

--- Maximus/2 3.01