Hi All,

I'm intrigued by the possibilities of the new 5.1 Client cluster support for 
unix (this is probably old hat to Windows people).

We have a new passwddir option which allows us to place the TSM encrypted 
password wherever we like e.g. a shared disk.
The CLUSTERNODE option must therefore imply that the host name is is not 
combined with the password when it is encrypted (? security hole)
We then run  with manageservices schedule so the CAD process runs dsmsched on 
the correct machine at the time of the schedule.

The client install guide states that this is only supported under AIX 4.3.3 and 
it implies HACMP.
The only hook that I can see that might be HACMP specific is to discover which 
filesystems are cluster controlled and I can see no reason why this client 
would need 5.1 server function.
I have Sun/Veritas clients that need this badly, and I'm looking at AIX/Veritas 
for some upcoming work.

Does the AIX 4.3.3 support require HACMP?  Should it work with other HA 
software even if not supported?
When can we expect Sun/Veritas support?
Will it run on older server levels?


Sorry Andy, its must seem that it doesn't matter what you give us we want more, 
but any clues on this will be appreciated.

Thanks

Steve Harris
AIX and TSM Admin 
Queensland Health, Brisbane Australia
 







**********************************************************************
This e-mail, including any attachments sent with it, is confidential 
and for the sole use of the intended recipient(s). This confidentiality 
is not waived or lost if you receive it and you are not the intended 
recipient(s), or if it is transmitted/ received in error.  

Any unauthorised use, alteration, disclosure, distribution or review 
of this e-mail is prohibited.  It may be subject to a statutory duty of 
confidentiality if it relates to health service matters.

If you are not the intended recipient(s), or if you have received this 
e-mail in error, you are asked to immediately notify the sender by 
telephone or by return e-mail.  You should also delete this e-mail 
message and destroy any hard copies produced.
**********************************************************************