DSXchange

I would read the database in a job. You need to get the parameter values in a variable in the sequence to use in a parameter. I would make the sequence multiple instance. Use the source as the instance id. There are lots of ways to get the values into variables. No need to to use environment variabl...

You do not have to use an exception handler. You can execute a failed link which all it does is go straight to last sequencer before the end. Then Job2 never executes and it does not abort. You can have as many links as you want coming after a job or a wait for file. Each with there own status. Norm...

Do you have an after job routine or script? If so then it might have failed.

You might need to call support. I guess you need to reindex.

The operator role probably does not have export rights. Not sure which do and which do not.

Running the job is easy as Craig explains. Just learning the syntax of dsjob command.

This is not easily done within the job. Unless each table has the same metadata then this might be very difficult.

Here is my code from my batch file. SET DsBaseDir=C:\Progra~1\Ascential\DataStage7.5.1 SET DsCompileCmd=%DsBaseDir%\dscc.exe %DsCompileCmd% /h %ImportHost% /u %ImportUser% /p %ImportPassword% %ImportProject% /j %%i /f >> %LogFileName% This is obviously older version of DataStage but all you need to ...

I don't think you can compile a whole folder like that. You need to compile one job at a time. All you need is the job name. I also think you are quoting the command wrong. "C:\PF\IBM\IS\Clients\Classic\dscc.exe" or leave them off because the is no space in the command path. C:\PF\IBM\IS\C...

Double your fun.

There are backup scripts on Ray's web page you can download. The are several. The one most people use does a full export. There is one called DataStageExport.bat which will export a list of jobs. The list name is hardcoded to a specific directory. You have source code so modify this to meet your nee...

dsjob is the easiest. Build you a shell script.
Something like this. Kind of off the top of my head. Should be close to accurate.

You can do the same thing in BASIC by commenting out the wait routine.

ErrCode = DSWaitForJob(hJob1)

This one line waits for the job to finish.

EtlStats does this. There is code in the get row count driver that if the job name is a sequence then it will loop through all the jobs and send each job name to the get row counts job. * ------------------------------------------------------------ * DSJobReportDbDriver * ---------------------------...

If you have special characters like '@' in column names then you need to quote it properly. The connector should know the valid quote character. Have it generate the statement with quote characters. Then try it.

If ODB is your bottleneck then fire your Oracle DBA.