Thank you for those words about its having been tested on MVS.
I can of course do the ftp with translation. The only problem I have is that the text files are not localized within the package. That kind of manual operation is error prone. This seems to point to a general problem of distributing something which includes bytecodes and text. It cries out for a general solution for installation that handles some files requiring translation and others not. If we are successful in building something, I know we will have to make it (more) seamless.
Thanks for the prompt response.
- Thom
----------
From: Mike Cowlishaw[SMTP:
[hidden email]]
Sent: Monday, September 08, 1997 11:52 AM
To:
[hidden email]
Subject: NetRexx on 390
NetRexx 1.1 should operate correctly on 390 platforms, with the NetRexx
source files in EBCDIC, etc. It has been tested on the MVS beta.
(It uses the Reader and Writer classes for I/O, which handle 'local code
page to Unicode' translations. Works the same for EBCDIC as for other
platforms.)
For text files from the package .. handle like text files from any
other ASCII source ... e.g., ftp in TEXT mode.
--
Mike Cowlishaw, IBM Fellow, IBM UK Laboratories
http://www2.hursley.ibm.com~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
To unsubscribe from this mailing list ( ibm-netrexx ), please send a note to
[hidden email]
with the following message in the body of the note
unsubscribe ibm-netrexx <e-mail address>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
To unsubscribe from this mailing list ( ibm-netrexx ), please send a note to
[hidden email]
with the following message in the body of the note
unsubscribe ibm-netrexx <e-mail address>
Locked
