FWIW, I see things the same as Phil. Either unprotect the register before bumping it, or don't use the feature, or potentially ignore the warning.
Charles -----Original Message----- From: IBM Mainframe Assembler List [mailto:[email protected]] On Behalf Of Phil Smith III Sent: Thursday, June 28, 2018 7:23 AM To: [email protected] Subject: Re: An idea I got when researching a bug - warnings when a specific register is changed Hobart Spitz wrote: >If you are traversing a linked-list of control blocks (e.g.), you might >validly modify a USING register that points to a DSECT of that control >block. Sure, but...so? You'd explicitly unprotect, change, reprotect. That's the whole point. (Or not protect at all; this is optional, after all.) Seriously, not picking a fight, just don't understand whether you're saying "This doesn't work because" or "Note that in cases like this, there'd be some tinkering"?
