Skip to Main Content
Cloud Management and AIOps


This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation 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 (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
  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 (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.

Status Future consideration
Created by Guest
Created on Feb 21, 2023

EQQSERVER avoid 878 abend by limiting connections

The EQQSERVER uses memory under 16 MB. If many jobs use the EQQSERVER, we get an S878.

To avoid downtime, the number of concurrent connections must be limited. The server task should reject or queue new incoming connections (e.g. a FIFO queue). To use a queue or reject new connections, a parameter must be introduced in parmlib.

If the maximum number of concurrent connections cannot be determined automatically, a new parameter with the maximum number of connections must also be included in the parmlib.

Idea priority High
  • Admin
    Marco Cardelli
    Reply
    |
    Mar 24, 2023

    We accept the requirement although we don't think that allowing a limit to the number of the connections is the proper solution. We will design a solution at implementation time.

  • Guest
    Reply
    |
    Feb 27, 2023

    Hello Marco,

    no, it is not targeted to the DWC. Many applications (services and batch) use PIF to change the current plan. Several times a year we hit the limits of the server task and it breaks with the system abend. Our system automation can handle this situation. However, depending on the load on the system, it takes one to two minutes for the server task to come back online.

    Therefore, we prefer rejecting connections to crashing the task.

  • Admin
    Marco Cardelli
    Reply
    |
    Feb 24, 2023

    Hi all, are you getting this problem while using the Server for the Dynamic Workload Console or what is the scenario?

  • Guest
    Reply
    |
    Feb 21, 2023