RE: Re: GCIC Fullscreen applications - Update

Hi Paul  - Mr. BFN
And everybody else as well.
 
I implemented  the CRLF and LF per your suggestion. Works fine.
But ... I keep running into new issues -
TAB character ---
 
Normal files work fine.
However the "C" program that I choose as one of the test cases has lots of
TAB x''05' Ebcidic in the data.
 
Our version of  IND$FILE routine brings that to the MF as HEX '05' which is
proper.
 
But the EDIT routine treats that as a binary non-displayable character. My
version of XEDIT works the same way. No tabs.
Same for the BROWSE  routine.
 
Currenty I cannot do CH /x'05'/     /
Forgot or more likely too Lazy and did not add the "x" funtion in the CH
command. or the F command
 
I have three options as I see it. Need a suggestion.
 
A) leave the file transfer as is:  and fix the change routine - so that it
can be fixed via XEDIT change - That is doable. My version of X-EDIT works
that way.
 
B) Add a parameter to the FT transfer (on the host FT screen)   TAB=nn and
then during the transfer convert them
  (that would change the file from the original) I have neve seen that
solution anywhere. Would only affect the HOST SIDE.
  But I would probably have to eventually fix the F and CH to work with
ch/x'  ' in  any case as well.
 
C) Add a  set parameter to the EDIT & Browse function "TAB=n" and just
display the Shift with out changing the data.
 
That would be easy for the Browser but extremely complicated for the editior
- Would affect SHIFT and TRUNC and all CH Funtions. 
Even simple line edition would be affected.
Since what you see displayed would not actually be what is in the data. Also
would have to limit that to variable Files. Very complicated.
 
 
Easiest is Option "B" but a very unique solution.
 
Next and what I favor is:
Option "A" for the editor and  
Option  "C" for the browser and a fix to find hex as well in the browser. 
 
Option "C" for the editor is an awful lot of work and not really necessary.
Older versions of X-EDIT. all the ones I am familiar with. do not display it
correctly either. But they allow OPTION "B". 
 
Not familiar with  the latest X-EDIT but I think it has an internal
translate table and you can define how to DISPLAY every character
 
Suggestion Please
 
Roc
 
 
 


  _____  

From: [email protected] [mailto:[email protected]] On Behalf Of
kerravon86
Sent: Monday, September 06, 2010 23:51 
To: [email protected]
Subject: [H390-VM] Re: GCIC Fullscreen applications - Update


  

--- In [email protected] <mailto:H390-VM%40yahoogroups.com> , "Rocky"
<rocsystems@...> wrote:
>
> Should I use the IBM logic or can I enhnace it by recognizing 
> an LF or CR as an end of line as well.

I'd vote for recognizing both LF and CRLF as line
terminators, the only two formats I've ever seen
in the real world.

In PDPCLIB for MSDOS/Windows I do the same thing,
ie a lot of effort to optimize the search for the
LF or CRLF terminator. (I used a LF sentinel so
that I could just search for LF before checking
for CR).

BFN. Paul.