DSXchange

Search, search, search. An Exact Search for "Unable to allocate Type 30 descriptor" will reveal all.

I'm 99% sure it handles them just fine. I'll run a quick test later and see.

So... you successfully start the first job and then in the second Director window you receive that error when you press the 'Run' icon?

What is your target? :? Build a routine with a FOR loop, appending the values from your range. If your target is another sequential file, you can even add CHAR(10) characters between them to create individual records from the returned string. Crude illustration: YearString="" FOR year = Co...

We have a project that throws this message for any process that reads the entire list of jobs. OK, perhaps not "any process" but the Director sure does. I was thinking I could query DS_JOBS for that name, get the job number and copy another job's files over to that number in the project to...

Are you supplying two unique/different Invocation IDs when you run the jobs?

Which 8.x version do you have? Unless it's 8.1 then you do need a bunch of patches to get everything working and 8.1 probably needs one or two as well. Best to check with your official support provider, as you are doing.

No clue on the ODBC question. As to the "Enterprise" one, if you have PX jobs then you have the "Enterprise Edition" and can do anything "orch" related.

Did you actually create a Parameter Set called "DSParams"? That name jumps out at me as there's actually a system file by that name.

What stage are you using and where exactly in it are you attempting to "access" this parameter set value?

In thinking about this, it seems to me in hindsight that we could have move beyond all of the 'standard' answers that we got bogged down in if it had been more more clear that you had this issue with all jobs in all situations. Meaning you couldn't even run a single job manually with no other jobs r...

Wow... glad it was as simple as that.

Thanks for posting that. We'll all have to keep in mind the fact that the -14 error could also mean an issue with the Universe repository / engine as well nowadays, I would have expected a more... catastrophic... error than that.

#and $ are the usual suspects but that's not the case here. Have you tried using the DB2 stages via the Plugin metadata option? Or the command line "orchdbutil" utility?

Hmmm... is there anything "funny" about this table's name, does it use special characters for instance?

If this is a problem just for you on your PC, I would suggest you reinstall the client software. If this is a problem for everyone, I have no idea what to suggest at the moment.