What is a Profile

• The profile name.

• The terminal type used (10, 18, 24) or the terminal type file name if you are using a terminal type file created through the workstation configurator utility (TTUTIL.PUB.SYS).

  For more information, see Terminal type file name under "Terminal Profile Screen," later in this chapter.

• The line speed, in bits per second. (Does not apply to the DTC 16RX).

• The record width in characters (bytes).

• The type of modem used, if any.

• Specify the protocol used to establish a modem link between the DTC and an attached device. (Does not apply to the DTC 16RX).

• Whether the user is allowed to enter the :HELLO command to logon to the HP 3000.

• Whether the terminal will use hardware handshake. (Supported on DTC 16iX/ 16MX and DTC 72MX only.)

• The type of parity that will be used if parity is enabled.

• Specifies whether auto speed and parity sensing will occur at logon for terminals using this profile. (Does not apply to the DTC 16RX).

• Specifies whether the terminal will be reset after a DTC is powered on or after the connection is re-established. (Does not apply to the DTC 16RX).

• Number of stop bits to be used for asynchronous characters. (Supported on DTC 16iX/DTC 16MX and DTC 72MX only.)

• Whether to enable flow control between the DTC port and the connected device.

• Specifies whether native language devices will be used.

• The device class names associated with the terminal.

• The terminal port name. Usually used for extended switching connections.

• Specify whether the DTC user interface timeout is active.

• Specify whether switching is enabled for the port.

• Specify whether the DTC will establish a connection automatically when the modem lines are raised.

• The maximum number of sessions allowed from a terminal.

• Specify whether "keep alive" mechanism is to be activated to detect if connection is still there. (Does not apply to the DTC 48 without memory extension.)

• Specify whether port configuration parameters; data length and parity, have to be forced when binary mode is selected. (Supported on DTC 16iX/DTC 16MX and DTC 72MX only.)

• Specify destination node if automatic connection is enabled.

• Specify the character that will return the terminal user to the DTC user interface.

• The profile name.

• The printer type used (18, 21, 22, or 26) or the printer type file name if you are using a printer type file created through the workstation configurator utility (TTUTIL.PUB.SYS).

  For more information, see Printer type file name under "Printer Profile Screen," later in this chapter.

• The line speed in bits per second. (Does not apply to the DTC 16RX).

• The record width in characters (bytes).

• The type of modem used, if any.

• Specify the protocol used to establish a modem link between the DTC and an attached device. (Does not apply to the DTC 16RX).

• The type of parity that will be used, if parity is enabled. (Does not apply to the DTC 16RX).

• Whether the printer is initially spooled.

• Whether the printer will use a native language character set.

• Whether hardware handshake is used. (Supported on DTC 16iX/16MX and DTC 72MX only.)

• Number of stop bits to be used for asynchronous characters. (Supported on DTC 16iX/DTC 16MX and DTC 72MX only.)

• Whether to enable flow control between the DTC port and the connected device.

• The device class names associated with the printer.

• The printer port name.

• Specify whether the printer can be accessed by a single system or multiple systems.

• Specify whether the DTC will establish a connection automatically when the modem lines are raised.

• Specify the number of hosts sharing this printer.

• Specify whether "keep alive" mechanism is to be activated to detect if connection is still there. (Does not apply to the DTC 48 without memory extension.)

• Specify whether port configuration parameters; data length and parity, have to be forced when binary mode is selected. (Supported on DTC 16iX/DTC 16MX and DTC 72MX only.)

• Specify destination node if automatic connection is enabled.

• A string that may be sent to the device under specific conditions such as after a port reset, or a connection is closed.

• The profile name.

• The terminal type used (24 recommended) or the terminal type file name if you are using a terminal type file created through the workstation configurator utility (TTUTIL.PUB.SYS).

• The record width in characters (bytes).

• Whether the terminal user can issue the :HELLO command at the terminal.

• Whether the terminal will reset itself after a lost connection (for use with HP terminals only).

• Whether the terminal will use a native language character set.

• Whether or not the DTC will perform a PAD test at connection establishment time to determine the PADs behavior.

