Re: DSPJRN OUTPUT(*OUTFILE) and resulting record length

Joe,



Not sure what is up with the record length issue, but check out EXPJRNE at
http://www.tools400.de/English/english.html



The output file it creates breaks up the JOESD field into the actual fields
from the original journaled file.



Hope this helps.



Richard







From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Joe Pluta
Sent: Tuesday, March 15, 2011 2:16 PM
To: Midrange Systems Technical Discussion
Subject: DSPJRN OUTPUT(*OUTFILE) and resulting record length



A couple of parameters in the DSPJRN command (OUTFILFMT and ENDDTALEN)
control the size of the JOESD field in the output of the DSPJRN
command. JOESD is what actually contains the data in type R entries:
actual file I/O like writes and updates. I have a command that does a
DSPJRN to an output file with OUTFILFMT(*TYPE1) and ENDDTALEN(*CALC).
This has worked wonderfully up until now, but suddenly today I started
getting failures because the data length was too long. Something
started causing records with a JOESD of 32641 to be added. The real
downside is that DBU can no longer handle the records. For those
unfamiliar with DBU, when you use DBU to view the output file from
DSPJRN, it now only shows the journal fields, but it also breaks up the
JOESD field based on the format of the journaled file. It's very, very
cool.

I can truncate the data to make sure that I don't get this error (I've
done that and it seems to work just fine), but I'd like to know what
caused it. Anybody have any idea how to tell which journal entry caused
the huge record length to be calculated?

Joe
--