🚀 go-pugleaf

I know of no one else other than PL/I that actually uses dummy sections, but
the idea is twofold. One is to provide a common data area that can be accessed
by all subroutine, assuming that the address of the data area is always passed
as a parameter or otherwise accessible. A-cons and the like aren't very useful
for programs invoked with LOAD, LINK, and XCTL, for example.
The second apsect is the ability to tailor the actual data area to the options,
features, components, or whatever of the implementation actually being used,
and to insulate against changes. For example, suppose a DCB for an audit file
was placed in a data area, and the size of the DCB was expanded in a later
release of OS. Simply recompiling the routine that allocated the common area
would be sufficient, as opposed to all of the components.