> I consider it highly unlikely that those character sequences would occur in > hex data strings.
Well, you're right, assuming by "hex" the OP meant its proper usage, A-F, a-f, 0-9. I've gotten so used to "hex" used to mean "non-print" that I assumed that is what he meant. You may notice other posters suggested uuencode and BASE64, which would be superfluous for true hex. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Paul Gilmartin Sent: Thursday, October 27, 2016 2:10 PM To: [email protected] Subject: Re: Rexx and hex data strings On Thu, 27 Oct 2016 10:43:43 -0700, Charles Mills wrote: > >-----Original Message----- >From: Tony Harminc >Sent: Thursday, October 27, 2016 10:30 AM > >On 27 October 2016 at 12:56, Itschak Mugzach wrote: >> What I am trying to reference a comment block in a rexx program. The >> SOURCELLNIE() function does work, including if program is compiled. >> Still have a problem with some odd number of '/*' or '*/' that may be >> included in the text, but I can manage that by replacing it the >> another pair of characters. > I consider it highly unlikely that those character sequences would occur in hex data strings. >You might do better to safely encode the binary (hex) data using something >like BASE64. This is easy, though it does enlarge the data by a factor of >1.3... ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
