Moderators: sysprog, prino, sfan, steve-myers, Tim001
No. Everyone has read access to most system data sets. In this context a system data set is a data set with high level qualifier that is not a user id, though how you can easily determine this I don't know.tsubluh wrote:... What if I need to browse a SYS1.MODGEN macro ? Does that action result in a 913 ? ...
"Allocate" in this context is attempting to allocate a new data set, not allocate an existing data set for ordinary use, even if that use will later cause a S913 ABEND. In other words, DISP=(MOD,...) will cause problems if allocation determines MOD really means NEW.tsubluh wrote:... "...accessing data sets of others, this includes trying to allocate data sets with an HLQ that is not your userid"
Allocate with what DISP=? ...
Yes.RSI01DD wrote:Hi Steve,
I believe I too may have got a 913 while "snooping" through the SYSFAN.MAIN... data sets. Sorry.
As the INTENT was only read, is this really a violation?
Thanks.
Dan
steve-myers wrote:I believe the SYSFAN.MAINUSER data sets are part of the automated user ID management process and the admins regard them as extremely off limits.
steve-myers wrote:I said this before and I will say it again. SYSADM is a user.
steve-myers wrote:The outage at the end of April and extending into May was caused by a user using another user's data to attempt to hide his malfeasance; it fooled the admins for about 5 minutes. Fortunately one of the admins was logged on when this started, otherwise it would not have been possible to assign a root cause to this outage. It did cause the admins to more strictly protect user data. Other than network issues, there have been no z/OS outages since early May.
Return to Dezhi systems: Mainframe
Users browsing this forum: No registered users and 0 guests