[Jim Kosloskey]

Lawrence,

As I understand it MLLP Version 2 does add the standard handling of the Commit Ack/Nak. In Cloverleaf, I am unsure what happens when a Commit Nak is received. I do not see anywhere to specify that handling and I am unsure what the standard says on that point. Perhaps the assumption is the engine does not need to know if a Commit Nak occurred. If that is the case, I disagree. I know a lot of shops set up to just unilaterally kill acknowledgments altogether, but I submit that is not good practice.

As for inter-site routing, be careful. There are limitations to how well that works – especially in high volume integrations. Under the covers, I understand it uses cross process handling which has limitations. I still recommend using TCP/IP ports on localhost to do inter site routing using length encoded TCP/IP and minimal ack (single hex code for pos/neg.  If you would like to discuss this off-line, email me.

I don’t understand your thinking regarding specifying clients as servers, specifically the advantages you anticipate.

email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 60 years IT – old fart.

[Jim Kosloskey]

What little I know, and it is admittedly not a lot, it appears the wizard is for importing a csv file to a table.

What I found more useful was to have the user create a stored procedure to expose the data (probably stored in a DB), then invoking that Stored Procedure in a Cloverleaf defined DB Lookup.

I produced a white paper on how I accomplished that with a Sybase DB (but should work with any Cloverleaf supported DB). I think that was posted on clovertech. If you cannot find it and are interested in the concept, email me and I will send you a copy.

email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 60 years IT – old fart.

[Jim Kosloskey]

If the source system is taking care of those files so that not deleting them in Cloverleaf is a viable option, you can use the fileset local Delete UPoC (A tcl proc) to control which files Cloverleaf actually deletes. I have a set of procs that (under argument control) provides a fair amount of flexibility to control what files get deleted. You can have those procs if you like, just email me.

email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 60 years IT – old fart.

[Jim Kosloskey]

Brenda,

I did a quick test on Cloverleaf 2209 and the proc is indeed removing the envelope leaving the ST and following segments to the SE as expected.

My file is quite simple:

• ISA
• ST
• B11
• SE
• IEA

ISA*00* *00* *ZZ* *XX* *080215*1614*U*00401*000000012*0*T*\~GS*HI*MDACC*UHC*20080215*1614*000000004*X*004010X0941A~ST*213*cn123~B11*iq*id code*123120*oz*2*US*5.00*C*Junk Charge~SE*3*cn123~GE*1*000000004~IEA*1*000000012~

Note there are no CR or NL until the end of message. Some systems try to make the X12 readable and add CR and/or NL where they do not belong which is OK for humanoids, nit so much for computer systems. If you have that situation, you may need to do some preprocessing to clean that up – although I would complain to the source to provide a proper file.

So, I am not sure what your issue might be but am willing to brainstorm with you.

email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 60 years IT – old fart.

[Jim Kosloskey]

Brenda,

Yeah, I will need to know more as you should not get a disposition error. What release of Cloverleaf? I know when I used that proc on 6.0 it had issues, so I wrote my own. But I think those issues have been resolved in later releases. If I have some time today and tomorrow, I will try to setup an example on 2209 to see if I get an issue with that proc.

Feel free to reach out to me whenever you feel the need.

email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 60 years IT – old fart.

[Jim Kosloskey]

Brenda,

There is a Cloverleaf provided Tcl proc called hcix12splitinterchange that removes the envelope (ISA and potentially GS) and splits the messages on GS or ST depending on the argument provided. That envelope data is then placed in each of the split message’s metadata USERDATA Field.

The splitinterhange proc would go in the IB Tps UPoC. Then, if an X12 message is being output, there is an hcix12buildinterchange proc that puts the envelope around each OB messages and that goes in the OB TPS UPoC.

If OB messages need to be batched, then there are a couple of procs for x12 batching and unbatching.

IN your variant, you would not specify the envelope. You would specify the GS if indeed each message is structured that way but I suspect there is one GS per file with multiple ST segments inside.

If you still have questions, email me and I will assist off-line.

email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 60 years IT – old fart.

[Jim Kosloskey]

I am assuming Xlate here.

Yes, depending on if the indicated segments have something that can be used to identify them as the source for the consolidation.

It is also easier if the segments to be consolidated are ALWAYS all together as in the example.

Another consideration is: can this consolidated segment be the last or first segment in the OB at all times or does it need to be in place (like in the middle).

So, a qualified yes. I would need to know more about the situation but if you would like to brainstorm this via desktop sharing off-line, email me.

email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 60 years IT – old fart.

[Jim Kosloskey]

Interestingly, when I do the same activity for xlateInList all is as expected. This leads me to suspect that when the Source is empty, there is no xlateOutVals to upvar.

email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 60 years IT – old fart.

[Jim Kosloskey]

Robert,

Thanks, I have produced a proc that does what I want for both standard and DB Lookup Tables. My thought is this would be a nice enhancement to have built-in to the product as an Xlate Action. If anyone would like a copy of the proc(s) and User Doc I have built, they can email me.

Yours is an interesting challenge especially to work within the expanding framework of the Cloverleaf architecture. Perhaps an API for Tables similar to NCI would be an answer to getting the table information you seek.

email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 60 years IT – old fart.

[Jim Kosloskey]

I have done this now and have produced a white paper on what was done. I will attempt to attach that white paper here. If that fails, and you want a copy or just want to discuss what I discovered, feel free to email me.

Attachments:

You must be logged in to view attached files.

email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 60 years IT – old fart.

[Jim Kosloskey]

Thank you for the hard work getting us back on-line. One really does not know how much one uses something until it is gone.

email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 60 years IT – old fart.

[Jim Kosloskey]

This is a wide topic. There are some ‘normal’ situations that fit the standard (assuming HL/7 and TCP/IP) and some ‘not so normal’ situations. Many have tried ‘one solution fits all’ with what I consider mixed success. Compounding things is receiving systems don’t always follow the rules.

If you would like, I would be happy to discuss various scenarios with you and go over the configuration setup. Just email me and we can discuss this off-line.

email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 60 years IT – old fart.

[Jim Kosloskey]

Jason,

Yes, one could get the host xlate name in the host xlate and set a temp variable (temp variables are transferrable between host an included xlate and vice-versa) but that reduces the generic potential of the facility. I was hoping there was something already in place under the covers that could be referenced.

Before I explored alternatives and alternatively asked for an enhancement, I wanted to find out if there was something already provided.

email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 60 years IT – old fart.

[Jim Kosloskey]

I agree that is what is happening, but I don’t believe that is what should be happening. The implication in all of the documentation is that the xlateInList and XlateInVals lists are in synch with each other and that is to be expected. The reality is there are cases where that is not true and I do not think those cases should exist. The relationship between xlatexxLixt and xlatexxVals (in and out) should be maintained in my opinion and based on what I can gather from the documentation available and my past experience.

I have coded xltp type procs this way since release 3.1 and although I cannot prove it, I do not recall this particular issue in the intervening releases I have used (I have not used all the intervening releases).

email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 60 years IT – old fart.

[Jim Kosloskey]

I have attached a white paper on using a Stored Procedure for Table lookup. This happens to be for a postgresql db but the techniques should work for any DB that has Stored Procedures.

Attachments:

You must be logged in to view attached files.

email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 60 years IT – old fart.

[Author]

Replies