I second - er, third - this request! I'll go one step further and
suggest another seconds-based variable: HPSECSTODAY, the number of
seconds since midnight. This would make calculating elapsed times easier
and more precise. Combined with HPMONTH and HPDATE, you could even
calculate elapsed times spanning multiple days! Yes, I know I could do
some of this with HPCONNSECS, but that only works for calculations
during a given job or session. I'm looking for something I could use to
write to a file from multiple jobs/sessions that could be used for
calculating elapsed times between events in those differing
jobs/sessions. Hence my desire for something like HPSECSTODAY. (Ouch,
sorry about that; it sounds awful, doesn't it? Maybe Jeff Vance and CSY
-- or you good listers -- can clean it up for me. It's the concept I'm
interested in, not the name of the variable.)

Patrick

John Korb wrote:
>
> Yup!  Been there, wished for that.  Same reason, too - logging!
>
> John
>
> At 1/22/99 05:19 PM , Mark Bixby wrote:
> >Has anybody else ever wished for an HPSECOND CI variable to go along with the
> >current time-of-day variables HPHOUR and HPMINUTE?
<snip>
> >It seems to me this would be a really easy CI enhancement, given that HPHOUR
> >and HPMINUTE already exist.....

--
Patrick Santucci
Technical Services Analyst
KVI, a division of Seabury & Smith, Inc.
Visit our site! http://www.kvi-ins.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Why is it that when I was young life was complex because
I lacked experience and now that I'm experienced life is
complex because I'm not young?"           - James Trudeau