Logan, David wrote:
Apologies, you are right...I was writing from memory, and
mis-remembered. The client needs an AXSET and an ETCON. The only way to
issues AXSET and ETCON seems to be in supervisor state. The only way for
a problem program to gain access to supervisor state code seems to be
via an SVC.
I tried using a system LX, and removed the above setup. I get a S0C2 in
the client. This indicates to me that even WITH a system LX, I still
need an SVC to issue the ATSET and the ETCON.
If this is true, I don't see any way to get around an SVC to allow
clients access to my service.
----------------------<unsnip>---------------------
Make it APF-authorized, then use MODESET to move into and out of
Supervisor state. User SVC's are very easily abused by ingenious
hackers. Remember, not all hackers come from the outside of an organization.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
