I long ago coded a CLP which accepted the option plus some variables
to do a variety of static coded actions, according to the option. Odd I
had never thought of using REXX interpret. Nice. Thanks.
I recalled that since the CLP could not handle a variable number of
parameters, that I had coded '&T' [see my "DO" option example later]
which made the following error a bit more obvious to me...
Note that the quoted REXX is not entirely safe, because &T will be
blank for a member with a SRCTYPE of *NONE; thus a syntax error for
evaluation as _'if ="*LIB"'_ Without the quoting, the value replacing
&T is interpreted as a REXX variable; e.g. for a CLP /source type/ it
would evaluate as _'if CLP="*LIB"'_ instead of _'if "CLP"="*LIB"'_ That
is of course unlikely going to be an issue since CLP="CLP" unless a
prior statement gave the variable CLP a value. Regardless...
parm('if &T = "*LIB" then "chgcurlib &N" else "chgcurlib &L"')
should be instead:
parm('if "&T"="*LIB" then "chgcurlib &N" else "chgcurlib &L"')
FWiW I finally found an old system with my CLP. It is slightly
modified here, so hopefully other than the spurious 'else' it can be
compiled. I dropped the CC=ChgCurLib logic and some others, but left a
more complicated example only because I wanted to see how difficult it
was to use the REXX to replace that logic.
My DO option for an effective DMPOBJ needed to dump a specific
member, so I defined an option DO [and some others like CC for ChgCurLib]:
This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact