>>On Mon, Feb 18, 2013 at 10:32 AM, esst...@juno.com <esst...@juno.com> wrote: >>Rob Scott wrote
>>>(a) The first will have LXRES SYSTEM=YES for the PC-cp - this will be >automatically available to ALL address spaces >>>(b) The second will have LXRES SYSTEM=NO for the other PC-ss routines that >your "selected" address spaces will use >>Its interesting Rob recommended the reservation of two Linkage Indexs. To be fair to our boy Rob, I don't think he's actually advocating using two LXs. He is just pointing out that the scheme you're proposing would *need* two. That's the main reason that almost nobody uses non-system LXs. You need a PC service already connected to a system LX in order to connect the non-system LX to each client address space. And since you would by definition already have a system LX, the non-system LXs would be superfluous. One could argue there are benefits in using non-system LXs but I don't know of anybody that does that. Most long-lived vendor code just gives the server space an AX of 1 and uses a single system LX and pc entry table. No muss, no fuss. That's why IBM ended up having to invent that ASN and LX reuse feature... (topic for another day) -- This email might be from the artist formerly known as CC (or not) You be the judge. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
