Skip to Main Content
IBM Z Hardware and Operating Systems Ideas Portal


This is the public portal for all IBM Z Hardware and Operating System related offerings. 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
Workspace z/OS
Categories BCP_Consoles
Created by Guest
Created on Apr 4, 2023

Operlog should write more than a single MDB to a logblock to allow connecting of multiple MDBS for long multi-line messages

OPERLOG currently only writes  a single Message Data Block (MDB) to a logblock for the OPERLOG logstream.  When attempting to display OPERLOG in hardcopy format, know applications like IEAMDBLG, SDSFLOG and ISFLOG read single logblocks containing single MDBs and format each MDB with a new multiline major line although the MDBs can be part of a long multiline message. The resulting display is not in hardcopy format where there is only one major line and one end line per message. MDBs are not architected to connect to subsequent MDBs when a long multiline message requires multiple MDBs. 
The MAXBUFSIZE  for a logstream logblock is 65532 bytes. The MAXBUFSIZE for an OPERLOG logblock containing a single MDB is 4096. Operlog should include all the MDBs that can fit into a logblock so that an applications can  read one logblock that contains  all the MDBs for a long multiline and connect the MDBs to display a multiline message with one major line and one end line. 

Idea priority Low
  • Guest
    Reply
    |
    Jun 23, 2023
    This item is a valid requirement but unlikely to be given high enough priority to be placed into the product plan. The subject environment is bound by decades old architectural limitations. The subject DISPLAY command can be modified to reduce the volume of output produced, thus avoiding the limitation. More than 250 devices in a range is a trigger ( D U,,,1000,250+ )