@jim-kosloskey
Forum Replies Created
-
AuthorReplies
-
March 2, 2026 at 12:00 pm in reply to: Best practices for Cloverleaf interface support tools #122332
You are correct in that there may only be a portion of what you want initially (maybe ever) and indeed to expand the scope will be an effort, but this is a start and at least it is a start. Thanks for adding your input.
email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 61 years IT – old fart.
February 27, 2026 at 12:43 pm in reply to: Best practices for Cloverleaf interface support tools #122321Although Site Doc is not really the topic here, might I suggest Infor is looking for suggestions about Site Doc at this link:
https://clovertech.infor.com/forums/topic/user-research-survey-cloverleaf-ide-site-documentation-tool-usage/
Since this seems to be a start to try to improve documentation, starting with this survey may begin the discussion to expansion of the documentation tools to be developed.
email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 61 years IT – old fart.
February 9, 2026 at 12:42 pm in reply to: How to escape the ampersand (&) character in an Xlate #122283The idea for the \T\ is the receiving system should revert that back to an & if it is following the HL/7 standard. So, you see it as the \T\ in the message you send and then the receiving system changes that back to &.
Try that and see if the receiving system behaves properly. If not, let us know.
email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 61 years IT – old fart.
Sorry to hear that.
email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 61 years IT – old fart.
Thank you, but not brilliant, I just have bashed my head against the same wall before. Now get upgraded!!
email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 61 years IT – old fart.
If it worked in the testing tool, it should work in the engine assuming you are executing the same Xlate in the engine as you are testing. This is something you might have already checked but make sure the Xlate you are testing is in the same site as the engine is running.
As for the code, I would need to see more to assist should you be executing the same Xlate you are testing. If you would like to do a desktop sharing session where I can help, email me.
email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 61 years IT – old fart.
Congratulations in getting it working. It appears your solution will only work if there is one and only one OBX/NTE group. Perhaps that is the situation. However, if the source system ever sends multiple OBX/NTE Groups, your solution may not function as desired.
email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 61 years IT – old fart.
Another example is you can actually increment or decrement the % counters directly as well by doing a MATH ADD with $%s1 (for example) and =1 in the Source column and $%s1 in the Destination column.
The rule is when referencing the iteration variable (% counter) in the Source or Destination a $ must prepend the iteration value, whereas when used in the address path of a data item no $ is used (or else the result has the value of zero).
email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 61 years IT – old fart.
Actually, I do MATH Actions on the % variables all the time. You can increment or decrement them as needed inside the Xlate thus reducing or eliminating altogether the need for intervening temp variables.
For example, to set the Set ID for an OBX Segment, do a MATH ADD using $%s1 and =1 placing the result in the OBX Set ID field (the % variables are always relative to zero, the Set ID relative to one).
I cover this along with other Xlate ITERATE nuances and principles in my Xlate ITERATE Calss (shameless plug).
email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 61 years IT – old fart.
If after reading the provided answers (all of which are correct) you still are having issues, I am willing to via desktop sharing, help you work through this issue. There are some nuances involved.
Just email me and we can work on this off-line if you would like. Email is in my signature.
email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 61 years IT – old fart.
Hi Tom,
I did this and needed to make a copy of the message to be OVER’d prior to setting the disposition and returning to the engine. I can send you that proc and its User Doc if you email me.
email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 61 years IT – old fart.
Sounds worthwhile – thanks for sharing.
email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 61 years IT – old fart.
Roland,
email me (my email is in my signature on this post) and I will try to help.
Jim
email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 61 years IT – old fart.
There is more regarding the Tcl API for SMATdb here:
docs/clis_2022.09_clfisolh_op_en-us.pdf
Find that file in your /integrator directory path as indicated above. This is what is available in 2209, hopefully it exists in your release. If it does not email me and I will see what I can do.
email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 61 years IT – old fart.
Tim,
I found some help file that indicates:
smatdbdelete smatdbhandle ?deleteCondition?
The deleteCondition is to be an SQL WHERE statement describing the conditions for deletion.
I suspect this module is to be called via another Tcl Proc so you will need to construct the wrapper. Perhaps use Charlie’s code modified to add a deletion option and exploit the other code to get to the point of deletion.
email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 61 years IT – old fart.
-
AuthorReplies
