My colleague Bob Shannon gave a "PC Routines For Dummies" presentation back in the late 1990s that contains example code and explanations of all the major components involved.
Google confirms that it can still be found on the web. The presentation was written before ASID and LX reuse, so bear that in mind when reading it and composing your own code. It is well worth a read for someone starting out in this area. Rob Scott Lead Developer Rocket Software 77 Fourth Avenue . Suite 100 . Waltham . MA 02451-1468 . USA Tel: +1.781.684.2305 Email: [email protected] Web: www.rocketsoftware.com -----Original Message----- From: IBM Mainframe Assembler List [mailto:[email protected]] On Behalf Of Farley, Peter x23353 Sent: 21 May 2014 13:50 To: [email protected] Subject: Re: Program Call Vs SVC PC routines are good; OK, I can accept that. But where are the substantial examples of how to properly set up and use them, showing all of the benefits Rob Scott listed below and the other sterling attributes of PC routines which have been mentioned here in the past? I know that ISV's cannot (and should not) reveal proprietary code, but perhaps a generalized example (with set up instructions, please!) of some simple function (an adding machine example comes to mind) from experienced developers on this list would help to train the rest of us in how to use this facility correctly and effectively. The CBT index (File 001) is not entirely useful in searching for such examples. Does anyone here know if the CBT collection has a substantial example (or any example at all) of code using PC? Peter -----Original Message----- From: IBM Mainframe Assembler List [mailto:[email protected]] On Behalf Of Rob Scott Sent: Tuesday, May 20, 2014 5:59 AM To: [email protected] Subject: Re: Program Call Vs SVC There is also much more flexibility and environmental choice available to a software product that uses PC routines instead of an SVC. Some of the benefits I can think of include : PC routines can be defined to (o) Run in a specific execution key (o) Run with a specific cross-memory environment enabling easy client/server architecture exploitation (o) Only be available to a subset of address spaces in the system PC routines can (if coded correctly) (o) Run in SRB mode (o) Be dynamically inserted and removed from the system safely (o) Reside in private storage -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.
