Peter, Thanks for the reply. But there is still the second question I asked - Can you say if there is any (near?) future possibility of a PC or SVC interface that would permit application-level code (problem state, non-zero-key) to use the TRAP facility?
Such a facility would make many application-level assembler debugging tools (including and maybe especially the CBT collection) far more efficient and useful than is currently possible via ESTAEX or BAKR/PR methodologies. Peter -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Peter Relson Sent: Tuesday, November 21, 2017 7:55 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ECVTDUCU & "trap" condition in z/OS EXTERNAL: This email originated from outside of Broadridge. Do not click any links or open any attachments unless you trust the sender and know the content is safe. There is no additional documentation and there are no other references because there is no particular need for there to be. If you are using the trap instructions then you know (or need to know) about the trap control block and that the trap instructions architecture requires you to provide information controlling the traps within the dispatchable unit control table (DUCT). This pointer (and the service behind it) was created so that individual trap exploiters would not code these updates themselves because they were more likely to get it wrong than z/OS development is and were more likely not to be in a position to react to architectural changes (such as happened when z/Architecture was introduced) than z/OS development is. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
