TS/MP Pathsend and Server Programming Manual (G06.24+, H06.03+)

Examples
NonStop TS/MP Pathsend and Server Programming Manual–132500
B-3
Pathsend Requester Example
The following files are used by BREQ and must exist before running the
program:
INFILE -- each record is one transaction
OUTFILE -- the outcome of the transaction
ERROR LOG -- Entry sequenced; record length 132; not audited.
The physical file name is read from the ASSIGN
'ERROR-LOG-FILE'.
MESSAGE LOG -- Entry sequenced; record length 132; audited.
The physical file name is read from the ASSIGN
'MESSAGE-LOG-FILE'.
TRACE (OPTIONAL) -- Entry sequenced; record length 80; not
audited; may be a terminal, may not be a
spooler location ($S.#SOME.LOC). The physical
file name is read from the ASSIGN
'TRACE-FILE'.
The following ASSIGNS passed in:
ERROR-LOG-FILE
-- Used to record error msgs.
MESSAGE-LOG-FILE
-- A write to this file is part of a transaction. It contains
request msgs received by BREQ from DRIVER.
TRACE-FILE (OPTIONAL)
-- Used to log certain READs, SENDs, and TMF operations.
There can also be up to 50 ASSIGNs to give logical names to PATHMONs
that may be referenced in the input record.
The following PARAM is passed:
MAX-RETRIES
-- BREQ uses this number to calculate the number of times
it will try to recover from PATHSEND SEND failures.
Example run-line:
RUN BREQ/ NAME $BREQ, IN infile, OUT outfile/
The procedures on the following pages are listed in alphabetical
order.
?ENDIF 1
?PAGE "COMPILER DIRECTIVES, GLOBALS, AND EXTDECS"
?INSPECT, SYMBOLS, NOCODE
?LIST
?DATAPAGES 64