Thanks! Should the doc contain a hint that performance would be improved if the token were doubleword aligned? I looked and looked for such an assertion, and finding none, took it that a character field is a character field is a character field. Why not document as two doublewords, or at least point out that doubleword alignment would be beneficial?
Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Peter Relson Sent: Thursday, October 5, 2017 4:59 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: IEAVPSE parameter question It is fine with z/OS itself if you use the same field for both the input token and the updated token. Whether it works for you will depend on whether you care. Maybe your recovery looks at something that wants to know if you still have the old token vs the updated one. The functionality of IEAVPSE (and the other similar "pause" targets, but not "multi-pause" IEAVPME2 / IEA4PME2): -- does a LM of the token into registers while running in your state and key -- PC's to change state (where the target uses the registers and never looks at the parameter list) -- does a LM into registers of the updated token -- PR's back to your state and key -- STM's to your updated-token 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 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