• Whether the DTC will send an initial profile to set the PAD to default X.3 parameters at connection establishment time. (If you set this option to N you must also set "PAD test requested" to N.

• Whether to allow changes to X.3 parameters after connection establishment.

• How the data forwarding option is set. (You may select a data forwarding option only if you request "X.3 setting" to allow changes to X.3 parameters.)

• The device class names associated with the terminal.

• The profile name

• The printer type used (26 for PAD printer) or the printer type file name if you are using a terminal type file created through the workstation configurator utility (TTUTIL.PUB.SYS).

• The record width in characters (bytes).

• Whether the printer is initially spooled.

• Whether the printer uses a native language character set.

• Whether or not the DTC will perform a PAD test at connection establishment time to determine the PADs behavior.

• Whether the DTC will send an initial profile to set the PAD to default X.3 parameters at connection establishment time. (If you set this option to N you must also "PAD test requested" to N.

• Whether to allow changes to X.3 parameters after connection establishment.

• The device class names associated with the printer.

• The name of the port.

• The line speed, in bits per second.

• The type of modem used, if any.

• Specify the protocol used to establish a modem link between the DTC and the attached device.

• The type of parity that will be used if parity is enabled.

• The mode of data transfer in back-to-back connections, can be ASCII or binary.

• Specify whether ENQ/ACK flow control is enabled.

• Number of stop bits to be used for asynchronous characters. (Supported on DTC 16iX/DTC 16MX and DTC 72MX only.)

• Whether to enable flow control between the DTC port and the connected device.

• Specify whether "keep alive" mechanism is to be activated to detect if connection is still there. (Does not apply to the DTC 48 without the memory extension.)

• Specify whether port configuration parameters; data length and parity, have to be forced when binary mode is selected. (Supported on DTC 16iX/DTC 16MX and DTC 72MX only.)

• Specify whether the DTC will establish a connection automatically when the modem lines are raised.

• Specify whether hardware handshaking will be used.

• Specify destination node if automatic connection is enabled.

• A string that may be sent to the device under specific conditions such as after a port reset, or a connection is closed.

Use terminal type 10 for Hewlett-Packard terminals and Hewlett-Packard personal computers running in terminal emulation mode. This type enables the XON/XOFF protocol (both receive and transmit). It supports block mode data transfers and can detect data transmission errors through the use of parity checking. This terminal type can work with some non-Hewlett-Packard devices, but none of them are supported.

	NOTE: The system console uses terminal type 10, but it does not have the same functionality as other terminals connected and configured as terminal type 10. A UPS also uses terminal type 10, but it has different functionality from other devices connected and configured as terminal type 10.

Use terminal type 18 for non-Hewlett-Packard devices. It differs from terminal type 10 in the following ways:

Use terminal type 24 for PAD terminals. Limitations apply to operations over PAD connections. For example, the following functions are not supported:

For more information on supported PAD operations, refer to the Asynchronous Serial Communications Programmer's Reference Manual.

Use printer type 18 for spooled and application printers, without status checking. An application printer is controlled by a program running on an MPE/iX computer. The program performs the following functions:

Printer type 18 responds to an XOFF character sent from a printer. The XOFF protocol stops the flow of data to the printer so data cannot be lost. However, the printer cannot send an XOFF character if it is unplugged, turned off, or loses power. In these instances, data is lost.

Use printer type 21 for remote spooled printers. These are asynchronous printers that can use the MPE/iX spooler.

Printer type 21 uses the XON/XOFF protocol and status checking. Status checking means an HP printer that respond to the interrogation string: [Esc] ? [DC1].

In addition, data transmission errors can be detected (but not corrected) using parity checking.

Use printer type 22 for local spooled printers. These are asynchronous printers that can use the MPE/iX spooler, but not with modems.

Printer type 22 supports the same data protection methods (the XON/XOFF protocol and status checking) as printer type 21, except for parity checking.

Use printer type 26 for remote spooled printers connected to a network. These are printers that can be spooled and connected through a modem to a statistical multiplexer or printers connected to a PAD. Printer type 26 builds on printer type 22, with additional features to cope with delays that occur over a buffered connection.

The status request is sent and the time begins. If there is no reply, the timer is reset. This is repeated 10 times.

If the status request detects an error condition, for example the printer runs out of paper, a system console message is displayed and the retry is done only one more time. If there is no reply or an error occurs, the connection is closed and the spooler stopped.

The XOFF timer is also retried 10 times. After the last entry, the connection shuts down and data is refused. In addition to status request and XOFF changes, all closed connection requests from the computer are not acted upon for 10 seconds. This avoids having to reestablish the remote connection if another spoolfile becomes ready to print before the 10 second wait expires.