Good idea.

Currently in pgmA I have two files - JRNFILE in and ETL-CUST file out.

I was hoping to avoid adding the CUST file itself - it complicates pgm and would only be used for an initial load.


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Richard Casey
Sent: Wednesday, October 03, 2012 10:02 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: make cust file look like a journal record - format

If I've been following this thread correctly, you use DSPJRN to create an
output file and then call pgmA to process that file.

Instead of burning CPU and disk space to create journal records (or journal
look-alikes) for the entire data file, would it be feasible to add the
initial load capability to pgmA?

For example: let's say that pgmA currently goes something like this:
Read journal record from DSPJRN output file
Do something (??) with journal fields (check entry type, etc).
Process data record (the JOESD field in the journal record)
Repeat until end of DSPJRN output file

Would this work:
If initial load,
Read data file
Process data record (same format as JOESD)
Repeat until end of data file
Perform logic shown earlier

Make sense?

Have fun!

This thread ...


Return to Archive home page | Return to MIDRANGE.COM home page