Integration
This is an IBM Automation portal for Integration 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
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 - WebSphere
Product family - Integration
Product - IBM MQ
For recording keeping, the previous attributes were:
Brand - WebSphere
Product family - Connectivity and Integration
Product - IBM MQ
This has long been a topic of interest at the customers where I've done MQ security consulting. The array of elaborate schemes implemented in code to capture these files as they roll is incredibly diverse.
The biggest issue is that the rollover interval is not predictable and may be artificially reduced in an attack. To address this, IBM might provide a primary/secondary extent set similar to transaction logs and an availability interval.
For example, the admin specifies 10 secondary extents and an availability interval of 65 minutes. If at any point log activity would roll AMQERR03.LOG before it was 65 minutes old, it rolls to secondary extents. This continues until either secondary extents are exhausted (which generates an event) or the hour expires. Meanwhile, the log archiving job runs hourly and the administrator can be confident that *all* the logs were retrieved.
We are considering modifications to MQ's error logging for a future release. While we may not do exactly as suggested here, we would hope to make it easier to monitor error messages.
Development -
Utilizing syslog() or a platform-specific equivalent would be acceptable for this process. We are trying to develop a process by which we could 'archive' the AMQERR0x.LOG files as they are 'rolled', but before they are overwritten. Today, we have made the files very large, to help us w/ problem determination and for historical purposes. Having a means to archive these logs (similar to z/OS) would be very helpful.
This came back into our system with no additional info provided
How would you expect to monitor for the changes in the error logs? Remember that the queue manager is not necessarily running fully at the time of writing to these files, so anything that involves writing real MQ event messages cannot be reliable. Similarly, it cannot be running any background daemon to process the files. And writing something like an error message to the log files will only useful if there is a monitor permanently reading from the log, and then resetting to the top of the file when such a message appeared. Alternatives might involve syslog() or a platform-specific equivalent.
How would you expect to monitor for the changes in the error logs? Remember that the queue manager is not necessarily running fully at the time of writing to these files, so anything that involves writing real MQ event messages cannot be reliable. Similarly, it cannot be running any background daemon to process the files. And writing something like an error message to the log files will only useful if there is a monitor permanently reading from the log, and then resetting to the top of the file when such a message appeared. Alternatives might involve syslog() or a platform-specific equivalent.