DSXchange

I imported some match specifications from version 7.5.1A to 8. However, on one specification, whenever I try to use it, I get the error: Could not load MatchSpec xml string.

On another one, I get the error:
Match: Invalid [MPROB]: value [ZIP5] is not a valid number

My match specification has ZIP5 but does not have [ZIP5]. It is a char column. I am not bringing it as a number. Why would it give that message?

I also get the error:

Error occurred during initializeFromArgs().

The "not a valid number" problem is likely to be caused by a european number in the MProb and UProb parameters eg. 0,1

If you open the export file in notepad and search for MProb you will see if this is the problem. You can edit the file if you wish.

How can 0 or 1 be European number? These are default values that Match stcgae picks when I am creating a match. Currently, the values I have are .9 and .01.

I think Bob is referring to the use of a comma as a decimal delimiter (as commonly used in mainland Europe)

J.

No. I am not using a comma. I am just using a decimal like .99 or .01. By the way, can any of you guys point me to a location where I can llok up these errors? It seems like with QualityStage, specially in DS8, if there is an error, there is absolutely no help.

In version 8 there is an Errors and Messages manual. I have not checked to determine whether QualityStage messages are included.

Ray, thank you for your response. Obviously, these errors are NOT listed in the Errors manual that comes with Datastage 8. There are very few errors which are listed there so that guide is not very helpful.

I am getting this error. Has anybody found a solution that they can share with me? Thanks.

Have you contacted your support provider? There are a number of issues with QS8 importing rulesets. There is a wrap-up fix pack that solves many of them. Do you have that applied?

Thanks ArndW for your response. No, I haven't contacted my support provider. Its a convoluted process and we have to pay for every contact. Have you seen this error before? This absolutely does not make sense because the value in the mProb box is .9.

No, I haven't seen that specific error before, so it might not be one of the ones corrected by the major DS/IIS patch.

Ok. I found the solution. For an unduplicate match, I needed to use a unduplicate match specification. I was using a reference match specification. Obviously, the error message, "Invalid [MPROB]", has absolutely nothing to do with this problem.