On Fri, 15 Nov 2024 21:40:01 +0000, Baessler, Derek <[email protected]> wrote:

>This might be more of a Windows question rather than z/OS, but I'll give it a 
>shot here.
>
>This deals with transferring some reports on z/OS (stored in DSORG=PS, 
>RECFM=FBA datasets) to a .txt file on a Windows PC. These datasets have some 
>x'00' bytes on some lines.
>
>On Windows 10, Notepad is able to open and display the files after transfer. 
>It seems to ignore the x'00' bytes or just interpret them as spaces, but the 
>rest of the text in the report is perfectly readable.
>
>On Windows 11, Notepad seems the think the files are encoded in Chinese and 
>they are not displayable.
>
>We can view the files with Visual Studio Code on both Windows 10 and 11. It 
>displays NUL where the x'00' bytes are, but they are otherwise readable in 
>both.
>
>We've tried transferring with both SFTP (Tectia) and FTP. We get the same 
>results with both- the transferred .txt files are readable in Win10 Notepad, 
>but not Win11.
>
>We couldn't find where to convince Notepad on Win11 to display these 
>correctly. Has anyone run into something similar or have any ideas?
>
>The customers that are running into this issue aren't IT people and usually 
>don't have admin rights to install something like VS Code or Notepad++ on 
>their PCs. So allowing them to continue to use standard Windows Notepad would 
>be preferable.
>
>Obviously the best thing to do would be to update the program that's writing 
>these reports on z/OS to not write the x'00' bytes. That program probably 
>hasn't changed in 20+ years more. We could probably do something with 
>DFSORT/ICETOOL as well to replace the x'00' bytes with x'40'. But hoping for a 
>quick setting fix on the Windows 11 side.

https://www.windowsdigitals.com/restore-old-notepad-in-windows-11/

-- 
Dale R. Smith

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

Reply via email to