| Author |
Message
|
| kwelch |
 Posted: Wed May 22, 2002 12:49 pm Post subject: WKSPACE Parser in WMQI 2.1 |
 |
|
Master
Joined: 16 May 2001
Posts: 255
|
Has anyone had any problems using the WKSPACE parser with WMQI 2.1? We are getting errors saying WKSPACE not found. We have copied the lil file into the bin directory but still get this error.
Is it possible that it's not compatible with WMQI 2.1? We have read the information and it says compatible with 2.0x and up but the pdf specifically references 2.0.1. I also read somewhere and now can't find it where the lil was supported for 2.1 but not the source or compiling of the source(not sure if I correctly interpreted that or not!).
If anyone has any ideas or has this working in 2.1 I would like to hear from you and see if you did anything different. Thanks!
Karen |
|
| Back to top |
|
 |
| kirani |
| Posted: Wed May 22, 2002 12:53 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
If you have not recompiled the code then existing lil file should work with wMQI 2.1 without any problem. Have you restarted the broker after copying the lil file? Check for any error messages in your systemlog.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| kwelch |
| Posted: Thu May 23, 2002 6:13 am Post subject: |
|
|
Master
Joined: 16 May 2001
Posts: 255
|
Hi Kiran,
There are no messages in the system log but I do get this error in the application log from the event viewer.
( MQITEST.UDS_POC_EXECGRP_DEV ) No constant for parser class name for root element name 'WKSPACE'.
The message broker could not locate a constant for a parser class name for a root element name.
Contact the author or supplier of the loadable implementation library implementing the parser to check whether or not the constant has been registered. If it has not, install an updated version of the loadable implementation library. If registration has taken place, contact your IBM support center.
I don't know if the configuration manager was restarted or not is that necessary? I will certainly check.
Thanks,
Karen |
|
| Back to top |
|
|
| kwelch |
| Posted: Tue May 28, 2002 6:28 am Post subject: |
|
|
Master
Joined: 16 May 2001
Posts: 255
|
Hi again Kiran,
I did have the configuration manager stop and restart. Now I don't get those errors anymore and I write out an XMl message which looks like my entire input message put into XML(with the cobol copybook names as tag names) then after that I get about 50,000 bytes of unreadable garbage. When I comment out the WKSPACE parser code, I get a normal looking XML message.
Any other ideas? Was there something else we should have done besides copying the lil file? We did not recompile. We just took the lil file and copied it to the bin directory. Thanks for any help or suggestions!
Sincerely,
Karen |
|
| Back to top |
|
|
| kirani |
| Posted: Tue May 28, 2002 8:40 am Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Hi Karen,
Could you post your ESQL code here? Do you have CopyMessageHeaders or CopyEntireMessage checked in your compute node? I came across a bug in WKSPACE parser that has to do something with copying message headers only. I don't remember exactly what it was. I will try to go thru my notes and see if I can find some more information about it.
Regards,
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| kwelch |
| Posted: Tue May 28, 2002 8:54 am Post subject: |
|
|
Master
Joined: 16 May 2001
Posts: 255
|
Hi Kiran,
I did find out something but I don't quite understand it. Maybe this will ring a bell with you. I ran a trace on my messagflow. It appears that the code using the wkspace parser is executing correctly from what I can tell, but it seems to be obliterating my Input and my LocalEnvironment.Variable information because the nodes after that get failed to navigate to path element because it does not exist.
I do copy entire message which generates: Set OutputRoot = Inputroot; and then I also SET OutputLocalEnvironment = InputLocalEnvironment and in the advanced tab I do have LocalEnvironment and Message checked.
Let me know if you still want the ESQL. It's some code given to me by a consultant that no longer works here to do Julian Gregorian date conversion.
Thanks for your help!
Karen |
|
| Back to top |
|
|
| Sandman |
| Posted: Thu May 30, 2002 8:51 am Post subject: |
|
|
Centurion
Joined: 16 Oct 2001
Posts: 134
Location: Lincoln, RI
|
One of our flows that was doing some simple XML:MRM conversion and putting the message back out to another queue was actually producing a message that had some XML elements from the original message mixed in at the beginning of our MRM message. This caused the length of the message to be bigger than we expected.
After several hours of troubleshooting, we isolated the problem to a subflow that was using the WKSPACE parser. When we removed the references, the flow worked fine. So we converted the subflow to use Environment.Variables and it works fine.
Anyone else witness similar problems?
The bottom line for us is that we remain wary of using these nonsupported "SupportPacs".
Regards,
Mike |
|
| Back to top |
|
|
| kwelch |
| Posted: Thu May 30, 2002 10:04 am Post subject: |
|
|
Master
Joined: 16 May 2001
Posts: 255
|
Hi Mike,
This sounds very similar to my problem only I am going MRM to XML. It looks like it coverted all the original MRM input into XML and then added some extra stuff which I can't read. Maybe this is the Environment.Variable.* stuff that I was createing in previous compute nodes. I was not sure. Anyway, I am in the process of doing what you did of converting the WKSPACE references to use the LocalEnvironment.Variables.
Unless someone knows of some other work around?
Karen |
|
| Back to top |
|
|
|
|
