Cloud Management and AIOps
This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation and AIOps 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.
Considering for the new fix pack release
Looking for the following improvements to be made to the script:
1)Expectation is that all the logs should be gathered whether or not they are stored in a default or non-default directory location, example where log location is /opt/IBM/tivoli/log which is different from the default ITNM log location /opt/IBM/tivoli/netcool/log/precision. So where the log is a symbolic link (lrwxrwxrwx 1 user group date log -> /opt/IBM/tivoli/log/netcool) if the script follows the symbolic link, we also could get the files. The current itnm_data.pl script behaviour creates frustration for the customer, as when logs are not gathered, L2 is requesting again for the logs to be loaded to the case and this also results in a delay in the troubleshooting of the reported issue.
2) Would like to a check to be built into the script, to make it more robust, to validate the domain name being passed when running it. If the domain name is not valid, the script should display an error to say that the domain name is not valid and a valid domain name should be passed to the script.