On Wed, 15 Nov 2023 03:39:00 -0500 John Dravnieks <[email protected]> wrote:
:>The conditional assembly language is very simplistic and one aspect is that
it does NOT rescan. So if you code a SETC variable in a model statement as
the opcode, then that is what it will expect in that variable - just the opcode.
:>If you have extra data in the SETC value - as in this case the operands -
then the assembler will be looking for an opcode of 'SR 15,15' and then you
get the error message.
:>If you want to create an machine instruction with a label, opcode and
operands, each one needs to be in its own SETC variable
:>&label SETC 'label'
:>&opcode SETC 'SR'
:>&operands SETC '15,15'
:>&label &opcode &operands
:>This little snippet will work as expected while this will not
:>&instruction SETC 'label SR 15,15'
:>&instruction
I recall that the operands had to be separate symbols.
It now works with all the operands in one symbol?
Does that also apply to macro calls, i.e.,
&DCBSTUFF SETC 'DSORG=PS,MACRF=GL,LRECL=80'
DCB &DCBSTUFF
?
Is that documented or an unexpected feature?
--
Binyamin Dissen <[email protected]>
http://www.dissensoftware.com
Director, Dissen Software, Bar & Grill - Israel
