HP NonStop Remote Server Call (RSC/MP) Installation and Configuration Guide Abstract This manual describes the installation, configuration, and management of RSC/MP software on a HP NonStop™ system acting as a server and on a variety of client workstations. Product Version RSC/MP R7.3 Supported Release Version Updates (RVUs) This publication supports J06.03 and all subsequent J-series RVUs, H06.03 and all subsequent H-series RVUs, and G06.
Document History Part Number Product Version Published 522358-007 RSC/MP R7.2 March 2007 522358-008 RSC/MP R7.2 October 2007 522358-009 RSC/MP R7.2 April 2008 522358-010 RSC/MP R7.2 September 2008 522358-011 RSC/MP R7.
HP NonStop Remote Server Call (RSC/MP) Installation and Configuration Guide Index Figures What’s New in This Manual ix Manual Information ix New and Changed Information Tables ix About This Manual xi Manual Contents and Organization Audience Requirements xii Related Manuals xii Notation Conventions xiii xi 1.
Contents 4. Installing RSC/MP on Windows Workstations 4.
Contents 6. Installing RSC/MP on UNIX Workstations Specifying Piccolo Logging 5-17 Creating the [NIF-nifname] Sections (for all installations) Configuration Options Reference 5-19 Pipeman Section ([PIPEMAN]) 5-19 Resolver Section ([RESOLVER]) 5-36 5-18 6.
Contents 10. IPX/SPX Network Interface Configuration TCP/IP Example PIPE.INI Configuration File 9-12 10. IPX/SPX Network Interface Configuration Prerequisites to Configuring 10-1 SPX Network Interface Addressing 10-2 Configuring Multiple NIFs 10-2 Special Considerations for Configuring NonStop NIFs Configuration Options Reference 10-3 Network Interface Section ([NIF-nifname]) 10-3 SPX Example PIPE.INI Configuration Files 10-9 10-2 11.
Contents 14.
Contents A. Migration to RSC/MP 7.2 Testing the RSC/MP Client Configuration 14-8 A. Migration to RSC/MP 7.2 Differences Between RSC/MP 7.x and Earlier Versions A-1 Features That are No Longer Supported A-2 Migration Tips A-2 Determining the Appropriate Migration Section A-3 Migrating from RSC for Piccolo 5.1 -- RSC/MP 6.x to RSC/MP 7.2 A-4 Migrating from RSC for Piccolo 5.0 to RSC/MP 7.2 A-5 Migrating from RSC 5.0 and Previous Versions to RSC/MP 7.2 A-6 Using RSC/MP 6.
Contents D. RSC/MP Scripts for Modems and Logons Working With the TDP as a Whole C-2 Working With Objects Within the TDP C-3 D.
Contents Index Index Figures Figure 1-1. Figure 5-1. Figure 5-2. Figure 5-3. Figure 13-1. Figure A-1. Figure B-1. Figure F-1. Figure F-2. Figure F-3. Figure F-4. Figure F-5. Figure F-6. Figure F-7.
What’s New in This Manual Manual Information HP NonStop Remote Server Call (RSC/MP) Installation and Configuration Guide Abstract This manual describes the installation, configuration, and management of RSC/MP software on a HP NonStop™ system acting as a server and on a variety of client workstations. Product Version RSC/MP R7.3 Supported Release Version Updates (RVUs) This publication supports J06.03 and all subsequent J-series RVUs, H06.03 and all subsequent H-series RVUs, and G06.
What’s New in This Manual • • • • • • • • • New and Changed Information Two columns in a table in the introduction for were causing confusion and were removed. These were “Hardware Platform” and “Software Environment” for RSC clients on page 1-4. A new host is provided to support HP Integrity NonStop servers. This new deliverable was added to the list of RSC/MP Components; see Versions of RSC/MP on the Host on page 1-4.
About This Manual HP NonStop Remote Server Call (RSC/MP) allows workstation-based client applications to communicate with NonStop system host-based Pathway servers and named Guardian processes. RSC/MP is made up of workstation and host components. This guide describes how to install, configure, and manage these components and also describes the RSC/MP configurable attributes which are controlled dynamically and interactively.
About This Manual • • • • • • • • • • • Audience Requirements Section 10, IPX/SPX Network Interface Configuration, describes how to configure the NIFNVL section of the PIPE.INI file for the SPX interface. Section 11, Managing the RSC/MP Transport (Piccolo), describes the PIPECP program and lists the PIPECP commands. Section 12, Configuring and Managing the RSC/MP TDP Process, discusses starting the host process, the TDP commands that you can use to configure the TDP, and TDP logging.
About This Manual • • Notation Conventions Remote Server Call (RSC/MP) Programming Manual Remote Server Call (RSC/MP) Messages Manual You can find detailed information about other NonStop system components in the appropriate HP manuals. Notation Conventions General Syntax Notation The following list summarizes the notation conventions for syntax presentation in this manual. Uppercase letters. Uppercase letters indicate keywords and reserved words; enter these items exactly as shown.
About This Manual Notation for Messages | Vertical line. A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces. For example: INSPECT { OFF | ON | SAVEABEND } … Ellipsis. An ellipsis immediately following a pair of brackets or braces indicates that you can repeat the enclosed sequence of syntax items any number of times.
About This Manual Notation for Messages Non-italic text. Non-italic letters, numbers, and punctuation indicate text that is displayed or returned exactly as shown. For example: Backup Up. Lowercase italic letters. Lowercase italic letters indicate variable items whose values are displayed or returned. For example: p-register process-name [ ] Brackets. Brackets enclose items that are sometimes, but not always, displayed.
About This Manual Change Bar Notation A percent sign precedes a number that is not in decimal notation. The % notation precedes an octal number. The %B notation precedes a binary number. The %H notation precedes a hexadecimal number. For example: %005400 %B101111 %H2F P=%p-register E=%e-register Change Bar Notation Change bars are used to indicate substantive differences between this manual and its preceding version.
1 Introduction What is RSC/MP? Remote Server Call/MP (RSC/MP) software lets you use personal computers (PCs) and workstations to communicate with Pathway servers and other NonStop processes on a NonStop system. The NonStop system can act as the host to one or many client workstations. RSC/MP permits workstations to invoke NonStop Transaction Services/MP (TS/MP) servers on NonStop servers.
Introduction Workstation Components Figure 1-1.
Introduction Host Components 2. Network interfaces (NIFs) for the various protocols (nifsock, nifnb, and so on) that are protocol-specific interfaces to the communications facility. 3. Piccolo control program (PIPECP) that provides a command line interface to control Pipeman. Host Components RSC/MP on the NonStop host system has the following components: • RSC/MP Transport (Piccolo) that contains three components: 1. PIPE manager (Pipeman) that maintains the transport connections. 2.
Introduction RSC/MP Requirements RSC/MP Requirements HP provides specific versions of RSC/MP for the NonStop host and for the clients on the platforms shown in Table 1-1 and Table 1-2. Table 1-3 shows the demonstration software requirements. For specific Software Environment requirements, review the softdoc associated with the appropriate RSC/MP component. Table 1-1.
Introduction Communications Protocols Communications Protocols Table 1-4 shows the communications protocols available for each RSC/MP product. Table 1-4. RSC/MP Communication Protocols Communication Protocol Platform TCP/IP UNIX X Win32 X Win32+TSE X Windows Vista X NetBIOS Async SPX X X X X RSC/MP Installation RSC/MP includes the following software: • • Host software — Different versions of the host software exist for Integrity NonStop servers and for NonStop S-series servers.
Introduction Testing RSC/MP Testing RSC/MP Before testing RSC/MP, you must determine that the workstation is correctly connected to the NonStop host. The method of testing connectivity depends on the type of physical connection and protocol used; for example, use a PING command for TCP/IP networks. After you install and start RSC/MP, use an RSC/MP test program (RSCTESTW for Windows, or RSCTEST for UNIX) to check the installation.
2 RSC/MP Quick Start Guide This section describes how to set up an RSC/MP host on a NonStop system and an RSC/MP Win32 client on a workstation. The Quick Start Guide describes a very basic configuration, which may be too simplistic for your requirements. If the configuration described here does not work, check the TroubleShooting section Appendix B, Installation Troubleshooting for information about analyzing problems, and refer to the rest of the manual for more detailed setup instructions.
RSC/MP Quick Start Guide Configuring RSC/MP on the Host To configure RSC/MP: 1. Use FUP to copy STARTRSC, STOPRSC, PIPETXT, PWYCFG, and TDPCFG from the ISV to your own subvolume and position to that subvolume. 2. The STARTRSC TACL macro assumes that the TDP and RSCCOM objects are in $SYSTEM.SYSTEM and that the other RSC/MP objects are in $SYSTEM.ZRSCHOST. If this arrangement is not true for your installation, edit the STARTRSC file you copied in Step 1 and make the following changes: • Change $SYSTEM.
RSC/MP Quick Start Guide Identifier Comments IN (Optional, but recommended to allow Piccolo to work properly if you exit from the terminal used to start Piccolo.) Enter an input file name. Refer to IN Option on page 5-22 for details. OUT (Optional, but recommended to allow Piccolo to work properly if you exit from the terminal used to start Piccolo.) Enter an output file name. Refer to OUT Option on page 5-29 for details.
RSC/MP Quick Start Guide Below is an example of an updated PIPEINI file. [PIPEMAN] DomainName=mycompany.com SystemName=rscmp1 in=\rscmp1.$YMIOP.#CLCI out=\rscmp1.$YMIOP.#CLCI term=\rscmp1.$YMIOP.#CLCI NifList=nifsock ;the TCP/IP network interface [NIF-nifsock] ProgramFile=nifsock ; executable for TCP/IP network interface ServicePort=5678 ; overrides default of 2787 ProcessName=$ZTC6 ; overrides default of $ZTC0 Note.
RSC/MP Quick Start Guide Client Workstation Installation and Configuration Client Workstation Installation and Configuration Follow this procedure to install the RSC/MP Win32 client on a workstation running Windows. The workstation must have least 4 MB of free disk space and have the TCP/IP network enabled. Use the PING command to check the TCP/IP configuration on the workstation. Installing the RSC/MP Win32 Client To install the RSC/MP Win32 client on a workstation, follow the directions in the README.
RSC/MP Quick Start Guide Testing the RSC/MP Installation Testing the RSC/MP Installation To test the RSC/MP installation: 1. Start the transport by using the PIPECP START command. 2. Run the RSCTESTW program. 3. When the RSC/MP Diagnostic Test Utility window appears, click on the Start button. The test program is set to use a Guardian named process and should run without making any modifications to the options. 4.
3 Installing RSC/MP on the Host The main component of the RSC/MP NonStop host software is the Transaction Delivery Process (TDP) that manages transactions between the NonStop host and client workstations. The files that are installed on the host are listed in Files Installed on the RSC/MP Host on page 3-2. For new installations or upgrades, install the host software first and then the workstation software.
Files Installed on the RSC/MP Host Installing RSC/MP on the Host 8. Obtain the name of the current EMS template files. You will need this information if you want to restore the original system templates. See the DSM Template Services Manual or the EMS Messages Manual for more information. 9. Run the command RUN TMPLMRG to merge the RSC/MP EMS templates into the system template files.
Files Installed on the RSC/MP Host Installing RSC/MP on the Host Table 3-1.
Files Installed on the RSC/MP Host Installing RSC/MP on the Host Table 3-1. Files Installed on the RSC/MP Host (page 3 of 3) RSC/MP Host Location File Name Description Required for product use? $SYSTEM.SYSTEM RSCCOM RSC/MP command program yes RSCHELP RSCCOM help text no TDP TDP object yes LIBPIPE dynamic link library yes2 SOFTDOC RSC/MP host release documentation no $genvol.SOFTDOCS 1. At least one NIF is required. 2.
4 Installing RSC/MP on Windows Workstations Three RSC/MP clients are available for Windows workstations: Win32, Win32+TSE and Windows Vista. To install RSC/MP on Windows workstations, do the following: • • • • Verify you have the minimum RSC/MP requirements on your workstation by reviewing the documentation on the RSC/MP Windows CD. Perform the installation according to the instructions provided with the CD.
Installing RSC/MP on Windows Workstations Installing the Win32+TSE Client from CD workstation and locate the RPW32EXE.EXE file on the central workstation. Either double-click on the RPW32EXE.EXE file, type RPW32EXE.EXE at a DOS prompt, or select Start->Run and enter the full path of the RPW32EXE.EXE file. c. Transfer the RPW32EXE.EXE file to the NonStop and then transfer RPW32EXE.EXE to the target workstation. The file must be transferred in BINARY mode. Log on to the workstation and locate the RPW32EXE.
Installing RSC/MP on Windows Workstations Installing the Windows Vista™ Client from CD Installing the Windows Vista™ Client from CD To install the Windows Vista™ client software from the CD: 1. Insert the RSC/MP Windows Vista Client CD into a drive attached to a Windows workstation. 2. Navigate to the WS_SW folder on the CD. 3. Select one of these installation methods: a. Install directly onto the workstation attached to the CD drive by double-clicking on the RPSETUP.MSI file. b.
Installing RSC/MP on Windows Workstations Silent Installation Silent Installation The Win32 client allows you to record an installation and silently play it back to install the RSC/MP Win32 client on many workstations without user interaction. Silent Installation Considerations The silent installation is based on a set of responses recorded to a response file during an interactive installation.
Installing RSC/MP on Windows Workstations Files Installed on the Windows Workstation Using a Response File to Perform a Silent Installation Use the rpw32exe.exe Win32 client file and the recorded response file to perform a silent installation type: rpw32exe.exe -s -a -s -f1c:\mydir\myrsc.iss Check for a log file called setup.log which has information about the status of the installation.
Installing RSC/MP on Windows Workstations Files Installed on the Windows Workstation Table 4-1. Files Installed on the Windows Workstation (page 2 of 3) Directory File Name Description Required for product use? bin rscpipe.exe RSC/MP I/O manager yes rsctest.exe RSC/MP test console application program no rsctestw.exe RSC/MP test Windows application program no rscconfig.exe RSC/MP configuration tool no rscconfig.hlp RSC/MP configuration tool help text no rscvproc.
Installing RSC/MP on Windows Workstations Running RSC/MP as a Service Table 4-1. Files Installed on the Windows Workstation (page 3 of 3) source rsctest.c RSC/MP test console application source no rsctest.mak RSC/MP test application make file for MS Visual Studio 6 no Directory File Name Description source rsctestw.c RSC/MP test Windows application source no rsctestw.def RSC/MP test Windows application definitions no rsctestw.ico RSC/MP test Windows application icon no rsctestw.
Installing RSC/MP on Windows Workstations Running RSC/MP as a Service The system requirements and capabilities of the RSC/MP Windows clients vary as described below.
Installing RSC/MP on Windows Workstations Running the RSC/MP Win32 Client as a Service Running the RSC/MP Win32 Client as a Service The Win32 client is intended for use by traditional, single-user workstation applications. The RSC/MP service mechanism is a convenience feature which provides a method by which the necessary RSC/MP processes can be started automatically before they are needed by the RSC/MP application.
Installing RSC/MP on Windows Workstations Changing the RSC Service Startup Mode Changing the RSC Service Startup Mode If you install RSC/MP to run as a service, the installation program sets the RSC Service and Piccolo Service startup modes to Automatic in order to have Piccolo Service and RSC Service start automatically at system boot time.
Installing RSC/MP on Windows Workstations Using RSC/MP from Another Service (Win32+TSE Client Only) To change the startup mode on Windows NT: 1. Open the Control Panel. 2. From the Control Panel, open Services. 3. Select RSC from the Services list. 4. Click on the Startup button. 5. Select either Automatic, Manual, or Disabled in the Service dialog. 6. Close the dialog box. 7. Select Piccolo from the Services list. 8. Click on the Startup button. 9.
Installing RSC/MP on Windows Workstations Installing RSC/MP as a Service Installing RSC/MP as a Service If you installed RSC/MP and elected not to run RSC/MP as a service and later decide that you do need RSC/MP as a service, you can install the RSC Service program by following these steps: 1. Locate the rscserv.exe file (located in the bin subdirectory under the main directory into which you installed RSC/MP). 2. From a command prompt, invoke the rscserv.
Installing RSC/MP on Windows Workstations Viewing Error Messages Viewing Error Messages In general, RSC/MP error messages are reported using return codes from the RSC/MP API. Additional information in the form of log messages are written to the RSC/MP and Piccolo log files as described in Specifying Piccolo Logging on page 5-17. When RSC/MP runs as a service, however, fatal startup errors are written to the system event logs to assist in troubleshooting unattended startup failures.
Installing RSC/MP on Windows Workstations Running RSC/MP From a File Server When sharing configuration files stored on the file server, use the automatic SystemName generation function and follow the rules by which the Pipeman process and the Piccolo API locate the Piccolo configuration file (see RSC/MP components use the following search sequence to locate Piccolo configuration files: on page 5-6).
5 Configuring the RSC/MP Transport (Piccolo) The network transport mechanism that RSC/MP uses is called Piccolo. RSC/MP uses Piccolo both on the NonStop host and on the client workstation. Although the RSC/MP functional components are different at both ends—TDP runs on the host, RSC/MP applications and RSCPIPE run on the workstation—Piccolo itself is almost the same at both ends. This section describes how to configure the RSC/MP transport (Piccolo) both on the NonStop host and the client workstation.
Configuring the RSC/MP Transport (Piccolo) Backup Process section is usually not required; see the Resolver section described in Configuration Options Reference on page 5-19 to help determine if you need the Resolver section. 5. Start the Pipeman and NIF processes using the PIPECP START command. See Automatic Startup of Piccolo on page 5-13 for information about automatically starting the subsystem. See PIPECP Commands on page 11-2 for information about the PIPECP START command. Note.
Overview of Piccolo Configuring the RSC/MP Transport (Piccolo) Overview of Piccolo Piccolo consists of a single manager process (Pipeman) and one or more network interface processes (NIFSOCK, NIFNB, NIFASY, and so on). These processes running together provide the communications mechanism that connects the RSC/MP application running on the workstation to the TDP running on the NonStop host, through RSCPIPE (which also runs on the workstation).
Configuring the RSC/MP Transport (Piccolo) Configuring Piccolo (general instructions) On systems that use a single Pipeman process, you should isolate the TDP, the RSC/MP client application, and the RSCPIPE process from the Piccolo configuration file on their respective systems. However, on systems requiring multiple concurrent instances of Piccolo, these processes (through the Piccolo API) must be able to access the configuration file to find the correct Pipeman process.
Configuring the RSC/MP Transport (Piccolo) Configuring a Single Instance of Piccolo (for most installations) Configuring a Single Instance of Piccolo (for most installations) By default, the Pipeman and NIF processes search for a configuration file named PIPEINI (on the NonStop host) or PIPE.INI (on all workstation platforms) located in the same subvolume or directory in which Pipeman is started.
Configuring the RSC/MP Transport (Piccolo) • • • Configuring Multiple Instances of Piccolo (for advanced installations) On the NonStop host, the IPC key is the process name of the Pipeman process — for example, $PIPE1, $PIPE2, and so on. The default IPC key is $PIPE. On UNIX workstations, the IPC key is the full name of an existing file or directory that will not change while Pipeman is running — for example, /usr/users/rsc_production, /usr/users/rsc_debug, /usr/users/rsc_run/pipe.ini, and so on.
Configuring the RSC/MP Transport (Piccolo) Managing Multiple Instances of Piccolo (for advanced installations) Managing Multiple Instances of Piccolo (for advanced installations) For platforms that support instances of Piccolo, changing the configuration file name allows for convenient management of the multiple configurations. For example, you can name each configuration differently, such as PIPEINI1, PIPEINI2, and so on.
Managing Multiple Instances of Piccolo (for advanced installations) Configuring the RSC/MP Transport (Piccolo) Figure 5-3. Multiple Piccolo Environments NonStop Host Workstation Production Environment Production Environment RSC/MP application TDP PIPEMAN NIF PIPEMAN RSCPIPE NIF PIPEINI PIPE.INI Development Environment Development Environment PARAM PIPEINI $USER.RSCDEV.PIPEINID setenv PIPEINI /user/users/pipe.ini.
Configuring the RSC/MP Transport (Piccolo) • Combining Piccolo and RSC/MP Configuration Settings (workstations only) To get useful log information from multiple Piccolo instances, the Pipeman processes should not compete for a common log file name. Be sure that the LogFileName option setting is unique for each Piccolo instance.
Configuring the RSC/MP Transport (Piccolo) Configuring Using the RSC/MP Configuration Wizard Configuring Using the RSC/MP Configuration Wizard For Windows workstations, you can configure the NIFs by using the RSC/MP Configuration Wizard program. Click on the Configure RSC/MP icon and the screens will guide you through the configuration steps.
Configuring the RSC/MP Transport (Piccolo) Creating the Configuration File (for all installations) running) and at least one network interface. This sample configuration file is for a workstation myworkstation.mycompany.com that will connect to NonStop hosts using TCP/IP service port 5001: [PIPEMAN] SystemName=myworkstation DomainName=mycompany.
Configuring the RSC/MP Transport (Piccolo) Creating the [PIPEMAN] Section (for all installations) Creating the [PIPEMAN] Section (for all installations) System Names and Addresses Every instance of Pipeman in a network is considered a Piccolo system. Each Piccolo system must have a unique system address. The system address of a Pipeman instance is derived by Piccolo by combining the system name and domain name in its configuration file.
Configuring the RSC/MP Transport (Piccolo) Automatic Startup of Piccolo Automatic Startup of Piccolo Piccolo must be running in order for RSC/MP to be usable. Piccolo can be started directly by using the PIPECP START command, or it can be configured to start automatically when needed by RSC/MP. To use automatic startup, set the AutoStart entry in the [PIPEMAN] section to 1: AutoStart=1 Automatic startup can be used on the host, the workstation, or both. If used on the host, the TDP starts Piccolo.
Configuring the RSC/MP Transport (Piccolo) Large-Message Support Starting with RSC/MP 7.0, the maximum message size has been increased from 31000 bytes to 56000 bytes for RscWrite and RscWriteRead to a named server. Where applications require the new expanded maximum message size, Piccolo must be explicitly configured on both the host and the workstation to provide large-message support.
Configuring the RSC/MP Transport (Piccolo) Optional Entries The PIPECP STATUS LINKS command indicates which links are capable of processing large messages. Within the “ver” (version) column, a three-digit number specifies the version of the Piccolo software that is running at the remote end of the link. When executed on the host, PIPECP STATUS LINKS shows client version information. When executed on the client, PIPECP STATUS LINKS shows host version information.
Configuring the RSC/MP Transport (Piccolo) Creating the [RESOLVER] Section (optional, for workstations only) Each entry in the [RESOLVER] section gives the detailed information that a network interface (NIF) needs to reach the remote host. Several alternative methods can be supplied for a given system; in this case, the methods will be attempted in order from left to right.
Configuring the RSC/MP Transport (Piccolo) Specifying Piccolo Logging Specifying Piccolo Logging All Piccolo log messages are written to a text file by the Pipeman process. The location, size, and detail level of the logs can be specified using the LogFileName, LogFileEntries, and LogLevel options in the [PIPEMAN] section of the configuration file. The LogFileName option specifies the name of the primary log file.
Configuring the RSC/MP Transport (Piccolo) Creating the [NIF-nifname] Sections (for all installations) Creating the [NIF-nifname] Sections (for all installations) Each network interface (NIF) must have its own configuration file section. The protocolspecific content of these sections is described in each NIF-specific section later in this guide.
Configuring the RSC/MP Transport (Piccolo) Configuration Options Reference Configuration Options Reference The following options are available for configuring the Pipeman section in the PIPE.INI file. Pipeman Section ([PIPEMAN]) The Pipeman section contains configuration options that control the operation of the Pipeman process.
Configuring the RSC/MP Transport (Piccolo) Pipeman Section ([PIPEMAN]) AutoStartTimeout Option The AutoStartTimeout option works with the AutoStart option. When AutoStart is enabled (set to 1), AutoStartTimeout gives the number of seconds to allow for startup of the PIPEMAN process. The default value should be suitable for most installations.
Configuring the RSC/MP Transport (Piccolo) Pipeman Section ([PIPEMAN]) CPU Option The CPU option defines the number of the CPU on which the process is to run. CPU=number number An integer from 0 through 15. Required: No. Default: For Pipeman sections: The CPU on which the PIPECP is running that starts PIPEMAN. For NIF sections: The CPU in which the Pipeman process is running. Platforms: NonStop Example: CPU=1 DomainName Option The DomainName option defines the addressing domain of the local system.
Configuring the RSC/MP Transport (Piccolo) Pipeman Section ([PIPEMAN]) 2. In this example, the name is too long; the system address is more than 46 characters: westwing.building02.campus04.widgit.company.com EnableLargeMessages Option The EnableLargeMessages option enables support for large messages (greater than 31000 bytes, up to 56000 bytes). Ability to use large messages is subject to the system and configuration constraints described in Large-Message Support on page 5-13.
Configuring the RSC/MP Transport (Piccolo) Pipeman Section ([PIPEMAN]) IpcKey Option The IpcKey option defines a unique Interprocess Communications (IPC) path that will be used to communicate with the Pipeman process. Only use this option if you intend to run multiple, concurrent instances of Piccolo. IpcKey=processname (for NonStop) IpcKey=filename (for UNIX) IpcKey=name (for Windows) processname A valid process name that does not already exist when Pipeman is started.
Configuring the RSC/MP Transport (Piccolo) Pipeman Section ([PIPEMAN]) KeepAliveInterval Option The KeepAliveInterval option defines (in seconds) how long before a keepalive packet is generated for an idle pipe. Keepalives are used to detect loss of a network connection that might otherwise go unnoticed due to absence of RSC/MP message traffic. KeepAliveInterval=number number The number of seconds, 1 through 65535; or 0 to disable Piccolo keepalives.
Configuring the RSC/MP Transport (Piccolo) Pipeman Section ([PIPEMAN]) LogFileName Option The LogFileName option defines the name and location of the Piccolo log files. Any subvolume (for NonStop) or directory (for workstations) can be supplied. Log files are rolled over when they reach the limit specified in the LogFileEntries option, with the last 10 log files being preserved.
Pipeman Section ([PIPEMAN]) Configuring the RSC/MP Transport (Piccolo) LogLevel Option The LogLevel option defines the level of detail that is written to the Piccolo log file. Note. Setting the log level to 8 or greater can have a serious impact on performance and is not recommended, except as specifically directed by HP Global Customer Support Center (GCSC)). Piccolo logs each message to the log file with a specific number representing severity or classification.
Configuring the RSC/MP Transport (Piccolo) Pipeman Section ([PIPEMAN]) Examples: 1. This example causes critical level messages to be logged: LogLevel=0 2. This example causes critical, error, warning, and informational messages to be logged: LogLevel=7 (Note that 7 is the sum of 0, 1, 2, and 4, which represent critical, error, warning and informational messages, respectively.) Note. If the LogFileName option is set, logging of critical errors cannot be suppressed.
Configuring the RSC/MP Transport (Piccolo) Pipeman Section ([PIPEMAN]) NifList Option The NifList option contains a list of network interface symbolic names, separated by commas, that should be started automatically when Pipeman starts. For each NIF name listed, there must be a corresponding network interface section [NIF-nifname] in the Piccolo configuration file. NIF sections not included in a NifList must be started manually using the PIPECP START nifname command to be operable.
Configuring the RSC/MP Transport (Piccolo) Pipeman Section ([PIPEMAN]) Example: If the configuration file contains this NifList option in the Pipeman section: NifList=mytcpip, mynetbios, mynifsamp Then the following sections must also exist in the file: [NIF-mytcpip] [NIF-mynetbios] [NIF-mynifsamp] OUT Option The OUT option specifies the OUT file for the Pipeman process. OUT=filename filename A valid file name. Required: No.
Configuring the RSC/MP Transport (Piccolo) Pipeman Section ([PIPEMAN]) PRI Option The PRI option specifies the execution priority of the Pipeman process. A process that has a higher number will run first. PRI=priority priority A valid integer in the range 1 through 199. Required: No. Default: For Pipeman sections: 1 less than the priority of the PIPECP that starts Pipeman. For NIF sections: The priority of the Pipeman process.
Configuring the RSC/MP Transport (Piccolo) Pipeman Section ([PIPEMAN]) SilentWindowsShutdown Option The SilentWindowsShutdown option defines whether Pipeman will check for running Piccolo clients when Pipeman is stopping as part of an operating system shutdown. This option is effective only under the following conditions: • • • Pipeman is running on the Windows operating system Piccolo is not running as a service Pipeman is stopping as the result of an operating system shut down.
Configuring the RSC/MP Transport (Piccolo) Pipeman Section ([PIPEMAN]) ShowIcon Option The ShowIcon option defines whether Pipeman and all NIF processes should show or hide their icons while they are running. When shown, the icons appear in the system task bar as minimized windows; these cannot be restored or maximized. If RSC/MP is installed as a service, the icons will appear only on the console, and only when the RSC/MP Piccolo service is configured to “Allow Service to Interact with Desktop”.
Configuring the RSC/MP Transport (Piccolo) Pipeman Section ([PIPEMAN]) SystemName Option This option defines the name of the local system. SystemName=string string The system name and domain name (see DomainName Option on page 5-21) are concatenated to form the system address, which can be no more than 46 characters in length. The SystemName may contain only the following characters: A through Z, a through z, 0 through 9, and hyphen (-). The name is not case sensitive and must be unique within the domain.
Configuring the RSC/MP Transport (Piccolo) Pipeman Section ([PIPEMAN]) T1Interval Option The T1Interval option defines (in seconds) the maximum amount of time Pipeman will wait before re-sending a packet that has not been acknowledged. T1 and T2 are calculated by Pipeman based on the throughput rate of the messages. Note. Do not alter this value unless instructed to do so by HP Global Customer Support Center (GCSC).
Configuring the RSC/MP Transport (Piccolo) Default: 3 Platforms: All Pipeman Section ([PIPEMAN]) Example: T1Retries=10 T2Interval Option The T2Interval option defines the maximum number of seconds before a packet will be explicitly acknowledged by Pipeman. T1 and T2 are calculated by Pipeman based on the throughput rate of the messages. Note. Do not alter this value unless instructed to do so by HP Global Customer Support Center (GCSC).
Configuring the RSC/MP Transport (Piccolo) Platforms: Resolver Section ([RESOLVER]) NonStop Example: Term=$home Resolver Section ([RESOLVER]) The Resolver section can be included in the PIPE.INI file to map (or resolve) system addresses to corresponding extended addresses. Extended addresses consist of network address tags that are understood by Piccolo and user-defined tags. These tags are preceded by the section name [RESOLVER] and are described in Appendix E, Resolver Reference Tags.
6 Installing RSC/MP on UNIX Workstations RSC/MP runs on a variety of UNIX platforms, including the following: • • • • • • • • RS6000 with AIX HP-9000 with HP-UX HP-9000 with HP-UX Integrity HP-Integrity (Itanium) IBM-compatible PC with SCO UnixWare Sun SPARC with Sun Solaris IBM-compatible PC with Sun Solaris IBM-compatible PC with SUSE Linux To install RSC/MP on UNIX workstations, do the following: • • • • • Verify you have the minimum RSC/MP requirements on your workstation by reviewing the documenta
Installing RSC/MP on UNIX Workstations Installation from the CD Table 6-1. Shared Library Names Platform Shared Library Names Shared Library Environment Variable Linux libpipe.so and librsc.so LD_LIBRARY_PATH SCO UNIX libpipe.so and librsc.so LD_LIBRARY_PATH Solaris libpipe.so.1 (and libpipe.so, a symbolic link to libpipe.so.1) LD_LIBRARY_PATH librsc.so.1 (and librsc.so, a symbolic link to librsc.so.
Installing RSC/MP on UNIX Workstations Installing on AIX From a CD Installing on AIX From a CD 1. Insert the RSC/MP AIX Client CD into a drive attached to a Windows workstation. 2. Navigate to the WS_SW folder on the RSC/MP Client CD. 3. Locate the file RPAIXEXE.TAR. 4. Select one of these installation methods: • Transfer the TAR file to the UNIX workstation. The file must be transferred in BINARY mode.
Installing RSC/MP on UNIX Workstations Installing on HP-UX From a CD Installing on HP-UX From a CD Note. This version of RSC/MP supports multithreaded RSC/MP applications on HP-UX. Depending on the number of threads required by the application, it might be necessary to adjust the HP-UX system configuration in order to run the application.
Installing RSC/MP on UNIX Workstations Installing on Linux From A CD Installing on Linux From A CD 1. Insert the RSC/MP Linux Client CD into a drive attached to a Windows workstation. 2. Navigate to the WS_SW folder on the RSC/MP Client CD. 3. Locate the file RPLINEXE.TAR. 4. Select one of these installation methods: • Transfer the TAR file to the UNIX workstation. The file must be transferred in BINARY mode.
Installing RSC/MP on UNIX Workstations Installing on SCO UnixWare From A CD Installing on SCO UnixWare From A CD 1. Insert the RSC/MP SCO Client CD into a drive attached to a Windows workstation. 2. Navigate to the WS_SW folder on the RSC/MP Client CD. 3. Locate the file RPUXWEXE.TAR. 4. Select one of these installation methods: • Transfer the TAR file to the UNIX workstation. The file must be transferred in BINARY mode.
Installing RSC/MP on UNIX Workstations Installing on Solaris From A CD Installing on Solaris From A CD Note. The current version of RSC/MP supports multithreaded RSC/MP applications on Solaris. Depending on the number of threads required by the application, it might be necessary to adjust the Solaris system configuration in order to run the application.
Installing RSC/MP on UNIX Workstations Files Installed on the UNIX Workstation Files Installed on the UNIX Workstation The files installed on a workstation vary with the platform. The following table lists files using Solaris as an example. Shared library filenames vary according to system convention. Table 6-2. Files Installed on the UNIX Workstation Directory samples File Name Description Required for product use? libpipe.so Piccolo shared library yes1 librsc.
Installing RSC/MP on UNIX Workstations IPC Resource Requirements IPC Resource Requirements RSC/MP makes use of certain System V IPC resources in transferring messages between RSC/MP client processes and the PIPEMAN process and between PIPEMAN and NIF processes. In order for RSC/MP to operate correctly, certain system parameters may need to be adjusted to reflect some absolute and usage-based IPC requirements.
Installing RSC/MP on UNIX Workstations System V Message Queues System V Message Queues RSC/MP uses message queues with messages of exactly 4 bytes in size. • MSGMAX (maximum size of a message) must be greater than or equal to 4. The PIPEMAN and NIF processes use one message queue each. • MSGMNI (number of unique message queue identifiers) must be greater than the total number of PIPEMAN and NIF processes that will run concurrently, plus the requirements of all other software running on the system.
7 Asynchronous Network Interface Configuration This section shows how to configure the asynchronous Network Interface (NIF) by: • • Setting up addressing. Using the options in the PIPE.INI file. The asynchronous network interface (NIFASY) allows two Piccolo systems to communicate with each other over an asynchronous connection. The connection type can be switched or dedicated using a null modem, dumb modem, or smart modem.
Asynchronous Network Interface Configuration Asynchronous Network Interface Addressing See Configuration Options Reference on page 7-2 for more information about the asynchronous network options that are used in the NIF-nifname section in the PIPE.INI file. Asynchronous Network Interface Addressing You can use the Resolver section to map system addresses to network addresses. The asynchronous network interface allows each tag to be specified only once.
Asynchronous Network Interface Configuration Network Interface Section ([NIF-nifname]) AnswerScript Option The AnswerScript option specifies the file name of an answer script that will be used to control a smart modem when answering a call. This option is only effective when the LinkType option is SWITCHED, the LinkControl option is SCRIPT, and the CallDirection option is IN or BOTH. Note.
Asynchronous Network Interface Configuration Network Interface Section ([NIF-nifname]) CallDirection Option The CallDirection option defines whether or not the NIFASY should only answer calls, make outgoing calls, or both. Note that this option is ignored for dedicated links. There are three options: • • • IN Incoming calls are accepted. OUT Outgoing calls can be made. BOTH Incoming calls are accepted and outgoing calls can be made.
Asynchronous Network Interface Configuration Network Interface Section ([NIF-nifname]) CallScript Option The CallScript option specifies the file name of a call script that will be used to control a smart modem when originating a call. This option is only effective when the LinkType option is SWITCHED, the LinkControl option is SCRIPT, and the CallDirection option is OUT or BOTH. The name specified for this option is the default call script for the network interface.
Asynchronous Network Interface Configuration Network Interface Section ([NIF-nifname]) ComDevice Option The ComDevice option defines the communications device or port that will be dedicated to the network interface. Note that the network interface opens this device for its exclusive use. While the network interface is running, the device is not available for use by other applications. This option may be overridden by adding an entry in the Resolver section for the destination system.
Asynchronous Network Interface Configuration Network Interface Section ([NIF-nifname]) ComOptions Option The ComOptions option defines the line attributes that will be set for the ComDevice. This option may be overridden by adding an entry in the Resolver section for the destination system. See Appendix E, Resolver Reference Tags, for more information about the tags that can be used in the Resolver section. The value is a string in the following format: ComOptions=speed.databits.stopbits.
Asynchronous Network Interface Configuration Network Interface Section ([NIF-nifname]) CPU Option The CPU option specifies the number of the processor where the process is to run. CPU=number number An integer in the range from 0 through 15. Required: No Default: The CPU in which the Pipeman process is running.
Asynchronous Network Interface Configuration Network Interface Section ([NIF-nifname]) FlowControl Option The FlowControl option defines the flow control method to be used on the link. There are three options: • • • Hardware control Use RTS/CTS flow control; your hardware must be set up for flow Software Use XON/XOFF flow control None Do not use flow control FlowControl=HARDWARE | SOFTWARE | NONE Required: No Default: NONE Platforms: All Note.
Asynchronous Network Interface Configuration Network Interface Section ([NIF-nifname]) IN Option The IN option specifies the IN file for the NIF process. IN=filename filename A valid file name. DEFINES are not supported. Required: No. Default: The IN file of the Pipeman process. Platforms: NonStop Example: IN=$CONSOLE LinkControl Option The LinkControl option defines how the network interface will determine when the asynchronous connection has been established.
Asynchronous Network Interface Configuration Network Interface Section ([NIF-nifname]) LinkRequestRetriesMax Option The LinkRequestRetriesMax option specifies the maximum number of times that Pipeman will attempt to establish a logical link through the NIF to a host before either attempting to use the next NIF in the NifList, or returning a PIPERC_PATH_FAILURE error. LinkRequestRetriesMax=number number An integer in the range of 1 through 65535.
Asynchronous Network Interface Configuration Network Interface Section ([NIF-nifname]) LinkType Option The LinkType option defines whether the asynchronous connection to the remote system is switched or dedicated. Null modem, leased line, and X.25 PVCs are generally considered dedicated connections. Dialup modem and X.25 SVCs are generally considered switched connections. LinkType=SWITCHED | DEDICATED Required: No Default: Dedicated Platforms: All Examples: 1. LinkType=switched 2.
Asynchronous Network Interface Configuration Network Interface Section ([NIF-nifname]) PRI Option The PRI option specifies the execution priority of the NIF process. PRI=priority priority An integer in the range 1 through 199. Required: No. Default: The priority of the NIF process. Platforms: NonStop Example: PRI=128 Priority Option The Priority option specifies the order in which this NIF will be used (if multiple NIFs are configured) when making a connection to a remote node.
Asynchronous Network Interface Configuration Network Interface Section ([NIF-nifname]) ProgramFile Option The ProgramFile option defines the program file that should be run for this network interface. This option is required. For the asynchronous network interface, this value must be NIFASY.
Asynchronous Network Interface Configuration Network Interface Section ([NIF-nifname]) SendTransparent Option The SendTransparent option defines a list of control characters that should be escaped for transparent transmission across the link. Certain characters are always escaped—5 (ENQ), 13 (carriage return), 125 (PPP escape), 126 (PPP flag) and 127 (delete). Others are automatically escaped when needed—for example, 17 (XON) and 19 (XOFF) when using XON/XOFF flow control.
Asynchronous Network Interface Configuration Platforms: Network Interface Section ([NIF-nifname]) NonStop Example: Term=$home Throughput Option The Throughput option provides a reference value that a NIF will use in estimating transmission times for messages it sends via an asynchronous connection.
Asynchronous Network Interface Configuration Asynchronous Example PIPE.INI Configuration File Asynchronous Example PIPE.INI Configuration File [Pipeman] DomainName=mycompany.com SystemName=thissystem NifList=nifdial [NIF-nifdial] ProgramFile=nifasy ComDevice=com2 ComOptions=19200.8.1.n FlowControl=Hardware LinkControl=Script LinkType=Switched CallScript=c:\rsc\bin\atcall.scr CallDirection=OUT [Resolver] boston.corsof.com=comdevice:com2, comoptions:19200.8.1.n, $phone:555-2222 accounting.corsof.
Asynchronous Network Interface Configuration Asynchronous Example PIPE.
8 NetBIOS Network Interface Configuration This section shows how to configure the NetBIOS Network Interface (NIF) by: • • Setting up addressing. Using the options in the PIPE.INI file. The NetBIOS network interface (NIFNB) is used to transmit RSC/MP data over a NetBIOS network. Each host and workstation must be configured with its own Pipeman process and network interface.
NetBIOS Network Interface Configuration Configuration Options Reference ARP uses (and requires) the NetBIOS broadcast feature. If your network configuration supports NetBIOS broadcasting, then you can use ARP. With ARP, all hosts listen on a common group name (by default, ZPIPEARP). To connect with a host, the workstation broadcasts a message containing the desired host’s full system name (as defined in the host Piccolo’s [Pipeman] section) the SystemName and DomainName options.
NetBIOS Network Interface Configuration Network Interface Section ([NIF-nifname]) AdapterNumber Option The AdapterNumber option defines the network adapter number used by the NIFNB. Although there may only be one physical adapter in your system, your NetBIOS interface may use a logical adapter number to indicate the network protocol that the NetBIOS interface should use. Make certain you are using the correct logical adapter number. See your System Administrator for the number of the logical adapter.
NetBIOS Network Interface Configuration Network Interface Section ([NIF-nifname]) ArpTimeout Option Note. Do not alter this value unless instructed to do so by HP Global Customer Support Center (GCSC). The ArpTimeout option defines the timeout of broadcast name resolution retries. This option is only used with installations that use ARP. ArpTimeout=number number A number in the range from 0 through 65535.
NetBIOS Network Interface Configuration Network Interface Section ([NIF-nifname]) DatagramQueue Option The DatagramQueue option defines the maximum number of simultaneous NetBIOS datagram-receives that the NIF will post to the network adapter. The NIF uses datagrams to resolve remote system addresses. Increasing this value increases the use of NCB resources on the network adapter. Decreasing this value may reduce address resolution speed. This option is only used with installations that use ARP.
NetBIOS Network Interface Configuration Network Interface Section ([NIF-nifname]) IdleDisconnect Option The IdleDisconnect option defines the number of seconds that a physical network connection will be maintained when no pipes are using the logical connection. IdleDisconnect=number number The number of seconds in the range from 5 through 65535. Required: No Default: 60 seconds Platforms: All Example: IdleDisconnect=180 IN Option The IN option defines the IN file for the NIF process.
NetBIOS Network Interface Configuration Network Interface Section ([NIF-nifname]) LinkRequestRetriesMax Option The LinkRequestRetriesMax option defines the maximum number of times that Pipeman will attempt to establish a logical link through the NIF to a host before either attempting to use the next NIF in the NifList, or returning a PIPERC_PATH_FAILURE error. LinkRequestRetriesMax=number number An integer in the range from 1 through 65535.
NetBIOS Network Interface Configuration Network Interface Section ([NIF-nifname]) ListenQueue Option The ListenQueue option defines the maximum number of NetBIOS LISTEN NCBs that the network interface posts to the network adapter. Increasing this value increases the use of NCB resources on the network adapter. Decreasing this value may reduce the speed at which connections are established. ListenQueue=number number A number in the range from 1 through 8.
NetBIOS Network Interface Configuration Network Interface Section ([NIF-nifname]) MultilanLine Option The MultilanLine option defines the device name of the LAN controller that the NIF uses, or the NBT or NBX process name to be used. MultilanLine=name name The process name of the LAN communications subsystem on the local system that supports the Multilan WSPTP interface. See your Multilan documentation for more information. When running over NBT or NBX, supply the NBT or NBX process name.
NetBIOS Network Interface Configuration Network Interface Section ([NIF-nifname]) NBName Option This option is for installations that are NOT using ARP. The NBName option defines the NetBIOS session name used for incoming connections. An NBName can be specified in the Resolver section for outgoing connections. NBName=name name A valid NetBIOS session name. Required: Yes, when not using ARP; otherwise, not required. Default: Internally generated.
NetBIOS Network Interface Configuration Network Interface Section ([NIF-nifname]) OUT Option The OUT option defines the OUT file for the NIF process. OUT=filename filename A valid file name or process name; DEFINES are not supported. Required: No Default: The OUT file of the Pipeman process. Platforms: NonStop Example: OUT=$CONSOLE PRI Option The PRI option defines the execution priority of the NIF process. PRI=priority priority An integer in the range from 1 through 199.
NetBIOS Network Interface Configuration Network Interface Section ([NIF-nifname]) Priority Option The Priority option defines the order in which this NIF will be used (if multiple NIFs are configured) when making a connection to a remote node. In attempting to reach a host, Pipeman will first try using the NIF having the lowest priority value, if that fails, then the next higher priority NIF will be tried, and so on. Priority=number number A integer in the range from 0 through 65535.
NetBIOS Network Interface Configuration Network Interface Section ([NIF-nifname]) ReceiveQueue Option The ReceiveQueue option defines the maximum number of NetBIOS receive requests that are posted to the network adapter. Increasing this value increases the use of NCB resources on the network adapter. Decreasing this value may reduce connection throughput. Note that if this value is set to greater than one, the NetworkBufferSize option is automatically set to 32000.
NetBIOS Network Interface Configuration NetBIOS Example PIPE.INI and PIPEINI Configuration Files NetBIOS Example PIPE.INI and PIPEINI Configuration Files Example 1: Using NIFNB ARP (Multilan on the NonStop host). On the host (in the PIPEINI file): [Pipeman] DomainName=mycompany.com SystemName=myhost ; workstation will reach us at this name ; using ARP mechanism . . . [NIF-mynif] ProgramFile=nifnb MultilanGateway=#GW1 MultilanLine=$LANA On the workstation (in the PIPE.INI file): . . .
NetBIOS Network Interface Configuration NetBIOS Example PIPE.INI and PIPEINI Configuration Files On the workstation: . . . [NIF-mynif] ProgramFile=nifnb AdapterNumber=1 . . . [Resolver] myhost.mycompany.
NetBIOS Network Interface Configuration NetBIOS Example PIPE.
9 TCP/IP Network Interface Configuration This section shows how to configure the TCP/IP Network Interface (NIF) by: • • • Setting up addressing. Selecting the TCP/IP port. Using the options in the PIPE.INI file. The TCP/IP network interface (NIFSOCK) transmits data between two Pipeman processes on a TCP/IP network. Each system must be configured with its own Pipeman process and NIF.
TCP/IP Network Interface Addressing TCP/IP Network Interface Configuration TCP/IP Network Interface Addressing You can use the Resolver section to map system addresses to network addresses. The TCP/IP network interface allows up to 16 IP address tags to be specified in a single extended address. The Resolver section recognizes the formats described in the following table. Table 9-1. Resolver Formats IPv4 ip:* ip:”*” Uses the IPv4 address resolved through DNS and the service port of the local NIF.
TCP/IP Network Interface Configuration • • Selecting the TCP/IP Port Second collecting all addresses specified with the ip: tag, in order from left to right. During either the first or second collection, a wildcard (ipv6:* or ip:*) will cause IP address collection to stop and all previously collected addresses to be discarded. The wildcard thus overides any and all other IP addresses specified in the extended address.
TCP/IP Network Interface Configuration Network Interface Section ([NIF-nifname]) Required: No Default: The CPU on which the Pipeman process is running. Platforms: NonStop Example: CPU=3 EnableProtocolKeepAlives Option The EnableProtocolKeepAlives option determines whether the protocol-specific keepalive will be enabled by Piccolo. This option increases network traffic if enabled. EnableProtocolKeepAlives=enabled enabled YES to enable, NO to disable.
TCP/IP Network Interface Configuration Network Interface Section ([NIF-nifname]) IdleDisconnect Option The IdleDisconnect option defines the number of seconds that a physical network connection will be maintained when no pipes are using the logical connection. IdleDisconnect=number number A valid number of seconds in the range 5 through 65535. Required: No Default: 60 seconds. Platforms: All Example: IdleDisconnect=180 IN Option The IN option defines the IN file for the NIF process.
TCP/IP Network Interface Configuration Network Interface Section ([NIF-nifname]) LinkRequestRetriesMax Option The LinkRequestRetriesMax option defines the maximum number of times that Pipeman will attempt to establish a logical link through the NIF to a host before either attempting to use the next NIF in the NifList (if there is one), or returning a PIPERC_PATH_FAILURE error (if there isn’t one). LinkRequestRetriesMax=number number An integer in the range of 1 through 65535.
TCP/IP Network Interface Configuration Network Interface Section ([NIF-nifname]) NetworkBufferSize Option The NetworkBufferSize option defines the size of the send and receive buffer for each network connection. This value determines how much data the TCP/IP subsystem will buffer on behalf of the network interface before suspending data transfer. The default value is appropriate for all applications.
TCP/IP Network Interface Configuration Network Interface Section ([NIF-nifname]) PRI Option The PRI option defines the execution priority of the NIF process. PRI=priority priority A valid integer in the range 1 through 199. Required: No Default: The priority of the Pipeman process. Platforms: NonStop Example: PRI=128 Priority Option The Priority option defines the order in which this NIF will be used (if multiple NIFs are configured) when making an outbound connection to a remote node.
TCP/IP Network Interface Configuration Network Interface Section ([NIF-nifname]) ProcessName Option The ProcessName option defines the name of the TCP/IP process to use on NonStop systems. The value must be the process name of a properly configured TCP/IP process on the NonStop system. ProcessName=name name A valid name of a running, properly configured TCP/IP process. Required: No Default: $ZTC0 Platforms: NonStop Example: ProcessName=$ZTC1 ProgramFile Option This option is required.
Network Interface Section ([NIF-nifname]) TCP/IP Network Interface Configuration ServiceIPAddress Option The ServiceIPAddress option defines a single IP address on which NIFSOCK will listen for incoming connections. Setting this option overrides the default behavior of accepting connections on all IP addresses. The IP address must contain a single, literal IPv4 or IPv6 address or a single hostname.
TCP/IP Network Interface Configuration Network Interface Section ([NIF-nifname]) ServicePort Option The ServicePort option is a numeric value that defines the TCP/IP service port on which incoming connections will be accepted (NonStop host) or the default TCP/IP service port for outgoing connections (all workstations). The default value of 2787 is recommended because this port number has been assigned to Piccolo by the Internet Assigned Number Authority.
TCP/IP Network Interface Configuration TCP/IP Example PIPE.INI Configuration File TCP/IP Example PIPE.INI Configuration File In this example, the default service port of 2787 is used. The Resolver section shows three formats of configuring the NIFSOCK NIF. [NIF-mynifsock] ProgramFile=nifsock ;required option ServicePort=2787 ;the default service port [Resolver] ; this example shows the IP address 10.0.0.1 and service ; port 2006. boston.corsof.com=ip:10.0.0.1.
10 IPX/SPX Network Interface Configuration This section shows how to configure the IPX/SPX Network Interface (NIF) by: • • • • Setting up addressing. Configuring multiple NIFs. Allowing for special NonStop considerations. Using the options in the PIPE.INI file. The SPX network interface (NIFNVL) is used to transmit RSC/MP data using the Novell SPX protocol as the transport. The host and workstation must be configured with NIFNVL.
IPX/SPX Network Interface Configuration SPX Network Interface Addressing SPX Network Interface Addressing The SPX NIF makes use of the Novell bindary services to resolve addresses to network addresses. The SPX NIF provides two means of specifying the name for which a listen will be posted: • • The default use of SystemName. The SPXName option which allows the choice of a specific name to be used for the listen.
IPX/SPX Network Interface Configuration Configuration Options Reference 2. By using the ProcessName keyword in the [NIF-nifname] section. Configuration Options Reference The following options are available for configuring the SPX network interface process in the PIPE.INI file. The example configuration file shown later in this section uses some of these options. Network Interface Section ([NIF-nifname]) This NIF section contains options that control the operation of the SPX network.
IPX/SPX Network Interface Configuration Network Interface Section ([NIF-nifname]) EnableProtocolKeepAlives Option The EnableProtocolKeepAlives option determines whether the protocol-specific keepalive mechanism should be enabled. If enabled, this option increases network traffic. EnableProtocolKeepAlives=enabled enabled YES to enable, NO to disable.
IPX/SPX Network Interface Configuration Network Interface Section ([NIF-nifname]) IN Option The IN option specifies the IN file for the NIF process. IN=filename filename A valid file name; DEFINES are not supported. Required: No Default: The IN file of the Pipeman process.
IPX/SPX Network Interface Configuration Network Interface Section ([NIF-nifname]) LinkRequestRetryInterval Option The LinkRequestRetryInterval option specifies the length of time that initiating Pipeman will wait for confirmation of establishing a logical link from the destination Pipeman before repeating its request or moving on to another NIF, according to the setting of the LinkRequestRetriesMax option. LinkRequestRetryInterval=number number An integer in the range of 1 through 65535.
IPX/SPX Network Interface Configuration Network Interface Section ([NIF-nifname]) PRI Option The PRI option specifies the execution priority of the NIF process. PRI=priority priority An integer in the range 1 through 199. Required: No Default: The priority of the Pipeman process. Platforms: NonStop Example: PRI=128 Priority Option The Priority option specifies the order in which this NIF will be used (if multiple NIFs are configured) when making a connection to a remote node.
IPX/SPX Network Interface Configuration Network Interface Section ([NIF-nifname]) ProgramFile Option The ProgramFile option specifies the program file that should be run for this NIF. For SPX network interfaces, this value must be NIFNVL. ProgramFile=nifnvl Required: Yes Default: None Platforms: All Example: ProgramFile=nifnvl SPXName Option The SPXName option specifies the name which will be concatenated with the DomainName used to broadcast to the Novell bindary service as an SPX service.
IPX/SPX Network Interface Configuration SPX Example PIPE.INI Configuration Files Term Option The Term option specifies the name of the home terminal for the NIF process. Term=terminalname terminalname A valid name for a terminal or process, which can also include a node name. Required: No Default: The home terminal of the Pipeman process. Platforms: NonStop Example: Term=$home SPX Example PIPE.INI Configuration Files This example shows a single NIFNVL: [PIPEMAN] DomainName=mycompany.
IPX/SPX Network Interface Configuration SPX Example PIPE.INI Configuration Files This example shows a Resolver section in a PIPE.INI file of a corresponding workstation. [Resolver] sample.demo.
11 Managing the RSC/MP Transport (Piccolo) This section describes the PIPECP Piccolo control program and commands that you use to manage Piccolo. These commands allow you to start and stop Piccolo; to obtain Pipeman status, NIF status, and version information; and to control Piccolo and NIF event logging. Running the PIPECP Program PIPECP is an interactive program that presents an identical command-oriented interface on all supported platforms.
Managing the RSC/MP Transport (Piccolo) PIPECP Commands PIPECP Commands Within the PIPECP window, you can enter the following commands at the prompt (pipecp>): BACKUP START cpu Starts the backup process. cpu must be the number of a valid installed and running CPU. For NonStop systems only. BACKUP STOP Stops the backup process. For NonStop systems only. CFGSW Directs PIPECP to use a different configuration file and communicate with a different Pipeman process. For NonStop and UNIX systems only.
Managing the RSC/MP Transport (Piccolo) PIPECP Commands STOP Stops Piccolo. Use STOP -Y to suppress the confirmation prompt. STOP nifname Stops the specified network interface. VERSION filename Displays the Piccolo version report of an executable file or library.
Managing the RSC/MP Transport (Piccolo) PIPECP Commands HP NonStop Remote Server Call (RSC/MP) Installation and Configuration Guide—522358-011 11-4
12 Configuring and Managing the RSC/MP TDP Process The Transaction Delivery Process (TDP) is a persistent NonStop process pair that facilitates delivery of messages between the workstation application and host server applications. Through the TDP, a workstation can communicate with any Pathway server or a named NonStop process. RSCCOM is a host process that provides a command interface to configure and control the TDP.
Configuring and Managing the RSC/MP TDP Process Editing the STARTRSC File Editing the STARTRSC File STARTRSC is a sample TDP startup TACL macro and can be used as it is; however, you can make the following changes: • • If you are not going to pass the volume and subvolume names as an argument when you run the macro, change all the [RSCWORK] references in the STARTRSC file to indicate the volume and subvolume in the format $vol.subvol.
Configuring and Managing the RSC/MP TDP Process Editing the STARTRSC File Three choices for starting the TDP are presented in the STARTRSC sample TACL macro. The simplest command is active within the file; if another choice is the desired one for starting the TDP, comment out the undesirable command and activate the desirable one. The three choices are: 1. Start the TDP on the same CPU where the current TACL is running: RUN [SYSTEM.SYSTEM.]TDP /NAME $zrsc, NOWAIT/ 2.
Configuring and Managing the RSC/MP TDP Process Running Processes at High PINs Running Processes at High PINs All RSC/MP processes are compatible with High PINS . The TDP process can accept opens and requests from TCPs, UMS requesters, and other Guardian processes that run with HIGHPIN ON, regardless of whether the TDP itself is configured to run with HIGHPIN ON. Configuring TDP Objects The TDP is composed of objects (ACS, PIPE, and TERM) that are referenced and controlled individually through RSCCOM.
Configuring and Managing the RSC/MP TDP Process RSC/MP Configuration Limits RSC/MP Configuration Limits Table 12-1 shows the RSC/MP configuration limits. These limits are stated both as theoretical maximums (that is, the limits imposed by the architecture of the RSC/MP product) and as maximums observed during product testing. The actual limits observed at your site may vary (either larger or smaller) from the limits observed during product testing.
Configuring and Managing the RSC/MP TDP Process TERM Object TERM Object All RSC/MP connections and sessions terminate with a TERM object. While a TERM generally corresponds to a workstation, a workstation can be configured to access multiple TERM objects. The TERM object sets defaults for the sessions associated with it. For example, a TERM object can enforce access through an ACS process regardless of how individual workstations are configured.
Configuring and Managing the RSC/MP TDP Process Logging Using EMS Tokens (GCSC) may request additional logging to diagnose a TDP problem. To turn on optional logging, follow these steps: 1. Use the RSCCOM command LOGOPEN to start logging and to identify the log file; for example: LOGOPEN $DATA.RSC.ERRLOG The log file ($DATA.RSC.ERRLOG, in this example) must be a pre-existing, unstructured Enscribe file, spooler (for example, $5.#MYTRACE), or a terminal with a paused TACL (for example, $ASY01.#TERM2). 2.
Configuring and Managing the RSC/MP TDP Process Suppressing Event Types increases the size of the token stream; using the template merge operation is recommended instead. Note. If you do not merge the templates, DO NOT define the RSCUSEEMS PARAM prior to starting the TDP, otherwise messages will not be properly displayed. Suppressing Event Types To suppress object state changes (for example, stopping, starting or aborting) from being sent to the console, use the CONTROL TDP SUPPRESSEMS command.
Configuring and Managing the RSC/MP TDP Process Logging Events TERM Object Event Types The TERM object has these options for logging events: ACSALLOW Attempts to access a server for which the ACS object permitted the access. ACSREJECT Attempts to access a server for which the ACS object rejected the access. CONNECTION Events related to establishing connections; for example, connect and disconnect.
Configuring and Managing the RSC/MP TDP Process Logging Events HP NonStop Remote Server Call (RSC/MP) Installation and Configuration Guide—522358-011 12-10
13 RSCCOM Command Reference This section describes the RSCCOM commands that are used to manage the RSCCOM environment, control the TDP, and manage the TDP objects. Overview of RSCCOM Commands RSCCOM is a NonStop system process which provides a command interface to the TDP. You can enter RSCCOM commands interactively at a workstation to configure and control the TDP. There are three categories of RSCCOM commands: • Operational commands that manage the internal RSCCOM environment.
RSCCOM Command Reference ! Command ! Command The ! command allows immediate execution of a previously executed command line. This command acts like the FC command, but executes the specified command immediately. When no arguments are indicated, the ! command repeats the last command string entered. ! !prefix !number prefix The leading character of the previously entered command string that you want to re-execute. number The number of the stored command to re-execute.
RSCCOM Command Reference ASSUME Command text The text to be commented. Example: The following example shows comments in an RSCCOM OBEY file: [ configure TERM objects ADD TERM SMITH [workstation for John Smith ADD TERM JONES [workstation for Tom Jones [START ALL TERMS START TERM * ASSUME Command The ASSUME command sets the default TDP object.
RSCCOM Command Reference FC Command FC Command The FC (fix command) command repeats a command line, allowing you to edit the command. This FC command behaves similar to the TACL FC command. FC FC prefix FC number prefix The leading characters of the command string to edit. number The command prompt number of the command line of the command to edit. When no arguments are entered, FC returns the previous command string entered.
RSCCOM Command Reference HELP Command Example: The following example shows the correction of a typing error in which a V was used instead of a C in the word DYNAMIC: 4(( ALTER TERM DYNAMIV ACSERVER ACS1 ***Error 3016: TERM object ‘DYNAMIV’ has not been configured. 5(( FC 5(( ALTER TERM DYNAMIV ACSERVER ACS1 ..... 5(( RC ALTER TERM DYNAMIC ACSERVER ACS1 ..... 6(( HELP Command The HELP command displays short descriptions of the RSCCOM commands and parameters.
RSCCOM Command Reference HISTORY Command HISTORY Command The HISTORY command displays the last 20 previously entered RSCCOM commands. HISTORY H MAXERRORS Command The MAXERRORS command sets the number of errors that RSCCOM ignores when executing an IN or OBEY command file, or an IN process file. MAXERRORS number number The maximum number of errors that RSCCOM ignores. MAXERRORS can be entered in the command file that is used for the IN file option of the RSCCOM STARTUP command. The default value is 1.
RSCCOM Command Reference OBEY Command Example: The following command allows RSCCOM to continue executing the command file until it encounters 10 warnings or the end of the file: 1(( MAXWARNINGS 10 OBEY Command The OBEY command reads commands from a batch file. OBEY filename filename An edit file name from which RSCCOM reads commands. RSCCOM reads and executes commands from the named file until it encounters an EXIT command or the end of the file. All lines read from the file are echoed to the terminal.
RSCCOM Command Reference RSCCOM TDP Control Commands RSCCOM TDP Control Commands There are several RSCCOM commands that can be used to control the operation of the TDP. Enter these commands at an RSCCOM prompt. CONTROL TDP BACKUPCPU LOGOPEN STATUS TDP CONTROL TDP SECURITY LOGCLOSE VERSION CONTROL TDP SUPPRESSEMS OPEN The TDP commands are not case-sensitive. Multiple commands may be entered on one command line by separating each command with a semicolon (;).
RSCCOM Command Reference CONTROL TDP SECURITY Command CONTROL TDP SECURITY Command The CONTROL TDP SECURITY command defines the security attributes for an existing TDP process.
RSCCOM Command Reference LOGOPEN Command LOGOPEN Command The LOGOPEN command names the files that the TDP uses for reporting errors and changes in object status. The TDP generates either text or event messages for each log file. Logging is provided primarily for RSC/MP development and debugging purposes, as use of this command can cause performance problems associated with the extra I/O. There is no default log file. Note. Critical events are always logged to the console, $0.
RSCCOM Command Reference LOGCLOSE Command LOGCLOSE Command The LOGCLOSE command closes the current error log opened with the LOGOPEN command. LOGCLOSE OPEN Command The OPEN command specifies the name of the TDP to which RSCCOM directs subsequent commands and closes any previously opened TDP. OPEN [ \system.]$process system The name of the host system. If not supplied, the current host system name is used. process The name of the TDP process to open.
RSCCOM Command Reference VERSION Command Current memory in use is current-mem bytes. Maximum memory use is max-mem bytes. Pathsend is pathsend-state. Log file: logfile-state. Security: 'O' These are the parameters that are returned: process-name The name of the target TDP. prim-cpu The number of the primary CPU.
RSCCOM Command Reference TDP Object Management using RSCCOM Commands TDP Object Management using RSCCOM Commands You use the RSCCOM commands for configuring and managing the following TDP objects: • • • ACS PIPE TERM To avoid entering the object type for the following commands, you can set a default object type through the ASSUME command. ABORT Command The ABORT command aborts TDP objects regardless of their current state.
RSCCOM Command Reference ALTER Command ADD type name type The type of TDP object. name The name supplied for the object. The ACS and PIPE object name can be from 1 through 15 alphanumeric characters; the TERM object name can be from 1 through 8 characters. The name must start with a letter and is not case-sensitive.
RSCCOM Command Reference DELETE Command Example: The following command alters the ACSERVER attribute of the TERM object TERM01 to MYACS: 1(( ALTER TERM TERM01 ACSERVER MYACS DELETE Command The DELETE command removes an object from the TDP. An object must be in the STOPPED state before it can be deleted. DELETE type name DELETE type * type The type of TDP object. name The name supplied for the object to delete. * Deletes all configured objects of this type.
RSCCOM Command Reference INFO Command INFO Command The INFO command displays the current attribute values for an object. See TDP Object Attributes and Configuration Notes on page 13-28 for a list of attributes for the ACS, PIPE, and TERM objects. INFO type name [ OBEYFORM ] INFO type * type The type of TDP object. name The name of the object for which to display information.
RSCCOM Command Reference SET TEMPLATE ADD TERM RESET Command No TERM01 To capture this data in an edit file, start RSCCOM with the INFO command from the TACL prompt, using the OUT facility: > RSCCOM /out $volume.subvol.file/$TDP; INFO TERM * OBEYFORM RESET Command The RESET command changes the values for the attributes of an object from the values that are entered with the SET command to the default values. This command does not affect the attributes of an object that has already been added to the TDP.
RSCCOM Command Reference SET Command SET Command The SET command establishes values for an object’s attributes. Use the SET command before the ADD command. After adding the object, you can change attribute values by using the ALTER command. SET type attribute value type The type of TDP object. attribute The name of an attribute (see TDP Object Attributes and Configuration Notes on page 13-28). value A value for the attribute.
RSCCOM Command Reference START Command This is an example of the system default attributes for a TERM object: PWYPATHMON IDSPATHMON IDSTCP IDSTCLPROG IDSINITIAL PWYTIMEOUT ACSERVER LOGEVENTS TEMPLATE $RSCP $RSCP RSC-TCP $SYSTEM.ZRSCHOST.IDS IDS-SAMPLE 30 None None No START Command The START command initiates operation of an object. START type name START type * type The type of TDP object. name The name supplied for the object.
RSCCOM Command Reference STATS Command STATS Command The STATS command shows data accumulated within the TDP of the specified object, if the object is in the started state. Note. Use of the STATS command with the ACS object displays the message “STATS data is not available for an ACS object”. STATS type name [ RESET ] STATS type * [ RESET ] type The type of TDP object. name The name supplied for the object.
RSCCOM Command Reference STATS Command This is an example of the output of a STATS command for a TERM object: Term RSCQA15 Since(Started/Reset) Wed May 15, 2001 08:27:13 # Connected 17 ---- IOs ---RECV SENT REQSIZE 63708 35712 >56789 ---- UMS ---RECV SENT REQSIZE 0 0 0 ---- TMF TRANSACTIONS---STARTED COMMITTED ABORTED 17 17 0 ---- SERVER RESPONSE TIME (SECONDS) --MINIMUM AVERAGE MAXIMUM 0.000257 0.895676 2.
RSCCOM Command Reference STATUS Command UMS REPSIZE The total number of bytes that this TERM object has handled for UMS replies (from workstation applications) since resettime. TMF TRANSACTIONS STARTED The total number of transactions initiated by this TERM object. TMF TRANSACTIONS COMMITTED The total number of transactions committed by this TERM object. TMF TRANSACTIONS ABORTED The total number of transactions aborted by this TERM object.
RSCCOM Command Reference STATUS Command Examples: The following command displays the status for the TERM object named TERM01: 1(( STATUS TERM TERM01 The following command displays the status for all configured TERM objects: 2(( STATUS TERM * ACS Object Status Report The following example shows the format of the ACS object status report: ACS Status Sess Req. Last Event name Outstanding ---------------------------------------------------------------------ACS1 ACS2 Started Started 0 0 0 0 ACS started.
RSCCOM Command Reference STATUS Command This is the data in a PIPE object status report: PipeName The name of the PIPE object. Status The current status of the PIPE. These are the possible values: The PIPE object is stopped. STOPPED The PIPE object is executing. STARTED Sessions The number of outstanding Pipe sessions (one-to-one correspondence with RSC/MP connection). Last Event The last RSC/MP event recorded for this TDP object. There are two types of events: 1.
RSCCOM Command Reference STATUS Command Conn The number of physical connections. Sess The number of TERM sessions. Last Event The last RSC/MP error event recorded for this TDP object. TERM Object Detailed Status The following information is included in the TERM object status report if the DETAIL attribute is set: CONNECTION TYPE The communications object through which the connection was established. SESSION HANDLE A specific number issued by the TDP at the time of the BeginSession call.
RSCCOM Command Reference STOP Command STOP Command The STOP command stops operation of TDP objects that have no outstanding sessions. Use the ABORT command to stop an object that has outstanding sessions. STOP type name STOP type * type The type of TDP object. name The name supplied for the object. The ACS and PIPE object name can be from 1 through 15 alphanumeric characters; the TERM object name can be from 1 through 8 characters. The name must start with a letter and is not case-sensitive.
RSCCOM Command Reference TELL Command alias-type Defines the type of the alias that follows, either GROUP or SESSION. GROUP Sends the message to the group of workstation sessions with the GROUP_ALIAS option equal to alias. SESSION Sends the message to a workstation session with the SESSION_ALIAS option equal to alias. alias Defines which sessions receive the message-text.
RSCCOM Command Reference TDP Object Attributes and Configuration Notes TDP Object Attributes and Configuration Notes ACS Object Attributes Table 13-1. ACS Object Attributes Attribute Name Description ACSSERVERCLASS The valid Pathway server class name of an ACS server that is running in a Pathway environment. If blank, then the ACS server is not running in a Pathway environment. If specified, then the Pathmon name must be set in the ACSPROCESSNAME attribute. The default is no ACS server class name.
RSCCOM Command Reference PIPE Object Attributes PIPE Object Attributes For PIPE objects, the object name must be unique in the TDP, but does not need to be unique on the host or on the network. Piccolo distributes connections across PIPE objects of the same name in the same host. The name must match the first portion of the HOST_PIPENAME option on the workstation. Table 13-2.
RSCCOM Command Reference PIPE Object Attributes The PIPE object also has two read-only attributes that are not configurable after TDP startup: Attribute Name Description PIPEINI LOCATION The Piccolo configuration file name and location. This value is derived at TDP startup from the PIPEINI or PATH environment variables or, if neither is provided, by finding the configuration file of the default Pipeman process, $PIPE. Pipeman IpcKey The process name of the Pipeman process.
RSCCOM Command Reference TERM Object Attributes. TERM Object Attributes. Table 13-3. TERM Object Attributes (page 1 of 2) Attribute Name Description ACSERVER The Access Control Server invoked for sessions on this TERM.
RSCCOM Command Reference TERM Object Attributes. Table 13-3. TERM Object Attributes (page 2 of 2) Attribute Name Description LOGEVENTS Used for logging events. Logging choices are ACSALLOW, ACSREJECT, CONNECTION, DIAGNOSTIC, MEMORY, SESSION, TMF, MESSAGE, or ALL. See the TERM Object Event Types on page 12-9 for a definition of these categories. You can alter the LOGEVENTS attribute without the TERM object being in the STOPPED state.
RSCCOM Command Reference TERM Object Attributes. TERM Object Configuration Notes Each workstation must have a TERM object in the TDP. There are two types of TERM objects: static and dynamic. Static TERM objects require that you specify a TERM name for each workstation before it is connected. The name of the TERM object (TERM01 in the following example) must match in the host and workstation configurations (see Figure 13-1). The TDP uses this TERM object only for a specific workstation.
RSCCOM Command Reference TERM Object Attributes. Configuring Dynamic TERM Objects You can configure the TDP so that TERM objects are created dynamically at the time the workstation is connected. This capability is helpful when there are a large number of workstations that do not correspond directly to one particular TDP. It is also helpful in that it allows for a single, non-unique, distributable RSC.INI file.
RSCCOM Command Reference • TERM Object Attributes. Use a TERM template with a name other than dynamic. Follow these steps: 1. Configure the TDP: a. Using the SET command, change the TEMPLATE attribute to YES: set term template yes b. Add a TERM object to the TDP and name it, for example, NEWTERM: add term newterm 2. Edit the RSC.INI file: a. Add the TERM_TEMPLATE option; for example: term_template=newterm b.
RSCCOM Command Reference TERM Object Attributes.
14 Configuring the RSC/MP Client This section describes how to configure the client workstations. RSC/MP Client Configuration and Verification Follow these steps to configure and test the RSC/MP client: 1. Install and configure the host component (see Section 3, Installing RSC/MP on the Host, and Section 12, Configuring and Managing the RSC/MP TDP Process). 2.
Configuring the RSC/MP Client Basic RSC.INI Configuration Basic RSC.INI Configuration RSC/MP configuration files can be created and adjusted using an ordinary text editor on all platforms. Also, the RSC/MP Configuration Wizard (RscConfig.exe file) can be used to create a basic configuration file on the Windows platform. An RSC/MP configuration file can have any name. The default name is RSC.INI, and this name is used throughout this subsection. Note.
Basic RSC.INI Configuration Configuring the RSC/MP Client option is not specified, the RSC/MP error file must be in the application’s current directory, C:\ (for Windows), or in the PATH (for Windows and UNIX). Example: ERROR_FILE = c:\rsc\RSC.ERR 3. The SUBSYSTEM_NAME option. This option supplies the RSC/MP I/O manager (RSCPIPE) process logical name. When the application issues an RscConnect call the RSC/MP API library will attempt to communicate with RSCPIPE.
Configuring the RSC/MP Client Starting the RSC/MP Transport Manager (Pipeman) Starting the RSC/MP Transport Manager (Pipeman) The PIPEMAN process must be running in order for RSC/MP clients to operate correctly. PIPEMAN must be started in one of the following three ways: 1. When RSC/MP is installed as a service, PIPEMAN will be started automatically when the RSC Service starts.
Configuring the RSC/MP Client Configuring the RSC/MP I/O Manager Process (RSCPIPE) Starting the RSCPIPE Process on Windows Systems The syntax for starting the RSCPIPE process from the RSC.INI file is: SUBSYSTEM_CMDLINE = "[-h | -hh] [-dflogname] [-cN] [-lN]" The syntax for starting the RSCPIPE process from a command line prompt is: \rscpipe.exe [-h | -hh] [-dflogname] [-cN] [-lN] [subsystem_name] See Appendix A, Migration to RSC/MP 7.
Configuring the RSC/MP I/O Manager Process (RSCPIPE) Configuring the RSC/MP Client -cN Specifies the debugging class. Values range from 0 (no debugging classes) to 255 (all debugging classes). The default value is 255. This setting takes effect only when diagnostic logging has been enabled with the -d flag. The debugging classes are specified as a sum of the target class values, selected from the values below.
Configuring the RSC/MP I/O Manager Process (RSCPIPE) Configuring the RSC/MP Client Starting the RSCPIPE Process on UNIX Systems The syntax for starting the RSCPIPE process from the RSC.INI file is: SUBSYSTEM_CMDLINE = "[-d] [-cN] [-lN]" The syntax for starting the RSCPIPE process from a command line prompt is: /rscpipe.exe [-d] [-cN] [-lN] [subsystem_name] See Appendix A, Migration to RSC/MP 7.2 for command line parameters specific to migrating applications. The folder where rscpipe.
Configuring the RSC/MP Client subsystem_name Testing the RSC/MP Client Configuration The logical name of the RSCPIPE process. This name identifies a running instance of the RSCPIPE process, for example the icon name or the process name in a task list. In order for an application to identify and use this RSCPIPE instance, the name specified here must match the SUBSYSTEM_NAME option established by the application.
A Migration to RSC/MP 7.2 This appendix provides the following installation and configuration information: • • • • The differences between RSC/MP 7.2 and earlier versions. Features that are no longer supported. Procedures for migrating from previous releases to RSC/MP 7.2. Information about host and workstation connectivity options. See the Remote Server Call (RSC/MP) Programming Manual for information about the programming migration issues. Differences Between RSC/MP 7.
Migration to RSC/MP 7.2 Features That are No Longer Supported Features That are No Longer Supported These features are not supported in this version: • • • • Pathway session type PATHSENDNOOVERRIDE and PATHSENDOVERRIDE commands ADSPPORT object Step-Aside feature Migration Tips There are three major variations of RSC that are referenced in the following section: • • • RSC, also known as RSC Classic. This variation utilizes direct communication objects. Versions up through 5.0 are RSC versions.
Determining the Appropriate Migration Section Migration to RSC/MP 7.2 Determining the Appropriate Migration Section Use the steps below to identify the appropriate migration section. 1. Determine if the current installation uses Piccolo. On the workstation, look for the file rscpipe in the RSC installation area. If the file is not found, use the migration section Migrating from RSC 5.0 and Previous Versions to RSC/MP 7.2 on page A-6. 2. Determine if the current installation is prior to RSC 5.1.
Migration to RSC/MP 7.2 Migrating from RSC for Piccolo 5.1 -- RSC/MP 6.x to RSC/MP 7.2 Migrating from RSC for Piccolo 5.1 -- RSC/MP 6.x to RSC/MP 7.2 This section assumes that the Piccolo component has been installed and configured from a previous version. The RSC/MP 7.2 host component supports connection requests from RSC for Piccolo and RSC/MP clients 5.1 - 7.
Migration to RSC/MP 7.2 Migrating from RSC for Piccolo 5.0 to RSC/MP 7.2 Migrating from RSC for Piccolo 5.0 to RSC/MP 7.2 This section assumes the Piccolo component has been installed and configured from a previous release. This migration is very similar to the previous section EXCEPT the old client will NOT be able to communicate with the new RSC/MP host. The migration must be performed as a unit. Each client that needs to communicate with the RSC/MP 7.
Migration to RSC/MP 7.2 Migrating from RSC 5.0 and Previous Versions to RSC/MP 7.2 Migrating from RSC 5.0 and Previous Versions to RSC/MP 7.2 A migration from non-Piccolo based RSC clients to RSC/MP requires a conversion to Piccolo as well as a migration of the host and all clients. Two ways to accomplish this migration are discussed here. The first approach describes an intermediate migration to RSC/MP 6.3; the second approach describes migrating the host and clients to RSC/MP 7.2 in a single leap.
Migration to RSC/MP 7.2 Migrating the Host and Client Directly to RSC/MP 7.2 Migrating the Host and Client Directly to RSC/MP 7.2 The migration from RSC 5.0 and earlier to RSC/MP 7.2 can be a large effort. The migration requires conversion to Piccolo and spans a number of changes in functionality. Upgrading directly to RSC/MP 7.
Migration to RSC/MP 7.2 Migrating Connectivity Options Migrating Connectivity Options This section is relevant only for upgrades from a version of RSC that was not based on Piccolo. See Determining the Appropriate Migration Section on page A-3 to determine if an installation is Piccolo-based or not. Prior to releases that included Piccolo, all connectivity information was specified in the RSC.INI file or programmatically by RscSetOption.
Migration to RSC/MP 7.2 Method 2: Using Compatibility Mode Method 2: Using Compatibility Mode Compatibility mode provides the ability for connectivity information specified by the RSC/MP API call RscSetOption, as was done in pre-Piccolo applications, to be pushed through to the Piccolo layer. Applications that call RscSetOption to set any of the "Compatibility Mode" options in the table Discontinued RSC.INI Options on page A-16 will not require re-coding.
Migration to RSC/MP 7.2 Method 2: Using Compatibility Mode Configuring Workstation Network Interfaces (NIFs) The Piccolo configuration file requires connectivity information; this information must match what the application is specifying in RscSetOption function calls. Select the appropriate protocol type from the items below and update the Piccolo configuration file with the required connectivity options.
Method 2: Using Compatibility Mode Migration to RSC/MP 7.2 used to select among multiple TDPs running on a single NonStop server system — then the special flag -use_tcpport must be used when invoking RSCPIPE: rscpipe -use_tcpport (command line) SUBSYSTEM_CMDLINE="-use_tcpport" (in RSC.INI for auto start of RSCPIPE) When RSCPIPE is invoked with the -use_tcpport flag, the RSC layer will push the entire HOST_INET_ADDRESS, including the service port, to the Piccolo layer.
Migration to RSC/MP 7.2 Method 2: Using Compatibility Mode Piccolo Configuration File Example, UpperCase NETNAME (host): [nif-nifnb] ProgramFile=nifnb NBCase=U Alternatively, the all-lowercase convention can be used. To use lower case, provide the special flag -net_lower when invoking RSCPIPE: rscpipe -net_lower (command line) SUBSYSTEM_CMDLINE="-net_lower" (in RSC.
Migration to RSC/MP 7.2 Method 2: Using Compatibility Mode On the host, Piccolo must be configured with a NIFASY for each device through which RSC/MP clients will connect. Piccolo Configuration File Example (host): [nif-example] ProgramFile=nifasy ComDevice=COM2 Piccolo Configuration File Example (client): [nif-example]ProgramFile=nifasy ComDevice=COM2 Use of Multiple NIFs The following discussion applies to RSC/MP clients on which the Piccolo transport has been configured to run multiple NIF processes.
Method 2: Using Compatibility Mode Migration to RSC/MP 7.2 Figure A-1. Multiple NIFs in Compatibility Mode RSC/MP workstation application code : RscSetOption(ulOptionsHandle, "HOST_INET_ADDRESS", "12.3.45.6", 0); RscSetOption(ulOptionsHandle, "SUBSYSTEM_NAME", "RSCTCP"❶, 0); RscConnect(ulOptionsHandle, ...
Method 2: Using Compatibility Mode Migration to RSC/MP 7.2 Starting RSCPIPE in Compatibility Mode The RSCPIPE process facilitates communication between the RSC layer and the Piccolo layer on the workstation. In order to push connectivity information from the RSC layer to the Piccolo layer, the RSCPIPE process must be started with special “connectivity mode” options. Use the SUBSYSTEM_CMDLINE option to pass options to RSCPIPE during auto startup.
Migration to RSC/MP 7.2 Discontinued RSC.INI Options Discontinued RSC.INI Options The options shown in Table A-2 are either not supported by RSC/MP clients or are supported only in Compatibility Mode using the migration feature discussed in Method 2: Using Compatibility Mode on page A-9. Table A-2. Discontinued RSC.
B Installation Troubleshooting This appendix describes the test programs and procedures for checking the installation and configuration of RSC/MP and how to report problems to HP Global Customer Support Center (GCSC). Notes About Diagnostic Clues Many things that can go wrong in the RSC/MP system (such as misconfigurations, API programming errors, operational and network failures) can be diagnosed using the RSC/MP primary logging functions.
How to Trace Errors Installation Troubleshooting How to Trace Errors This appendix provides a step-by-step process for troubleshooting an RSC/MP connection. This process includes the following assumptions: • You have followed the instructions for installing RSC/MP on the host and workstation. Using this procedure, you can quickly target the most common problems and provide a resolution for most of them.
Installation Troubleshooting Step 2. Determine if the Communications Transport is Functional 3. Compare the results of the commands above to the RSC/MP host and client softdocs to verify that compatible RSC/MP software is running on the NonStop host and the workstation. Step 2. Determine if the Communications Transport is Functional Use a tool provided by the communications transport provider, such as PING for TCP/IP or start a TACL or an async line to verify that the network is working correctly.
Installation Troubleshooting 2. Step 4. Check the Host Configuration On a Windows workstation or a UNIX workstation, enter this command: > pcfgchk which should produce output similar to the following (line numbers and sections processed vary depending on the data in the Piccolo Configuration file; VPROC and configuration file names will vary depending on the platform): Piccolo Configuration Check Program - T7981V70 - (28SEP2003) 4.0.0/001 - Win32 Copyright (c) 1994-2003 Cornerstone Software, Inc.
Installation Troubleshooting Step 5. Run the Workstation RSC/MP Test Program If no process is found, start the process before proceeding: 4>RUN $SYSTEM.ZRSCHOST.TDDSVR /NAME $TDD,NOWAIT/INTERPROCESS If there is more than one RSC/MP ISV on your system, be sure that you are using the correct one. Use the VOLUME command to locate to the ISV for the version of RSC/MP that you are going to use. 3. Ensure that a TDP process is running. The installation process moves the TDP object code to $SYSTEM.SYSTEM.
Installation Troubleshooting Step 6. Interpret the Workstation and Host Error Messages 6. Messages from the workstation can reach the target TDP process on the NonStop host. This requires that the NIF is communicating with the correct port in the NonStop communications subsystem and that the port is started. 7. The TDP process is able to open and communicate with the designated server process on the NonStop system.
Installation Troubleshooting Step 7. Check the Status of the TDP Objects Step 7. Check the Status of the TDP Objects Follow these steps to determine the current status and most recent errors of TDP objects: 1. Use the RSCCOM STATUS command for TERM objects, STATUS TERM *. 1 (( status term * Term Status Conn Sess Last Event -----------------------------------------------------------------@DYN0654 (DYNAMIC:TERM01) Started 0 0 TERM started. [ 2802 ] @DYN0655 (DYNAMIC:TERM02) Started 2 2 TERM started.
Step 8. Check the Status of the Components Installation Troubleshooting Step 8. Check the Status of the Components Check the status of the RSC/MP Transport components: > pipecp status nif NIF name Type Process Pri Links Address -------------------------------------------------------------------nif01 TCP/IP 4c4 10 0 10.1.70.
How to Use Logging Installation Troubleshooting How to Use Logging This subsection shows how to use logging on the RSC/MP components. Figure B-1.
RSC/MP API Logging Installation Troubleshooting RSC/MP API Logging API logging can be used to record certain details of the internal activities of the RSC/MP API library (DLL or shared library) for diagnostic purposes. When engaged, the logging function adds processing burden to the RSC/MP client application and generates potentially large log files. Logging should therefore be engaged only when required by Customer Support. To engage API logging, use the following options: . RSC.
Installation Troubleshooting RSCPIPE Logging If the client does not use RSC_DEFAULT_OPTIONS and does not call RscLoadOptions, follow the steps below to force the use of options. This setup will cause the RSC/MP API to load RSC_DEFAULT_OPTIONS from the specified file at the beginning of the first RSC/MP API function that the application calls. 1. Put the API logging options into a new options file. 2.
Installation Troubleshooting Piccolo Logging Piccolo Logging Piccolo logging is enabled by using the PIPECP LOGLEVEL command on both the RSC/MP client and the NonStop host. The following example shows the currently defined log levels.
TDP Logging Installation Troubleshooting TDP Logging Enabling TDP logging is a two step process: 1. A log file must be opened. 2. The PIPE and/or TERM object logging attributes must be selected. You can use the following RSCCOM commands to enable TDP logging: RSCCOM Command Description LOGOPEN $s.#tdplog The log file can be a spooler file, an unstructured Enscribe file, or a terminal ID.
How to Report Problems Installation Troubleshooting How to Report Problems If you must call HP Global Customer Support Center (GCSC), be ready to supply the following information. Copy or print these pages and complete this information. RSC/MP Information RSC/MP versions (see Step 1.
How to Report Problems Installation Troubleshooting Transport Information Transport type __ Asynchronous __ NetBIOS __ IPX/SPX __ TCP/IP LAN vendor (3COM, Ungermann-Bass, or other) Protocol stack and drivers used (XNS, NBP, or other) Workstation Information Operating environment and version Manufacturer and model Memory amount NonStop Host Information Processor type NonStop Kernel release Communications configuration HP NonStop Remote Server Call (RSC/MP) Installation and Configuration Guide—52
Installation Troubleshooting How to Report Problems HP NonStop Remote Server Call (RSC/MP) Installation and Configuration Guide—522358-011 B-16
C RSCCOM Syntax Summary This appendix lists RSCCOM commands by functional group. See Section 13, RSCCOM Command Reference, for more detail about these commands. See Notation Conventions on page xiii at the beginning of this guide for the conventions used to express command syntax. Working with RSCCOM These commands are processed by RSCCOM only. The TDP does not need to be opened to use these commands.
RSCCOM Syntax Summary Working With the TDP as a Whole OBEY filename Accept input from the given filename [ text Remainder of line is a comment (Use this inside the OBEY file only. It is not accepted when RSCCOM is used interactively.) MAXERRORS number Set the maximum allowable number of errors MAXWARNINGS number Set the maximum allowable number of warnings OPEN [\system.]$process Open a TDP process for RSCCOM to control Working With the TDP as a Whole RSCCOM passes these commands to the TDP.
RSCCOM Syntax Summary Working With Objects Within the TDP Working With Objects Within the TDP The commands in the following tables work with objects of the following types: • • • ACS PIPE TERM Saving keystrokes by setting a default object type Using the ASSUME command allows you to avoid entering the object type repeatedly.
RSCCOM Syntax Summary Working With Objects Within the TDP Adding, modifying, and deleting objects ADD typeA name Add a new object of the type ALTER typeA name attribute value Change one attribute of an existing object of the type DELETE typeA name Delete an object of the type DELETE typeA * Delete all objects of the type Starting and stopping objects START typeA name Start an object of the type START typeA * Start all objects of the type STOP typeA name Stop an object of the type that has no
Working With Objects Within the TDP RSCCOM Syntax Summary Getting information about objects INFO typeA name [OBEYFORM] INFO typeA * Show the attributes of one object of the type [optionally, in a format that can be used as input in an OBEY file] Show the attributes of all objects of the type STATS typeA name [ RESET ] Get statistics on one object [and optionally reset counters] STATS typeA * [ RESET ] Get statistics on all objects of the type [and optionally reset counters] STATUS typeA name [ DETAI
RSCCOM Syntax Summary Working With Objects Within the TDP HP NonStop Remote Server Call (RSC/MP) Installation and Configuration Guide—522358-011 C-6
D RSC/MP Scripts for Modems and Logons This appendix provides a script language reference and sample scripts for modems. Script Language Reference The script language provides a flexible means of controlling an attached device such as a smart modem during call answer and origination. The script controls the transmission and reception of control strings to the attached device. The language provides for conditional and unconditional testing, branching, and rudimentary loop counting.
RSC/MP Scripts for Modems and Logons Comments Comments The semicolon (;) serves as a comment delimiter, except when it appears inside a quoted string. Text following the semicolon, through the end of the line, is disregarded by the script interpreter. Conditional Testing The IF command controls the execution of the script based on timer expiration, received string matching, and counter value. Counting The script language provides a single counter that can be used to control script execution.
RSC/MP Scripts for Modems and Logons Script Language Commands Script Language Commands The following are script language commands, their definitions, and examples. Counter Command Set the value of the script counter. counter { value | operator } value Any signed 32 bit value. operator Plus sign (+) to increment the value and minus sign (-) to decrement the value. Disconnectstring Command Used when a disconnect is not detectable from RS-232 signals (for example, CD or DTR).
RSC/MP Scripts for Modems and Logons MESSAGE Command MESSAGE Command Write a message to the RSC/MP log file. message { string } RETURN Command Stop script processing. return { success | failure | shutdown } success The link has been established. failure The link could not be established. shutdown Stops the network interface. SEND Command Send a string to the attached device. The maximum string size is 256 characters.
RSC/MP Scripts for Modems and Logons WAIT Command stopbits 1 or 2 parity E for even, O for odd, or N for none • Set the port speed. set speed { value } value A valid port speed value. • Set case sensitivity when matching strings. set case { ON | OFF } ON For case sensitive string matching. OFF For non-sensitive string matching. OFF is the default. WAIT Command Wait for the specified length of time to pass or for certain responses to be received.
RSC/MP Scripts for Modems and Logons Sample Scripts The IF command can be used to determine whether the WAIT command completed due to timeout, or to check for specific strings in the input text. See the IF [NOT] Command on page D-3 for more information. Sample Scripts Sample scripts are supplied with RSC/MP to illustrate the script language and to serve as starting points for the development of user scripts. For Microsoft Windows systems, the following script is supplied: • ATCALL.
E Resolver Reference Tags This appendix lists the extended address tags for the asynchronous, NetBIOS, IPX/SPX, and TCP/IP platforms. The NIF address tag applies to all platforms (listed under All NIF Reference Tags on page E-1). These tags can be referenced in the Resolver section (preceded by the section name [Resolver] in PIPE.INI file) to map (or resolve) system addresses to corresponding extended addresses.
NetBIOS Reference Tags (nifnb) Resolver Reference Tags NetBIOS Reference Tags (nifnb) Tag Name Tag Value Format NBName name[.lana] name is a valid NetBIOS name or an asterisk (*) to indicate to resolve the address using broadcast name resolution. lana is the optional LAN adapter number. If not specified, the current configuration of the NIF’s LAN adapter number is used.
TCP/IP Reference Tags (nifsock) Resolver Reference Tags Tag Name Tag Value Format IPv6 “ipaddress. port” * ipaddress is a valid IPv6 address (example: “fe80::cafe:babe”). port is an optional port field. If not specified, the current configuration of the NIF service port is used. * indicates the address is resolved using DNS and overrides any other IP address specified. This tag is only used in the Resolver section.
Resolver Reference Tags TCP/IP Reference Tags (nifsock) HP NonStop Remote Server Call (RSC/MP) Installation and Configuration Guide—522358-011 E-4
F Best Practices Guide This appendix contains information intended to help you use RSC/MP effectively, including: • • Three conceptual models showing a range of RSC/MP configuration styles, see Model Configuration Scenarios on page F-1. Notes about configuring home terminals for RSC/MP, see Host Home-Terminal Considerations on page F-12. Model Configuration Scenarios This subsection describes three configuration scenarios.
Scenario 1 Best Practices Guide Figure F-1. Scenario 1 workstation (typical) workstation (typical) NonStop host HOST1 Servers Servers Servers Application Application RSCPIPE RSCPIPE PIPEMAN PIPEMAN PIPEMAN NIF NIF NIF TCP/IP TCP/IP TCP/IP TDP 10.1.90.
Best Practices Guide Scenario 1 Disadvantages • • This configuration does nothing to provide fault tolerance. If the host TDP or PIPEMAN process should crash, no workstation will be usable. Loss of the host NIF process can be tolerated, since PIPEMAN will restart the NIF automatically; but if the CPU on which the NIF is running goes down, if the network adapter fails, or if the network segment goes down, the system cannot be used.
Scenario 1 Best Practices Guide Figure F-2. Scenario 1 improved with NIFs on the same network adapter workstation (group “B”) workstation (group “A”) NonStop host HOST1 Servers Servers Servers Application Application RSCPIPE RSCPIPE TDP TDP PIPEMAN PIPEMAN PIPEMAN PIPEMAN NIF NIF NIF TCP/IP NIF port 5002 TCP/IP port 5001 port 5001 port 5002 $ZTC0 10.1.90.20 Network CDT013 ° Multiple NIFs on different network adapters (see Figure F-3).
Scenario 1 Best Practices Guide Figure F-3. Scenario 1 improved with NIFs on different network adapters workstation (group “B”) workstation (group “A”) Application Application RSCPIPE RSCPIPE PIPEMAN PIPEMAN NonStop host HOST1 Servers Servers Servers TDP TDP PIPEMAN PIPEMAN SystemName HOST1A NIF TCP/IP NIF port 5002 TCP/IP port 5001 SystemName HOST1B NIF NIF $ZTC0 $ZTC1 10.1.90.20 10.1.90.
Scenario 2 Best Practices Guide Scenario 2 A more typical production environment may need a moderate level of redundancy and provision for greater system throughput. In this case, a configuration similar to the following can be used (see Figure F-4). Figure F-4.
Best Practices Guide Scenario 2 Workstation configuration • • • One PIPEMAN process One NIF One network adapter DNS configuration This configuration relies on the DNS server to cause incoming connection requests to be distributed among the NIFs. For example, a round-robin DNS system can be employed. The example shown in Figure F-4 makes use of a DNS server that will give a different IP address for HOST1 on each name lookup. The first workstation that connects uses10.1.90.20, the second uses 10.1.90.
Scenario 2 Best Practices Guide Figure F-5. Scenario 2 modified to run without round-robin DNS workstation (group “B”) workstation (group “A”) Application Application RSCPIPE RSCPIPE NonStop host HOST1 Servers Servers TDP Servers TDP TDP active backup PIPEMAN PIPEMAN PIPEMAN NIF NIF NIF NIF NIF NIF TCP/IP TCP/IP $ZTC0 $ZTC1 $ZTC2 $ZTC3 10.1.90.20 10.1.90.21 10.1.90.22 10.1.90.23 Network Group B workstations have Group A workstations have [RESOLVER] HOST1=ip:10.1.90.
Scenario 2 Best Practices Guide Possible improvements to this configuration • To alleviate the heavy loading on the PIPEMAN process, consider running additional instances of PIPEMAN, each with its own set of TDPs and NIFs (see Figure F-6). Use PARAM PIPEINI to direct each TDP to its intended instance of PIPEMAN. Give each PIPEMAN instance its own SystemName setting, and configure each workstation to use one of those names.
Scenario 3 Best Practices Guide Scenario 3 In a critical production environment where redundancy and high performance are major requirements, two separate networks might be used (different wires, switches, hubs, routers, and so on). In this case, a configuration similar to the following can be used (see Figure F-7). Figure F-7.
Best Practices Guide Scenario 3 NonStop host configuration • • • • Multiple TDPs, configured with identical PIPE, TERM, and ACS objects; each TDP has its backup process enabled Multiple PIPEMAN processes, each with backup Multiple NIFs on for each PIPEMAN, configured in such a way that every PIPEMAN is reachable by either physical network All host processes running in different CPUs where possible Workstation configuration • • • • One PIPEMAN process One NIF Two network adapters, wired to different n
Best Practices Guide Host Home-Terminal Considerations Host Home-Terminal Considerations In many NonStop installations, it is common practice to connect to the host through Telnet or X-Windows sessions on a workstation. However, you should not use such a session as the home terminal for a TDP, PIPEMAN, or NIF process. By nature, Telnet sessions are transient. They are created when a user logs onto a NonStop server and are deleted upon logout.
Index A ABORT command 13-13 Access Control Server (ACS) 1-3 ACS object status report 13-23 ACSALLOW 12-9 ACSERVER attribute 13-31 ACSPROCESSNAME attribute 13-28 ACSREJECT 12-9 ACSSERVERCLASS attribute 13-28 Active backup 5-2 AdapterNumber option 8-3 ADD command 13-13 Address resolution protocol (ARP) 8-1 AIX installation 6-3 Alias 13-27 ALL events 12-9 ALTER command 13-14 AnswerScript option 7-3 API introduction 1-1 library B-10 logging B-10 Piccolo 5-4 Application program interface (API) overview 1-2 ArpRe
Index D CONNECT command 11-2 CONNECTION events 12-9 CONTROL TDP BACKUPCPU command 13-8 CONTROL TDP SUPPRESSEMS command 13-8 Counter command D-3 Counting character D-2 CPU option 5-21, 7-8, 8-4, 9-3, 9-4, 10-3, 10-4 D DatagramQueue option 8-5 Data, sending and receiving D-2 DETAIL attribute 13-22 DIAGNOSTIC events 12-9 DISCONNECT events 12-9 Disconnectstring command D-3 Distributed Systems Management (DSM) event collector 12-6 DLL library B-10 Domain option 8-5 DomainName option 5-21 Dynamic TERM object c
Index M LinkControl option 7-10 LinkRequestRetriesMax option 7-11, 8-7, 9-6, 10-5 LinkRequestRetryInterval option 7-11, 8-7, 9-6, 10-6 LinkType option 7-12 ListenQueue option 8-8 Local network adapter 8-1 Log collection points B-9 Log file 5-17 closing 13-11 opening 13-10 setting up 12-6 TDP 12-6 viewing 12-8 Log messages tokenized 12-7 LOGCLOSE command 12-7, 13-11 LOGEVENTS attribute 12-7, 13-29, 13-32 LogFileEntries option 5-24 LogFileName option 5-25 Logical connection 8-1 LOGLEVEL command 11-2 LogLeve
Index Q configuring single instance 5-5 de-installing as a Service 4-13 error messages 4-13 logging B-12 overview 5-3 running as a Service 4-13 service startup 4-11 using multiple ports 9-3 PING command 2-5 PIPE object events 12-9 status report 13-23 PIPECP commands 11-2 PIPECP program 11-1 PIPEINI environment variable 5-6 Pipeman process configuration 14-2 log file 5-17 starting 14-4 starting from Telnet session F-12 PIPEMAN section optional entries 5-15 specifying logging in 5-17 PIPE.
Index S running multiple instances 4-13 single Pipeman process 5-4 RSCTESTW program 2-6 RSCTESTW.EXE test program 14-8 RSCUSEEMS variable 12-7 RSCVPROC utility B-2 RSCWRITEREADS attribute 13-28 RSC.
Index U TDP aborting objects 13-13 adding objects 13-13 backup process 13-8 commands 13-8 configuration file (TDPCFG) 12-6 configuring objects 12-4 configuring objects using RSCCOM 13-1 displaying status 13-11 logging B-13 persistent 13-8 setting default object types 13-3 specifying name of process 13-11 starting from Telnet session F-12 status messages 13-10 using multiple processes 5-4 TDPCFG file 12-3, 12-6 TELL command 13-26 TEMPLATE attribute 13-32 TERM object attributes 13-31 dynamic configuration 1
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.
Examples Examples HP NonStop Remote Server Call (RSC/MP) Installation and Configuration Guide—522358-011 1
Examples HP NonStop Remote Server Call (RSC/MP) Installation and Configuration Guide—522358-011 2
What’s New in This Manual What’s New in This Manual ix Manual Information ix New and Changed Information ix About This Manual xi Manual Contents and Organization Audience Requirements xii Related Manuals xii Notation Conventions xiii xi 1. Introduction What is RSC/MP? 1-1 The RSC/MP Environment 1-1 Workstation Components 1-2 Host Components 1-3 RSC/MP Requirements 1-4 Communications Protocols 1-5 RSC/MP Installation 1-5 General Steps for Installation 1-5 Testing RSC/MP 1-6 2.
5.
7. Asynchronous Network Interface Configuration Installing on AIX From a CD 6-3 Installing on HP-UX From a CD 6-4 Installing on Linux From A CD 6-5 Installing on SCO UnixWare From A CD 6-6 Installing on Solaris From A CD 6-7 Files Installed on the UNIX Workstation 6-8 IPC Resource Requirements 6-9 System V Shared Memory 6-9 System V Message Queues 6-10 System V Semaphores 6-10 7.
11. Managing the RSC/MP Transport (Piccolo) Network Interface Section ([NIF-nifname]) 10-3 SPX Example PIPE.INI Configuration Files 10-9 11. Managing the RSC/MP Transport (Piccolo) Running the PIPECP Program PIPECP Commands 11-2 11-1 12.
14.
B. Installation Troubleshooting Migrating from RSC 5.0 and Previous Versions to RSC/MP 7.2 A-6 Using RSC/MP 6.3 to Migrate A-6 Migrating the Host and Client Directly to RSC/MP 7.2 A-7 Migrating Connectivity Options A-8 Method 1: Moving Connectivity Settings to Piccolo A-8 Method 2: Using Compatibility Mode A-9 Discontinued RSC.INI Options A-16 B. Installation Troubleshooting Notes About Diagnostic Clues B-1 How to Test the Configuration B-1 How to Trace Errors B-2 Step 1.
E. Resolver Reference Tags Counting D-2 Parameter Substitution D-2 Sending and Receiving Data D-2 Script Language Commands D-3 Counter Command D-3 Disconnectstring Command D-3 GOTO Command D-3 IF [NOT] Command D-3 MESSAGE Command D-4 RETURN Command D-4 SEND Command D-4 SET Command D-4 WAIT Command D-5 Sample Scripts D-6 E.
Index HP NonStop Remote Server Call (RSC/MP) Installation and Configuration Guide—522358-011 8
Figures Figures Figure 1-1. Figure 5-1. Figure 5-2. Figure 5-3. Figure 13-1. Figure A-1. Figure B-1. Figure F-1. Figure F-2. Figure F-3. Figure F-4. Figure F-5. Figure F-6. Figure F-7.
Figures HP NonStop Remote Server Call (RSC/MP) Installation and Configuration Guide—522358-011 2
Tables Tables Table 1-1. Table 1-2. Table 1-3. Table 1-4. Table 3-1. Table 4-1. Table 6-1. Table 6-2. Table 9-1. Table 12-1. Table 12-2. Table 13-1. Table 13-2. Table 13-3. Table A-1. Table A-2.
