This file contains the Lower Layer Protocol Parameters used by the HL7 package. Each protocol will use a separate node to hold the parameters associated will the LLP used by the Logical Link. The currently defined nodes are: 100 - MailMan 200 - HLLP 300 - X3.28 There may be redundant information contained on nodes, the goal was to allow the applications to grap a one node for all the parameters required. There should be an entry in this file for each Logical Link defined in file (#870). There is an x-ref "ALLP" defined for file (#870) to facilitate navigation from this file.
.01name(+)0;1FREE TEXTB
.02llp type(+)0;2POINTER869.1
100.01mail group100;1POINTER3.8
200.01hllp device200;1POINTER3.5
200.02re-transmision attempts200;2NUMERICEnter the number of times to re-try sending a message. The default is 5 tries if this field is left blank. If a single message exceeds this value an Alert is sent to the HL7 mail group and the link is shutdown.
200.03block size200;3NUMERIC
200.04read timeout200;4NUMERIC Number of seconds the Lower Layer Protocol remains in a read state for data to come in on the link. The default is 10 seconds if this field is left blank.
200.05ack timeout200;5NUMERIC The number of seconds the Lower Layer Protocol waits for an acknowledgement from the receiving application. If this field is less than the READ TIMEOUT field, the READ TIMEOUT value will be used.
200.06llp start block200;6SET OF CODES11:VT
200.07llp end block200;7SET OF CODES28:FS
200.08protocol id version200;8SET OF CODES21:2.1
200.09uni-directional wait200;9NUMERICThe number of seconds the Lower Layer Protocol waits after sending a messages. This is only used if the message doesn't want an acknowledgment.
300.01x3.28 device300;1POINTER3.5
300.02maximum message size300;2NUMERIC
300.03maximum block size300;3NUMERIC
300.04timer a300;4NUMERIC
300.05timer b300;5NUMERIC
300.06timer d300;6NUMERIC
300.07timer e300;7NUMERIC
300.08term300;8SET OF CODES13:CR
300.09soh300;9SET OF CODES01:SOH
300.1stx300;10SET OF CODES02:STX
300.11etb300;11SET OF CODES23:ETB
300.12etx300;12SET OF CODES03:ETX
300.13eot300;13SET OF CODES04:EOT
300.14enq300;14SET OF CODES05:ENQ
300.15rint300;15SET OF CODES60:RINT
300.16dle300;16SET OF CODES16:DLE
300.17nak300;17SET OF CODES21:NAK
300.18ack0300;18SET OF CODES48:ACK0
300.19ack1300;19SET OF CODES49:ACK1
300.2ack2300;20SET OF CODES50:ACK2
300.21ack3300;21SET OF CODES51:ACK3
300.22ack4300;22SET OF CODES52:ACK4
300.23ack5300;23SET OF CODES53:ACK5
300.24ack6300;24SET OF CODES54:ACK5
300.25ack7300;25SET OF CODES55:ACK7
400.01tcp/ip address400;1FREE TEXT
400.02tcp/ip port400;2NUMERIC
400.03tcp/ip service type400;3SET OF CODESC:CLIENT (SENDER)
This field determines if the Logical Link is the client (sender) or a listener (server) of a message. Choose from: CLIENT (SENDER): Indicates that this Logical Link connects to a target system, with the current system acting as the sender. SINGLE LISTENER: Designates that the current system is a server (listener), using a single M process to do the listening. MULTI LISTENER: Designates that the current system is a server (listener), creating multiple background processes.
Enter 'YES' if this connection needs to remain open even if there are no messages to send. The connection will remain open until it is disconnected by either side via shutting-down the logical link. A setting of 'YES' is appropriate for connecting to a COTS device with a high volume of messages.
400.05retention400;5NUMERICRetention is the maximum time in seconds in which a non-persistent LLP will wait after the associated queue has been emptied. If further messages arrive in the queue before the retention time has expired, the LLP will continue to dequeue and send messages. Otherwise, the LLP will become inactive and will remain inactive until further messages are queued.
400.06startup node400;6POINTER14.7This field is ONLY for VMS sites running Dual Taskman in DCL. This field is used to specify what Taskman node you want to job the Lower Level Protocol. It should only be used if you have two Taskmans running and only want the LLP to run on a particular node. It will only work if you are running the dual Taskmans in DCL context on a VMS system.

Not Referenced