- This topic has 7 replies, 3 voices, and was last updated 6 years, 7 months ago by
.
-
Topic
-
-
Replies
-
-
-
If you have messages in SMAT which represent the messages you want to test with then yes just extract using the SMAT tool to either a new line terminated or length encoded file.
If there are many messages I want to test with I put each message in a file – I find that easier to work with.
If there are no existing messages maybe because this is a new source system and there are no messages to be had, you can actually use the Xlate and the Xlate Testing tool to craft a test message according to the Source System’s spec. Save the message in the Testing tool to a file then use that file to test the new Xlate.
This is a technique I cover in my Xlate class.
email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.
-
C:cloverleafcis6.0integratortestalexecprocessesfr_paragon>hcismat -i C:c
loverleafcis6.0integratortestalexecprocessesfr_paragonfr_paragon_15100.ms
g -orsf c:cloverleafparagon_15100.txt -nl
hcismat: Invalid argument bad variable name “::SMAT::argArray(TARGET)”: upvar wo
n’t create a scalar variable that looks like an array element
usage: hcismat -i filename ?-pri priority? ?-nl? ?-reply? ?-ib? <mes
sage selection criteria>
-
-
-
Well I think there is a script provided with cloverleaf which will convert len10 encoded records to nl.
I don’t recall the name but I think it is len10tonl or something like that maybe someone else can give the correct name if that is not correct.
After doing the GUI SMAT extract, use that script from the command line to convert to NL.
However, the Xlate testing tool can use len10 files inbound.
email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.
-
-
- The forum ‘Cloverleaf’ is closed to new topics and replies.
