On Tue, 26 Aug 2008 17:49:13 -0500, William H. Blair <[EMAIL PROTECTED]> wrote:
. >In the sense you are speculating about, no. But >obviously it will be somewhat different, because >JES3 code is used instead of JES2. But it's the >same process, basically, and the same SVC (111). > >That disappeared with JES3. It's all now done in >the SAM compatibility interface layer, whose job >is to take the "buffer" from the application who >issued a PUT against their DCB, which causes it >to enter the C/I code which then in turn issues a >PUT against the _real_ ACB that was created. That >ACB PUT using an RPL is what calls the HAM SVC, >for both JES2 and JES3. Eventually, the specific >JESx code gets control. JES2 buffers (both UBUF >and PBUF) are in private, while JES3 buffers are >in common. > Hi Bill, It is not often (maybe never) that I get a chance to correct you. As of z/OS R7 JES2 no longer uses SVC 111. At that release HASCHAM was split into two modules (HASCHAM (unauthorized )and HASCPHAM (authorized) and now uses PC linkage instead of an SVC to get to the authorized part of the code. Nice to hear from you. I have really enjoyed your posts. Doug Henry USBank ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
