HP NonStop SSH 544701-014 Reference Manual page 229

LOGON controls user authentication for TYPE DYNAMIC services. The default is NONE, requiring no authentication
before starting the application specified by PROG. This is appropriate when the application performs its own
authentication, for example, TACL.
LOGON REQ requires authentication before starting the application. If the SSH SYSTEM-USER for the session is a
valid Guardian userid, then that Guardian userid is used for the session. If SSH SYSTEM-USER is *NONE*, then STN
will prompt the workstation user to enter a valid Guardian userid and password.
LOGON REQ should be used when PROG is the OSS shell (OSH).
LIMIT max-sessions
LIMIT controls the number of simultaneous sessions for a TYPE DYNAMIC service. The default is zero (0), which
disables LIMIT and allows any number of sessions. Values 1-9999 may be specified, then STN rejects an attempts to use
a TYPE DYNAMIC service when LIMIT sessions are already active.
DEBUGOPT OFF | <number>
DEBUGOPT controls the debug-option parameter of Guardian procedure call process_create_, used when starting the
application for TYPE DYNAMIC services. The default is OFF, which omits the parameter. A value in the range 0-7 is
used to set the low order three bits <13:15> of the debug-option parameter.
Setting DEBUGOPT 0 will avoid a problem with PATHCOM leaving ZZSA files when a session is terminated at the
remote workstation. Refer to ADD SERVICE parameter HOME for more information.
RESILIENT YES | NO
RESILIENT is an option for TYPE DYNAMIC services that allows the application to remain active after the terminal
session is disconnected. The STN implementation of RESILIENT is similar in general functionality to that of HP
Telserv, but with some key differences.
RESILIENT NO, the default setting, defines a traditional dynamic service. Upon session disconnect, file system errors
are returned to the application, and most applications, like TACL, will detect this and stop. If KILL_DYNAMIC is set,
STN will stop the application on session disconnect.
When RESILIENT is set to YES, LOGON is automatically set to REQ.
When a session requests a RESILIENT service, STN first checks for any existing windows left over from previous
sessions for the service. If any such window is found, the session is connected to that window. The application that was
running on that window during the previous session will, in general, repeat its prompt, but otherwise the session resumes
exactly where it left off. For example, a TACL will still be logged on and have its environment intact. Specific operation
during such a reconnection is described below:
1. STN first notifies the workstation user that the session is being reconnected to a resilient window with the
message:
STN70 Reconnecting to resilient window #ZWNnnnn
Last access: <time>
2. Then STN displays information about any application programs running on the window, example:
STN70 application $Y1G7 $SYSTEM.SYS00.TACL
STN70 application 1,175 $SYSTEM.SYS00.FUP
The application line is repeated for each opener of the window, including process name, cpu/pin, or posix
pid, and the object file name. This helps clarify exactly what is running in the resumed session.
3. Finally the session is then resumed with handling dependent on the application I/O that was active when the
previous session was disconnected.
•
ITI (conversational), read or writeread pending
The application I/O is completed with febreak 111. For TACL and most other applications this repeats the
prompt.
HP NonStop SSH Reference Manual
STN Reference • 229