DSXchange

If you have a warning on a job then it does not finish "OK". This will not run the next step if there is no link for warnings. It also does not run the exception handler. The exception handler is only for aborted or stopped jobs.

It is here http://www.dsxchange.com/viewtopic.php? ... ight=dsjob

I am on Ds7.1. It does it correctly.

This works fine at our site. I am not sure what happened.

Try searching ADN.

I think Ken Bland or Craig Hulett posted a really cool one. Ken definitely posted a cool UNIX shell script.

In earlier versions of DataStage this was an easy way to see how a job works. This is not as simple any more. There is a RT_BPnnn file where nnn is the job number. This does get compiled. I doubt if you could still look at the generated code. Hack it and see. I am sure ASCL will be thrilled to see w...

You can also buy DwNav from my web site or I have a lot of free tools that do a great job of automating documentation. On my tips page or on ADN download KgdGenHtml.zip. This is a few jobs which generate nice html documentation one file per job and one file per routine. It will also build an index p...

If you are on version 5 then you need to upgrade to 7.5. Release 7.1 and above sequences work fine. You need to update your profile if you are not on version 5 any more.

I use multiple instances because a job may need to run at the same time. For example at the end of each job sequence we gather row counts. So the instance id is the sequence name and so is one of the parameters. Therefore the same sequence will never finish at the same time unless it is a multiple i...

You could use mget and mput to get multiple files. You need to turn off prompting with prompt command.

mget k*

Will get all files that start with a "k".

Here is a code snipet which gets all the invocation ids for a job. It should get you close. JobStatuses = '' open 'DS_JOBS' to DS.JOBS else goto TheEnd open 'DS_JOBOBJECTS' to DS.JOBOBJECTS else goto TheEnd * ---------------------------------------------------------------------- ecmd='SSELECT DS_JOB...

The dependent jobs of a job sequence are stored in field 31 of the "ROOT" record of DS_JOBOBJECTS when field 32 is "2". Here is the SQL. SELECT NAME, CATEGORY, EVAL "TRANS('DS_JOBOBJECTS','J\':@RECORD<5>:'\ROOT',31,'X')" AS DEPEND_JOBS FMT '35L', EVAL "if TRANS('DS_JOBOBJE...

They should always stop it in Director. It is the proper way. It may not stop it the fastest. A job runs as a separate process in the background. The Director is the proper tool to start and stop these jobs. Designer has a separate connection to the DataStage engine. If you have a job displayed then...

Sure. You can write it to a sequential file but why not do it in a job. You could write it to a hash file or a sequential file in a job. It would be easy to read that from a routine.