journals

Hello everyone,

 

I need opinions.  I have been an RPG programmer for 20 years.   I still see
things I've never seen before but this one doesn't make any since to me.

 

I have been programming for a manufacturing company about 1 year now.   The
company had some IBM guy to come in and develop the barcode label and place
the record into production (MAPICS).    Before the label is printed it is
first journaled into a journal with the journal receiver etc....,  then
received from the journal and sent to a program that prints the bar code
label.   

 

Now, I was always taught that journaling was only for backup and recovery
purposes,  which I know what some people will say,  that he designed it this
way incase there was a disaster and the records could be received but,
wasn't there a better way to achieve this.   It appears to me that this way
would be cumbersome,  eat up the DSAD of the machine and he is journaling
the record first  and receiving it back before he prints the label.
Shouldn't he have at least printed the label first before he journaled the
record.   I just want your all's opinion about this design.  Maybe there is
something I don't see here but the journal sequence goes haywire all the
time and we have to reconstruct it.     EVERYBODY, ANYBODY GIVE ME YOUR
THOUGHTS ON THIS?????

 

 

Kathy Carter

Application Developer