@sc40
Forum Replies Created
-
AuthorReplies
-
October 30, 2018 at 8:20 pm in reply to: needing some pdl guidance no-match: no more phrases to try #86449
If you use encapsulation I don’t think you’ll get a pdl error in the process log because you’re not using a pdl.
October 30, 2018 at 4:30 pm in reply to: needing some pdl guidance no-match: no more phrases to try #86445True. Determining if it is an issue, and if it is, resolving it, should be the first priority.
October 29, 2018 at 8:17 pm in reply to: needing some pdl guidance no-match: no more phrases to try #86443Another option might be to ditch the pdl approach and go with the tcpip protocol instead of the pdl-tcpip protocol. Using the tcpip protocol lets you configure the start and end blocks via the Encapsulated Data Option. Select USER for the Mode, add your start and end block settings.
Would this be a case where a tcl proc is a better solution? Seems like this can all be done in one tcl proc.
I’m new to X12, putting together an Epic X12 interface from Epic to Cloverleaf to Experian (X12 msg type). Using the X12 pdl from James I am now able to receive X12 from Epic (and reply back with a tcl TA1 reply proc), then send the X12 msg to Experian, but I get a reply back which isn’t handled since I don’t have an X12 TPS Inbound Reply proc.
Has anyone run into this issue? I can use hcitpsmsgkill, that works, but then I’m not getting the status (ack/nack) checked. I could write my own IB reply proc (once I figure out what a ack/nack in X12 looks like)…
thanks,
Steve
Is the “permission denied” error on the directory or on a specific .tcl file?
Bob – we’re on 6.1.2, AIX, no issues there. We run ~12-14 million messages a day, so we’d prefer to wait for the performance fix just to avoid any potential issues. We also want to move off of Windows 7 as most of our organization has done so. The 6.2 gui supports Win 7 and 10, which would allow us to test on WIN 10.
–Steve
Same here. It would be helpful to know when the release will be available.
thanks,
Steve Pringle
Here are 2 ksh scripts we use to turn off/on all alerts on all sites.
We send emails often, both from tcl code and alerts. We have not seen any issues. We’re running CL 6.1.2 on AIX.
It would also help to know what hardware platform/OS you’re running on and how it’s configured.
We process ~12 million messages a day, we’re running on a dedicated AIX server with 4 cpus and 32 Gb of memory. This configuration is more than sufficient to handle the load.
Hi Rob –
Inquiring minds – is there an ETA for the 6.2.2 release?
thanks,
Steve
We’re running Epic 2015 and we were told by our Epic counterparts to set the HL7 version id to 2.4.
We also set the Epic profile variable “SEND_MSH_MESSAGE_STRUCTURE” on our ADT queues (as Paul Bishop suggested) to false, so ADT^A04^ADT_A01 is sent out as ADT^A04.
Hi Levy,
That did it! I ran into a few other minor issues but the bad wsdl was the major problem. I fixed the wsdl file as you suggested. I actually had validated the wsdl file on a validation tool I found online, and it passed, so go figure.
I don’t have apache CXF so I couldn’t try the wsdlvalidator tool.
anyway – thanks for your help!
–Steve
Well, we’re using the PAYLOAD service mode option on the thread, which lets CXF handle the SOAP envelope/Header. So it seems all we need to supply is the payload, not the SOAP envelope/header.
From the user’s guide:
Service Mode
PAYLOAD
Selecting PAYLOAD tells the system to send/receive only the contents of the SOAP Body element and that CXF will handle the SOAP Envelope/Header.
Use PAYLOAD mode unless there is information in the SOAP Header that the system requires or must send that CXF does not already handle.
thanks,
Steve
-
AuthorReplies
