When a TN6530 client (terminal emulator) such as Win6530 or J6530 first connects to STN, several messages are displayed as the session is initiated. Each message begins with the letters "STN" followed by a two-digit message number for ease of identification.
STN00 Connected to STN version Axx <date/time> <window-name>
This is the first message displayed which confirms connection to STN (as distinct from Telserv or other Telnet servers). The STN version string is included. <window-name> is in the form
\node.$process.#window.
STN01 Host IP <h> <subnet> Port <p> <window-name>
This is the second message, which confirms the NSK host IP address <IP>, the TCP process name <subnet>, port number <p> and finally the full filename of the STN window in the form
\node.$process.#window. This information can be useful for support purposes.
STN02 Services:
This message precedes the list of services displayed.
STN03 Terminal type <ttype> is not supported
The TN6530 client (terminal emulator) sent a terminal type identifier unknown to STN. Verify that the terminal emulator is properly set for TN6530 emulation.
STN04 Connected to Dedicated Window <window>
This message indicates that the session has been automatically connected to a dedicated window named <window> whose IP address matches the remote workstation.
STN05 Dedicated Window(s) are configured for this workstation IP address, but are already in use or otherwise unavailable. Session terminated.
Self explanatory.
STN06
Reserved for future use.
STN07 SU Window not found
User entered #WINDOW name in response to the menu, but the specified window is not configured.
STN08 Window is not Type SU
User entered #WINDOW name in response to the menu, but the specified window is not configured as type SU.
STN09 Window is stopped by system operator
User entered #WINDOW name in response to the menu, but the specified window was stopped by STNCOM STOP/ABORT WINDOW command.
STN10 Connected to SU Window
User entered #WINDOW name in response to the menu, and the session was successfully connected to the requested window.
STN11 Service not found
User entered a service name in response to the menu, but the specified service is not configured.
STN12 Service is stopped by system operator
User entered a service name in response to the menu, but the specified service was stopped by STNCOM STOP/ABORT SERVICE command.
STN13 No Static Window available for this Service
User entered a service name in response to the menu, but the specified static service either has no windows configured, or all configured windows are in use or STOPPED.
STN14 Connected to Static Window <window>
User entered a service name in response to the menu, and the session was successfully connected to <window>, which was configured for the requested static service.
STN15 The Dynamic Service selected required a userid and password STN15 Enter group.user:
Self explanatory. Enter a valid username.
STN16 Enter password:
This prompt follows the response to STN15.
STN17 Input error; proper syntax is group.user
Improper response to STN15 prompt.
STN18 Unknown userid or incorrect password
Self explanatory.
STN19 Add Window failed for Dynamic Service
User entered a dynamic service name in response to the menu, but a new dynamic window could not be added, usually due to a resource shortage. Notify support.
STN20 Starting Dynamic Service application
STN is starting the application for the requested dynamic service.
STN21 Dynamic Service Application Creation Error
STN was not able to start the application for the requested dynamic service. An additional message STN22-STN34 is displayed with error details from PROCESS_CREATE_.
STN22 file error <fe> on PROGRAM file
PROCESS_CREATE_ error 1: File system status <fe> on PROGRAM file.
STN23 file error <fe> on LIB file
PROCESS_CREATE_ error 3: File system status <fe> on LIB file.
STN24 file error <fe> on SWAP file
PROCESS_CREATE_ error 5 or 6: File system status <fe> on SWAP file.
STN25 file error <fe> on HOME TERM file
PROCESS_CREATE_ error 8 or 9: File system status <fe> on HOME file.
STN26 CPU(s) configured for this service are down
PROCESS_CREATE_ error 10: none of the CPUs for this service are running.
STN27 file error <fe> on process name
PROCESS_CREATE_ error 11: File system status <fe> on HOME file.
STN28 PROGRAM file format error <detail>
PROCESS_CREATE_ error 12: PROGRAM file error, see detail.
STN29 LIB file format error <detail>
PROCESS_CREATE_ error 13: LIB file error, see detail.
STN30 no pcb available
PROCESS_CREATE_ error 15: no pcbs available.
STN31 unlicensed privileged program
PROCESS_CREATE_ error 17.
PROCESS_CREATE_ error 18.
STN33 PROG and LIB files the same
PROCESS_CREATE_ error 19.
STN34 process_create_ error <status> substatus <substatus>
PROCESS_CREATE_ error <status> with detail <substatus>.
STN35 **WARNING** Terminal will be disconnected if it stays idle...
Terminal has been idle and is within IDLE_WARNING minutes of BANNER_TIMEOUT or INPUT_TIMEOUT.
STN36 Terminal was idle too long! Disconnecting...
Terminal has been idle for BANNER_TIMEOUT or INPUT_TIMEOUT minutes.
STN37 BLAST <text>
System operator used STNCOM command BLAST to send <text> to all terminals.
STN38 No application program active on this terminal for nnn seconds. Session terminated.
At the beginning of a session, OPENER_WAIT seconds have elapsed and no application has opened the window.
STN39 Session terminated - application request (control 12) <time>
The application has disconnected the session via control 12. This is normal termination for some applications.
After session termination, 6530 terminals will always be left in conversational (ITI) mode, and the terminal display is erased.
STN39 Session terminated - application closed terminal <time>
The application has closed the window and AUTODEL_WAIT seconds have elapsed. This is normal termination for some applications.
After session termination, 6530 terminals will always be left in conversational (ITI) mode, and the terminal display is erased.
STN40 Operating in limited mode
If the STN LICENSE file has an EXPIRE date that has already passed, but the LICENSE parameters are otherwise valid, then STN will operate in limited mode with only two sessions allowed.
STN41 The requested dynamic service application was started, but did not connect to this Telnet window within 60 seconds. The application, and this Telnet session are being stopped.
This generally indicates a programming error in the application for the dynamic service. Contact the system administrator.
STN42 open (for startup message) error on process <p> fe <fe>
For dynamic windows, STN tried to open the newly created application process <p> to pass the startup message, but the open was rejected with file system error <fe>. Contact the system administrator.
STN43 write (for startup message) error on process <p> fe <fe>
For dynamic windows, STN opened the newly created application process <p> to pass the startup message, but the write was rejected with file system error <fe>. Contact the system administrator.
STN44 Application has connected to this window
STN has detected an open from the application program. The next message will be from the application (e.g. TACL prompt).
STN45 Maximum number of users exceeded - session will be terminated
The number of simultaneous active sessions exceeded the limit specified in the LICENSE file USERS parameter, or the limit of two when operating in limited mode.
STN46 Secure session: <SSL/TLS or SSH info>
This is an informational message to emphasize that the session is secure. Encryption details are provided.
STN47 Unencrypted session (not secure)
This is an informational message to emphasize that no encryption is being used for this session.
STN48 <window-or-service>
This is an informational message to echo the response to the menu prompt. This is especially useful when the service name is automatically entered by the terminal emulator.
STN50 Negotiation timeout - check Line Mode setting in terminal emulator. Session terminated.
Telnet IAC negotiations did not complete within 20 seconds.
STN51 Workstation IP address not in range for requested service
The IP address of the remote workstation is not defined in the IPRANGE, or the IPRANGE is not defined.
STN52 This Telnet Host requires encryption at the Telnet workstation.
A workstation emulator running in PLAIN mode (without SSL encryption) attempted to connect to an encrypted STN listener. The session is disconnected after a brief delay.
STN53 This telnet host does not support encryption at the workstation - session terminated.
A workstation emulator running with SSL encryption attempted to connect to a PLAIN
(unencrypted) STN listener. This message will usually not display on the emulator screen, but can be seen as plain text in network or sniffer traces.
STN54 session timed out waiting for user logon response
A session connected to a SERVICE with LOGON REQ, but the user did not respond to the logon prompt.
STN57 This 6530 emulator does not support required WSINFO
See STNCOM command WSINFO.
STN58 WSINFO address does not match network address
See STNCOM command WSINFO.
STN59 Input discarded
For an SSH session with no read active (TACL PAUSE-d etc), a very large amount of keyboard input was received. Further input is discarded.
STN70 Reconnecting to resilient window #ZWNnnnn
Connection to a resilient service where an existing window from a previous session has been reconnected to the current session
STN70 application $pname|pid xxxx xxxx|cpu,pin programfilename
When reconnecting to a resilient window, existing applications are listed for informational purposes.
STN71 Userid not allowed for this service
The selected SERVICE requires a specific userid.
STN72 Using userid from SSH
CI-SYSTEM-USER is being used instead of STN15/STN16 prompt
STN73 Using SSH_Default_Svc
CI-PROGRAM *MENU* (without anything following *MENU*) and the service specified by SSH_DEFAULT_SVC is used
STN74 Dynamic Service Session Limit Exceeded
SERVICE LIMIT exceeded