Paul, The ssvt consists of a header, 256 byte table, and function routines. The 256 byte table can have two meaning sets of values; zero and greater than zero. If the function code is zero, then the sub system is not interested in the function. If the function code is greater than zero then the value becomes an index into the function code routines.
For example, If the 10th byte into the 256 byte table is zero, then this subsystem is not interest in this broadcast message and this subsystem is skipped. If then 10th byte has a one, then the first function routine in the list of function routines in the ssvt is called. If the 10th byte contained a 3, then the third function routine in the list of function routine would be called. Hope this helps, Chip > On Jan 27, 2017, at 18:23, esst...@juno.com <esst...@juno.com> wrote: > > . > > I have been reading the MVS Using The Subsystem Interface > . > I need some clarification on SubSystem Interface (SSI) Function Routines. > These are the function Routines defined by the IEFSSVTI and > IEFSSVT TYPE=REQUEST macros. > . > My understanding is for broadcast requests, the SSI checks every > subsystem to determine if each subsystem is interested in the requested > function. > . > If the SSI finds a subsystem that is interested in the requested broadcast > function the SSI pass control to the respective function routine specified in > the IEFSSVTI macros. > The process is repeated for each subsystem interested in handling the > requested function. > . > . > Is my assessment correct ? > . > . > What is not clear from "MVS Using The Subsystem Interface" is how to exactly > determine if the requested function is to be handled by my subsystem. > . > . > For Example: > I have a member in IEFSSNxx SYS1/PARMLIB for My Subsystem Called ABC1 > it also specifies an INIT Routine (ABCINIT) And a Commmand Prefix as a > prameter. > . > My Subsystem Initialization Routine (ABCINIT) does issues a IEFSSVT > REQUEST=CREATE > to create the SSVT. > The Respective IEFSSVTI macros specify a Function Code of 10 and a Program > called > ABC@CMDS. > . > My understanding is the SSI will invoke my Function Routine (ABC@CMDS) for > Function > Code 10. It is up to MY Routine (ABC@CMDS) to determine if it is interested > in processing > this request code 10. > . > Im trying to determine the recommended methods for determining this. > . > . > I thought Of Defining a System Level Name Token Pair with in My SubSystem > Initialization Routine (ABCINIT). The Name Token would have My SSID embeded > in its name. > . > When My Function Routine (ABC@CMDS) receives control It Constructs the same > Name Token > as the Initialization Routine (ABCINIT) and use the SSID from the SSCVT > pointed to by register 0 > as the SSID embeded in the Name Token. My Function Routine Retrieves the Name > Token- > If Its found This Request should be processed by My Routine. > . > . > Is this a possible method to determining if a Command is to be handled by My > SubSystem ? > . > What Methods do others use ? > . > Thanks In advance > Paul > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
