Enabling Full Tty Access; Enabling 6530 Terminal Access; Configuring An Alternate Command Interpreter - HP NonStop SSH 544701-014 Reference Manual

Enabling Full TTY Access

SSH2 allows remote SSH clients to establish fully functional OSS shell sessions. This includes the allocation of pseudo
terminals (PTYs), which allow remote users to execute full screen applications, such as vi or Emacs.
PTYs are not natively supported by OSS on the NonStop server. To overcome this limitation, SSH2 comes bundled with
a component named STN. The STN component is also used in another comForte product, SecurTN.
For each PTY allocation request received over SSH, STN will create a dynamic "window" subdevice. STN can also
display a service menu to 6530 clients connecting over SSH, allowing users to connect to a service mapped to pre-
configured static windows or to a service program started on the dynamic window. This feature allows a complete
migration of an existing Telnet access configuration to SSH. Please refer to
chapter and to chapter "STN
To Start the STN Pseudo Terminal Server Included with SSH2
Note: For cases in which SSH2 was delivered with HP NonStop SSH as part of the RVU or as an independent product
for G-Series prior to G06.32, an STN PTY server will be pre-installed as a generic process: SSH-ZPTY ($ZPTY).
1. At the TACL prompt, issue the following commands:
CLEAR ALL PARAM
PARAM BACKUPCPU ANY
RUN STN/NAME $PTY, NOWAIT/
2. Verify if the process started successfully by checking its status and EMS for any error messages.
Note: For productive use of the STN component, we recommend that you install the EMS template file named
"ZSTNTMPL" using standard installation procedures. This will ensure that STN EMS messages will be displayed
correctly.

Enabling 6530 Terminal Access

The STN PTY server also supports 6530 pseudo terminals. This enables products such as comForte's MR-Win6530 to
create fully functional 6530 terminal sessions with clients over the SSH protocol. 6530 block mode applications, such as
ViewPT and Tedit are also supported.
6530 client access can be controlled by setting following attributes of the USER entity of the SSHCTL database:
•
ALLOW-CI
•
CI-PROGRAM
•
CI-COMMAND
By default, SSH2 will start a TACL process on the 6530 PTY device. The TACL will be logged in under the SYSTEM-
USER configured for the USER entity. The following sections explain how to configure an alternate command
interpreter, and how to enable a service menu similar to TELSERV.
Note: Basic 6530 PTY access requires STN A66 or later.

Configuring an Alternate Command Interpreter

TACL is the default command interpreter that SSH2 starts on a 6530 pseudo terminal. You can use the CI-PROGRAM
and CI-COMMAND attributes to assign a different program as the 6530 command interpreter. For example, you can use
PATHCOM to run a PATHWAY PROGRAM directly on the pseudo 6530 terminal.
112 • Configuring and Running SSH2
Reference" for further details.
"Enabling 6530 Terminal
HP NonStop SSH Reference Manual
Access" in this