DSXchange

I think that the DS_JOBS contents could be rebuilt with some effort if all other files are still present. Much of the DS_JOBS metadata could be reconstructed from the DS_JOBOBJECTS.

Do you have a UNIX level or DataStage export file backup?

The API call to DSGetLinkMetaData() will return a complete list of column names and metadata for each link in a stage. You would need to use DSOpenJob(), DSGetJobInfo(), DSGetStageInfo() and DSCloseJob() in order to get this to work.

What is preventing you from using parameters for the file names in the stage?

NEVER delete DataStage files from UNIX unless you know exactly what you are doing. If you had deleted the job correctly, from the Designer or Director, it would have freed the disk space and you would not have any problems now.

What happened when you tried my suggestion?

Please don't post multiple threads simultaneously with the same question, this thread is already active.

The stage itself will only take one filename, but if you need to wait for all the files you can just put them sequentially, one stage per file. If more "intelligence" is needed then you could always call a shell script from your job and return an appropriate code for "all files presen...

This is exactly why we always state that you should never remove files from the OS level! The name "Config" should have been a warning - it is not a log file but a necessary configuration file. From the OS level, the RT_CONFIGnnnn files are subdirectories. Copy another RT_CONFIGnnn (any on...

The command is on your client PC, not on the UNIX server.

This might have to go to IBM support and they will probably just state "not supported". It would seem that even just the dsrun.exe won't work on your 64bit installation. Do you have options to execute the program in some sort of 32bit compatibility mode or 32bit environment from Win64?

Balayya - I don't mean to sound petty, but why can you not do that yourself - you must have DS since you are debugging a script; just choose a job in a project on your installation and execute the command. I'd attach some output if I were at a DS installation, but you should be able to take care of ...

As has been answered twice in this thread already, you need 2 steps, the first to get values from your table and the second to use those values to call jobs. You cannot set parameter values inside the job that uses those values, therefore you need a sequence that does this work and then calls the job.

Is your database on the same server as DataStage? If not, then it might be best to do it in the DB. Even if both applications are on the same server it can be faster to limit the data at the first (database) level. Do you mean that you wish to use non-indexed columns are part of your selection crite...

Although I haven't had my morning coffee yet, it would seem that 4057M is quite close to 3.9G which looks like your physical memory is equal to your virtual memory - meaning no swap!
Does your job repartition or sort the data? This would explain larger memory use.

There is very little housekeeping that can be done from the OS level. I can think of cleaning up the /tmp and Project/&PH& directories, that is about it. The rest needs to be approached from within DS - i.e. autopurge settings for logs.

Blanks are not modified or trimmed automatically in DataStage. A Char(2) definition will have length 2 regardless of contents, otherwise it is a VarChar column. Hmm, I just saw that you posted in PX but marked it as a server job. Data is not typed strictly in server and you could get a length of 1. ...