RE: Re: GCIC Fullscreen applications Replace algorythm

Mike wrote: 

             A1234567xMVCxxxFOO,BARxxxxxxxxxxxMOVExxxTOxxxxFOO
	
	and c/FOO/ZOPPER/ is entered, I would expect to see :
	
	A1234567xMVCxxxZOPPER,BARxxxxxxxxxxxMOVExxxTOxxxxFOO

Ok that is also doable - I would rather see:
            A1234567xMVCxxxZOPPER,BARxxxxxxxxxMOVExxxTOxxxxFOO

But that is why I asked for the agorythm

I accept  the majority  consensus of shifting the entire line - Much easier
for me.
Now as to the TRUNC  position -

I will set the zone arbitrarily as Paolo suggested.
With the modification that I will default it by file type or lrecl and the
user can change it.

For Variable length records the default trunc will be current LRECL+100 -
that will also be the max LRECL that you can edit to.

I have an issue with variable length records because I build a fixed table
in memory based on the LRECL

But I will build the table the size for variable records as LRECL + 100 and
fill the extra positions with NULLS
That way you will be able to make the record lareger by at least 100
positions durng editing.
And I will rewrite with the new lengths

There is one variable length exec file out there with an LRECL of 3  (I
created  it with just the characters JKL with EDIT)
Can't make it bigger currently.

For type Assembler I will set the default trunc to 72 as in most editors -
that will keep the continuation lines in proper positions
For all other filetypes that are fixed I will set the default trunc to 80

If the fields are not the same length the entire record will be shifted up
to the TRUNC or from the TRUNC position.

If I have to shift out anything other than blanks that will cause an eror
message and nothing will happen to that record
The message will means that you have to do a search and look at it manually.

If not good enough then come up with a specific alternative or forever hold
your peace.
If you don’t get what you expect that will be a  feature and not a BUG.

Are we all agreed?

Roc



  


________________________________

	From: [email protected] [mailto:[email protected]] On
Behalf Of Mike Stramba
	Sent: Monday, August 09, 2010 12:56 
	To: [email protected]
	Subject: Re: [H390-VM] Re: GCIC Fullscreen applications Replace
algorythm
	
	
	  

	On 8/9/10, Martin Trübner <[email protected]
<mailto:Martin%40pi-sysprog.de> > wrote:
	> I do not like the idea of doing something based on filetype....It
is
	> tricky enough to use it in setting XEDIT-behavior but a change in
	> command-behavior...
	
	I agree, keep it simple
	
	If the line is :
	
	A1234567xMVCxxxFOO,BARxxxxxxxxxxxMOVExxxTOxxxxFOO
	
	and c/FOO/ZOPPER/ is entered, I would expect to see :
	
	A1234567xMVCxxxZOPPER,BARxxxxxxxxxxxMOVExxxTOxxxxFOO
	
	^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
	All these blanks
	remain the same that they were
	
	If a C/short/VeryLongStringToReplaceThePreviousShortString/
	
	is entered, and that results in comments .. whatever getting shifted
	past col 72 (or prefereably the editor TRUNC setting ( :) ), then
the
	line is truncated.
	
	Trying to auto-wrap .. auto format is of course possible (what isn't
?
	;)), but needlessly complex
	
	> a change as you are suggesting could easy be done using same
	> length strings... CH / MVC / PACK /
	
	Yes, another good, simple solution :)
	
	> @Paolo
	>
	>>> and eliminating extra blanks would be a plus (an improvement
over
	>>> XEDIT).
	>
	> Well, I am an XEDIT bigot and I answer: use "zone" command and you
have
	> that in XEDIT.
	
	Dunno what "zone" does, will have to look up the Xedit commands.