Re: Date manipulation

docdwarf_at_panix.com
Date: 12/30/03


Date: 29 Dec 2003 18:45:22 -0500

In article <217e491a.0312291438.63031a9f@posting.google.com>,
Richard <riplin@Azonic.co.nz> wrote:
>"Howard Brazee" <howard@brazee.net> wrote
>
>> But you will notice that the code said:
>> DISPLAY 'SIPR702 BEGAN ' FUNCTION CURRENT-DATE (5:2)
>> '/' FUNCTION CURRENT-DATE (7:2)
>> '/' FUNCTION CURRENT-DATE (1:4)
>> ' ' FUNCTION CURRENT-DATE (09:2) hour
>> ':' FUNCTION CURRENT-DATE (11:2)
>> ':' FUNCTION CURRENT-DATE (13:2).
>>
>> Saying when a program starts doesn't happen 1000 times a second.
>
>It does if 'SIPR702' is a sub program CALLed for each transaction.

... and if your Production Review process is such that it allows such a
thing to happen then your organisation deserves everything which might
happen to it.

DD