View Audit

Figure: Example View Audit Screen

Audit Date/Time

The date/time the audit record was created.

Location

The location from where the audit message was generated.

Till

The till from where the audit message was generated.

Computer

The name of the computer from where the audit message was generated.

Type

The type of audit message.

P

Program Started

Shows when a program has successfully connected to the database. This is effectively the time the program started.

T

Program Time

Shows when a program finishes and are used as timing records. They are similar to ‘Program Started’ records but are produced only when a program has finished executing. These records will have the Started, Finished and Minutes columns filled in. They can be used to determine how long a particular job ran for and also to determine how often a specific program is being used.

E

Error

Records an error within a program.

W

Warning

Displays all warnings.

 

Other

Shows a general status message. For example, if a batch job was processing a number of locations, an audit record might be written as processing starts for each location.

 

Reloads and Upgrades

Shows any reloading and upgrading information.

Who

The user who was running the program that created the audit record.

Task

The name of the program that created the audit record.

Description

The exact content depends on the type of message:

Program Started

The full command line string, including parameters, used to run the program.

Program Time

The full command line string, including parameters, used to run the program.

Error

The error message.

Other

A general status message.

Started

The time the program started. This is only recorded for Program Time audit records.

Finished

The time the program finished. This is only recorded for Program Time audit records.

Execute

The number of minutes a program ran for. This is only recorded for Program Time audit records.

On the right side of the screen is an area used by some error messages. It will contain full details of the error, exactly where it occurred in the program, and so on. This can be used by support to find why an error occurred and to fix bugs.

Converted from CHM to HTML with chm2web Pro 2.85 (unicode)