Wayne Driscoll wrote:
Bob, thanks, but I guess I need to dig deeper into the REXX manuals. I haven't done a ton of REXX work in years, except for some IPCS stuff, and this one has me stumped. The token contains an address and other data. I was expecting that REXX(TOKEN(VAR)) would behave similar to REXX(STORAGE(VAR)) does in the evaluate and set the variable to an external format, since it doesn't, I need to find the REXX function to get it into this format.
I'll defer to many who contribute to IBM-MAIN and use REXX more than I do to help with the conversion. We'll add something like a FORMATTED (always as hexadecimal digits) versus UNFORMATTED (current default) option to the wish list for improving the NAMETOKN subcommand. It would, as you suggest, make it easier to use NAMETOKN in situations like you describe and would make it feasible to use NAMETOKN reliably in a CLIST. That said, we never know when priority activities will lighten enough to pursue items on the wish list. Do polish your REXX skills and get it working with REXX builtins.
Bob Wright - MVS Service Aids ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
