Skip to Main Content
Cloud Management and AIOps

This is an IBM Automation portal for Cloud Management and AIOps products. 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 (

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 updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Created by Guest
Created on Mar 2, 2023

Allow RACF surrogate authority to be used in the script to define the DB2 database for a DWC running on z/OS

As discussed in case TS012239863, when defining a DB2 for z/OS database it is not necessary to run the SQL (whether it is run as batch job, as a BPXBATCH invocation of a script, or directly as a script under OMVS) under the userid that has SYSADM authority to the DB2,as the job/script can be run via a surrogate user who is allowed to act as the SYSADM, without having to provide the password for the SYSADM user.  This is a requirement for z/OS as the person installing  the DWC may not be allowed to have the SYSADM password but has surrogate authority (via RACF) to use this.  Currently in the properties file used by the script  both the userid and password of the DB2 SYSADM user must be specified (as DB_ADMIN_USER   and DB_ADMIN_USER_PASSWORD) but the DB_ADMIN_USER_PASSWORD should be optional, so that if the script is going to be run with RACF surrogate authority the script will just allow DB2 to make all the necessary definitions.  This works fine for the EQQINDWC sample definition job (provided by z Workload Scheduler in the SEQQSAMP dataset) and a z/OS installation of the DWC requires that EQQINDWC be run prior to the script.  

Idea priority High