I would have used the HPDATETIME variable and split it into two values (DATE and TIME). Removes the problem noted by Roy.

regards,
Robert W.Mills


On 7 Sep 2013, at 06:00 PM, Roy Brown <[log in to unmask]> wrote:

> In message <[log in to unmask]>, Alan Yeo <[log in to unmask]> writing at 10:31:28 in his/her local time opines:-
> 
> <Snip original problem description from
>> Just in case it helps I noticed that you thought that is was streamed at 00:00:03  but looking at your original post
>> 
>>> !
>>> !COMMENT
>>> !COMMENT ### JOB submission ###
>>> !COMMENT           JOB Name: MEAC1307,JOBBER.HARTLYNE
>>> !COMMENT        Streamed at: 20130731000000300
>> 
>> This I thing shows that it was streamed at 00:00:00 + 300ms
>> 
>> is it possible that you have some code that is testing the time and is treating 00:00:00 as equal to something or not greater, or is doing a calculation on zero. I'll bet its a once in a blue moon occasion that at a month end something hits that less than 1 second slot when hh:mm:ss is zero.
> 
> Hmmm.
> 
> Non-atomic time/date retrieval?
> 
> Get the time = 23:59:59:999
> (Midnight happens)
> Get the date= 07/31/2013
> Help! I'm late! Gotta run!
> -- 
> Roy Brown        'Have nothing in your houses that you do not know to be
> Kelmscott Ltd     useful, or believe to be beautiful'  William Morris
> 
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *