DSXchange

I prefer to use DSTransformError() or DSLogInfo() to PRINT. You can also use compiler directives $DEFINE, $IFDEF, $IFNDEF, $ELSE and $ENDIF to "conditionally compile" your debugging statements. When debugging is done, simply change $DEFINE to $UNDEFINE and recompile, and your debugging statements - ...

It's not a problem unless you actually want to work with DataStage roles in the Administrator client - that is, it does not prevent any other Administrator functionality.

I think, if you install with the Operator's licence (xxxxxx-DSDIR) on the Operator's PC, you will get pretty much exactly what you want. The Operator role only allows the running of released jobs (at least up to version 7.0) and does not allow viewing of log entries that might contain data (unless t...

Prefer DataStage constants, in case "they" change the values.

When DataStage Engine picks up a multi-line entry or result it converts all the line termination characters to a special character called a "field mark". This means that you do not need to be concerned whether you are processing a UNIX or a DOS line terminator, and it also means that there are no li...

You are correct. This is not something that DataStage does. But DataStage can control the shell script(s) that you create to perform the movement of files. You can use an Execute Command activity from a job sequence, or you can use a before/after subroutine from a job, for example ExecSH (the task o...

It's not available out of the box. The technology is well-known - do a Google search and create a parallel routine.

You changed your ulimit, but not the one for the ID under which DataStage processes run. That's why Arnd had you check via a before-job subroutine. The dsenv script is executed by all DataStage processes. However, on some UNIXes, only superuser can increase ulimit - you may need to ask your System A...

A search would have found that your question has already been answered, for example here

Could you pre-populate a Lookup File Set with just those rows that satisfy the range restriction, then do the lookup solely on the natural key?

Umm... 32 is Seq(" "), not Seq("0")

This "no design information" message can also result from a job having been "released" (the precursor to Version Control), which creates a new version-stamped job that is never able to be changed again. How they achieve this is by removing that job's ROOT record for that job from DS_JOBOBJECTS. In t...

It would be very difficult to bar "production access from DataStage clients". I've not seen this requirement at any site. Most use Version Control or other means to make job designs read-only; it's kind of vital to have access to the logs unless you want to create job sequence activities or after-jo...

Sounds like they've changed the message (I've been on a 7.0 site for a couple of weeks). Has anyone had a response from support provider about what might cause this? If it occurs because of client licensing, you (the administrator) can check the DS_LICENSE table to see which client machines are actu...

Reporting Assistant was deprecated some time back in favour of MetaStage. It (Reporting Assistant) does not do job sequences and does not do parallel job.