The ECB is in Fixed CSA running under a different Address space for some reason even after posted the task is still not dispatched I know this because I have placed a WTO right after I am running under TESTAUTH and can observe the ECB before with the 80 bit and the RB and after with 40 bit using TASID with the storage view function
Sent from Mail for Windows 10 From: Peter Relson Sent: Monday, March 19, 2018 6:17 PM To: [email protected] Subject: Re: Using Pseudo Post It is not a "Pseudo Post", it is a "Quick Post". It does not "eliminate the requirement to use the CS instruction", as the example clearly shows it using CS. If you have addressability to the ECB, you can use this. If you do not, you cannot. This has nothing to do with swappability (although if you have cross-memory access to another address space, then that address space is required to be non-swappable). Usually you will not have addressability to a different address space's private storage and thus must use cross-memory post (i.e, POST with ASCB) OR, better, IEAMSXMP (as provided via OA49677). Unless you can guarantee that your target space cannot terminate and that the ECB is safe to post, most uses of cross-memory post have an intrinsic system integrity flaw that can only be addressed by doing some validation of the intended target address space and task (which XM post cannot do, but which IEAMSXMP can, because it has more information at its disposal). 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 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
