The OP’s table is built with multiple macro invocations so a global
SETC variable is required in order for the table to persist from one invocation
to the next.
Keven
On Mon, Mar 4, 2019 at 7:51 PM -0600, "Jon Perryman" <[email protected]>
wrote:
Using GBLC is rarely needed to generate these types of tables (e.g. cics and
IMS definitions).
If you really need the table in a different location, then use LOCTR. Even
generating a different CSECT would work.
Regards, Jon.
On Monday, March 4, 2019, 11:27:15 AM PST, Charles Mills wrote:
Cool! New since I was last writing serious HLASM macros. Also suggested by
someone else. It's a good solution to the stated problem but I think the GBLC
array might be his best solution overall since it would feed directly into
generating the table. It's not elegant -- sequentially searching an unsorted
character array again and again in what is basically an interpreted language --
but it would do the job.
Charles
