DSXchange

DTM, MODIFIER and REASON are multi-valued columns within the DS_AUDIT table. Together they form a "nested table" called MODS. You can see all this with LIST.DICT DS_AUDIT. To expose the MODS table, one way is to use the UNNEST operator in the FROM clause. This "explodes" the other columns (the singl...

Three methods (at least) are available, and that's without writing a program. Method 1 Define a "spool channel" output as a disk file. SETPTR 3,132,20000,0,0,3,BANNER filename,BRIEF Channel number (the first argument) can be anything from 0 through 255. The other numeric arguments, in order, are pag...

I think you'd be surprised at how large DataStage allows VarChar to be!
Whether the database server can manage VarChar(64000) is a different question!

Well, you're re-inventing the wheel by wanting to run job B for each row processed by job A.
Look in the Routines branch (sdk\Utility category) at the routine called UtilityRunJob, which does exactly what you're trying to achieve.

You will have to un-protect the project. The point of a protected project is that it does not allow change. Import the Routine into the unprotected project then re-protect the project. Of course, you will need to be in a group that is a member of the DataStage Business Manager role for this to be ef...

You have to figure out, perhaps by DESCRIBE, perhaps by inspecting ALL of the metadata in your job (for example, are any parameter markers binding to the wrong columns), why Oracle expected NUMBER. Create a test job that only accesses this one column. See if the problem goes away. If it does, the pr...

Provided it's a PROGRAM (and not a FUNCTION or a SUBROUTINE), the following steps are required. Get to the UNIX prompt. Ensure that your $DSHOME environment variable is set to the correct value (the location of the DSEngine directory). Execute the $DSHOME/dsenv shell script. Change directory to the ...

Hashed files are not used in parallel jobs.

Lookups are performed with Join, Merge or Lookup stage types.

It's a completely different approach to that used in server jobs.

The (parallel) Transformer stage does, indeed, support only one input link.

You've posted in the Parallel Extender forum.

The Parallel Sequential File stage does indeed have these properties.

Now you're complaining that the same properties are not there in server jobs.

It is NOT THE SAME STAGE TYPE!

"is not in a runnable state" is an error message that suggests that your job was not eligible to be run. Your assertion that the job is in a runnable state is therefore questionable. The only possible states in which a job is eligible to run are "Finished OK", "Finished (see log)", "Validated OK", "...

Which view in Director? Status view needs to refer to the RT_STATUSnnn table for each job in the currently selected category. (Hint: don't have too many jobs per category.) Log view needs to refer only to the RT_LOGnnn table for the currently selected job, but this may involve a large number of even...

You can purchase UniVerse from IBM. But, is that what you really want? If (as other threads suggest) you are trying to create DataStage BASIC programs, then you need a DataStage BASIC compiler. This is not compatible (any more) with a UniVerse BASIC compiler. Each will successfully compile the same ...

Everything in the UniVerse BASIC and DataStage BASIC manuals assumes that you are interactively in the shell (uvsh or dssh respectively). To achieve this in DataStage you must be attached to a project directory, have executed the dsenv script (on UNIX only), and have issued the dssh command ($DSHOME...

Error code 39204, you can ascertain from the InterCall Developer's Guide, decodes as "slave failed to start correctly".
Looks like a (temporary?) process allocation problem.

Search the forum for other instances of 39204 and "slave".

This has got to be a recent change. I'm running 7.1r1 on AIX, and dsjob -lprojects alone was fine. Followed that with dsjob -ljobs projectname and that with dsjob -lprojects again. Everything was OK, with status = 0. Perhaps there's something you missed out in your environment? I have execution of $...