DSXchange

Best to start by posting in the correct forum, this one is for Server jobs. However, we can see about having the Moderator move it, so that's for future reference only. How about we start with a better explanation of your goal, for example - what exactly do you mean by "symbolic characters"...

There's no "docs" and any links you can turn up yourself for Control-M rather easily using Google or your favorite search engine. I would suggest you spend some time with the people in your company responsible for Control-M if you need a better understanding of what it does or to see examp...

No "where" clause? That means the key column is illegal, that or you need to add the clause and bind the Key into it as noted by position. And ensure your selected columns match the columns defined in the stage. Exactly.

You don't absolutely "need" a script to schedule something in Control-M or any other Enterprise Scheduler but it certainly is the correct way to do that. As noted, the script would be a wrapper for the dsjob command and could do a number of things besides simply launch a job - it could che...

Why, there would still be the kduke option. Similar in taste to the sjfearnside option, but with a tangy twist of lemon.

I was thinking the same thing but it seems the seed is more applicable to the Randomize() function. Rnd(n) is supposed to generate a random number between 0 and n-1 rather than a series of 'pseudo-random' numbers.

Mind you, I haven't read the BASIC manual entry for this, only the online help.

So it's a CHAR(15) in DB2? If the concern is just for this particular value and all other values pass thru then use an IF-THEN-ELSE derivation. Or is this a more general rule you need to apply to multiple values?

That's because what you have is a literal string: "EOA1010LdIncidentTable.DSJobInvocationId" so it uses that rather than realize there is a macro locked inside the quotes prison. Not saying this will solve all of your problems but try: hJob10 = DSAttachJob("EOA1010LdIncidentTable.&quo...

What is the datatype of your target field in the table? What database?

Try adding the Preserve Type optional propery to the 'Column for Calcuations' and set it to True.

Perhaps this will help:

viewtopic.php?t=111077

To the best of my knowledge, it basically goes "left to right" and stops evaluating as soon as it can. Your problem may have strictly been a null versus empty string issue but I'm going to have to defer that judgement to those that have a more intimate knowledge of How Things Work, like Ra...

"(an EMPTY string; I guess this differs from a NULL string)"

It most definitely does. Differ, that is.

For whatever this is worth, I haven't seen this issue in Oracle as long as the proc properly does a RAISE of any errors encountered.