On 2019-04-23, at 06:08:17, Jonathan Scott wrote: > Ref: Your note of Mon, 22 Apr 2019 11:06:34 -0400 > > One way of detecting and preventing the use of self-modifying > code is to use RSECT instead of CSECT for any section which is > intended to be read-only, in which case HLASM will flag a > reentrancy violation if it detects an attempt to store into that > section. > But not, as someone said, if the instruction uses an explicit base register.
> Another is to use the RENT option, which will enable that check > for all control sections. However, as code may deliberately use > CSECT to map initialised work areas, this may not provide > sufficiently fine-grained control. > Wishlist: that dependent USINGs could be enhanced to provide such fine-grained control. -- gil
