> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/rdm/knowledge-base/knowledge-base-articles/entry-settings/ibm5250.md).

# IBM5250

Configure IBM5250 session entries in Remote Desktop Manager, including host, port, credentials, and terminal logging options such as log path and log mode.

This article details the many settings and options available for ***IBM5250*** session entries in Remote Desktop Manager.

<table data-header-hidden><thead><tr><th width="200"></th><th></th></tr></thead><tbody><tr><td><strong>SETTINGS</strong></td><td><strong>DESCRIPTION</strong></td></tr><tr><td><strong>Name</strong></td><td>The name of the entry.</td></tr><tr><td><strong>Folder</strong></td><td>The folder where the entry is located.</td></tr><tr><td><strong>Display</strong></td><td>How the session is displayed when it is opened.</td></tr><tr><td><strong>Host</strong></td><td>The source of the host used by the entry.</td></tr><tr><td><strong>Credentials</strong></td><td>The source of the credentials used by the entry.</td></tr></tbody></table>

### General

<table><thead><tr><th width="220">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Host</strong></td><td>Enter the host name or IP address of the remote host, or choose one from a list. This field is required, and unavailable when the host comes from a linked or inherited source.</td></tr><tr><td><strong>Port</strong></td><td>Enter the port used to connect to the host. The default port is 23.</td></tr><tr><td><strong>Username</strong></td><td>Enter the username used to log in. This field is unavailable when the credentials come from another source.</td></tr><tr><td><strong>Password</strong></td><td>Enter the password used to log in. This field is unavailable when the credentials come from another source, or when <em><strong>Disable password saving in vaults</strong></em> is enabled in the system settings.</td></tr></tbody></table>

### Advanced

<table><thead><tr><th width="220">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Enable logging</strong></td><td>Log the terminal session. <em><strong>Log path type</strong></em>, <em><strong>Log path</strong></em>, <em><strong>Log filename</strong></em>, <em><strong>Log mode</strong></em>, and <em><strong>Log overwrite mode</strong></em> are available when this option is checked.</td></tr><tr><td><strong>Log path type</strong></td><td><p>Choose where the log file is written:</p><ul><li><strong>Custom</strong></li><li><strong>Global</strong></li></ul></td></tr><tr><td><strong>Log path</strong></td><td>Enter or browse to the log file. This field is shown when <em><strong>Log path type</strong></em> is set to <em><strong>Custom</strong></em>, and is required when <em><strong>Enable logging</strong></em> is checked.</td></tr><tr><td><strong>Log filename</strong></td><td>Enter the name of the log file. This field is shown when <em><strong>Log path type</strong></em> is set to <em><strong>Global</strong></em>, and is required when <em><strong>Enable logging</strong></em> is checked.</td></tr><tr><td><strong>Log mode</strong></td><td><p>Choose what is written to the log:</p><ul><li><strong>Event</strong></li><li><strong>Printable output</strong></li></ul></td></tr><tr><td><strong>Log overwrite mode</strong></td><td><p>Choose how an existing log file is handled. This field is available when <em><strong>Log mode</strong></em> is set to <em><strong>Printable output</strong></em>:</p><ul><li><strong>Default</strong></li><li><strong>Prompt</strong></li><li><strong>Append</strong></li><li><strong>Overwrite</strong></li></ul></td></tr><tr><td><strong>Verbose</strong></td><td>Set the verbose level, from 0 to 4.</td></tr></tbody></table>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.devolutions.net/rdm/knowledge-base/knowledge-base-articles/entry-settings/ibm5250.md?ask=<question>&goal=<user_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 `automate deployments from our CI pipeline` 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.
