DSXchange

Can you save the job that isn't working under another name, delete the original, rename & recompile the copy?

QualityStage will do this for you, and it is a part of the product at V8.

Craig, we've been thinking about that type of an approach as well. But with 512Kb string length and only getting 4000 character chunks out of it at a time it is really goign to slow things down. The xmltype is not readable either, we've tried that. The XML string isn't really processed here, but it ...

Did the multiple job in fact go and compile your project's jobs?

From the Administrator or from TCL, execute the command "COUNT DS_JOBS". Do you get a record count or an error message?

The Orchadmin rm method looks into the .ds file you are deleting and removes the segment files actually used. No chance of missing files or deleting too many.

I think so as well, and if the SELECT for the multiple job compile fails then it would point there as well.

Try "export PATH=$PATH:."

If you add that to your user's .profile or to the dsenv file then it will automagically happen each session.

We have large strings containing XML that we need to store and later read & process in Oracle. These strings can be up to 512Kb long, so we cannot use VarChar2 in Oracle as that is limited to 4000. Using the Enterprise Oracle stage we can write these strings successfully to tables, using "LongVa...

That means that one or more of your DataStage hashed files might be corrupt, most likely caused by the disk full condition. If the project directory didn't fill up then I would try a quick multiple job force compile of the whole project from the designer - this might (low probability) clean things u...

This means that your PATH environment variable does not contain "."

Try "./dsjob -lprojects"

Can you try to DS.REINDEX, it might be a defect index.

Yes, you can use OCONV(In.MessyString,'MCP') to turn all those nasty characters into "."

Ag_ram - just so I understand your post, you can recommend having the poster identify which job number he has, go and delete the appropriate RT_LOGnnn directory from the disk, then edit the original job and do a "save as" in order to get a runnable job - then finally delete the original job (which c...

Ahh, that is correct. I think the American idiom for this is that you are "SOL" - meaning that that answer to your original question is "no"

I think I've done that with server jobs and it worked. Have you actually tried adding the entries?