• Subject: Re: Build Timestamp?
  • From: Francis Lapeyre <flapeyre@xxxxxxxxxxxxxx>
  • Date: Mon, 29 Sep 1997 18:55:18 -0500
  • Organization: Communiqué, Inc. User

Kahn, David wrote:
> 
> Francis Lapeyre (flapeyre@COMMUNIQUE.NET) wrote:
> 
> >Kahn, David wrote:
> >>
> >> The TIME opcode requires a numeric result field. Crazy though it
> >> sounds
> >> you cannot TIME straight into a timestamp field.
> >
> >TIME to a timestamp field works, all right, but only if you have
> V3R7.
> 
> Thanks for the information, Francis. We're still stuck on V3R2 for the
> time being. It does seem as though a timestamp should be a natural
> target for TIME - saves all that messing around. Another
> incompatibility
> between V3R2 and V3R7. Don't tell Dave M .  :-)
> 
> Dave Kahn - TCO, Tengiz, Kazakstan
> =========
> 
> e-mail:  kahn@tengizchevroil.com    (until September 30th)
>          dkahn@cix.compulink.co.uk  (from  October 1st)
> 

David:

You're welcome. We are addressing the need to go from V3R2 on our
development box to a RISC machine at V3R7, or higher. There are things
you can do in full-blown V3R7 RPG IV that just don't work under V3R2. We
are forced to develop in V3R2, although our main production box is at
V3R7 (a 2-way Model 530), and our machine in Australia will soon be
upgraded to V3R7. Since V3R2 is the end of the line as far a CISC goes,
it makes sense to upgrade the development box, rather than bogging down
the users by moving development back to the main production box.

-- 
    Francis Lapeyre                       flapeyre@communique.net
    ____________________________________________________________
   |                                                            |
   |"The probability of life originating from accident is       |
   |comparable to the probability of the Unabridged Dictionary  |
   |resulting from an explosion in a printing factory."         |
   |                                                            |
   | --Prof. Edwin Conklin                                      |
   |____________________________________________________________|

****** Unsolicited commercial e-mail is not tolerated here. *******
****** Senders of such mail do so at their own peril.       *******
****** A copy, complete with header, is forwaded to the     *******
****** originating ISP for action.                          *******

      Opinions are my own. Otherwise, they are someone else's.
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MAJORDOMO@midrange.com
|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2021 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.