> 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/tn3270.md).

# TN3270

Configure TN3270 entries in Remote Desktop Manager, including the host, port, account, credentials, and terminal logging options.

This article details the many settings and options available for ***TN3270*** 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><p>How the entry opens:</p><ul><li><strong>Embedded (tabbed)</strong></li><li><strong>Undocked</strong></li></ul><p>When <em><strong>Undocked</strong></em> is selected, two lists beside it select the monitor and the virtual desktop. The virtual desktop list is not supported on macOS.</p></td></tr><tr><td><strong>Host</strong></td><td>Where the host of the entry comes from. Select a host mode from the list. When the host comes from a linked host entry, the <em><strong>Host</strong></em> field of the <em><strong>General</strong></em> tab is unavailable.</td></tr><tr><td><strong>Credentials</strong></td><td>How the credentials of the entry are provided. Select a credential mode from the list. When the credentials come from a linked credential entry, the <em><strong>Username</strong></em> and <em><strong>Password</strong></em> fields of the <em><strong>General</strong></em> tab are unavailable.</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>The host name or IP address of the mainframe. Required unless the host comes from a linked host entry.</td></tr><tr><td><strong>Port</strong></td><td>The port of the host. The default port is <code>3270</code>.</td></tr><tr><td><strong>Account</strong></td><td>The account of the entry. When this field has a value, it can be copied to the clipboard from the entry's clipboard actions. A warning icon beside the field indicates that the credentials configured are not used to log in to the host automatically.</td></tr><tr><td><strong>Username</strong></td><td>The username of the entry. Available when <em><strong>Credentials</strong></em> is set to <em><strong>Username and password</strong></em>.</td></tr><tr><td><strong>Password</strong></td><td>The password of the entry. Available when <em><strong>Credentials</strong></em> is set to <em><strong>Username and password</strong></em>. Unavailable when the <em><strong>Disable password saving in vaults</strong></em> system setting is enabled.</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 only when this option is enabled.</td></tr><tr><td><strong>Log path type</strong></td><td><p>Where the log file is saved:</p><ul><li><strong>Custom</strong> — Uses the file set in <em><strong>Log path</strong></em>.</li><li><strong>Global</strong> — Uses the file named in <em><strong>Log filename</strong></em>.</li></ul></td></tr><tr><td><strong>Log path</strong></td><td>The log file. Visible when <em><strong>Log path type</strong></em> is set to <em><strong>Custom</strong></em>, and required when logging is enabled.</td></tr><tr><td><strong>Log filename</strong></td><td>The name of the log file. Visible when <em><strong>Log path type</strong></em> is set to <em><strong>Global</strong></em>, and required when logging is enabled.</td></tr><tr><td><strong>Log mode</strong></td><td><p>What the log records:</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>What happens when the log file already exists. 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>The level of detail of the logs, from 0 to 4. This setting is available whether or not <em><strong>Enable logging</strong></em> is checked.</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/tn3270.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.
