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

[CRPence <CRPbottle@xxxxxxxxx>]

On 3/15/11 11:16 AM, Joe Pluta wrote:
> 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. <<SNIP>>

  Since *CALC suggests the DSPJRN should assign the field length 
according to the largest entry-specific data available on the request, 
then perhaps just a simple query of the data for where the 
entry-specific data is too long, in order to review the entry code, 
entry type, job, and the specific data to see which rows effected the 
requirement for the large record length and perhaps also learn\infer 
what caused those entries to be logged within the specified receiver 
range and sequence numbers.?

Regards, Chuck