HP3000-L Archives

January 1999, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Eric H. Sand" <[log in to unmask]>
Reply To:
Eric H. Sand
Date:
Fri, 22 Jan 1999 19:45:10 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (77 lines)
<In response to Larry in response to Patrick in response to John>

    Please visit the following 2 year old hp3000-l thread regarding
calculating a given time frame via a system variable. I believe it
still holds water...or maybe it just stands the test of time.


http://raven.utc.edu/SCRIPTS/WA.EXE?A2=ind9701B&L=hp3000-l&D=0&H=&T=&O=&F=&P
=24420

                            Eric Sand
                            [log in to unmask]


> -----Original Message-----
> From: Simonsen, Larry [SMTP:[log in to unmask]]
> Sent: Friday, January 22, 1999 5:10 PM
> To:   [log in to unmask]
> Subject:      Re: HPSECOND CI var to go with HPHOUR & HPMINUTE?
>
> If you do this we might as well add the milliseconds.  Some time we will
> need them and while in that area of code go for both.
> ------------------------------------------------------------------------
> Larry Simonsen          Phone: 801-489-2450
> Flowserve Corporation   Fax: 801-491-1750
> PO Box 2200             http://www.flowserve.com
> Springville, UT 84663   e-mail: [log in to unmask]
> ------------------------------------------------------------------------
>
>
> -----Original Message-----
> From:   Patrick Santucci [mailto:[log in to unmask]]
> Sent:   Saturday, January 23, 1999 5:24 AM
> To:     [log in to unmask]
> Subject:        Re: HPSECOND CI var to go with HPHOUR & HPMINUTE?
>
> 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 listeners -- 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

ATOM RSS1 RSS2