On Thu, 25 Sep 2014 11:43:23 -0400, Farley, Peter x23353 wrote: >Discovered this unpleasant fact today: Editing or Viewing an existing RECFM=VB >UTF-8 file or PDS(E) member uses X'40' for the trailing spaces on screen >(i.e., the part of each record past the end of the actual record contents). > >Editing a new file or PDS(E) member using ASCII or UTF-8 mode uses X'20' for >spaces as expected. > ... >Am I wrong to expect that editing or viewing an existing file or member in >ASCII or UTF-8 mode should consistently use the ASCII/UTF-8 space character >X'20'? > >P.S. - This is on a z/OS V2.1 system. > ISPF Edit is stupid and obsessive concerning trailing spaces. AFAIK, there's no way to add trailing spaces to a record, nor to remove some but not all of them. I'm dismayed but not surprised with what you observe. The hex display should distinguish between blanks present in the line and the area beyond the end of the line. Browse does this well: blanks appear as '40'; nonexistent characters as blank space in the hex display.
BTW, how do non-ASCII UTF-8 characters, code points above 0xFF, appear in the hex display? Does ISPF add a third or fourth line of hex as needed? -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
