The header of the server log includes the title, task numbers, session start date and time, server code file title, server version identifier, maximum number of workers supported, the requested maximum number of idle workers maintained, and the identifier for the earliest version of the driver that can be supported. The last line identifies the columns that follow the header. The following provides an example of header information for the server log file:

MCPSQL log for job 00939/0939
  Wednesday, June 4, 2012 12:58:03.1374
Server (USER)SYSTEM/MCPSQL/SERVER ON UI2.
  Version 56.180.0045
maximum Workers supported = 256
Server Internal Release no. = 056180
MM/DD HH:MM:SS(MIX#)

A trailer provides the date and time at the end of the log session as shown in the following example:

End of log Wednesday, June 4, 2012 12:58:33.2257

Other lines in the log each begin with a prefix containing the month and day, the time to the nearest second, and the mix number as shown in the following example:

06/04 12:58:06(0939) idle Worker #1 starting

Static information, which is not provided in the header, is written to the log as procedures are completed so that the data is accessible. This information appears at various locations in the body of the log. The following is one such example:

06/04 12:58:06(0939) MCPSQL_config file name:06/04 12:58:06(0939)
 (USER)MCPSQL/SERVER/CONFIG ON PACK

Dynamic information about significant events is written to the log as the events occur. The following is an example:

06/04 12:58:06(0939) Worker #0 
  (USER)SYSTEM/MCPSQL/WORKER ON PACK starting
06/04 12:58:06(0939)
  active Workers = 1, idle Workers = 1, total = 2

All error messages generated by the Query Processor server that signal environmental errors (that is, database errors and warnings or Query Processor server malfunctions) are written to the log as well as being sent to the Query Processor provider for display.