DSXchange

All you've got is the "most recent" job status, there's no history stored. So you'd have to check outside of the sequence itself as any checking the sequence itself does (say 'before job') would be after it had already started. Seems to me you'd need to have your job control check first an...

And there's really no need pad at all. The Date Format Strings fully support variable width month and day values. %m and %d instead of %mm and %dd. In the grand scheme of All Things DataStage, wasn't this a relatively recent change? I'm fairly certain they did not support variable month / day value...

Again, there's no dates just two strings which is why I was suggesting the substring/pad approach rather than a "there and back again" conversion to datesville.

You'd have to post your actual constraint derivations before anyone could provide more cogent help.

Just an FYI - there are no "date" datatypes here, just two string fields that hold two different external representations of a date. And you don't need to check the length of the fields, simply left pad the month or day values to a size of 2 using a 0 as the pad character.

You want them to be bold where? Your target would need to be something that supported bolded fonts...

As noted, you'll need to find out what exactly that is... it may not be something that can be applied externally. Isn't there some kind of "Notes Administrator" there you can ask about it?

After a lot of contemplation I purchased one of the training programs online from one of the various companies. This program consisted of 129 questions and their answers with the promise that if the candidate studies from this material he / she should pass the exam. Not aiming this at you, Tony, bu...

OK... why not simply change the routine so it returns a zero when everything goes ok and a non-zero when something goes wrong? I don't see any reason for it to return text like "200 rows merged" but then we don't know what exactly the routine does. Is this command line sqlplus? You have co...

Welcome aboard. Next time please put more thought into your post's subject, we all know you're here for help with "Data Stage". So do you really need to "bypass" B as in sometimes run A->B->C and other times run A->C or do you need to conditionally run B or C depending on what ha...

Under your projects directory, you'll find a directory named RT_BP1 inside of which you'll find a file of the name listed in your error. Look at the code around lines 134/135 to see what is causing the issue.

You is they. :wink: You have to understand that with either "upsert" the first action must fail before the second is triggered. An insert only fails when it violates a unique key constraint, so without one all you'll ever get is inserts. For "Update else Insert" the update fails ...

I think this is one string field in a single record that has 'new lines' in it. If that's the case then you could use Convert() to either remove them or convert them to a space. Use CHAR(10) to represent the new line / line feed, for example.

They didn't mention "upserts" yet but was hoping that would come out in the details they followed up with if they were. And yes, in that case doing them in that order would be... problematical.

I already tried using the single quotes around it, as you suggested, but then it treats that as a string value and does not evaluate the InvocationId. Then something is not right about how you are specifying the macro as I recall doing that exact same thing all the time back in the day and it will ...