I am actually looking at a TCP buffer to decide what function is being
executed. There is stuff in the COMMAND (which can be 64k) field after
the blank so we can't stretch the second operand. The length used must
be the length of the =C'' field This is just a short sample. I have some
programs that have to check for many more commands and branch
accordingly. (I did leave out the BE's in my sample since I figured
everyone would understand that.)
Right now, I use the first format, with the =C'' first, but it be much
more handy to use the second format with the =C'' last.
FYI, The 'how' is not as important to me as the ability. The 'CLC:2'
just seems to be the best suggestion right now. Although, I would not
have minded something like: CLC COMMAND(#),=C'OPEN '
Tony Thigpen
-----Original Message -----
From: Rob van der Heij
Sent: 05/23/2012 11:51 AM
On Wed, May 23, 2012 at 3:51 PM, Tony Thigpen<t...@vse2pdf.com> wrote:
Switch CLC operands works, but leaves the code messier.
CLC =C'OPEN ',COMMAND
CLC =C'CLOSE ',COMMAND
CLC =C'TERMINATE ',COMMAND
CLC =C'END ',COMMAND
vs:
CLC:2 COMMAND,=C'OPEN '
CLC:2 COMMAND,=C'CLOSE '
CLC:2 COMMAND,=C'TERMINATE '
CLC:2 COMMAND,=C'END '
Think you stretch it beyond where it breaks. You would not have the
CLC's without intervening tests on the CC so it does not look really
so bad... And I am fairly sure you normally would not want to CLC
the long field with a random section of the literal pool starting at
C'OPEN' :-(
What I would want is CLC:2 to "stretch" the literals to the length of
the field, rather than having me to code it like
CLC COMMAND,=CL(L'COMMAND)'OPEN'
Rob
