Hi, I had previosly workaround for that, managing hierarchy of clopsets outsided of TSM (ITSM?) (making all changes in flat files hierarchy and updating cloptsets via scripts).
This worked but was for my small installation of 100 clients rather complex, so I abandoned it. So, you are not alone. regards Juraj Salak -----Original Message----- From: Jolliff, Dale [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 10, 2002 3:44 PM To: [EMAIL PROTECTED] Subject: Client Option Sets Is it just me, or would anyone else like to see the ability to attach multiple client option sets to a node? Why would it not be a good idea to be able to do this?
