Page protection is the most likely thing that is going on. But you need to read the principles of operation. It is very clear on things that can result in PIC 4. Once you have eliminated the cases that do not apply (such as anything to do with storage key), few possibilities will remain.
Most PIC 4's do not set the translation exception ID (which I presume is what "exception address" is in your display). Sometimes the ID is an address. But even when it's an address, the low 12 bits are not part of the address. Thus a translation exception address of 1F004 may apply to an exception anywhere in the 1F000 page. The "004" has architected meaning which you can read. In POP-09 it starts on page 3-71. As Rob Scott mentioned, the DIAGxx CsvRentProtect option would result in the loaded module being in page-protected storage which in turn I will make no direct comment (just an obvious indirect one) on the entire premise of zapping someone else's code to pervert its intent, but you know where I stand. And of course everyone shudders, rightly, over user-written SVCs since a huge percentage of them have system integrity errors. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
