SSH Reference Manual

• No WINDOW pre-configuration required.
• No application pre-configuration required.
• Workstations can have identical configurations.
• Unique window names are difficult to track and manage.
• Application process creation slows window startup.
• Can be awkward for Pathway and other applications that allocate CPU and other resources using their own
algorithms.
Processes created by STN for SERVICE TYPE DYNAMIC that do not have a userid from LOGON REQ or from SSH
authentication are started with CAID 0,0 (sometimes known as NULL.NULL) rather than 255,255 (SUPER.SUPER) as
was done before version B20.
TYPE STATIC
The PROG, CPU, PRI, LIB, SWAP, PARAM, USER, HOME, LIMIT, RESILIENT, DEBUGOPT and LOGON fields
are not allowed with TYPE STATIC.
When a session requests a static service, a search is made for a previously defined WINDOW that satisfies the following
requirements:
• SERVICE field matches this service.
• TYPE is STATIC.
• Has an application running and waiting for a new session (CONTROL 11).
• Is not already in session.
If no such window is found, an error message is displayed and the service menu is repeated.
PROG program-file-name
Required when TYPE DYNAMIC is used; not allowed otherwise. PROG specifies the object file for the dynamic service
to be started.
CPU (cpunum | cpunum-cpunum | ANY)
Default is (0,15) or as specified by DYN_CPU. Only allowed with the TYPE DYNAMIC parameter. Specifies the CPU
number, or range of CPU numbers, in which STN will start the dynamic service application. If a range is specified, STN
will "round-robin" each new session to spread the workload over the specified CPUs. ANY can be specified for any
available cpu.
PRI priority
Only allowed with the TYPE DYNAMIC parameter. Specifies the process priority used to start the dynamic application.
If omitted, the priority specified by the DYNAMIC_PRI command is used. Priority can be a number from 0 to 199.
TERM_TYPE TN6530 | 6530 | ANSI | ANY
TERM_TYPE controls the inclusion of services on STN02 Service menus. The default is ANY. TN6530 and 6530 are
equivalent.
Workstation terminal emulators are divided into two groups. Those that support HP 6530 telnet extensions and which are
configured for the HP 6530 protocol are considered type TN6530; all others are considered type ANSI. For TN6530
emulators, the STN02 will include only those services with TERM_TYPE TN6530 or ANY. For ANSI (all other)
emulators, the STN02 will include only those services with TERM_TYPE ANSI or ANY.
TERM_TYPE only affects the display formatted for the STN02 Service menu. It does not restrict access to services or
otherwise affect application or terminal activity. For example, an ANSI emulator could request a service configured for
TERM_TYPE TN6530 even though the service name was not displayed on the STN02 service menu.
HP NonStop SSH Reference Manual STN Reference • 253