Most text editors work by reading the entire file into memory, where you
can then view it, page up and down, and possibly modify (edit) the
contents.. Then, if you choose to "save" the changes, the editor
rewrites the entire file from the copy in memory. This is, in effect
also how SEU works, on a source file member basis. (SEU also has
additional logic to handle a "crashed" session and recover changes made
in a previous SEU session, etc.)
Do you really want to be reading an entire file of 1.5 or 2.3 GB into
memory, just to browse it, or perhaps to make a few small changes?
Are you really "editing" the contents of this file? In what ways?
What kind of data is in this large "text" file? Is it XML?
I just wonder if this is "the best tool for the job"?
There are various Unix commands / tools available in QShell or PASE,
such as "sed" that might also be useful.
Mark S. Waterbury
> On 10/19/2012 10:06 AM, J Franz wrote:
Is there a file editor (prefer i based) that can open and edit large text files
in the IFS?
Somewhere between 1.5 and 2.3 gig the EDTF command returns a "Object is too
large to process"
CPFB620 w/Errno 3525
Notepad and Notepad++ fail.