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-8
Error Handling in Pathway/iTS 1.1
the SCOBOL program provided the ON ERROR clause is specified. The processing of
SCOBOL program continues in this case depending on the error handling logic of the
program. If the ON ERROR clause is not specified, the backup TCP after take over
aborts the terminal. In most cases, this requires an operator intervention to correct the
situation. If this situation happens at any time, PATHTCP4 does not have any status
about the state of the initiated SEND operation. Manual intervention is required to find
the state of the last SEND and to see if duplicate SENDs can be reissued by restarting
the terminal.
PATHTCP4 strongly suggests SCOBOL programs to wrap up non-retryable database
operations under TMF. This would help in maintaining database consistency and in
normal operation of PATHTCP4.
Similarly, if a dialog is active under TMF transaction and primary TCP abends before
the dialog could end, the back up TCP after take over logs a message to PATHMON,
aborts the current transaction, and reissues the whole transaction from the BEGIN-
TRANSACTION statement in SCOBOL program.
If the dialog is not protected under TMF, back up TCP, after take over, logs an error
message to PATHMON and reports an error (TERMINATION-STATUS 24) to SCOBOL
program provided the ON ERROR clause is specified. The processing of SCOBOL
program continues in this case depending on the error handling logic of the program. If
the ON ERROR clause is not specified, back up TCP after take over aborts the
terminal. In most cases, this requires an operator intervention to correct the situation. If
this situation occurs at any time, PATHTCP4 does not have any status about the state
of the initiated dialog. Manual intervention is required to find the state of the dialog and
to see if duplicate dialogs can be reissued by restarting the terminal.
Error Handling in Pathway/iTS 1.1
TERMINATION STATUS or SUB-STATUS register values are set by PATHTCP4 for the
SEND verb. These values are generated for the DIALOG-BEGIN, DIALOG-SEND,
DIALOG-END and DIALOG-ABORT verbs also. For the termination status values, see
the
Pathway/iTS SCREEN COBOL Reference Manual
.