That's interested I worked Lu 6.2 xref and we never had to specify EBCDIC ..only binary
Scott ford www.identityforge.com Tell me and I'll forget; show me and I may remember; involve me and I'll understand. - Chinese Proverb On Jan 18, 2013, at 10:20 AM, Paul Gilmartin <[email protected]> wrote: > On Fri, 18 Jan 2013 15:15:47 +0100, Boris Lenz wrote: >> >> At the risk of not understanding the documentation, I've already tried out >> every possible combination of codepages in the SBDataconn command that I >> could think of, without any success. What's your suggestion for >> SBDataconn? > Did you specify the same conversion at both ends? E.g.: > > quote site sbdataconn=(IBM-1047,ISO8859-1) > locsite sbdataconn=(IBM-1047,ISO8859-1) > > ...? so whatever perversion is introduced at the transmitting end > might be undone at the other. > > I had expected that translation would apply not to the names, > only to the content. I guess that's wrong. > > Also discussed here recently: > > EBCDIC > MODE B > > ... which transmits the data in untranslated binary. I don't know > what happens to data set names. And that combination introduces > spurious 0x40 in RECFM=VB data sets; seems to be no problem > with F or U. > > Walt suggested specifying both names. That might not play well > with MPUT/MGET. > > I hate EBCDIC! > > -- gil > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
