Walt,

yep I understand the ramifications. Its a current working in many installations.

Without going to deep ( NDA required ), we collect RACF data from the IRREVX01 
and

build a message that is built in Subpool 231. We check where the command 
originates, i.e.; 

SSI, Operator, Parmlib ..in our experience very few from Operator and parmlib. 
That does mean it wont happen.

We check the SSI , Operator and Parmlib origin also.


My question was what was the best way to determine  where the command 
originated, if it was from

batch or TSO/ISPF…I was in the code looking at a REMOVE/CONNECT issue we had 
and had fixed it ..so in my review I started to 

think about a new technique for above.


Now we are doing:


CVT->ASCB->TSB   this is working fine …


But like I mentioned I am open to a better solution , I don't know all the 
answers, I understand how it works , the issue is basically technique which I 
am always improving.


Regards,

Scott Ford

www.identityforge.com





From: Walt Farrell
Sent: ‎Tuesday‎, ‎February‎ ‎18‎, ‎2014 ‎1‎:‎24‎ ‎PM
To: IBM Mainframe Assembler List





On Tue, 18 Feb 2014 16:53:11 +0000, Sokolsky, Hayim Z. <[email protected]>
wrote:

>In answering Scott's question ... it greatly depends which exit you are in.
>You may not be local to the originating address space.
>

That's a good point, Hayim.

Actually, I think that applies to all the exits that might be associated
with commands. Unless Scott is using that exit on a system he owns, and on
which he knows that the RACF subsystem address space is not running, it's
always possible that the command might be running in the RACF subsystem
address space.

And by the way, Scott, batch and TSO are not the only two choices for where
a RACF command may be issued. They can come from STCs, of course, and they
can also come in from MVS consoles (or via MGCRE in general), from the RACF
parameter library, and over the network via RRSF.

So it would be interesting to know why you care where it came from and what
use you plan to make of the information. It's likely that you've asked the
wrong question, or asked it in slightly the wrong way.

(And, by the way, it's a much more appropriate question (imho) for the
RACF-L list than a list about using assembler language.)

--
Walt

Reply via email to