On Wed, Jul 30, 2014 at 7:02 AM, Elardus Engelbrecht <[email protected]> wrote: > John McKown wrote: > >>The code must be addressable by the target address space. z/OS will not do >>this for you. Therefore, do _not_ try to schedule an SRB in a different >>address space which uses code in your private address space. > > Interesting. Just curious, but where is that documented?
Which? That the code needs to be addressable by the target address space? Or that it will not cause it to be addressable? I find it interesting that this information is not where I expected. But I did find this: http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/iea2a2b0/35.1.17 <quote> Note that in this example, the SRB routine is running in a different address space from the scheduling code. To run an SRB routine in a different address space from the scheduling code, the SRB routine must be either in a different program that is accessible from the target address space, or in the common storage together with the scheduling code. </quote> I guess that I just ASSuMEd that z/OS did not try to "copy" something into the target address space. Seems most unlikely to me. But the above certainly _implies_ that it is the responsibility of the issuer of the SCHEDULE to make sure that the routine is addressable in the target address space. > >>You will likely get beat abruptly about the head and shoulders by your >>customers. Especially the sysprogs whose systems you (might) have crashed. > > If the OP survived that far... ;-D > > Survivers wil be promoted to pavement sweeping... > > Groete / Greetings > Elardus Engelbrecht -- There is nothing more pleasant than traveling and meeting new people! Genghis Khan Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
