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.
Edit a new PDS member in ASCII or UTF-8 mode (HEX ON to show actual characters)
and you get this, which is good and what you would expect to see:
EDIT TDPEFAR.CBT391.XPDFTEXT(TEMP) - 01.00 Columns 00001 00072
Command ===> Scroll ===> CSR
****** ***************************** Top of Data ******************************
000001 Qwertyuiop Asdfghjkl Zxcvbnm 1234567890-=
576777766724766666662576766623333333333232222222222222222222222222222222
17524959F00134678ABC0A8362ED01234567890DD0000000000000000000000000000000
------------------------------------------------------------------------------
000002 Qwertyuiop Asdfghjkl Zxcvbnm 1234567890-=
576777766724766666662576766623333333333232222222222222222222222222222222
17524959F00134678ABC0A8362ED01234567890DD0000000000000000000000000000000
------------------------------------------------------------------------------
However, edit an existing ASCII or UTF-8 member and you get this, which is
unexpected and IMHO wrong:
EDIT TSOUSER.RECFMV.TEXTFILE (TEST) - 01.02 Columns 00001 00072
Command ===> Scroll ===> CSR
000318 Qwertyuiop Asdfghjkl Zxcvbnm 1234567890-= @@@@@@@@@@@@@@@@@@@@@@@
576777766724766666662576766623333333333232222222244444444444444444444444
17524959F00134678ABC0A8362ED01234567890DD0000000000000000000000000000000
------------------------------------------------------------------------------
000319 @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
444444444444444444444444444444444444444444444444444444444444444444444444
000000000000000000000000000000000000000000000000000000000000000000000000
------------------------------------------------------------------------------
000320 Qwertyuiop Asdfghjkl Zxcvbnm 1234567890-= @@@@@@@@@@@@@@@@@@@@@@@@
576777766724766666662576766623333333333232222222444444444444444444444444
17524959F00134678ABC0A8362ED01234567890DD0000000000000000000000000000000
------------------------------------------------------------------------------
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'?
Peter
P.S. - This is on a z/OS V2.1 system.
--
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
