Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software 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 Delivered
Created by Guest
Created on Mar 14, 2013

Update PROCs genereted to specify DS for SYSUDUMP/RKLVSNAP DD's not SYSOUT

The problem that occured created a huge amount of output to RKLVSNAP DD (enough to fill out JES2 spool to 100% in less than 30 minute). The mitigating action and specified 'reccomended' settings for SYSUDUMP and RKLVSNAP in the PMR was to direct them to a dataset with small primary and large secondary. However, the delivered procs generated by the install still creates them as SYSOUT. If the IBM recomentation is that these go to dataset should IBM even want/need them, I feel the JCL should be delivered that way.

This is probably applicable to all Omegamon z/OS products but the case experienced was with the TEMS.

Idea priority Low
  • Guest
    Reply
    |
    Dec 5, 2016

    Delivered in PARMGEN PTF UA76016 for APAR OA46184 (1Q15 Interim Feature) -
    • New WCONFIG(KCI$SLOG) for RKLVSNAP/RKLVLOG. TMS:Engine-based product started tasks (TEMS, CUA, Agents) will remove these DDs from the product started tasks, and instead, PARMGEN will replace the DDs with a customer-controlled WCONFIG imbed called WCONFIG(KCI$SLOG) that gets imbedded during $PARSE* job.
    • New WCONFIG(Kpp$SDMP) SYS%DUMP DD - TMS:Engine-based product started tasks (TEMS, CUA, Agents) that currently have a SYSUDUMP DD, will remove it from the product started tasks that currently hardcode a SYSUDUMP DD, and instead, PARMGEN will replace as a customer-controlled WCONFIG imbed called WCONFIG(Kpp$SDMP) (one per product). Current products that have a hardcoded SYSUDUMP DD are:
    • TEMS (KDS)
    • OMEGAMON XE for Storage CUA (KDF)
    • OMEGAMON XE for IMS (Classic KOI STC per IMS subsystem and CUA KI2)
    • OMEGAVIEW (KMV)
    • OMEGAMON XE on z/OS Classic KOM and CUA KM2
    • OMEGAMON XE for Mainframe Networks CUA (KON).

  • Guest
    Reply
    |
    Jun 19, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - zSeries Software
    Product - Tivoli OMEGAMON XE on z/OS

    For recording keeping, the previous attributes were:
    Brand - Tivoli
    Product family - Performance Monitoring
    Product - Tivoli OMEGAMON XE on z/OS

  • Guest
    Reply
    |
    Mar 21, 2013

    This is something development agrees with and would like to provide.   It requires coordination across other monitors and will take planning against other business priorities but will try and provide this request.