× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. March 2011

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

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. :)

Joe

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.

Regards, Chuck


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.