TN3270e Server Manual

ManualsBrandsHP ManualsServerHP NonStop G-Series

Abstract

An HP NonStop™ TCP/IP service, the HP enhanced TN3270 server (TN3270e server)

enables you to use popular TN3270 client software to access 3270 applications on HP

NonStop™ D-series systems, HP NonStop™ S-series systems, and HP Integrity

NonStop™ NS-series systems. The TN3270e server provides TCP/IP access to

Pathway, TACL, TEDIT, PS Mail, and other HP 3270 applications from terminals, hosts,

and a wide variety of workstations. The TN3270e server provides features that support

RFC 2355; these features are in addition to those provided by the traditional Guardian

TN3270 server.

Product Version

Enhanced TN3270 Server D40

Supported Release Version Updates (RVUs)

This manual supports D40.00 and all subsequent D-series RVUs, G01.00 and all

subsequent G-series RVUs, and H06.03 and all subsequent H-series RVUs until

otherwise indicated by its replacement publication.

Part Number Published

422923-003 August 2013

Summary of content (178 pages)

PAGE 1
TN3270e Server Manual Abstract An HP NonStop™ TCP/IP service, the HP enhanced TN3270 server (TN3270e server) enables you to use popular TN3270 client software to access 3270 applications on HP NonStop™ D-series systems, HP NonStop™ S-series systems, and HP Integrity NonStop™ NS-series systems. The TN3270e server provides TCP/IP access to Pathway, TACL, TEDIT, PS Mail, and other HP 3270 applications from terminals, hosts, and a wide variety of workstations.
PAGE 2
Document History Part Number Product Version Published 422923-001 Enhanced TN3270 Server D40 August 1999 422923-002 Enhanced TN3270 Server D40 July 2005 422923-003 Enhanced TN3270 Server D40 August 2013
PAGE 3
Legal Notices  Copyright 1999, 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.
PAGE 4
PAGE 5
TN3270e Server Manual Index Examples Figures Tables Legal Notices What’s New in This Manual vii Manual Information vii New and Changed Information vii About This Manual ix Who Should Read This Manual ix Related Manuals ix Organization of This Manual x Notation Conventions xi 1.
PAGE 6
3. Using the TN3270e Server Contents Troubleshooting the Installation 2-3 3. Using the TN3270e Server Initializing the Startup Environment 3-1 Starting the TN3270e Server 3-2 3270 Local and Remote Commands 3-5 Name Resolution 3-6 EMS Events 3-7 Completion Codes 3-8 4.
PAGE 7
6. ITI Communication Protocol Contents Message Format for Outbound Data 5-1 Message Format for Inbound Data 5-2 SNAX/XF Mode 5-3 Two-Step READ Requests 5-3 SNAX/XF CRT SETMODE Procedure 5-3 Extended Highlighting in SNAX/XF Mode 5-5 6.
PAGE 8
9. Trace Formatter Contents ZETN-EVT-GETHOST-ERR 8-4 ZETN-EVT-LOG-SWITCH 8-5 ZETN-EVT-NET-ERROR 8-5 ZETN-EVT-QUIT 8-5 ZETN-EVT-RECV-ABORT 8-6 ZETN-EVT-SESS-ERROR 8-7 ZETN-EVT-SESS-ESTAB 8-8 ZETN-EVT-SESS-TERM 8-9 ZETN-EVT-SPI-ERROR 8-10 ZETN-EVT-STARTED 8-10 ZETN-TKN-BANNER 8-11 9. Trace Formatter A. Terminal Models in SNAX/XF Mode B. Client Messages C. ETN32COM Error Messages Error Messages C-1 D. TN3270e Server Messages E.
PAGE 9
Index Contents ZETN-TKN-GETHOST-ERR Token Code E-12 ZETN-TKN-HOST-NAME Token Code E-12 ZETN-TKN-LISTOPEN-RSP Token Code E-12 ZETN-TKN-NLS-ALLORONE-CHOICE Token Code E-13 ZETN-TKN-NLS-DISPLAY-BASE Token Code E-14 ZETN-TKN-NLS-TABLEADDRESS Token Code E-14 ZETN-TKN-NLS-TABLENAME Token Code E-14 ZETN-TKN-NLS-TABLEVALUE Token Code E-14 ZETN-TKN-NLS-TRANSLATION Token Code E-15 ZETN-TKN-OPCODE Token Code E-15 ZETN-TKN-OPNAME Token Code E-17 ZETN-TKN-PROCESS-NAME Token Code E-17 ZETN-TKN-REASON Token Code E-18 ZE
PAGE 10
Contents Table 3-3. Table 7-1. Table A-1. Table A-2.
PAGE 11
What’s New in This Manual Manual Information TN3270e Server Manual Abstract An HP NonStop™ TCP/IP service, the HP enhanced TN3270 server (TN3270e server) enables you to use popular TN3270 client software to access 3270 applications on HP NonStop™ D-series systems, HP NonStop™ S-series systems, and HP Integrity NonStop™ NS-series systems. The TN3270e server provides TCP/IP access to Pathway, TACL, TEDIT, PS Mail, and other HP 3270 applications from terminals, hosts, and a wide variety of workstations.
PAGE 12
New and Changed Information What’s New in This Manual     Manual-wide: Replaced instances of “Guardian Enhanced TN3270 Server” with “enhanced TN3270 server” or “TN3270e server”. In About This Manual, updated the list of manuals under Related Manuals. In About This Manual, placed the bulleted list under Organization of This Manual into a table. In Section 1, Introduction to the Enhanced TN3270 Server, updated Figure 1-3 to reflect change of TLAM to SLSA.
PAGE 13
About This Manual This manual describes the HP enhanced TN3270 server product, which enables you to use client software to access IBM 3270-series applications on HP NonStop operating systems. This section includes the following information:     Who Should Read This Manual Related Manuals Organization of This Manual Notation Conventions Who Should Read This Manual This manual is intended for system managers who install and maintain the TN3270e server.
PAGE 14
Organization of This Manual About This Manual        Interactive Upgrade Guide 2 SCF Reference Manual for AM3270 and TR3271 (D-series only) SNAX/CDF Application Programming Manual (D-series only) SNAX/XF and SNAX/APN Event Management Programming Manual SPI Programming Manual System Generation Manual for AM3270 (D-series only) Guardian Procedure Calls Reference Manual You will also find useful information in the following publications:        Kelly, B. “TN3270 Enhancements.
PAGE 15
Notation Conventions About This Manual Table i. Manual Sections and Appendixes Section/Appendix Description Section 4, Using ETN32COM Describes how to start the ETN32COM operator interface and lists the ETN32COM commands. Section 5, CRT Communication Protocol Describes the TN3270e CRT communication protocol, including message formats, application file system procedures, and error handling.
PAGE 16
General Syntax Notation About This Manual computer type. Computer type letters within text indicate C and Open System Services (OSS) keywords and reserved words. Type these items exactly as shown. Items not enclosed in brackets are required. For example: myfile.c 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.
PAGE 17
General Syntax Notation About This Manual Punctuation. Parentheses, commas, semicolons, and other symbols not previously described must be typed as shown. For example: error := NEXTFILENAME ( file-name ) ; LISTOPENS SU $process-name.#su-name 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.
PAGE 18
Notation for Messages About This Manual !o:i. In procedure calls, the !o:i notation follows an output buffer parameter that has a corresponding input parameter specifying the maximum length of the output buffer in bytes. For example: error := FILE_GETINFO_ ( filenum , [ filename:maxlen ] ) ; !i !o:i Notation for Messages This list summarizes the notation conventions for the presentation of displayed messages in this manual. Bold Text. Bold text in an example indicates user input typed at the terminal.
PAGE 19
Notation for Management Programming Interfaces About This Manual either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example: obj-type obj-name state changed to state, caused by { Object | Operator | Service } process-name State changed from old-objstate to objstate { Operator Request. } { Unknown. } | Vertical Line.
PAGE 20
Change Bar Notation About This Manual Change Bar Notation Change bars are used to indicate substantive differences between this manual and its preceding version. Change bars are vertical rules placed in the right margin of changed portions of text, figures, tables, examples, and so on. Change bars highlight new or revised information. For example: The message types specified in the REPORT clause are different in the COBOL85 environment and the Common Run-Time Environment (CRE).
PAGE 21
1 Introduction to the TN3270e Server The TN3270e server is a Transmission Control Protocol/Internet Protocol (TCP/IP) service that acts as a Guardian 3270 access method. It allows workstations running the public-domain TN3270 client to access 3270 block-mode or conversational HP applications, including Pathway, TACL, TEDIT, and PSMAIL/3270. The TN3270e server allows you to emulate both the terminal and printer members of the 3270 family using Telnet.
PAGE 22
Features Introduction to the TN3270e Server The TN3270e server runs as a subtype 30 device and emulates the SNAX/XF interface. Note. The AM3270 interface supported by the traditional Guardian TN3270 server process is not supported by the TN3270e server process. The TN3270e server returns to HP applications calling DEVICEINFO, a device type and subtype corresponding to its configuration.
PAGE 23
Clients Introduction to the TN3270e Server The TN3270e server does not support the following features:    ISO 8859/0 character sets RFC 1041 (3270-Regime) Exclusive opens of the TN3270e server Note. For details about the differences between the TN3270e server and the traditional Guardian TN3270 server by feature, see Differences by Feature on page 1-10. Clients The TN3270e server clients are available for a wide variety of platforms, including MS-DOS, Apple, DEC, IBM, and most UNIX systems.
PAGE 24
Option Negotiation Introduction to the TN3270e Server Figure 1-2. Option Negotiation Sequence With TN3270e Client TN3270e Server TN3270e Client DO TN3270E WILL TN3270E SEND DEVICE-TYPE DEVICE-TYPE REQUEST term-model CONNECT device-name DEVICE-TYPE IS term-model CONNECT device-name FUNCTIONS REQUEST function-list FUNCTIONS IS function-list 3270 DATA VST002.vsd During TN3270e server option negotiation with TN3270e clients, the following rules apply:    The BINARY and EOR options are implied.
PAGE 25
TN3270 Protocol Restrictions Introduction to the TN3270e Server TN3270 Protocol Restrictions Due to limitations of the public-domain TN3270 protocol, the following 3270 terminal features are not supported:    Negative terminal responses PTR (printer) protocol RFC 2355 SNA-specific functions:      SCS-CTL-CODES BIND-IMAGE RESPONSES SYSREQ ATTN key Note.
PAGE 26
The TN3270e Server Environment Introduction to the TN3270e Server The TN3270e Server Environment This section describes typical TN3270e server environments. Figure 1-3 shows the environment of a simple TN3270e server environment. Figure 1-3. Simple TN3270e Server Environment Guardian System 3270 Application TN3270e Server ($TN32) TCP/IP ($ZTC0) Workstation SLSA TN3270 Client 5600/361x Ethernet LAN VST003.vsd Each copy of the TN3270e server accesses a single TCP/IP process.
PAGE 27
The TN3270e Server Environment Introduction to the TN3270e Server Figure 1-4 shows a TN3270e server configuration that has a single TCP/IP configuration. Note that port number 2000 has been assigned to the TN3270e server to avoid a conflict with the TELSERV (Telnet server) program default port number 23. Figure 1-4. Single TCP/IP Process Configuration Guardian System TN3270e Server Port 2000 TELSERV Port 23 TCP/IP Process Single TCP/IP Process Controller Workstation TN3270 PCT VST005.
PAGE 28
Application Considerations Introduction to the TN3270e Server Figure 1-5 shows a TN3270e server configuration with a multiple TCP/IP configuration. Note that default port number 23 is retained for the TN3270e server. There is no conflict with the default port number 23 used for the TELSERV (Telnet server) program because TELSERV runs on a different TCP/IP process. In this environment, the user must connect to different IP addresses. Figure 1-5.
PAGE 29
Safeguard Considerations Introduction to the TN3270e Server Safeguard Considerations If you add an TN3270e server window as a Safeguard-protected terminal and the TN3270e server is stopped and restarted, Safeguard suspends the Safeguardprotected terminal. After restarting the TN3270e server, you must use Safecom to thaw and restart the Safeguard terminal.
PAGE 30
Custom Application Considerations Introduction to the TN3270e Server  If you are using a Pathway version prior to C31, when starting SCREEN COBOL programs using the PATHCOM RUN PROGRAM command, you must specify TYPE IBM-3270:n (where n is the terminal model). The following is an example of the PATHCOM command for Pathway versions prior to C31: PATHCOM RUN menu,TYPE IBM-3270:2  The terminal attribute PRINTER IS-ATTACHED is not supported and should not be specified in a PATHCOM ADD TERM command.
PAGE 31
Differences by Protocol Introduction to the TN3270e Server Differences by Protocol The following protocol restrictions differ from those that are applicable to the traditional Guardian TN3270 server. For specific information about protocol restrictions applicable to the TN3270e server, see TN3270 Protocol Restrictions on page 1-5.
PAGE 32
Differences by SPI Command Introduction to the TN3270e Server TN3270e Server Manual—422923-003 1-12
PAGE 33
2 System Setup This section tells you how to set up the TN3270e server on your system. It gives the system requirements and installation steps. This section also provides instructions on configuring TCP/IP and verifying the TCP/IP configuration. System Requirements Before you begin using the TN3270e server, check that your system meets the requirements listed in Table 2-1. Note. See the TN3270e server softdoc for updates on the latest software versions required. Table 2-1.
PAGE 34
Files System Setup Table 2-1. System Requirements (page 2 of 2) Component Requirement T9631D20 Event Management Service (EMS) T9632D10 EMS Distributor T9752D10 Subsystem Programmatic Interface (SPI) Optional software T9100D20 Data Definition Language (DDL) T9205D20 HP Tandem Advanced Command Language (TACL) T9640D20 ViewPoint T9633D20 Event Management Service (EMS) Template Compiler T9634D20 EMS Filter Compiler The TN3270e server reports events only to the EMS.
PAGE 35
Installing the TN3270e Server System Setup Installing the TN3270e Server Follow these steps to install the TN3270e server: 1. If you are using Install (D-series installations only) to install the TN3270e server, perform the RESTDSV, SYSGEN, and REPSUBSYS phases of the Install program. If you are using DSM/SCM to install the TN3270e server, see the DSM/SCM User’s Guide for detailed information about DSM/SCM installation methods. Note.
PAGE 36
Troubleshooting the Installation System Setup implementations. Refer to the documentation from your TCP/IP vendor for details on running PING.  Establish a Telnet connection from your workstation to the TELSERV (6530) process. When you have successfully installed the TN3270e server, go on to Section 3, Using the TN3270e Server to find out how to initialize the startup environment and start the TN3270e server.
PAGE 37
3 Using the TN3270e Server This section describes how to initialize the startup environment and start the TN3270e server. Initializing the Startup Environment To initialize the startup environment for the TN3270e server, issue the following optional commands as appropriate for your system environment. All parameters and defines have default values.
PAGE 38
Starting the TN3270e Server Using the TN3270e Server Starting the TN3270e Server To start the TN3270e server, issue the ETN32SRV command from the TACL prompt using the following syntax. ETN32SRV / tacl-options / port [ etn32-options ] tacl-options are the standard TACL run options described in the TACL Reference Manual. The following TACL run options are relevant for the TN3270e server: NAME tn3270-name specifies the process name of the TN3270e server program, where tn3270name is the process name.
PAGE 39
Starting the TN3270e Server Using the TN3270e Server This space must be available on the swap volume. You can change the amount of swap space allocated for the buffer segment with the -m command line option described later. The TN3270e server ignores any IN or OUT file specification.
PAGE 40
Starting the TN3270e Server Using the TN3270e Server -h causes pool-checking on every memory-management call. Due to increased overhead, you should use this option only when you suspect corruption of the memory pool. -k specifies that a TN3270e server process supports the Kanji character set in CRT mode windows. Setting the -k option tells the SETMODE 144 procedure to return a set of values appropriate for the Kanji character set. Be sure to use the -k option in conjunction with the -s option (SNAX mode).
PAGE 41
3270 Local and Remote Commands Using the TN3270e Server event may occur for printer type clients that do not request client response processing. Using this option prevents the rare event from occurring. For interactive terminal client types, this is not a problem as this option affects only the WRITE type request. Note. If you run the TN3270e server with no command line arguments, the startup syntax is displayed and the TN3270e server terminates.
PAGE 42
Name Resolution Using the TN3270e Server Table 3-1 illustrates when to set the -r option. Table 3-1. Setting the -r Option Client accepts: -r no -r Remote only Required Not supported Remote or local Supported Supported Local only Not supported Required Table 3-2 shows the various 3270 command sets defined by IBM. Table 3-2.
PAGE 43
EMS Events Using the TN3270e Server   If -n1 is specified, host names are resolved from the hosts file specified by PARAM TCPIP^HOST^FILE or, if PARAM is omitted, from $SYSTEM.ZTCPIP.HOSTS. If a host is not found in the hosts file, the host name does not appear in EMS events and no error is reported. If -n2 is specified, the method of host name resolution is determined by the presence or absence of the TCPIP^HOSTS^FILE and TCPIP^RESOLVER^NAME as expressed by the rules in Table 3-3. Note.
PAGE 44
Completion Codes Using the TN3270e Server Completion Codes The TN3270e server returns the following completion codes: 0 Process terminated normally (STOP PROCESS). A shutdown event is sent to EMS. 1 Process terminated with a startup error. Either an EMS event is generated or an error message is written to the hometerm file. 2 Process abended. Either an EMS event is generated or an error message is written to the hometerm file.
PAGE 45
4 Using ETN32COM This section tells how to use ETN32COM, the operator interface to the TN3270e server. This section describes how to start ETN32COM and how to use ETN32COM commands. Starting ETN32COM To start ETN32COM, enter the following command at the TACL prompt: etn32com [/tacl-opts/] [ tn32-name ] [ ; cmd ... ] tacl-opts are the standard TACL options, for example, IN, OUT, or PRI. tn32-name is the process name of the TN3270e server process to be opened.
PAGE 46
Completion Codes Using ETN32COM Completion Codes ETN32COM returns the following completion codes: 0 Program terminated normally (EXIT). 1 Process terminated with warning messages. 2 Program abended.
PAGE 47
ETN32COM Commands by Type Using ETN32COM ETN32COM Commands by Type ETN32COM provides the following commands, which are listed by type. Each command is described in this section, listed in alphabetical order.
PAGE 48
ETN32COM Command Descriptions Using ETN32COM ETN32COM Command Descriptions This section contains descriptions of the ETN32COM commands. ABORT WINDOW This command terminates a session on the specified window. The session with the client will be disconnected. Error 140 (FEMODEMERR) will be returned to all outstanding application I/Os. ABORT WINDOW window-name window-name is #window for the specified window or asterisk (*) for all windows.
PAGE 49
ADD WINDOW Using ETN32COM ADD WINDOW This command adds a static window to the TN3270e server configuration. ADD WINDOW window-name [ , device-spec ] window-name is #window.
PAGE 50
ADD WINDOW Using ETN32COM If you specify CALLER ip-address, the window is assigned only to a session initiated by that IP address. If you omit the CALLER, the window may be used by any session. When a session is established, the TN3270e server looks first for an available window with the caller’s address. If no window is available, it looks for any available window without a CALLER address. ip-address is a TCP/IP address in dotted decimal form. port-num is an integer between 0 and 65,534.
PAGE 51
ADD WINDOW Using ETN32COM Examples ~ADD WINDOW #win001 ~ADD WINDOW #win001 ~ADD WINDOW #mywin, CALLER 130.252.161.97 ~ADD WINDOW #mywin, CALLER 130.252.161.
PAGE 52
ALTER PROCESS Using ETN32COM ALTER PROCESS These commands allow you to modify the process attributes by switching EMS event logging to the specified EMS collector, enabling and disabling national language support translation, and modifying character values in the national language support translation tables. ALTER PROCESS , {LOGFILE collector} {TRANSLATE ON|TRANSLATE OFF} {INPUTTABLE|OUTPUTTABLE, A|ADDRESS integer, V|VALUE integer} collector is an EMS primary or alternate collector.
PAGE 53
ALTER WINDOW Using ETN32COM ALTER WINDOW This command allows you to modify the CALLER attribute of the window. ALTER WINDOW window-name , device-spec window-name is #window.
PAGE 54
ALTER WINDOW Using ETN32COM If you specify CALLER ip-address, the window is reserved for clients with that IP address. If you omit ip-address, the window can be accessed by any client. ip-address is a TCP/IP address in dotted decimal form. port-num is an integer between 0 and 65,534. If you specify PORT port-num and CALLER, the window is further restricted to a session originating from the specified port on the client.
PAGE 55
COMMENT Using ETN32COM COMMENT This command causes all text up to a semicolon (;) or end-of-line to be ignored. COMMENT text text is a text string.
PAGE 56
DELETE WINDOW Using ETN32COM DELETE WINDOW This command deletes a window from the TN3270e server configuration. The window being deleted must not be in use. DELETE WINDOW window-name window-name is #window for a specified window or an asterisk (*) for all windows.
PAGE 57
EXIT Using ETN32COM EXIT This command exits ETN32COM.
PAGE 58
FC Using ETN32COM FC The FC command (short for Fix Command) allows you to edit (fix) a command you previously entered. FC Examples -> FC ..STARFUS WINDOW #WIN001 DDIT ..STATUS WINDOW #WIN001 R002 ..
PAGE 59
HELP Using ETN32COM HELP This command displays online help for the specified command or for all commands. HELP [ command-name | ALL ] HELP displays the syntax of all commands. HELP command-name displays the syntax and description of the specified command. HELP ALL displays the syntax and description of all commands.
PAGE 60
INFO PROCESS Using ETN32COM INFO PROCESS This command displays static and dynamic information from the TN3270e server process. INFO PROCESS [ table-id [ cell-spec ] [ base ] ] table-id is either INPUTTABLE for the national language input translation table or OUTPUTTABLE for the national language output translation table. cell-spec is the decimal address of the table cell to display in decimal. If cell-spec is omitted, the entire table is displayed in the specified base.
PAGE 61
LISTOPENS [WINDOW] Using ETN32COM LISTOPENS [WINDOW] This command displays the openers of the specified window. LISTOPENS [WINDOW] window-name window-name is #window for the specified window.
PAGE 62
OPEN [PROCESS] Using ETN32COM OPEN [PROCESS] This command opens the specified TN3270e server process. The server banner will be displayed. All subsequent commands will be sent to the currently open process. OPEN [PROCESS] process-name process-name is the name of the specified TN3270e server process to be opened.
PAGE 63
STATUS PROCESS Using ETN32COM STATUS PROCESS This command displays the status of the TN3270e server process. STATUS PROCESS Example ~STATUS PROCESS Number of windows: 3 Logfile: \CSO.
PAGE 64
STATUS PROCESS Using ETN32COM (6) current allocated is the current number of bytes allocated from the memory pool. Percent current allocated (7) is the percentage of configured (1) memory. (8) maximum allocated is the maximum number of bytes allocated from the memory pool. Percent maximum allocated (9) is the percentage of configured (1) memory. (10) current count is the current number of allocations from the buffer pool. (11) maximum count is the maximum number of allocations from the buffer pool.
PAGE 65
STATUS SESSION Using ETN32COM STATUS SESSION This command displays the status of the specified session. STATUS SESSION is used to locate the window with the specified IP address or LU name. STATUS SESSION { ip-address | , { TERMINAL , LUNAME | PRINTER , { LUNAME | ASSOCIATE } } device-name } ip-address is a TCP/IP address in dotted decimal format. device-name is device-name, and refers to the network name, or LU name, of the device. device-name can be up to 8 characters in length.
PAGE 66
STATUS SESSION Using ETN32COM State the session states and meanings are listed below. State Meaning ACCEPT An accept_nw2 is pending on the socket. KEEPALIVE A SETSOCKOPT call is pending. AVAIL An internal state used to test for an available window. REJECT An internal state used when a session is rejected because no window was available. TTYPE The state is waiting for negotiation of terminal-type option to complete.
PAGE 67
STATUS WINDOW Using ETN32COM STATUS WINDOW This command displays the status of the specified window. STATUS WINDOW window-name [ , DETAIL [ , STATS ] ] window-name is #window for the specified window or an asterisk (*) for all windows. DETAIL displays additional detailed information on the status of the window. STATS displays the elapsed time, the number of messages sent and received, and the number of bytes sent and received for the session is displayed.
PAGE 68
STATUS WINDOW Using ETN32COM These are the Window states: State Meaning CLOSED The window has been added, but no application has opened it. OPEN An application has opened the window, but it has not yet posted a Control11 (wait for modem connect). CTRL-11 A Control-11 is pending from an application. SESS-ESTAB A Control-11 is pending and the session has been established. The STATE MACHINE is waiting for 3270 mode negotiation to be completed.
PAGE 69
STOP PROCESS Using ETN32COM STOP PROCESS This command terminates the current TN3270e server process.
PAGE 70
TRACE PROCESS Using ETN32COM TRACE PROCESS This command starts and stops tracing the TN3270e server process. The trace file is created with the ownership and security of the process access ID of the TN3270e server process. TRACE PROCESS trace-options TRACE PROCESS , STOP trace-options are TO trace-file, PAGES num-pages, RECSIZE recsize. trace-file is the name of the trace file. num-pages is the size of the trace file in pages. The range is from 50 to 65,000 pages. The default is 200 pages.
PAGE 71
5 CRT Communication Protocol This section is divided into the following parts:   CRT Mode describes the format of Telnet 3270 data in CRT mode. SNAX/XF Mode on page 5-3 describes the applicable file system procedures for running the TN3270e server in SNAX/XF mode. CRT Mode The TN3270e server windows in CRT mode use data buffers passed from an application which contain standard 3270 buffer orders and text. The TN3270e server does not examine the screen orders.
PAGE 72
Message Format for Inbound Data CRT Communication Protocol Message Format for Inbound Data For inbound data, as shown in Figure 5-2, the buffer returned to the application contains the complete data message, starting with the Attention ID (AID) character, as it was received from the client. Communications characters are stripped. A single buffer is returned to the application. Figure 5-2.
PAGE 73
SNAX/XF Mode CRT Communication Protocol SNAX/XF Mode You can configure the TN3270e server process to emulate the SNAX/XF application interface by specifying the -s switch on the command line. The TN3270e server runs in AM3270 mode by default.
PAGE 74
SNAX/XF CRT SETMODE Procedure CRT Communication Protocol A SETMODE function 144 procedure also returns a value indicating the IBM device type. The IBM device type code returned depends on which IBM terminal emulation is selected for the window during Telnet terminal type negotiation. If the -k option is selected, a value of 2 is returned, indicating that the terminal is not a 3277 or 3276 terminal.
PAGE 75
Extended Highlighting in SNAX/XF Mode CRT Communication Protocol last-params [1].<8:15> is the double-byte character set. If the -k option is not selected, the TN3270e server returns a 0 by default, indicating no double-byte character set. If the -k option is selected, the TN3270e server returns a 3, indicating IBM MIXED. Other SNAX/XF CRT SETMODE Procedures Some SNAX/XF SETMODE procedures do not function in a TCP/IP environment or with the TN3270e server.
PAGE 76
CRT Communication Protocol Extended Highlighting in SNAX/XF Mode TN3270e Server Manual—422923-003 5-6
PAGE 77
6 ITI Communication Protocol This section is divided into the following parts:   Interactive Terminal Interface describes the interactive terminal interface (ITI). Applicable File System Procedures (SNAX/XF Mode) on page 6-4 describes the application interface to the TN3270e server when it is configured to emulate SNAX/XF. Interactive Terminal Interface A TN3270e server window assigned to the interactive terminal interface (ITI) protocol is used to run the HP Tandem Advanced Command Language (TACL).
PAGE 78
Message Formats ITI Communication Protocol Message Formats The ITI protocol, as shown in Figure 6-1, takes an output buffer containing text to be written and adds the following information before the existing text: 1. A command character (CMD) 2. A write control character (WCC) 3. Appropriate 3270 screen orders The text line is following by: 1. An IS-A-COMMAND (IAC) character 2. An end-of-record (EOR) character Figure 6-1.
PAGE 79
ITI Considerations ITI Communication Protocol   The ITI protocol does not handle the BACKSPACE and LINE DELETE terminal local operations. The ITI protocol maintains an output line count and cursor address. The output data display wraps. A screen separator of a line of equal signs (=) indicates the bottom of the screen. The screen separator updates each time a READ or WRITEREAD request is completed.
PAGE 80
Applicable File System Procedures (SNAX/XF Mode) ITI Communication Protocol Applicable File System Procedures (SNAX/XF Mode) You can configure the TN3270e server process to emulate the SNAX/XF application interface by specifying the -s switch on the command line. The TN3270e server runs in AM3270 mode by default.
PAGE 81
CONTROL Operations ITI Communication Protocol CONTROL Operations CONTROL operations perform device-dependent I/O operations. The CONTROL 11 and 12 procedures are used for session management. CONTROL 11 is used to wait for a session to be established. CONTROL 12 disconnects a session. CALL CONTROL (filenumber, operation, parameter [, tag ]) filenumber INT:value is a number of an open file, identifying the file to which the CONTROL procedure performs an I/O operation.
PAGE 82
READ[x] Procedure ITI Communication Protocol READ[x] Procedure A READ procedure causes the blocks received by the TN3270e server to be collected and stripped of any communication control characters. When the final block is received, the READ request is completed to the application process with text only. CALL READ[x] (filenumber, buffer, read-count [, count-read ] [, tag ]) filenumber INT:value is the number of the file to be read. buffer INT .ref:* (for READ) STRING .
PAGE 83
SETMODE Function Procedures ITI Communication Protocol SETMODE Function Procedures The SETMODE function procedures are used to set specified terminal characteristics for the ITI protocol. The function parameter can have the value of 8, 11, 12, or 20. Uses for parameter-1 and parameter-2 vary, depending on the value of function. CALL SETMODE (function [, parameter-1 ] [, parameter-2 ]) function INT:value 6 (set spring control) is not supported. 7 (set auto line feed) is not supported.
PAGE 84
SETMODE Function Procedures ITI Communication Protocol parameter-2 INT:value 2 0 0 normal access to terminal (default). 1 BREAK access to terminal. sets the display or nondisplay of keyboard data: parameter-1 INT:value 0 causes the next WRITE procedure to the terminal to be preceded by a non-display video attribute, which in turn inhibits the display of all characters following the current cursor position.
PAGE 85
SETMODE function 144 Procedure ITI Communication Protocol SETMODE function 144 Procedure The SETMODE function 144 procedure is used in a SNAX environment to find the single-byte character set and double-byte character set (if any) defined for the logical unit (LU). In an TN3270e server environment, SETMODE function 144 returns hardcoded values for the Katakana (single-byte) and Kanji (double-byte) character set codes.
PAGE 86
SETMODE function 144 Procedure ITI Communication Protocol last-params [0].<1:7> IBM device type can be 0 through 3, inclusive. 0: Printer (PRT protocol; not supported) 1: IBM-3277 2: Not 3277 or 3276 (this value is always returned when the -k option is set) 3: IBM-3276 last-params [0].<8:15> is the value of ALLOWEDMIX LU attribute. The TN3270e server always returns a 0. last-params [1].<0:7> is the logical unit (LU) single-byte character set.
PAGE 87
SETPARAM Function 3 Procedure ITI Communication Protocol SETPARAM Function 3 Procedure The SETPARAM function 3 procedure sets or fetches the parameters for handling a BREAK indication received from a terminal. CALL SETPARAM (filenumber, function [, param-array ] [, param-count ] [, last params ] [, last-param-count ]) filenumber INT:value is the number of an open file to which BREAK handling parameters are sent. function INT:value sets or fetches parameters for BREAK handling. param-array INT .
PAGE 88
SETPARAM Function 3 Procedure ITI Communication Protocol param-count INT:value is the number of bytes in param-array. The value for this parameter must be 8. last-params INT .ref:1 is the returned previous parameter settings of function passed by reference (INT .ref:1). last-params[n] an integer array containing: last-params[0] sets BREAK ownership: 0 disable BREAK (default). 1 enable BREAK.
PAGE 89
SETPARAM Function 3 Procedure ITI Communication Protocol BREAK Message Considerations Whenever the TN3270e server detects the input of a PA1 key (simulated BREAK key) from a 3270 terminal configured for ITI protocol, a BREAK message is sent to the owner of the break for that terminal. The six parameters of the BREAK message are: 1. -20, which identifies the BREAK message 2. The logical device number of the I/O operations process 3. The system number of the I/O operations process 4.
PAGE 90
WRITE [x] Procedure ITI Communication Protocol WRITE [x] Procedure A WRITE procedure adds communication characters to the text to be written, and then writes the data to the device. WRITE procedures to the application process complete immediately, advancing an internal line counter. If the new line count positions the next line to be written at the bottom of the screen, the bottom of the screen wraps to the top.
PAGE 91
WRITEREAD [x] Procedure ITI Communication Protocol WRITEREAD [x] Procedure A WRITEREAD procedure is processed by the TN3270e server as a WRITE request followed by a READ request from the application process. CALL WRITEREAD[x] (filenumber, buffer, write-count, readcount [, count-read ] [, tag ]) filenumber INT:value is the number of the file where the WRITE/READ is to occur. buffer INT .ref:* (for WRITEREAD) STRING .
PAGE 92
WRITEREAD [x] Procedure ITI Communication Protocol TN3270e Server Manual—422923-003 6-16
PAGE 93
7 SPI Interface This section summarizes the Subsystem Programmatic Interface (SPI) commands and describes those supported by the TN3270e server.
PAGE 94
Commands and Responses SPI Interface Table 7-1 lists valid command and object combinations. Table 7-1. Command and Object Combinations Objects Commands Windows ABORT X ADD X ALTER X DELETE X Process X GETVERSION X INFO X LISTOPEN X STATUS X X STOP TRACE Session X X X X Errors are returned in the token ZSPI-TKN-RETCODE. Error values are enumerated in ZETN-DDL-RETCODE-ENM. Commands and Responses This section describes the TN3270e server SPI commands and responses.
PAGE 95
ZETN-CMD-ADD SPI Interface Token descriptions: ZETN-TKN-SUBDEV is the window name. To abort all windows, set the value to an asterisk (*). ZETN-TKN-SUBDEV and ZETN-TKN-RETCODE are returned for each window aborted. ZSPI-TKN-CONTEXT is returned if you specify abort for all windows and not all response records could be returned in the buffer provided. In this case, you must issue a continuation request with the ZSPI-TKN-CONTEXT token to abort the remaining windows.
PAGE 96
ZETN-CMD-ALTER SPI Interface ZETN-CMD-ALTER Command: ZETN-CMD-ALTER Object: ZETN-OBJ-PROCESS Purposes: a. Switches logging to the specified EMS collector. b. Changes NLS character values. c. Enables and disables national language support (NLS) translation Request tokens: a. ZETN-TKN-FILENAME b. ZETN-TKN-NLS-TABLENAME ZETN-TKN-NLS-TABLEADDRESS ZETN-TKN-NLS-TABLEVALUE c. ZETN-TKN-NLS-TRANSLATION Response tokens: a. ZETN-TKN-FILE-ERROR b. None. c. None.
PAGE 97
ZETN-CMD-DELETE SPI Interface ZETN-CMD-DELETE Command: ZETN-CMD-DELETE Object: ZETN-OBJ-WINDOW Purpose: Deletes a window from the TN3270e server process. Request tokens: ZETN-TKN-SUBDEV Response tokens: [ ZSPI-TKN-DATALIST ] ZETN-TKN-SUBDEV ZETN-TKN-RETCODE [ ZSPI-TKN-ENDLIST ] [ ZSPI-TKN-CONTEXT ] The window must be in the CLOSED state. Token descriptions: ZETN-TKN-SUBDEV is the window name. You can use an asterisk (*) to delete all windows.
PAGE 98
ZETN-CMD-INFO SPI Interface ZETN-CMD-INFO Command: ZETN-CMD-INFO Object: ZETN-OBJ-PROCESS Purposes: a. Returns static information about the TN3270e server process. b. Returns the contents of the NLS translation tables. Request tokens: a. None. b. ZETN-TKN-NLS-TABLENAME ZETN-TKN-NLS-TABLEADDRESS ZETN-TKN-NLS-DISPLAY-BASE ZETN-TKN-NLS-ALLORONE-CHOICE Response tokens: a. ZETN-TKN-BANNER b.
PAGE 99
ZETN-CMD-LISTOPEN SPI Interface ZETN-CMD-LISTOPEN Command: ZETN-CMD-LISTOPEN Object: ZETN-OBJ-WINDOW Purpose: Returns a list of openers of the specified window. Request tokens: ZETN-TKN-SUBDEV Response tokens: ZSPI-TKN-DATALIST ZETN-TKN-LISTOPEN-RSP ZSPI-TKN-ENDLIST Token descriptions: ZETN-TKN-SUBDEV is the window name. ZETN-TKN-LISTOPEN-RSP contains the process identification of the opener.
PAGE 100
ZETN-CMD-STATUS SPI Interface ZETN-TKN-SOCKADDR-IN contains the IP address and port number for which status is requested. SOCKADDR.PORT may be a specific port or –1 to obtain the status of all sessions with that IP address. ZETN-TKN-DEVICE-NAME contains the device name for which status is requested. ZETN-TKN-SUBDEV is the window name. ZETN- MAP-STATUS-SESSION-RSP is an extensible structured token containing information about the session.
PAGE 101
ZETN-CMD-STOP SPI Interface ZETN-CMD-STOP Command: ZETN-CMD-STOP Object: ZETN-OBJ-PROCESS Purpose: Terminates the TN3270e server process. Request tokens: None. Response tokens: None. ZETN-CMD-TRACE Command: ZETN-CMD-TRACE Object: ZETN-OBJ-PROCESS Purpose: Initiates/terminates tracing of the TN3270e server process. Request tokens: [ ZETN-TKN-TRACE-OPTS ] Response tokens: ZETN-TKN-TRACE-ERROR Token descriptions: ZETN-TKN-TRACE-OPTS is omitted to stop tracing.
PAGE 102
ZETN-CMD-TRACE SPI Interface TN3270e Server Manual—422923-003 7-10
PAGE 103
8 Event Messages This section describes the Event Management Service (EMS) event messages for the TN3270e server.
PAGE 104
ZETN-EVT-ABORT Event Messages ZETN-EVT-ABORT Event ZETN-EVT-ABORT Tokens ZETN-TKN-ABORT-TEXT Token Descriptions ZETN-TKN-ABORT-TEXT contains a description of the cause of the error. ZETN-EVT-ASSERTION-FAILURE Event ZETN-EVT-ASSERTION-FAILURE Tokens ZETN-TKN-ASSERTION-CONDITION ZETN-TKN-SOURCE-FILE ZETN-TKN-EDIT-SEQNUM Token Descriptions ZETN-TKN-ASSERTION-CONDITION is a text string containing the illogical condition.
PAGE 105
ZETN-EVT-FILE-ERROR Event Messages ZETN-EVT-FILE-ERROR Event ZETN-EVT-FILE-ERROR Tokens ZETN-TKN-FILE-OP ZETN-TKN-FILE-ERROR [ ZETN-TKN-SUBDEV ] [ ZETN-TKN-HOST-NAME ] [ ZETN-TKN-SOCKADDR-IN ] Token Descriptions ZETN-TKN-FILE-OP specifies which NonStop OS procedure returned the error. ZETN-TKN-FILE-ERROR is the error returned by the NonStop OS procedure. ZETN-TKN-SUBDEV is the window name, if the error occurred while in session.
PAGE 106
ZETN-EVT-FSM-ERROR Event Messages ZETN-EVT-FSM-ERROR Event ZETN-EVT-FSM-ERROR Tokens ZETN-TKN-FSM ZETN-TKN-FSMID ZETN-TKN-FSMOBJ Token Descriptions ZETN-TKN-FSM is a structure containing the previous state, the event, the action, and the next state. ZETN-TKN-FSMID is an enumeration identifying the state machine that encountered the error. ZETN-TKN-FSMOBJ contains the name of the object on which the state machine error occurred.
PAGE 107
ZETN-EVT-LOG-SWITCH Event Messages ZETN-EVT-LOG-SWITCH Event ZETN-EVT-LOG-SWITCH Tokens ZETN-TKN-FILENAME Token Descriptions ZETN-TKN-FILENAME is the name of the new EMS collector. ZETN-EVT-NET-ERROR Event ZETN-EVT-NET-ERROR Tokens ZETN-TKN-OPCODE ZETN-TKN-SOCKET-ERROR ZETN-TKN-PROCESS-NAME Token Descriptions ZETN-TKN-OPCODE specifies the socket operation that returned the error. ZETN-TKN-SOCKET-ERROR specifies the error returned by the socket operation.
PAGE 108
ZETN-EVT-RECV-ABORT Event Messages Tokens None. ZETN-EVT-RECV-ABORT Event ZETN-EVT-RECV-ABORT Tokens ZETN-TKN-FILE-ERROR ZETN-TKN-OPNAME Token Descriptions ZETN-TKN-FILE-ERROR is the NonStop OS error that occurred. ZETN-TKN-OPNAME is the NonStop OS procedure that returned the error.
PAGE 109
ZETN-EVT-SESS-ERROR Event Messages ZETN-EVT-SESS-ERROR Event ZETN-EVT-SESS-ERROR Tokens ZETN-TKN-OPCODE ZETN-TKN-SOCKET-ERROR ZETN-TKN-SUBDEV ZETN-TKN-SOCKADDR-IN [ ZETN-TKN-HOST-NAME ] Token Descriptions ZETN-TKN-OPCODE specifies the socket operation that returned the error. ZETN-TKN-SOCKET-ERROR is the error returned by the TCP/IP socket library. ZETN-TKN-SUBDEV is the name of the window associated with the session on which the error occurred.
PAGE 110
ZETN-EVT-SESS-ESTAB Event Messages ZETN-EVT-SESS-ESTAB Event ZETN-EVT-SESS-ESTAB Tokens ZETN-TKN-SUBDEV ZETN-TKN-SOCKADDR-IN [ ZETN-TKN-HOST-NAME ] Token Descriptions ZETN-TKN-SUBDEV is the window name. ZETN-TKN-SOCKADDR-IN is a structure containing the IP address and port number of the client. ZETN-TKN-HOST-NAME is present if name resolution is enabled and the client’s IP host name was found.
PAGE 111
ZETN-EVT-SESS-TERM Event Messages ZETN-EVT-SESS-TERM Event ZETN-EVT-SESS-TERM Tokens ZETN-TKN-REASON ZETN-TKN-SESSION-STATS ZETN-TKN-SUBDEV ZETN-TKN-SOCKADDR-IN [ ZETN-TKN-HOST-NAME ] Token Descriptions ZETN-TKN-REASON specifies the reason the session was terminated. ZETN-TKN-SESSION-STATS contains the elapsed time, number of messages sent and received, and the number of bytes sent and received. ZETN-TKN-SUBDEV is the window name. This token is present only if the session was connected to a window.
PAGE 112
ZETN-EVT-SPI-ERROR Event Messages ZETN-EVT-SPI-ERROR Event ZETN-EVT-SPI-ERROR Tokens ZETN-TKN-SPI-ERROR ZETN-TKN-OPNAME Token Descriptions ZETN-TKN-SPI-ERROR is the error returned by the SPI procedure. ZETN-TKN-OPNAME is the SPI procedure that returned the error. ZETN-EVT-STARTED Event ZETN-EVT-STARTED Token ZETN-TKN-BANNER Token Description ZETN-TKN-BANNER contains the version string of the TN3270e server process.
PAGE 113
ZETN-TKN-BANNER Event Messages ZETN-TKN-BANNER Event ZETN-TKN-BANNER Token ZETN-TKN-BANNER Token Description ZETN-TKN-BANNER contains the version string of the TN3270e server process.
PAGE 114
ZETN-TKN-BANNER Event Messages TN3270e Server Manual—422923-003 8-12
PAGE 115
9 Trace Formatter The section describes the TN3270e server trace formatter. The trace formatter prints the results of traces captured by the trace facility. To start the trace formatter, enter the following command at a TACL prompt. RUN isv.etnfmttr / tacl-opts / [ objname ] isv is the installation volume-subvolume. tacl-opts IN trace-file is the name of the trace file to be printed. It must be the name of an existing disk file or the name of a currently executing TN3270e server process.
PAGE 116
Trace Formatter (Part 2 - information about a $RECEIVE message) (1) (2) (3) (4) opener-pid FILE = opener-file-num [ READ CNT = count ] MSGTAG = msgtag (5) SYNCID = syncid (6) sys-msgtype (Part 3 - the contents of the buffer) An example of the contents of the buffer follows, shown in hexadecimal, ASCII, and EBCDIC. (Part 1) (1) 20:28:00.972 (2) (3) UC.00 P=%006742 AWAITIO (4) FNUM=000 (5) (7) $RECEIVE COUNT=0036 (8) system message received (6) (Part 2) (1) FROM \CSO.03.
PAGE 117
A Terminal Models in SNAX/XF Mode Table A-1 lists the terminal model numbers that the TN3270e server recognizes when performing terminal-type subnegotiation in SNAX/XF mode. Table A-1.
PAGE 118
Terminal Models in SNAX/XF Mode Table A-1.
PAGE 119
B Client Messages The following is a list of messages that the TN3270e server can send to the client. All messages, unless otherwise indicated, terminate the session. [host-name:] APPLICATION DISCONNECTED Cause. The application terminated the session. Effect. The session between the TN3270e server and the application is terminated. Recovery. Informative message only; no corrective action is needed. CLIENT REFUSED OPTION: required-telnet-option Cause.
PAGE 120
Client Messages NOT IN 3270 MODE, INPUT DISCARDED Cause. The client sent input during option negotiation. Effect. The input from the client is ignored. Recovery. Informative message only; no corrective action is needed. REJECT_CONN_PARTNER (0x00) Cause. This message is a device-type reject reason code that the TN3270e server sent to a client in response to a device-type request command.
PAGE 121
Client Messages REJECT_INV_ASSOCIATE (0x02) Cause. This message is a device-type reject reason code that the TN3270e server sent to a client in response to a device-type request command. The client used the ASSOCIATE command, and the device-type is neither a printer nor a terminal. Effect. The session could not be established with the client. Recovery. Notify your system operator that the client is requesting an invalid printer association. REJECT_INV_DEVICE_NAME (0x03) Cause.
PAGE 122
Client Messages REJECT_TYPE_NAME_ERROR (0x05) Cause. This message is a device-type reject reason code that the TN3270e server sent to a client in response to a device-type request command. The requested devicename is incompatible with the requested device-type; for example, such an incompatibility could be a terminal/printer mismatch. Effect. The session could not be established with the client. Recovery.
PAGE 123
Client Messages TERM TYPE NOT RECOGNIZED Cause. During option negotiation, the client did not send a recognized terminal type. Effect. The session could not be established with the client. Recovery. Notify your system operator that the client is requesting support for a terminal type that the system does not provide. TERM TYPE TOO LONG Cause. The maximum allowed length of a terminal model is 40 characters. The client sent a terminal type longer than 40 characters.
PAGE 124
Client Messages TN3270e Server Manual—422923-003 B-6
PAGE 125
C ETN32COM Error Messages This appendix describes each error message displayed by ETN32COM, the operator interface to the TN3270e server. Error Messages 1 PAGES must be >= 10 and <= 62255 Cause. The number of pages specified for a trace was outside the range of 10 through 62,255, inclusive. Effect. ETN32COM was not started. Recovery. Reenter the start command, specifying a number from 10 through 62,255, inclusive. 2 Illegal file name Cause. An illegal file name was specified. Effect.
PAGE 126
Error Messages ETN32COM Error Messages 4 RECSIZE must be <= 4095 Cause. The RECSIZE value exceeded the maximum size for trace records of 4095 bytes. Effect. The trace process was not started. Recovery. Reenter the command, specifying a record size from 1 through 4,095, inclusive. 5 Illegal subdevice Cause. The subdevice identifier was invalid. Effect. The command did not execute. Recovery. Reenter the command, specifying a valid window name.
PAGE 127
Error Messages ETN32COM Error Messages 8 Process is not ETN32SRV Cause. The TN3270e server process name was invalid. Effect. The command did not execute and the TN3270e server did not start. Recovery. Ensure that the process you are trying to open is executable by ETN32SRV and then reenter the command. 9 SSID is not ETN32SRV Cause. A process was opened that returned an incorrect subsystem ID (SSID). Effect. The command did not execute. Recovery.
PAGE 128
Error Messages ETN32COM Error Messages 12 SPI: Invalid command Cause. The TN3270e server received an SPI command that it did not recognize. Effect. The command did not execute. Recovery. Check the input for accuracy. If necessary, enter the HELP ALL command to display a list of valid commands. 13 SPI: Invalid object Cause. The TN3270e server received an SPI command containing an object type that it did not recognize. Effect. The command did not execute. Recovery.
PAGE 129
Error Messages ETN32COM Error Messages 16 Unknown return code: return-code Cause. The currently open process returned an unrecognized error in response to an SPI command, where return-code specifies the return code. Effect. The command did not execute. Recovery. Advise your HP representative of the circumstances of the condition. 17 WINDOW NOT FOUND Cause. A command referred to a window that could not be located. Effect. The command did not execute. Recovery.
PAGE 130
Error Messages ETN32COM Error Messages 20 TOO MANY WINDOWS Cause. An additional window could not be added because 255 windows are already defined. Effect. The command did not execute. Recovery. Informative message only; no corrective action is needed. 21 SPI: WRONG SSID Cause. The TN3270e server rejected the SSID from ETN32COM. Effect. The command did not execute. Recovery. Ensure that the process you are trying to open is executable by ETN32SRV. 22 SIO: Error err Cause.
PAGE 131
Error Messages ETN32COM Error Messages 24 SPI: Invalid buffer format Cause. The SPI interface detected an invalid buffer. Effect. The command did not execute. Recovery. Advise your HP representative of the circumstances of the condition. 25 SPI: Illegal parameter Cause. The SPI interface detected an invalid parameter. Effect. The command did not execute. Recovery. Check the input for parameter accuracy. If necessary, enter the HELP command to display a description of the parameter(s).
PAGE 132
Error Messages ETN32COM Error Messages Recovery. Advise your HP representative of the circumstances of the condition. 29 SPI: checksum error Cause. A checksum error was detected on the SPI buffer. Effect. The command did not execute. Recovery. Advise your HP representative of the circumstances of the condition. 30 SPI: internal error Cause. An internal error occurred in one of the SPI routines. Effect. The command did not execute. Recovery.
PAGE 133
Error Messages ETN32COM Error Messages Recovery. Advise your HP representative of the circumstances of the condition. 34 Error err switching EMS collectors Cause. A file system error occurred when opening a new EMS collector process, where err specifies the error. Effect. The command did not execute and the EMS collector was not switched. Recovery. Resolve the error condition as described in the Guardian Procedure Errors and Messages Manual and then reenter the command. 35 Syntax error Cause.
PAGE 134
Error Messages ETN32COM Error Messages 38 Trace usesegment error err Cause. An error occurred in a USESEGMENT call, where err specifies the error returned by USESEGMENT. Effect. The command did not execute. Recovery. Advise your HP representative of the circumstances of the condition. 39 Trace already active Cause. You attempted another trace while one was in progress. Effect. The command did not execute. Recovery. Informative message only; no corrective action is needed. 40 Tracing not active Cause.
PAGE 135
Error Messages ETN32COM Error Messages 42 Writeread error: err Cause. An error occurred during a WRITEREAD request to the TN3270e server process, where err specifies the NonStop OS file system error. Effect. The command did not execute and the trace process was not started. Recovery. Resolve the error condition as described in the Guardian Procedure Errors and Messages Manual and then reenter the command. 43 Integer too large Cause.
PAGE 136
Error Messages ETN32COM Error Messages 46 Version mismatch with server process Cause. An attempt was made to open a TN3270e server process whose version is incompatible with the ETN32COM process. Effect. The command did not execute. Recovery. Make sure that the versions of both ETN32COM and ETN32SRV are compatible. See the TN3270e server softdoc for updates on the latest software versions required. If necessary, advise your HP representative of the circumstances of the condition.
PAGE 137
Error Messages ETN32COM Error Messages syntax. For information about the HELP command, see HELP on page 4-15. Finally, retry the command.
PAGE 138
Error Messages ETN32COM Error Messages TN3270e Server Manual—422923-003 C-14
PAGE 139
D TN3270e Server Messages This appendix describes messages sent by the TN3270e server. 1 STARTED banner banner is the version of the TN3270e server software for the process. Cause. The TN3270e server process was started. Effect. The TN3270e server process can be configured. Recovery. Informational message only; no corrective action is needed. 2 SHUTDOWN Cause. The TN3270e server received a STOP PROCESS command. Effect. The TN3270e server is terminating. Recovery.
PAGE 140
TN3270e Server Messages 3 Session established. Window subdev [ Host: host-name ] IPADDR=ipaddr PORT=port subdev is the name of the TN3270e server window. host-name is the name of the internet protocol (IP) host (if known) that is running the TN3270e server client session. ipaddr is the remote internet protocol (IP) address of the client of the TN3270e server session. port is the remote port number of the client of the TN3270e server session. Cause. A session was established with the TN3270e server process.
PAGE 141
TN3270e Server Messages 4 Session opcode Error err Window subdev [ Host: host-name ] IPADDR=ipaddr PORT=port opcode is the socket operation that returned the error. err identifies the error returned by the Transmission Control Protocol/Internet Protocol (TCP/IP) process. subdev is the name of the window associated with the session during which the error occurred. host-name is the name of the internet protocol (IP) host (if known) running the TN3270e server client session.
PAGE 142
TN3270e Server Messages 5 Session terminated. Reason reason Window subdev [ Host: host-name ] IPADDR=ipaddr PORT=port Elapsed days Days hrs:mins:secs Msgs sent/rcvd: msgs-sent / msgs-rcvd Bytes sent/rcvd: bytes-sent / bytes-rcvd reason is the reason the user session was terminated. subdev is the name of the window associated with the session that was terminated. host-name is the name of the internet protocol (IP) host (if known) running the TN3270e server client session.
PAGE 143
TN3270e Server Messages Cause. A user session was terminated for the reason specified by reason. Effect. The window is available for reuse unless it was closed due to an application failure. Recovery. Reestablish the session if necessary. 7 SPI opname Error err opname is the name of a NonStop Kernel file-system operation. err identifies the error returned by the Subsystem Programmatic Interface (SPI) procedure. Cause. An error occurred on a call to a SPI routine. Effect.
PAGE 144
TN3270e Server Messages 9 fsmid State machine error State=fsm.state Event=fsm.event ( objname ) fsmid is the identification of the finite state machine (FSM) within the TN3270e server that generated the event. fsm.state is the current state of the FSM. fsm.event is a signal causing a predetermined action based on the current state and error. objname is the name of the object for which the FSM error occurred. Cause. A finite state machine (FSM) error occurred. Effect.
PAGE 145
TN3270e Server Messages err identifies a file-system error. subdev is the name of the window (if known) associated with the session on which the error occurred. host-name is the name of the internet protocol (IP) host (if known) running the TN3270e server client session. ipaddr is the remote internet protocol (IP) address of the client (if known) of the TN3270e server session. port is the remote port number of the client (if known) of the TN3270e server session. Cause.
PAGE 146
TN3270e Server Messages 12 ASSERTION FAILURE: ( condition ) FILE: source-file Line: edit-linenumber condition is the error condition. source-file identifies the NonStop Kernel source file where the condition occurred. edit-linenumber identifies the line number of the NonStop Kernel source file where the condition occurred. Cause. The TN3270e server encountered a logical inconsistency in the code. Effect. The TN3270e server terminates, and then creates an Inspect save file. Recovery.
PAGE 147
TN3270e Server Messages Cause. The TN3270e server encountered an input/output (I/O) error on the socket used to monitor network connections requests. Effect. The socket to the TCP/IP process is closed and reopened. Recovery. The TN3270e server continues to try to reestablish the socket with TCP/IP for errors 14, 66, and 201. Monitor the TN3270e server to see if the socket can be restored. If the TN3270e server cannot automatically restore the socket, restart the TCP/IP process.
PAGE 148
TN3270e Server Messages 16 Primary Process Established: Process Name = process-name process-name is the TN3270e server process. Cause. The primary process of a TN3270e server NonStop pair started. Effect. The primary process tries to start a backup process. Recovery. Informational message only; no corrective action is needed. 17 Backup Process Established: Process Name = process-name process-name is the TN3270e server process. Cause. The backup process of a TN3270e server NonStop pair started. Effect.
PAGE 149
TN3270e Server Messages Effect. The primary process tries to start another backup process. Recovery. Informational message only; no corrective action is needed.
PAGE 150
TN3270e Server Messages TN3270e Server Manual—422923-003 D-12
PAGE 151
E Subsystem-Specific Tokens Tokens specific to the TN3270e server subsystem are described in this appendix. They are identified by a token name that starts with ZETN.
PAGE 152
Token List Subsystem-Specific Tokens ZETN-TKN-PROCESS-NAME Token Code (See page E-17) ZETN-TKN-REASON Token Code (See page E-18) ZETN-TKN-RETCODE Token Code (See page E-19) ZETN-TKN-SESSION-STATS Token Code (See page E-20) ZETN-TKN-SOCKADDR-IN Token Code (See page E-21) ZETN-TKN-SOCKET-ERROR Token Code (See page E-21) ZETN-TKN-SOURCE-FILE Token Code (See page E-23) ZETN-TKN-SPI-ERROR Token Code (See page E-23) ZETN-TKN-SUBDEV Token Code (See page E-23) ZETN-TKN-TRACE-ERROR Token Code (See page E-24) TN32
PAGE 153
Token Definitions Subsystem-Specific Tokens Token Definitions Tokens specific to the TN3270e server subsystem are defined in the following section. ZETN-MAP-INFO-TABLE-RSP Token Map This structured token contains the national language support table values displayed. Token Map ZETN-MAP-INFO-TABLE-RSP Token Type ZETN-TYP-INFO-TABLE Token Definition Definition ZETN-DDL-INFO-TABLE-RSP. 02 CONTENTS Type BINARY 16[256]. 02 SENTINEL Type BINARY 16.
PAGE 154
ZETN-MAP-STATUS-PROCESS-RSP Token Map Subsystem-Specific Tokens ZETN-MAP-STATUS-PROCESS-RSP Token Map This extensible structured token returns status information about the TN3270e server process. Token Map ZETN-MAP-STATUS-PROCESS-RSP Token Type ZETN-TYP-STATUS-PROCESS Token Definition Definition ZETN-DDL-STATUS-PROCESS-RSP. 02 NUM WINDOWS Type BINARY 16. 02 POOL STATS Type ZETN-DDL-POOL-STATS. 02 LOG-FILE Type ZSPI-DDL-CHAR50. 02 LOG-FILE-LEN Type BINARY 16. 02 TRACE-FILE Type ZETN-DDL-CHAR50.
PAGE 155
ZETN-MAP-STATUS-SESSION-RSP Token Map Subsystem-Specific Tokens ZETN-MAP-STATUS-SESSION-RSP Token Map This is an extensible structured token that contains information about one session. Token Map ZETN-MAP-STATUS-SESSION-RSP Token Type ZETN-TYP-STATUS-SESS-RSP Token Definition Definition ZETN-DDL-STATUS-SESSION-RSP. 02 SESSION-STATE Type 02 HOST-NAME Type 02 SOCKADDR-IN Type 02 TERM-MODEL Type 02 WINDOW-NAME Type 02 DEVICE-NAME Type End BINARY 16. ZETN-DDL-HOST-NAME. ZETN-DDL-SOCKADDR-IN. ZETN-DDL-TTYPE.
PAGE 156
ZETN-MAP-STATUS-WINDOW-RSP Token Map Subsystem-Specific Tokens WINDOW-NAME contains the subdevice name. ZETN-MAP-STATUS-WINDOW-RSP Token Map This is an extensible structured token containing information about one window. Token Map ZETN-MAP-STATUS-WINDOW-RSP Token Type ZETN-TYP-STATUS-WINDOW-RSP Token Definition Definition ZETN-DDL-STATUS-WINDOW-RSP. 02 WINDOW-STATE Type 02 DEV-TYPE Type 02 NUM-OPENS Type 02 CALLER Type 02 DEVICE-NAME Type End BINARY 16. BINARY 16. BINARY 16. ZETN-DDL-SOCKADDR-IN.
PAGE 157
ZETN-TKN-ABORT-TEXT Token Code Subsystem-Specific Tokens Caller is ZETN-DDL-SOCKADDR-IN. Definition ZETN-DDL-SOCKADDR-IN. 02 SIN-FAMILY 02 SIN-PORT 02 SIN-ADDR End Type Binary 16. Type ZETN-DDL-PORT. Type ZETN-DDL-IN-ADDR. ZETN-TKN-ABORT-TEXT Token Code This token contains a description of the cause of the error. Token Code ZETN-TKN-ABORT-TEXT Token Type ZETN-TYP-ABORT-TEXT Token Definition Definition ZETN-DDL-ABORT-TEXT Type Character Occurs Varying.
PAGE 158
ZETN-TKN-DEVICE-NAME Token Code Subsystem-Specific Tokens Token Definition Definition ZETN-DDL-BANNER Type Character Occurs Varying. ZETN-TKN-DEVICE-NAME Token Code This token contains the device name associated with a TN3270e server window. Token Code ZETN-TKN-DEVICE-NAME Token Type ZETN-TYP-DEVNAME Token Definition Definition ZETN-DDL-DEVNAME. ZETN-TKN-DEVICE-TYPE Token Code This token contains the device type associated with a TN3270e server window.
PAGE 159
ZETN-TKN-EDIT-SEQNUM Token Code Subsystem-Specific Tokens ZETN-TKN-EDIT-SEQNUM Token Code This token is a structure containing the line number on which the illogical condition was detected. Token Code ZETN-TKN-EDIT-SEQNUM Token Type ZETN-TYP-EDIT-SEQNUM Token Definition Definition ZETN-DDL-EDIT-SEQNUM. 02 LINE-NUMBER 02 FRACTION End Type BINARY 16. Type BINARY 16. ZETN-TKN-FILE-ERROR Token Code This token contains the NonStop OS file system error that occurred.
PAGE 160
ZETN-TKN-FSM Token Code Subsystem-Specific Tokens ZETN-TKN-FSM Token Code This token is a structure containing the previous state, the event, the action, and the next state. Token Code ZETN-TKN-FSM Token Type ZETN-TYP-FSM Token Definition Definition ZETN-DDL-FSM. 02 STATE 02 EVENT 02 ACTION 02 NEXT-STATE End Type Type Type Type BINARY BINARY BINARY BINARY 16. 16. 16. 16. ZETN-TKN-FSMID Token Code This token identifies the state machine that encountered the error.
PAGE 161
ZETN-TKN-FSMOBJ Token Code Subsystem-Specific Tokens ZETN-TKN-FSMOBJ Token Code This token contains the name of the object for which the state machine error occurred.
PAGE 162
ZETN-TKN-GETHOST-ERR Token Code Subsystem-Specific Tokens ZETN-TKN-GETHOST-ERR Token Code This token identifies the error returned by the GETHOSTBYADDR function. Token Code ZETN-TKN-GETHOST-ERR Token Type ZETN-TYP-GETHOST-ERR Token Definition ZETN-DDL-GETHOST-ERR-ENM. ZETN-DDL-GETHOST-ERR-ENM identifies possible GETHOSTBYADDR errors. Definition ZETN-DDL-GETHOST-ERR-ENM.
PAGE 163
ZETN-TKN-NLS-ALLORONE-CHOICE Token Code Subsystem-Specific Tokens Token Type ZETN-TYP-LISTOPEN-RSP Token Definition Definition ZETN-DDL-LISTOPEN-RSP. 02 OPENER 02 OPENER-LEN 02 PRIMARY 02 BACKUP End Type Type Type Type ZSPI-DDL-CHAR50. BINARY 16. ZETN-DDL-OPENID. ZETN-DDL-OPENID. OPENER is the process name of the opener. OPENER-LEN is the number of characters in the process name string. PRIMARY contains the process handle and file number of the primary process of the opener. Definition ZETN-DDL-OPENID.
PAGE 164
ZETN-TKN-NLS-DISPLAY-BASE Token Code Subsystem-Specific Tokens ZETN-TKN-NLS-DISPLAY-BASE Token Code This token specifies the numeric base in which NLS table data is displayed. Token Code ZETN-TKN-DISPLAY-BASE Token Type ZSPI-TYP-INT ZETN-TKN-NLS-TABLEADDRESS Token Code This token identifies one of the 256 bytes in either the NLS input translation table or the NLS output translation table, per the ZETN-TKN-NLS-TABLENAME value.
PAGE 165
ZETN-TKN-NLS-TRANSLATION Token Code Subsystem-Specific Tokens ZETN-TKN-NLS-TRANSLATION Token Code This token specifies that NLS translation is disabled (value=0) or enabled (value=1). Token Code ZETN-TKN-TRANSLATION Token Type ZSPI-TYP-INT ZETN-TKN-OPCODE Token Code This token contains the socket operation that returned the error. Token Code ZETN-TKN-OPCODE Token Type ZETN-TYP-OPCODE Token Definition TRACE-OP-CODES.
PAGE 166
ZETN-TKN-OPCODE Token Code Subsystem-Specific Tokens TRACE-OP-CODES identifies various I/O operations. Definition TRACE-OP-CODES.
PAGE 167
ZETN-TKN-OPNAME Token Code Subsystem-Specific Tokens ZETN-TKN-OPNAME Token Code This token contains the name of the procedure that returned the error. Token Code ZETN-TKN-OPNAME Token Type ZSPI-TYP-CHAR16 ZETN-TKN-PROCESS-NAME Token Code This token contains the name of TCP/IP process that is reporting the error.
PAGE 168
ZETN-TKN-REASON Token Code Subsystem-Specific Tokens ZETN-TKN-REASON Token Code This token identifies the reason the session was terminated. Token Code ZETN-TKN-REASON Token Type ZETN-TYP-REASON Token Definition ZETN-DDL-REASON-ENM. ZETN-DDL-REASON-ENM lists the reasons a session was terminated. Definition ZETN-DDL-REASON-ENM.
PAGE 169
ZETN-TKN-RETCODE Token Code Subsystem-Specific Tokens ZETN-TKN-RETCODE Token Code This token identifies errors that are returned for a SPI command. Token Code ZETN-TKN-RETCODE Token Type ZETN-TYP-RETCODE Token Definition ZETN-DDL-RETCODE-ENM. ZETN-DDL-ERROR-ENM lists the errors that can be returned to a SPI command. Definition ZETN-DDL-RETCODE-ENM.
PAGE 170
ZETN-TKN-SESSION-STATS Token Code Subsystem-Specific Tokens ZETN-TKN-SESSION-STATS Token Code This token returns statistical information about a session, including the elapsed time and number of messages and bytes transferred. Token Code ZETN-TKN-SESSION-STATS Token Type ZETN-TYP-SESSION-STATS Token Definition Definition ZETN-DDL-SESSION-STATS. 02 ELAPSED.
PAGE 171
ZETN-TKN-SOCKADDR-IN Token Code Subsystem-Specific Tokens ZETN-TKN-SOCKADDR-IN Token Code This token contains an IP address and port number of an IP connection. Token Code ZETN-TKN-SOCKADDR-IN Token Type ZETN-TYP-SOCKADDR-IN Token Definition Definition ZETN-DDL-SOCKADDR-IN. 02 SIN-FAMILY 02 SIN-PORT 02 SIN-ADDR End Type ZSPI-BINARY 16. Type ZETN-DDL-PORT. Type ZETN-DDL-IN-ADDR. ZETN-TKN-SOCKET-ERROR Token Code This token identifies an error returned by a socket operation.
PAGE 172
ZETN-TKN-SOCKET-ERROR Token Code Subsystem-Specific Tokens ZETN-DDL-SOCKET-ERR-ENM lists the errors that can be returned by a socket operation. Definition ZETN-DDL-SOCKET-ERR-ENM.
PAGE 173
ZETN-TKN-SOURCE-FILE Token Code Subsystem-Specific Tokens ZETN-TKN-SOURCE-FILE Token Code This token contains the name of the NonStop OS source file where the condition occurred. Token Code ZETN-TKN-SOURCE-FILE Token Type ZSPI-TYP-STRING ZETN-TKN-SPI-ERROR Token Code This token contains the error returned by the SPI procedure. Token Code ZETN-TKN-SPI-ERROR Token Type ZETN-TYP-SPI-ERROR ZETN-TKN-SUBDEV Token Code This token contains the name of a TN3270e server window.
PAGE 174
ZETN-TKN-TRACE-ERROR Token Code Subsystem-Specific Tokens ZETN-TKN-TRACE-ERROR Token Code This token returns error information if a START TRACE command was unsuccessful. Token Code ZETN-TKN-TRACE-ERROR Token Type ZETN-TYP-TRACE-ERROR Token Definition Definition ZETN-DDL-TRACE-ERROR. 02 ERROR Type ZETN-DDL-TRACE-ERROR-ENM. 02 INFO Type ZSPI-BINARY 16. End ZETN-DDL-TRACE-ERROR-ENM enumerates errors returned by START TRACE. Definition ZETN-DDL-TRACE-ERROR-ENM.
PAGE 175
Index Numbers D 3270 commands 3-5 Data inbound/outbound message format 5-1 Defining the IP host name 2-3 DELETE WINDOW command 4-12 A ABORT WINDOW command 4-4 ADD WINDOW command 4-5 ALTER PROCESS command 4-8 ALTER WINDOW command 4-9 AM3270 interface support 1-2 Application considerations 1-8 ASCII 3270 commands 3-5 Audience -ix B BREAK message 6-13 C Client messages B-1 Commands 3270 3-5 ETN32COM descriptions 4-4 local and remote 3-5 SPI descriptions 7-2 summary 7-1 COMMENT command 4-11 Completion cod
PAGE 176
F Index Extended highlighting in SNAX/XF mode 5-5 WRITE[x] procedure 6-14 L F LISTOPENS [WINDOW] command 4-17 FC command 4-14, 6-2 Features supported 1-1 TN3270 protocol, unsupported 1-5 unsupported 1-3 Files names and locations 2-2 Fix (FC) command 6-2 H HELP command 4-15 Highlighting in SNAX/XF mode 5-5 Host name resolution 3-6 M Memory pool, usage 4-19 Message BREAK 6-13 Message format inbound/outbound data 5-1 Messages client B-1 error D-1 ETN32COM, error C-1 N I Name resolution 3-6 Inbound
PAGE 177
T Index SETPARAM function 3 procedure 6-11 SNAX/XF mode operations CONTROL 6-5 other 5-5 SETMODE function 144 procedure 5-3, 6-9 SETMODE function procedures 6-7 SPI commands descriptions 7-2 summary 7-1 Starting ETN32COM 4-1 Guardian Enhanced TN3270 Server 3-2 Startup environment, initializing 3-1 STATUS PROCESS command 4-19 STATUS SESSION command 4-21 STOP PROCESS command 4-25 Supported features 1-1 Supported terminal models SNAX/XF mode A-1 System requirements 2-1 T TACL run options 3-2 TCP/IP host nam
PAGE 178
Z Index ZETN-TKN-ABORT-TEXT token code E-7 ZETN-TKN-ASSERTION-CONDITION token code E-7 ZETN-TKN-BANNER event 8-11 ZETN-TKN-BANNER token code E-7 ZETN-TKN-DEVICE-NAME token code E-8 ZETN-TKN-DEVICE-TYPE token code E-8 ZETN-TKN-EDIT-SEQNUM token code E-9 ZETN-TKN-FILENAME token code E-9 ZETN-TKN-FILE-ERROR token code E-9 ZETN-TKN-FSM token code E-10 ZETN-TKN-FSMID token code E-10 ZETN-TKN-FSMOBJ token code E-11 ZETN-TKN-HOST-NAME token code E-12 ZETN-TKN-LISTOPEN-RSP token code E-12 ZETN-TKN-NLS-ALLORONE-CH