There's no need to do your own parsing -- as Steve Smith (I think
it was) suggested, check the AINSERT statement: it was designed
for exactly this kind of situation.
Also, the NOCOMPAT(SYSLIST) option sometimes helps for substituted
operands that are a list (like (A,B,C)), but won't help for operands
like A,B,C -- which seems to be your situation.
John Ehrman
(Apologies for the tardy answer -- away for a couple of days.)
(------------------ Referenced Note Follows --------------------)
Date: Thu, 24 Aug 2006 09:52:57 -0400
From: "Thompson, Steve (SCI TW)" <[EMAIL PROTECTED]>
<...snips...>
I am afraid that the problem is what I suspected, and what another
poster suggested, that this (&COND) is handed to the IF macro as a
string and not a "parse-able" line of text (as one would get had the
macro had been coded in open code with what the contents of &COND
are/were).
So I am on my way to writing all my own bit testing rather than calling
another macro to do it.
----------------------------------------------------------------------
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
