IBM Support

Sterling Control Center (SCC) does not cause configuration file components to be deleted from Connect:Direct UNIX nodes when removed from configs, even though the configuration job appears to complete successfully.

Troubleshooting


Problem

Removing a netmap entry attribute for a Connect:Direct node from within SCC does not cause it to actually be removed from the netmap of that node, despite the configuration job completing successfully.

Symptom

1. Login to SCC and create new remote netmap entry in Unix Connect:Direct server
2. In netmap Node Entry Properties specify all required values and then in unix tab go to the 'Advanced' option
3. In Advanced specify a value for alternate Comminfo field, like 127.0.0.1, for example
4. Add the remote node definition to Connect direct server
5. Go to the entry added in point 1-4 to advanced tab and remove the value from Alternate Comminfo field (leave it empty)
6. Update entry in SCC
7. You can refresh details but you will see in the actual netmap.cfg that the value for alternate comminfo was not removed , you can also check the configuration job which appears to have completed successfully.

Cause

This has been identified as a product defect under APAR IT01791

Environment

Linux

Resolving The Problem

Please apply the fix from APAR IT01791.

[{"Product":{"code":"SS9GLA","label":"IBM Control Center"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"--","Platform":[{"code":"PF016","label":"Linux"}],"Version":"5.3","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
17 December 2019

UID

swg21675057

Page Feedback