On Wed, 30 Jan 2019 08:08:43 -0500, Peter Relson wrote:
>
>I'll quibble about the very title of this post. I'd say that there is no
>such thing as an external dsect.
>A dsect is just a mapping. What you are talking about is simply an
>external CSECT of DC's for which you provide a DSECT to map.
>
That earns you the right to an RCF. The HLASM Ref. uses "external DSECT"
three times, generally in connection with the DXD instruction.
On Sun, 3 Feb 2019 17:19:42 -0500, Steve Smith wrote:
>Bleah. "Good form" may be in the eye of the beholder. Personally, I see
>very little value in macro keywords that specify if or how to create one
>statement of output. I'd rather they leave it to the programmer to code
>CSECTs, DSECTs, etc. where he wants them.
>
I believe DSECT={YES|NO} is valuable. It saves the programmer not only
one instruction but the need to wrap the macro call in order to use
&SYSLOC LOCTR in order to restore the calling context.
I might prefer SECT={CSECT|DSECT|NONE} to support the programmer's
embedding multiple macros in one data area by entirely suppressing the
CSECT/DSECT instruction.
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
