If your TYPE=ENTRY macro invocations accumulate their parameter data in
a global SETC array then it would be trivial to check for duplicates when
adding entries. The TYPE=FINAL macro invocation would then generate the table
in addition to to doing whatever it currently does.
Regards,Keven
On Sun, Mar 3, 2019 at 8:15 PM -0600, "Jon Perryman" <[email protected]>
wrote:
To me the easiest method is with global variables using a prefix to avoid
variable name collisions. It's been a long time, so you may not be correct but
you can understand the idea.
gblb &(prefix&xcode) defaults to 0 first time aif
(&(prefix&xcode)).error already definedprefix&xcode setb 1
I think (not sure) that LCL variables are dropped when the macro terminates.
This wouldn't help your situation.
Regards, Jon.
On Sunday, March 3, 2019, 2:28:22 PM PST, [email protected] wrote:
Hi,.I construct a table using a set of Macros.
The macro supports four different TYPE fuctions.
I can have a TYPE=INITIAL, TYPE=ENTRY, TYPE=FINAL, and
TYPE=DSECT.
.
TYPE=INITIAL basically sets up pointers to the first entry, last entry,
and a count of the number of entries.
.
TYPE=ENTRY describes the individual elements in the table, each ENTRY
is identified by a four character Transaction Code.
.
I want to know how best to identify a duplicate Transaction Code during Assembly
of the Table.
.
For Example
SV5000XX TYPE=INITIAL
SV5000XX TYPE=ENTRY,XCODE=ABCD,P1=JOB001,P=JOB002,P3=JOB003
SV5000XX TYPE=ENTRY,XCODE=IJKL,P1=JOB021,P=JOB032,P3=JOB043
SV5000XX TYPE=ENTRY,XCODE=ABCD,P1=JOB0AA,P=JOB0BB,P3=JOB0CC
SV5000XX TYPE=FINAL
.
In the above scenario, I would want to flag entry three as a duplicate
XCODE of ABCD during assembly.
.
I want to know how best to identify a duplicate Transaction Code during Assembly
of the Table.
.
Any suggestions - sample conditional assembly code would be best
.
Paul D'Angelo
*
*
*
