- DASSXB64 is the Assembler Subroutine for converting between EBCDIC and BASE64. As someone else pointed out, the subroutine =does= do anjavascript:edCloseAllTags(0); intermediate conversion from EBCDIC to ASCII and then to BASE64 because the only doc the person who wrote this could find gave the conversion between ASCII and BASE64. I would have preferred a way to go directly from EBCDIC to BASE64 simply because if any web hackers attempted to unconvert the BASE64 to ASCII, they'd get garbage and not many of the hackers (the 16-to-30-year-old variety anyway) have probably ever heard of EBCDIC. But this one works so we're using it until we get IPCS/Cryptographic processing available (maybe, someday).
- DASWCB64 is the COBOL Copybook layout used by COBOL programs (both CICS and Batch) to pass the values between the caller and the Assembler Subroutine.
- DASWPB64 is a sample of the COBOL code used to set up the data values and CALL the Assembler subroutine for conversion in both directions.
| Attachment | Size |
|---|---|
| DASSXB64.txt | 43.64 KB |
| DASWCB64.txt | 9.05 KB |
| DASWPB64.txt | 2.89 KB |
Hi, I'm interested to use a routine similar to DASSXB64. The flow I would implement is quite different. Inbound flow (FROM64), in DASSXB64, does apply "FX" to an inbound ascii file to obtain the original ascii file, then does apply A2E to convert it in EBCDIC ccsid. I need to make E2A before apply "FX", because my inbound record is EBCDIC.
Similarly, in the "outbound flow" (TO64), in DASSXB64 it does apply firstly the conversion E2A to obtain an ascii file where to use "TX" to make base64 convertion. I need first to use "TX" then convert with A2E. My personal know how on assembler and BASE64 logic/structures is not so good to easily change DASSXB64: may I ask for this change to somebody who wishes to give me this help, pls? May be Derek?
I thank you very much for any kind answer, tks. Franco
