Pathway/iTS System Management Manual (H06.03, J06.03+)

What’s New in This Manual
HP NonStop Pathway/iTS System Management Manual—426748-005
xii
Changes in the H06.14/J06.03 Manual
°
Table 7-2 Commands and Objects on page 7-4
•
Added CONTROL TERM Commands on page 10-7.
•
Updated considerations of:
°
ABORT TERM command on page 10-3
°
STOP TERM command on page 10-41
•
Updated the format of the display returned by the STATUS TERM command on
page 10-37.
•
Updated information about display format of the STATUS TERM command on
page 10-38.
•
Added Synchronous Upgrade for SCOBOL Applications on page 10-44.
Changes in the H06.14/J06.03 Manual
•
Supported release statements have been updated to include J-series RVUs.
•
Added the description for:
•
Wild Card Support for TCP Commands
•
Wild Card Support for TERM Commands
•
Wild Card Support for PROGRAM Commands
Changes in the H06.10 Manual
Added error messages, 3246 to 3253 on page 13-56.
Product Changes
Pathway/iTS 1.1 provides large message (more than 32000 bytes) communication
support between the SCOBOL requesters or converted Java clients and the Pathway
servers. The large message communication support is available to the TS/MP
Pathsend requesters in the form of Dialog styled communications
(SERVERCLASS_DIALOG_* APIs). The TCP component of Pathway/iTS 1.1 is called
PATHTCP4, which uses SERVERCLASS_SEND_* APIs for the processing of the
SEND verb for SCOBOL requesters and converted Java clients. PATHTCP4 does not
communicate to either the owner or external PATHMON process for link management
activities. Instead of performing Guardian WRITEREAD on Pathway server processes
to communicate with them, PATHTCP4 becomes a Pathsend requester and uses
Pathsend APIs to communicate with Pathway servers. Therefore, any existing
Pathway/iTS 1.0 application can be used along with Pathway/iTS 1.1 with no or
minimal changes to the applications. PATHTCP4 also supports four SCOBOL verbs-
DIALOG-ABORT, DIALOG-BEGIN, DIALOG-END, and DIALOG-SEND (for both
SCOBOL requesters and converted Java clients) that resemble dialog styled
communications in Pathsend requesters. PATHTCP4 uses