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).
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.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Cloud
Product family - Operations Management
Product - Tivoli Netcool/OMNIbus
Component - Product functionality
Source - Other
For recording keeping, the previous attributes were:
Brand - Cloud
Product family - Operations Management
Product - Tivoli Netcool/OMNIbus Probes
Component - Product functionality
Source - Other
This isn't in regards to *A* lookup table, but lookup table functionality in general. The RFE was opened with a detailed description and a use case. The desire is to be able to search a lookup table by more than just one column in order to:
a) find data using multiple fields
b) allow for searching data without having to duplicate the lookup table
c) allow for searching data without having to make the system more complex, adding additional lookup tables that have to be maintained, causing a potential drift and thus issues
Example:
Existing:
table moo = {{"host1","a"},{"host2","b"}}
$extra = lookup(@Node,$chr)
Change:
table moo = {{"host1","a"},{"host2","b"}}
$key_pos = 1
$extra = lookup(@Node,$chr,$key_pos)
$key_pos = 2
$backwards = lookup($chr,@Node,$key_pos)