needing pdl for Experian eligibility epic query interface going thru cloverleaf

James – I recompiled the X12_tcp.pdl and set the thread sending data to Experian to use the X12_tcp.pdl.  That seemed to work as we got the TA1 from them.  We send that back to the query interface on Epic.  We are asking them to send us eligibility data now that it looks like we resolved the protocol transmit begin/end blocks for them.

So far, it looks like it is working and I appreciate the help on this.

• This reply was modified 8 months, 2 weeks ago by Nancy McDaniel.

Needing assistance.  We were able to use the x12_tcp.pdl when testing.

The issue is when we went to production, we discovered Experian is using multiple servers and only one was able to send data, the other was getting connection refused.

So then we tried switching over to multi-server option.  We had used it a couple of times for Epic interconnect interfaces with high volume.  The issue is that the info we had gotten on setting up multi-server  was using the tcp protocol instead of the pdl-tcpip protocol and then using default of mllp in encapsulation configuration.

We would like to use the multi-server option for the listening thread but have a question on what the setup should be since Experian uses different start and end block.

The PDL has STX for start and ETX for end.  I tried using that in the encapsulation wrapper but it did not recognize the wrapper.  Debug definitely shows Experian sending 02 for begin block and 03 for end block.  I then tried setting the start to 02 and end to 03.  But it is still not recognizing the data.  02 hex = STC ascii and 03 hex = ETX ascii.

Any suggestions on getting the multi-server option working for Experian X12 using tcp protocol instead of the pdl-tcpip is greatly appreciated.

Jim – yes we tried the multi-server with PDL tcp/ip thread.

Note this is the input (response) thread from Experian.

When I changed it from server mode to multi-server and went into multi-server config – only change was to click on option to save IP and port.

We then got the following error – message in error state.

Unable to write message as connection no longer available — retries disabled.

Jim,

We have several connections with them – we have one that we send data to them and that is successful.

this thread is elg_271_in which is the one that we are listening for messages from Experian.  They did some initial testing and it worked.

But when we went live with them today, we found out that there are doing load balancing and sending data from multiple servers.  They said they are seeing a lot of connection refused messages.

that is why we decided to try the multi-server configuration.

We have 2 multi-server input threads – Epic interconnect to our cloverleaf server with high volume.  Epic provide guidance – they recommended do not set the max client setting – so we have it at zero and it works great.  We did have to switch to the tcp protocol instead of the pdl-tcpip protcol but we were able to use the default MLLP protocol setting.

Your suggestion of bumping up the max client did not work.

We are getting the data but it goes to the error database with error 418 unable to write message as connection no longer available — retries disabled.

I can put in a support ticket and see if they can help me with this error.