Log access extended operations

Three types of extended operation requests support access to the log files. IBM® Verify Directory administration server supports the following log access extended operations:

• Clear log extended operation
• Get lines extended operation
• Get number of lines extended operation

The server provides access to the following log files:

• ibmslapd.log
• db2cli.log
• db2clicmds.log
• audit.log
• bulkload.log
• ibmdiradm.log
• lostandfound.log
• idstools.log
• db2load.log
• tracemsg.log
• adminAudit.log (this file is available only if the Administration Server audit log OID (1.3.18.0.2.32.11) is in the list of supported capabilities in the root DSE)
• ibmslapd.trace.log (this file is available only if the trace log OID (1.3.18.0.2.32.14) is in the list of supported capabilities in the root DSE)

Lines are numbered starting with line 0. A line is considered all characters up to and including a new line or 400 characters, whichever comes first.

To make the log access request, a client application can use the client APIs for extended operations. An LDAP v3 extended operation request has the form:

	ExtendedRequest ::= [APPLICATION 23] SEQUENCE {
                requestName      [0] LDAPOID,
                requestValue     [1] OCTET STRING OPTIONAL }

All the extended requests use a LogType. LogType is defined as:

LogType ::= ENUMERATED {
	SlapdErrors	       (1),
	CLIErrors         (2),
	AuditLog          (4),
	BulkloadLog       (8),
	AdminErrors       (16),
	AdminAudit        (32),
	DebugOutputFile   (64),
}

RequestValue ::= { log	LogType; }