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
Client Error Messages
HP NonStop Pathway/iTS Web Client Programming Manual—520270-003
A-15
Message Descriptions
Effect. The operation fails. If ON ERROR clause is mentioned, then error is reported
against the term but the term continues to run depending on the error-handling logic in
the SCREEN COBOL program. If ON ERROR clause is not mentioned, then TCP
aborts the terminal after logging the error against the term.
Recovery. Clean up the requester portion of dialog by calling DIALOG-END and
initiate a new dialog if required.
3253
Cause. A dialog statement has hit a dialog related error. Possible causes of this error
are:
•
A DIALOG-BEGIN or DIALOG-SEND statement failed because either the server
requested a dialog abort or the server abended before replying to the transaction
request.
•
A DIALOG-SEND statement failed because the dialog has already been ended or
aborted.
•
A DIALOG-BEGIN or DIALOG-SEND statement failed because the associated
transaction has been aborted which caused the dialog to be aborted as well.
Effect. The operation fails. If ON ERROR clause is mentioned, then error is reported
against the term but the term continues to run depending on the error-handling logic in
the SCREEN COBOL program. If ON ERROR clause is not mentioned, then TCP
aborts the terminal after logging the error against the term.
Recovery. Clean up the requester portion of dialog by calling DIALOG-END and
initiate a new dialog if required.
3300
Cause. The TCP/IP socket connection was not established by invoking the
GatewayInitateConnection class before sending a request to the terminal control
process (TCP).
Effect. The applet stops.
Recovery. Isolate and correct the problem within the Java program, using the stack
trace information in
error-loc
to locate the problem. Alternatively, correct the
problem in the SCREEN COBOL program and reconvert the application.
*3253* ERROR OCCURRED DURING DIALOG VERB EXECUTION (errnum)
*3300* CONNECTION NOT ESTABLISHED WITH GATEWAY REQUESTER
THREAD
error-loc