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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
Case TS003095404 has been closed today. If you can looked at the dump on MCEVS1, and if you feel the necessity to look at it, I recommend that you should do it quickly. The dump will be deleted after a while.
Most of the data in these SMF records in the JES2 address space are associated with JCLLIB DDs. While it is true the data resides within the JES2 address space, the records are actually associated with the DDs that are being allocated during Converter.
Case TS003095404 is still open. We can look at the dump now. Can you look at the dump on MCEVS1?
Most of the data in these SMF records in the JES2 address space are associated with JCLLIB DDs. While it is true the data resides within the JES2 address space, the records are actually associated with the DDs that are being allocated during Converter.
Case TS003095404 is still open. We can look at the dump now. Can you look at the dump on MCEVS1?
.Just for clarification, can you confirm that the DDs for which you would like to see type 30 EXCP information suppressed are dynamically allocated by the Converter?
If we were to make a change, it would be to update individual allocation requests to suppress DD-level accounting, so it is important to understand which allocation requests would need to be updated.
The problem is about SMF30 subtype4 and subtype5 gathering for JES2 address space. As conversion happens within the JES2 address space and we read in additional DDs and JCLLIBs for each job.... those are going to generate a record. The problem is that these are stored in storage and would be written out to MANxx datasets at step (or job termination), but JES2 itself does not have such a termination because it is always up and running. So all of these records build up in JES2 private over time and eat up our storage.
The caller (IBM SE) understands that the customer should specify SUBSYS(JES2,INTERVAL) and SUBSYS(JES2,NODETAIL) to prevent it. However I think that it is useful if the customer prevent it even with SUBSYS(JES2,NOINTERVAL) and SUBSYS(JES2,NODETAIL). The SMF S99DASUP flag setting is able to suppress the TYPE30 EXCP. I suppose the converter development team can create a parameter that supresses TYPE30 EXCP.
The problem is about SMF30 subtype4 and subtype5 gathering for JES2 address space. As conversion happens within the JES2 address space and we read in additional DDs and JCLLIBs for each job.... those are going to generate a record. The problem is that these are stored in storage and would be written out to MANxx datasets at step (or job termination), but JES2 itself does not have such a termination because it is always up and running. So all of these records build up in JES2 private over time and eat up our storage.
The caller (IBM SE) understands that the customer should specify SUBSYS(JES2,INTERVAL) and SUBSYS(JES2,NODETAIL) to prevent it. However I think that it is useful if the customer prevent it even with SUBSYS(JES2,NOINTERVAL) and SUBSYS(JES2,NODETAIL). The SMF S99DASUP flag setting is able to suppress the TYPE30 EXCP. I suppose the converter development team can create a parameter that supresses TYPE30 EXCP.
Hello, we would like to ask for additional information to help us understand this request.
We already support (through SVC 99 Dynamic Allocation) an option to suppress DD-level accounting information for a DD when it is being allocated. It is up to the application/subsystem to determine whether it is appropriate to use this option when allocating data sets.
It is not clear whether this request is asking for a global system option to suppress all DD-level accounting information that applies to all SMF type 30 records, or something more granular. If you are asking for something more granular, it would be better to request this from the specific application or subsystem (in this case, I think that would be JES2.) It might also help us if you could provide some information about the DDs being allocated so that we could understand what DDs you would like to have supressed.
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
Component - BCP_General
Operating system - IBM z/OS
Source - Client
For recording keeping, the previous attributes were:
Brand - Servers and Systems Software
Product family - z Systems Software
Product - z/OS
Component - BCP_SMF
Operating system - IBM z/OS
Source - Client
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
Component - BCP_SMF
Operating system - IBM z/OS
Source - Client
For recording keeping, the previous attributes were:
Brand - Servers and Systems Software
Product family - z Systems Software
Product - z/OS
Component - BCP_General
Operating system - IBM z/OS
Source - Client