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
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
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.
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/OS Communications Server
For recording keeping, the previous attributes were:
Brand - WebSphere
Product family - Enterprise Networking
Product - z/OS Communications Server
The GETBUFFS error is occurring in the CTRACE writer which is being driven by the Packet trace and TCP/IP component trace. Both tracing options provide filtering options that can be used to reduce the amount of data captured. Depending upon the problem being diagnosed it may not be possible to reduce the captured data enough to keep from over running the ability for the CTRACE writer to keep up. When capturing to a CTRACE writer at high speeds multiple datasets can help reduce the impact of I/O delay. Please refer to the z/OS MVS Diagnosis: Tools and Service Aids -> Component trace -> Obtaining a component trace -> Request writing component trace to trace data sets -> Prepare for a specific component trace to trace data sets for information on specifying multiple trace data sets.
Please let us know if this does not address your concerns.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - WebSphere
Product family - Enterprise Networking
Product - z/OS Communications Server
Component - TCP/IP
Operating system - IBM z/OS
Source - None
For recording keeping, the previous attributes were:
Brand - Servers and Systems Software
Product family - zSeries Software
Product - z/OS
Component - DFSMS EREP
Operating system - IBM z/OS
Source - Customer Advisory Council
.Hello Trinh,
I believe that the root cause is the component that is generating the 21K to 67K CTRACE (or TTRACE) records a second. Therefore, it is that component's fault that the TRACEWRT GETBUFF entries are generated for LOGREC:
the GETBUFF failures should be throttled to not generate a unique LOGREC entry for each and every occurrence
LOGREC eventually fills up, and probably reports LOGREC FULL, but it was misinterpreted to be EREP full.
My recommendation to you is to please add my interpretation of the root cause, and have your RFE representative transfer this to Comm Server (TCPIP) to evaluate the possibility of reducing the number of LOGREC entries generated when GETBUFF failures occur. We'll see where this goes after their analysis.
There was 'talk' about creating a LOGREC analysis and elimination facility; but the technology to do so is still too expensive to consider.
Ralph A. Sharpe
z/OS Virtual Storage Dumping Services
Hi Stephen,
EREP is just a formatting tool for the records logged by other components.
LOGREC may have control about how records were logged and released the full buffer.
Could you please contact 'Ralph Sharpe/Poughkeepsie/IBM@IBMUS' to help out?
Thanks.
Creating a new RFE based on Community RFE #71377 in product z/OS.