TRANSFER Release D30 Documentation Supplement

File Formats
1-16 118474—TRANSFER Release D30 Documentation Supplement
TRANSFER D30 Documentation Supplement
•
DEQ-D30, ENQ-D30, READQ-D30, ENQ-TIMED-D30 UOWs.
TRANSFER is converted for use in D20 in the following way:
•
All calls to superseded Guardian PROCs have been converted.
•
New type system messages from $RECEIVE will be handled.
•
All external interfaces that now use CPU-PIN will be converted to use process
handle.
•
Certain processes will be forced to run at low PINs to avoid problems with down-rev
nodes.
Support for High PIN Requesters
Many TRANSFER customers write Pathway applications in SCREEN COBOL that run
as requesters to TRANSFER servers. The previously mentioned changes to $RECEIVE
handling enable these requesters to run at high pins.
TRANSFER Processes and Low and High PIN Use
TRANSFER processes and many servers now run at high pins. Some servers are forced
at bind time, to run at low PINs in order to avoid problems with the following processes:
•
EXPRTSRV
•
IMPRTSRV
•
GFSERV
•
PSSERV
In a mixed network, while some nodes are running D30 TRANSFER and some are
running versions earlier than D30, all processes must be running at low PINs. Setting a
new parameter TRSetHighPin to YES in TRDEFLTS allows all TRANSFER processes
to run at high PINs except EXPRTSRV, IMPRTSRV, GFSERV, and PSSERV which
always run at low PINs.
File Formats
In order to support high PIN requesters in the Queue Manager facility, the Queue File
record layout must include a process handle. By using the FILLER field that follows the
CPU-PIN, you accomplish. The record layout and Full-Key changes, but the record
length and file size does not.
To use the D30 Queue Manager, no conversion is needed. The value of KEYLEN for the
new queue file increases from 56 to 76 because of the increase in size for Full-Key.
When the D30 Queue Manager starts up, it checks the queue file. If the queue file is in
the old format, the message “File xxxx is a pre-enlightened queue file” is logged. If the
Queue Manager is running high PIN and the queue file is in the old format, the Queue
Manager logs a message “Queue Manager is running at a high PIN” and then stops.
Only old UOWs are allowed if the queue file is in the old format. Similarly, new UOWs