Pathway/iTS Web Client Programming Manual (H06.03+, J06.03+)
Table Of Contents
- HP NonStop Pathway/iTS Web Client Programming Manual
- Legal Notices
- Contents
- What's New in This Manual
- About This Manual
- 1 Introduction to Pathway/iTS Web Clients
- 2 How to Compile, Build, and Maintain a Pathway/iTS Web Client
- 1. Prepare the SCREEN COBOL Object File
- 2. Create a Configuration File
- 3. Run the Converter
- 4. Modify Java or SCREEN COBOL Code as Needed
- 5. Run PROFDBM to Set Up the User Profile Database
- 6. Build the Converted Client
- 7. Deploy the Web Client
- 8. Customize the Screens
- 9. Specify the Port Number of the Router Process
- 10. Configure Pathway Servers for User Profiles and User Conversion Routines
- 11. Tune the Application for Performance by Changing the Session-Length Parameter
- 12. Maintain the Client
- 3 Logon Security and User Profiles
- 4 User-Written User Conversion Procedures for Web Clients
- 5 SCREEN COBOL-to-Web Conversion Mappings
- 6 Java Import Package Reference
- 7 Introduction to Pathway/iTS 1.1
- A Client Error Messages
- B SCREEN COBOL Features Not Supported for Web Conversion
- Index
- Content Feedback
Introduction to Pathway/iTS 1.1
HP NonStop Pathway/iTS Web Client Programming Manual—520270-003
7-7
Statistics Collected by Pathway/iTS 1.1
Statistics Collected by Pathway/iTS 1.1
In PATHTCP4, the statistics collected are different from PATHTCP3. PATHTCP4 does
not generate statistics for SERVER objects. TS/MP ROUT processes generate
SERVER object statistics. For details on how the TS/MP ROUT processes generate
SERVER object statistics, see the
TS/MP System Management Manual
, or
TS/MP
Supplement for Limits Relief Manual
depending on the ROUT process running on your
system. TCP STATS ON attributes to collect server statistics are ignored in
PATHTCP4.
TCP object statistics collected by PATHTCP4 are different from those of PATHTCP3. In
PATHTCP4, the QUEUE INFO statistics collection for TCP object has changed.
PATHTCP4 does not perform any link management activity and hence the LINK and
DELINK statistics are not collected. No value will be displayed for LINK and DELINK
fields. All other fields in QUEUE INFO continue to be displayed as in PATHTCP3.
Example 7-1. Sample TCP Statistics for QUEUE INFO.
Fault Tolerance in Pathway/iTS 1.1
In terms of the level of fault tolerance, there is a difference in behavior in PATHTCP4
compared to PATHTCP3 in case TCP runs as process pair and the primary TCP fails
while a SEND or a Dialog is outstanding. HP suggests the PATHTCP3 users to
recognize this change in behavior and change the application, if required, before
migrating to the new environment.
When PATHTCP4 is configured as a process pair and the primary TCP fails, the
terminals controlled by the TCP can still be used. However, if a SEND or a dialog to a
server class is outstanding when the primary TCP fails then the recovery procedure
depends on whether or not TMF subsystem was used for database consistency, that is
whether or not the SEND was done after a successful call to BEGIN-TRANSACTION.
If the SEND is being done under TMF transaction, backup TCP, after take over, logs a
message to PATHMON, aborts the current transaction and reissues the entire
transaction from BEGIN-TRANSACTION statement in SCOBOL program.
If the SEND is not protected under TMF, the backup TCP, after take over, logs an error
message to PATHMON and then reports another error (TERMINATION-STATUS 24) to
TCP TCPX2 02 DEC 2006, 14:03:02
INTERVAL 5 SECS COUNT 2/5
.
.
.
QUEUE INFO: REQ CNT %WAIT MAX WAITS AVG WAITS
TERMPOOL 816 0.0 0 0.00
SERVERPOOL 3095 0.0 0 0.00
MEMMAN 1176 1.3 1 0.01
LINK -- -- -- --
DELINK -- -- -- --
CHECKPOINT 320 0.0 0 0.00