We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
DB2 z/OS security; hide install SYSADM and SYSOPR from DSNZPARM; use RACF instead
In DB2 z/OS, no group and/or userids are more powerful than the Install SYSADM and to no small degree the Install SYSOPR.
Yet, these userids and/or groups are easily found by anyone having access to a db2 subsystem and knowing the existance of DSNZPARM. Loading that module in storage from a hlq.SDSNEXIT will show a list of userids and/or groups a hacker would like to know.
If using DB2/RACF security, I propose that two things should happen to support this proposal:
RACF/DB2 should allow class DSNADM to have some new SYSADM and SYSOPR types like:
ssid.userid.INSTALLSYSADM1 (userid or group)
ssid.userid.INSTALLSYSADM2 (userid or group)
ssid.userid.INSTALLSYSOPR1 (userid or group)
ssid.userid.INSTALLSYSOPR2 (userid or group)
DSNTIJUZ when assembling macro DSN6SPRM should have some new features
if SYSADM, SYSADM2, SYSOPR1, SYSOPR2 have non-blank values it should generate a mnote 4 ... perhaps with a warning to see security manual for how they could be converted to a entry in class DSNADM.
And the DB2 subsystem, seeing blank values, should try to find the install sysadm or install sysopr userid/group names in RACF class DSNADM instead of allowing anyone to find them in DSNZPARM.
Do not place IBM confidential, company confidential, or personal information into any field.