Configuration changes are required on the server when cells/columns are physically added to an existing library otherwise those added cells/columns are not used.
The server needs to be restarted and library audited or possibly needs to be redefined.
When a library is physically upgraded, for example, when drives, cells or columns are added to a physical library to expand it, the Tivoli Storage Manager server needs to be notified of these changes.What needs to be done on the Tivoli Storage Manager will depend on the server level.
With SAN Device Mapping implemented (since TSM520 for Windows and TSM530 for most other platforms), when hardware changes are done to the library, the Tivoli Storage Manager server needs to be restarted. During server initialization, Tivoli Storage Manager server will access the library. If the library inventory has changed, it will be refreshed at that time. If drives are added or deleted from the library or drive element addresses are changed, this information will be refreshed at server initialization also. If the library path has changed, then the path needs to be updated with the new device name for the new library path. The same holds true when dealing with a 3584 library with the ALMS feature. This is discussed in the following document : http://www-1.ibm.com/support/docview.wss?uid=swg21053638 That document will mention that “TSM supports the Advanced Library Management System (ALMS) and Virtual I/O Slots (VIOS) features of IBM 3584. When changing the number of drive, storage, or import/export elements for a logical library, the TSM server must be restarted.”