Telserv Manual Abstract This manual describes the HP NonStop™ Telserv subsystem. Part I contains a product overview. Part II contains operational and configuration information for system administrators, operators, support planners. Part III contains information for interactive terminal users. Part IV contains information for programmers. Product Versions G06 (G-series), H01 (H-series and J-series) Supported Release Version Updates (RVUs) This guide supports the G06.24 and all subsequent G-series RVUs, H06.
Document History Part Number Product Version Published 427174-004 Telserv G06 December 2003 424174-005 Telserv G06 (G-series) Telserv H01 (H-series) July 2005 424174-006 Telserv G06 (G-series) Telserv H01 (H-series and J-series) February 2010 424174-007 Telserv G06 (G-series) Telserv H01 (H-series and J-series) December 2010 424174-008 Telserv G06 (G-series) Telserv H01 (H-series and J-series) April 2013 424174-009 Telserv G06 (G-series) Telserv H01 (H-series and J-series) October 2013
Legal Notices Copyright 2013 Hewlett-Packard Development Company L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Telserv Manual Glossary Index Figures Tables Legal Notices What’s New in This Manual ix Manual Information ix New and Changed Information x About This Manual xi Who Should Read This Guide xi How This Guide Is Organized xi Related Documentation xii Notation Conventions xiii Part I. Overview 1. The TELNET Server (Telserv) Interactive Interface 1-3 Programmatic Interface 1-3 Part II. Configuration and Management 2. Configuration Quick Start 3.
Contents 5.
Contents 5.
6. Using PTrace Contents TRACE Command 5-45 Examples of the TRACE Command 5-49 VERSION Command 5-49 VERSION PROCESS Command 5-49 VERSION null Command 5-50 Examples of the VERSION Command 5-50 6. Using PTrace Device Type and Subtype 6-1 PTrace Commands 6-1 SELECT Command 6-1 Part III. Accessing and Using Telserv from a Terminal 7. Accessing and Using Telserv Services The TELNET Protocol 7-2 Modes of Operation 7-2 Line Mode and Character Mode ASCII and Binary Mode 7-2 7-2 8.
10. Modes of Operation Contents ttywritesz Command 9-9 TELNET Commands 9-9 Part IV. Programming Information 10. Modes of Operation A. Telserv Error Messages Sent to Terminals Recovering From Errors A-1 TELNET Error Messages A-1 Telserv Error Messages A-7 B. SCF Error Messages for Telserv C.
Glossary Contents START WINDOW Command C-6 STATS Command C-7 STATS PROCESS C-7 STATS SERVICE C-7 STATS WINDOW C-7 STATUS Command C-7 STATUS PROCESS C-7 STATUS WINDOW C-7 STOP Command C-8 STOP PROCESS C-8 STOP WINDOW C-8 TRACE Command C-8 TRACE PROCESS C-9 TRACE WINDOW C-10 VERSION Command C-10 VERSION PROCESS C-10 VERSION null C-10 Glossary Index Figures Figure 1-1. Figure 4-1. Figure 4-2. Figure 10-1.
Contents Telserv Manual—427174-009 vii
Contents Telserv Manual—427174-009 viii
What’s New in This Manual Manual Information Telserv Manual Abstract This manual describes the HP NonStop™ Telserv subsystem. Part I contains a product overview. Part II contains operational and configuration information for system administrators, operators, support planners. Part III contains information for interactive terminal users. Part IV contains information for programmers.
New and Changed Information What’s New in This Manual New and Changed Information Changes in 424174-009 Added the section Considerations for the NAMES null Command on page 5-35 Updated the section Programmatic Interface on page 1-3 Updated the section Subsystem Control Point (SCP) on page 4-2 Changes in 424174-008 Updated the section PROCESS Object on page 5-3. Changes in 424174-007 This manual has been updated to reflect support of a new PARAM that is used to bind Telserv to an IP address.
About This Manual This section includes the following information: Who Should Read This Guide How This Guide Is Organized Related Documentation Notation Conventions Notation Conventions The Telserv Manual provides information about the HP TELNET Server (Telserv) subsystem.
Related Documentation About This Manual Section 5, Subsystem Control Facility (SCF) Commands for Telserv lists all SCF commands, objects, and object attributes for the Telserv subsystem. Section 6, Using PTrace contains the subsystem-specific details for using PTrace to format Telserv subsystem trace files created through the use of the SCF TRACE command.
Notation Conventions About This Manual PTrace Reference Manual TACL Reference Manual Operator Messages Manual OSM Users’ Guide For information about TCP/IP and TELNET, you can consult the following manuals: TCP/IP Applications and Utilities User Guide For G-series: TCP/IP Configuration and Management Manual TCP/IP (Parallel Library) Configuration and Management Manual TCP/IPv6 Configuration and Management Manual For H-series and J-series: TCP/IP Configuration and Management Manual TCP/IPv6 C
General Syntax Notation About This Manual italic computer type. Italic computer type letters within text indicate C and Open System Services (OSS) variable items that you supply. Items not enclosed in brackets are required. For example: pathname [ ] Brackets. Brackets enclose optional syntax items. For example: TERM [\system-name.]$terminal-name INT[ERRUPTS] A group of items enclosed in brackets is a list from which you can choose one item or none.
Notation for Messages About This Manual Quotation marks around a symbol such as a bracket or brace indicate the symbol is a required character that you must type as shown. For example: "[" repetition-constant-list "]" Item Spacing. Spaces shown between items are required unless one of the items is a punctuation symbol such as a parenthesis or a comma. For example: CALL STEPMOM ( process-id ) ; If there is no space between two items, spaces are not permitted.
Notation for Messages About This Manual Bold Text. Bold text in an example indicates user input typed at the terminal. For example: ENTER RUN CODE ?123 CODE RECEIVED: 123.00 The user must press the Return key after typing the input. Nonitalic text. Nonitalic letters, numbers, and punctuation indicate text that is displayed or returned exactly as shown. For example: Backup Up. lowercase italic letters. Lowercase italic letters indicate variable items whose values are displayed or returned.
Change Bar Notation About This Manual % Percent Sign. A percent sign precedes a number that is not in decimal notation. The % notation precedes an octal number. The %B notation precedes a binary number. The %H notation precedes a hexadecimal number. For example: %005400 %B101111 %H2F P=%p-register E=%e-register Change Bar Notation Change bars are used to indicate substantive differences between this manual and its preceding version.
Change Bar Notation About This Manual Telserv Manual—427174-009 xviii
Part I.
Part I.
1 The TELNET Server (Telserv) For HP NonStop™ systems, the HP Telserv subsystem is the implementation of the server portion of the TELNET protocol. The TELNET protocol is a general, bidirectional, 8-bit, byte-oriented protocol in the TCP/IP protocol suite. It specifies how terminal devices and terminal-oriented processes must interface. Telserv runs on a NonStop system as an operating-system process and uses the socket library routines of the TCP/IP software for TCP access.
The TELNET Server (Telserv) Figure 1-1 shows the Telserv process on a NonStop S-series server A communicating with two client applications. NonStop server B shows an HP TELNET client communicating with Telserv. This figure also shows a non-HP client application communicating with Telserv. This non-HP client could use Telserv to access host processes or files. Figure 1-1.
Interactive Interface The TELNET Server (Telserv) Interactive Interface The Telserv subsystem is managed by entering interactive (SCF) commands that affect the operation of subsystem objects.
Programmatic Interface The TELNET Server (Telserv) Telserv Manual—427174-009 1-4
Part II.
Part II.
2 Configuration Quick Start Starting the Telserv subsystem requires only a single operation. Simply issue a TACL RUN command to create the Telserv process. Before issuing the RUN command, make sure that the underlying protocol stack is up and running. You can also (but need not) use the TACL PARAM command to specify certain parameters that determine operational aspects of the Telserv process (see Telserv Parameter Names and Values for the TACL PARAM Command on page 3-1).
Configuration Quick Start Launch specified programs Provide recovery from network and system failures (called a resilient session) The WINDOW object is the virtual terminal through which a user’s data can be sent and received after undergoing transformation to HP NonStop TELNET semantics. The WINDOW object provides the interface between a client application and the Telserv process.
3 Starting the Telserv Process Port 23 is the well-known port that is reserved for TELNET communication. When you start an HP Telserv process, if you don’t specify a port number in the RUN command, the process uses port 23 by default. To run multiple Telserv processes per TCP/IP process, you must configure each additional Telserv process to communicate over another port.
Starting the Telserv Process Telserv Parameter Names and Values for the TACL PARAM Command Table 3-1 lists all parameter names and values supported for the HP Telserv process. Table 3-1. Telserv Parameter Names and Values in the TACL PARAM Command (page 1 of 9) Name Description ZTNT^TACL^PROGRAM Specifies the file name of a TACL program other than the default. When TACL is chosen, this alternate TACL program is used.
Starting the Telserv Process Telserv Parameter Names and Values for the TACL PARAM Command Table 3-1. Telserv Parameter Names and Values in the TACL PARAM Command (page 2 of 9) Name Description ZTNT^ECHO^SPL^CHAR Allows the Telserv process to suppress the echoing of Special Characters (Line Kill, End Of File, and Erase Character) after the DONT ECHO option is negotiated. Setting PARAM ZTNT^ECHO^SPL^CHAR to OFF enables this behavior.
Telserv Parameter Names and Values for the TACL PARAM Command Starting the Telserv Process Table 3-1. Telserv Parameter Names and Values in the TACL PARAM Command (page 3 of 9) Name Description ZTNT^ATP^COMPATIBLE Enables or disables certain features similar to those in the ATP6100 product. Values are YES or NO. The default value is NO.
Starting the Telserv Process Telserv Parameter Names and Values for the TACL PARAM Command Table 3-1. Telserv Parameter Names and Values in the TACL PARAM Command (page 4 of 9) Name Description ZTNT^CUSTOM^BANNER Specifies whether or not Telserv sends a customized welcome banner instead of the default welcome banner. Values are YES or NO. The default value is NO.
Starting the Telserv Process Telserv Parameter Names and Values for the TACL PARAM Command Table 3-1. Telserv Parameter Names and Values in the TACL PARAM Command (page 5 of 9) Name Description ZTNT^KEEPALIVE^OFF Specifies whether to disable the KEEPALIVE socket option. Values are YES or NO. The default value is NO. The syntax is: PARAM ZTNT^KEEPALIVE^OFF (YES | NO) Setting the PARAM value to YES disables the KEEPALIVE functionality.
Telserv Parameter Names and Values for the TACL PARAM Command Starting the Telserv Process Table 3-1. Telserv Parameter Names and Values in the TACL PARAM Command (page 6 of 9) Name Description ZTNT^LOG^CONNECTS Enables or disables the generation of EMS messages when a client connects to or disconnects from Telserv. Values are YES or NO. The default value is NO.
Starting the Telserv Process Telserv Parameter Names and Values for the TACL PARAM Command Table 3-1. Telserv Parameter Names and Values in the TACL PARAM Command (page 7 of 9) Name Description ZTNT^LOG^SERVICENAME Displays the service name chosen, in the CONNECT and DISCONNECT EMS event messages, in the case of login failure. Use this PARAM in conjunction with ZTNT^LOG^CONNECTS. The syntax is: PARAM ZTNT^LOG^SERVICENAME (YES|NO) The DEFAULT value is NO.
Telserv Parameter Names and Values for the TACL PARAM Command Starting the Telserv Process Table 3-1. Telserv Parameter Names and Values in the TACL PARAM Command (page 8 of 9) Name Description ZTNT^SENDBRK^ON^DISCONN Specifies whether or not a break message is sent to the break owner when a session terminates. V The syntax is: PARAM ZTNT^SENDBRK^ON^DISCONN (YES|NO) Values are YES or NO. The default value is NO.
Using the RUN Command and Specifying Run Options Starting the Telserv Process Table 3-1. Telserv Parameter Names and Values in the TACL PARAM Command (page 9 of 9) Name Description ZTNT^SERVICECHOICE^ECHO Enables or disables the echoing of user input before Telserv accepts the service chosen by the user. The Values are YES or NO. The default value is YES. The syntax is: PARAM ZTNT^SERVICECHOICE^ECHO (YES | NO) Setting this PARAM value to YES or allowing it to default causes Telserv to echo user input.
Using the RUN Command and Specifying Run Options Starting the Telserv Process an ampersand (&) at the end of each broken line (as shown in the example following the syntax information). RUN [ [ [ [ [ [ [ [ [ [ [ [ [ [ $volume.subvolume.
Using the RUN Command and Specifying Run Options Starting the Telserv Process -7 indicates that data is transferred between the server and client in 7-bit format and in ASCII code. Therefore, this format cannot be used when you are transferring binary data. If you do not specify this option, the 8-bit format is used. If the client negotiates terminal type with Telserv and the terminal type name is TN6530, the data is transferred in 7-bit format regardless of the default data transmission.
Using the RUN Command and Specifying Run Options Starting the Telserv Process to pause and restart rapidly scrolling text on the terminal. SETMODE 264 provides the programmatic interface. For information about SETMODE procedures, see the Guardian Procedure Calls Reference Manual. [ -KANJI ] makes the backspace (BS) key operational when you use TELSERV in binary mode (for example, with clients that work in the Kanji environment). Each keystroke erases one character from the terminal display.
Binding Telserv to an IP Address Starting the Telserv Process If you do not specify this option, a selection prompt is displayed. [ -NOTACL ] specifies that TACL is not displayed as one of the services in the selection menu. If you do not specify this option, TACL appears as a service on the selection menu. [ -XTABS | -NOXTABS ] determines whether or not TAB characters are converted to spaces. SETMODE 261 provides the programmatic interface.
Fault Tolerance Starting the Telserv Process which you want Telserv to service connections. Use the DEFINE and PARAM commands to perform this task.
Altering and Stopping a Telserv Process Starting the Telserv Process Whenever a takeover occurs, Telserv makes the configuration data (specified through SCF or through a management program) available to the backup process taking control. Thus, you need not reconfigure the Telserv process manually. Configuration data, when input to the Telserv process, is saved to an ENSCRIBE, key-structured file.
4 Subsystem Control Facility (SCF) for Telserv This section provides background information essential to managing the HP Telserv subsystem interactively through the use of the Subsystem Control Facility (SCF). Topics covered here include: General information on SCF operation Prerequisites Compatibility information. Definition and discussion of SCF objects for Telserv SCF Operation SCF is used to configure, control, and collect information about NonStop data communications subsystems.
Subsystem Control Point (SCP) Subsystem Control Facility (SCF) for Telserv Figure 4-1. SCF Overview SCF SCP ($ZNET) Telserv Command (Obey) VST 002.VSD Subsystem Control Point (SCP) The Subsystem Control Point (SCP) is a network-management process for receiving and redistributing the messages that SCF sends to certain data communications subsystems like Telserv. SCP lies between SCF and Telserv.
Subsystem Control Facility (SCF) for Telserv SCF Commands response, and event-message buffers. SPI is described in the Distributed Systems Management (DSM) Programming Manual. SCF Commands Several commands are available for displaying and changing SCF session parameters. Table 4-1 shows these commands and their effects. Table 4-1. Changing SCF Session Parameters Command Effect ASSUME defines a default object to be used when the object is omitted from an SCF command.
Subsystem Control Facility (SCF) for Telserv Sensitive and Nonsensitive Commands Sensitive and Nonsensitive Commands Because some commands can have detrimental effects if improperly used, special qualification is required to use them. These commands are called sensitive commands. A sensitive command is one that can be issued only by a user with super-group access, the owner of the subsystem, or a member of the same group as the owner of the subsystem.
Subsystem Control Facility (SCF) for Telserv States the subordinate objects are affected. ALL specifies that the named object and the subordinate objects are affected. If subtype is omitted, ALL is assumed. States Objects can have operational states, such as STOPPED or STARTED. The exact sequence of states an object goes through varies from object to object and from subsystem to subsystem. SCF commands for the Telserv subsystem recognize only two states: STOPPED and STARTED.
Subsystem Control Facility (SCF) for Telserv Modes of Operation Modes of Operation SCF can be run in two modes: interactive or noninteractive. Because interactive and noninteractive input are treated differently by SCF, the following distinctions are important: The mode is interactive when both input and output pass through the same terminal, or when the same process is used for both input and output.
Subsystem Control Facility (SCF) for Telserv Setting the Initial Output Destination Setting the Initial Output Destination To specify an initial output destination for an SCF session, use the OUT option of the RUN command. You can specify a terminal (identified by its logical-device name), a disk file, an application process, or a printer. For example, the following RUN command initiates SCF and directs it to send its output to a disk file named $DATA.SCF.
SCF Online Help Subsystem Control Facility (SCF) for Telserv SCF commands for Telserv permit the use of the command parameter SUB. You can use SUB to specify which subordinate objects the command affects. For example, you may want to get information for all the Telserv objects subordinate to a Telserv process. One way to do this is with the following command: INFO PROCESS $ZNT, SUB ALL Specific information about the format of each SCF command appears in Appendix C, SCF Command Syntax.
Subsystem Control Facility (SCF) for Telserv Prerequisites Prerequisites The Telserv subsystem requires the NonStop TCP/IP subsystem, the Parallel Library TCP/IP subsystem, the NonStop TCP/IPv6 subsystem, or the NonStop IPX/SPX subsystem. The Telserv subsystem and the TCP/IP subsystem each run one process. After creating the process, you define virtual terminals by adding windows. Note. H-series and J-series systems do not support Parallel Library TCP/IP or NonStop IPX/SPX.
Subsystem Control Facility (SCF) for Telserv PROCESS Object are to be changed and what the new value is to be. Details on the required syntax for each command you can use with the Telserv subsystem are provided in Appendix C, SCF Command Syntax. PROCESS Object A PROCESS is a subsystem that implements the Telserv protocol. Naming Conventions for the Object Starting the Telserv process involves specifying a name that you will later use in your management commands.
Subsystem Control Facility (SCF) for Telserv WINDOW Object A service name is fully qualified to the Telserv subsystem by preceding it with the process name the service is to be associated with. For example: $ZNT01.SERVICE1 WINDOW Object The WINDOW object is the virtual terminal through which a user’s data can be sent and received after undergoing the appropriate transformation to Telserv semantics. The WINDOW object provides the interface between a client application and the Telserv process.
Subsystem Control Facility (SCF) for Telserv WINDOW Object client who selects a valid service. Thus, a given client might not get the same window for each session it establishes. To configure a static window, use a non-null string for the SERVICENAME attribute of the WINDOW object. For example: SCF> ADD WINDOW #win, SERVICENAME “myserv” Multiple static windows can have the same service name. Clients can access static windows only by specifying the service name (for example, myserv).
Object-Name Templates Subsystem Control Facility (SCF) for Telserv SU Windows SU windows support applications that must keep the context of the previous session when the client reconnects. To configure an SU window, use a null string for the SERVICENAME attribute of the WINDOW object. For example: ADD WINDOW #win, SERVICENAME "" Only one SU window exists for each Telserv process. Clients can access SU windows only by specifying the window name (for example, #win).
Subsystem Control Facility (SCF) for Telserv ? Object-Name Templates A trailing string; for example, $ZTNT.#WI* selects all objects subordinate to $ZTNT that have names starting with #WI. An undefined number of characters; for example, $ZTNT*5 selects all names that start with $ZTNT and end with 5. Use the question mark to represent an unknown character in a specific position; for example, $ZTNT.
5 Subsystem Control Facility (SCF) Commands for Telserv Table 5-1 lists the SCF commands you can use with the HP Telserv subsystem. The table shows the object types to which each command applies. Table 5-1.
Subsystem Control Facility (SCF) Commands for Telserv ABORT Command cannot. In addition, sensitive commands can be issued only by users in the SUPER group or issued by any valid user on the system. ABORT Command The ABORT PROCESS command forces the Telserv subsystem to shut down, without considerations for data integrity. All outstanding requests are returned with the File System error 201. The sockets are closed and the specified process terminates abnormally (ABEND).
Subsystem Control Facility (SCF) Commands for Telserv Examples of the ABORT Command PROCESS Object Use the STOP PROCESS command for more controlled termination of a process. Use the SAVEABEND option to specify whether a saveabend file should be created. Specify ON to create a saveabend file. Specify OFF to suppress the creation of a saveabend file. The default value is ON. WINDOW Object ABORT WINDOW is a sensitive command.
ADD SERVICE Command Subsystem Control Facility (SCF) Commands for Telserv The ADD command has the following object-spec: object-type object-name SERVICE WINDOW service-name window-name ADD SERVICE Command The attribute-specs for the SERVICE object are: [ [ [ [ [ [ [ [ [ [ [ [ [ [ { ACCESS { ALL | SYSTEM | OWNER | NONE } ASSIGNED { ON | OFF } AUTODELETE { ON | OFF } CPU { 0 through 15 } DEFAULT { ON | OFF } DISPLAY { ON | OFF } LIB file-name OWNER "24-char" PARAM "128-char" PRI { 0 through 190 } PROGR
Subsystem Control Facility (SCF) Commands for Telserv ADD SERVICE Command AUTODELETE automatically deletes a SERVICE when all WINDOWS associated with that service are deleted. The default is OFF. CPU identifies the CPU to use to NEWPROCESS the file-name identified in PROGRAM. If CPU is not specified, Telserv communicates with CMON to determine which CPU to use. This attribute is invalid if PROGRAM is not specified and is rejected with Telserv error 4.
Subsystem Control Facility (SCF) Commands for Telserv ADD SERVICE Command PRI specifies the program’s priority, otherwise, Telserv uses its own priority minus one. This attribute is invalid if PROGRAM is not specified and is rejected with Telserv error 4. PROGRAM contains the local file name of the initial program to be launched by the Login Server when a session is established. Invalid or inaccessible file names are rejected with Telserv error 11.
Subsystem Control Facility (SCF) Commands for Telserv ADD WINDOW Command CONVERSATION configures a conversational terminal service and initiates the session in conversation mode. PRINT configures a printer (write-only device) service.
Subsystem Control Facility (SCF) Commands for Telserv ADD WINDOW Command ENDOFLINE is a 1-byte ASCII value used to signify that an input line is complete. The default value is a CARRIAGE-RETURN (%H0C in hexadecimal). This attribute is valid only when SERVICETYPE is set to conversation mode. ERASE is a 1-byte ASCII value used to erase a single character of input. The default value is a BACKSPACE (%H08 in hexadecimal). This attribute is valid only when SERVICETYPE is set to conversation mode.
Subsystem Control Facility (SCF) Commands for Telserv Considerations for the ADD Command PRINT indicates that the SERVER may initiate a connection, thus allowing a printer (write-only device) to be configured. Considerations for the ADD Command The considerations contain information about command use that should be read before studying the command syntax in detail. All Objects ADD is a sensitive command. SERVICE Object A PROGRAM attribute is required for DYNAMIC services.
Subsystem Control Facility (SCF) Commands for Telserv Considerations for the ADD Command The following example adds a window for a printer connection: ADD WINDOW $ZTNT.
ALTER Command Subsystem Control Facility (SCF) Commands for Telserv ALTER Command The ALTER command changes attribute values associated with the specified PROCESS, SERVICE, or WINDOW. The ALTER SERVICE command can only be issued when all subordinate windows are in the STOPPED summary state. The ALTER WINDOW command can only be issued when the window is in the STOPPED state. ALTER is a sensitive command. ALTER [ / OUT file-spec / ] [ object-spec ] { , attribute-spec [ , attribute-spec ] ...
Subsystem Control Facility (SCF) Commands for Telserv ALTER PROCESS Command TIMEOUTVALUE is the time (in minutes) after which inactive terminals are disconnected. If a terminal had been logged on, it is logged off and disconnected. The value 32767 indicates infinite time. If inactive terminals are not to be disconnected, 32767 should be specified. The default value is 32767.
ALTER SERVICE Command Subsystem Control Facility (SCF) Commands for Telserv ALTER SERVICE Command The attribute-specs for the SERVICE object are: [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ ACCESS { ALL | SYSTEM | OWNER | NONE } ASSIGNED { ON | OFF } AUTODELETE { ON | OFF } CPU { 0 through 15 } DEFAULT { ON | OFF } DISPLAY { ON | OFF } LIB file-name OWNER "24-char" PARAM "128-char" PRI { 0 through 190 } PROGRAM file-name RESILIENT { ON | OFF } SUBTYPE { DYNAMIC | STATIC } SWAP file-name TYPE { BLOCK | CONVERSATION | P
Subsystem Control Facility (SCF) Commands for Telserv ALTER SERVICE Command DEFAULT allows the user to specify a default SERVICE to be automatically accessed when a connection is established, bypassing the welcome menu and service selection options. The default value is OFF. Each Telserv process can have only one DEFAULT service. If an attempt is made to specify more than one DEFAULT service the command is rejected with Telserv error 19.
Subsystem Control Facility (SCF) Commands for Telserv ALTER SERVICE Command PRI specifies the program’s priority. Otherwise, Telserv uses its own priority minus one. This attribute is invalid if PROGRAM is not specified and is rejected with Telserv error 4. PROGRAM contains the local file name of the initial program to be launched by the Login Server when a session is established. Invalid or inaccessible file names are rejected with Telserv error 11.
ALTER WINDOW Command Subsystem Control Facility (SCF) Commands for Telserv CONVERSATION configures a conversational terminal service and initiates the session in conversation mode. PRINT configures a printer (write-only device) service.
Subsystem Control Facility (SCF) Commands for Telserv Considerations for the ALTER Command ENDOFLINE is a 1-byte ASCII value used to signify that an input line is complete. The default value is a CARRIAGE-RETURN (%H0C in hexadecimal). This attribute is valid only when SERVICETYPE is set to conversation mode. ERASE is a 1-byte ASCII value used to erase a single character of input. The default value is a BACKSPACE (%H08 in hexadecimal).
Subsystem Control Facility (SCF) Commands for Telserv Examples of the ALTER Command Use the INFO SERVICE command with the SUB ALL syntax to view all windows subordinate to a service. Use the STOP WINDOW command to stop each window subordinate to a service. WINDOW Object ALTER WINDOW is a sensitive command. The WINDOW object must be in the STOPPED summary state before its attributes can be altered.
Subsystem Control Facility (SCF) Commands for Telserv Examples of the ALTER Command SERVICE Object ALTER SERVICE $znt.
Subsystem Control Facility (SCF) Commands for Telserv DELETE Command DELETE Command The DELETE command removes a SERVICE or WINDOW from the subsystem. The DELETE SERVICE command removes an existing SERVICE object. If SUB ALL is specified, the command will delete the specified SERVICE and all subordinate windows. All subordinate windows must first be in the STOPPED summary state. Issue an INFO SERVICE command with the SUB ALL option to obtain a listing of the subordinate window objects.
Subsystem Control Facility (SCF) Commands for Telserv Examples of the DELETE Command All Objects DELETE is a sensitive command. When the DELETE operation finishes, any windows you specified for deletion are removed from the subsystem. This command reverses the effect of the ADD command. Examples of the DELETE Command The examples are designed to show correct ways of specifying command syntax. SERVICE Object DELETE SERVICE $ztnt.
INFO PROCESS Command Subsystem Control Facility (SCF) Commands for Telserv INFO PROCESS Command The syntax for the INFO PROCESS command is: INFO [ / OUT file-spec / ] PROCESS process-name [ , SUB [ NONE | ALL | ONLY ] ] [ , DETAIL ] The display for the INFO PROCESS command without the DETAIL option is: TELSERV Info PROCESS *Max Terminals 256 Total Terminals 0 *Timeout Value 3 Port 9876 Max Terminals is the maximum number of terminals that can be present in the system.
Subsystem Control Facility (SCF) Commands for Telserv INFO PROCESS Command BCPU is the backup process CPU. PPIN is the primary process PIN. BPIN is the backup process PIN. TACL ON indicates that TACL should be one of the services listed in the service menu at the beginning of an incoming session. Transport Process is the name of the transport process in use. Menu is the service menu. ON indicates the service menu should be displayed at the beginning of an incoming session.
INFO SERVICE Command Subsystem Control Facility (SCF) Commands for Telserv Total Terminals is the number of terminals. Program is the name of the program that this process was started from. CPU List is the list of processors on which the application can be launched when no CPU attribute is specified for the SERVICE object and the $CMON process is not available on the system.
INFO SERVICE Command Subsystem Control Facility (SCF) Commands for Telserv Display indicates whether or not service names are displayed in the Service Menu. ON indicates that service names should be displayed in the Service Menu at the beginning of an incoming session. OFF indicates that service names should not be displayed in the Service Menu at the beginning of an incoming session. Program is the local file name of the initial program to be launched by the Login Server when a session is established.
INFO WINDOW Command Subsystem Control Facility (SCF) Commands for Telserv Access is the authorized access for this service. CPU is the CPU to use to NEWPROCESS the program identified in the Program field. Pri specifies the program's priority. Swap is a local volume name used for the Program swap file. Program is the local file name of the initial program to be launched by the Login Server when a session is established.
INFO WINDOW Command Subsystem Control Facility (SCF) Commands for Telserv Service Name is the name of the service associated with this terminal. Service Type is the type of the service associated with this window. Local Port is the local TCP port number for this connection. This field is valid only when TCP is the transport layer used. Foreign IP Address is the IP address of the remote machine for this connection. This field is valid only when TCP is the transport layer used.
Subsystem Control Facility (SCF) Commands for Telserv INFO WINDOW Command End-of-Line is the one-byte character value used to signify that an input line is complete. Interrupt is the one-byte character value used to send a break message to the process that owns the break on the terminal. Service Type is the type of the service associated with this window. Service Name is the name of the service associated with this terminal. Local Port is the local TCP port number for this connection.
Subsystem Control Facility (SCF) Commands for Telserv Considerations for the INFO Command Netware Remote Address is the remote Netware address associated with this connection. This field is valid only when SPX is the transport layer used. The format of this value is the same as that for Netware Local Address. Considerations for the INFO Command The considerations contain information about command use that should be read before studying the command syntax in detail.
Subsystem Control Facility (SCF) Commands for Telserv LISTOPENS Command LISTOPENS Command The LISTOPENS PROCESS command displays information about the openers of the Telserv server process. The LISTOPENS WINDOW command identifies applications that have opened the specified window.
Subsystem Control Facility (SCF) Commands for Telserv LISTOPENS WINDOW Command BCPU is the backup CPU of the opener process. BPIN is the backup PIN of the opener process. BLFN is the logical file number of the backup opener process. Service is the service name of the window.
Subsystem Control Facility (SCF) Commands for Telserv Examples of the LISTOPENS Command BPIN is the backup PIN of the opener process. BLFN is the logical file number of the backup opener process. Service is the service name of the window. Examples of the LISTOPENS Command The examples are designed to show correct ways of specifying command syntax.
NAMES Command Subsystem Control Facility (SCF) Commands for Telserv NAMES Command The NAMES command lists the names and types of all, or a subset of, the objects known to the subsystem. You can use an object-name template with this command.
NAMES SERVICE Command Subsystem Control Facility (SCF) Commands for Telserv NAMES SERVICE Command The syntax for the NAMES SERVICE command is: NAMES [ / OUT file-spec / ] SERVICE service-name [ , SUB [ NONE | ALL | ONLY ] ] The display for the NAMES SERVICE command is: TELSERV Names SERVICE \COMM.WINSERV SERVICE WINSERV TACL ZVTL ZTELNET ZBLOCK ZCONV ZPRINT WINDOW #WIN SERVICE lists the SERVICE objects. WINDOW lists the WINDOW objects.
Considerations for the NAMES null Command Subsystem Control Facility (SCF) Commands for Telserv The display for the NAMES null command is: TELSERV Names PROCESS \COMM.$MTNT PROCESS $MTNT SERVICE WINSERV TACL ZVTL ZTELNET ZBLOCK ZCONV ZPRINT ZSPI WINDOW #WIN PROCESS lists the PROCESS objects. SERVICE lists the SERVICE objects. WINDOW lists the WINDOW objects. Considerations for the NAMES null Command Use the ASSUME PROCESS command before issuing this command.
Subsystem Control Facility (SCF) Commands for Telserv START WINDOW Command START WINDOW Command The START WINDOW command initiates the operation of a window and places the window in the STARTED summary state. You can use an object-name template with this command. START [ / OUT file-spec / ] WINDOW window-name Considerations for the START WINDOW Command The considerations contain information about command use that should be read before studying the command syntax in detail.
STATS PROCESS Command Subsystem Control Facility (SCF) Commands for Telserv The STATS command has the following object-spec: object-type object-name PROCESS SERVICE WINDOW process-name service-name window-name STATS PROCESS Command The syntax for the STATS PROCESS command is: STATS [ / OUT file-spec / ] PROCESS process-name [ , SUB [ NONE | ALL | ONLY ] ] [ , RESET ] The display for the STATS PROCESS command is: TELSERV Stats PROCESS \COMM.$MTNT Sample Time............ 22 Jul 1994, 11:39:55.
Subsystem Control Facility (SCF) Commands for Telserv STATS SERVICE Command Total Net Data is the total number of bytes received from the network. Total User Data is the total number of bytes sent by the user to the network. Total Net Requests is the total number of packets received from the network. Total User Requests is the total number of user requests.
STATS WINDOW Command Subsystem Control Facility (SCF) Commands for Telserv Aborts is the number of connections aborted because the client could not be authenticated, the client did not have sufficient privileges to access the service, or the login process was not able to launch the initial program. Inuses is the maximum number of windows in use at sample time. The number of windows in use cannot be reset with the RESET option.
Subsystem Control Facility (SCF) Commands for Telserv Considerations for the STATS Command Write Requests are the number of write requests posted by the user. Writeread Reqs are the number of writeread requests posted by the user. Control Reqs are the number of control requests posted by the user. Setmode Reqs are the number of SETMODE requests performed by the user. Cancel Reqs are the number of requests that were canceled before completion by the user.
Subsystem Control Facility (SCF) Commands for Telserv Examples of the STATS Command WINDOW Object The following command displays statistics for all windows under the assumed process. STATS WINDOW * The following command displays statistics for the assumed process and then resets the counters to zero. STATS PROCESS, RESET The next command displays statistics for the window #WN1 under the assumed process.
Subsystem Control Facility (SCF) Commands for Telserv STATUS Command STATUS Command The STATUS command displays the status of the specified object. You can use an object-name template the STATUS WINDOW command.
STATUS WINDOW Command Subsystem Control Facility (SCF) Commands for Telserv STATUS WINDOW Command The syntax for the STATUS WINDOW command is: STATUS [ / OUT file-spec / ] WINDOW window-name [ , DETAIL ] The display for the STATUS WINDOW command without the DETAIL option is: TELSERV Status WINDOW Name #PTY0007 Status STARTED Data Transmission 8BITS Name is the name of the WINDOW object. Status is the summary state of the object. Data Transmission is the number of bits used in transmission.
Subsystem Control Facility (SCF) Commands for Telserv Examples of the STATUS Command The STATUS command reports on, but does not change, the summary state of specified objects. STATUS is a nonsensitive command; any valid user on the system can issue this command. PROCESS Object Use the STATUS PROCESS with the SUB ALL syntax to display the status of all the WINDOWS in the subsystem. Use the INFO PROCESS command to view the current attribute settings.
Subsystem Control Facility (SCF) Commands for Telserv STOP PROCESS Command STOP PROCESS Command The syntax for the STOP PROCESS command is: STOP [ / OUT file-spec / ] PROCESS [ process-name ] STOP WINDOW Command The syntax for the STOP WINDOW command is: STOP [ / OUT file-spec / ] WINDOW [ window-name ] Considerations for the STOP Command The considerations contain information about command use that should be read before studying the command syntax in detail. All Objects STOP is a sensitive command.
TRACE Command Subsystem Control Facility (SCF) Commands for Telserv To examine trace files, use the formatter available with the PTrace program. The PTrace program is described in Section 6, Using PTrace. Caution. The trace operation can significantly increase CPU use by the Telserv process. To avoid problems with other processes in the CPU, you should lower the priority of the Telserv process before you issue the TRACE command.
Subsystem Control Facility (SCF) Commands for Telserv TRACE Command PAGES designates how much space, in units of pages, is allocated in the extended data segment used for tracing. You can specify PAGES only when initiating a trace, not when you are modifying its parameters. pages is an integer in the range 4 through 64 or equal to 0. If you omit this option or specify 0, the default value 64 is applied to the trace. RECSIZE specifies the length of the data in the trace data records.
Subsystem Control Facility (SCF) Commands for Telserv TRACE Command ALL ( or blank) Specifies that all trace options are selected. This is the default value. The trace file can get very large very quickly. It will wrap, if requested, or will simply stop tracing when the TO file gets full. CONN Traces connection activity between the client and Telserv. LOGIN Trace user login process. ONLINE This keyword causes trace records to be displayed on the Telserv home terminal if online trace is enabled.
Subsystem Control Facility (SCF) Commands for Telserv Examples of the TRACE Command Examples of the TRACE Command The examples are designed to show correct ways of specifying command syntax. PROCESS Object The following command traces the PROCESS object $ZTNT, writes results into the file named TLW, prevents the trace collector process from being initiated, and selects the tracing of all Telserv process activity. TRACE PROCESS $ZTNT, TO $SYSA.TRACES.
Subsystem Control Facility (SCF) Commands for Telserv VERSION null Command The display for the VERSION PROCESS command without the DETAIL option has the following format: VERSION PROCESS \COMM.$MTNT: TELSERV - T9553D30 - (21JUL94) - (21JUL94) The display for the VERSION PROCESS command with the DETAIL option has the following format: Detailed VERSION PROCESS \COMM.
Subsystem Control Facility (SCF) Commands for Telserv Examples of the VERSION Command The following command displays the banner for the assumed process as well as the banners for Guardian, the SCF Kernel, and the product module.
Subsystem Control Facility (SCF) Commands for Telserv Telserv Manual—427174-009 5-52 Examples of the VERSION Command
6 Using PTrace This section contains the subsystem-specific details for using PTrace to format Telserv subsystem trace files created through the use of the SCF TRACE command. These details include the device type and subtype for the Telserv subsystem, any variations to the standard PTrace commands, applicable SELECT keywords, and special considerations for using PTrace. For complete information on using PTrace, refer to the PTrace Reference Manual.
SELECT Command Using PTrace keyword is one of the keywords listed in Table 6-1. Table 6-1. SELECT Keywords for the Telserv Subsystem Keyword Description Keywords for the PROCESS object: ALL Specifies that all trace options are selected. This is the default value. The trace file can get very large very quickly. It will wrap, if requested, or will simply stop tracing when the TO file gets full. CONN Trace connection activity between client and Telserv. LOGIN Trace user login process.
Part III.
Part III.
7 Accessing and Using Telserv Services As part of the Telserv product, HP provides a TELNET client that runs on the NonStop system. Other vendors provide TELNET client software as part of their terminal emulator products. The client features included in the HP NonStop TELNET client differ from the features other vendors provide in their terminal emulator products. While other vendor’s products support the 6530 terminal type, the HP NonStop TELNET client runs in NVT mode only.
The TELNET Protocol Accessing and Using Telserv Services The TELNET Protocol The TELNET protocol provides a bidirectional, byte-oriented communications facility. The TCP/IP or IPX/SPX connection is used to transfer data and TELNET control functions are referred to as TELNET connections. Note. The interface to IPX/SPX is available on G-series systems only. Both ends of a connection, the TELNET client and Telserv, negotiate TELNET control functions once the connection has been established.
ASCII and Binary Mode Accessing and Using Telserv Services 2. From the Welcome banner screen, use ENTER CHOICE to select a service application, such as TACL WELCOME To idev [PORT $ZTC5 #23 WINDOW $ZTN5.#PTT7HET] TELSERV - T9553D40 - (10SEP00) - (IPMADD) Available Service: TACL EXIT Enter Choice> 3. Log on to the NonStop system. 4. Press control escape; that is, press caret (^) and left angle bracket (]). 5. The TELNET prompt appears telnet> 6.
ASCII and Binary Mode Accessing and Using Telserv Services Telserv Manual—427174-009 7-4
8 Using TELNET to Connect to Telserv You can establish communications with Telserv from any system on the network that has a HP NonStop TELNET client. You invoke the TELNET client on your terminal, and the client establishes the connection with Telserv. This section contains the following information: How to run a TELNET client in the OSS environment How to run a TELNET client in the NonStop Kernel environment See Starting the Telserv Process on page 3-1 for information on creating a Telserv process.
Using TELNET to Connect to Telserv Running a TELNET Client in the NonStop™ Kernel Environment The remainder of this section discusses running the TELNET client in the NonStop™ Kernel environment. Running a TELNET Client in the NonStop™ Kernel Environment To run the TELNET client, enter the TELNET command. The form of the TELNET command is: telnet [ / run-option [ , run-option ] ... / ] [ [ -s IP-address ] host [ port ] ] run-option is a TACL RUN command option.
Establishing a Connection Using TELNET to Connect to Telserv For example, if the Telserv process you wish to connect to is running in port 6000 in a host named homesys, you would enter the following command: TACL 4> telnet homesys 6000 WELCOME TO homesys.Tandem.COM [WINDOW $ZTNT.#xxxnnnn] T9553D30 TELNET SERVER 01OCT94 Available Services: TACL EXIT Enter Choice> If you request a connection to a port that does not have a running Telserv process, you will not get a TELNET connection.
Host Names and Name-Resolution Files Using TELNET to Connect to Telserv Host Names and Name-Resolution Files A host name is the official name by which the host system is known to the Internet. On a NonStop S-series system, the host name can be associated with the system’s Internet address in the name-resolution configuration file, or the name can be mapped to an address through a name server. You can ask the system manager of the host system what the host name is.
Addressing Remote Hosts Using TELNET to Connect to Telserv TCP/IP Configuration and Management Manual (if you are using NonStop TCP/IP) TCP/IP (Parallel Library) Configuration and Management Manual (if you are using Parallel Library TCP/IP. H-series and J-series systems do not support Parallel Library TCP/IP.
Addressing Remote Hosts Using TELNET to Connect to Telserv For example, the class A address 79.3.8.22 identifies the network address as 79 and the local host address as 3.8.22. You can also use hexadecimal notation by preceding the hexadecimal digits with 0X or 0x; for example, 0x4f.0x3.0x8.0x16. Sometimes an Internet address is represented externally as two numbers separated by a period: the first number is the network address and the second is the local address; for example, 130.4541.
9 TELNET Client Commands and TELNET Commands TELNET Client Commands This subsection contains descriptions of the syntax (enclosed in boxes) and rules for using TELNET client commands and provide examples of typical ways to use the commands. Table 9-1 summarizes the TELNET client commands. Table 9-1.
close Command TELNET Client Commands and TELNET Commands close Command Use the close command to disconnect from the remote system and return to the TELNET prompt at the local system. close Examples Assume you want to end a session with a system that prompts you for another logon ID after you enter a command to log off. To disconnect from the system, you use the following technique: Enter command to log off. login: Enter escape character.
help or ? Command TELNET Client Commands and TELNET Commands Argument Display flushoutput (f) [^O] flushoutput interrupt (i) [^C] interrupt kill (k) [^X] kill localchars (l) won't recognize certain control characters netdata (n) won't print hexadecimal representation of network traffic options (o) won't show option processing quit (g) [^\] quit Example To display the interrupt character and the current setting of interrupt and netdata, enter the following display command: telnet> displ
TELNET Client Commands and TELNET Commands open Command c[haracter] | l[ine] specifies the type of input. In character mode, the TELNET client immediately sends each character you type to the remote system. In line mode, the text you type is echoed locally and sent to the remote host when you press the RETURN key. The TELNET client enters the mode you specify only if the remote host is capable of entering that mode. By default, the mode is character.
TELNET Client Commands and TELNET Commands send Command If TELNET encounters the end of the file, the result is the same as issuing a quit command. Example To disconnect from the remote system and exit TELNET, enter the following command: telnet> quit send Command Use the send command to send one or more special character sequences to the remote system. send { argument [ argument ] ... } argument is the name of the character sequence you want to send.
status Command TELNET Client Commands and TELNET Commands Example Assume you are working with a remote system in character-input mode, and you want to erase the characters you have entered on a line. In this example, the remote system prompt is a dollar sign ($): $ cp outk telnet> send el $ Enter escape character. Send erase line sequence. Remote system erases line.
toggle Command TELNET Client Commands and TELNET Commands argument specifies the name of the toggle control you want to change. You can abbreviate the name to the letters required to uniquely identify the toggle. The following table describes each toggle and its initial setting when you start TELNET. Argument Function autoflush Determines whether output is flushed when you send interrupt (intr) characters.
toggle Command TELNET Client Commands and TELNET Commands Name Keys Function interrupt ^C Sends the TELNET IP (interrupt processing) sequence to the remote system. kill ^X In character-input mode, sends the TELNET EL (erase line) sequence to the remote system. quit ^\ Sends the TELNET BRK (break) sequence to the remote system. * The ^ represents the CNTL command. ? displays information on the toggle command.
TELNET Client Commands and TELNET Commands ttywritesz Command ttywritesz Command Use the ttywritesz command to determine the maximum number of characters that can be sent at one time to your terminal from the remote system. ttywritesz argument argument is an integer specifying the size of your terminal buffer, in bytes. The default size is 70 bytes. Example To specify a buffer size of 75 bytes, enter the following command: telnet> ttywritesz 75 TELNET Commands Table 9-2 describes the TELNET commands.
TELNET Client Commands and TELNET Commands TELNET Commands Table 9-2. TELNET Commands Command Code Function DONT Signifies that either the client or the server is requesting the other not to use a certain option that the other was willing to use. WILL Signifies that either the client or the server is willing to use a certain option. WONT Signifies that either the client or the server will not use an option that the other asked it to use.
Part IV.
Part IV.
10 Modes of Operation Several modes of communication are used between: An application on the NonStop system and the Telserv process. Note. The term application refers to any service application that you write and that the interactive user can select, as well as to such HP NonStop utilities such as TACL, FUP, and INSPECT. The Telserv process and the client software, including any TELNET client software you write.
Modes of Operation client software uses option TELOPT_TTYTYPE during negotiation and sends one of the following strings: TN6530 TN653X UB6530 UB653X In block mode, additional applications are available to the terminal user; for example, TEDIT on a NonStop S-series server operates in block mode. Telserv ignores all other terminal-type options requested during negotiation with a client program.
Modes of Operation Application The application on the NonStop system must issue the following SETMODE procedure calls: SETMODE 8,0,0 Sets conversation mode, which is the only mode allowed for NVT. SETMODE 6,0,0 Specifies no spacing, thus preventing from being added to the output stream. SETMODE 20,0,0 Specifies no echoing, thus preventing characters received from being echoed. SETMODE 9 nnnn, nnnn Sets the interrupt characters.
Modes of Operation Telserv Manual—427174-009 10-4
A Telserv Error Messages Sent to Terminals Recovering From Errors You can apply the following general approach to recover from errors that you receive on your terminal screen while using TELNET with the Telserv Product. Make sure that the command you have entered has valid parameters, such as the host name or address, the user name or ID, or the port number. Some errors result from a simple typing mistake. If you have made a typing error, try the command again.
Telserv Error Messages Sent to Terminals TELNET Error Messages Recovery. Make sure that you have specified the host name or address correctly. If the TELNET port is not 23, specify the correct port number. Can't set mode number on term err error-number Cause. TELNET cannot set the mode you specified because of the error specified by error-number. Effect. The mode is not set. Recovery. See Recovering From Errors at the beginning of this appendix. Can't turn off/on crmod err error-number Cause.
Telserv Error Messages Sent to Terminals TELNET Error Messages Recovery. If you did not terminate the session, try to reconnect again later. Open of my-term error error-number Cause. A file-system error occurred when TELNET tried to open the virtual terminal file process. Effect. The connection that you requested is not made. Recovery. See Recovering From Errors at the beginning of this appendix. READX error (error-number) on term fd file-number Cause.
Telserv Error Messages Sent to Terminals TELNET Error Messages Effect. TELNET terminates. Ask your system administrator if the TCP/IP process is running. See “ TELNET: bind-nw failed with error no.: error-code Cause. TELNET could not bind to the specified subnet IP address because of the following error: error-code. Effect. The run command is not executed. Recovery. Retry the command. Make sure that you are using the correct subnet IP address. TELNET: connect error-reason Cause.
Telserv Error Messages Sent to Terminals TELNET Error Messages Cause. The entry for TELNET is missing from the $SYSTEM.ZTCPIP.SERVICES file, so TELNET cannot determine which terminal control process (TCP) port to use. Effect. The command failed. Recovery. Ask the system administrator or operator to place an entry for TELNET in the SERVICES file. The entry should specify TCP port 23. toggle: ambiguous argument ('toggle ?' for help) Cause.
Telserv Error Messages Sent to Terminals TELNET Error Messages WRITEX error (error-number) on term fd file-number Cause. A write error occurred when TELNET tried to write to the specified file. Effect. The operation failed. Recovery. See Recovering From Errors at the beginning of this appendix.
Telserv Error Messages Sent to Terminals Telserv Error Messages Telserv Error Messages Sorry, too many users Cause. No windows are available. The number of virtual terminals, or windows, has exceeded the limit set for the process by the SCF MAXTERMINALS attribute, and only dynamic services are configured. Effect. Service selection is not performed and the connection terminates. Recovery. As a terminal user, you can take no direct action.
Telserv Error Messages Sent to Terminals Telserv Error Messages Terminal was idle too long! Disconnecting... Cause. There has been no activity at this terminal for a long period. Effect. The connection to the system is terminated. This error message is sent after several warning messages. Recovery. Connect again and maintain activity on the terminal, or ask the system administrator to use SCF to disable the banner time-out value or the time-out value for the process.
Telserv Error Messages Sent to Terminals Telserv Error Messages Sorry, window cannot be selected Sorry, invalid choice Cause. You typed in a window name instead of a service name. Effect. The Service Menu is displayed again. Recovery. Enter the correct service name rather than a window name. Note that window names begin with a pound sign (#). Sorry, too many users for service: Cause. The number of windows allocated to this service, have been exhausted. (The service is of subtype STATIC.
Telserv Error Messages Sent to Terminals Telserv Error Messages Sorry, too many users for dynamic service: Cause. The number of windows has exceeded the limit set for the process by the SCF MAXTERMINALS attribute, and the service chosen has the SUBTYPE attribute specified as DYNAMIC. Effect. The terminal is disconnected. Recovery.
B SCF Error Messages for Telserv This appendix provides you with information for interpreting Telserv subsystem error messages generated by the Telserv process. Italicized words in the message descriptions stand for values that are inserted by the Telserv process. Error messages are identified by a 5-digit number preceded by the character E.
SCF Error Messages for Telserv 3 TELSERV E00003 Inconsistency between SERVICETYPE and SERVICENAME. Cause. SERVICETYPE in this ADD command is different from the SERVICETYPE associated with the SERVICENAME already defined. Effect. The command does not execute. Recovery. Change the SERVICETYPE or SERVICENAME in this ADD command to be consistent with each other. 4 TELSERV E00004 Inconsistency between attribute values: name1 and name2 Cause.
SCF Error Messages for Telserv 7 TELSERV E00007 Special Service name may not be altered or deleted. Cause. Special Services have names that start with the character “Z”. These services cannot be altered or deleted. Effect. The command does not execute. Recovery. Informative message only; no corrective action is needed. The Special Service remains unchanged. 8 TELSERV E00008 Subordinate object exists for name. Cause.
SCF Error Messages for Telserv 11 TELSERV E00011 File or device name specified for attribute attribute does not exist. Cause. The specified file or device name does not exist. Effect. The command does not execute. Recovery. Reenter the command and specify the correct file or device name. 12 TELSERV E00012 File specified for attribute attribute is not an executable program. Cause. The file code of the specified file indicates that it is not an executable program.
SCF Error Messages for Telserv 15 TELSERV E00015 Specified caller IP address already exits in another service. Cause. The specified caller IP address is already associated with an existing window in a different service. Effect. The command does not execute. Recovery. Specify a different caller IP address. 16 TELSERV E00016 Caller IP address is required for window. Cause. Caller IP address must be specified for windows subordinate to a service whose ASSIGNED attribute has been turned on. Effect.
SCF Error Messages for Telserv 19 TELSERV E00019 The Default Service already exists. Cause. Only one Default Service can be allowed per Telserv process. Effect. The command does not execute. Recovery. Use another Telserv process to configure the Default Service. 20 TELSERV E000020 Attribute already specified. Cause. An attribute is being specified more than once. Effect. The command does not execute. Recovery. Reissue the command after removing the duplicate attribute.
C SCF Command Syntax This appendix provides a summary of the SCF command syntax.
ADD Command SCF Command Syntax ADD Command ADD [ / OUT file-spec / ] [ object-spec ] { , attribute-spec [ , attribute-spec ] ... } ADD SERVICE ADD [ / OUT file-spec / ] SERVICE service-name { , attribute-spec [ , attribute-spec ] ...
ADD WINDOW SCF Command Syntax ADD WINDOW ADD [ / OUT file-spec / ] WINDOW window-name { , attribute-spec [ , attribute-spec ] ...
ALTER SERVICE SCF Command Syntax ALTER SERVICE ALTER [ / OUT file-spec / ] SERVICE service-name { , attribute-spec [ , attribute-spec ] ...
DELETE SERVICE SCF Command Syntax DELETE SERVICE DELETE [ / OUT file-spec / ] SERVICE service-name [ , SUB [ NONE | ALL | ONLY ] ] DELETE WINDOW DELETE [ / OUT file-spec / ] WINDOW window-name INFO Command INFO [ / OUT file-spec / ] [ object-spec ] [ , SUB [ NONE | ALL | ONLY ] ] [ , DETAIL ] INFO PROCESS INFO [ / OUT file-spec / ] PROCESS process-name [ , SUB [ NONE | ALL | ONLY ] ] [ , DETAIL ] INFO SERVICE INFO [ / OUT file-spec / ] SERVICE service-name [ , SUB [ NONE | ALL | ONLY ] ] [ , DETAIL ]
LISTOPENS PROCESS SCF Command Syntax LISTOPENS PROCESS LISTOPENS [ / OUT file-spec / ] PROCESS process-name [ , SUB [ NONE | ALL | ONLY ] ] LISTOPENS WINDOW LISTOPENS [ / OUT file-spec / ] WINDOW window-name NAMES Command NAMES [ / OUT file-spec / ] [ object-spec ] [ , SUB [ NONE | ALL | ONLY ] ] NAMES PROCESS NAMES [ / OUT file-spec / ] PROCESS process-name [ , SUB [ NONE | ALL | ONLY ] ] NAMES SERVICE NAMES [ / OUT file-spec / ] SERVICE service-name [ , SUB [ NONE | ALL | ONLY ] ] NAMES WINDOW NAME
STATS Command SCF Command Syntax STATS Command STATS [ / OUT file-spec / ] [ object-spec ] [ , SUB [ NONE | ALL | ONLY ] ] [ , RESET ] STATS PROCESS STATS [ / OUT file-spec / ] PROCESS process-name [ , SUB [ NONE | ALL | ONLY ] ] [ , RESET ] STATS SERVICE STATS [ / OUT file-spec / ] SERVICE service-name [ , SUB [ NONE | ALL | ONLY ] ] [ , RESET ] STATS WINDOW STATS [ / OUT file-spec / ] WINDOW window-name [ , RESET ] STATUS Command STATUS [ / OUT file-spec / ] [ object-spec ] [ , SUB [ NONE | ALL | ON
STOP Command SCF Command Syntax STOP Command STOP [ / OUT file-spec / ] [ object-spec ] STOP PROCESS STOP [ / OUT file-spec / ] PROCESS [ process-name ] STOP WINDOW STOP [ / OUT file-spec / ] WINDOW [ window-name ] TRACE Command TRACE [ / OUT file-spec / ] [ object-spec ] { , STOP { [ , COUNT count [ , NOCOLL [ , PAGES pages [ , RECSIZE size [ , SELECT select-spec [ , TO file-spec [ , WRAP } ] ] ] ] ] ] ] } *** *** This attribute is required when a trace is started.
TRACE PROCESS SCF Command Syntax TRACE PROCESS TRACE [ / OUT file-spec / ] [ object-spec ] { , STOP { [ , COUNT count [ , NOCOLL [ , PAGES pages [ , RECSIZE size [ , SELECT select-spec [ , TO file-spec [ , WRAP } ] ] ] ] ] ] ] } *** *** This attribute is required when a trace is started. where select-spec is one or more of the following specifications: { keyword } { ( keyword [ , keyword ] ...) } { number } { ( number [ , number ] ...
TRACE WINDOW SCF Command Syntax TRACE WINDOW TRACE [ / OUT file-spec / ] [ object-spec ] { , STOP { [ , COUNT count [ , NOCOLL [ , PAGES pages [ , RECSIZE size [ , SELECT select-spec [ , TO file-spec [ , WRAP } ] ] ] ] ] ] ] } *** *** This attribute is required when a trace is started. where select-spec is one or more of the following specifications: { keyword } { ( keyword [ , keyword ] ...) } { number } { ( number [ , number ] ...
Glossary This glossary defines terms used both in this manual and in other Telserv or TELNET manuals. Both industry-standard terms and HP NonStop terms are included. broadcast. A packet delivery system that delivers a copy of a given packet to all hosts that attach to it is said to broadcast the packet. Broadcast may be implemented with hardware or software. CCITT (International Telegraph and Telephone Consultative Committee).
ECHO Glossary ECHO. The name of a program used in the Internet to test the reachability of destinations by sending them an ICMP echo request and waiting for a reply. emulator. A software program that enables a device to simulate the functions of another software or hardware device. For example, the PC6530 terminal emulator program (PCT) enables your workstation to simulate the functions of a 65-Series terminal. error. A condition that causes a command or other operation to fail. event management.
Internet Protocol (IP) Glossary Internet Protocol (IP). The Internet standard protocol that defines the Internet datagram as the unit of information passed across the Internet, and that provides the basis for the Internet connectionless, best-effort packet delivery service. International Organization for Standardization (ISO).
interactive command Glossary licensed to use a dedicated range of MAC addresses. That way, each controller is guaranteed it own unique address. interactive command. See also programmatic command. In DSM, a command entered by a human operator rather than by a program. object-name template. See also wild-card character. In DSM, a name that stands for more than one object. Such a name includes one or more wild-card characters, such as * and ?. object.
protocol Glossary protocol. A formal description of message formats and the rules two or more machines must follow to exchange those messages. Protocols can describe low level details of machine-to-machine interfaces (for example, the order in which the bits from a byte are sent across a wire), or high-level exchanges between application programs (for example, the way in which two programs transfer a file across the Internet).
Subsystem ID (SSID) Glossary provides security features, version compatibility, support for tracing, and support for applications implemented as NonStop™ process pairs. Subsystem ID (SSID). In DSM programmatic interfaces, a data structure that uniquely identifies a subsystem to SPI. It consists of the name of the owner of the subsystem, a subsystem number that identifies that particular subsystem, and a subsystem version number. The subsystem ID is an argument to most of the SPI procedures.
Glossary Transmission Control Protocol/Internet Protocol (TCP/IP) participants must establish a connection. Software implementing TCP usually resides on the operating system and uses the IP protocol to transmit information across the Internet. It is possible to terminate (shut down) one direction of flow across a TCP connection, leaving a one-way (simplex) connection. The Internet protocol suite is often referred to as TCP/IP because TCP is one of the two most fundamental protocols.
X.
Index A ABORT command ABORT PROCESS 5-2 ABORT WINDOW 5-2 considerations 5-2 description 5-2 syntax C-1 ADD command ADD SERVICE 5-4 ADD WINDOW 5-7 considerations 5-9 description 5-3 syntax C-2 Addressing a remote host 8-5 ALTER command ALTER PROCESS 5-11 ALTER WINDOW 5-16 considerations 5-17 description 5-11 syntax C-3 Application layer, TELNET 3-1 Arguments in TELNET send command 9-5 ASCII mode 7-2 Assumed, as used in this manual 5-1 Attributes (alterable) PROCESS BANNERTIMEOUTVALUE 5-11 DROPCR 5-12 MAXTERM
D Index Configuration 4-1 Connection establishing TELNET 9-4 to HP NonStop TELNET server 8-1 D DELETE command considerations 5-20 DELETE SERVICE 5-20 DELETE WINDOW 5-20 description 5-20 syntax C-4 Device names, defined 4-4 Disconnecting from remote system TELNET close 9-2 TELNET quit 9-4 Display examples INFO PROCESS 5-22 DETAIL 5-22 INFO SERVICE 5-24 DETAIL 5-24 INFO WINDOW 5-26 DETAIL 5-26 LISTOPENS PROCESS 5-30 LISTOPENS WINDOW 5-31 NAMES null 5-35 NAMES PROCESS 5-33 NAMES SERVICE 5-34 NAMES WINDOW 5-
M Index LISTOPENS command description 5-30 examples 5-32 LISTOPENS PROCESS 5-30 LISTOPENS WINDOW 5-31 syntax C-5 LNP, with TCP/IPv6 3-15 Logical Network Partition 3-14 Logical Network Partition (LNP), with TCP/IPv6 3-14 Logical states 4-5 M Maximum number of objects 4-9 MAXTERMINALS attribute 5-11 MENU attribute 5-11 Messages SCF error B-1 TELNET error A-1 Telserv error A-7 Mode interactive 4-6 noninteractive 4-6 Modes, TELNET input and 9-3 N Names device 4-4 object 4-4 NAMES command description 5-33 NA
P Index P Port, using TELNET on 8-3 Presentation layer, TELNET 3-1 PROCESS attributes (alterable) BANNERTIMEOUTVALUE 5-11 DROPCR 5-12 MAXTERMINALS 5-11 MENU 5-11 TIMEOUTVALUE 5-11 PTrace device subtype 6-1 device type 6-1 PTrace commands HEX 6-1 OCTAL 6-1 SELECT 6-1 Q Question mark (?) in TELNET toggle command 9-8 R Recovering from errors A-1 Remote system addressing 8-5 disconnecting from 9-4 TELNET 9-2 RUN command options 3-10 syntax 3-10 S SCF configuration 4-1 input source 4-5 online help commands
T Index PRI 5-13 PROGRAM 5-13 RESILIENT 5-13 SUBTYPE 5-13 SWAP 5-13 TYPE 5-13 SERVICENAME attribute 5-7 SERVICETYPE attribute 5-7 Session, starting 4-6 Setting the output destination 4-7 Special characters displaying TELNET 9-2 START command description 5-36 START WINDOW 5-36 START WINDOW command syntax C-6 States defined 4-5 object 4-5 STATS command considerations 5-40 description 5-36 STATS PROCESS 5-37 display 5-37 STATS WINDOW 5-39 display 5-39 syntax C-7 STATUS command description 5-42 STATUS PROCESS
V Index character mode 9-3 characters sent at one time 9-9 close command 9-2 display command 9-2 displaying remote system name 9-6 escape character, displaying 9-6 help command 9-3 input mode 9-3 input mode,displaying current 9-6 line mode 9-3 local characters, Telserv 9-6 mode command 9-3 open command 9-4 question mark (?) command 9-3 quit command 9-4 remote system, displaying name of 9-6 send command 9-5 sending special characters 9-5 status command 9-6 terminal buffer size 9-9 toggle command 9-6 ttywri
Special Characters Index SERVICETYPE 5-8 Special Characters $ZNET 4-1 ? (question mark) in TELNET toggle command 9-8 Telserv Manual—427174-009 Index-7
Special Characters Index Telserv Manual—427174-009 Index-8
