Pathway/iTS SCREEN COBOL Reference Manual (H06.10+, J06.03+)
Procedure Division
HP NonStop Pathway/iTS SCREEN COBOL Reference Manual—426750-003
6-36
DIALOG-BEGIN
TERMINATION-STATUS 25
Cause. While executing a DIALOG-ABORT statement, TCP could not connect to the
ROUT process because of a retryable ROUT connect error. Typical file-system errors
are FENOTRDY, FENOLCB and FETOOMANY. The message did not reach the server
process. Since the errors are retryable, the SCOBOL requester can retry the operation
after some time delay. The TERMINATION-SUBSTATUS special register stores the
file system error.
Action Without ON ERROR Clause. The system suspends the terminal. However,
the terminal can be resumed.
DIALOG-BEGIN
The DIALOG-BEGIN statement initiates a dialog with a Pathway server process in the
directed server class. Optionally, the DIALOG-BEGIN statement sends a transaction
request message to the server process and receives a reply from the same. The
DIALOG-BEGIN statement includes the message and a list of reply specifications.
In processing the DIALOG-BEGIN statement, the TCP retains the reply code values
that are to be used when the server sends a reply. On receiving a reply, the TCP
compares the reply code value with the list of reply code values and determines which
reply was received and, consequently, determines the structure of the data. Then, the
TCP copies the reply into the SCREEN COBOL program. A dialog initiated in any
program unit within the SCOBOL program can be used, ended, or abended by any
other program unit within the same SCOBOL program. Only one active dialog per
terminal is allowed in Pathway/iTS 1.1 release. If a SCREEN COBOL program
attempts to issue more than one dialog per terminal, irrespective of whether the ON
ERROR clause is specified or not, TCP abends the terminal after logging the error to
PATHMON. Any active dialog from the terminal including the transaction will also
abend.
RETRYABLE ROUT CONNECT ERROR
Note. The TERMINATION-SUBSTATUS special register contains the file-system error.
DIALOG-BEGIN [
identifier-1
] ,... TO
server-class-name
[ UNDER PATHWAY
pathmon-name
]
[ AT SYSTEM
system-name
]
[ REPLY { CODE {
reply-code-value
} ...
YIELDS [ VARYING ] {
identifier-2
} ... } ...
CODE OTHER YIELDS [ VARYING ] {
identifier-2
} ...
[ ON ERROR
imperative-statement
]