HP NonStop Pathway/iTS System Management Manual Abstract This manual describes the management interface to the HP NonStop™ Pathway/iTS product; it is intended for system managers and operators. It provides instructions and guidelines for configuring and controlling the Pathway/iTS objects (those related to terminal control processes (TCPs), terminals, and intelligent devices) and for monitoring the status and performance of those objects.
Document History Part Number Product Version Published 426748-001 Pathway/iTS 1.0 October 2000 426748-002 Pathway/iTS 1.0 February 2006 426748-003 Pathway/iTS 1.1 May 2007 426748-004 Pathway/iTS 1.1 May 2008 426748-005 Pathway/iTS 1.
Legal Notices © Copyright 2009 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.
HP NonStop Pathway/iTS System Management Manual Index Examples Figures Tables Legal Notices What’s New in This Manual xi Manual Information xi New and Changed Information About This Manual xv Who Should Read This Manual Related Documentation xv Notation Conventions xvi xi xv 1.
1. Introduction to Pathway/iTS System Management (continued) Contents 1. Introduction to Pathway/iTS System Management (continued) SNA Devices 1-17 Unsupported or Special-Function I/O Devices The LINKMON Process 1-18 Requester-Server Communication 1-18 System Management Tasks 1-19 1-17 2.
4. Maintaining Pathway/iTS Objects Contents 4.
5. Tuning Your System Using Statistics (continued) Contents 5. Tuning Your System Using Statistics (continued) POOL INFO 5-8 AREA INFO 5-12 QUEUE INFO 5-14 REQ CNT 5-16 % WAIT 5-16 Terminal Statistics 5-17 I/O Info 5-18 Area Info 5-23 Response Time Info 5-24 Frequency Distribution 5-25 6.
. Terminal Control Process (TCP) Commands Contents 9. Terminal Control Process (TCP) Commands ADD TCP Command 9-2 ALTER TCP Command 9-3 CONTROL TCP Command 9-4 DELETE TCP Command 9-9 INFO TCP Command 9-10 PRIMARY TCP Command 9-13 REFRESH-CODE TCP Command 9-14 RESET TCP Command 9-16 SET TCP Command 9-18 SHOW TCP Command 9-32 START TCP Command 9-33 STATS TCP Command 9-35 STATUS TCP Command 9-37 STOP TCP Command 9-42 SWITCH TCP Command 9-44 Wild Card Support for TCP Commands 9-45 Example 9-45 10.
. TERM Commands (continued) Contents 10. TERM Commands (continued) Procedure for Synchronous Upgrade 10-45 11. PROGRAM Commands ADD PROGRAM Command 11-2 ALTER PROGRAM Command 11-3 DELETE PROGRAM Command 11-5 INFO PROGRAM Command 11-6 RESET PROGRAM Command 11-8 RUN PROGRAM Command 11-10 SET PROGRAM Command 11-15 SHOW PROGRAM Command 11-24 Wild Card Support for PROGRAM Commands Example 11-25 11-25 12. Tell Message Commands DELETE TELL Command 12-2 INFO TELL Command 12-3 TELL TERM Command 12-4 13.
E. Setting TMF Parameters Contents E. Setting TMF Parameters SET TERM and SET PROGRAM Commands and TMF E-1 Effect of TMF Parameters in PATHCOM on SCREEN COBOL SEND Operations E-1 Timeouts on SEND Operations to Servers E-4 TCP Checkpointing Strategy E-4 Precautions for Using TMF Parameters E-5 F. Setting the DISPLAY-PAGES Parameter Screen Caching F-1 Terminal Memory Organization F-1 Determining the DISPLAY-PAGES Value F-2 Estimating Field-Attribute Entries F-3 Assessing Terminal Capacity F-3 G.
Examples (continued) Contents Examples (continued) Example 5-7. Example 5-8. Example 5-9. Example 6-1. Example 6-2. Example 6-3. Example 6-4. Example 6-5. Example 6-6. Example 6-7. Example 10-1. Example G-1. Example G-2.
Tables (continued) Contents Tables (continued) Table 5-1. Table 5-2. Table 5-3. Table 5-4. Table 5-5. Table 5-6. Table 5-7. Table 7-1. Table 7-2. Table C-1. Table C-2. Table D-1. Table F-1. Table F-2. Table F-3. Table F-4.
Contents HP NonStop Pathway/iTS System Management Manual—426748-005 x
What’s New in This Manual Manual Information HP NonStop Pathway/iTS System Management Manual Abstract This manual describes the management interface to the HP NonStop™ Pathway/iTS product; it is intended for system managers and operators. It provides instructions and guidelines for configuring and controlling the Pathway/iTS objects (those related to terminal control processes (TCPs), terminals, and intelligent devices) and for monitoring the status and performance of those objects.
What’s New in This Manual • • • • • ° Changes in the H06.14/J06.03 Manual Table 7-2 Commands and Objects on page 7-4 Added CONTROL TERM Commands on page 10-7. Updated considerations of: ° ° ABORT TERM command on page 10-3 STOP TERM command on page 10-41 Updated the format of the display returned by the STATUS TERM command on page 10-37. Updated information about display format of the STATUS TERM command on page 10-38. Added Synchronous Upgrade for SCOBOL Applications on page 10-44.
What’s New in This Manual Changes in the G06.28 Manual SERVERCLASS_DIALOG_* APIs for executing these dialog verbs that enable clients to send more than 32000 bytes message to the same Pathway server process. The SCUP and Web Client components of Pathway/iTS 1.1 product are changed to support the new functionalities. For compatibility reasons, Pathway/iTS 1.1 package includes the legacy TCP component, that is, PATHTCP3 product.
What’s New in This Manual • • Product Changes ° Router Processes on page 1-13 provides a general description of the router process. ° Starting Router Processes on page 3-1 describes how to start router processes. ° Stopping Router Processes on page 3-7 describes how to stop router processes. New TCP configuration attribute, SENDMSGTIMEOUT, to support filtering of 3161 timeout error messages when the ON ERROR clause is used with a SEND MESSAGE statement.
About This Manual This manual is both a task-oriented manual and a reference manual. It provides instructions and guidelines for configuring and controlling the HP NonStop Pathway/iTS objects in a PATHMON environment and for monitoring the status and performance of those objects. The Pathway/iTS objects are those that operate under the run-time portions of Pathway/iTS (the terminal control process (TCP) and SCREEN COBOL run-time environment).
Notation Conventions About This Manual Pathway/iTS Management Programming Manual Describes the management programming interface for Pathway/iTS objects in the PATHMON environment. Pathway Products Glossary Defines technical terms used in this manual and in other manuals for the Pathway products: Pathway/iTS, TS/MP, and Pathway/XM.
General Syntax Notation About This Manual each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines. For example: LIGHTS [ ON ] [ OFF ] [ SMOOTH [ num ] ] K [ X | D ] address-1 { } Braces. A group of items enclosed in braces is a list from which you are required to choose one item. The items in the list may be arranged either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines.
Notation for Messages About This Manual Line Spacing. If the syntax of a command is too long to fit on a single line, each continuation line is indented three spaces and is separated from the preceding line by a blank line. This spacing distinguishes items in a continuation line from items in a vertical list of selections. For example: ALTER [ / OUT file-spec / ] CONTROLLER [ , attribute-spec ]...
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 P=%p-register E=%e-register Change Bar Notation Change bars are used to indicate substantive differences between this manual and its preceding version.
About This Manual Change Bar Notation HP NonStop Pathway/iTS System Management Manual—426748-005 xx
1 Introduction to Pathway/iTS System Management This manual provides the information you need to define and control objects under the HP NonStop Pathway/iTS product to support SCREEN COBOL requesters and web clients in a Pathway environment by using the PATHCOM interface. It also provides syntax and complete descriptions of all PATHCOM commands for Pathway/iTS objects, in addition to cause, effect, and recovery information for error messages reported by Pathway/iTS terminal control processes (TCPs).
Which Sections Do You Need? Introduction to Pathway/iTS System Management Which Sections Do You Need? This manual is organized into logical groups of information for easy reference. Table 1-1 is a descriptive map showing which sections are relevant to particular operating environments and tasks. Table 1-1.
Introduction to Pathway/iTS System Management Which Sections Do You Need? Table 1-1.
Pathway Environment Overview Introduction to Pathway/iTS System Management Table 1-1.
Introduction to Pathway/iTS System Management • • • • Objects and Processes Provided by Pathway/iTS PATHMON—the process that manages TCP, TERM, PROGRAM, and SERVER objects. The PATHMON process and the objects controlled by it make up the PATHMON environment. Each PATHMON environment includes only one PATHMON process. PATHCOM—the interactive interface to the PATHMON process.
Introduction to Pathway/iTS System Management Pathway Environment Configurations available. The Pathway/XM product allows you to configure router processes as part of a Pathway/XM environment. Pathway Environment Configurations Depending on your configuration, a Pathway environment might also include other software, such as TMF and the run-time portion of the HP NonStop Remote Server Call/MP (RSC/MP) product.
Pathway Environment Configurations Introduction to Pathway/iTS System Management Figure 1-1.
Introduction to Pathway/iTS System Management Distributing a Pathway Environment Distributing a Pathway Environment Depending on the requirements of your application, you might distribute a Pathway environment over several CPUs in a single HP NonStop system or among several NonStop systems. A PATHMON environment is a set of Pathway environment objects controlled through a single PATHMON process.
Distributing a Pathway Environment Introduction to Pathway/iTS System Management Figure 1-2. PATHMON-Controlled Objects Distributed Over Two CPUs Screen Program Library Users' Terminals and Workstations CPU 0 Users' Terminals and Workstations CPU 1 TERMs TCP TCP TERMs PATHMON Server Class A Server Server Processes Processes Server Class B Server Class A Server Processes Server Processes Server Class B Server Processes PATHCOM Database Command Terminal VST009.
TS/MP Objects and Processes Introduction to Pathway/iTS System Management Figure 1-3. PATHMON-Controlled Objects Distributed Over Two Nodes \NODEA TERMs Screen Program Library TCP Server Class Users' Terminals and Workstations $PMA Server Processes Database PATHCOM Command Terminal \NODEB Server Class $PMB Server Processes Database VST010.vsd TS/MP Objects and Processes The following elements of a Pathway environment are provided by TS/MP.
Introduction to Pathway/iTS System Management PATHCOM Processes The PATHMON process enforces the limits you set for the environment and monitors the operation of the objects under its control by: • • • • • • Keeping a record of the object definitions in the PATHMON configuration file Starting TCPs, TERM objects, PROGRAM objects, and SERVER processes Facilitating access between TCPs or LINKMON processes and server processes to support requester/server communication Reporting status information and system
Introduction to Pathway/iTS System Management Pathway/iTS Objects and Processes Pathway/iTS Objects and Processes The following elements of a Pathway environment are provided by the Pathway/iTS product. Information about defining and managing these items is given in this manual. TCP Objects A terminal control process (TCP) interprets and executes screen program instructions for each input-output (I/O) device or process the TCP is configured to handle.
Introduction to Pathway/iTS System Management Router Processes deleted) by the PATHMON process in response to a RUN PROGRAM command, using a template you configure as a PROGRAM object. (A PROGRAM object is simply a mechanism for creating temporary TERM objects as they are needed.) Router Processes A router process listens and distributes connection requests from web clients and from intelligent devices that use the raw sockets protocol.
Browser-Based Web Clients Introduction to Pathway/iTS System Management Figure 1-4. Transaction Sources NonStop System RSC LINKMON Personal Computer or Workstation Pathsend Requesters Point-of-Sale Terminal GDSX PATHMON Environment Command Terminal Server Class PATHCOM PATHMON Servers Automated Teller Machine IDS TCP GDSX Any I/O Device Application Terminal Router Database Workstation with Browser VST007.
Introduction to Pathway/iTS System Management Personal Computers and Workstations Personal Computers and Workstations Personal computers (PCs) and workstations can access a PATHMON environment using the RSC/MP product. RSC/MP enables client-server computing by supporting a variety of hardware and software configurations and communications protocols for personal computers (PCs) and workstations.
External TCPs Introduction to Pathway/iTS System Management The term “external TCP” is relative to your point of view: a TCP that runs in another PATHMON environment is external to your environment, but it is local to that other environment. In the other environment, that TCP is exactly like any other local TCP. Figure 1-5.
Introduction to Pathway/iTS System Management Intelligent Devices Intelligent Devices Intelligent devices—such as automated teller machines (ATMs), workstations, barcode readers, and machines running the Unix operating system—can access Pathway server classes through SCREEN COBOL requester programs and the TCP. This access route is possible when you use the intelligent device support (IDS) facility, which is part of the TCP.
Introduction to Pathway/iTS System Management • The LINKMON Process A file or any other device has to be accessed before sending data to the SCREEN COBOL program, for example, when data requires encryption or decryption. Using the GDSX product, you can implement message switching, develop and modify data communications protocols, and perform data-stream conversions, all of which facilitate access to Pathway server classes.
System Management Tasks Introduction to Pathway/iTS System Management Figure 1-6. Requester Access to Server Classes NonStop System PATHMON-Controlled Objects Server Class A Application Terminals TCP1 Server TCP2 Application Terminals $PMA Application Workstations Database Server Class B Server Database Router VST006.
System Management Tasks Introduction to Pathway/iTS System Management Figure 1-7.
Introduction to Pathway/iTS System Management System Management Tasks The following briefly describes the tasks shown in Figure 1-7 on page 1-20: 1. Start the Pathway environment. This task consists of starting the PATHMON and PATHCOM processes. The PATHCOM process provides the interactive command interface to the PATHMON process. 2. Configure and start the PATHMON environment. • • • Configure the PATHMON process. You can specify a backup processor and request error dumping.
Introduction to Pathway/iTS System Management • System Management Tasks Reconfigure objects to correct problems and improve performance. 6. Stop your PATHMON environment. Use the SHUTDOWN2 command to stop your system in an orderly way so you can restart easily later. (Although the SHUTDOWN command is supported for backward compatibility, the SHUTDOWN2 command is recommended.) The SHUTDOWN2 command also provides options for faster shutdown in emergencies.
2 Configuring Pathway/iTS Objects The tools to configure and manage a PATHMON environment, including the PATHMON process and the PATHCOM interface, are provided by TS/MP. Comprehensive instructions for configuring and managing a PATHMON environment, in addition to the SERVER objects in that environment, are given in the TS/MP System Management Manual.
Configuration Overview Configuring Pathway/iTS Objects Figure 2-1. PATHMON Environment With a Single Application PATHCOM Inventory Control Application Server Class PATHMON Server Processes TCP Server Class Inventory Control Database Command Terminal Server Processes TERMs TERMs Screen Program Library Users' Terminals and Workstations VST021.
Configuration Overview Configuring Pathway/iTS Objects Figure 2-2.
Configuring Pathway/iTS Objects Configuring Limits for Pathway/iTS Objects How you configure a PATHMON environment depends on various management objectives: the size of your application or applications, the number of users, responsetime requirements, whether the application is distributed over a network, and so on.
Configuring Pathway/iTS Objects Specifying Node Independence choose your parameters very carefully. Once you start your PATHMON environment, you cannot alter these limits without shutting it down for complete reconfiguration. It is recommended that you always allow some space for growth. For example, if you are not certain whether you might need an extra TCP, leave room for one or two. Providing for a few more objects than you initially need can save you much unnecessary work later.
Configuring Pathway/iTS Objects Configuring TCP, TERM, and PROGRAM Objects Configuring TCP, TERM, and PROGRAM Objects After specifying global limits and issuing the START command (as described in the TS/MP System Management Manual), you configure TCPs and the TERM, PROGRAM and SERVER objects that run under the PATHMON process to support your application. Note that only the TCPs and the TERM and PROGRAM objects are configured as part of the Pathway/iTS product.
Configuring Pathway/iTS Objects • Defining Attributes Reporting operating errors and status information to the PATHMON process For Pathway/iTS web clients, the gateway program interpreted and executed by the TCP validates user access and performs functions such as beginning and ending transactions, user conversion routines, unsolicited message processing, and send operations to Pathway server processes.
Configuring Pathway/iTS Objects • Defining Attributes PRI specifies the priority at which TCPs run. You should coordinate with the system manager for your PATHMON environment when setting this attribute, to ensure that TCP priorities are compatible with priorities set for server classes. In general, priorities should facilitate the completion of work over the arrival of work. Usually, this means that server classes should have a higher priority than TCP objects.
Configuring Pathway/iTS Objects Distributing the Transaction Load Across TCPs = SET TCP MAXREPLY 32000 = SET TCP MAXTERMDATA 200000 = ADD TCP TCP-WEB Distributing the Transaction Load Across TCPs In general, you want to spread the workload across all available resources. In this case, the load is the transaction load generated by web clients, terminals, or intelligent devices.
Configuring Pathway/iTS Objects Configuring TCPs for a Customized TCP Object Library Configuring TCPs for a Customized TCP Object Library You are allowed nine user conversion procedures for data passed between a SCREEN COBOL program and a terminal screen or intelligent device. These procedures are stored in the TCP user library object file, $SYSTEM.SYSTEM.PATHTCPL. For web clients converted from SCREEN COBOL programs, these user conversion procedures are run by the Pathway/iTS gateway process.
Configuring Pathway/iTS Objects Configuring TERM Objects For Pathway/iTS web clients and sockets IDS requesters, you must use configured TERM objects. However, for other intelligent devices and for terminals, temporary TERM objects can be easier to use than configured TERM objects. Because more default attributes are supplied for a PROGRAM object than for a TERM object, it is easier to use a PROGRAM object.
Configuring Pathway/iTS Objects Configuring PROGRAM Objects clients, this must be GATEWAY, the name of the initial screen program in the gateway requester. This is the name specified in the PROGRAM-ID sentence of the Identification Division in a SCREEN COBOL program. • TCP specifies the name of the TCP that controls the screen program and oversees communication between the screen program and the input-output device or process.
Configuring Pathway/iTS Objects Configuring PROGRAM Objects screen programs temporarily on one or more devices. When the task is completed, the TERM object is automatically deleted. When a user issues a RUN PROGRAM command, the associated PROGRAM object implicitly creates a TERM object for that individual device or process. This TERM object manages that device or process, and enables the user to interact with the Pathway application associated with the screen program.
Configuring Pathway/iTS Objects Communication Between PATHMON Environments Configuring a Template for Several Device Types A PROGRAM object can serve as a template for several device types. The template can optionally associate several device-related attributes with each device type.
Configuring Pathway/iTS Objects Communication Between PATHMON Environments For communication between PATHMON environments, the TCP requesting a server link must pass all process security checks. If the TCP and server class are on different nodes, the security requirements demand the following: • • The person who starts the local PATHMON process must possess a remote password for the external PATHMON process’s node.
Configuring Pathway/iTS Objects Communication Between PATHMON Environments HP NonStop Pathway/iTS System Management Manual—426748-005 2- 16
3 Starting and Stopping Pathway/iTS Objects This section describes how to start and stop HP NonStop Pathway/iTS objects, including the router process and the PATHMON-controlled objects—TCPs, TERM object, and PROGRAM objects. Starting Router Processes Pathway/iTS router processes are not part of the PATHMON environment; you must start them in the Guardian operating environment.
Starting and Stopping Pathway/iTS Objects Starting PATHMON-Controlled Objects For example: TACL > RUN ROUTER /NAME $ROUT1, CPU 5, NOWAIT/ 8857 HTTP $ZTC1 4 If the specified TCP/IP process does not exist, or if the specified TCP/IP port number is a reserved port or is being used by another process, the router process reports an error. You can ensure connection availability and reliability by running the both the router process and the TCP as process pairs.
Starting PATHMON-Controlled Objects Starting and Stopping Pathway/iTS Objects Figure 3-1. Starting a PATHMON-Controlled Object = START TCP TCP- X $PMX Backup CPU 1 PATHCOM PATHMON TCP-X TCP-X CPUS 3:2 PROGRAM \QATST.$A.W.PATHCP2 TCLPROG \QATST.$DATA.SAMPLE.POBJ SERVERCLASSES 5 SERVERPROCESSES 25 TERMS 5 ••• VST020.vsd You must start some objects before starting others. For example, you must start a TCP before starting the TERM objects that use the TCP.
Starting and Stopping Pathway/iTS Objects Starting TCPs Because the asterisk option slows processing, a more efficient way to start all objects is to use an command file in which all the objects are named. Use the asterisk option if no command file is available. If an object is already running when you issue the START command, the PATHMON process displays an error message and makes no attempt to start the object.
Starting and Stopping Pathway/iTS Objects • • • Starting Multiple TCPs and TERM Objects in Parallel Checks the specified library file for the program indicated by the INITIAL attribute. Opens communication with the terminal, device, or process specified by the FILE attribute. Executes the screen program code. If you enter a START TERM command before the TCP that controls the TERM is running, the PATHMON process displays an error message.
Starting and Stopping Pathway/iTS Objects Starting PROGRAM Objects For example, the following command, entered at an application terminal, runs the application named PROG-1: = RUN PROGRAM PROG-1 In response, the PATHMON process starts the objects needed by the application as follows: • • Starts the required TCP (specified by the TCP attribute in the PROGRAM definition) if the TCP is not already running.
Starting and Stopping Pathway/iTS Objects Stopping Router Processes After you enter the RUN PROGRAM command, the PATHCOM prompt immediately appears on $TERMA; you can now enter other PATHCOM commands while SALES runs. If you do not specify the NOWAIT option, the PROGRAM runs at the same terminal from which you specified the RUN PROGRAM command. The PATHCOM prompt does not appear until you exit the PROGRAM: = RUN PROGRAM SALES . (SALES application is running) .
Starting and Stopping Pathway/iTS Objects Stopping TCPs Stopping TCPs To stop a TCP, use the STOP TCP command. You can only stop a TCP after you have stopped all TERM objects controlled by that TCP. The following command stops the TCP named TCP-EXT1: = STOP TCP TCP-EXT1 The PATHMON process stops TCPs in the order you specify them in your STOP commands.
Starting and Stopping Pathway/iTS Objects Stopping Multiple TCPs and TERM Objects in Parallel You can also stop a TERM object by using the ABORT TERM command, as shown in this example: = ABORT TERM *, TCP TCP-1 If a TERM object is in TMF transaction mode, the transaction is backed out before the TERM object is aborted. Note. PATHCOM is provided as part of TS/MP. For more information on the PATHCOM process and commands, see the TS/MP System Management Manual.
Pathway/iTS Objects and the SHUTDOWN2 Command Starting and Stopping Pathway/iTS Objects Pathway/iTS Objects and the SHUTDOWN2 Command You can shut down the whole PATHMON environment by stopping all PATHMON-controlled objects collectively with the SHUTDOWN2 command. Note. This subsection describes the effect of the SHUTDOWN2 command and options on Pathway/iTS objects controlled by the PATHMON process.
Specifying the ORDERLY Option Starting and Stopping Pathway/iTS Objects Table 3-1. Effects of SHUTDOWN2 Options Outstanding work ORDERLY ABORT IMMEDIATE All outstanding work For TCPs and server classes, outstanding work (I/O activity) is completed. For transactions involving an aborted TERM, unknown.4 Unknown Not allowed Not allowed (I/O activity) is completed New work Not allowed 1. Because the TCP was stopped by a Guardian STOP procedure call, the terminals were essentially aborted.
Starting and Stopping Pathway/iTS Objects Specifying the ABORT Option The ORDERLY option requires the most time to complete the shutdown operation, because all transactions in progress are allowed to complete before objects (TCP, TERM, and server objects) involved in the transaction are stopped. For example, a TERM waiting for I/O to a server class to complete cannot be stopped until the I/O completes. (Note that the TERM object must be in a qualified state in order to be stopped.
Starting and Stopping Pathway/iTS Objects • Specifying the IMMEDIATE Option The status of any outstanding transactions is unknown.
Starting and Stopping Pathway/iTS Objects Specifying the IMMEDIATE Option HP NonStop Pathway/iTS System Management Manual—426748-005 3- 14
4 Maintaining Pathway/iTS Objects System Maintenance Tasks This section describes operations you need to perform on a regular basis to maintain TCP, TERM, and PROGRAM objects in a PATHMON environment.
Maintaining Pathway/iTS Objects A System Management Scenario This section provides several examples of the INFO, STATUS, and STATS commands, showing various syntax options for these commands and the resulting display information. The following scenario illustrates how to use the information provided by the INFO, STATUS, and STATS commands to detect problems within your environment and determine how to reconfigure the system to rectify these problems.
Maintaining Pathway/iTS Objects • Displaying Configuration Information You can add another TCP object that might or might not be dedicated exclusively to the RUN PROGRAM command. You must keep in mind, however, that when you make a change to your configuration, the change can affect other performance factors.
Maintaining Pathway/iTS Objects Displaying Configuration Information The INFO TCP Command The INFO TCP command displays information about a single TCP, multiple TCPs, or all TCPs controlled by the PATHMON process. The following example displays information about a single TCP named M6530-TCP1: = INFO TCP M6530-TCP1 Example 4-1 shows the TCP information displayed in response to the command. Example 4-1.
Maintaining Pathway/iTS Objects Displaying Configuration Information For a complete description of all the TCP attributes viewable through the INFO TCP command, see the description of the SET TCP command in Section 9, Terminal Control Process (TCP) Commands. The INFO TERM Command The INFO TERM command displays information about a single TERM object, multiple TERM objects, or all TERM objects described in the PATHMON configuration file.
Maintaining Pathway/iTS Objects Displaying Status Information For a complete description of all the TERM attributes viewable through the INFO TERM command, see the description of the SET TERM command in Section 10, TERM Commands. The INFO PROGRAM Command The INFO PROGRAM command displays information about a single PROGRAM object, multiple PROGRAM objects, or all PROGRAM objects described in the PATHMON configuration file.
Displaying Status Information Maintaining Pathway/iTS Objects Various levels of detail can be reported using the STATUS command. For instance, the STATUS TCP command features an option for reporting the status of terminals controlled by the TCP. The STATUS TCP Command The STATUS TCP command displays status for a single TCP, multiple TCPs, or all TCPs defined in a PATHMON environment.
Displaying Status Information Maintaining Pathway/iTS Objects For each TCP, you can also view the status of the terminals the TCP controls by including the DETAIL option in your command. For example, this command displays status information for the TCP M6530-TCP1 and all terminals under its control: = STATUS TCP M6530-TCP1, DETAIL Example 4-6 shows the information displayed in response to the command. Example 4-6.
Displaying Status Information Maintaining Pathway/iTS Objects The display shows the name and state of each TERM object; the name of the TCP that controls the TERM object; and the file name of the TERM object. The ERROR and INFO columns provide information about any system errors associated with a TERM object. For each TERM object, you can also view the status of the program unit currently executing on a TERM object by including the DETAIL option in your command.
Maintaining Pathway/iTS Objects Displaying Statistics Information The following are usage considerations when executing the STATUS TERM command: • • If you issue the STATUS TERM command to a PATHMON process on a remote CPU and a TERM on the remote CPU is inaccessible to your local PATHCOM, the command fails with an error 1024, “TERM, ILLEGAL FILE NAME (000).” If you encounter this error, try the command again using PATHCOM on the remote CPU.
Displaying Statistics Information Maintaining Pathway/iTS Objects . = STATS TCP ... . = CONTROL TCP TCP-A, STATS OFF Once you enter the CONTROL TCP STATS OFF parameter, all statistical counters are reset to 0. The STATS TCP Command The STATS TCP command displays statistics about TCP operations and data space allocation for a single TCP, multiple TCPs, or all TCPs in a PATHMON environment. (This command does not display information about external TCPs that might have links to local servers.
Displaying Statistics Information Maintaining Pathway/iTS Objects Example 4-11. STATS TCP With DETAIL Option TCP M6530-TCP1 POOL INFO: TERMPOOL SERVERPOOL TERMPOOL SERVERPOOL SIZE 10008 20000 MAX REQ 260 1932 REQ CNT 130799 193346 AVG REQ 66 440 MAX ALLOC 568 3876 11 APR 1996, 14:18:02 AVG ALLOC CUR ALLOC 66 32 440 38 . . .
Maintaining Pathway/iTS Objects Reconfiguring Pathway/iTS Objects The STATS TERM Command The STATS TERM command displays statistics, including response time information, about TERM operations for a single TERM object, multiple TERM objects, or all TERM objects in a PATHMON environment. These statistics are gathered by the TCP that controls the TERM or TERM objects.
Maintaining Pathway/iTS Objects Specifying New Limits your transaction throughput and response time requirements and to update or expand the system to provide needed resources. In response to your changing application requirements, you might need to specify new limits or add, alter, or delete objects running under the Pathway/iTS product.
Maintaining Pathway/iTS Objects Changing Backup CPUs and Dump Files Adding Objects You add TCP, TERM, and PROGRAM objects using the SET and ADD commands for that particular object. Once you have configured and added an object, you can start the object using the START command for that object. For complete information about configuring, adding and starting objects, see Section 2, Configuring Pathway/iTS Objects.
Maintaining Pathway/iTS Objects Exchanging Primary and Backup CPUs To change the backup CPU for the TCP, you enter the CONTROL TCP command for the object you wish. For instance, to change the backup CPU to CPU 7 for the TCP named TCP1, enter the following: = CONTROL TCP TCP1, BACKUPCPU 7 To direct the memory dumps for the TCP to files named PMDUMP and TCPDUMP, respectively, enter the following: = CONTROL TCP TCP-1, DUMP ON (FILE TCPDUMP) The PATHMON configuration file is updated to reflect this change.
Managing Exception Conditions Maintaining Pathway/iTS Objects For instructions on specifying a destination for TCP error and status messages, see the TS/MP System Management Manual. Managing Exception Conditions You can change various aspects of a PATHMON environment as it is running. Often you will need to change system parameters because an exception or error condition has occurred for an object, such as a TERM object or TCP.
Using EMS Event Messages Maintaining Pathway/iTS Objects From this information, the operator sees that two TERM objects are not running. The error codes under the ERROR and INFO columns help solve the problem.
Maintaining Pathway/iTS Objects Managing Links For more information about SPI processes and event messages for the TS/MP and Pathway/iTS products, see the TS/MP Management Programming Manual and the Pathway/iTS Management Programming Manual. Managing Links A link is a connection between a link manager, such as a TCP, and a specific server process. The link is used to send a request to, and receive a reply from, a server. Note.
Improving Performance Maintaining Pathway/iTS Objects A TCP will delete a link to a server process when any of this situations occur: Cause Action A “DELETEDELAY” timer expires for a dynamic link. Returns the dynamic link. An OPEN error occurs on a link. Returns the link. An I/O error occurs on a link. (I/O errors include timeouts caused by the SET SERVER TIMEOUT value. Timeouts caused by the SERVERCLASS_SEND_ timeout value are not considered to be link errors.
Maintaining Pathway/iTS Objects Prevent TCLPROG File Checking Prevent TCLPROG File Checking System performance is improved if TCLPROG file checking is not performed. At the TCP level, set the CHECK-DIRECTORY attribute to OFF to prevent the system from checking the TCLPROG file. To prevent the system from checking the TCLPROG file at the TERM and PROGRAM level, you must remove the TCLPROG file.
Maintaining Pathway/iTS Objects TCP-Specific Problems When describing the problem to your service provider, include details of how to reproduce the problem by navigating to particular screens and pressing particular keys. TCP Dump When a TCP detects an inconsistency in its control tables, the TCP dumps automatically if the dump feature is enabled.
Maintaining Pathway/iTS Objects Terminal-Specific Problems PATHMON Configuration and TCP Object Information Make the PATHCTL file available to your service provider. Also, use PATHCOM commands to display information about the TCP at the time of the problem, as follows: >PATHCOM $ =INFO tcp =EXIT where pm is the name of your PATHMON process and tcp is the name of a TCP.
Maintaining Pathway/iTS Objects • • • SCUP-Specific Problems All copy libraries referenced in the source file or files. If applicable, a compiler listing showing the problem. Error messages written to the terminal but not included in the compiler listing. SCUP-Specific Problems If you detect a problem with SCUP, collect the relevant object code (POBJ) files for review. Keeping Development and Production Separate It is recommended that you do not mix your development and production environments.
Maintaining Pathway/iTS Objects Migrating Pathway/iTS Objects to a Different System You can direct these messages to selected users (addressing their terminals by TERM object name), or to all users accessing your application. Devices represented by both configured TERM objects and temporary TERM objects can receive these messages.
Migrating Pathway/iTS Objects to a Different System Maintaining Pathway/iTS Objects Even with a node-independent PATHMON environment, a number of migration considerations arise. The node-independent designation can provide a smooth migration for disk files and process names. However, you might have to change parts of device names manually even if the node portion of the name is independent.
Maintaining Pathway/iTS Objects Migrating Pathway/iTS Objects to a Different System You should also consider whether your SCREEN COBOL requesters—perhaps those run by TCPs on remote systems—use hard-coded node names in requests to server processes that belong to the application you want to migrate. If screen application requests have not been coded for node independence, the applicable code must be changed manually.
Maintaining Pathway/iTS Objects Migrating Pathway/iTS Objects to a Different System HP NonStop Pathway/iTS System Management Manual—426748-005 4- 28
5 Tuning Your System Using Statistics Statistics and System Tuning This section describes the HP NonStop Pathway/iTS terminal control process (TCP) and the statistics that the TCP produces. You can use the statistics generated by transaction processing functions in the PATHMON environment to detect bottlenecks in TCP processing. Based on careful analysis of these statistics, you can reconfigure your PATHMON environment to eliminate some performance degradations.
Tuning Your System Using Statistics Link Management Link Management Links enable communication between requester programs and server programs. The TCP coordinates the sharing and dissolving of links between SCREEN COBOL requester programs and server programs. The following list describes the properties of links: • • • • A link results in a single open of a server with a nowait depth of 1. This open is available for use by multiple requesters on a serial basis.
Tuning Your System Using Statistics Link Management Requesting a New Link When a terminal task requests a new link, the task joins both the link queue and the server-class wait queue inside the TCP: 1. The TCP specifies a timeout value for the LINK queue. 2. After the timeout expires, the TCP issues the link request to the PATHMON process. 3. The task remains on the LINK queue until: • • The PATHMON process establishes the link. The PATHMON process denies the request for a new link.
Tuning Your System Using Statistics Memory Management and Allocation If no terminal tasks are waiting, the TCP sets a timeout value for the dynamic link—using the value specified with the SET SERVER DELETEDELAY command—and places the link on the TCP DELINK queue. The DELETEDELAY parameter specifies the maximum amount of time a link between a link manager and a dynamic server can remain idle before the link manager automatically closes the server and informs the PATHMON process.
Tuning Your System Using Statistics Memory Management and Allocation A wait queue is associated with each pool. If enough pool space is available, the request is granted and the requesting task proceeds. Otherwise, the task joins the wait queue until enough pool space is available. Data Area The TCP allocates terminal data area in an extended segment of memory.
Checkpointing Tuning Your System Using Statistics Checkpointing Checkpointing refers to the communication between the primary and backup processes of a TCP process pair. During processing, the primary TCP keeps the backup TCP informed of what it is doing—for example, sending a request, receiving a reply, and so on—with checkpoint messages, as shown in Figure 5-1. Consequently, if the primary process fails, the backup process has enough information to take over and continue. Figure 5-1.
TCP Statistics Tuning Your System Using Statistics TCP Statistics TCP statistics provide information about the following: • • • Storage pools (POOL INFO) Memory segments (AREA INFO) Queues associated with the storage pools, memory management, link management, and checkpointing (QUEUE INFO) Example 5-1 shows a sample set of TCP statistics. These statistics are described in the subsections that follow. Example 5-1.
POOL INFO Tuning Your System Using Statistics POOL INFO The POOL INFO section in the statistics display provides information about the two storage pools in memory: TERMPOOL and SERVERPOOL. Example 5-2 shows only the POOL INFO section of the sample TCP statistics. Example 5-2. Sample TCP Statistics for POOL INFO TCP TCPX2 INTERVAL 5 SECS COUNT 2/5 POOL INFO: SIZE REQ CNT TERMPOOL 40962 132 SERVERPOOL 55278 0 MAX REQ AVG REQ TERMPOOL 1596 280 SERVERPOOL 0 0 . . .
Tuning Your System Using Statistics POOL INFO SIZE SIZE indicates the maximum number of bytes available in each pool, as determined by the TCP’s configuration. If this number is consistently low (the value for MAX ALLOC is near the value for SIZE), terminal tasks are using most of the available pool space; in this case, you might want to increase the size of the pools.
Tuning Your System Using Statistics • • • POOL INFO In general, TERMBUF should be large enough to hold the largest display sent to a terminal. Although this might oversize TERMPOOL, the excess space is held only for a short time, so system performance is not adversely affected. The excess space is not used because, generally, the terminal is in a read state rather than a write state.
Tuning Your System Using Statistics • POOL INFO MAX-TPS indicates the maximum number of transactions per second (the peak transaction rate). You can determine MAX-TPS in several ways. For example: • • You can code your application to record this information. You can estimate this information by counting the number of SEND statements to a server class (where the server class has a fixed relationship to a transaction).
AREA INFO Tuning Your System Using Statistics AREA INFO The AREA INFO section in the statistics display provides information about the data and code segments in memory. This information is primarily useful to HP internal development. • • DATA is the area of the extended data segment that the TCP allocates for context data for all of its terminals. CODE is the area of the extended data segment that the TCP allocates for SCREEN COBOL object code.
AREA INFO Tuning Your System Using Statistics Table 5-2. TCP Statistics for AREA INFO Statistic For CODE, Indicates For DATA, Indicates SIZE Total number of bytes allocated to the code area for all SCREEN COBOL object code Total size of all slots for all terminal tasks REQ CNT Number of requests for defined code segments N.A.
Tuning Your System Using Statistics QUEUE INFO This costs extra disk space for the swap file, but prevents the TCP from performing unnecessary code fetching. (The SCREEN COBOL code area is not shared between multiple TCPs within a CPU. Consequently, large code areas might create the potential for increasing the memory pressure within the operating system. However, it is more efficient for the system to perform code fetching than the TCP.
QUEUE INFO Tuning Your System Using Statistics Example 5-4. Sample TCP Statistics for QUEUE INFO TCP TCPX2 INTERVAL 5 SECS 02 MAY 1996, 14:03:02 COUNT 2/5 . . . QUEUE INFO: TERMPOOL SERVERPOOL MEMMAN LINK DELINK CHECKPOINT REQ CNT 816 3095 1176 1 1 320 % WAIT 0.0 0.0 1.3 0.0 0.0 0.0 MAX WAITS 0 0 1 0 0 0 AVG WAITS 0.00 0.00 0.01 0.00 0.00 0.00 . . . The Table 5-3 lists the statistics for the queues and what they indicate. Table 5-3.
Tuning Your System Using Statistics REQ CNT REQ CNT The following subsections describe the entries for REQ CNT. (Note that requests waiting on the $RECEIVE queue of a server process are not collected for statistical purposes.) TERMPOOL and SERVERPOOL For TERMPOOL and SERVERPOOL, REQ CNT indicates the number of requests for buffer allocation that were queued, and implies the number of SEND statements. MEMMAN For MEMMAN, REQ CNT indicates the number of requests for SCREEN COBOL code that were queued.
Tuning Your System Using Statistics Terminal Statistics TERMPOOL and SERVERPOOL For TERMPOOL and SERVERPOOL, % WAIT indicates the percentage of requests for buffer space that waited in the queue. A nonzero value indicates that some task had to wait until sufficient space was available. For information about sizing TERMPOOL and TERMBUF, see POOL INFO on page 5-8 in this section.
I/O Info Tuning Your System Using Statistics • Frequency distribution (optional) Example 5-5 shows a sample set of terminal statistics. Because frequency distribution is an optional item, this figure does not include distribution statistics. For an example of terminal statistics showing frequency distribution, see Frequency Distribution on page 5-25. Example 5-5.
I/O Info Tuning Your System Using Statistics Example 5-6. Sample Terminal Statistics for I/O INFO TERM TERM1 I/O INFO: DISPLAY ACCEPT SEND REPLY CHECKPOINT REQ CNT 38 19 19 ** ** MAX TSIZE 161 20 2 2 910 . . . 18 FEB 1996, 09:11:51 AVG TSIZE I/O CNT 73 19 20 19 2 19 2 ** 469 ** The Table 5-4 lists the statistics for the I/O operations and what they indicate. Table 5-4.
I/O Info Tuning Your System Using Statistics Table 5-4.
Tuning Your System Using Statistics I/O Info require a physical I/O operation, REQ CNT indicates the number of logical I/O operations—not the number of physical I/O operations. The DISPLAY statements generally cause the TCP to generate data for the terminal and place the data in a TERMPOOL buffer, but do not always require that the TCP write the buffer to the terminal. Consequently, a logical I/O operation does not necessarily generate a physical I/O operation.
Tuning Your System Using Statistics I/O Info AVG TSIZE AVG TSIZE indicates the size of the average data transfer for the DISPLAY, ACCEPT, SEND, and REPLY statements and for checkpoint operations. DISPLAY Statements For DISPLAY, AVG TSIZE indicates the size of the average buffer sent to the terminal. If the number indicated for AVG TSIZE is greater than that specified for TERMBUF, multiple I/O operations are required to display the data.
Area Info Tuning Your System Using Statistics Conversational-Mode Terminals For terminals running in conversational mode, the TCP writes output to the terminal whenever it executes a DISPLAY statement that generates data for a screen line. You cannot specify the size of the terminal buffer for conversational-mode terminals. Area Info The AREA INFO section of the statistics display provides information about the data and code segments used by a terminal task.
Tuning Your System Using Statistics Response Time Info Response Time Info The RESPONSE TIME INFO section of the statistics display provides information about the response time of terminal tasks. Response time for a terminal is the length of time that elapses from the moment a user presses a function key until the next opportunity to press a function key. Example 5-8 shows only the RESPONSE TIME INFO section of the sample terminal statistics. Example 5-8.
Tuning Your System Using Statistics Frequency Distribution Frequency Distribution When you specify the FREQTABLE option of the STATS TERM command, the PATHMON process displays supplemental statistics on response time within a given time interval. The supplemental information is contained in the frequency distribution table, as shown in Example 5-9. A separate frequency distribution table is generated for each terminal. Example 5-9.
Tuning Your System Using Statistics Frequency Distribution Table 5-7.
6 Examples of System Management Tasks Example Task Overview This section presents an example that demonstrates typical system management operations. The example illustrates configuration guidelines and steps, using many of the commands described throughout this manual and the TS/MP System Management Manual. By following the steps in the example, you can create and configure a PATHMON environment that runs a small sample application.
Examples of System Management Tasks Configuring and Starting a Simple PATHMON Environment (Task 1) screen and server programs are intended as brief samples that are easy to use: brevity and simplicity are emphasized more than standard design and coding practices. (The screen program is written for terminals running in block mode. However, this program could easily have been written for terminals operating in conversational mode.
Examples of System Management Tasks Configuring and Starting a Simple PATHMON Environment (Task 1) 6. Using your text editor, create the file named CONFIG1 to serve as the PATHCOM command file, and enter the PATHCOM commands shown in Example 6-2: Example 6-2.
Examples of System Management Tasks Configuring and Starting a Simple PATHMON Environment (Task 1) allows up to five input-output devices to be used at the same time. These commands enable the PATHMON process and the TCP to support up to five application terminals simultaneously. • • The SET SERVER MAXLINKS command allows up to five concurrent links to exist between a server process and a TCP.
Examples of System Management Tasks Restarting the System and Adding Configured TERM Objects (Task 2) In response, the PATHMON process shuts down the PATHMON-controlled objects and then terminates itself. 10. Terminate your interaction with PATHCOM by entering: = EXIT 9> PATHCOM returns control to TACL. 11. You can examine the log file to see a record of the events that took place while your PATHMON environment was running.
Examples of System Management Tasks Restarting the System and Adding Configured TERM Objects (Task 2) a. Determine the file name by which the operating system recognizes each terminal. To do this, enter this command at this terminal: 20> WHO TACL responds by displaying the file name for the terminal, plus other operating environment information. b. Suspend the TACL process by entering this command at this terminal: 21> PAUSE This command frees the terminal for dedication to your PATHMON environment.
Examples of System Management Tasks Communicating With Another PATHMON Environment (Task 3) 6. Enter the START commands for starting the TCP and TERM objects. Remember that you must start the TCP first, for example: = START TCP EXAMPLE-TCP = START TERM *, TCP EXAMPLE-TCP When the START TERM command is executed, the application’s initial screen appears on the terminals. 7.
Examples of System Management Tasks . PROCEDURE DIVISION. . . SEND-DATA. MOVE 0 TO SEND-ERROR-FLAG SEND ENTRY-MSG TO "EXAMPLE-SERVER" UNDER PATHWAY "$AC1" REPLY CODE 0 . . . Communicating With Another PATHMON Environment (Task 3) <--(Added) YIELDS ENTRY-REPLY 3.
Examples of System Management Tasks Communicating With Another PATHMON Environment (Task 3) 5. Using your text editor, create a file named CONFIG2 and enter the PATHCOM commands shown in Example 6-6. Example 6-6.
Examples of System Management Tasks Communicating With Another PATHMON Environment (Task 3) This command specifies that the PATHMON process for the first PATHMON environment can communicate with one external TCP. Returning to the CONFIG2 file, notice that the SET PROGRAM TYPE command specifies the same program name used as the PROGRAM-ID in Step 2. 6.
Summary of Example Examples of System Management Tasks This concludes Task 3 of the example. Summary of Example By running the complete example described in this section, you generate the PATHMON-controlled objects shown in Figure 6-1. Figure 6-1.
Examples of System Management Tasks Summary of Example HP NonStop Pathway/iTS System Management Manual—426748-005 6- 12
7 Overview of PATHCOM This section contains overview information to help you get started using PATHCOM to manage HP NonStop Pathway/iTS objects in your PATHMON environment. See the TS/MP System Management Manual for more detailed information on how PATHCOM works, how to manage your PATHMON environment, and how to configure and manage the TS/MP objects. PATHCOM Interface to PATHMON Environments PATHCOM is a command language interpreter and interactive command interface to the PATHMON process.
Command List Overview of PATHCOM Figure 7-1. PATHCOM Commands and Object States Object Unconfigured Object Configured/Stopped SHOW START ADD ALTER CONTROL Object Running STATUS INFO RESET INFO SWITCH SET STATUS PRIMARY REFRESH-CODE DELETE STOP STATS VST004.vsd Note. The CONTROL TERM commands must be issued when TERM is in the STOPPED state for COUPLE request. The relationships illustrated in Figure 7-1 apply for all of the PATHCOM commands and the PATHMON-controlled objects.
Command List Overview of PATHCOM Table 7-1.
Command and Object Relationships Overview of PATHCOM Table 7-1. PATHCOM Commands (page 2 of 2) PATHCOM Commands Description Valid Objects * SUSPEND Interrupts execution of a SCREEN COBOL program until a RESUME command is received TERM SWITCH Causes primary and backup processes to exchange functions TCP TELL Displays a message on a terminal TERM *Although TELL is listed here as a valid object, it is not like other objects.
Command Format Overview of PATHCOM Table 7-2. Commands and Objects (page 2 of 2) Objects PATHCOM Commands TCP STOP x External TCP SUSPEND SWITCH TERM PROGRAM TELL x x x TELL x Command Format When entering PATHCOM commands, consider: • In general, options within a command are position independent. That is, you can place the options in any order within the command line.
Overview of PATHCOM Interactive Mode Interactive Mode PATHCOM functions in interactive mode when you enter commands from a terminal keyboard. PATHCOM prompts for a command by printing an equal sign (=). When you enter a command, PATHCOM executes the command and issues another prompt.
Overview of PATHCOM PATHMON Configuration File You can use DEFINEs to specify names for the files that PATHCOM uses directly as IN, OUT, and OBEY command files. In the following example, PATHCOM reads commands from the command file specified by DEFINE =CMD-FILE ($DATA.PW.CONFIG) and lists them on the device specified by DEFINE =OUT-FILE ($S): 12> ADD DEFINE =CMD-FILE, CLASS MAP, FILE $DATA.PW.
Overview of PATHCOM File Name Expansion File names of disk files are represented to programs on HP NonStop systems by these four parts concatenated into a contiguous string. Each part is separated from the other by a period as follows: \node.$volume.subvolume.file–identifier When you supply only a partial file name as a command parameter, the internal representation of the file name is expanded into the full four-part file name. As a minimum, a partial file name must consist of the file identifier.
8 Pathway Environment Control Commands In general, the PATHCOM commands that control the PATHMON process and the Pathway environment as a whole deal with objects managed by the TS/MP product or with the global PATHWAY and PATHMON objects. These commands are described in detail in the TS/MP System Management Manual. One of these commands, however— the SET PATHWAY command—allows you to define attribute values for HP NonStop Pathway/iTS objects in addition to the TS/MP objects.
Pathway Environment Control Commands SET PATHWAY Command MAXTCPS number is the maximum number of TCP objects that you can add to the PATHMON configuration file. The total of the values for MAXTCPS, MAXEXTERNALTCPS, and MAXLINKMONS cannot exceed 800. A maximum of 255 TCPs, external TCPs, and LINKMON processes are allowed to hold links concurrently to a single server process.
Pathway Environment Control Commands SET PATHWAY Command number must be a value from 0 through 4095. If you omit this attribute, the default is 0; temporary TERM objects cannot be started in the PATHMON environment through the RUN PROGRAM command. MAXTELLQUEUE number is the maximum number of tell messages that can be queued for each terminal. number must be a value from 0 through 300. If you omit this attribute, the default is 4.
Pathway Environment Control Commands Other Commands Example The following SET PATHWAY commands define requester-based elements in an example PATHMON environment: SET SET SET SET SET SET SET PATHWAY PATHWAY PATHWAY PATHWAY PATHWAY PATHWAY PATHWAY MAXEXTERNALTCPS 5 MAXPROGRAMS 1 MAXTCPS 4 MAXTELLQUEUE 5 MAXTELLS 50 MAXTERMS 25 MAXTMFRESTARTS 5 Note. The configuration in this example does not include server-based objects that run under TS/MP, nor does it include the global PATHWAY and PATHMON objects.
9 Terminal Control Process (TCP) Commands This section describes the PATHCOM commands that define and control TCPs; the commands are listed in alphabetical order.
Terminal Control Process (TCP) Commands ADD TCP Command ADD TCP Command Use the ADD TCP command to enter the name and description of a TCP into the PATHMON configuration file. Use this command after defining a TCP with the SET TCP command. ADD TCP tcp-name [ , tcp-attribute ]... tcp-name specifies the name of a TCP. A TCP name can be from 1 through 15 alphanumeric or hyphen characters and must start with a letter, be unique within the PATHMON environment, and not be a PATHCOM reserved word.
ALTER TCP Command Terminal Control Process (TCP) Commands ALTER TCP Command Use the ALTER TCP command to change the attribute values of a TCP that was previously added to the PATHMON configuration file. The TCP must be stopped before you can alter an attribute value. For a list of the TCP attributes, see the SET TCP Command on page 9-18. ALTER [ TCP ] tcp-name { , tcp-attribute } { , RESET tcp-keyword } { , RESET ( tcp-keyword [, tcp-keyword ]...
Terminal Control Process (TCP) Commands CONTROL TCP Command tcp-keyword specifies a single SET TCP command attribute keyword or several keywords separated by commas and enclosed in parentheses. Consideration If a TCP is configured with the TCP INSPECT attribute set to ON and a file name, the ALTER TCP RESET command sets the INSPECT attribute to OFF and deletes the file name. Examples The following commands change various TCP attribute values.
Terminal Control Process (TCP) Commands CONTROL TCP Command BACKUPCPU number specifies the CPU where the TCP backup process runs. The TCP primary process stops its existing backup process and creates a new backup in the CPU that you specify. If the CPU you specify for the BACKUPCPU attribute is the CPU where the backup process currently resides, the TCP still stops its backup process and starts a new backup process in the same CPU.
Terminal Control Process (TCP) Commands CONTROL TCP Command Both the primary and backup dump files are created on volume $DATA using subvolume PWAYDMPS. The P (primary TCP dump) and B (backup TCP dump) characters replace the last character of an eight-character name, or are appended to the end of a shorter dump file name. If the dump file already exists when the dump operation occurs, the TCPs reuse the existing file by purging the file’s information and writing the latest memory dump.
Terminal Control Process (TCP) Commands CONTROL TCP Command \node can be either a specific node name or \*, a generic name representing the node on which the PATHMON process is currently running. For example, the following file name directs the TCP to create the appropriate ZZTCPnnP or ZZTCPnnB file on volume $DATA using subvolume TCP05DMP: (FILE $DATA.TCP05DMP) (FILE $DATA.TCP05DMP.
CONTROL TCP Command Terminal Control Process (TCP) Commands Considerations • • • • If the TCP primary process is running in the CPU defined for the TCP backup process because of a SWITCH command or some other processor change, the BACKUPCPU attribute causes the PATHMON process to change the PATHMON configuration file so that it contains the current CPU numbers for both the primary and backup TCPs.
Terminal Control Process (TCP) Commands DELETE TCP Command Examples The following command stops the TCP backup process for TCP-1 and restarts it in CPU 5: CONTROL TCP TCP-1, BACKUPCPU 5 The following command sets the TCP DUMP attribute to OFF: CONTROL TCP TCP-1, DUMP OFF The following command changes the location of the TCP backup process and sets its DUMP attribute to ON: CONTROL TCP TCP-1, BACKUPCPU 4, DUMP ON (FILE T2DUMP) DELETE TCP Command Use the DELETE TCP command to remove a TCP description from
Terminal Control Process (TCP) Commands INFO TCP Command INFO TCP Command Use the INFO TCP command to display the attribute values defined in the PATHMON configuration file for a TCP. This command does not display information about external TCPs (TCPs that are controlled by another PATHMON process and are therefore outside this PATHMON environment). INFO [ / OUT list-file / ] { [ TCP ] tcp-name } { [ TCP ] (tcp-name [ , tcp-name ]...
Terminal Control Process (TCP) Commands INFO TCP Command OBEYFORM displays the information in the format you would use to set up a PATHMON configuration file; each attribute is displayed as a syntactically correct PATHCOM SET command. PATHCOM adds a RESET TCP command before and an ADD TCP command after each TCP description. Considerations • • • • INFO TCP displays both the TCP attribute values you explicitly defined for a TCP and default values for the attributes you did not explicitly define.
Terminal Control Process (TCP) Commands SET SET SET ADD TCP TCP TCP TCP INFO TCP Command TCLPROG \*.$MFG.PARTS.
Terminal Control Process (TCP) Commands PRIMARY TCP Command PRIMARY TCP Command Use the PRIMARY TCP command to resume operation of the TCP primary process in the CPU defined for this process in the PATHMON configuration file. Use this command after an individual process or CPU failure, or after a SWITCH command has moved the TCP primary process from one CPU to another. PRIMARY { [ TCP ] { tcp-name } } { { (tcp-name [ , tcp-name ] ...
Terminal Control Process (TCP) Commands REFRESH-CODE TCP Command Errors The following table lists the most common errors that can occur during the processing of the PRIMARY TCP command: This Message… Is Displayed When… *1070* BACKUP PROCESS NOT UP You have issued a CONTROL TCP, BACKUPCPU command or a SWITCH TCP command directly after issuing a PRIMARY TCP command and the TCP backup process has not had enough time to be restarted.
Terminal Control Process (TCP) Commands REFRESH-CODE TCP Command TCP * modifies the directory-checking operations of all TCPs running in this PATHMON environment. If STATE is specified, modifies all TCPs meeting the criteria specified. STATE state-type specifies the state of multiple TCPs. Possible values are: PENDING RUNNING STOPPED NOT PENDING NOT RUNNING NOT STOPPED This command modifies directory-checking operations only for those TCPs in the RUNNING state.
RESET TCP Command Terminal Control Process (TCP) Commands • If a TCP primary process fails and the CHECK-DIRECTORY attribute for that TCP is set to OFF, the TCP automatically reads the TCLPROG directory file during a SCREEN COBOL CALL statement before the TCP backup process takes over. This action occurs even if a REFRESH-CODE TCP command is not issued.
Terminal Control Process (TCP) Commands RESET TCP Command Considerations • • If you invoke the RESET TCP command after the SET TCP command but before the ADD TCP command, the attribute values you specify revert to the PATHMON default values. Some required SET TCP attributes have no default values. If you include a required attribute in the RESET TCP command, the attribute is set to a null value and must be set again before you add the TCP description to the PATHMON configuration file.
Terminal Control Process (TCP) Commands SET TCP Command SET TCP Command Use the SET TCP command to establish the values for the TCP object attributes. See Section 2, Configuring Pathway/iTS Objects, for more information on configuring TCPs. SET TCP tcp-attribute [ , tcp-attribute ]...
Terminal Control Process (TCP) Commands SET TCP Command see Appendix C, Configuration Limits and Defaults, in this manual, and to the TS/MP System Management Manual, for information about configuration limits. MAXTERMS number specifies the maximum number of terminals that the TCP can have open at the same time. number must be a value from 0 through 4095, where 4095 is the total allowed for all PATHMON-controlled objects. A TCP opens its terminals with a syncdepth of 1.
Terminal Control Process (TCP) Commands SET TCP Command If you omit this attribute, the default is ON. Note. This attribute affects the TCLPROG file at the TCP level only; it has no effect on any TCLPROG file at the TERMINAL or PROGRAM level. In other words, when the CHECK-DIRECTORY attribute is set to OFF, any TCLPROG file at the TERMINAL or PROGRAM level is still checked. ON directs the TCP to check the SCREEN COBOL program directory file for the latest accessible version of the called program unit.
Terminal Control Process (TCP) Commands SET TCP Command The value you assign for this attribute depends on the number and the size of the screen programs in your applications and also on the available swap space. Some guidelines for estimating this attribute are: • • • Use the size of the SCREEN COBOL programs (the screen data plus the RUNUNIT SIZE listed for these programs compiled with MAP) that make up the applications for this TCP.
Terminal Control Process (TCP) Commands SET TCP Command ON directs the TCP to create one or more disk files and write the contents of its data stack and its extended data segment to these files. After creating 10 primary process and 10 backup process dump files, the TCP stops performing memory dumps. This prevents writing over existing dump files that may indicate the original cause of a problem, and prevents filling a disk with dump files.
SET TCP Command Terminal Control Process (TCP) Commands OFF directs the TCP not to write data stack information to a file when it encounters an internal or fatal error. GUARDIAN-LIB file-name specifies the name of the library object file that contains additional TCP code space for user conversion routines. If you supply a value for this attribute, the operating system uses this file name and the file named in the PROGRAM attribute to access the TCP object code.
Terminal Control Process (TCP) Commands SET TCP Command HIGHPIN { ON | OFF } specifies whether the TCP runs at a high PIN or a low PIN. ON The TCP runs at a high PIN. OFF The TCP runs at a low PIN. If you omit this attribute, the default is OFF. For a TCP to run at a high PIN, the ?HIGHPIN flag must be set in the PATHTCP2 file. The ?HIGHPIN flag is set by default for this file. HOMETERM file-name specifies the name of the terminal that receives the TCP debugging information.
Terminal Control Process (TCP) Commands SET TCP Command The TCP can control a maximum of 8 terminals simultaneously running the Inspect program and can process a total of 20 program breakpoints for all SCREEN COBOL programs under inspection. If a TCP primary process fails, all breakpoints set for the Inspect program are lost. The breakpoints should be reentered when the TCP backup process takes over. LIKE tcp-name sets the attribute values for a TCP to those of the named TCP.
Terminal Control Process (TCP) Commands • SET TCP Command The longest reply (in bytes) possible from any server process replying to a SEND verb from any terminal under control of this TCP. If you omit this attribute, the default is 2000 bytes. The TCP uses this number and the value for the MAXTERMDATA attribute to allocate the size of the context areas (Slot 0 and Slot 1) for its terminals.
Terminal Control Process (TCP) Commands SET TCP Command NONSTOP { 0 | 1 } specifies whether a TCP runs with a backup process and performs normal checkpoint operations. 0 The TCP does not run with a backup process. 1 The TCP runs with a backup process. If you omit this attribute, the default is 1. In a single processor environment, using the default generates an error. You can either ignore the error or set NONSTOP to 0.
Terminal Control Process (TCP) Commands SET TCP Command If you omit this attribute, the default is in the format $Znnn. PROGRAM file-name specifies the TCP object file name (usually $SYSTEM.SYSTEM.PATHTCP2). If you do not specify a node name, the default node for file-name expansion can be affected by several factors, including values you specify for the TS/MP CMDVOL command and the NODEINDEPENDENT attribute of the NonStop TS/MP SET PATHWAY command.
Terminal Control Process (TCP) Commands SET TCP Command See Section 5, Tuning Your System Using Statistics, for more details about the SERVERPOOL attribute. Note. The pool space value allocated for SERVERPOOL is the value you configure rounded up to the next highest multiple of 4. STATS { ON | OFF } specifies whether the TCP gathers resource usage and system performance statistics. ON The TCP gathers statistics. OFF The TCP does not gather statistics. If you omit this attribute, the default is OFF.
Terminal Control Process (TCP) Commands SET TCP Command These buffers, like any pool buffer, are held only for the time required to perform the terminal I/O operation. Note. TERMBUF is not relevant to verbs (for example, the SEND MESSAGE verb) used with the IDS facility. TERMPOOL bytes specifies the number of bytes that the TCP allocates in its data area for all terminal I/O buffers. The value for bytes is the minimum number of bytes that the TCP allocates for the pool size.
SET TCP Command Terminal Control Process (TCP) Commands Errors The following table lists the most common errors that can occur during the processing of the SET TCP command: This Message… Is Displayed When… *1038* TCP tcp-name, PROCESS CREATION FAILURE: FILE SYSTEM ERROR ON LIBRARY FILE SECURITY VIOLATION (48) The person starting the PATHMON process does not have WRITE access to the file specified in the PROGRAM or GUARDIAN-LIB attributes.
Terminal Control Process (TCP) Commands SHOW TCP Command SHOW TCP Command Use the SHOW TCP command to display a subset of the TCP attributes in alphabetic order. This command displays the attribute values for a TCP not yet added to the PATHMON configuration file. SHOW [ / OUT list-file / ] TCP OUT list-file directs output to the named list file; this could be a DEFINE name. If this option is omitted, the PATHMON process directs the output to the PATHCOM list file; this is typically the home terminal.
Terminal Control Process (TCP) Commands START TCP Command Examples If you issue the SHOW TCP command before setting the TCP attributes, the following information is displayed: TCP AUTORESTART 0 CHECK-DIRECTORY ON DEBUG OFF . . . TCLPROG ? TERMBUF 1500 TERMPOOL 10000 The following command directs the SHOW command output to a file named TCPFLE: SHOW/OUT TCPFLE/TCP START TCP Command Use the START TCP command to initiate operation of TCPs.
Terminal Control Process (TCP) Commands START TCP Command This command starts only those TCPs in the STOPPED state. If you specify any other state, the system redisplays the command prompt; it does not display any output or generate an error message. You can substitute SEL for STATE.
Terminal Control Process (TCP) Commands STATS TCP Command STATS TCP Command Use the STATS TCP command to display resource usage and performance statistics collected by the TCP. These statistics provide information about TCP operations and data space allocations. This command does not display statistics for any external TCPs (TCPs that are controlled by another PATHMON process and are therefore outside this PATHMON environment) that might be linked to local server processes.
Terminal Control Process (TCP) Commands STATS TCP Command STATE state-type specifies the state of the multiple TCPs. Possible values are: PENDING RUNNING STOPPED NOT PENDING NOT RUNNING NOT STOPPED This command displays statistics only for those TCPs in the RUNNING state. If you specify any other state, the system redisplays the command prompt; it does not display any output or generate an error message. You can substitute SEL for STATE.
Terminal Control Process (TCP) Commands STATUS TCP Command Considerations • • • If the SET TCP STATS attribute value is set to OFF, the TCP does not gather information for this command. When you use the DETAIL option, the TCP displays the terminals and server class statistics described in Section 10, TERM Commands, and in the TS/MP System Management Manual, respectively.
Terminal Control Process (TCP) Commands STATUS TCP Command OUT list-file directs output to the file that you specify; this could be a DEFINE name. If you omit this option, the PATHMON process writes the output to the PATHCOM list file; this is typically the home terminal. tcp-name specifies the name of a previously defined and added TCP. E\node.$process-name specifies the name of an external TCP (a TCP that is controlled by another PATHMON process and, therefore, is outside this PATHMON environment).
STATUS TCP Command Terminal Control Process (TCP) Commands Display Format Without DETAIL The format of the display returned by the STATUS TCP command without the DETAIL option is shown below. TCP tcp-name . . . STATE state . . . ERROR pw-error . . . INFO info . . . PROCESS process-name . . . CPUS pri:backup . . . The fields in this display are as follows: Display Field Description TCP Name of the TCP STATE Current state of the TCP.
STATUS TCP Command Terminal Control Process (TCP) Commands The TCP, STATE, ERROR, INFO, PROCESS, and CPUS fields have the same meanings as for the display without the DETAIL option. The additional fields returned in the detailed display are as follows: Display Field Description TERM Name of the terminal WAIT Reason the terminal is waiting. The possible values are listed separately below. PENDING Command that is pending to the terminal.
Terminal Control Process (TCP) Commands STATUS TCP Command wait-cause Description TERMREAD The terminal is waiting for a file-system read operation to the terminal to complete. SERVER The terminal is waiting for a server process to become available (all links to the desired server class are currently in use), or there are outstanding link requests to the PATHMON process. SERVERIO The terminal is waiting for a request to a server to complete.
Terminal Control Process (TCP) Commands STOP TCP Command Consideration When a TCP from one PATHMON environment requests a link to a server class in a different PATHMON environment, the PATHMON process controlling the server class considers the requesting TCP to be an external process. However, a STATUS TCP command issued to the local PATHMON process (the one controlling the server class) displays the names of both the external and local TCPs.
Terminal Control Process (TCP) Commands STOP TCP Command If you omit this option, the STOP command aborts on any error. TCP * stops all TCPs configured in the PATHMON configuration file. STATE state-type specifies the state of the multiple TCPs. Possible values are: PENDING RUNNING STOPPED NOT PENDING NOT RUNNING NOT STOPPED This command stops only those TCPs in the RUNNING state.
Terminal Control Process (TCP) Commands SWITCH TCP Command SWITCH TCP Command Use the SWITCH command to make the TCP exchange the function of its primary process with the function of its backup process while the TCP is running. This command does not change the value of the SET TCP CPUS attribute in the PATHMON configuration file. SWITCH { [ TCP ] tcp-name } { [ TCP ] tcp-name [ , tcp-name ]...
Terminal Control Process (TCP) Commands Wild Card Support for TCP Commands Errors The following table lists the most common errors that can occur during the processing of the PRIMARY TCP command: This Message… Is Displayed When… *1070* BACKUP PROCESS NOT UP You have issued a CONTROL TCP, BACKUPCPU command or a SWITCH TCP command directly after issuing a PRIMARY TCP command and the TCP backup process has not had enough time to be restarted.
Example Terminal Control Process (TCP) Commands The system displays this output: TCP STATE ERROR INFO PROCESS CPUS TCP1 RUNNING \ACS.$Y75V 2:3 TCP2 RUNNING \ACS.$Y75V 2:3 TCPA RUNNING \ACS.$Y75V 2:3 TCPB RUNNING \ACS.
10 TERM Commands This section describes the PATHCOM commands that define and control configured TERM objects and control and inquire about temporary TERM objects; the commands are listed in alphabetical order.
ABORT TERM Command TERM Commands ABORT TERM Command Use the ABORT TERM command to abort a suspended or running TERM object. This command can be issued to configured and temporary TERM objects. ABORT { [ TERM ] term-name } { [ TERM ] ( term-name [ , term-name ]... ) } { TERM * [ , option [ , option ] ] } option is: STATE state-type TCP tcp-name term-name specifies the name of a TERM object. You can use either a single TERM name or several TERM names separated by commas and enclosed in parentheses.
ABORT TERM Command TERM Commands • The coupling information is lost after issuing an ABORT command.
ADD TERM Command TERM Commands ADD TERM Command Use the ADD TERM command to enter the name and description of a TERM object into the PATHMON configuration file. Use this command after defining a TERM object with the SET TERM command. This command can be issued only to configured TERM objects. ADD TERM term-name [ , term-attribute ]... term-name specifies the name of a TERM object.
ALTER TERM Command TERM Commands ALTER TERM Command Use the ALTER TERM command to change the attribute values of a TERM object that was previously added to the PATHMON configuration file. For a list of the TERM attributes, see the SET TERM Command on page 10-18. The TERM object must be stopped before you can alter an attribute value. This command can be issued only to configured TERM objects. ALTER [ TERM ] term-name { , term-attribute [ , term-attribute ]...
ALTER TERM Command TERM Commands Consideration If a TERM object is configured with the SET TERM INSPECT attribute set to ON and a file name, the ALTER TERM RESET command sets the INSPECT attribute to OFF and deletes the file name.
CONTROL TERM Commands TERM Commands CONTROL TERM Commands Use the CONTROL TERM commands to achieve synchronous upgrade for SCOBOL applications. The CONTROL TERM commands are: • • CONTROL TERM COUPLE CONTROL TERM DECOUPLE These commands are used to: • • couple TERM to a SERVER in the specified PATHMON. All sends from this TERM to the given SERVER go to the specified PATHMON. decouple TERM to delete coupling information. Note. The CONTROL TERM commands are supported by TS/MP 2.
CONTROL TERM Commands TERM Commands request to the access control server (ACS) infrastructure for delivering it to the appropriate server process. • • • • Use the CONTROL TERM DECOUPLE command to deliver the requests from the TERM for the specified server to any PATHMON in the domain. Specify the server and PATHMON names appropriately. The TERM must be in the STOPPED state for COUPLE request. The TERM can be in the STOPPED or RUNNING state for DECOUPLE request.
DELETE TERM Command TERM Commands DELETE TERM Command Use the DELETE TERM command to remove a TERM object description from the PATHMON configuration file. A TERM object must be stopped before PATHCOM can delete it. This command can be issued to configured and temporary TERM objects. DELETE [ TERM ] { term-name } { ( term-name [, term-name ]... ) } term-name specifies the name of a TERM object. Use either a single name or several names separated by commas and enclosed in parentheses.
INFO TERM Command TERM Commands INFO TERM Command Use the INFO TERM command to display the attribute values defined in the PATHMON configuration file for a TERM object. This command can be issued for configured and temporary TERM objects. INFO [ / OUT list-file / ] { [ TERM ] term-name [ , OBEYFORM ] } { [ TERM ] (term-name [, term-name ]...) [ , OBEYFORM ] } { TERM * [ , option [ , option ]...
INFO TERM Command TERM Commands OBEYFORM displays the information in the format you would use to set up a PATHMON configuration file; each attribute is displayed as a syntactically correct PATHCOM SET command. PATHCOM adds a RESET TERM command before and an ADD TERM command after each TERM object description. Considerations • • INFO TERM displays only the SET TERM attribute values that you explicitly defined for a TERM object. The attributes are displayed in alphabetic order.
INFO TERM Command TERM Commands The following command displays attribute values for all TERM objects in the STOPPED state under the control of the TCP named TCPA: INFO TERM *, STATE STOPPED, TCP TCPA The following sequence of commands captures a configuration for a complete PATHMON environment (minus the START PATHWAY command) in the command file called NEWCONFG: =INFO/OUT =INFO/OUT =INFO/OUT =INFO/OUT =INFO/OUT =INFO/OUT NEWCONFG/PATHMON, OBEYFORM NEWCONFG/PATHWAY, OBEYFORM NEWCONFG/TCP *, OBEYFORM NEWC
INSPECT TERM Command TERM Commands INSPECT TERM Command Use the INSPECT TERM command to invoke the HP Inspect symbolic debugger process to debug a SCREEN COBOL program running on a TERM object. This command establishes a breakpoint at the next program instruction; the program waits for commands from the Inspect process. Before you use the INSPECT TERM command, the SET TCP INSPECT attribute must be set to ON. This command can be issued for configured and temporary TERM objects.
INSPECT TERM Command TERM Commands Examples The following commands invoke the INSPECT process to debug a program running on the specified TERM objects: INSPECT TERM TERM-1 INSPECT TERM-2, FILE $TERM6 HP NonStop Pathway/iTS System Management Manual—426748-005 10 -14
RESET TERM Command TERM Commands RESET TERM Command Use the RESET TERM command to change the values for TERM object attributes from the ones you defined with the SET TERM command to the defaults. This command does not change the attributes of a TERM object already added to the PATHMON configuration file. This command can be issued only to configured TERM objects. RESET TERM [ term-keyword [ , term-keyword ]...
RESUME TERM Command TERM Commands RESUME TERM Command Use the RESUME TERM command to restart a screen program that has been suspended with the SUSPEND TERM command. The RESUME TERM command changes the TERM state to RUNNING. This command can be issued to configured and temporary TERM objects. RESUME { [ TERM ] term-name } { [ TERM ] ( term-name [ , term-name ]... ) } { TERM * [ , option [ , option ] ] } option is: STATE state-type TCP tcp-name term-name specifies the name of a TERM object.
RESUME TERM Command TERM Commands Considerations • • • After you enter a RESUME TERM command, the SCREEN COBOL program starts executing at the point where the TERM object was suspended. Screen recovery is performed before the program resumes normal execution. If a TERM object in TMF transaction mode was suspended for a programmatic reason and is in a restartable state, the RESUME TERM command initiates TERM activity by restarting the logical transaction at the BEGIN-TRANSACTION verb.
SET TERM Command TERM Commands SET TERM Command Use the SET TERM command to define values for the TERM object attributes. This command can be issued only to configured TERM objects. SET TERM term-attribute [ , term-attribute ]...
SET TERM Command TERM Commands PATHWAY command. For details, see Specifying Node Independence on page 2-5. The following is an example of a file name for a process emulating a terminal: \*.$PRO45.#X25LA.TERM45 where $PRO45 is the process file name and #X25LA is a communication line. If you define a process file name, you must also define a corresponding terminal type using the TYPE attribute. This attribute is required to create a valid definition for a TERM object.
SET TERM Command TERM Commands If you omit this attribute, the default is OFF. This attribute is effective only for terminals running in conversational mode. ON directs the TCP to accept the Break key function. If the TCP is executing a SCREEN COBOL program in conversational mode, the terminal operator can press the Break key to prematurely terminate ACCEPT and DISPLAY statements.
SET TERM Command TERM Commands If you omit this attribute, the default is used. If you specify a value greater than the defined maximum, the defined maximum is used. Terminal Type Default Value Defined Minimum Defined Maximum T16-6540 7 1 16* T16-6530WP 7 1 8* T16-6530 7 1** 8* T16-6520 3 1** 3 IBM-3270 1 1 1 TS530 8 1 8* * This is the absolute maximum allowed for the TCP. However, if the terminal or terminal emulator has less memory, the working value is negotiated downward.
SET TERM Command TERM Commands OFF corrects the display by suppressing the duplicate characters (if a terminal is configured so that it displays input characters). If you define this option for the supported terminal types T16-6520, T16-6530, and T16-6540, no input characters appear on the terminal screen. CURRENT directs the TCP to obtain the operating mode of the terminal from the operating system and to use that mode when it opens the terminal.
SET TERM Command TERM Commands If you omit file-name and the Inspect command terminal is not named in the SET TCP INSPECT attribute, the default is the home terminal of the TCP. OFF does not start the Inspect process when the program begins. IOPROTOCOL { 0 | 1 } specifies the protocol the TCP follows when a SCREEN COBOL SEND MESSAGE statement completes with a timeout or an unsolicited message. If you omit this attribute, the default is 0.
SET TERM Command TERM Commands file-name specifies the file name for the print device. You usually use file-name when the printer is not attached or when multiple attached printers are connected to a line controller. This attribute overrides the current value configured for the PRINTER attribute.
SET TERM Command TERM Commands In a production environment, it is better not to specify a TCLPROG filename for TERM (and PROGRAM) objects. If you specify a TCLPROG filename, the TCP checks the file every time a SCREEN COBOL program unit is requested. TMF { ON | OFF } specifies whether the TMF subsystem runs with this TERM object. This option is intended to be used only as a debugging aid. For more information about this attribute, see Appendix E, Setting TMF Parameters.
SET TERM Command TERM Commands term-type:term-subtype The possible values are: 1:n or IBM-3270:n IBM 3270 terminal 3:0 or T16-6520:0 6520 terminal 4:0 or T16-6530:0 6530 terminal 5:0 or CONVERSATIONAL Conversational-mode terminal 6:0 or T16-6540:0 6540 terminal emulating a 6530 terminal 7:n or INTELLIGENT:n Intelligent device or web client 8:0 or T16-6530WP:0 6530WP terminal For intelligent devices, term-type must be either 7 or INTELLIGENT, and termsubtype, which identifies th
SET TERM Command TERM Commands not specify a term-subtype value, the TCP determines the device type from a call to the file-system DEVICEINFO procedure. If a program unit for an intelligent device does not specify a term-subtype value in the TERMINAL IS clause or a term-subtype value is not specified in this attribute, a default value is used rather than the value obtained from the file-system DEVICEINFO procedure.
SHOW TERM Command TERM Commands SHOW TERM Command Use the SHOW TERM command to display a subset of the TERM attributes in alphabetic order. This command displays the attribute values for a TERM object not yet added to the PATHMON configuration file. This command can be issued only to configured TERM objects. SHOW [ / OUT list-file / ] TERM OUT list-file directs output to the named list file; this could be a DEFINE name.
SHOW TERM Command TERM Commands TCP ? TMF ON The following command directs the screen displays to a particular file: SHOW/OUT TERMFLE/TERM HP NonStop Pathway/iTS System Management Manual—426748-005 10 -29
START TERM Command TERM Commands START TERM Command Use the START TERM command to direct the TCP to begin executing a SCREEN COBOL program on one or more designated TERM objects. The TCP that controls the TERM objects must be running before you issue this command. This command can be issued only to configured TERM objects. START { [ TERM ] term-name [ , INITIAL program-unit-name ] } { [ TERM ] ( term-name [ , term-name ]... ) [ , INITIAL program-unit-name ] } { TERM * [ , option [ , option ]...
START TERM Command TERM Commands TCP tcp-name starts all TERM objects controlled by the specified TCP. Consideration The START TERM is valid only for configured TERM objects. Temporary TERM objects are started when the RUN PROGRAM command executes.
STATS TERM Command TERM Commands STATS TERM Command Use the STATS TERM command to display resource-usage and performance statistics, including response time information, collected by the TCP. These statistics provide information about TERM object operations. The STATS attributes of the SET TCP command control the gathering of these statistics. This command can be issued for configured and temporary TERM objects. STATS [ / OUT list-file / ] { [ TERM ] term-name [ , term-attribute [ , term-attribute ]...
STATS TERM Command TERM Commands COUNT number specifies the number of times that the STATS command repeats. You can stop the repeating of the command by pressing the Break key. FREQTABLE generates a frequency distribution table containing statistics for each terminal. The frequency distribution table is not generated⎯even if you specify the FREQTABLE option⎯under the following conditions: • • There have been fewer than 50 response time measurements collected at the time of the STATS request.
STATS TERM Command TERM Commands Considerations • • If the SET TCP STATS attribute is set to OFF, the TCP does not gather information for this command. Use the CONTROL TCP STATS ON command to dynamically enable the TCP statistics collection mechanism. For more information about the STATS TERM command display, see Section 5, Tuning Your System Using Statistics.
STATUS TERM Command TERM Commands STATUS TERM Command Use the STATUS TERM command to display the current status of a TERM object. This command can be issued for configured and temporary TERM objects. STATUS [ / OUT list-file / ] { [ TERM ] term-name [ , DETAIL ] } { [ TERM ] ( term-name [, term-name ]... ) [ , DETAIL ] } { TERM * [ , option [ , option ]... ] } option is: STATE state-type TCP tcp-name DETAIL OUT list-file directs output to the file that you specify; this could be a DEFINE name.
STATUS TERM Command TERM Commands TCP tcp-name displays status information for all TERM objects controlled by the specified TCP. Display Format Without DETAIL The format of the display returned by the STATUS TERM command without the DETAIL option is shown below. TERM term-name . . STATE state . . ERROR pw-error . . INFO info . . TCP TCP-name . . FILE file-name . .
STATUS TERM Command TERM Commands Display Format With DETAIL The format of the display returned by the STATUS TERM command with the DETAIL option is shown below. TERM term-name . . STATE state . . ERROR pw-error . . WAIT wait-cause PENDING pend-cause . . . . [ [ [ [ [ PU-FILE PU-NAME PU-VRSN INST-ADDR INST-CODE CHAR-SET TRANS-ID TRANS-RESTARTS SERVER COUPLING ACCEPT accept INFO info . . . . TCP TCP-name . . STOPMODE stopmode . . FILE file-name . . TRANSMODE transmode [ RECOVERING ] . .
STATUS TERM Command TERM Commands Display Field Description TRANS-ID Identifier assigned to a transaction by the TMF subsystem TRANSRESTARTS Number of times a transaction has been restarted SERVER Name of the server class the terminal is communicating with or waiting for The STATUS TERM command now displays the coupling information when issued with the DETAIL option. The following example shows the command output with coupling information: \NSSYS.$VOL.
STATUS TERM Command TERM Commands Example 10-1. Example STATUS TERM Display With DETAIL During Shutdown TERM TERM-1 STATE RUNNING WAIT SUSP-RESTART ERROR PENDING PU-FILE PU-NAME PU-VRSN INST-ADDR INST-CODE INFO ACCEPT TCP TCP-1 STOPMODE FILE \MARS.$PWY.#FILE1 TRANSMODE 0 %000000 %000000 Consideration In a production environment with a large number of terminals, it is better not to use the TERM * option to return status information on all TERM objects in the PATHMON environment.
STOP TERM Command TERM Commands STOP TERM Command Use the STOP TERM command to stop a TERM object. The TCP stops a TERM object as soon as the TERM object reaches a qualified state. A qualified state exists when the following three conditions are met: • • • The TERM object has reached a SCREEN COBOL ACCEPT statement. The SCREEN COBOL special register STOP-MODE is set to zero. The TERM object (if running under TMF auditing) is not in TMF transaction mode.
STOP TERM Command TERM Commands Consideration • • This command is usually issued only to configured TERM objects; temporary TERM objects created in response to a RUN PROGRAM command are usually terminated automatically by the PATHMON process when the task has completed. The coupling information is lost after issuing a STOP command.
SUSPEND TERM Command TERM Commands SUSPEND TERM Command Use the SUSPEND TERM command to direct the TCP to temporarily suspend execution of the SCREEN COBOL program. This command can be used for debugging when it is important to preserve the TERM object in its most recent state. The RESUME TERM command releases the suspension.
Wild Card Support for TERM Commands TERM Commands This command suspends only those TERM objects in the RUNNING state. If you specify any other state, the system redisplays the command prompt; it does not display any output or generate an error message. You can substitute SEL for STATE. TCP tcp-name suspends all TERM objects controlled by the specified TCP.
Example TERM Commands Example The following command displays the status information for all terms configured under the PATHMON environment whose name starts with TER: STATUS TERM TER* The system displays this output: TERM STATE ERROR INFO TCP FILE TERM1 RUNNING TCP1 \ACS.$ZTNT.#PTTAADV TERM2 RUNNING TCP1 \ACS.$ZTNT.#PTTAADV TERM3 RUNNING TCP1 \ACS.$ZTNT.#PTTAADV TERMA RUNNING TCP1 \ACS.$ZTNT.
Procedure for Synchronous Upgrade TERM Commands Procedure for Synchronous Upgrade Perform the following steps to achieve synchronous upgrade for SCOBOL applications: 1. Select a PATHMON server that must be upgraded within the domain. 2. Issue the CONTROL DOMAIN PARTITION command for the selected PATHMON server ($PM1.SRV) on the domain: PDMI 1>> OPEN %dom PATHMON : \NSSYS.$PM1 PATHMON : \NSSYS.$PM2 PDMI 2>> CONTROL DOMAIN PARTITION PATHMON $PM1 SERVER SRV %dom PARTITIONED FOR $PM1.SRV 3.
Procedure for Synchronous Upgrade TERM Commands All future requests from these TERMs are sent to the upgraded PATHMON server ($PM1.SRV) with 9th bit of flag parameter of the SERVERCLASS_SENDL_ procedure. 9. Start TERMs. Because of the prior CONTROL command, TERMs will send the request to the already upgraded PATHMON server. PDMI 8>> START TERM1 $Z2L0: TERM TERM1, STARTED All the terms send requests to the upgraded PATHMON server ($PM1.SRV).
11 PROGRAM Commands This section describes the PATHCOM commands that define and control PROGRAM objects; the commands are listed in alphabetical order.
PROGRAM Commands ADD PROGRAM Command ADD PROGRAM Command Use the ADD PROGRAM command to enter the name and the description of a PROGRAM object into the PATHMON configuration file. Use this command after defining a PROGRAM object with the SET PROGRAM command. ADD PROGRAM program-name [ , program-attribute ]... program-name specifies the PROGRAM object name.
ALTER PROGRAM Command PROGRAM Commands ALTER PROGRAM Command Use the ALTER PROGRAM command to change the attribute values of a PROGRAM object description that was previously added to the PATHMON configuration file. For a list of the PROGRAM object attributes, see the SET PROGRAM Command on page 11-15. ALTER [ PROGRAM ] program-name { , program-attribute } { , RESET program-keyword } { , RESET (program-keyword [ , program-keyword ]...
ALTER PROGRAM Command PROGRAM Commands Consideration If you set multiple values for the RUN PROGRAM TYPE command, the RESET option deletes only the type you specify. For example, if you define TYPE 2, TYPE 4, and TYPE 5 for a particular PROGRAM object and enter RESET TYPE 5, only TYPE 5 is deleted from the list of types for that PROGRAM object definition.
PROGRAM Commands DELETE PROGRAM Command DELETE PROGRAM Command Use the DELETE PROGRAM command to remove a PROGRAM object description from the PATHMON configuration file. DELETE [ PROGRAM ] { program-name } { ( program-name [ , program-name ]...) } program-name specifies the name of a PROGRAM object. Use either a single name or several names separated by commas and enclosed in parentheses.
PROGRAM Commands INFO PROGRAM Command INFO PROGRAM Command Use the INFO PROGRAM command to display the attribute values defined in the PATHMON configuration file for a PROGRAM object. INFO [ / OUT list-file / ] { [ PROGRAM ] program-name } { [ PROGRAM ] ( program-name [ , program-name ]... ) } { PROGRAM * } [ , OBEYFORM ] OUT list-file directs output to the named list file; this could be a DEFINE name.
PROGRAM Commands INFO PROGRAM Command Examples The following command requests PROGRAM object attribute information for two specific PROGRAM objects: INFO (PROG-3,PROG-5) The following command: INFO PROGRAM PROG-1, OBEYFORM causes the PATHMON process to display the PROGRAM object attributes in the following format: RESET PROGRAM SET PROGRAM ERROR-ABORT ON SET PROGRAM OWNER \*.
PROGRAM Commands RESET PROGRAM Command RESET PROGRAM Command Use the RESET PROGRAM command to change the values for the PROGRAM object attributes (listed under program-keyword in the syntax) from the values that you defined with the SET PROGRAM command to the defaults. This command does not change the attributes of a PROGRAM object already added to the PATHMON configuration file. RESET PROGRAM [ program-keyword [ , program-keyword ]...
PROGRAM Commands RESET PROGRAM Command The following commands reset the values for the specified attributes: RESET PROGRAM TMF RESET PROGRAM TCP, OWNER RESET PROGRAM TYPE 3, TYPE 4 HP NonStop Pathway/iTS System Management Manual—426748-005 11- 9
PROGRAM Commands RUN PROGRAM Command RUN PROGRAM Command Use the RUN PROGRAM command to initiate the execution of a SCREEN COBOL program on a device interoperating with your PATHMON environment. When this command is issued, the PATHMON process performs the following: 1. Creates a temporary TERM object based on the configuration information in the PROGRAM object template. (This is similar to the ADD TERM command.
PROGRAM Commands RUN PROGRAM Command PRINTER specifies the printer to be used for the SCREEN COBOL PRINT SCREEN verb. An attached printer either physically plugs into the terminal (for example, a 6520 or 6530 terminal) or connects to the same line controller (for example, an IBM 3270 compatible terminal using AM3270) as the terminal on which the SCREEN COBOL program runs. file-name specifies the file name for the print device.
RUN PROGRAM Command PROGRAM Commands The file-name parameter must be represented in network form. It must begin with a $ (dollar sign) followed by one to six alphanumeric characters, and the first character must be alphabetic. The file-name cannot exceed a total of seven characters including the $ symbol. Specifying a terminal name as the file allows you to run PATHCOM on one terminal and the SCREEN COBOL program on another terminal.
RUN PROGRAM Command PROGRAM Commands NOWAIT causes the program to execute concurrently with PATHCOM, so that the PATHCOM prompt returns immediately to your screen. To use the NOWAIT option, you must specify a terminal that is different from the terminal on which you give the RUN PROGRAM command. If you do not specify this option, the PATHCOM prompt does not return to your screen until after the program has completed running.
PROGRAM Commands RUN PROGRAM Command The following command directs a copy of the screen image to an unattached printer: RUN PROG-3,PRINTER $LP The following command directs the SALES program to run under control of process $FE.#TERMA, which emulates a 6530 terminal: RUN SALES, FILE $FE.
SET PROGRAM Command PROGRAM Commands SET PROGRAM Command Use the SET PROGRAM command to establish the values for the PROGRAM object attributes. SET PROGRAM program-attribute [ , program-attribute ]... program-attribute is: TCP tcp-name TYPE program-type ( [ [ [ [ [ [ [ [ , , , , , , , , INITIAL program-unit-name BREAK { ON | OFF } ] DISPLAY-PAGES number ] ECHO { ON | OFF | CURRENT } ] EXCLUSIVE { ON | OFF } ] IOPROTOCOL { 0 | 1 } ] MAXINPUTMSGS number ] TCLPROG file-name ] TRAILINGBLANKS { ON | OFF } ).
SET PROGRAM Command PROGRAM Commands TYPE program-type specifies the type of program, the name of the screen program that the TCP uses when starting the terminal, and specific terminal and program options.
SET PROGRAM Command PROGRAM Commands If the terminal operator presses the Break key while the TCP is executing an ACCEPT statement that is coded with an ESCAPE ON ABORT clause, the TCP stops accepting terminal input and terminates the ACCEPT statement without changes to the working storage section. Pressing the Break key has no effect on the TCP when the ACCEPT statement is coded without an ESCAPE ON ABORT clause.
PROGRAM Commands SET PROGRAM Command attributes. If you specify too many display pages, you might receive the terminal error ALL FIELDS USED. For detailed information on how to select the appropriate value for the DISPLAY-PAGES attribute, see Appendix F, Setting the DISPLAY-PAGES Parameter. ECHO { ON | OFF | CURRENT } overrides the terminal echo mode (that is, the mode configured for a terminal at system generation time) so that character input appears correctly on the terminal.
PROGRAM Commands SET PROGRAM Command IOPROTOCOL { 0 | 1 } specifies the protocol the TCP follows when a SCREEN COBOL SEND MESSAGE statement completes with a timeout or an unsolicited message. If you omit this attribute, the default is 0. 0 directs a TCP to issue a CANCEL procedure to cancel a SEND MESSAGE I/O. The I/O is cancelled because an unsolicited message arrives or a SEND MESSAGE TIMEOUT occurs. 1 directs a TCP to use a CONTROL-26 protocol to cancel a SEND MESSAGE I/O.
PROGRAM Commands SET PROGRAM Command TRAILINGBLANKS { ON | OFF } specifies whether the TCP suppresses the display of trailing ASCII blank characters in output lines sent to terminals by the SCREEN COBOL DISPLAY and SEND MESSAGE verbs. If you omit this attribute, the default is ON. ON directs the TCP not to suppress trailing ASCII blanks. OFF directs the TCP to suppress trailing ASCII blanks.
PROGRAM Commands SET PROGRAM Command OWNER owner-id specifies the user ID authorized to issue the RUN PROGRAM command. The user ID must be known to the system on which PATHCOM is running. Use this attribute in conjunction with the SECURITY attribute. The value of owner-id is one of the following: [ \system-number.] group-number, user-number [ \node.] group-name.
SET PROGRAM Command PROGRAM Commands If you omit file-name, the SCREEN COBOL TERMINAL-PRINTER special register is set to SPACES (that is, ASCII blanks). If a printer is not attached, the SCREEN COBOL verb PRINT-SCREEN obtains the printer’s file name from the special register TERMINAL-PRINTER. IS-ATTACHED directs the copy of the screen image to a printer that is either physically attached to the terminal or on the same line controller as the terminal on which the program runs.
SET PROGRAM Command PROGRAM Commands TMF { ON | OFF } specifies whether the TMF subsystem runs with this PROGRAM object. This option is intended to be used only as a debugging aid. For more information about this attribute, see Appendix E, Setting TMF Parameters. If you omit this attribute, the default is ON. ON invokes TMF auditing when necessary.
PROGRAM Commands SHOW PROGRAM Command SHOW PROGRAM Command Use the SHOW PROGRAM command to display a subset of the PROGRAM object attributes in alphabetic order. This command displays the attribute values for a PROGRAM object not yet added to the PATHMON configuration file. SHOW [ / OUT list-file / ] PROGRAM OUT list-file directs output to the named list file; this could be a DEFINE name.
PROGRAM Commands Wild Card Support for PROGRAM Commands The following command directs the SHOW PROGRAM display to the file named PROGFLE: SHOW/OUT PROGFLE/PROGRAM Wild Card Support for PROGRAM Commands The INFO PROGRAM command in PATHCOM allows management and operation of all PROGRAM objects configured under a PATHMON environment by using the wild card "*". It can be applied to a subset of configured PROGRAM objects. Note. The above mentioned wild card support is applicable only to TS/MP 2.
PROGRAM Commands The system displays this output: PROGRAM EXPROG ERROR-ABORT ON OWNER \ACS.255,255 SECURITY "N" TCP EX-TCP TMF OFF TYPE T16-6520 (INITIAL EXAMPLE) PROGRAM EXPROG1 ERROR-ABORT ON OWNER \ACS.255,255 SECURITY "N" TCP EX-TCP TMF OFF TYPE T16-6520 (INITIAL EXAMPLE) PROGRAM EXPROG2 ERROR-ABORT ON OWNER \ACS.
12 Tell Message Commands The commands for controlling tell messages are: • • • DELETE TELL INFO TELL TELL TERM These commands control messages that a TCP displays to the transaction process terminal operators. The commands can be directed to configured and temporary TERM objects. The SCREEN COBOL TELL-ALLOWED special register controls the issuing of these tell messages. When the TELL-ALLOWED special register is set to YES, tell messages can be displayed for the specified terminal.
Tell Message Commands DELETE TELL Command DELETE TELL Command Use the DELETE TELL command to delete a pending tell message. DELETE TELL number number specifies the number of the pending tell message.
Tell Message Commands INFO TELL Command INFO TELL Command Use the INFO TELL command to display the text of a pending tell message. INFO [ / OUT list-file / ] TELL { number } { * } OUT list-file directs output to the named list file; this could be a DEFINE name. If this option is omitted, the PATHMON process directs the output to the PATHCOM list file; this is typically the home terminal. number specifies an integer that identifies the message whose text is to be displayed.
TELL TERM Command Tell Message Commands TELL TERM Command Use the TELL TERM command to display a message on a terminal or set of terminals. The TCP waits for the terminal operator to complete the current screen before displaying the message, so normal operation is not disrupted.
Tell Message Commands TELL TERM Command Considerations • • • Each terminal has a circular queue for tell messages. If the queue is full when a new tell message is sent, the oldest tell message in the queue is overwritten by the new message. You specify the size of the queue using the MAXTELLQUEUE attribute in the SET PATHWAY command. When you issue a TELL command, the tell message is assigned a number between zero and the value of MAXTELLS.
Tell Message Commands TELL TERM Command HP NonStop Pathway/iTS System Management Manual—426748-005 12- 6
13 TCP Messages (Numbers 3000-3999) This section lists the messages for errors or other conditions reported by terminal control processes (TCPs). General Information All messages returned by the PATHMON environment are logged by the PATHMON process; however, messages in some number ranges represent errors reported to the PATHMON process by other processes.
TCP Messages (Numbers 3000-3999) Operating System Error Numbers For example: ERROR - *3161* TERM TERM-1, I/O ERROR --- INST CODE: SEND AT OFFSET %37 IN PROGRAM UNIT PROG-X(1) IN TCLPROG \SYS.$VOL.SUBVOL.POBJ Note. The additional information on terminal errors, which is appended to the standard error message text, significantly increases the size of messages sent to a log file.
TCP Messages (Numbers 3000-3999) • • TCP Messages A description of the application task that was in progress when the error was encountered Supporting documentation such as Event Management Service (EMS) logs, trace files, and dump files, if applicable If your local operating procedures require contacting the Global Customer Support Center (GCSC), supply your system number and the numbers and versions of all related products as well. 3002 *3002* TERM term-name, DEPENDING VARIABLE VALUE TOO BIG Cause.
TCP Messages (Numbers 3000-3999) TCP Messages 3005 *3005* TERM term-name, CALL: ACTUAL NUMBER OF PARAMETERS MISMATCHES FORMAL Cause. The number of parameters passed in the USING clause of a CALL statement does not equal the number of parameters given in the Procedure Division header of the called program. Effect. The operation fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program.
TCP Messages (Numbers 3000-3999) TCP Messages 3008 *3008* TERM term-name, ILLEGAL DATA REFERENCE Cause. There was an attempt to reference data outside the SCREEN COBOL program’s local data area. Effect. The operation fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see General Information on page 13-1. 3009 *3009* TERM term-name, REFERENCED SCREEN IS ILLEGAL FOR TERMINAL TYPE (%p-register) Cause.
TCP Messages (Numbers 3000-3999) TCP Messages Effect. The operation fails. Recovery. Check that the terminal type that was specified when the program unit was compiled is compatible with the physical terminal. If necessary, resolve the incompatibility.
TCP Messages (Numbers 3000-3999) TCP Messages 3012 *3012* TERM term-name, SCREEN REFERENCED BUT NOT DISPLAYED (screen-number) Cause. A screen was referenced but is not displayed. The screen is identified by a screen number; 0 corresponds to the first screen declared in the program source. Effect. The operation fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see General Information on page 13-1.
TCP Messages (Numbers 3000-3999) • TCP Messages Supporting documentation such as Event Management Service (EMS) logs, trace files, and dump files, if applicable If your local operating procedures require contacting the GCSC, supply your system number and the numbers and versions of all related products as well. 3015 *3015* TERM term-name, ARITHMETIC OVERFLOW Cause. A data-related error occurred during numeric manipulation.
TCP Messages (Numbers 3000-3999) TCP Messages 3018 *3018* TERM term-name, ERROR DURING TERMINAL IO (errnum) Cause. A file-system error occurred while a TCP was performing a terminal I/O operation. Effect. The I/O operation fails. Recovery. For information regarding the specified file-system error, see the Guardian Procedure Errors and Messages Manual. 3019 *3019* TERM term-name, WRONG TRANSFER COUNT IN TERMINAL IO Cause.
TCP Messages (Numbers 3000-3999) TCP Messages Effect. If the transaction message was sent to the server, the system does not know how much processing was done by the server before the failure. Recovery. Recovery depends on why the SEND operation failed as indicated by an earlier operator message. For additional information, see the description of that message. 3022 *3022* TERM term-name, SEND: SERVER CLASS NAME INVALID Cause.
TCP Messages (Numbers 3000-3999) • • TCP Messages A description of the application task that was in progress when the error was encountered Supporting documentation such as Event Management Service (EMS) logs, trace files, and dump files, if applicable If your local operating procedures require contacting the GCSC, supply your system number and the numbers and versions of all related products as well. 3025 *3025* TERM term-name, TERMINAL INPUT DATA STREAM INVALID Cause.
TCP Messages (Numbers 3000-3999) TCP Messages 3029 *3029* TERM term-name, TRANSACTION RESTART LIMIT REACHED Cause. The TCP attempted to restart a transaction more than the number of times defined for the MAXTMFRESTARTS attribute. Effect. The transaction is not restarted. Recovery. Isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see General Information on page 13-1. 3030 *3030* TERM term-name, TMF NOT CONFIGURED Cause.
TCP Messages (Numbers 3000-3999) TCP Messages 3036 *3036* TERM term-name, CANNOT CALL PU WITH TERMINAL-ERRORS DECLARATIVE Cause. A program unit was called with a USE FOR TERMINAL-ERRORS statement from a USE FOR TERMINAL-ERRORS declarative. Effect. The call fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see General Information on page 13-1.
TCP Messages (Numbers 3000-3999) TCP Messages 3041 *3041* TERM term-name, INVALID PRINTER SPECIFICATION Cause. An invalid printer was specified: either the printer for an IBM 3270 terminal is not attached to the same control unit as the terminal, or ATTACHED PRINT SCREEN was specified for a 6510 terminal. Effect. The operation fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program.
TCP Messages (Numbers 3000-3999) TCP Messages 3050 *3050* TERM term-name, TERMINAL STOPPED BY PENDING REQUEST Cause. The terminal stopped due to a pending stop request. Effect. None. Recovery. Informational message only; no corrective action is needed. 3051 *3051* TERM term-name, TERMINAL SUSPENDED BY PENDING REQUEST Cause. The terminal was suspended because of a pending suspend request. Effect. None. Recovery. Informational message only; no corrective action is needed.
TCP Messages (Numbers 3000-3999) TCP Messages 3054 *3054* TERM term-name, IO PROTOCOL DENIED (protocol-number) Cause. The indicated input/output protocol is invalid. This error occurs when the IOPROTOCOL attribute is set to 1, but the front-end process does not support completion of outstanding READ requests as specified in the terminal control process’s (TCP’s) call to the CONTROL procedure. Effect. The operation fails. Recovery.
TCP Messages (Numbers 3000-3999) • • • TCP Messages Your PATHMON configuration file and PATHMON process version A description of the application task that was in progress when the error was encountered Supporting documentation such as Event Management Service (EMS) logs, trace files, and dump files, if applicable If your local operating procedures require contacting the GCSC, supply your system number and the numbers and versions of all related products as well.
TCP Messages (Numbers 3000-3999) TCP Messages 3060 *3060* TERM term-name, DEVICE DOESN'T SUPPORT DOUBLEBYTE CHARACTERS --- INST CODE: instruct AT OFFSET %offset IN PROGRAM UNIT unit(version) IN TCLPROG tclprog Cause. The terminal task that the TCP is attempting to link with has aborted for one of the following reasons: • • • An attempt was made to run a SCREEN COBOL program unit containing doublebyte characters on an IBM 3270 device or emulator that does not support Start Field Extended (SFE) orders.
TCP Messages (Numbers 3000-3999) TCP Messages 3062 *3062* TERM term-name, INVALID KATAKANA OR DBCS DATA DESCRIPTOR (number) --- INST CODE:instruct AT OFFSET %offset IN PROGRAM UNIT unit(version) IN TCLPROG tclprog Cause. Translation routines were unable to correctly translate data from internal format to the external format required by the device. The field in error is indicated by the DESCRIPTOR number. Effect. The program terminates abnormally. Recovery. Abort the terminal.
TCP Messages (Numbers 3000-3999) • • TCP Messages A double-byte character started on the last column of a Fujitsu 3270 device. As a result, a space was inserted into the data stream that caused the number of displayable characters to exceed the field size. A double-byte character started on the last column of a JET6530 or PCT emulator. As a result, a space was inserted into the data stream that caused the number of displayable characters to exceed the field size. Effect. None. Recovery.
TCP Messages (Numbers 3000-3999) TCP Messages 3067 *3067* TERM term-name, FIELD CONTAINS OTHER THAN DCBS DESCRIPTOR number --- INST CODE:instruct AT OFFSET %offset IN PROGRAM UNIT unit(version) IN TCLPROG tclprog Cause. The TCP encountered a data field that did not contain only double-byte (Kanji) character data.
TCP Messages (Numbers 3000-3999) TCP Messages 3069 *3069* TERM term-name, UNILATERAL ABORT: BACKUP TASK STATE NOT VALID --- INST CODE: instruct AT OFFSET %offset IN PROGRAM UNIT program-unit(version) IN TCLPROG tclprog Cause. The terminal control process (TCP) encountered a backup open error for the identified TERM task. This message is generated when a TERM task fails and the backup TCP becomes the primary TCP before the TERM task is deleted. Effect.
TCP Messages (Numbers 3000-3999) TCP Messages 3072 *3072* RUN-TIME DYNAMIC ATTRIBUTE SETTING INVALID --INST CODE: instruct AT OFFSET %offset IN PROGRAM UNIT unit(version) IN TCLPROG tclprog Cause. An invalid attribute setting was detected, or the specified attribute setting would cause an out-of-bounds condition to occur during the run-time processing of the control structure. Effect. The SCREEN COBOL program is suspended. Recovery. Isolate and correct the problem within the SCREEN COBOL program.
TCP Messages (Numbers 3000-3999) TCP Messages Effect. The operation fails. Recovery. For information regarding the specified file-system error, see the Guardian Procedure Errors and Messages Manual. 3101 *3101* TCP tcp-name, TCLPROG DIRECTORY FILE OPEN ERROR (errnum) Cause. A file-system error occurred while the terminal control process (TCP) was opening the TCLPROG directory file. Effect. The operation fails. Recovery.
TCP Messages (Numbers 3000-3999) • TCP Messages Supporting documentation such as Event Management Service (EMS) logs, trace files, and dump files, if applicable If your local operating procedures require contacting the GCSC, supply your system number and the numbers and versions of all related products as well. 3104 *3104* TCP tcp-name, ILLEGAL TCLPROG CODE FILE Cause. The format of the file specified as the TCLPROG code file is invalid. This is an internal error. Effect.
TCP Messages (Numbers 3000-3999) TCP Messages 3107 *3107* TCP tcp-name, SWAP FILE CREATION ERROR (errnum) Cause. A file-system error occurred while the specified terminal control process (TCP) was attempting to obtain swap space from the Kernel Managed Swap Facility (KMSF). Effect. The swap space is not obtained from KMSF. Recovery. For information regarding the specified file-system error, see the Guardian Procedure Errors and Messages Manual.
TCP Messages (Numbers 3000-3999) TCP Messages 3112 *3112* TERM term-name, REPLY NUMBER NOT KNOWN TO PROGRAM Cause. A server replied with a message containing a reply code not listed in the SEND statement of the program. Effect. The operation fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see General Information on page 13-1. 3113 *3113* TERM term-name, TRANSACTION MESSAGE SIZE EXCEEDS LIMIT Cause.
TCP Messages (Numbers 3000-3999) TCP Messages If a reply exceeds the largest number of bytes allowed, the terminal control process (TCP) reports the byte count as the maximum reply length allowed plus 1. Effect. The operation fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see General Information on page 13-1. 3116 *3116* TCP tcp-name, ERROR DURING SERVER I/O (errnum) Cause.
TCP Messages (Numbers 3000-3999) • • TCP Messages A description of the application task that was in progress when the error was encountered Supporting documentation such as Event Management Service (EMS) logs, trace files, and dump files, if applicable If your local operating procedures require contacting the GCSC, supply your system number and the numbers and versions of all related products as well. 3119 *3119* TCP tcp-name, NO SPACE FOR NEW SERVER PROCESS Cause.
TCP Messages (Numbers 3000-3999) TCP Messages 3123 *3123* TERM term-name, NO SERVER PROCESS LINKED TO Cause. The SCREEN COBOL run unit was waiting for a link to a server class when the server class became unavailable. Effect. The SEND operation fails. Recovery. Recovery depends on why the SEND failed, which is indicated in an earlier message. For additional information, see the description of the earlier message.
TCP Messages (Numbers 3000-3999) TCP Messages Effect. The I/O operation fails and the TERM object is aborted. Recovery. Make sure that the router process is running. Then stop and restart the TERM object. 3141 *3141* TERM term-name, SOCKET ERROR (tcpip-errnum) Cause. A TCP/IP file-system error (tcpip-errnum) occurred during a socket function call performed by the terminal control process (TCP) on behalf of the specified TERM object. Effect.
TCP Messages (Numbers 3000-3999) TCP Messages 3144 *3144* TERM term-name, MEMORY ALLOCATION ERROR IN ROUTER Cause. A memory allocation error occurred within the router process while the router was maintaining connection request status information for the TERM objects. Effect. The router process terminates abnormally. The TERM objects that were waiting for connections resend their requests to the router process. Recovery. Restart the router process.
TCP Messages (Numbers 3000-3999) TCP Messages Recovery. Informational message only; no corrective action is needed. 3148 *3148* TERM term-name, ERROR DURING NOWAITED SOCKET SEND (tcpip-errnum) Cause. A TCP/IP file-system error (tcpip-errnum) occurred during a nowait socket send operation to the client. Effect. The send operation fails. The session is closed and the TERM object is reinitialized for a new session. Recovery. Informational message only; no corrective action is needed.
TCP Messages (Numbers 3000-3999) TCP Messages Recovery. For information regarding the specified file-system error, see the Guardian Procedure Errors and Messages Manual. 3162 *3162* TERM term-name, RECEIVED MESSAGE SMALLER THAN EXPECTED (byte-length) Cause. The message received from a RECEIVE UNSOLICITED MESSAGE operation, a TRANSFORM operation, or a SEND MESSAGE operation was smaller than expected. The length of the message received is indicated in bytes. Effect. The operation fails. Recovery.
TCP Messages (Numbers 3000-3999) TCP Messages 3165 *3165* TERM term-name, EDIT ERROR OCCURRED ON MESSAGE INPUT Cause. An edit error occurred on input from an intelligent device. Effect. The operation fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see General Information on page 13-1. If a USER CONVERSION clause is used in the program, check the user conversion routine.
TCP Messages (Numbers 3000-3999) TCP Messages 3168 *3168* TERM term-name, DEVICE SUBTYPE IS INVALID (subtype) Cause. The device subtype specified for the TYPE attribute of an intelligent device is invalid. Effect. The operation fails. Recovery. Enter the correct subtype value (that is, 0, 1, or 2) for the intelligent device. 3169 *3169* TERM term-name, ILLEGAL TIMEOUT VALUE (timeout) Cause. The SCREEN COBOL program unit specified an invalid timeout value.
TCP Messages (Numbers 3000-3999) TCP Messages Recovery. Isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see General Information on page 13-1. 3172 *3172* TERM term-name, SEND MESSAGE LENGTH EXCEEDS MAXIMUM ALLOWED (byte-length) Cause. After conversion of message data from an unsupported format to a supported format, the message length exceeded the maximum number of bytes allowed for all messages.
TCP Messages (Numbers 3000-3999) TCP Messages 3175 *3175* TERM term-name, EDIT ERROR OCCURRED ON MESSAGE OUTPUT Cause. An edit error occurred on output to an intelligent device. Effect. The operation fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see General Information on page 13-1. If a USER CONVERSION clause is used in the program, check the user conversion routine.
TCP Messages (Numbers 3000-3999) TCP Messages 3178 *3178* TERM term-name, ATTEMPT TO RECEIVE UNSOLICITED MESSAGE WHEN TERM MAXINPUTMSGS = 0 Cause. A SCREEN COBOL program unit attempted to receive an unsolicited message, but the terminal was not configured for unsolicited messages. Effect. The operation fails. Recovery. Configure the MAXINPUTMSGS attribute for the associated TERM or PROGRAM object to a value greater than zero. 3179 *3179* TERM term-name, DATA LEFT OVER ON SCATTER TO WORKING STORAGE Cause.
TCP Messages (Numbers 3000-3999) TCP Messages Effect. The operation fails. Recovery. This situation is disallowed only on output processing through the message section. Isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see General Information on page 13-1. 3182 *3182* TERM term-name, DELIMITER IS NOT BYTE ALIGNED Cause. The delimiter’s offset was not byte-aligned during delimited field processing.
TCP Messages (Numbers 3000-3999) TCP Messages 3185 *3185* TERM term-name, FIELD OCCURRENCE EXCEEDS WORKING STORAGE MAXIMUM OCCURRENCE (offset) Cause. An error occurred during an attempt to map between working storage and the message section; the message section definition cannot support the structure in working storage. offset indicates the instruction address of the program unit. Effect. The operation fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program.
TCP Messages (Numbers 3000-3999) TCP Messages 3200 *3200* TCP tcp-name, INVALID FORMAT MESSAGE RECEIVED BY TCP Cause. A terminal control process (TCP) or LINKMON process received an invalid request from the PATHMON process. This error usually occurs when incompatible versions of the PATHMON process and the TCP or the LINKMON process are running at the same time. Effect. The request cannot be processed. Recovery.
TCP Messages (Numbers 3000-3999) • TCP Messages Supporting documentation such as Event Management Service (EMS) logs, trace files, and dump files, if applicable If your local operating procedures require contacting the GCSC, supply your system number and the numbers and versions of all related products as well. 3202 *3202* TCP tcp-name, TERMINAL IDENTIFIER NOT KNOWN TO TCP Cause. The TCP encountered an unknown terminal identifier. This is an internal error. Effect. The request cannot be processed.
TCP Messages (Numbers 3000-3999) TCP Messages Recovery. Repeat the operation when the TCP is in the appropriate state. 3205 *3205* TERM term-name, TERMINAL STATE DOES NOT ALLOW OPERATION Cause. The specified terminal is not in the appropriate state for the attempted operation. Effect. The operation fails. Recovery. Repeat the operation when the terminal is in the appropriate state. 3206 *3206* TCP tcp-name, TCP CANNOT HANDLE MORE TERMINALS Cause.
TCP Messages (Numbers 3000-3999) TCP Messages Recovery. Use the SCREEN COBOL Utility Program (SCUP) to merge program units for all the requesters configured for the TCP into fewer than 16 pseudocode files; or, reassign requesters among TCPs so that the requesters assigned to a given TCP share fewer pseudocode files. 3209 *3209* TCP tcp-name, PROCESSOR DOES NOT HAVE PATHWAY MICROCODE Cause. The microcode required to operate TS/MP or Pathway/iTS software is not installed on this system. Effect.
TCP Messages (Numbers 3000-3999) TCP Messages Effect. The TCP recreates the backup process, if possible. Recovery.
TCP Messages (Numbers 3000-3999) TCP Messages Effect. The backup process terminates. Recovery. For additional information, see the description associated with the nested message. 3216 *3216* TCP tcp-name, TCP INTERNAL ERROR (%p-register) Cause. An internal TCP failure occurred. %p-register is the value of the P-register at the time of the failure, in octal. Effect. The TCP terminates. If the DUMP attribute is on, the TCP takes a memory dump before terminating. Recovery.
TCP Messages (Numbers 3000-3999) • • TCP Messages A description of the application task that was in progress when the error was encountered Supporting documentation such as Event Management Service (EMS) logs, trace files, and dump files, if applicable If your local operating procedures require contacting the GCSC, supply your system number and the numbers and versions of all related products as well. 3218 *3218* TCP tcp-name, TAKEOVER BY BACKUP Cause.
TCP Messages (Numbers 3000-3999) TCP Messages Recovery. Reduce the number of terminals under the control of a TCP that are attempting to use the Inspect process. 3222 *3222* TCP tcp-name, INSPECT BREAKPOINT TABLE FULL Cause. An attempt was made to set more than 20 program breakpoints for each TCP. Effect. The Inspect operation fails. Recovery. Set fewer than 20 program breakpoints for each TCP. 3223 *3223* TCP tcp-name, REQUEST NOT ALLOWED WHILE AT BREAKPOINT Cause.
TCP Messages (Numbers 3000-3999) TCP Messages 3226 *3226* TCP tcp-name, REQUESTED FUNCTION NOT SUPPORTED IN THIS RELEASE Cause. The PATHMON process requested a function that is not supported in this version of the terminal control process (TCP) or LINKMON process. Effect. The operation fails. Recovery. Use a newer version of the TCP or LINKMON process. 3227 *3227* TERM term-name, SEND: EXTERNAL PATHMON NAME INVALID Cause.
TCP Messages (Numbers 3000-3999) TCP Messages Recovery. Isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see General Information on page 13-1. 3230 *3230* TERM term-name, SEND: NO ROOM FOR NEW EXTERNAL PATHMON IN TCP Cause.
TCP Messages (Numbers 3000-3999) TCP Messages 3233 *3233* TCP tcp-name, SERVER PROCESS UNKNOWN Cause. The terminal control process (TCP) or LINKMON process received a message from the PATHMON process containing a reference to a server process that is unknown to the TCP or LINKMON process. This is an internal error. Effect. The TCP or LINKMON process cannot process the request. Recovery.
TCP Messages (Numbers 3000-3999) TCP Messages Recovery. Check the log file for the name of the file that is causing the problem; then correct the problem. 3238 *3238* TERM term-name, PARAMETER REFERENCE EXCEEDS FORMAL PARAMETER SIZE Cause. A linkage section in a called program is larger than the maximum size of the corresponding parameter in the calling program. Effect. The call fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program.
TCP Messages (Numbers 3000-3999) • TCP Messages Supporting documentation such as Event Management Service (EMS) logs, trace files, and dump files, if applicable If your local operating procedures require contacting the GCSC, supply your system number and the numbers and versions of all related products as well. 3241 *3241* TCP tcp-name, UNSOLICITED MESSAGE REJECTED BY TCP (errnum) or *3241* TERM term-name, UNSOLICITED MESSAGE REJECTED BY TCP (errnum) Cause.
TCP Messages (Numbers 3000-3999) TCP Messages Recovery. Take recovery action based on the error number. For information about unsolicited-message errors, see the HP NonStop Pathway/iTS TCP and Terminal Programming Guide. 3242 *3242* TCP tcp-name, MULTIPLE UNSOLICITED MESSAGES REJECTED Cause.
TCP Messages (Numbers 3000-3999) TCP Messages Effect. The operation fails. Recovery. A licensed copy of Pathway/iTS should be installed. 3246 *3246* SERVER CLASS IS EITHER IN FREEZE PENDING OR IN FROZEN STATE Note. This error does not appear in the RETCODE token or in an error list; it appears only in response to the STATUS TCP or STATUS TERM command. Cause. The server class to which a send or a dialog was targeted, is either in freezepending or in frozen state. Effect. The operation fails.
TCP Messages (Numbers 3000-3999) TCP Messages 3248 *3248* A RETRYABLE LINKMON CONNECT ERROR OCCURRED (errnum) Note. This error does not appear in the RETCODE token or in an error list; it appears only in response to the STATUS TCP or STATUS TERM command. Cause. A retryable LINKMON connect error occurred on primary CPU of the TCP. The associated file error gives the file-system error occurred with the LINKMON process. Typical file-system errors are 100 (FENOTRDY), 28(FETOOMANY) and 30 (FENOLCB).
TCP Messages (Numbers 3000-3999) TCP Messages program. If ON ERROR clause is not mentioned, then TCP aborts the terminal after logging the error against the term. If the term is associated with any dialog, the dialog is also aborted. Recovery. Recovery is application specific. Since TCP does not know the status of the last I/O hence the SEND/DIALOG operation can be retried if it is OK to send duplicate message to the server class. Pathway/iTS 1.
TCP Messages (Numbers 3000-3999) TCP Messages Cause. A DIALOG-END statement is called when the server has not yet ended the dialog. Effect. The operation fails. If ON ERROR clause is mentioned, then error is reported against the term but the term continues to run depending on the error-handling logic in the SCREEN COBOL program. If ON ERROR clause is not mentioned, then TCP aborts the terminal after logging the error against the term. If the term is associated with any dialog the dialog is also aborted.
TCP Messages (Numbers 3000-3999) TCP Messages the SCREEN COBOL program. If ON ERROR clause is not mentioned, then TCP aborts the terminal after logging the error against the term. Recovery. Clean up the requester portion of dialog by calling DIALOG-END and initiate a new dialog if required.
A Syntax Summary This appendix contains summaries of the PATHCOM commands described in this manual. All commands are listed in alphabetical order. Note that PATHCOM commands that create or manage TS/MP objects, such as SERVER and LINKMON objects, are described in the TS/MP System Management Manual. ABORT { [ TERM ] term-name } { [ TERM ] ( term-name [ , term-name ]... ) } { TERM * [ , option [ , option ] ] } option is: STATE state-type TCP tcp-name ADD PROGRAM program-name [ , program-attribute ]...
Syntax Summary ALTER [ TCP ] tcp-name { , tcp-attribute } { , RESET tcp-keyword } { , RESET ( tcp-keyword [, tcp-keyword ]...
Syntax Summary DELETE [ PROGRAM ] { program-name } { ( program-name [ , program-name ]...) } DELETE [ TCP ] { tcp-name } { ( tcp-name [ , tcp-name ]...) } DELETE TELL number DELETE [ TERM ] { term-name } { ( term-name [, term-name ]... ) } INFO [ / OUT list-file / ] { [ PROGRAM ] program-name } { [ PROGRAM ] ( program-name [ , program-name ]... ) } { PROGRAM * } [ , OBEYFORM ] INFO [ / OUT list-file / ] { [ TCP ] tcp-name } { [ TCP ] (tcp-name [ , tcp-name ]...
Syntax Summary INFO [ / OUT list-file / ] { [ TERM ] term-name [ , OBEYFORM ] } { [ TERM ] (term-name [, term-name ]...) [ , OBEYFORM ] } { TERM * [ , option [ , option ]... ] } option is: STATE state-type TCP tcp-name OBEYFORM INSPECT [ TERM ] term-name [ , FILE file-name ] PRIMARY { [ TCP ] { tcp-name } } { { (tcp-name [ , tcp-name ] ... ) } } { TCP * } [ , IFPRICPU number ] REFRESH-CODE { [ TCP ] tcp-name } { [ TCP ] ( tcp-name [, tcp-name ]...
Syntax Summary RESET TCP [ tcp-keyword [ , tcp-keyword ]... ] tcp-keyword is: AUTORESTART CHECK–DIRECTORY CODEAREALEN CPUS DEBUG DUMP GUARDIAN–LIB GUARDIAN–SWAP HIGHPIN HOMETERM RESET TERM INSPECT MAXINPUTMSGLEN MAXINPUTMSGS MAXPATHWAYS MAXREPLY MAXSERVERCLASSES MAXSERVERPROCESSES MAXTERMDATA MAXTERMS NONSTOP POWERONRECOVERY PRI PROCESS PROGRAM SENDMSGTIMEOUT SERVERPOOL STATS SWAP TCLPROG TERMBUF TERMPOOL [ term-keyword [ , term-keyword ]...
Syntax Summary RUN [ PROGRAM ] program-name [ , program-parameter [ , program-parameter ]... ] program-parameter is: PRINTER { file-name [ IS-ATTACHED ] } { IS-ATTACHED } FILE file-name TYPE program-type NOWAIT SET PATHWAY pw-attribute [ , pw-attribute ]...
Syntax Summary SET PROGRAM program-attribute [ , program-attribute ]... program-attribute is: TCP tcp-name TYPE program-type ( [ [ [ [ [ [ [ [ , , , , , , , , INITIAL program-unit-name BREAK { ON | OFF } ] DISPLAY-PAGES number ] ECHO { ON | OFF | CURRENT } ] EXCLUSIVE { ON | OFF } ] IOPROTOCOL { 0 | 1 } ] MAXINPUTMSGS number ] TCLPROG file-name ] TRAILINGBLANKS { ON | OFF } ) ...
Syntax Summary SET TCP tcp-attribute [ , tcp-attribute ]...
Syntax Summary SET TERM term-attribute [ , term-attribute ]...
Syntax Summary STATS [ / OUT list-file / ] { [ TCP ] tcp-name } { [ TCP ] ( tcp-name [ , tcp-name ]... ) } { TCP * [ , option [ , option ]... ] } [ , tcp-attribute [ , tcp-attribute ]...
Syntax Summary STATS [ / OUT list-file / ] { [ TERM ] term-name [ , term-attribute [ , term-attribute ]... ] } { [ TERM ] ( term-name [, term-name ]... ) [ , term-attribute [ , term-attribute ]... ] } { TERM * [ , option [ , option ] ...
Syntax Summary STATUS [ / OUT list-file / ] { [ TERM ] term-name [ , DETAIL ] } { [ TERM ] ( term-name [, term-name ]... ) [ , DETAIL ] } { TERM * [ , option [ , option ]... ] } option is: STATE state-type TCP tcp-name DETAIL STOP { [ TCP ] tcp-name [ , WAIT ] } { [ TCP ] ( tcp-name [ , tcp-name ]... ) [ , WAIT ] } { TCP * [ , option [ , option ] ] } option is: STATE state-type WAIT STOP { [ TERM ] term-name } { [ TERM ] ( term-name [ , term-name ]...
Syntax Summary SWITCH { [ TCP ] tcp-name } { [ TCP ] tcp-name [ , tcp-name ]...
Syntax Summary HP NonStop Pathway/iTS System Management Manual—426748-005 A -14
B PATHCOM Reserved Words This appendix contains a list of words that are reserved and should not be used for variable names in PATHCOM commands. Although it might be possible in some contexts to use words on this list, HP strongly recommends that these words not be used in any user-assigned names.
TS/MP Objects PATHCOM Reserved Words MAXSERVERCLASSES PROGRAM MAXSERVERS PROTECTED VOLUME MAXSTARTUPS REC WAIT MAXTCPS RESET WARM MAXSPI MAXTELLQUEUE MAXTELLS SECS MAXTERMS SECURITY MAXTMFRESTARTS SEL MINS SERVER MODE SET SHARED NODEINDEPENDENT SHOW NUMSTATIC SHUTDOWN SHUTDOWN2 OBEY START OBEYFORM STARTUP OBEYVOL STATS OFF STATUS ON STDERR OPEN STDIN OSS STDOUT OUT STOP OUTPUT SWITCH OWNER T16-6510 PARAM T16-6520 PATHMON T16-6530 PATHWAY T16-6530WP POWERON
Pathway/iTS Objects PATHCOM Reserved Words Pathway/iTS Objects Reserved words exclusive to the HP NonStop PathwayiTS (requester-oriented) objects appear in the following table: ABORT BREAK PRINTER CHECK-DIRECTORY REFRESH-CODE CODEAREALEN RESUME CURRENT RUN DIAGNOSTIC SERVERPOOL DISPLAY-PAGES STATE SUSPEND ECHO SWAP ERROR-ABORT TCLPROG INITIAL TCP INSPECT TELL IOPROTOCAL TERM IS-ATTACHED TERMBUFF TERMPOOL MAXINPUTMSGLEN TRAILINGBLANKS MAXINPUTMSGS TYPE MAXPATHWAYS MAXREPLY MAXSERV
PATHCOM Reserved Words Pathway/iTS Objects HP NonStop Pathway/iTS System Management Manual—426748-005 B- 4
C Configuration Limits and Defaults Table C-1 lists global limits for various items within each PATHMON environment. Note. These limits are subject to change with product SPRs or with new software releases. Table C-1. Global PATHMON Environment Limits Item Limits Per PATHMON Environment PROGRAM objects Maximum of 4095 supported by each PATHMON process; suggested maximum of 4094 to avoid error 1108.
Configuration Limits and Defaults Table C-2. Limits and Defaults for Parameters (page 1 of 6) PATHCOM Parameter* SPI Token/Field** Value Limits and Defaults AUTORESTART ZAUTORESTART Values: 0 through 32,767 Value should be greater than 0. Default: 0 Values: 0 through 15 Value should be a CPU that is not physically adjacent to the primary CPU. Default: Depends on command Values: ON | OFF Default: OFF Values: ON | OFF Suggested value is OFF for production, ON for development.
Configuration Limits and Defaults Table C-2. Limits and Defaults for Parameters (page 2 of 6) PATHCOM Parameter* SPI Token/Field** Value Limits and Defaults DUMP ZDUMP Values: ON | OFF Suggested value is ON. Default: OFF Values: ON | OFF | CURRENT Default: ON Values: ON | OFF Default: ON Values: ON | OFF Default: OFF Values: One through seven alphanumeric characters, including the $; the first character after the $ must be alphabetic. Default: N.A.
Configuration Limits and Defaults Table C-2. Limits and Defaults for Parameters (page 3 of 6) PATHCOM Parameter* SPI Token/Field** Value Limits and Defaults MAXSERVERCLASSES ZMAXSERVERCLASSES Values: 0 through 4095 Total of MAXSERVERS values for all server classes must not exceed value of MAXSERVERPROCESSES. Default: N.A. MAXSERVERPROCESS ES ZMAXSERVERPROCESS ES Values: 0 through 4095 Default: N.A. MAXTCPS ZMAXTCPS Described in TS/MP Management Programming Manual.
Configuration Limits and Defaults Table C-2. Limits and Defaults for Parameters (page 4 of 6) PATHCOM Parameter* SPI Token/Field** Value Limits and Defaults PROGRAM ZPROGRAM Values: For Guardian operating environment server processes, the name of the Guardian object file name; 1 through 15 alphanumeric or hyphen characters; first character must be alphabetic.
Configuration Limits and Defaults Table C-2. Limits and Defaults for Parameters (page 5 of 6) PATHCOM Parameter* SPI Token/Field** Value Limits and Defaults TERM ZTERM Values: 1 through 15 alphanumeric or hyphen characters; first character must be alphabetic. Default: N.A. Values: 256 through value of TERMPOOL TERMBUF ZTERMBUF If writing diagnostic display messages to terminal: 1315 through value of TERMPOOL.
Configuration Limits and Defaults Table C-2.
Configuration Limits and Defaults HP NonStop Pathway/iTS System Management Manual—426748-005 C- 8
D Migration Information This appendix covers migration and compatibility issues for Pathway applications that include the HP NonStop Pathway/iTS product on C-series and D-series systems. The following topics are discussed: • • Interprocess communication issues Application conversion For more information about running applications on systems running the D-series RVU, see the Guardian Application Conversion Guide. Note.
Application Conversion Guidelines Migration Information If a process runs at a high PIN, all processes that communicate with that process must be able to communicate with a high-PIN process. The characters "N.A." indicate that an option is not available. Table D-1. Pathway/iTS Process High-PIN and Low-PIN Support Operation PATHTCP2 SCREEN COBOL SCUP Run at a high PIN Yes No No Service high-PIN server Yes N.A. N.A. Service high-PIN requesters Yes N.A. N.A.
Migration Information Application Conversion Guidelines For more information about converting your applications, see the Guardian Application Conversion Guide.
Migration Information Application Conversion Guidelines HP NonStop Pathway/iTS System Management Manual—426748-005 D- 4
E Setting TMF Parameters When you are configuring and controlling a Pathway application that uses TMF, consider the following three basic questions: • • • How do the settings you specify for the TMF parameter of the SET TERM and SET PROGRAM commands affect SCREEN COBOL SEND statements? How is the TCP checkpointing strategy affected by the settings you specify for the TMF parameter of the SET SERVER command? (For more information about the SET SERVER command beyond that presented in this appendix, see th
Setting TMF Parameters Effect of TMF Parameters in PATHCOM on SCREEN COBOL SEND Operations commands affect a SCREEN COBOL SEND statement when the PATHMON process and the TMF subsystem are both running on the system. Note. The SET SERVER command is used to set attributes for SERVER objects created and controlled under TS/MP. For more information about SERVER objects and the server environment, see the TS/MP System Management Manual and the TS/MP Management Programming Manual.
Effect of TMF Parameters in PATHCOM on SCREEN COBOL SEND Operations Setting TMF Parameters Figure E-1.
Setting TMF Parameters Timeouts on SEND Operations to Servers Depending on the type of file access attempted, the TCP either allows the SEND statement to execute or issues the appropriate error message.
Setting TMF Parameters Precautions for Using TMF Parameters operate on audited files require fewer checkpoints than SEND requests to servers that do not operate under TMF protection. TCP checkpointing requirements can be significantly reduced if Pathway applications running with the TMF subsystem have TMF protected servers read outside of transaction mode before updating the database. Caution.
Setting TMF Parameters Precautions for Using TMF Parameters HP NonStop Pathway/iTS System Management Manual—426748-005 E- 6
F Setting the DISPLAY-PAGES Parameter This appendix explains how to calculate the DISPLAY-PAGES parameter of the SET TERM and SET PROGRAM commands. Note. For more information on the SET TERM and SET PROGRAM commands, including syntax descriptions, see Section 10, TERM Commands, and Section 11, PROGRAM Commands. Screen Caching The DISPLAY-PAGES parameter specifies the depth of the terminal’s screen caching.
Determining the DISPLAY-PAGES Value Setting the DISPLAY-PAGES Parameter Figure F-1. RAM Organization Within a Terminal Terminal Random Access Memory (RAM) Screen-Image Area Screen A Screen B Screen C Field-Attribute Entries Area Field-Attribute Entries Area: Screen A Field-Attribute Entries Area: Screen B Field-Attribute Entries Area: Screen C VST024.vsd Determining the DISPLAY-PAGES Value The correct value of the DISPLAY-PAGES parameter depends on the application being run.
Estimating Field-Attribute Entries Setting the DISPLAY-PAGES Parameter Estimating Field-Attribute Entries Although the actual number of field-attribute entries a screen definition contains depends on the layout of the screen, you can estimate the number of field-attribute entries by multiplying the number of screen fields by 2. For example, a screen with 10 input fields has approximately 20 field-attribute entries.
Assessing Terminal Capacity Setting the DISPLAY-PAGES Parameter Table F-3. Storage Capacity of 6530 Terminal DISPLAY-PAGES Value Average Number of Field-Attribute Entries per Screen 1 4095 2 2510 3 1488 4 976 5 670 6 465 7 319 8 209 Table F-4 lists the average number of field-attribute entries a TS530 terminal can store. Note that the number of pages that the TS530 terminal can cache is fixed at 8. Table F-4.
G Source Code for Programs in Section 6 This appendix presents the source code for the screen and server programs used in the examples described in Section 6, Examples of System Management Tasks. You can configure and run a real PATHMON environment based on this example. To create this environment: 1. Enter the source code for the screen program into a text file named SC (using your text editor). 2. Enter the source code for the server program into a text file named SV (using your text editor). 3.
Source Code for Screen Program Source Code for Programs in Section 6 Example G-1. Source Code for the Screen Program (page 1 of 3) IDENTIFICATION DIVISION. PROGRAM-ID. EXAMPLE-SCREEN-PROGRAM. ENVIRONMENT DIVISION. CONFIGURATION SECTION. SOURCE-COMPUTER. T16. OBJECT-COMPUTER. T16, TERMINAL IS T16-6520. SPECIAL-NAMES. F1-KEY IS F1, F2-KEY IS F2, F15-KEY IS F15, F16-KEY IS F16 SF1-KEY IS SF1, SF16-KEY IS SF16, ATTENTION IS REVERSE. DATA DIVISION. WORKING-STORAGE SECTION. 01 WS. 02 ERROR-MSG PIC X(64).
Source Code for Programs in Section 6 Source Code for Screen Program Example G-1. Source Code for the Screen Program (page 2 of 3) SCREEN SECTION. 01 EXAMPLE-SCREEN BASE SIZE 24, 80. 03 FILLER AT 1, 20 VALUE "EXAMPLE SCREEN COBOL PROGRAM". 03 FILLER AT 10, 1 VALUE "MESSAGE NUMBER :". 03 MESSAGE-NUMBER AT 10, * + 2 PIC 9, USING MESSAGE-NUMBER OF ENTRY-MSG. 03 MESSAGE-TEXT AT 12, 1 PIC X(64) FROM SERVER-RECORD OF ENTRY-REPLY. 03 FILLER AT 21, 15 VALUE "F1 - READ F16 - EXIT PROGRAM".
Source Code for Programs in Section 6 Source Code for Screen Program Example G-1. Source Code for the Screen Program (page 3 of 3) SEND-DATA. MOVE 0 TO SEND-ERROR-FLAG. SEND ENTRY-MSG TO "EXAMPLE-SERVER" REPLY CODE 0 YIELDS ENTRY-REPLY CODE 999 YIELDS ERROR-REPLY ON ERROR PERFORM SEND-ERROR. IF SEND-ERROR-FLAG = 99 DISPLAY TEMP "SEND ERROR" IN ERROR-MSG OF EXAMPLE-SCREEN ELSE PERFORM ONE OF PARA-1 PARA-2 DEPENDING ON TERMINATION-STATUS. PARA-1.
Source Code for Programs in Section 6 Source Code for Server Program Source Code for Server Program The source code for the server program (to be entered in the text file named SV) appears in Example G-2. This code is written in COBOL and can be compiled using the COBOL85 compiler. Example G-2. Source Code for the Server Program (page 1 of 2) IDENTIFICATION DIVISION. PROGRAM-ID. EXAMPLE-SERVER. ENVIRONMENT DIVISION. CONFIGURATION SECTION. SOURCE-COMPUTER. TANDEM/16. OBJECT-COMPUTER. TANDEM/16.
Source Code for Programs in Section 6 Source Code for Server Program Example G-2. Source Code for the Server Program (page 2 of 2) WORKING-STORAGE SECTION. 01 RECEIVE-FILE-STATUS. 02 STAT-1 PIC 9. 88 CLOSE-FROM-REQUESTOR VALUE 1. 02 STAT-2 PIC 9. 01 WS. 02 ERROR-CODE PIC 999 COMP. PROCEDURE DIVISION. BEGIN-COBOL-SERVER. OPEN INPUT MESSAGE-IN. OPEN OUTPUT MESSAGE-OUT SYNCDEPTH 1. PERFORM B-TRANS UNTIL CLOSE-FROM-REQUESTOR. STOP RUN. B-TRANS. READ MESSAGE-IN, AT END STOP RUN.
Source Code for Programs in Section 6 Source Code for Server Program HP NonStop Pathway/iTS System Management Manual—426748-005 G- 7
Source Code for Programs in Section 6 Source Code for Server Program HP NonStop Pathway/iTS System Management Manual—426748-005 G- 8
Index Numbers 6540 cache error… (message 3057) 13-17 A ABORT TERM command 3-9, 10-2/10-3 ACCEPT display field 9-40 ACCEPT Statement 5-22 ACCEPT statement 10-19 Actual number of parameters… (message 3005) 13-4 Actual parameter size… (message 3006) 13-4 ADD command PROGRAM 2-12/2-13 TCP 2-7 TERM 2-11 ADD PROGRAM command 2-12/2-13, 11-2 ADD TCP command 2-7, 9-2 ADD TERM command 10-4 Adding PROGRAM objects 2-12 TCP objects 2-7 TERM objects 2-11, 6-5 ALL FIELDS USED error 10-21, 11-17 ALTER command 4-15 ALTER P
C Index BACKUPCPU attribute CONTROL TCP command 9-5 Because 1-12 BEGIN-TRANSACTION statement E-4 Binder program 2-10, 9-23 BKPT-HOLD in WAIT display field 9-40 Blank characters, trailing 10-25, 11-20 Block mode terminals 6-1, 11-23 BREAK attribute SET PROGRAM command 11-16 SET TERM command 10-19 BREAK key function configuring for PROGRAM objects 2-13 configuring for TERM objects 2-12 STOP TCP command 9-42 Break key function PATHCOM commands 7-6 Buffer space determining size of 5-9 C Cache error… (message
D Index Communication protocol is not supported (message 3146) 13-32 Compaq Tandem Performance Data Collector (TPDC) See Tandem Performance Data Collector (TPDC) Configuration changing existing 4-13 displaying information about 4-3 examples 6-1 Configuration file, for PATHMON environment See PATHMON configuration file Configuration limits and defaults C-1/C-7 Configured terminal (TERM) objects See TERM objects Configuring a simple Pathway environment 6-1 applications in a PATHMON environment 2-1 limits fo
E Index DELINK queue definition of 5-2 statistics for 5-16, 5-17 DEPENDING value is… (message 3183) 13-40 DEPENDING variable value too big (message 3002) 13-3 DETAIL parameter STATS TCP command 9-36 STATUS TCP command 9-38 STATUS TERM command 10-35 Device does not support… (message 3065) 13-20 Device does not support… (message 3066) 13-20 Device doesn’t support… (message 3060) 13-18 Device requires intervention (message 3042) 13-14 Device subclass invalid (message 3168) 13-36 DEVICEINFO procedure 10-26, 1
F Index Error in backup… (message 3215) 13-46 Error in dialog mode (message 3250) 13-58 Error in non-retryable linkmon connect (message 3247) 13-56 Error in retryable linkmon error (message 3248) 13-57 Error in server class (message 3246) 13-56 Error in TCP (message 3249) 13-57 Error in XML generation (message 3149) 13-33 Error when dialog is invalid due to primary TCP failure (message 3252) 13-59 Error when dialog is not ended by server (message 3251) 13-59 Error while creating session (message 3145) 13-
G Index Function unimplemented (message 3203) 13-43 G Gateway program 1-12 GDSX product 1-17 Graphical user interfaces (GUIs) 1-15 GUARDIAN-LIB attribute SET TCP command 9-23 GUARDIAN-LIB incompatible… (message 3239) 9-31, 13-53 GUARDIAN-SWAP attribute SET TCP command 9-23 H HIGHPIN attribute SET TCP command 9-24 HIGHPIN attribute, for TCP objects 2-7 HOMETERM attribute SET TCP command 9-24 I IDS facility, for intelligent device support 1-17 IDS-related verbs 9-30 IFPRICPU attribute PRIMARY TCP command
L Index Invalid Katakana… (message 3062) 13-19 Invalid Katakana… (message 3063) 13-19 Invalid numeric item… (message 3040) 13-13 Invalid numeric item… (message 3053) 13-15 Invalid printer specification (message 3041) 13-14 Invalid pseudocode detected… (message 3001) 13-2 Invalid subscript value (message 3003) 13-3 IO protocol denied… (message 3054) 13-16 IOPROTOCOL attribute SET PROGRAM command 11-19 SET TERM command 10-23 IS-ATTACHED attribute RUN PROGRAM command 11-11 SET PROGRAM command 10-24, 11-22 IT
M Index M MAXEXTERNALTCPS attribute 8-2 Maximum number of waited run… (message 1148) 11-13 Maximum reply size exceeds… (message 3114) 13-27 MAXINPUTMSGLEN attribute 9-25 MAXINPUTMSGS attribute SET PROGRAM command 11-19 SET TCP command 9-25 SET TERM command 10-23 MAXLINKS attribute for SERVER objects 6-4 MAXPATHCOMS attribute, for PATHMON environments 6-3 MAXPATHWAYS attribute, for TCP objects 6-9, 9-25 MAXPROGRAMS attribute, for PATHMON environments 2-4, 8-2 MAXREPLY attribute, for TCP objects 2-7, 5-10,
N Index Multithreading as feature of TCP 1-12 definition of 1-12 N No room for another… (message 3208) 13-44 No room for new server class… (message 3110) 13-26 No room for new… (message 3230) 13-51 No server process linked to (message 3123) 13-30 No space for new server process (message 3119) 13-29 No unsolicited message… (message 3177) 13-38 Node names 7-7 Nondedicated devices and processes, and PROGRAM objects 2-12 Noninteractive mode 7-6 NONSTOP attribute 9-27 NonStop Kernel Open System Services proce
P Index OUT attribute INFO PROGRAM command 11-6 INFO TCP command 9-10 INFO TELL command 12-3 INFO TERM command 10-10 SHOW TCP command 9-32 SHOW TERM command 10-28 STATS TCP command 9-35 STATS TERM command 10-32 STATUS TCP command 9-38 STATUS TERM command 10-35 OUT parameter, SHOW PROGRAM command 11-24 Overlay screen displayed in… (message 3013) 13-7 OWNER attribute for PROGRAM objects 2-14 SET PROGRAM command 11-21 P Parameter reference exceeds… (message 3238) 13-53 Parameters configuration limits for C-
P Index PATHMON environment (continued) configuration file 7-7 configuring across CPUs 1-8 controlling and maintaining 4-1/4-25 distributed applications 2-3/2-4 distributing applications 2-1 restarting 6-5 shutting down 3-10 PATHMON object subtype 30 process support 11-13 PATHMON process attributes for DUMP 2-9 communicating with an external TCP 1-15/1-16 defined 1-5 displaying information about 4-1/4-3 environment, configuring and managing objects in 1-19 error and event logging 4-16 error dumps 2-9 func
Q Index PROGRAM objects (continued) as templates for device types 2-14 configuring 2-12/2-14 defined 1-5, 1-12, 2-10 defining and adding 2-12/2-14 DELETE command 4-15, 11-5 displaying information about 4-6 ERROR-ABORT 2-13 INFO command 11-6/11-7 OWNER 2-14 RESET command 11-8/11-9 RUN command 11-10/11-14 running 3-5 SECURITY 2-14 security for 2-14 SET command 11-15/11-23 SHOW command 11-24/11-25 stopping 3-7 terminal types 11-12 unsolicited messages, specifying 11-19 PROGRAM unit name invalid (message 3044
S Index RESET parameter ALTER PROGRAM command 11-3 ALTER TCP command 9-3 ALTER TERM command 10-5 STATS TCP command 9-36 STATS TERM command 10-33 RESET PROGRAM command 11-8/11-9 RESET TCP command 9-16/9-17 RESET TERM command 10-15 Response time displaying information about 5-24, 5-25 possibilities for decreased 4-3 reasons for increased 4-3 suggestions for improved determine efficient size for data transfers 5-21 reduce number of I/O operations required 5-21, 5-22 remove the TCLPROG file 4-21 set CHECK-DIR
S Index Screen programs coding 6-2 configuring TERM and PROGRAM objects for 2-10 executed by TCPs 1-12 names of 2-11 object libraries for 2-7, 2-10 source code for examples G-1 user conversion procedures for 2-10 Screen recovery executed… (message 3004) 13-3 Screen recovery, setting 9-27 Screen referenced but not… (message 3012) 13-7 Screen-image area F-1 Security for PROGRAM objects 2-13 requirements for communication between PATHMON environments 2-15 specifying for PROGRAM objects 2-14 SECURITY attribut
S Index Shutting down Pathway See also SHUTDOWN2 command Slots 9-26 SNAX High-Level Support (SNAX/HLS) 1-17 Socket error (message 3141) 13-31 Source code screen program example G-1 server program example G-5 Special register 3-11 specifies 9-38 SPI, using to monitor event messages 4-18 START command, guidelines 3-2 START TCP command 3-4, 9-33/9-34 START TERM command 3-4, 10-30/10-31 Starting objects PROGRAM objects with RUN command 3-5 TCPs 3-4 TERM objects 3-4 Starting router processes 3-1 Startup, cool
T Index SUSPEND-RESUME state 10-19 SUSP- in WAIT display field 9-40 SWAP attribute 9-29 Swap file creation error (message 3107) 13-26 Swap file I/O error (message 3109) 13-26 Swap file open error (message 3108) 13-26 Swap files 5-14, 9-23, 9-29 SWITCH command 4-16 SWITCH TCP command 9-44/9-45 SYNCID violation… (message 3201) 13-42 T TACL commands, no embedded comments in scripts 7-5 TACL scripts 7-5 Takeover by backup (message 3218) 13-48 Tandem Performance Data Collector (TPDC) 4-21 Task already using a
T Index TCP statistics (continued) POOL INFO 5-8 QUEUE INFO 5-14 SET TCP STATS command 4-10 TCP tasks 5-1/5-6 checkpointing 5-6 link management 5-2 memory management 5-4 statistics gathering 5-6 TCP trap (message 3217) 13-47 TCP user library object file 2-10 TCP2 code file 9-1 TCPs altering 4-15 as external objects 1-15 as multitasking processes 2-6 as multithreaded process 1-12 attributes for BACKUPCPU 4-16 CODEAREALEN 2-7 CPUS 2-7 DUMP 4-16 HIGHPIN 2-7 MAXPATHWAYS 6-9 MAXREPLY 2-7 MAXSERVERCLASSES 2-7,
T Index TERM objects ABORT command 10-2/10-3 ADD command 10-4 ALTER command 10-5/10-6, 10-7/?? altering 4-15 attributes for BREAK 2-12 DIAGNOSTIC 2-12 FILE 2-11 INITIAL 2-11 optional 2-12 required 2-11 TCP 2-12 TYPE 2-12 Break key for 2-12 collecting data about for problem diagnosis 4-23 configuring 2-10/2-12 defined 1-5, 1-12, 2-10 defining and adding 2-11/2-12 DELETE command 4-15, 10-9 detecting exception conditions for 4-17 displaying information about configuration 4-5 statistics 4-13 status 4-8 distr
T Index Terminals (continued) memory area 10-21, 11-17 output buffers, allocating 9-29/9-30 SCREEN COBOL programs 11-23 specifying maximum 9-19 specifying type 10-25 trailing blanks, suppressing 10-25, 11-20 type, specifying 11-16 user 2-6 Terminals, see TERM objects and PROGRAM objects TERMINAL-PRINTER special register 10-24, 11-11, 11-21 Terminating PATHCOM commands 7-6 TERMINATION-SUBSTATUS special register 10-19, 11-16 TERMPOOL attribute 2-7, 9-30 TERMPOOL, TCP storage pool description of 5-4 determin
U Index U Unilateral abort… (message 3069) 13-22 Unsolicited message rejected… (message 3241) 13-54 User conversion procedures, for screen programs 2-10 User conversion routines, collecting for TCP problem diagnosis 4-23 User terminals 2-6 V Value for MAXINPUTMSGS… (message 3240) 13-53 Variable field size would exceed… (message 3181) 13-39 Volume names 7-7 W WAIT display field 9-40 WAIT parameter, STOP TCP command 9-42 Wild Card Support PROGRAM commands 11-25 TCP commands 9-45 TERM commands 10-43 Worklo
Content Feedback First Name: __________________ Phone: _____________________ Company: ___________________ Last Name: _________________ e-mail address: ______________ (All contact information fields are required.) If you’re reporting an error or omission, is your issue: Minor: I can continue to work, but eventual resolution is requested. Major: I can continue to work, but prompt resolution is requested. Critical: I cannot continue to work without immediate response.
