DSXchange

It's not an updateable view so no-one is allowed to insert records into it, not just DataStage. Have a chat with your DB2 DBA to see what you'd need to do to accomplish that.

I've never seen it either and it's not a dcumented status code. Hold on, clarify something for me - does your script use "-jobstatus" or "-wait" to run the job?

Got that... but still, I don't believe adding that will change anything as the option of "operator combinality" is on and happening by default regardless. You specifically add the one you mentioned in order to set 'disable' to 'true' and thus stop it from happening. That was my only point ...

Sure, I wouldn't have mentioned it otherwise. :wink: You can run any valid 'sql' that you would in say the Administrator from the command line. I'll see if I can find an example, but a search for "uvsh" or "dssh" should turn something up. One example, should give you the basic id...

You really shouldn't see anything over 99 but occasionally we do. Under what circumstances are you seeing this?

OK... but isn't that the default? I thought the suggestion was to disable it so perhaps the problem stage/area would be more obvious in the score or logs but I guess not.

Carry on.

Ah... if only it was that easy.

JRodriguez wrote:Add the environment variable APT_DISABLE_COMBINATION=FALSE

Guessing you actually meant True here.

Not directly, no. It would be nice if "dsjob -jobinfo" included this but it doesn't. :( You'd need to query the repository for the JOBTYPEIND value of that job. A search will turn up mulitple conversations on the topic, including this one. That should still work fine in the 8.x release, ho...

I'm not seeing an "SFTP" stage, am I missing something? Or do we actually mean the FTP Enterprise stage with the 'Transfer Mode' option set to Secure FTP (SFTP) ? As noted, what issues are you seeing?

Split another link off the transformer to an Aggregator and send any single non-null field down it. Tell it to Count that field. Write the result to your other file.

So... with your 'irrespective' comment do you mean other than relying on what is in the Dependencies tab and using the 'dssearch' command?

OK... so do you get this with all jobs, only certain jobs, only jobs in certain folders, what? I'm wondering if the project needs to be reindexed, something that was mentioned in the other threads as well.

An exact search for "This key is already associated with an element of this collection" found 12 other people reporting the same issue, did none of them help you out?

I noticed that the warning went away when I handled the type conversion explicitly in 7.5.3. would that mean I would have to identify all instances where implicit conversion was taking place in the existing jobs and handle them appropriately? Yes. They should have given you that same warning in the...