your request was "DB2 operates for an SAP system. logprimary has been set to 100 and logsecond to 0 but log directory is full and flooded with 300 log files? "
The reason is probably that SAP requires archive logging by default, which means that obsolete online logs have been archived. If you do not move your DB2 archive logs to another place (e.g. tape, SAN, NAS) your log directory will get used to 100%.
You should either configure your DB2/SAP to allow re-using log files or you should manage your archive log files.
See LOGRETAIN andÂ LOGARCHMETH1 configuration values at http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/com.ibm.db2.luw.admin.config.doc/doc/r0000247.html.
One of my clients creates a full back-up every nite and deletes all obsolete archive logs. This is fine for systems which allow a maintenance time-out and some other minor draw-backs. The test systems operate with config parm LOGRETAIN OFF.
Nowadays SAP systems work on failsafe storage systems, so DB2 administrators should check their archive strategy.