Joe,

I use the Read and Write functions so I'm not sure if WRLINE has any
bearing on the problem. Just a SWAG, but it sounds like the other end
can't detect the beginning and/or end of the ack. The ack will need to use
the same beginning and end of message characters (x'0b' and x'1c0d') used
for the HL7. Also is there a need to do ebcdic to ascii and vise-versa
translations? I have to translate everything since all the systems I talk
to are ascii based.

Since the users at the other end can't do diagnosis, you may want to try a
utility called socket workbench (free for a 30 day trial, $160 to buy). It
will allow you to ensure your connection read and write process is working
as desired. This would allow you to send an HL7 to the socket workbench,
and socket workbench will in turn send you an ACK, You can then repeat
this as often as necessary to ensure your program is performing as
desired.

http://download.cnet.com/Socket-Workbench/3000-2218_4-10028746.html

Or the other product I mentioned 7Scan will also allow you to do similar
testing so that you can verify sending and receiving HL7 and the related
acknowledgement.

http://www.7scan.com/

Regards, Jerry

Gerald Kern - MIS Project Leader
Lotus Notes/Domino Administrator
IBM Certified RPG IV Developer
The Toledo Clinic, Inc.
4235 Secor Road
Toledo, OH 43623-4299
Phone 419-479-5535
gkern@xxxxxxxxxxxxxxxx


This e-mail message, including any attachments, is for the sole use of the
intended recipient(s) and may contain confidential and privileged
information. Any unauthorized use, disclosure or distribution is
prohibited. If you are not the intended recipient, please inform the
sender by reply e-mail and destroy this and all copies of this message.

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.