DSXchange

Technically, the correct syntax is:

ErrCode = DSSetParam(JobHandle,ParameterName,ParameterValue)

I'd also be curious if you are checking ErrCode after the call to see if it succeeded and if not, why.

If something must always be "X" I wonder why an option to set it to anything else would even exist? Was that not always the case?

I assumed they are looking for the C++ code for dsjob (which is actually published) rather than where the executable lives... but I guess we'll see.

Did you try an exact search for "Bad number of subobjects"?

From what I recall, it's in the same chapter where the various options are explained - the Command Line Interface chapter in the Server Job Developer's Guide pdf in your version.

I personally can't, no, but my understanding is they are documented. Perhaps someone else can point you to the exact place.

"2010-12-10 17:13:37.0000000001" seems to long to be a valid timestamp to me. What is the precision of your target TIMESTAMP column? Max is 9 and you've got 10 which is (I assume) why you got the 'overrun' error.

You need to let us know more than just "none of which worked". Spend some time troubleshooting the individual conversions. What I would do in your shoes to make sure this was working would be either: 1. Use stage variables to break this up into individual conv calls, do this one step at a ...

The list of objects that need SELECT privledges is fully documented and you are really castrating the product's functionality if your DBA won't allow just the select grants the tool needs to operate.

This isn't a license issue, it's a configuration issue. First you need to verify that you installed a supported compiler for your version. Secondly it needs to be configured correctly, something I'm assuming hasn't happened due to all of the "Could not open include file" warnings you are g...

Try adding and setting $APT_IMPORT_PATTERN_USES_FILESET=True in your job.

That's... interesting. It would seem it doesn't care what comes between the "dd" and "hh" elements. I thought it would be pickier than that.

That's not the version - I was looking for something like 10.2.0.1 and I'd be curious if all four segments are exactly the same on all servers.

Interesting... I would have just done a substring or a field, never really had much need to figure out what the "Group" conversions do. Is the full syntax for that code documented somewhere? All the Server Job Developer's Guide has are two example calls and nothing else. It seems to be aki...

Those aren't dates, those are timestamps which is why the code is not working. You need to ditch the time portion before what I posted will work.