On 1/9/2012 6:56 PM, Steve Comstock wrote:
First: none of the services time, stckconv, convtod produce
or accept as input that is displayable: it all needs some
manipulation.
My reading of the docs is thus (I'm doing this mostly for my
own benefit - it helps me re-think things):
128-bit STCKE value (hmm: that's 16 bytes all by itself:
how does it do that and still return date? never noticed
that before)
It's big enough.
----------------------------
OK, given the mysterious uncertainty of TIME when you
request STCKE, my best strategy may be:
* Get TIME as STCK
* Use STCKCONV to convert this value into time / date
in this format: hhmmssthmiju00 / yyyymmdd
and format these for messages
at end of run,
* Get TIME as STCK
* Use STCKCONV to convert this value into time / date
in this format: hhmmssthmiju00 / yyyymmdd
and format these for messages
* Subtract the starting STCK value from the ending STCK
value to get an interval (these are just 64 bit
integers, which simplifies other parts of my logic)
* Shift the 64-bit interval value 13 bits to the right
to get number microseconds in the interval
13? 63-51=12
* Convert to packed and edit the result
---------
What do you think?
It's better than what you said before.
-- gil
