While this is more an MVS question (because: Common say subpool
241 ...)
another suggestion which might be as good.
Have you considered key 9. Key nine is the free_for_all storage when
the storage protection override bit is on. That particular bit is on
for z/VSE and z/OS all the time. so ...
Martin wrote
Have you considered key 9. Key nine is the free_for_all storage when the
storage protection override bit is on.
That is an interesting approach
This also gets back to your first statement
While this is more an MVS question (because: Common say subpool
241 ...)
Well yes
Paul,
the only storage key that has the special attribute can be written
from any PSWkey is key 9 (since the bit in on all the time)
the other way round is with PSWkey 0 you can write any key storage.
This is way more powerfull (and dangerous) than an application in key
any0 writing to key 9.
ch /bit in on/bit is on/ .prev_msg 1
--
Martin
Pi_cap_CPU - all you ever need around MWLC/SCRT/CMT in z/VSE
more at http://www.picapcpu.de
On 7/5/2014 6:32 AM, esst...@juno.com wrote:
Well yes this is MVS-ish, And regarding the use of Key 9. Using KEY 9
is interesting however isnt that similiar to using KEY 8. I mention
that because several years ago there was a SHARE presentaion on
security and it frowned upon the use of Key 8
On 7/5/2014 5:30 AM, esst...@juno.com wrote:
I know this has been discussed before ...
I need to obtain storage from Common say subpool 241 ..
I also need non-authorized programs to fetch(access this storage) but not store
(update) tis common storage. Can someone suggest an appropriate storage
I am working in z/VSE, but I know you z/OS guys/gals have been involved
with LE for a longer period so maybe you have been down this road before.
In one vendor product I maintain, I have a mixture of LE/C,
Non-LE/Assembler and LE/enabled Assembler.
I am in the situation where I need to
Tony. In z/os I've done the following:
1) root task attaches non-le asm subtaks.
2) each sub tasks issues pipi with parms for non- main program
3) each sub task saves and reuses its own le token.
4) each sub task call LE program via pipi and passes parms as documented.
I'm not at office, so I
On Sat, 5 Jul 2014 15:51:56 +0200, mar...@pi-sysprog.de wrote:
Paul,
the only storage key that has the special attribute can be written
from any PSWkey is key 9 (since the bit in on all the time)
the other way round is with PSWkey 0 you can write any key storage.
This is way more powerfull (and
On Sat, 5 Jul 2014 12:30:21 GMT esst...@juno.com esst...@juno.com wrote:
:I know this has been discussed before ...
:I need to obtain storage from Common say subpool 241 ..
:I also need non-authorized programs to fetch(access this storage) but not
store (update) tis common storage. Can someone
Thanks, that means that I my thinking is in the right direction.
For the pipi call, do you remember if it was the CEEPIPI(init_sub_dp)
function?
Tony Thigpen
-Original Message -
From: Sam Siegel
Sent: 07/05/2014 01:51 PM
Tony. In z/os I've done the following:
1) root task attaches
Yes it is right direction. Yes it is sub_dp. I can dig out examples on
Monday.
Also, with some planning, sub tasks can also have sub tasks
On Jul 5, 2014 1:21 PM, Tony Thigpen t...@vse2pdf.com wrote:
Thanks, that means that I my thinking is in the right direction.
For the pipi call, do you
Thanks.
Examples are not necessary. I have used dub_dp before. I was just unsure
if I had the right approach.
Tony Thigpen
-Original Message -
From: Sam Siegel
Sent: 07/05/2014 05:30 PM
Yes it is right direction. Yes it is sub_dp. I can dig out examples on
Monday.
Also, with
13 matches
Mail list logo
