| # | Name | Location | Type | Details | Index | Description |
|---|---|---|---|---|---|---|
| .01 | domain name(+) | 0;1 | FREE TEXT | B | The domain name for this system. It will be used to populate component 2 of the Sending Facility field of the HL7 message headers. | |
| .02 | station number | 0;2 | FREE TEXT | |||
| .03 | production id(+) | 0;3 | SET OF CODES | P:production T:training | ||
| .04 | maximum string length | 0;4 | NUMERIC | This parameter determines the maximum length for strings that HLO will create when messages are being built. It doesn't apply to servers, as the size of input buffer used by TCP/IP determines the maximum string length created by a single read. | ||
| .05 | buffer size for hl7 (bytes) | 0;5 | NUMERIC | |||
| .06 | buffer size for user (bytes) | 0;6 | NUMERIC | |||
| .07 | normal msg retention (days) | 0;7 | NUMERIC | This field controls how many days successful messages are retained after being fully processed before they are purged. The application may specify a longer time to retain its messages, which would override the time specified here. | ||
| .08 | bad message retention (days) | 0;8 | NUMERIC | This field controls the purging of HL7 messages that do not complete successfully. The period should be reasonably long to allow investigation, but because of the high daily volume of messages purging must occur as quickly as practical. | ||
| .09 | hlo on/off switch | 0;9 | SET OF CODES | 0:OFF 1:ON | ||
| .1 | hlo standard listener | 0;10 | POINTER | 870 | ||
| .11 | hlo recount on/off flag | 0;11 | SET OF CODES | 0:OFF 1:ON | ||
| .12 | unsent msg retention (days) | 0;12 | NUMERIC | |||
| .13 | box-volume pair | 0;13 | POINTER | 14.7 | The BOX-VOLUME PAIR parameter allows a site to specify which CPU and volume set the HLO processes should run on. This parameter only controls procesess started by the HLO Process Manager by calling the Taskmanager APIs. This parameter is optional. For VMS sites, this parameter generally does NOT control what node to run the listener on, because VMS sites should use VMS TCPIP Services for their listener. For Cache/NT sites using a load balancer, this parameter can be used to specify what node to run the listener on. |
Not Referenced