DSXchange

They only show up there if you are logged in as the user that actually scheduled the jobs.

Not surprisingly, DataStage can do both "quite complex logic" and "performance". However... Create a job with a Transformer and a Stored Procedure stage. Create whatever fields in the Transformer you need to call the proc and set their values. Create a stage variable (you don't n...

Out of curiousity, have you tried using the Stored Procedure stage? Not sure what stage is "the stage" mentioned above that you are using, hence the question. You'd need to set it to a type of "Transform" rather than Source or Target for it to process single rows like that.

If the function performs an insert, delete or update, it cannot be used in a select statement just like a column. Of course, however now you've moved outside the scope of the original conversation / issue. Never mind the fact that this should have been asked as a new topic, so I've split it out for...

Well past time to involve your official support provider, it would seem. Did you look to see if there were any patches available for that connector? What exact 8.x version are you running?

Based on that "internal error" you posted, I would imagine you'd need to involve your official support provider to find out what's going on. Unless there is a property in the stage where you can adjust the "array size"? Doubt it, somehow. What exact version are you on? Are you cu...

harishkumar.upadrasta wrote:Corrected:

Index('|':lnk_xfmr_target.CLASS:'|','|ARC|PPD|CCD|CTX|COR|DNE|' ,1 )

Your correction is... correct! From the docs:

Input: string (string) substring (string) occurrence (int32)

As noted here (the post you found) you manually delete the components involved.

As noted, not much point of a DataStage job that just runs a stored procedure. Use your database's command line or procedural language for something like that. Any option to rewriting it as a DataStage job?

ray.wurlod wrote:Arnd's approach is totally valid.

Ah, true. Was reading it kind of... bass ackwards. Just to amend it slightly, I would say "Assuming that the string will always have at least one leading zero".

Welcome. First confirm for us you do indeed need to create a Server job rather than a Parallel one. Also let us know how the job will use the stored procedure - is it a source as it will supply rows to process? A target that will perform actions when called? Something that performs an action on one ...

I would think you could string together a StringToDate() followed by a DateToString() with the proper format masks. Assuming a varchar target, as Arnd notes.

Is the target column a string? Hmmm... I think the leading "EM" is going to negate your approach, Arnd. I was thinking you could find the first '0' starting from the back and then substring from there but zeroes in the number itself would hork that up. Seems you might need to find the firs...

And so will a Decimal 10.

It prevents "false positives" on a substring match. For example, yours would return true for "CPP" which is not in the valid set.