If a log runs out of space, the current transaction is rolled back. The server issues an error message and halts. You cannot restart the server until the recovery log size is increased.
The server halts.
Monitor archive logs and active logs. If the recovery log space is insufficient, monitor the archive log space first. If the archive log space is full or nearly full, run a full database backup to remove archive logs and consider adding more disk space to the archive log directory. If the archive log space is not full and the active log space is full or nearly full, update the value of the ACTIVELOGSIZE option in the dsmserv.opt file. Set the value of the ACTIVELOGSIZE option to the new maximum size of the active log.