DSXchange

The TRANS1 file is the Transformer stage code, not the routine code. The Routine code is viewed in the normal code editor for Routines. Put some debugging statements in, possibly controlling their compilation with $DEFINE, $IFDEF and $ENDIF compiler declarations. Find out what the values of things a...

Parallel jobs don't use the same NLS maps as server jobs use. You have marked the job type as Parallel.

Describe fully how you are loading SQL Server. Are you using insert-only, update-only, or one of the combinations. Are you using parameter arrays? How many rows are you sending per transaction? All these settings will affect how efficiently DataStage (ODBC stage) can communicate data into a SQL Serv...

Linux, like other variants of UNIX, seems less bothered about NFS-mounted disks (except during installation and for some administrative capabilities) than Windows. Provided, that is, that you leave the uvconfig parameter ALLOWNFS at its default value (which allows access to NFS-mounted file systems).

Prevention is always better than cure. We say over and over that kill -9 is a no-no for DataStage processes, for lots of reasons, but people keep doing it.

There are correct ways to get a job to stop. A SIGKILL signal is not among them.

Connectors are like shared containers - locked while open for editing, or even if potentially open for editing (that is, a job that uses them is open for editing).

There's a lot more valuable information in that post, if only you had a premium membership. Premium membership costs less than 30c (Rs12) per day and gives a number of benefits, including the ability to read the entirety of the five premium posters' posts. All revenue from premium memberships is dev...

You won't see any error messages there - that is simply a message telling you that compilation of the Transformation stage is complete. When you click Show Error, which stage is selected?

It needs key-based partitioning (whether Hash or Modulus) so that every key value has all its rows on the same partition, so that (necessarily) the pivot will generate the correct number of rows per key.

Not all APT environment variables mentioned in the manuals are automatically included in the project. There's nothing to stop you adding the ones that aren't already in the project, using the Administrator client or by editing the DSParams file for the project.

The Join stage will almost never give better "performance" (less execution time) than a homogeneous join performed in the database. There are two main reasons for this; first, the database almost certainly has indexing on the columns involved in the join criteria, so that the join can be resolved in...

Maybe they are allowed in the RMM stage?

No, I was actually asking about when you are browsing for a directory (folder) within the View Data dialog or the response to a pathname-type parameter dialog.

Please Search

Take a look in the Transformer stage constraints dialog - there should be a row count limiter there. But the job status would then be stopped, so it would need to be reset. Before that, you would need to establish where it got up to, so as to begin the extraction phase (or maybe just the load phase)...