×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
>> Jon, If by "gibberish" you mean human unreadable, then maybe the
un-tar operation went awry. What is the CCSID fo the files? I found it
easy to use EDTF to see all the CCSID's of files in a directory.
Yup - human unreadable. Lots of weird characters and they overlay
each other in the browser window.
I noted in the original post that the files were all viewable in a
5250 screen, no sign of any odd characters, so it didn't occur to me
to check the code page. I had untar'd in PASE and assumed it would
create the files with an appropriate code page - but now that I've
checked I see that you are right and they are code page 37! That
would certainly explain the problem - thanks for the hint.
Now all I have to do is find out why the IBM instructions did not work
in that they created files with the wrong code page.
Thanks for the hint on using EDTF to see all the code pages - I had no
idea it would do that. Not exactly intuitive is it!
Jon Paris
www.Partner400.com
www.SystemiDeveloper.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
