Re: Journal receiver problems

[rob@xxxxxxxxx]

Record levels are one prime example as to why you should avoid output files
and use API's instead.  Often IBM will document which output files have
changed with each release with the 'memo to users' for that release.  Just
as sure as spring follows winter, some output file, somewhere, will be
changed.  Check out the following:
http://publib.boulder.ibm.com/html/as400/v5r1/ic2924/info/apis/jc1.htm

Rob Berendt

==================
A smart person learns from their mistakes,
but a wise person learns from OTHER peoples mistakes.


                                                                                
                                         
                    Ron@cpumms.com                                              
                                         
                    Sent by:                   To:     MIDRANGE-L@midrange.com  
                                         
                    owner-midrange-l@mi        cc:                              
                                         
                    drange.com                 Subject:     Journal receiver 
problems                                    
                                                                                
                                         
                                                                                
                                         
                    05/22/01 12:43 PM                                           
                                         
                    Please respond to                                           
                                         
                    MIDRANGE-L                                                  
                                         
                                                                                
                                         
                                                                                
                                         





It appears that IBM changes the output format of the DSPJRN command with
every new release. We have a daily startup routine that displays the
journal to a work file, calls a program that reads the work file and writes
records to a permanent history file that the user can then interogate.
Everything works great until the user upgrades their operating system. Then
we have to delete the daily work file, recreate it, and re-compile the
program that reads it. This isn't hard to do, its just a pain in the neck,
especially since we have hundreds of customers on different releases.

I can't help thinking that I'm missing something. There must be an easier
way. I can't find anything in the DSPJRN command to control this and it
will blow up if there is a file out there that doesnt match the format it
wants to output. If I delete the file each time, the DSPJRN command would
not blow up but the format of the file would change and the follow on RPG
program would blow up.

Is anybody else handling this better?

Ron Hawkins

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---




+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---