Your requirement was confused by adding "epoch conversion". Sounded
like you expected one routine to decode a BASE64-encoded string (which
in most contexts is 7-bit ASCII as octets) interpret the binary as an
epoch timestamp, and generate displayable EBCDIC characters.
Now its sounds like you're looking a BASE64 encode/decode where the
(presumably) same glyphs are used to represent the base-64 digits are
EBCDIC rather than ASCII character codes. I suppose someone may have
done that, but you would end up with octets that require all 8 bits to
represent the characters, which would be a different goal than the
original ASCII usage.
If you really want the BASE64 encoding to be in EBCDIC characters, and
also a conversion of a binary value to be interpreted and displayed in
EBCDIC, I would think it much more useful to keep these as two
independent routines.
Joel C Ewing
On 3/9/24 00:21, Paul Gilmartin wrote:
On Wed, 6 Mar 2024 09:59:02 +0200, Binyamin Dissen wrote:
Base64 has nothing to do with EBCDIC.
???
It is a means of converting binary data to commonly printable characters
(typically A-Z a-z 0-9 + /) that can then be shipped in a non-binary manner.
To an assembler program it is almost certain to matter whether "A-Z a-z 0-9 + /"
are in ASCII or EBCDIC representation.
A simple duck-duck-go search will show examples. My first C program was a base
64 converter.
On Wed, 6 Mar 2024 06:11:01 +0000 Frank Bonaduce wrote:
:>Hello Folks. Is anyone aware of where one might locate any sample assembler
code, macros or APIs to perform the following:
:>- Base64 Decoding (to EBCDIC)- EPOCH Conversion
:>Thanks in advance for the assistance.� �Frank.
--
Joel C. Ewing
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
