Skip to Main Content
IBM Data and AI Ideas Portal for Customers


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 updates on 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,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Employees should enter Ideas at https://ideas.ibm.com


Status Delivered
Workspace Db2 for z/OS
Created by Guest
Created on Dec 1, 2016

Profile Table usage request - DSN_PROFILE_ATTRIBUTES

I have created the system tables on which service the use of profiles in DB2. This is basically a service which can be started and stopped with DB2 commands, and can be configured to target threads which are generated by certain users, come from certain locations, run a certain program, etc.
One of these services is the MONITOR THREAD service, in which one can set a threshold for a certain user, so that when the user submits so many processes at the same time, exceeding the threshold, the excess processes threads are queued in DB2 and held until one of the active threads of the user finishes. Then another one of the queued threads is allowed to run, until all the queued threads have cycled through and finished. This would simulate the role of job initiators and the input queue in JES 2, which is what we want to happen.
However, there is a caveat. The amount of threads which can be queued, before they begin to be rejected with a bad sqlcode is the same number as the specified threshold.
For example, if I set the threshold for the authorization id of a certain user to 15 (meaning he is allowed only 15 active processes at any given time) and he submits 35 threads, 15 will run immediately, 15 will be queued and 5 will fail with sqlcode -30041. These 5 failed threads will cause a lot of complaints.
Is there some way to have the queueing amount for a particular authid in the profile setup be different (larger) than the allowed amount to execute. For the situation above, for example, the ideal would be for the threshold to be 10, and the queueing limit to be 100. Important to note this is desired by authid, not by location. If you restrict by location, like an IP address, it will do this, but then you affect every user coming from that location. Also, if you hard code the IP address in the profile tables and the IP address changes, then no dice. Further, to cover every location, one can use *, but then the profile would affect even the local user on the LPAR.
This profile setup table SYSIBM.DSN_PROFILE_ATTRIBUTES has 3 columns in it to specify the type of function you want (such as MONITOR THREAD), the threshold value and another numeric column for more attributes.
These are :
ATTRIBUTE1 VARCHAR(1024) - this is where MONITOR THREAD function type goes
ATTRIBUTE2 INTEGER - this is where the threshold value goes, which is also used as the queue limit when checking by AUTHID
ATTRIBUTE2 FLOAT - unused for MONITOR THREAD, left as null in the table
  • Admin
    Janet Figone
    Reply
    |
    Dec 13, 2019

    This Idea was delivered in APAR PH12041 (SYSTEM PROFILE MONITORING PROFILE SEARCH IMPROVEMENTS).