DSXchange

I was responding to the original question, specifically - replacing the contents of positions 10 thru 12 in the string. One time, one place, hence the suggestion to substring. The OP was wondering how to make the pxEreplace do the same because there can be multiple occurances of the target character...

OK, verified. Any idea if there is an XMETA equivalent or have they migrated that functionality elsewhere in the suite?

I was wondering what exactly your proc, the one that you need to call does, not what one does in general.

I feel it would help to know what it does in order to help with the "how do I test it is working correctly" part.

A Server job that sources from a dataset? I think not... hold on tight, off to PX land we go!

I was thinking the SP stage had an ODBC option for 'Vendor' but on examining the docs that seems to be... incorrect. Can you go into a little more detail on your need here? What does the proc do? Do you need to execute it only once? Or once per row? The latter is going to be quite painful from a per...

That certainly was the place to check in the pre 8.x world, not so sure it can be counted on any longer. Perhaps there is an XMETA equivalent you can query?

Quite simple to substring instead, as already suggested.

First step? Help yourself - an exact search for "[ParamValue/Limitvalue is not appropriate]" will reveal all.

Not navitely but could you not do so via ODBC?

Split from this topic. I had to guess on the particulars (version, O/S) so if either are wrong please edit your post and correct them.

Why not use the Stored Procedure stage?

Substring using the "[]" operators:
Where "XXXX" is the replacement text for string positions 10 thru 12.

Edited because you actually meant 10th thru 12th.

Yes, that would be the typical solution to this particular problem, the use of 'in-band' nulls on both sides of the lookup.

:!: Just a quick note :!: RSunny, we are now on the fourth page of your hijacking of this thread, something I shouldn't have allowed to happen. Next time you have questions or problems of your own, start a new post. When I get some time, I'll get out the scapel and see if I can hack these two apart ...

That file is an include file (hence the .h) which defines status and error codes, amongst other things. I pointed it out to you so you could look up your -13 error, not as any kind of usage "documentation". :? Oddly enough, you'll find these functions amongst your online documentation such...