DFT^P03 Batch File?

There are a couple ways to approach this, but regardless, the simple answer to your question is that YOU must set it up so that Cloverleaf can process it correctly – that is, Cloverleaf will understand what to do if the variant includes the format for the batch and any translates iterate appropriately.

So, typically, you have a TPS that strips off header and trailer information, as this info is usually not desired to be forwarded on.  This is also a good place to do any integrity checks, if desired – that is, validate the transaction counts equal what the header/trailer states, or else there is an issue.

From there, I can suggest a couple different options… either 1) send on the whole transaction batch in one message, making sure your variant is built for repeating structure and your Xlate handles the iterations, or 2) have a TPS built to break the transactions into individual messages and continue them on.

I personally prefer #2.  The iteration over a large batch message can get tricky where an Xlate is concerned, as you need to remember to initialize your fields on iteration – or you could end up with data from other iterations held over if the subsequent iteration field is empty.  I also saved the individual transactions to a file for other conveniences – if we receive one big batch message, in smat it would be a single message… can get hard to work with if ever needing to find a specific inbound transaction in the whole thing.  Of course, this would also depend on exactly ‘how’ you are receiving your data – I’ve seen anywhere from the single inbound message, to headers, trailers, and transactions already broken down into separate messages – so that will help determine how you handle it.

If you’re certain the file will contain FHS, BHS BTS, FTS then this should be quicker:

proc batch_file_parser { args } {

global HciConnName

lvarpop will “pop” a list element out of a list.

It’s counter part is lvarpush which will insert into a list.

The syntax is tricky in that you are naming the list and not supplying the data within the list.

Therefore in the example above, you “pop” from the list named msg instead of the data $msg.

Anyhow,

lvarpop msg 0 will pop the first element in the list.

You could capture what is popped by doing something like:

set firstval [lvarpop msg 0]

You can also replace data in a list with lvarpop.

lvarpop msg 0 XYZ will replace the first element in the list with the letters XYZ.

The command is also in the tcl help.

Hope this helps,

-mh

I agree that it should take 4 not 5 but you can echo to see what you’re popping.

It’s possible that there were two carrage returns at the end of your message.

It could also be that the split command may create a “last element” when it splits. I haven’t drilled into that much detail.

FHSrBHSrBTSrFTSr could end up with a list after split that looks like

{FHS} {BHS} {BTS} {FTS} {}

I usually get what I need and move on.

return $dispList would not make a difference.

I don’t use Xlates.

Perhaps someone else can take it from here. Jim?  😀

Rickey,

The CONTINUE Action or the SEND Action will cut a message at the point in the Xlate it is executed and then continue with the Xlate until end.

I prefer the CONTINUE because it simply moves the message on to the next stage in the engine.

Don’t forget to place a SUPPRESS Action in your Xlate. If you do not, you will receive one more message than you want.

I usually place my SUPPRESS right at the beginning of the Xlate to ensure the SUPRESS gets executed regardless of imbedded logic (such as IF Actions or ITERATES which have no repetitions).

Jim Kosloskey