IBM Support

Changes to Managed System lists with tacmd

Technical Blog Post


Abstract

Changes to Managed System lists with tacmd

Body

image

Changes to Managed System lists with tacmd


There has been a change brought in at 6.3 FP02 that allows a MSL to exist with no members subscribed to it.

This allows MSL's to be created before you know the managed systems you want to allocate to it.

It also allows the last member of a MSL to be removed without the MSL being deleted.


So now you can create a MSL via tacmd with

tacmd createsystemlist -l SJ_list

You will be able to see the MSL in the list with

 tacmd viewsystemlist -l SJ_list

you will see that there are no members in the Assigned Managed Systems.


Once you have used the list assigned members
 (this can be done with tacmd editsystemlist -l SJ_list -a Primary:SJ-ITM633:NT)

when you try and remove the last entry instead of an error

  KUICEL009E: The delete operation cannot delete all the systems from the specified system list.
 The specified system list was not updated because you can not remove all the entries from the system list.
 Check the specified system list and run the command again.

the last entry can be removed and the MSL remains as an empty list.


 However there are a couple of issues if you use both the GUI and the tacmd commands to do this work.

Creating a MSL in the TEP GUI has always allowed without adding any managed systems to it, you can save it and then go back to it later in the GUI.
However it has never and, at the moment,  still does not write this to the TEMS tables, so if an empty list is created by the TEP GUI you cannot view the list via a tacmd command.
As soon as a managed system has been added it will then be written to the TEMS tables and the tacmd command will show it.

Then if you remove the last entry via the TEP GUI before 6.3 FP04 this will allow the empty list to be maintained and the tacmd commands will again show it.

However if you are at 6.3 FP04 the removal of the last managed system from the list will also delete the MSL, this is due to a change that was brought in for APAR IV61046

IV61046 is to fix the 'event clearing' in Situation Event Console especially in logical workspace.

If this change is not needed then the new varaible:

KFW_CMW_REMOVE_MSL_MEMBER_EARLY=Y

is set in the TEPS config, then the behaviour will as before the MSL list will be left with no members existing.

If the variable is needed, then if you need the empty MSL do not remove the last member via the GUI use the tacmd command.

These two GUI issues are being addressed in Apar IV73322.

It should also be noted any MSL's created before 6.3FP02 cannot have the last entry removed even with a tacmd command;  as they still work under the old behaviour. This is being investigated at the moment.

 

Just an up date to the issue of not being able to remove the last entry on an old MSL list.  This has been investigated and was found to be an issue with the version of the tacmd command being used not the age of the MSL; so the removal should work correctly on any MSL.

[{"Business Unit":{"code":"BU004","label":"Hybrid Cloud"},"Product":{"code":"","label":""},"Component":"","Platform":[{"code":"","label":""}],"Version":"","Edition":""},{"Business Unit":{"code":"BU050","label":"BU NOT IDENTIFIED"},"Product":{"code":"SSZ8F3","label":"IBM Tivoli Monitoring V6"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions","Edition":""}]

UID

ibm11084191