Forum Replies Created
-
AuthorReplies
-
I’m with you, Tom. I saw the same red flags and would not agree to do this kind of manipulation in an engine. Scary stuff.
Thanks, David. Finding the page count in the decoded string is just what I needed. Now comes the struggle with the regular expression…
I’d try removing the ;# End Switch comment as well.
In the SMAT tool in Cloverleaf 6.0 there is a drop down, “Selected Encode Scheme”. I guess I thought that by selecting the encoding that I had configured for the threads I would be seeing what the encoded message would look like when it actually leaves the engine.
Maybe I’m not understanding how the encoding should be set up…. the messages that are sent from the sending application pass through two sites (and 2 threads in each site) and then to the receiving application. The message translation and table lookup are in the first thread of the first site the message hits. Do I set the encoding on all 4 threads (which is what I did), or do you only set it on the thread where the actual xlate and lookup table are being used?
What is the workaround for this bug? We will not be able to upgrade to 6.1 so will need to manage this in 6.0 (on Windows OS).
Thanks in advance.
I am seeing the same thing. Thought it was just me.
I’m trying to find more information about the daily schedule of the conference – particularly the start and end times each day. Is this the only website for information: http://forms.lawson.com/forms/healthcare_index ?Do you have an email address for Alli Kelso?
Thanks.
-
AuthorReplies