On Mon, 17 Dec 2007 07:51:56 -0500 "Logan, David" <[EMAIL PROTECTED]> 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. The client only needs to issue an ATSET, which does require authorization. :>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. Depends on how you define the PC. It can be defined as requiring supervisor state/system key, or acceptable in problem state. It can be defined as switching to supervisor state, or staying in problem state. Look carefully at the ETDEF operands. -- Binyamin Dissen <[EMAIL PROTECTED]> http://www.dissensoftware.com Director, Dissen Software, Bar & Grill - Israel Should you use the mailblocks package and expect a response from me, you should preauthorize the dissensoftware.com domain. I very rarely bother responding to challenge/response systems, especially those from irresponsible companies. ---------------------------------------------------------------------- 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
