H06.10 Release Version Update Compendium

4 Database and Transaction Processing Products
The H06.10 RVU includes new features for these products:
• Pathway/iTS 1.1 and Web Client
• TMF 3.5
• SQL/MX 2.3
Pathway/iTS
Screen COBOL
The H06.10 RVU introduces Pathway/iTS 1.1. Pathway/iTS 1.1 supports several new SCOBOL
statements. These statements enable users to send more than 32000 bytes of data to the same
Pathway server using a context-sensitive (dialog_style) communication model
• DIALOG-BEGIN starts a dialog for the terminal
• DIALOG-SEND continues the dialog to send messages to the same server process
• DIALOG-ABORT aborts the dialog
• DIALOG-END cleans up resources after the server ends or aborts the dialog
A terminal initiates a dialog with a server process in a server class by making a DIALOG-BEGIN
statement. The terminal can continue the dialog and send messages to the same server process
by making one or more DIALOG-SEND statements. The Pathsend requestor-server programming
model governs the communication with the server. The requestor can abort the dialog by calling
DIALOG-ABORT. DIALOG-END is called to clean up resources after the server has ended or
aborted the dialog.
In addigion, the existing SEND verb is translated into a context-free Pathsend to the server class.
These new features are provided by the PathTCP4 (T0700) component of Pathway/iTS.
Web Client
The web client feature of Pathway/iTS 1.1 enables users to convert the new DIALOG verbs as
well as the old SCOBOL features to a Web client and then build and deploy the resulting client
in a Pathway environment. Due to the introduction of four SCOBOL verbs, the gateway class
has been updated with four new delegation methods.
Migration Issues
Migration to PathTCP4 is optional.
Pathway/iTS includes both PathTCP3 and PathTCP4. PathTCP3 is unchanged. If you select
PathTCP4, examine the SCOBOL client programs for error handling and, optionally, implement
the new SCOBOL verbs for dialog-style communication. To bring 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 PathTCP4 as the TCP object in the
Pathway environment configuration and consider on which CPUs PathTCP will execute, since
it is a Pathway requestor. If PathTCP3 is used, no changes are necessary since PathTCP3 is
unchanged.
Note that it is not necessary to migrate to a minimum RVU level prior to migrating to H06.10.
Migrating to PathTCP4 is optional. Both PathTCP4 and PathTCP3 can be configured in the same
Pathway environment. Hence, PathTCP3 is packaged with PathTCP4 to minimize any impact.
Pathway/iTS 15