Re: OPM PL1 block defn

I do not fully understand what you are trying to do, and therefore my answer
may not be what you are looking for, but ..
IF you want to enable the MI assembler to accept repeated definitions of
symbolic names for variables (having the same length, type, etc. per field
name used)
THEN you can do so by specifying *DUP (in stead of the default *NODUP)
within the option template parameter passed to the QPRCRTPG API (which is
the MI assembler). This will allow duplicate declares of program objects.


>-----Original Message-----
>From: mi400-bounces@xxxxxxxxxxxx [mailto:mi400-bounces@xxxxxxxxxxxx]On
>Behalf Of Bruce Wilson
>Sent: Friday, March 14, 2003 1:51 AM
>To: MI400@xxxxxxxxxxxx
>Subject: [MI400] OPM PL1 block defn
>
>
>Aware that PL1 has a block structure, I am interested that internally it
>is represented by a MSPPTR and then 5 data declarations based on the
>pointer.  What is unusual is that all five of these declarations have
>the same name.
>In the HLL Sym Tbl each has an extension segment which is of normal
>length (26) but contains in the field where the LVL would be on a data
>structure definition the following alpha [in order: AU, ST, EX, PA,
>BA].  Internally the 5 records are chained together - doubly linked
>using the offset from the table start.
>Thus:
>DCL MSPPTR  .BLK@xxx;
>DCL DD *BLK1  CHAR(1) BAS(.BLK@xxx) POS(1) BDRY(16);
>DCL DD *BLK1  CHAR(1) BAS(.BLK@xxx) POS(1) BDRY(16);
>DCL DD *BLK1  CHAR(1) BAS(.BLK@xxx) POS(1) BDRY(16);
>DCL DD *BLK1  CHAR(1) BAS(.BLK@xxx) POS(1) BDRY(16);
>DCL DD  *BLK1 CHAR(1) BAS(.BLK@xxx) POS(1) BDRY(16);
>
>I am not aware that one can assemble an MI program with duplicate
>symbols and the repetitive nature of the above structure for every block
>.. always AU then ST EX PA BA.  While I think use of the HLL option in
>MI would allow one to create the duplicate symbols - the chaining of the
>five records previous/next is a mystery as is what the above structure
>is trying to implement.  Anyone have a 'glimmer' of an idea?
>