H06.10 Software Installation and Upgrade Guide

Pathway/iTS 1.1
The H06.10 RVU introduces Pathway/iTS 1.1. Pathway iTS\1.1 supports the following new
SCOBOL statements:
• DIALOG-BEGIN
• DIALOG-SEND
• DIALOG-ABORT
• DIALOG-END
These statements enable users to send more than 32000 bytes of data to the same Pathway server
using a context-sensitive communication model.
These new features are provided by the PathTCP4 (T0700) component of Pathway/iTS.
Migration
Pathway/iTS 1.1 includes both PathTCP3 and PathTCP4. PathTCP3 is unchanged.
Migration to PathTCP4 is optional. If you select PathTCP4, examine the SCOBOL client programs
for error handling and, optionally, implement the new SCOBOL verbs for dialog-style
communication. To carry the new features to the converted Java clients, first convert the modified
SCOBOL application, and then deploy the converted application. To use the new features, you
must configure Path TCP4 as the TCP object in the Pathway environment configuration and
determine on which CPUs PathTCP4 will execute, since it is a Pathsend requestor.
Once modified for PathTCP4, an application cannot be used with PathTCP3.
PSTATE (T0705H01) and WHOHAS (T0706H01)
PSTATE and WHOHAS are two tools that are owned and supported by the Global Mission
Critical Solution Center (GMCSC). As of H06.03 and G06.26, these two tools are delivered to
customers on the SUT.
• PSTATE provides a snapshot of the status of a running process. It provides everything that
TACL STATUS, DETAIL does plus information about all files open by the process and what
I/Os are outstanding.
• WHOHAS provides a list of processes that have open files. WHOHAS gives the same
information as FUP LISTOPENS but can report on all files, devices and processes in the
system.
SANMAN and SNETMON
These two SCF SANMAN (T0502) displays have been enhanced:
• SCF INFO CONN $ZZSMN
• SCF STATUS CONN $ZZSMN
Previously, three SANMAN Event Management Service (EMS) events that called out a modular
ServerNet expansion board (MSEB) explicitly for S-series have been modified to report a more
generic text message.
Before an Integrity NonStop NS-series server node can be connected to an existing NonStop
ServerNet Cluster with S-series nodes, an upgrade to SNETMON SPR T0294AAP is required on
all S-series nodes if these nodes are not already running the minimum required T0294AAP SPR
or a subsequent SPR. Failure to install the minimum T0294AAP SPR on the S-series nodes prevents
those nodes from successfully discovering Integrity NonStop NS-series server nodes and
vice-versa, thereby preventing the establishment of Expand-over-ServerNet lines between S-series
and H-series server nodes.
T0294AAP can be installed online and does not require a system load.
46 H06.10 Installation, Migration, and Fallback Considerations