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-6
FREEZE SERVER Command Changes
register) and prohibits the link managers (LINKMON processes) from sending requests
to a server class. If a server process has incomplete requests or is in active dialog, the
PATHMON process cannot freeze the server class until these requests are completed.
While waiting for the requests to complete, the server class goes into a FREEZE-
PENDING state. If no incomplete or outstanding requests exist for any server in the
server class, the PATHMON process immediately freezes the server class.
In addition to supporting the special registers in Pathway/iTS 1.0, Pathway/iTS 1.1
includes a special register for providing information about the dialog verbs.
DIALOG-INFO Special Register
The DIALOG-INFO special register communicates with the dialog status of a requester
program. In other words, this special register helps to communicate whether a terminal
is under active dialog or not. A copy of this register is available to each terminal. The
register is initialized to 65535 each time the requester program is called and can
contain only three possible values. Here is a summary of the possible values for this
special register, their meanings and action to be taken by the requester program.
FREEZE SERVER Command Changes
As PATHTCP4 is a Pathsend requester and does not execute any link management
operation, the SCREEN COBOL STOP-MODE special register value is ignored for the
FREEZE SERVER command. This behavior also implies that the bang command ‘!’ in
FREEZE SERVER command does not have any effect in PATHTCP4.
PATHTCP3 queues all the SEND tasks targeted at a frozen server class. The queued
tasks are processed once the server class is thawed. PATHTCP4 behaves differently in
the above case. If a SCREEN COBOL requester, running under PATHTCP4, attempts
to send to a frozen serverclass and the SEND/DIALOG-BEGIN/DIALOG-SEND
statement is coded without an ON ERROR clause, PATHTCP4 will abort the terminal. If
the terminal is in transaction mode, the associated transaction will also be aborted. If
ON ERROR clause is specified when PATHTCP4 hits this error, the SCOBOL
execution will continue according to the error handling logic specified in the program.
DIALOG-INFO
Register Value Meaning/Actions to be Taken
65535 The term is not under any active dialog. Either the term has not
started any dialog at all or the dialog has been ended or aborted
by the terminal.
0 (FEOK) The term is under active dialog. The last call to either DIALOG-
BEGIN or DIALOG-SEND was successful but the server has
ended the dialog from its end. The requester must end the dialog
now.
70 (FECONTINUE) The term is under active dialog. The last call to either DIALOG-
BEGIN or DIALOG-SEND was successful and the server has
expressed interest in continuing the dialog.