TimeWarp/3000 will properly handle all the possible date routines from all
languages on the HP 3000, as well as the CI. Here is an example from a
sample COBOL
program that we provide;
:warp turnon +13 years
------------------------------------------------------------------------
TimeWarp Status: (c) SMGA, 1998
TimeWarp Access ... Enabled
TimeWarp Status ... Turned ON (SAT, FEB 4, 2012, 7:34 AM)
Virtual DateTime ... '+13 YEARS'
TRACE mode ... FALSE
------------------------------------------------------------------------
:run cobdate.demo.timewarp
COBOL CURRENT-DATE [2012020407345700-0800]
WHEN COMPILED [1998012011012500-0800]
COBOL CURR-DATE [02/04/12]
COBOL TIME-OF-DAY [07:34:57]
COBOL DATE [120204]
COBOL TIME [07345770]
COBOL JULIAN DAY [12035]
COBOL DAY-OF-WEEK [6]
DATELINE [SAT, FEB 4, 2012, 7:34 AM]
CLOCK/FMTCLOCK [ 7:34 AM]
CALENDAR/FMTCAL [SAT, FEB 4, 2012]
FMTDATE [SAT, FEB 4, 2012, 7:34 AM]
HPDATEF [SAT, FEB 4, 2012 ]
HPTIMEF [ 7:34 AM ]
Check out www.smga3000.com for more information.
shawn
Joe Howell ([log in to unmask]) wrote:
: Recently I retrieved the SETDATE utility from the HP web site to assist
in
: initial testing on a Y2K remediation project . No problem with the
: install, etc. and when I ran it per the instructions it did appear to
: change the date.
: I wrote a small test COBOL program to verify the functionality. The
: results of this test are as follows:
[snip]
: Is there a "Y2K" complient version of this utility, specifically one
which
: will feed the "fake date" to the MOVE FUNCTION CURRENT-DATE utility? Any
: input is appreciated.
The CURRENT-DATE function of COBOL II/iX does not use the CALENDAR
intrinsic, so it is not affected by SETDATE.
I haven't used SETDATE, but I suspect it also wouldn't work with
the C/iX or POSIX/iX date and time functions, nor with the TIME
function in FORTRAN 77/iX.
Walter Murray
Hewlett-Packard
Support Technology Lab
|
