Paul, You are in a manual that is discussing cross-memory - it is therefore not talking about PC-cp.
The LXRES macro states that : "The linkage index reservation applies across all linkage tables in the system and remains in effect until one of the following happens: o An LXFRE macro explicitly frees a reserved linkage index. o The cross memory resource ownership task terminates. o The operator re-IPLs the system." As you need an LX for either PC-ss or PC-cp, the above tells you that the TCB that owns the PC routines for your application, be they PC-cp or PC-ss, should remain active for the duration that the PC routines are to be available to clients. All software that sets up PC routines does so under the ownership of a TCB that is long-lasting and persistent - sometimes you see this referred to as the "cross memory resource ownership task". For some software, the CMROT will be the jobstep TCB of the started task (or job) for the server - other software product might just attach a separate "do nothing" task to own the resources. 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 Discussion List [mailto:[email protected]] On Behalf Of [email protected] Sent: 16 December 2013 15:05 To: [email protected] Subject: Space Switch Entry Tables in different Job Step Hi, Im reviewing the > z/OS Extended Addressability Guide - Synchronous Cross Memory Communication - Considerations Before Using Cross Memory - Restrictions Third bullet Only One step of a job can establish ownership of space switch entry tables. Subsequent job steps cannot issue LXRES, AXRES or ETCRE macros. The statement speaks to Space Switching entry tables. So it is my understanding that NON-Space Switching Entry Tables can be owned by a different Job Step. If My understanding is correct I could theoreticly setup Non-Space Switch entry tables and PC routnes in STEP1 and the Space Switching entry tables in a second step. Is My understanding correct ? And if so, what would be the advantage ? As a Systems Porogrammer, who has installed more than my share of program products, I have not seen an IBM nor OEM Product that reserved ENTRY Tables in a different job step than the main job step. Paul D'Angelo ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
