SSH Reference Manual

Running STN as Persistent Process
STN can be started as kernel persistent process from SCF. The IN field of the RUN STN command is used to convey
PARAM and STNCOM configuration information, as shown in the following example:
ADD PROCESS STN1
, NAME $STN1
, PROGRAM $SYSTEM.STN.STN
, INFILE $SYSTEM.STN.STN1KIN
, STARTMODE SYSTEM -or- APPLICATION
, USERID SUPER.SUPER
The INFILE (STN1KIN in this example) contains STNCOM commands to configure WINDOWs and SERVICEs, and
also may contain PARAM commands as described above, but should always include the following:
PARAM GFTCOM^OBJECT $SYSTEM.STN.STNCOM
PARAM GFTCOM^IN $SYSTEM.STN.STN1KIN
PARAM GFTCOM^OUT $ZHOME
BANNER $SYSTEM.STN.BANNER1
STNCOM
STNCOM is the system operator interface to STN. STNCOM provides for configuration, status, and maintenance
requests. You can store your STNCOM commands in an EDIT format disk file or enter them conversationally. You can
direct your output to a terminal, printer, disk file, or spooler. Standard OBEY and FC commands are provided. A built-in
HELP command is used; you can easily change the HELP dictionary or extend it to conform to local requirements by
modifying the supplied STNCHELP EDIT file. When STNCOM is run, an implied OPEN $STN command is issued
prior to prompting for input. STNCOM commands can be continued over multiple lines. When an ampersand ("&")
appears as the last character on a line, the command is continued with the first column of the next line. There is no limit
on the number of lines over which a command may be continued, but commands are limited to 10240 characters. Prior to
STN version B24 the limit was 1024 characters. If STNCOM is prompting at a terminal for input, the prompt for
continuation lines will be the current prompt prefixed by ampersand ampersand space: "&& ". Continuations are allowed
from terminals, IN files and OBEY files.
Starting with version B08, responses to incorrect STNCOM commands will be preceded and followed by lines
containing "*** Error ***".
To start STNCOM, use the standard TACL RUN command, as shown in the following examples:
1> RUN stncom $stn
2> stncom $stn1 ; info stn ; e
3> stncom / IN stnin4 , OUT $s /
4> stncom $stn1 ; TRACE $system.stn.trace3,1M ; e
The following illustrates a sample session:
STNCOM T0801H01_23JAN2012_ABA
OPEN $STN
% info service
info service
SERVICE TACL
TYPE DYNAMIC
PROG $SYSTEM.SYSTEM.TACL
% version
version
248 • STN Reference HP NonStop SSH Reference Manual