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

[Buck Calabro <buck.calabro@xxxxxxxxxxxxxxxxx>]

Joel Stone wrote:

>I am trying to test a new version 
>of an RPG4 pgm.  I run the old 
>and new pgm versions, then use 
>CMPPFM to compare the output 
>files field by field.
>
>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.  

Don't use TIME.  Build your own function, say, createTimeStamp.  Within it,
hard code a fixed time stamp for the duration of your testing.  When you go
live, use the TIME op code again.  That way you won't have to chase all over
creation replacing TIME with hardcoding and vice versa.

The CMPPFM problems are unpleasant.  I typically use 3 SQL statements:

join where records are in old and new
records in old but not new
records in new but not old

Buck Calabro
Aptis; Albany, NY
"We are what we repeatedly do.
 Excellence, then, is not an act, but a habit." --Aristotle


Billing Concepts Corp., a NASDAQ Listed Company, Symbol: BILL
+---
| 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
+---