AFAIK, HLASM has no such option; I like it, but would prefer that the DROP for a protected register require special unprotect syntax. One issue that needs to be hashed out is how to handle dependent USING..
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Assembler List <[email protected]> on behalf of Binyamin Dissen <[email protected]> Sent: Monday, June 25, 2018 11:49 AM To: [email protected] Subject: An idea I got when researching a bug - warnings when a specific register is changed Since the assembler knows which instructions modify which registers, it would be nice if there was a way to "protect" a register for a code range. Perhaps USING area,Rx,protect Any alteration of the register until the DROP would cause a warning message on the instruction. Or might such an option exist? -- Binyamin Dissen <[email protected]> http://secure-web.cisco.com/1wcxp56lov39qk3BBLtchvV0LQyejkZJTb3QXPT6UZ5cgMXb2w11NN6GsMfCpgwMVqu006ipjTfkW-bo1EQUKjMVDT4RCi5W2XZxsSnfpFtZQ4Vu0x8ib659w2GpkZnChwb8tg1dFfNOcACO_kjATKdPxiH8dsn43YL4HDBWqWUe2fD5nIo01irMs4Alfn9Hv6i_2xUAfqAbOEwu9SQHCBHqp3tfkYuco2P3wpFpPkg4fGjdk2IwvY-4zLIsvvdqIt0YDFV2_631a95AiNomarBcLjbxWFwg-2Yf084wnNNkgslfd-4ues8cIEM8kCJP0VKf9HGboY7XTK1VkcEFYQbDI8qb5fpHPg_X9olULLOJm6sxSJJB0Zx1WN0B7lItLbwTFBfHbYJggcx0d1g8yw_NinenBl__0HJiDn4jA0MgQlwt6BSHkkq0CBgRwanlP/http%3A%2F%2Fwww.dissensoftware.com Director, Dissen Software, Bar & Grill - Israel Should you use the mailblocks package and expect a response from me, you should preauthorize the dissensoftware.com domain. I very rarely bother responding to challenge/response systems, especially those from irresponsible companies.
