Re: Variable Length fields

Œ
Hello Mark,

No limit to overflow.

Standard RGZPFM will do the trick.

Regards,
Simon Coulter.

«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»
«» FlyByNight Software         AS/400 Technical Specialists       «»
«» Eclipse the competition - run your business on an IBM AS/400.  «»
«»                                                                «»
«» Phone: +61 3 9419 0175      Mobile: +61 0411 091 400           «»
«» Fax:   +61 3 9419 0175      mailto: shc@flybynight.com.au      «»
«»                                                                «»
«» Windoze should not be open at Warp speed.                      «»
«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»

Œ-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58
MIME-Version: 1.0
Date: Sun, 09 Apr 2000 17:02:25 -0400
From: "M. Lazarus" <mlazarus@ttec.com>
To: MIDRANGE-L@midrange.com
Reply-To: MIDRANGE-L@midrange.com
Subject: Variable Length fields

Œimon,

At 09:31 AM 4/9/00 +1000, you wrote:
>The system uses about 25 bytes per overflow to track the variable 
>pieces.  There is a
>flag associated with the fixed length part and each overflow part 
>indicating whether
>overflow has occurred and the linkage data is stored with the overflowed 
>part.

  Is there a limit to the number of times a variable length field can 
overflow?


>If many records are fragmented then a reorg is required to fix the 
>fragmentation which will also improve performance.

  Would that be a standard RGZPFM or is there a special command / parm to 
do that?

  -mark