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-17
Message Descriptions
3304
Cause. An invalid parameter value was passed.
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.
3305
Cause. The program attempted to communicate with a host NonStop system that was
unknown.
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.
3306
Cause. A TCP/IP I/O exception occurred during a read or write on a socket.
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.
3307
Cause. A fatal error occurred while the terminal control process (TCP) was attempting
to start a transaction.
Effect. If the ON ERROR clause of the BEGIN-TRANSACTION statement is present
in the SCREEN COBOL source code—that is, if the onTxnErrorMethod method is
present in the Java code—then the ON ERROR branch is taken. Otherwise, the applet
stops.
*3304* INVALID PARAMETER
error-loc
*3305* UNKNOWN HOST
error-loc
*3306* ERROR DURING I/O ON SOCKET
error-loc
*3307* FATAL ERROR DURING BEGIN TRANSACTION
error-loc