> For the complete documentation index, see [llms.txt](https://docs.maitredpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maitredpos.com/maitred/maitred-online-help-contents-by-module/database/view/error-log.md).
# Error Log
This option allows to view the error log of your Maitre'D system.
**Identification**
**Listing**
This information refers to the line in the Maitre'D source program.
**Step**
This information refers to the step number in the Maitre'D source program.
**Event**
This is a sequential number to identify the error message.
**Information**
**Date**
The date when the error occurred.
**Time**
The time when the error occurred.
**Access Level**
The access level in use when the error occurred.
**Terminal number**
The terminal number from where the error occurred.
**Messages**
**Error**
A description of the error.
**Database**
The database from which the error occurred.
**OS Error:**
Error message reported by the operating system.
(For Example: Too many open files, not enough memory…)
.gif)
To go to the first record of the error log.
.gif)
To go to the previous record of the error log.
.gif)
To go to the next record of the error log.
.gif)
To go to the last record of the error log.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.maitredpos.com/maitred/maitred-online-help-contents-by-module/database/view/error-log.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.