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-13
Message Descriptions
the SCREEN COBOL program. If ON ERROR clause is not mentioned, TCP suspends
the terminal after logging the error against the term; however, the term can be resumed
to restart processing at the last verb.
Recovery. If the associated file-system error is 100 then it means that the LINKMON
process is just started on the CPU and is not yet ready to accept the Pathsend
requests. The term must retry the operation after a time delay. If associated file-system
error is 30, then it means that the outstanding incoming requests to the LINKMON
process have been reached. This is also a transient error and the term must retry the
operation.
3249
Cause. TCP abended while a SEND or a DIALOG I/O to server process was
outstanding and the term was not under transaction.
Effect. The operation fails. The server might or might not have received the message.
If ON ERROR clause is mentioned, 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, TCP aborts the terminal after logging
the error against the term. If the term is associated with any dialog, the dialog is also
aborted.
Recovery. Recovery is application specific. Since TCP does not know the status of
the last I/O hence the SEND/DIALOG operation can be retried if it is OK to send
duplicate message to the server class. Pathway/iTS 1.1 strongly recommends that the
send and dialog operations to server classes that do not allow duplicate messages
must be wrapped under TMF transactions.
3250
Cause. The context sensitive programming protocol has been violated by the
SCREEN COBOL program. The possible causes of this error are:
*3249* TCP FAILED WHEN A SEND/DIALOG TO SERVER WAS
OUTSTANDING
Note. This error does not appear in the RETCODE token or in an error list; it appears
only in response to the STATUS TCP or STATUS TERM command.
*3250* DIALOG MODE VIOLATION
Note. This error does not appear in the RETCODE token or in an error list; it appears
only in response to the STATUS TCP or STATUS TERM command.