RE: testing a batch RPG pgm which uses the TIME opcode

One more option is to create a data area in your test environment.  This
should contain either *CONST or *TIME.  In the RPG program, check for the
data area, if not found default to *TIME.
select
when   PgmCtl = '*CONST'
eval   TimeFld = '01-01-0001.00.00.00.000001'
other
Time              TimeFld
endsl

So when run in test environment, you use the constant else you use the
system time.  If you really want the time stamp of when the record was
written to the file, leave it alone and the DBM will give put in the time
stamp for you, to the nano second.


Christopher K. Bipes    mailto:ChrisB@Cross-Check.com
Sr. Programmer/Analyst  mailto:Chris_Bipes@Yahoo.com
CrossCheck, Inc.        http://www.cross-check.com
6119 State Farm Drive   Phone: 707 586-0551 x 1102
Rohnert Park CA  94928  Fax: 707 586-1884

If consistency is the hobgoblin of little minds, only geniuses work here.
Karen Herbelin - Readers Digest 3/2000

-----Original Message-----
>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??
+---
| 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
+---