H06.13 Software Installation and Upgrade Guide

NOTE: All NonStop SQL/MX objects must reside on volumes audited by TMF. NonStop SQL/MX
program files do not need to reside on audited volumes.
Before installing NonStop SQL/MX, review the instructions for preinstalling and installing NonStop
SQL/MX provided in the SQL/MX Installation and Management Guide.
Pathway/iTS 1.1
Pathway iTS/1.1, introduced in the H06.10 RVU, supports the following 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.
OSI FTAM and MHS Longer Password Support
Starting with the H06.10 RVU, the OSI FTAM (T6982) and MHS (T7937) products support
passwords up to 64 bytes long. The passwords can also include special characters. To use these
features, the Standard Security T6533H04 SPR or later must be installed.
H06.11
Safeguard Logon Without a Password
Starting in the H06.11 RVU, is enhanced to allow users to logon without a password. (This capability
can be used only if the SUPER.SUPER user has granted the program file that permission through
Safeguard.)
Migration
There are no migration or fallback considerations specific to the new logon feature. However, you
can use the mitigation procedure described under “Migration in a Safeguard Environment”
(page 49) to handle any unexpected failures that might occur when migrating to the new version
of Safeguard.
For more information, see Chapter 10 of the Safeguard Administrator's Manual.
56 H06.13 Installation, Migration, and Fallback Considerations