Temporary TCP/IP Sender/Receiver?

[Max Drown (Infor)]

Seems like I remember using a command line tool years ago that created a temporary tcp/ip sender or receiver process that could be used to send or receive HL7 messages to/from a Cloverleaf process without having to modify the NetConfig and adding a temporary thread. I can’t for the life of me remember the command or how it was used. Can someone refresh my memory?

-- Max Drown (Infor)

Topic

[Jim Kosloskey]

Max,

Are you thinking of hcitcptest?

Jim Kosloskey

email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

[Max Drown (Infor)]

That could be it. I’m not sure.

Code:

Usage: hcitcptest [-h hostname] [-f file] -t tcp_encoding_type -p port
Where:
   -n =  run in non-interactive mode, do not read from stdin
         should only be used in server mode
   -h =  an optional hostname to connect to
         If -h is not specified, hcitcptest will
         work as a server, listening on the port
         specified by the -p option

   -f =  an optional filename. All data recieved
         from the host will be written to this file.
         (Including any encoding characters)

   -t =  tcp_encoding_type
             one of:
                    2      2 byte length encoding
                    2e     2 byte length encoding (exclusive of encoding)
                    4      4 byte length encoding
                    4e     4 byte length encoding (exclusive of encoding)
                    orsos  ORSOS 2 byte length encoding
                    mlp    HL7 MLP encoding
                    raw    Data is sent “as-is” w/ Line Feed
                    nlf    Data is sent “as-is” w/o Line Feed

   -p =  port to listen on or connect to

How would that be used to send HL7 to a Cloverleaf thread?

-- Max Drown (Infor)

[Jim Kosloskey]

Max,

I will check with one of my colleagues. He did get the command to use a file which had HL/7 as input when using as a client I think.

Typically I use hcitcptest just for connectivity testing before I set anything up in Cloverelaf(R). After all, If I can’t connect via the command line utility, why waste time defining the NetConfig entry?

Jim Kosloskey

email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

[Jim Kosloskey]

Max,

Maybe you meant the old ‘blaster’ ‘catcher’ stuff.

I don’t even know if that is available any longer – I seem to recall that did not work very well in my experience.

Jim Kosloskey

email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

[Russ Ross]

Jim:

Your memory was correct that I used hcitcptest to send a HL7 message and here is the script I found that illustrates what I you referred to earlier:

Code:

#!/usr/bin/ksh

ip=’10.123.123.123′
port=’31022′

hcitcptest -h $ip
          -t mlp
          -p $port <<- ! MSH|^~&|the rest of the message segments !

I think I’ve also done interactive resending using hcitcptest by copying message to buffer and pasting into hcitcptest.  However, I might of had to change the to r before doing the interactive copy/paste.  A couple of tries should get you there if this is useful for you.  I have found it very usefull when wanting direct control to test connectivity, resend time out, and NAK behavior.

Russ Ross
RussRoss318@gmail.com

[Max Drown (Infor)]

Thanks!

-- Max Drown (Infor)

[Tim Wanner]

hl7_sndr: Portnum is required and must be > 1024

Usage: hl7_sndr -r portnum -f filename

         -b burstno -n nodenm -w t_delay

 where: portnum – is the tcp port number to use

        filename- is the filename to read data from

        burstno – number trans to send before wait

        nodenm  – name of node to connect to

        t_delay – delay in seconds between batches

hl7_rcvr: Portnum is required and should be > 1024

Usage: hl7_rcvr -p portnum -f filename -[c|a]

         -e ae_freq -r ar_freq -w ack_dly -m ack_dly_type

 where: portnum  – is the tcp port number to use

        -c|a  – commit or application ack’s

        filename – is the filename to store data in

        ae_freq  – frequency to send AE NAKs

        ar_freq  – frequency to send AR NAKs

        ack_dly  – delay in seconds before AA ACKs

        ack_dly_type – HL7 msg type to delay on

[Author]

Replies