Tony Harminc wrote >That's up to you. You look at the command text and decide if you are >interested. If you want to process only commands prefixed by the >command character you specified, then check for that and ignore >anything that doesn't start with that character.
. . That works fine for Function Code 10, which I only used as an example. If I look at Function Code 8 (End-of-Memory) call there is no command text. Are You saying each function code needs to be determined differently ? Using a different technique ? . Wouldn't the SSCVT have the Target SubSystem ID ? . . Paul D'Angelo ************* ---------- Original Message ---------- From: Tony Harminc <t...@harminc.net> To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Clarification on Recognizing My SubSystem Interface (ssi) Function Rou tines Date: Sat, 28 Jan 2017 01:36:32 -0500 On 27 January 2017 at 19:21, esst...@juno.com <esst...@juno.com> wrote: > 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 ? Yes. > 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. That's up to you. You look at the command text and decide if you are interested. If you want to process only commands prefixed by the command character you specified, then check for that and ignore anything that doesn't start with that character. In that case you would return RC=0 meaning that you are not interested. If you want to process the command, then do so, and return RC=4 to say that you have handled it. Nothing stops you from looking at and acting on commands that don't start with your character, but you can't do a lot of synchronous processing because you will delay the "rightful owner" in getting the command. So if, e.g., you want to notify your mainline program whenever someone issues a certain command, you can do that. There are all kinds of flags available as well as the command text. > 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. Yup. > Im trying to determine the recommended methods for determining this. [talk of name/token pairs] I'm kind of lost here... What are you trying to correlate using the N/T stuff? Just look at the text and do something or don't. If you want only to process commands starting with your character, you might do just as well to use the MODIFY interface, rather than going through the much riskier and difficult setting up of a subsystem, with all the potential of causing problems for other subsystems if you get it wrong. So instead of, say, *mycommand you would use f myprog,mycommand You don't even need APF authorization to do this. Tony H. ---------------------------------------------------------------------- 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
