HL7 Comm 0.8.5 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News HL7 Comm 0.8.5 (Default branch)
# 1  
Old 07-18-2008
HL7 Comm 0.8.5 (Default branch)

HL7 Comm is a stand-alone integration tool written in Java that allows you to send and receive HL7 messages over a TCP/IP MLLP connection. It offers a simple mode for testing and a configured mode for running as a full-fledged integration client, either with or without a GUI interface. License: GNU General Public License (GPL) Changes:
A bug with the logging mechanism in the 0.8 series has been corrected. A new InboundTrigger mechanism has been added to support applications that may wish to poll other services without a normal triggering event.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

4 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

HL7 MLLP Sender in C

Hi Everyone, This is a pretty big request, but I was wondering if anyone out there has a program written in C, Perl, Tcl or whatever that can be executed from the command line and will send HL7 messages from a NL delimited file and send them to the specifid host/port using the MLLP HL7 TCP... (1 Reply)
Discussion started by: troym72
1 Replies

2. UNIX for Dummies Questions & Answers

help in comm command

Hi all, I need help in comm command , I am having 2 files . I have to display the common line in the two file only onnce and i have to also display the non common line as well. tmpcut1 -- First file cat tmpcut1 smstr_303000_O_432830_... f_c2_queue_sys30.sys30 RUNNING 10 1000... (1 Reply)
Discussion started by: arunkumar_mca
1 Replies

3. Shell Programming and Scripting

comm with a variable

Hello all, I have two flat files that are colon delineated and I am trying to run a compare (Solaris v8 ksh) of $1 within a script to access a mysql database based on the results. Unix is telling me that it has to have physical file names. Is there a way to run a compare using variables? This is... (3 Replies)
Discussion started by: gozer13
3 Replies

4. Shell Programming and Scripting

comm ?!

Hi, I have two large files with uid's: - 581004 File1.txt - 292675 File2.txt I want to know which uid's are in File1.txt and not in File2.txt. I have used comm -23 File1.txt File2.txt. This should do the trick i thought. But in the output i keep having uid's in File1.txt that are also in... (8 Replies)
Discussion started by: tine
8 Replies
Login or Register to Ask a Question
MPI_Sendrecv(3OpenMPI)													    MPI_Sendrecv(3OpenMPI)

NAME
MPI_Sendrecv - Sends and receives a message. SYNTAX
C Syntax #include <mpi.h> int MPI_Sendrecv(void *sendbuf, int sendcount, MPI_Datatype sendtype, int dest, int sendtag, void *recvbuf, int recvcount, MPI_Datatype recvtype, int source, int recvtag, MPI_Comm comm, MPI_Status *status) Fortran Syntax INCLUDE 'mpif.h' MPI_SENDRECV(SENDBUF, SENDCOUNT, SENDTYPE, DEST, SENDTAG, RECVBUF, RECVCOUNT, RECVTYPE, SOURCE, RECVTAG, COMM, STATUS, IERROR) <type> SENDBUF(*), RECVBUF(*) INTEGER SENDCOUNT, SENDTYPE, DEST, SENDTAG INTEGER RECVCOUNT, RECVTYPE, SOURCE, RECVTAG, COMM INTEGER STATUS(MPI_STATUS_SIZE), IERROR C++ Syntax #include <mpi.h> void Comm::Sendrecv(const void *sendbuf, int sendcount, const Datatype& sendtype, int dest, int sendtag, void *recvbuf, int recvcount, const Datatype& recvtype, int source, int recvtag, Status& status) const void Comm::Sendrecv(const void *sendbuf, int sendcount, const Datatype& sendtype, int dest, int sendtag, void *recvbuf, int recvcount, const Datatype& recvtype, int source, int recvtag) const INPUT PARAMETERS
sendbuf Initial address of send buffer (choice). sendcount Number of elements to send (integer). sendtype Type of elements in send buffer (handle). dest Rank of destination (integer). sendtag Send tag (integer). recvcount Maximum number of elements to receive (integer). recvtype Type of elements in receive buffer (handle). source Rank of source (integer). recvtag Receive tag (integer). comm Communicator (handle). OUTPUT PARAMETERS
recvbuf Initial address of receive buffer (choice). status Status object (status). This refers to the receive operation. IERROR Fortran only: Error status (integer). DESCRIPTION
The send-receive operations combine in one call the sending of a message to one destination and the receiving of another message, from another process. The two (source and destination) are possibly the same. A send-receive operation is useful for executing a shift operation across a chain of processes. If blocking sends and receives are used for such a shift, then one needs to order the sends and receives cor- rectly (for example, even processes send, then receive; odd processes receive first, then send) in order to prevent cyclic dependencies that may lead to deadlock. When a send-receive operation is used, the communication subsystem takes care of these issues. The send-receive operation can be used in conjunction with the functions described in Chapter 6 of the MPI-1 Standard, "Process Topologies," in order to perform shifts on various logical topologies. Also, a send-receive operation is useful for implementing remote procedure calls. A message sent by a send-receive operation can be received by a regular receive operation or probed by a probe operation; a send-receive operation can receive a message sent by a regular send operation. MPI_Sendrecv executes a blocking send and receive operation. Both send and receive use the same communicator, but possibly different tags. The send buffer and receive buffers must be disjoint, and may have different lengths and datatypes. If your application does not need to examine the status field, you can save resources by using the predefined constant MPI_STATUS_IGNORE as a special value for the status argument. ERRORS
Almost all MPI routines return an error value; C routines as the value of the function and Fortran routines in the last argument. C++ func- tions do not return errors. If the default error handler is set to MPI::ERRORS_THROW_EXCEPTIONS, then on error the C++ exception mechanism will be used to throw an MPI:Exception object. Before the error value is returned, the current MPI error handler is called. By default, this error handler aborts the MPI job, except for I/O function errors. The error handler may be changed with MPI_Comm_set_errhandler; the predefined error handler MPI_ERRORS_RETURN may be used to cause error values to be returned. Note that MPI does not guarantee that an MPI program can continue past an error. SEE ALSO
MPI_Sendrecv_replace Open MPI 1.2 September 2006 MPI_Sendrecv(3OpenMPI)