I see one of my questions answered, and even with that, not entirely. So with that, let's jump in. I have three:
(1) This one has been partially answered, but what is the *best* way for a problem state program to get XMS authorization to a PC routine in another address space (non-system LX)? I chose using an SVC, but that seems like a HUGE overkill in order to issue two entire macros (ATSET and LXSET.) (2) My PC routine must be in common storage. The manuals indicate that the PC routine can be in private memory of the target address space (PRIMARY, but not HOME). However, if I load my PC routine into private storage, I get an ABEND. It must be in common storage even if my ASCMODE=AR and SSWITCH=YES is specified on my ETDEF. What's up with that? I don't need my routine in common storage, don't want it in common storage. I just can't seem to "PC" to it unless it is in common storage. ----- Those are the two operational questions. Then I ran into a bizarre situation at a customer site when trying to beta this thing that I wrote. I knew that we weren't going to have enough time to contact their systems programming department and get an IPL and a permanent SVC in, so I used the SVCUPDATE macro as part of the intialization routine of the started task. However, it seemed that something under the covers either (a) prevented SVCUPDTE from working, but without any obvious return code, or (b) "reset" the SVC table to a previous value, causing the XMS setup (as described in #1) to fail intermittently. (3) Does anyone know of an MVS security setting, or a third party product that controls the use of SVCUPDTE? I thought once in supervisor state, you were there. Thanks! David Logan ---------------------------------------------------------------------- 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
