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-14
Message Descriptions
•
A second DIALOG-BEGIN was attempted when the term is already under active
dialog.
•
A DIALOG-SEND was attempted without the term being under active dialog.
•
A DIALOG-END was attempted without the term being under active dialog.
•
A DIALOG-ABORT was attempted without the term being under active dialog.
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. If the term is associated
with any dialog the dialog is also aborted.
Recovery. There is no recovery action on this. Correct the SCREEN COBOL program
and restart the term. For instructions on how to isolate the problem within the program,
see Additional Information for Terminal Errors at the beginning of this section.
3251
Cause. A DIALOG-END statement is called when the server has not yet ended the
dialog.
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. If the term is associated
with any dialog the dialog is also aborted.
Recovery. There is no recovery action on this. Correct the SCREEN COBOL program
to make sure that the DIALOG-END is called only after the server has ended the
dialog. For instructions on how to isolate the problem within the program, see
Additional Information for Terminal Errors at the beginning of this section.
3252
Cause. A DIALOG-SEND, DIALOG-END or DIALOG-ABORT statement is called and
it was found that the dialog has been aborted by the LINKMON process due to the
primary TCP failure.
*3251* DIALOG HAS NOT BEEN ENDED BY THE SERVER
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.
*3252* DIALOG HAS BECOME INVALID DUE TO A PRIMARY TCP FAILURE