Thanks chuck. I will use that technique.

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of CRPence
Sent: Saturday, August 30, 2008 11:56 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: comparing varlen field error RNQ0115 question

The OUTFILFMT and the default ENTDTALEN(*OUTFILFMT) defines the
default length. Using ENTDTALEN(*CALC) defers to the DSPJRN to make the
decision. If the largest size is required [e.g. for consistency], then
specify the desired numeric length value for the ENTDTALEN() parameter,
instead of using any of the special values. And for storage concerns,
even that field can be Variable Length, by specifying the special value
*VARLEN, again with choice of *CALC or the explicitly specified length
and even the allocated length.

Regards, Chuck

tim wrote:
<<SNIP>>

I ran into one more unforeseen issue in the "journal logging"
process. When using the DSPJRN command to dump a journal to a PF,
the JOESD field in the dumped file will change in length based
on the journal entries. I had to created this file first with the
largest known size, then run the process.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].