× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: testing a batch RPG pgm which uses the TIME opcode
  • From: bmorris@xxxxxxxxxx
  • Date: Fri, 25 Aug 2000 15:06:21 -0400
  • Importance: Normal


>Date: Fri, 25 Aug 2000 10:57:26 -0400
>From: "Stone, Joel" <StoneJ@GourmetAward.com>
>
>3)  The RPG pgm uses the TIME opcode to time-stamp fields in the
>records.  Since the old version and new version run a few seconds
>apart, none of the output records ever match.  Is there a way to
>force the TIME opcode to return a constant value in a job so the
>timestamp fields will match when running CMPPFM??

Joel, you can't change how TIME works, but you can change your own
program to get a constant result in your timestamp:
   /IF DEFINED(CONSTANT_TIME)
  C         EVAL    timestamp = Z'2000-08-23-12.00.00.000000'
   /ELSE
  C         TIME                 timestamp
   /ENDIF
When you want to do your testing, compile your RPG program with
DEFINE(CONSTANT_TIME).


Another way would be to use a trigger program.

Barbara Morris


+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

This mailing list archive is Copyright 1997-2024 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.