A further discovery - Using the "EA" (Edit ASCII) command from the UDLIST 
display of a Unix File System directory of a copy of exactly the same data does 
NOT use X'40' for trailing (non-existent) spaces, but the expected X'20' 
instead.

So the behavior seems to relate to the file system source of the data; from 
"classic" MVS-type files the unexpected X'40' is used, from HFS/ZFS directories 
the expected X'20' is used.

Possibly fixable, possibly (B/W)AD.  If someone who has authority to report 
bugs wishes to make a report, it would be interesting to hear IBM's response.

Peter

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf 
Of Farley, Peter x23353
Sent: Thursday, September 25, 2014 11:43 AM
To: [email protected]
Subject: ASCII/UTF-8 Edit and View existing file use X'40' for trailing spaces 
on screen?!?!

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.
<Snipped>

--

This message and any attachments are intended only for the use of the addressee 
and may contain information that is privileged and confidential. If the reader 
of the message is not the intended recipient or an authorized representative of 
the intended recipient, you are hereby notified that any dissemination of this 
communication is strictly prohibited. If you have received this communication 
in error, please notify us immediately by e-mail and delete the message and any 
attachments from your system.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to