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 Not under consideration
Categories z/TPF
Created by Guest
Created on Feb 11, 2014

MQ04004 MQSeries needs different record IDs for TPFCS data

TPFUG_Req_Number: MQ04004
Contact Originator Id: rmansell@visa.com
Abstract: Provide ability to distinguish between MQ records for TPF logging
Description: Customers need to tailor RTV logging to not log specific records based on record ID and application usage. MQSeries uses generic TPFCS collection pools and therefore logging can not distinguish between MQ records and other records. These are sweeper records only which are created in large numbers when a queue grows rapidly.
Solution Considerations: This requirement needs further clarification. First, this implies that MQ message data is not guaranteed. Second, does the record ID specification need to be on a queue by queue basis or queue manager level? Third, if sweeper records are not logged, what would a swept queue chain look like if the system was restored and the log tapes applied with missing sweeper records? Would the queue be corrupt and need to be cleared.

Idea priority Low
  • Guest
    Reply
    |
    Oct 14, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - z Systems Software
    Product - z/TPF

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Transaction Processing
    Product - z/TPF