This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
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:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
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
Specific links you will want to bookmark for future use
Use RACF resource to control access to DVM JDBC Gateway Server databases
Currently USERID and PASSWORD info needs to be updated and maintained in the DVM AVZDRATH job in order for DVM users to access different DRDA databases. The AVZDRATH job needs to be updated monthly whenever a user’s password changes or when a user’s role changes which subsequently changes whether the user should or should not have DRDA database access.
Sample SYSIN to AVZDRATH job:
** NAME = User1
** NAME = User2
** NAME = User3
** NAME = User99
Rather than DVM Support maintaining security access to DRDA databases via a batch job, it would be better if access to different DRDA databases were controlled through access to a RACF resource (eg. RAVZ AVZDRATH) where access to the resource could be managed by a Security team.
Using a RACF resource to control DRDA database access would:
eliminate the need to update and run the AVZDRATH job every month as users passwords expire.
remove any security exposure having DVM Support maintain IDs and passwords in a batch job.
Satisfy best practices and better streamline roles and responsibilities between DVM Support and Security
Do not place IBM confidential, company confidential, or personal information into any field.