Yes but -
Many of these files have millions of records in them - that is a lot of wasted disk space I would think - even if only for the several days we keep journals around.
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Monnier, Gary
Sent: Monday, October 01, 2012 1:12 PM
To: Midrange Systems Technical Discussion
Subject: RE: make cust file look like a journal record - format
All you have to do is write a program that reads then updates the file in question. An RPG program that just reads and updates the file might be faster than an SQL script.
dow (not %EOF(CUST));
You don't have to change anything but by updating the record you force an entry to the journal where, you state, your program reads the journal changes. No change to your ETL are required.
> On 10/1/2012 11:19 AM, Stone, Joel wrote:
I have pgmA which reads cust journal changes and sends them off for
I would also like to be able to send the entire cust file using the
pgmA with no changes.
How can I make the cust record format look just like a journal
(the format that DSPJRN creates).
Cust file format:
I want this to look like a DSPJRN record so I can use the same pgmA
to load up all CUST records for an initial load.
Text Name Type Length
Length of entry JOENTL S 5
Sequence number JOSEQN S 10
Journal Code JOCODE A 1
Entry Type JOENTT A 2
Date of entry: Job date f JODATE A 6
Time of entry: hour/minut JOTIME S 6
|---------- journal header fields
Name of Job JOJOB A 10
Name of User JOUSER A 10
Number of Job JONBR S 6
Name of Program JOPGM A 10
Name of Object JOOBJ A 10
Entry Specific Data - Var JOESD A 80
<--------------------------------- I want my CUST data here!!
Most of the journal fields can empty - but I want my CUST data to be
in JOESD. Can SQL or OPNQRYF do this?
I think I need to take fields JOENTL thru JOOBJ and initialize those.
Then take all CUST fields CUST.* and string them together (alpha,
packed, > zoned) into the one JOESD field.
Is this possible without using an HLL?