I am deeply indebted to both of them.
Luckily, my pc guy, Gary Richtmyer of C&G Web Enterprises had already solved that problem for one of his customers. He volunteered to modify his code to handle the format produced by SysDumpVariables(). That turned out to be a file of 221 lines.
When I found out that ooRexx had the ability to pass the whole variable pool to an external routine via .context~variables, I started this effort on 17 Oct 2015 and, with Gil's help, had it functional by the end of the day! The file is 117 lines.
Call oosysdumpvariables .context~variables , outfile [, width]
width defaults to 15.
If width=0 then expanded_dumpvars.rex will not be executed for the optional validation and hex features, thus CR and LF will be shown as <CR> and <LF>.
Here is the code: ooSysDumpVariables.rex.html
When run from the command line, this is the result: ooSysDumpVariables.rex_help.txt.html
Would Anyone like to explore any of the above in more detail, or have a question?
Its been quite interesting Learning By Example to develop ooSysDumpVariables.
Until the code gets posted on RexxLA.org, it can be requested from me.
Thank you for your attention and participation!