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:
Post your ideas
Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notifications on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
Please use the following category to raise ideas for these offerings for all environments (traditional on-premises, containers, cloud):
Cloud Pak for Multicloud Management
Cloud Pak for Network Automation - incl Orchestration and Performance Management
Cloud Pak for Watson AIOps - incl Netcool Operations Management portfolio
Edge Application Manager
IBM Observability with Instana
ITM-APM Products - incl IBM Tivoli Monitoring v6 and Application Performance Monitoring v8
Workload Automation - incl Workload Scheduler
Tivoli System Automation - inc Tivoli System Automation Application Manager (SA AM), Tivoli System Automation for Multiplatforms (SA MP)
lssam should display correct NodeName which was defined by preprpnode
Currently, lssam pulls its node names from the NodeNameList of the IBM.PeerNode resource attributes but only uses the shortname. This can lead to different NodeNames: lsrpnode, lsrsrc,... show the defined hostname in the long version lssam shows a short version of the NodeNames.
This makes lssam unusable for scripting where NodeNames are used. It also leads to problem with commands like rgmbrreq, when using the resource name shown by lssam.
With this "enhancement" lssam should show the correct node name which was defined by preprpnode and can be display with lsrpnode. This would solve the describe problems and eleminate these paint points.
Name OpState RSCTVersion
zdwa005.generali-gruppe.de Online 126.96.36.199
zdwa006.generali-gruppe.de Online 188.8.131.52
$ sudo lssam
Online IBM.ResourceGroup:rg.ADEWASPROD9.zdwa005-WS70-ND.dmgr Nominal=Online
'- Online IBM.Application:ADEWASPROD9.zdwa005-WS70-ND.dmgr:zdwa005
Online IBM.ResourceGroup:rg.GDIS.PatrolZDWA005 Nominal=Online
'- Online IBM.Application:patrol:zdwa005
This makes lssam unusable for scripting where NodeNames are used. E.g. command rgmbrreq, when using the resource name shown by lssam:
$ sudo rgmbrreq -o lock IBM.Application:ADEWASPROD9.zdwa005-WS70-ND.dmgr:zdwa005
rgmbrreq: 2622-014 The resource "ADEWASPROD9.zdwa005-WS70-ND.dmgr" not found in the class "IBM.Application".
rgmbrreq: 2622-015 None of the resources with the specified types exists in their respective classes.
With the new enhancement lssam should show the correct Node Name, e.g.
This would eleminate the described problems / paint points.
Do not place IBM confidential, company confidential, or personal information into any field.