The confusion is with the PC routine and the server address space. It sounds like the PC was created with ETDEF SSWITCH=NO. In this case, the primary address space is the issuer of the PC call. This means that the PC routine cannot exist in the server address space (must be in LPA or CSA).
If SSWITCH=YES, then the PC routine can be in the server address space (in addition to LPA and CSA). As for the accessing the server buffers, SSWITCH=YES means the PC routine accesses them thru the Primary ASN and SSWITCH=NO means the PC routine accesses them thru the Secondary ASN. I hope this answers your question. Regards, Jon Perryman. ________________________________ From: "esst...@juno.com" <esst...@juno.com> To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Sent: Sat, May 19, 2012 7:53:26 AM Subject: A Curiosity Question I have a PARMLIB Memebr set up as SUBSYS SUBNAME(MYSS) INITRTN(INITRTN1) Now during IPL INITRTN1 executes and basically does three things 1) Load a Connection Services Routine 2) Sets Up the Connection Services Routine as a Non-Space Switching PC routine. 3)Creats a name Token pair to allow calling Address Spaces to retrieve the PC Numbers. The Connection Services Routine basically manages Buffers in a Server Address Space. To the Best of My knowledge the Caling Routines issue a PC instruction to the Connection Services Routine and Not the Address Space containg Buffers. Has anyone seen this implementaion/architecture ? Paul D'Angelo ========================================================================
