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

Joe,
Did you do the DSPJRN command with the keyword/value of ENTTYP(*RCD) or
without the keyword. If not you might try using the keyword/value on your
DSPJRN command and see if you still have and issue.




From: Joe Pluta<joepluta@xxxxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion<midrange-l@xxxxxxxxxxxx>
Date: 03/15/2011 01:18 PM
Subject: DSPJRN OUTPUT(*OUTFILE) and resulting record length
Sent by: midrange-l-bounces@xxxxxxxxxxxx



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