Hi Gary,

See Administrator's Guide (b_srv_admin_guide_linux.pdf), Chapter 21. Managing 
the database and recovery log, Increasing the size of the active log :

If the log is running out of space, the current transaction is rolled back, and 
the server issues an error message and halts. You cannot restart the server 
until the
active log size is increased. 
To increase the size of the active log while the server is halted, complete the 
following steps:
1. Issue the DSMSERV DISPLAY LOG offline utility to display the size of the 
active log.
2. Ensure that the location for the active log has enough space for the 
increased log size. If a log mirror exists, its location must also have enough 
space for the
increased log size.
3. Halt the server.
4. In the dsmserv.opt file, update the ACTIVELOGSIZE option to the new maximum 
size of the active log, in megabytes. For example, to change the active log to 
its
maximum size of 128 GB, enter the following server option:
activelogsize 131072
5. If you plan to use a new active log directory, update the directory name 
specified in the ACTIVELOGDIRECTORY server option. The new directory must be
empty and must be accessible to the user ID of the database manager.
6. Restart the server.

Log files of 512 MB are automatically defined until the size specified in the
ACTIVELOGSIZE option is reached. If a log mirror exists, log files are also 
defined
automatically.


-- 
Best regards / Cordialement / مع تحياتي
Erwann SIMON

----- Mail original -----
De: "Gary Lee" <glee AT BSU DOT EDU>
À: ADSM-L AT VM.MARIST DOT EDU
Envoyé: Lundi 14 Décembre 2015 21:25:47
Objet: [ADSM-L] extending tsm active logs for tsm 6.3.4

Tsm server 6.3.4 under redhat 6.7.

If I want to increase the size of the tsm active log, must I backup, reformat 
and restore the database?

So far that's all I have found.
If not, where is the procedure for extending the log?

Thanks for the help.