DSXchange

When you use DSAttachJob specify "JobName.InstanceName" to get the unique information for that invocation.

There is no DECODE function like that built into DataStage. There are various ways of doing this starting with a long IF-THEN-ELSE or a CASE statement. How you solve this depends upon what your primary objectives are - simplicity or performance.

There are hundreds of different "decode" functions out there in the programming world. Which one are you referring to?

Perhaps you have defined a user routine or transform that does this for you, that would explain why the command is case sensitive.

Julien,
"NVL" is not a DS/Basic builtin function which is why you are getting this error. You can substitute a IF ISNULL(In.Col) THEN 'value' ELSE In.Col for this functionality if you wish.

The short form is to use the DateFromDaysSince() function.

The reset will only change the status of one job at a time, not the parent or dependant jobs. Or perhaps I misunderstood your explanation. I can't recall a reset not doing -something- to a job in a project where everything else is working. If you don't have a busy machine you can clear out the conte...

You have successfully converted your string to a date, but that datatype doesn't allow numerical math to be performed on it, so DS tries to convert the date to a dfloat and fails (because no implicit conversion rules are defined). You need to use one of the date conversion functions such as DateFrom...

The project that you loaded the jobs into does not have the Red Brick load stage installed but the jobs try to use that stage. You will need to install that optional stage. If you don't know how to do this, the documentation has a pdf file (something like) " Supplemental Stage Installation Guide " t...

Is the error repeatable, i.e. if the job aborts now will a reset put it back into a runnable state? When you did a reset of the job, did it put any messages into the job's log file?

pre-sizing the modulo on a dynamic file and/or using a static hashed file of appropriate size works well. Also, do you have row buffering enabled? That will increase your speed. Are you sure that your hashed file write is the bottleneck? If you do short test and change your hashed file stage into a ...

I just re-read the post and realized that I misunderstood the question regarding nulls vs. normal padding. My mistake. I'm not at a DS enable computer now, but I was fairly certain that the row attributes have some setting letting the string be padded. If someone else doesn't give a solution I'll se...

If you define your output columns as fixed char with the appropriate widths, DataStage will implicitly perform the character conversion and add the space padding. But in order to do so you need to explicitly declare the lengths.

Making changes to a job will affect several OS files in a project. You cannot do a job-level save of DataStage jobs from UNIX. Version control and the old trusty .dsx export file are your only ways to do this.

Meena, you can specify optional arguments in user routines; but the number of parameters used in Before/After job routines as in the original post is fixed and you cannot change that.