On Thu, 18 Jun 2020 at 13:10, esst...@juno.com <esst...@juno.com> wrote: [...] > To be clear I'm interested in understanding SSI Function Call 08 and > not a Resource Manager. > . > If this function call is defined by a subsystem, the only variables presented > to the function routine are: and SSENASID (ASID of Ending Address Space), > SSENASCB (Address Of Ending Address Space ASCB), > SSENJBNM (Job Name List Pointer) of the SSEN Control Block.
Well you do have the entry values common to all SSI calls, notably the SSCVT entry for your subsystem in R0. > It is my understanding This Function Routine would need to examine some or all > of the above variables in the SSEN Control Block. The Function Routine would > need > to compare these variables against some previously stored values that the > sub-systems > function routine is interested in. > . > These "values of interest" would need to be possibly stored in some common > storage. > My question is how does SSI Function Call 08 determine where the "values of > interest" > are stored ? Or Where they are stored ? [...] > How was this validation coordinated prior to the existence of Name Token > Pairs ? Typically in common storage pointed to by the SSCVT - usually SSCTSUSE or SSCTSUS2. You could do worse than to examine the JES2 source code in module HASCJBTR near label SSIENEOM. In the JES2 case field SSCTSUS2 contains the address of the primary JES2 anchor block in CSA, the HCCT, which then points to pretty much anything needed, including ultimately information about each job/address space that runs under or uses services of that instance of JES2. I don't see a strong case for using name/token services when you already have a pair of pointers owned by the subsystem. I suppose N/T might be useful as a sort of associative memory for finding info about a particular address space that has used your subsystem's services. AFAIK the System Level N/T services are available in any context, and are quite high performing on retrieval. Tony H. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
