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

I seem to have purged some commentary about "internal entries" from my earlier reply, apparently since I had forgotten how they would be included. I think you will want to specify INCHIDENT(*YES) to "Include hidden entries" to determine if one of those entries might be at fault for the large calculated record length. Review the help text on that parameter to infer how specifying *YES might assist.

Regards, Chuck

On 3/15/11 1:44 PM, Joe Pluta wrote:

Thanks, Chuck, that sounds like a possibility. I did try a few
variations of the ENTDTALEN parameter, but I don't remember seeing
the CPF7064. I'll look for it more carefully. I've run out of
sleuthing time for today. :)

On 3/15/11 12:36 PM, Joe Pluta wrote:

No entry in the log has a prohibitively large value in JOENTL -
the largest value is 4577. I don't know how else to determine
which record is actually too long.

Use ENTDTALEN(4452) and a new output file, then refer to the
"first sequence number truncated" details of the message CPF7064 if
logged as a diagnostic. Perhaps repeat the DSPJRN with a value of
plus\minus a few as the specified ENTDTALEN() for a new output file
if the already known\suspected largest [at 4577] is diagnosed or
none were diagnosed. If an entry sequence number is identified with
that technique, review that specific entry with DSPJRN to the
display instead of the output file, to see what might be odd.