On Fri, 8 Aug 2014 04:29:20 -0400, Robert A. Rosenberg wrote: > >To do this you need to so the following: > >1) Use a TRT of the EBCDIC input string to verify that all the >characters have valid ASCII codes. The table would have x'00' if the >code can be mapped to ASCII and x'ff' if not. Hitting any of the >x'ff' entries means problems. >2) MVC the string to a workarea and use TR to convert to ASCII (use a >EBCDIC->ASCII Table). >3) Pass the workarea to the routine. >4) The result while EBCDIC should be the same display TEXT as that >put out by the Internet routine. If you need the ASCII version (as >opposed to just displaying it) you need to use the same EBCDIC->ASCII >table as was used in Step 2 above to get the ASCII version of the >Base64 string - IOW: Redo Step 2 moving the Base64 output to the >workarea. > I recommend omitting step (1) because it has no effect on the output.
Does the assembler routine product EBCDIC codes or ASCII? If the latter, omit step (4). (Your presumption of EBCDIC may be unjustified.) For longer inputs, does the assembler routine block with records separated by <LF>, by <CR><LF>, or by RDWs? FTP, SMTP, and HTTP servers with suitable options will perform many of the needed conversions. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
