Be aware that what you are attempting to do is dangerous and has the
potential to create system integrity exposures that would allow a
problem state program to cause a system failure. I am not saying that
it can not be done safely, because it can be. But to do it safely
without creating a system integrity exposure requires a lot more than
just using RSAPF=YES on the ATTACH.
On 5/15/2017 3:17 AM, Robin Atwood wrote:
Conditions 1 and 2 seem mutually exclusive. I tried coding MODESET MODE=SUP
and adding SM=PROB,KEY=PROP
to the ATTACH but it made no difference. I seem to be missing something
fairly massive here! Can anyone shed some light on this?
You need to get into key 0 and reset JSCBAUTH prior to issuing the
ATTACH in order to meet qualification #2 below for RSAPF=YES to be
performed, and the ATTACH must then be issued in either a system key or
supervisor state (or both)-
RSAPF=YES when these conditions are met:
- The caller is running in supervisor state, system key (0-7), or
both
- The caller is running non-APF authorized
- The subtask is attached in the problem program state and with a
non-system key.
Regards, Greg
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
