DSXchange

Check out this post if you think Sequencers are the highest form of job control: m A BATCH can be used to execute your own job control APIs. I don't use the BATCH as anything more than a glorified shell script, but it sure is powerful. I wrote a library of job control, and use a BATCH job as the stu...

Thanks Kenneth and Ray! We avoid having stage variable solutions if possible b'coz the code is not re-usable.Actually the Routine does a lot of verifications(lengthy code) and its kinda hard to implement it as a stage variable. Anyway, now that Ray has passed it,I will use it in peace regards Essen...

Put your verification as the derivation in a stage variable. Then, use the stage variable in the constraint to an exception link. In the exception link, capture the offending row to a file for review. Set the abort job row limit in the constraint to 1. The first row to qualify for that link will abo...

My guess is a permissions error. Make sure you can see this file internally, not just from a directory listing. Also, you can vi a sample file and just experiment with how importing works.

All of this documentation is available on your Start Menu --> Ascential DataStage --> Online documentation. Look at Manager client documentation.

Under Administrator you can set the userid that scheduled jobs run under. Have you configured this? If manually running the job from Director, it runs as you, if running from the schedule, it runs as the person who scheduled it. If the person who scheduled the job does not have access to all resourc...

I am curious why shouldn't i use DSLogFatal, Stop or Abort in routines in the routines ... mainly in my case if i found zero records anyhow i need to abort the job... and also instead of writing a basic routine to check for zerorecords in a file can i do the same using @INROWNUM OR @OUTROWNUM ... w...

All of this documentation is available on your Start Menu --> Ascential DataStage --> Online documentation. A Routine Activity stage allows you to execute a custom routine created in DS Manager as a task in your Sequence job.

You cannot have a job open up dialog boxes or interactive GUI programs. DataStage jobs are compiled programs, mean to run in a non-interactive background executing mode.

If you insist on something like this, then do not use DataStage.

Hey, how many places you going to post this message???? I replied over at http://www.dsxchange.com/viewtopic.php?p=105433#105433

What a great question! The answer is, if you're processing 65 million rows, you need to be using a "partitioned parallelism" approach. This means that you divide the source dataset into smaller segments, and then use multiple instances of a job to simultaneously process those segments. So, if you us...

The poster is on DS 6.0, so they should be using the wire protocol drivers. For those on earlier releases, yes, the ODBC piggybacks the OCI.

Adapt your function to accept a delimited (spaces, commas, whatever) string of filenames. Then, loop in your function thru the number of filenames and make your decision from there.

In a parallel job, you're using OCI, so it's sqlnet. In a Server job, using an OCI stage, it's also sqlnet. Using an ODBC stage obviously is ODBC.

Look at this post, I break down a hash file for you:

http://www.dsxchange.com/viewtopic.php?t=85364