Forum Replies Created
-
AuthorReplies
-
I ran into this issue going from 6.1 to 6.2. Our 6.1 is on AIX and our new 6.2 is back to Linux.
We have been using this process on our previous Linux servers and CLV versions. Only now have we run into it being an issue.
It seems everyone is spot on regarding it being an issue with 6.2. Hopefully it has been reported.
We had PDF we were decoding and oddly enough deals with the same contents as Sandy’s.
I used a good chunk of Charlie’s logic from the Sandy TCL and was able to get it to work. I did not need a lot off what Charlie supplied. However, I like some of his other code that I did not really need, but preferred after seeing what he did 🙂
For me all I had to do was change from using this:
exec uudecode [filename or data here]
to using the field with the data and:
package require uuencode
package require base64
set decodeWF [lindex [uuencode::uudecode $DeCryptWF] 0 2]
Thanks toa ll of you for reporting and looking into this!
We opened a ticket up and maxed out logging, but could never narrow down what was the cause.
I am still searching the forum, if I find an answer I will reply to this thread.
This was sitting with me and I had a tickle in my brain it may be the output schema. After reading your findings and performing the same steps to confirm for my setup, I had the same failsuccess. Thank you very much for taking the time to review this. I am trying to use a CDA R2 schema. I found there was one in “client/formats/xml” on our box, but I get the same error. I’ll start a new thread about CDA. Thanks again!
This answer provided by Infor Support satisfied our WebSphere team: In case anyone else runs across this. Here is what our websphere team sent to me: “I was able to recreate that error with rfhutil so it is not a problem in cloverleaf. I believe it is the transmission queue on MQ that is holding you up. The input queue into our Broker/MQ AIX environment has a max message length that will handle these documents; however, the transmission queue on the mainframe ZOS is not sufficient for this size.”
And they ended up increasing transmission queue/max message length to 4.19mb.
Smooth sailing now.
I did not even think to see if this was MQ specific configuration versus a Cloverleaf configuration. Still new to this game. Now I now to check the web first 😀
February 4, 2013 at 9:26 pm in reply to: Running ‘unsupported’ client only install on Windows 2008 #77248Our servers are being upgraded to 2008. I ran into this message: “Client Only install type is not supported on Windows Server 2008. Host Server and Client install type will be installed.”
We are working fine on Win Server 2003 and Citrix. Never saw any odd message we we ran patches.
So the install did indeed install server and client. Not going to use or activate Server.
I went to run the latest patch and received the same message as you. Removed the windows check and it installed.
Just started testing. Will reply to this thread if I encounter anything else. We are on 5.8 (5.8.4.0P with patch).
We are using 5.8 and I do not see this capability. Maybe I am overlooking it?
-
AuthorReplies