HP 3000 Manuals

What is a Profile [ Configuring and Managing Host-Based X.25 Links ] MPE/iX 5.0 Documentation


Configuring and Managing Host-Based X.25 Links

What is a Profile 

A profile is a group of device connection specifications and
characteristics that can be associated with devices.  Profiles can be
associated with terminals, printers, PAD terminals and printers, and
UPSs.

The word profile is used in two different contexts in this chapter.  When
a ldev is configured on the MPE/iX system, a profile name is associated
with each ldev.  This association is configured on the DTC Card
Configuration screens.  The information in the profile name describes the
characteristics of the ldev on the system and in the DTC. The information
configured in the profile name is described in the Profile Screens
section.

When a PAD ldev is configured, there is also a PAD profile number or
value that describes certain parameters of the connection between the PAD
and the X.25 card in the DTC. These additional PAD parameters are set
within the profile name associated with the PAD ldev.  The PAD Terminal
Profile section describes these PAD parameters.  Table 4 lists the PAD
profile numbers that are available.  The sample configuration file on the
HP 3000 Series 900 supplies several terminal and printer profiles.  You
may also create your own profiles.

At the end of this chapter, tables 1 through 5 list terminal, printer and
PAD profiles supplied by the HP 3000 Series 900, respectively.

Profile Name 

Each profile is identified by a profilename.  The name can be up to eight
characters long and must start with a letter followed by letters and
numbers.  At any one time, up to 256 profiles can be configured per
system.

The profiles supplied by the HP 3000 configuration file follow a naming
convention.  For example, TR10D96 denotes a terminal profile (TR) of
terminal type 10 (10), for direct connect (D), with line speed of 9600
bps (96).  Printer profiles starts with PR, such as PR18D96.  The
standard UPS profile is UP10D12 where (UP) denotes an HP PowerTrust UPS.

Terminal Profiles 

Terminal profiles 
define terminal characteristics for terminals, PCs running in terminal
emulation mode, and UPSs.

A terminal profile defines the following terminal characteristics:

   *   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 widthin characters (bytes).

   *   The type of modemused, if any.

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

   *   Whether the terminal can use the :HELLO command to logon to the HP
       3000.

   *   Whether the terminal will use hardwarehandshake.  (Supported on
       DTC 16iX/16MX and DTC 72MX only.)  (Does not apply to the DTC
       16RX).

   *   The type of parity that will be used if parityis enabled.

   *   Specifies whether auto speed and parity sensingwill 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).

   *   Specifies whether native languagedevices will be used.

   *   The device class names associated with the terminal.

       Terminal profile characteristics are described in detail under
       "Terminal Profile Screen," later in this chapter.

Printer Profiles 

Printer profilesdefine printer characteristics for printers.  A printer
profile defines these printer characteristics:

   *   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 bitsper second.  (Does not apply to the DTC
       16RX).

   *   The record widthin 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 theDTC 16RX).

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

   *   Whether the printer is initiallyspooled.

   *   Whether the printer will use a native languagecharacter set.

   *   Whether hardware handshake is used.  (Supported on DTC 16iX/16MX
       andDTC 72MX only.)  (Does not apply to theDTC 16RX).

   *   The device class names associated with the printer.

       Printer profile characteristics are described in detail under
       "Printer Profile Screen," later in this chapter.

PAD Terminal Profiles 

A PAD terminal profile defines these characteristics of the PAD terminal:

   *   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 following four parameters will be ignored when a profile is
       configured for non-nailed devices:  PAD test requested, send
       initial profile, X.3 setting requested, and data forwarding parm
       #3 and #4.  These four parameters will also be ignored when the
       connection is made through a public PAD, because the connection
       will be established to a non-nailed device on the host.

PAD Printer Profiles 

A PAD printer profile defines these characteristics of a PAD printer:

   *   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.

Terminal Types 

A terminal type is a collection of characteristics that cause a terminal
to act and react in a specific way.  It defines the relationship between
the terminal and the MPE/iX operating system.  Three terminal types are
supplied with MPE/iX: terminal type 10, terminal type 18, and terminal
type 24.

Terminal Type 10 

Use terminal type 10for 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 transfersand
can detect data transmission errorsthrough 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 consoleuses terminal type 10, but it does not have the same functionality as other terminals connected and configured as terminal type 10. A UPSalso uses terminal type 10, but it has different functionality from other devices connected and configured as terminal type 10.
Terminal Type 18 Use terminal type 18for non-Hewlett-Packard devices. It differs from terminal type 10 in the following ways: * Block mode data transfersare not supported. * Data protection is supplied through the XON/XOFF protocol.By default, parity checkingis not used. * The read trigger characteris not recognized. Terminal Type 24 Use terminal type 24for PAD terminals. Limitations apply to operations over PAD connections. For example, the following functions are not supported: * Block modeapplications. * HP Block Mode applications. * Parity generation, programmatically. * Parity checking, programmatically. For more information on supported PAD operations, refer to the Asynchronous Serial Communications Programmer's Reference Manual (32022-61001). Printer Types A printer typeis a collection of characteristics that cause a printer to act and react in specific ways. It defines the relationship between the printer and the MPE/iXoperating system. Four printer types are supplied with MPE/iX: printer type 18, printer type 21, printer type 22, and printer type 26. Printer Type 18 Use printer type 18for spooled and applicationprinters, without status checking. An application printer is controlled by a program running on an MPE/iX computer. The program performs the following functions: * Opens the printer. * Writes to the printer. * Initializes the printer before each listing. * Spools output to the printer. * Sends messages to the system consoleor the user's terminal. * Checks the status of the printer. (Only some printerscan supply this information.) * Closes the printer. Printer type 18 responds to an XOFF character sent from a printer. The XOFF protocolstops the flow of datato 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. Printer Type 21 Use printer type 21for remote spooledprinters. These are asynchronousprinters that can use the MPE/iX spooler. Printer type 21 uses the XON/XOFF protocoland status checking. Status checking means an HP printer that respond to the interrogation string: [Esc] ? [DC1]. In addition, data transmission errorscan be detected (but not corrected) using parity checking. Printer Type 22 Use printer type 22for local spooled printers.These are asynchronousprinters 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. Printer Type 26 Use printer type 26for remote spooled printersconnected to a network.These are printersthat can be spooledand connected through a modemto 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 requestis 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 messageis 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 timeris 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 spoolfilebecomes ready to print before the 10 second wait expires.


MPE/iX 5.0 Documentation