I have two TSM V6 instances on one computer. I always make the instance owner userid to be the owner of its raw logical volumes, as a matter of safety, with chmod 600. This way I don't accidentally allow more than one TSM instance to get access to the same raw LV.
This is not required, but it sure is a good idea! And it's a much better idea than 'chmod 666' suggested in that IBM document. The "sign of the devil" should be a warning of data loss if you use it, especially with multiple TSM instances. (And I'm not just being irrationally hexakosioihexekontahexaphobic.) Roger Deschner University of Illinois at Chicago [email protected] ======I have not lost my mind -- it is backed up on tape somewhere.===== On Thu, 19 Sep 2013, Shawn DREW wrote: >Yes, permission needs to be considered for v6 resource access, although you >don't necessarily need to reassign ownership. > >http://www-01.ibm.com/support/docview.wss?uid=swg21394164 > > >Regards, >Shawn >________________________________ >Shawn Drew > > >> -----Original Message----- >> From: [email protected] [mailto:[email protected]] >> Sent: Thursday, September 19, 2013 1:03 PM >> To: [email protected] >> Subject: [ADSM-L] TSM v5->v6 upgrade - permissions of raw disk pool vols >> >> Our TSM v5 servers all run as root. After the conversion to v6 they will be >> running as a non-root account which is the tsm/db2 instance owner. >> >> Our disk pools are all raw logical volumes. Do we need to change ownership >> of the raw volumes to the new instance owner so dsmserv can access the >> LV's? >> Along the same lines, is the new v6 dsmserv able to access the RMT tape >> devices, or do I have to change their ownership also? >> >> Thanks >> >> Rick >> >> >> >> >> >> ----------------------------------------- >> The information contained in this message is intended only for the personal >> and confidential use of the recipient(s) named above. If the reader of this >> message is not the intended recipient or an agent responsible for delivering >> it to the intended recipient, you are hereby notified that you have received >> this document in error and that any review, dissemination, distribution, or >> copying of this message is strictly prohibited. If you have received this >> communication in error, please notify us immediately, and delete the original >> message. > > >This message and any attachments (the "message") is intended solely for >the addressees and is confidential. If you receive this message in error, >please delete it and immediately notify the sender. Any use not in accord >with its purpose, any dissemination or disclosure, either whole or partial, >is prohibited except formal approval. The internet can not guarantee the >integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) >not therefore be liable for the message if modified. Please note that certain >functions and services for BNP Paribas may be performed by BNP Paribas RCC, >Inc. >
