Files > HL COMMUNICATION SERVER PARAMETERS

name
HL COMMUNICATION SERVER PARAMETERS
number
869.3
location
^HLCS(869.3,
description
Parameter file used by the HL7 Communication Server
Fields
#NameLocationTypeDetailsIndexDescription
.01one(+)0;1NUMERICBStub field used to create one [and only one] entry
.02domain0;2POINTER4.2The domain name for this environment must be unique to all environments running at your site. For example, if your production domain is SITE.DOMAIN.EXT and this is your test system, you must have an entry in your domain file that is different such as TEST.SITE.DOMAIN.EXT.
.03default processing id(+)0;3SET OF CODESP:production
T:training
What type of environment is this account? The messaging system will not permit messages to be sent from one type of environment to a different type. The third Processing ID used by HL7 is DEBUG. This mode must be defined on the EVENT DRIVER protocol on both the sending and receiving systems. An error will be logged when the PID for an inbound message is inappropriate for the receiving system. Note: Ideally, TRAINING and PRODUCTION designations are maintained in separate accounts. Application processing routines should be aware of the PID field when processing a message. Routines designed for a production environment will probably want to process messages differently when TRAINING or DEBUG mode is set.
.04institution0;4POINTER4This entry will be used in the sending facility field of HL7 message headers unless the application overrides this function by defining a facility in the Application Parameter file.
.05mail group0;5POINTER3.8This mail group should contain local IRM staff responsible for monitoring the messaging system. This group will be used for delivery of alerts or notification of significant events related to Messaging System operations.
11default number incoming filers1;1NUMERICThis is the default number of background filers that will be started
12default number outgoing filers1;2NUMERICThis is the default number of outgoing filers that will be started
20incoming filer task number2;0MULTIPLE869.32
30outgoing filer task number3;0MULTIPLE869.33
41purge completed messages4;1NUMERICThe number of days "Successfully Completed" messages are retained before they are purged. If no value is entered, the default is 7 days. Used as the actual value when the "Purge Messages" option is scheduled through TaskMan, and as the default when run interactively.
42purge awaiting ack messages4;2NUMERICThe number of days "Awaiting Application Acknowledgement" messages are retained before they are purged. If no value is entered, the default is 30 days. Used as the actual value when the "Purge Messages" option is scheduled through TaskMan, and as the default when run interactively.
43purge all messages4;3NUMERICThe number of days that any status message are retained before they are purged(except for ERROR status messages). If no value is entered, the default is 90 days. Used as the actual value when the "Purge Messages" option is scheduled through TaskMan, and as the default when run interactively.
44purge error status messages4;4NUMERICThe number of days error status messages are retained before they are purged. 90 days is used as the actual value when the "Purge Messages" option is scheduled through TaskMan, and as the default when run interactively.
51default retention5;1NUMERICUsed by the TCP/IP Link Manager. The maximum time, in seconds, in which the process supporting a non-persistent TCP/IP client logical link will wait for new messages before terminating. Upon expiration of the retention time, the process will terminate, and the logical link will become inactive and remain inactive until further messages are queued. The value entered here is the DEFAULT RETENTION time. This value will be used if the RETENTION field (#400.05) in the HL LOWER LEVEL PROTOCOL PARAMETER file (#869.2) is not valued for a given LLP. If no value has been entered in both DEFAULT RETENTION and RETENTION fields for a given non-persistent LLP, a default time of 15 seconds will be used as the retention time.
52link manager task number5;2NUMERICThis field is internally edited by the Link Manager. When the Link Manager starts, this field is updated with the value of the Link Manager's task number.
53stop link manager5;3BOOLEAN0:NO
1:YES
Flag indicating whether the Link Manager should be stopped. This field is updated by the TCP/IP Link Manager as well as through the TCP/IP Link Manager Start/Stop option. Use this option rather than directly editing this field to start/stop the TCP/IP Link Manager.
54lm last known $h5;4FREE TEXTThis field is updated periodically by the Link Manager with the $Horolog value at the time of the update. The Systems Link Monitor uses this information along with the LINK MANAGER TASK NUMBER to determine whether the Link Manager is running. Therefore, the use of this field should be restricted for internal use only and should not edited.
60link monitor views6;0MULTIPLE869.31Use this multiple to define VIEWS that can be used in the System Link Monitor option. A VIEW is a list of Logical Links to display in the System Link Monitor.
70ping ip7;0MULTIPLE869.34
80ping domain (partial)8;0MULTIPLE869.35
90don't ping port9;0MULTIPLE869.36
91don't ping link name (partial)10;0MULTIPLE869.391
92don't ping ip11;0MULTIPLE869.392
93don't ping domain (full)12;0MULTIPLE869.393
772last ien, file 772772;1NUMERICThis field holds an IEN, which can be a whole number up to 19 digits. This field is used by HL7 process to create and store the IEN for file #772. It can't be altered. Otherwise, it may cause serious problem to the message transaction when HL7 process is running.
773last ien, file 773773;1NUMERICThis field holds an IEN, which can be a whole number up to 19 digits. This field is used by HL7 process to create and store the IEN for file #773. It can't be altered. Otherwise, it may cause serious problem to the message transaction when HL7 process is running.

Not Referenced