Is there a way to avoid the PTITSLOG tablespace (PTITSLOG.PTLOG_MAIN_# table) from encountering an out of extents condition that can be encountered while using the CA DB2 toolset, like the Unicenter RC/Update for DB2 UDB for z/OS?
The PTITSLOG tablespace is defined in the Implementation section "General Facilities Objects" section. This is the tablespace that contains the main logging table.
A procedure is in place to clean up the logging table in which the highlevel.PARMLIB pds member ALOGDEL can have the retention time reduced and the highlevel.SRCLIB member LOG#ADEL needs to be executed. This execution can be scheduled to run at convenient time intervals. This procedure is documented in the General Facilities Reference Guide, Chapter 7, "Automatically Deleting Log Data".