The process registry is used by the HLO process manager to start, stop, and manage all of the processes used by the HLO system.
.01process name(+)0;1FREE TEXTBA unique name for the type of process.
CA flag that indicates whether or not this type of process is active under the HLO Process Manager. Some processes may not apply to some systems, for example, a particular site may not use the Taskman multi-listener.
.03minimum active processes0;3NUMERICThis field indicates the minimum number of concurrent processes of this type. The exact number changes as the HLO Process Manager starts and stops processes in response to changes in workload.
.04maximum active processes0;4NUMERIC
.05scheduling frequency (minutes)0;5NUMERICThis is how long the Process Manager should wait between checks to see if another process of this type should be started.
.06dt/tm last started or stopped0;6DATE-TIMEThe date and time when a process of this type was last started or stopped.
.07hang time (seconds)0;7NUMERICThis is how long a process should wait between attempts to find work to do.
.08get work function (tag)(+)0;8FREE TEXTThe M entry point to the GET WORK function for this process type.
.09get work function (routine)(+)0;9FREE TEXTThe routine in which this process type has located its GET WORK function.
.1do work function (tag)0;10FREE TEXTThe M entry point for the process's DO WORK function.
.11do work function (routine)0;11FREE TEXTThe routine in which the process's DO WORK function is located.
.12max tries finding work0;12NUMERICHow many times should the process look for work and then quit if it cannot find anything to do? It'll hang between attempts the specified length of time.
Setting this field to YES results in the process being made persistent via the Taskman persistent parameter.
.14dedicated link0;14FREE TEXTThe primary use of this field is for TCP/IP listener processes, and indicates which port (via the HL Logical Link) that the process should be listening on. However, it could be used to dedicate a client link process to a particular link.
.15vms tcp service0;15BOOLEAN1:YES
VMS services are not started or stopped via the HL7 Process Manager. However, on a VMS system, these services are an important part of the HL7 system, and so an entry in the HL7 Process Registry should be created for them. The Process Manager will use the PING functionality to verify that the listener is running.
.16box-volume pair0;16POINTER14.7The BOX-VOLUME PAIR field (#13) in the HLO SYSTEM PARAMETERS file (#779.1) may be used to optionally specify the node that the HL7 (optimized) software should run on. The BOX-VLUME PAIR field (#16) of the HLO PROCESS REGISTRY file (#779.3) may be used to optionally specify the ndoe that a specify type of HL7 (optimized) software should execute on. If this field has a value, it will override the value in the HLO SYSTEM PARAMETERS file (#779.1) for this type of HLO process. It is generally not necessary to designate which node an HLO process will execute on. The primary exception may be to allow a Cache/NT site to utilize multiple listeners running on multiple nodes. Cache/VMS sites should not utilize listeners running under the HLO Process Manager. Instead, those sites should utilize the VMS TCPIP Services. If desired for load balancing, such a service may be run on multiple nodes. The BOX-VOLUME PAIR parameters do NOT affect listeners that utilize the VMS TCPIP Services.

Not Referenced