DSXchange

Can "nearest" be in either direction or is it always up? For example, let's pick 2742.334566 with 5 for the multiple, do you go up to 2745 or down to 2740 since it is nearer?

So, "this error" is what you have as a quote in your first post? If so, it's not talking about data but rather seems to be saying that you have double quotes in the Table Name property of the stage. Do you?

It doesn't really work that way. And you do not need the DATE in any particular format, learn to use the Oracle TO_DATE() function.

No, you didn't... but I just did.

And off we go to the proper forum.

Sorry, but what exactly is your issue?

Do they follow a consistent naming convention like you seem to be doing with "REJT" records? If so, you could just expand what you are doing to recognize and classify those as well while you loop through the lists you are building. You can use the DSGetJobInfo() routine to capture both the...

I for one am not aware of any capability to export / import scheduling information via a dsx. As far as I know you'd either have to do that via crontab or by manually rescheduling the job post-import. I don't recall ever being able to see that information in a dsx file but perhaps that's new in the ...

... or try fully pathing the grep command in the Filter.

OK. Then it seems to me you need "inside information" to really understand what is going on here, so unless Ernie happens to wander by and add his expertise, we'll need to see what IBM Support has officially to say on the issue.

If you are not planning on storing it, then I don't see the point of computing it, especially twice - simply compare the two concatenated strings. And I forgot to mention the null issue, my bad. My only excuse is working with Informatica for the last two years. It doesn't seem to care about concaten...

As Arnd notes, which part of this does not seem to be working? What values are you passing in to the routine - JobName? Anything else?

If you plan on using a checksum for change management, then typically one would include a checksum field in the record with the value for the current row. Then you can generate one for the incoming row and compare the old v. new to see if anything had changed. Store the new checksum with the new / u...

<corrected your image tags>

As noted, sharing with us what exactly you've tried so far and what in the heck "not getting the desired results" means can help us help put you on the right track.

Out of curiousity, what are the characteristics of the XML file in question? Is it... 'large'? 'Complex'? If so, do you have the same issue with a smaller, simpler version of the file?