JMS, MQSeries, R/3 Link, NT and AIX...

Question

Hi all,
To put you in situation, I have a java application which can run from any type of OS as of now. It sends documents to a queue (IDOCS) and those documents are then sent to SAP by an R/3 Link adapter. Using native binding and running the java application on the same computer as the QueueManager (AIX) it was all working fine.
Now, I have translated my app to use JMS instead and tried to run it on my Windows 2000 PC. The message are sent allrigth to the queue, but R/3 Link is now giving me a handfull of errors, complaining about conversion, character sets and things like that.
Here is a sample of errors I get:
02/18/03 17:00:39 SMQ4165: Warning on MQGET from inbound queue. Reason code 2110.
EXPLANATION: The attempt to get a message from the inbound message queue returned a warning. The warning code was 2110. The message will be passed to the use
r exit if one has been specified. If no exit was specified, the message will be passed to the bad message queue. If no bad message queue was specified, the
message will be left on the inbound queue, and the server will terminate.
ACTION: None.
02/18/03 17:00:39 SMQ4192: A data conversion problem occurred on the MQGET. Attempting to process message.
EXPLANATION: A warning was issued because the message needs codepage conversion, but the message is either not in MQSTR format, or a user-defined data- conver
sion exit call failed.
ACTION: Ensure that incoming messages from machines with a different code page, are in MQSTR format or that there is a user exit defined to convert messages i
n other formats.
02/18/03 17:00:40 SMQ4167: IDoc has an invalid structure version. IDoc value="16777216". Expected value="1".
EXPLANATION: The value of the version field in the IDoc header structure contains an invalid value.
ACTION: Ensure that the IDoc message starts with a valid version of the Saplink header structure (MQSAPH).
02/18/03 17:00:40 SMQ4191: A message was put to the bad message queue. Bad message type 1, reason 4108.
EXPLANATION: The message was not in a valid IDoc format. The bad message type is 1 and the bad message reason is 4108.
ACTION: Check the bad message reason code in the bad message header of the message. Attempt to correct the error and send the message again.
I finally set the CCSID to 819 in the connection string, now I suspect that my problem is related to the encoding I use but I can't find what to set it to instead. I write everything in a ByteMessage by the way, just as I was doing it with the native bindings.
Does anyone know how I am supposed to set this up? What encoding type should I set it to? Is the CCSID correct? previously, I was setting the format this way: bytesMessage.format = "MQHSAP ";
But using JMS, there is no such property so I tried to just write it to the ByteMessage, not sure this works either...
Thanks in advance,
Daniel
If it can be of any help, here is a code fragment of what I am doing:
using native binding, which was working fine
//Add the mandatory R3/Link header to our message
bytesMessage.writeBytes("SAPH");
bytesMessage.writeInt(1);
bytesMessage.writeInt(108);
bytesMessage.writeInt(273);
bytesMessage.writeInt(819);
bytesMessage.writeBytes("MQSTR ");
for(int i = 28; i < 108; i++)
bytesMessage.writeByte(32);
bytesMessage.writeBytes(textMessage);
bytesMessage.encoding = MQC.MQENC_INTEGER_NORMAL;
bytesMessage.format = "MQHSAP ";
And using JMS:
//Test code
queue = session.createQueue("queue://" + manager + "/" + name + "?priority=5&persistence=2&targetClient=1&encoding=" +
MQC.MQENC_INTEGER_REVERSED + "&CCSID=819");
//Add the mandatory R3/Link header to our message
bytesMessage.writeBytes("SAPH".getBytes());
bytesMessage.writeInt(1);
bytesMessage.writeInt(108);
bytesMessage.writeInt(273);
bytesMessage.writeInt(819);
bytesMessage.writeBytes("MQSTR ".getBytes());
StringBuffer padding = new StringBuffer(80);
for(int i = 28; i < 108; i++)
padding.append(" ");
bytesMessage.writeBytes(padding.toString().getBytes());
bytesMessage.writeBytes("MQHSAP ".getBytes());
bytesMessage.writeBytes(textMessage.getBytes());
queueSender.send(bytesMessage);

Answer 1

Hi There,
I know you used JMS and Link for R/3.
Now I am doing the same but I am getting the same problem besides I am doing what you mention in the forum.
Can you give me a hand to fix this?
I have configured and MQSeries under win2003 and in the same machine a Link 4 R/3. I have a Java app using a .bindings file to connect to the Q and send a message the same way you did, but i am getting this error:
IDoc has an invalid structure header. IDoc value="RFH ". Expected value="SAPH".
IDoc has an invalid structure version. IDoc value="2". Expected value="1".
IDoc has an invalid system number. IDoc value=<T.
IDoc has an invalid client. IDoc value=�Y&#9830;.
IDoc has an invalid language. IDoc value=.
A message was put to the bad message queue. Bad message type 1, reason 4110.
It seems as if the all the JMS headers are at the begining of the msg and it always throw the same error. it doesn't matter what data I put in the bytesMessage.
I would really appreciate your help.
Here a portion code of my SendMessage operation.
     public String EnviarMsg(String Msg) throws JMSException {
          String resp = null;
          try {
               if (getQueueSend() == null) {
                    // Create un objeto QueueSender como productor del mensaje.
                    setQueueSend(QSess.createSender(MQueue));
                    // Crear y enviar un mensaje a la cola.
               * Aqui viene codigo para enviar msgs a la cola en formato SAP
               txtMsg = QSess.createBytesMessage();
               txtMsg.writeBytes("SAPH".getBytes());
               txtMsg.writeInt(1);
               txtMsg.writeInt(108);
               txtMsg.writeInt(273);
               txtMsg.writeInt(819);
               txtMsg.writeBytes("MQSTR ".getBytes());
               byte b = 32;
               for(int i=28; i<108; i++)
                    txtMsg.writeByte(b);
               txtMsg.writeBytes(Msg.getBytes());
               //txtMsg.encoding = MQC.MQENC_INTEGER_NORMAL;
               txtMsg.setStringProperty("JMS_IBM_Format", "MQHSAP ");
               //txtMsg.setText(Msg);
               // QueueSend.setDeliveryMode(DeliveryMode.NON_PERSISTENT);
               // QueueSend.setTimeToLive(30000);Funciona. Probado con el MQSeries
               // 6.0
               QueueSend.send(txtMsg);
               resp = "OK";