DSXchange

No, one or the other (not both). Usually I prefer to KEEP unmodified columns - it seems less work.

By "open" I assume you mean "drag onto the design area". Have you tried dragging one from the Stage Types branch of the Repository toolbar? Or do you mean open the properties of one that is already in a job design? Is your client on Windows XP sp2 and, if so, do you have the xpsp2 client patch insta...

We'd love to help you out - which way did you come in?

Etiquette Note
You do NOT hijack others' threads. Your problem is a different one - for example it does not mention the downcast() function. It's a new problem so you should begin a new thread. Try to devise a meaningful Subject for it.

Assuming that it's not already installed (as most administrators seem to install all plug-ins these days) use the Package Installer (from the Start menu on the server) to install it. You will find a folder called DataStage Packages on your Information Server installation media (CD/DVD).

Search
I know for a fact that "DSU.ExecDOS not cataloged" has been answered in the past.

Can you post the exact error message in its entirety, so we can see the stage type that is generating it? Have you involved your support provider (since you may have uncovered a bug)? Are you using any routines?

FLTABSZ sets the depth of the file (table) lock table in memory, FSEMNUM sets the breadth of the lock table in memory. Neither would cause a timeout error - if FLTABSZ were too small you might get a "lock table full" fatal error, but this would be quick, not a timeout.

Why not just include QT in a KEEP specification?

Loading to VIEWS is unsupported.

Seems pretty clear to me!

Is PXEngine mounted/visible on the other machine?

A "check" covers many possibilities. A query against the table is just one of them. Inspection tools such as ANALYZE.FILE are another. Repair tools such as UVFIXFILE or fixtool are yet another.

Upstream of the Aggregator stage use a Column Generator stage to generate a new column containing a constant. Perform the calculation on that. Discard it downstream of the Aggregator stage, perhaps in a Copy stage (which is permitted to drop columns).

As well, you should name your Data Set control files with a ".ds" suffix.

Best practice is to create a directory in which to store Data Set and File Set control files.

You could try DSLogFatal if you really want to abort the job from within a called subroutine. This is definitely not something that would be in my "best practice" category!

DSGetJobInfo(hJob,DSJ.STAGELIST) will return a list of active stages. You may prefer DSJ.JOBFULLSTAGELIST to get all stage names. From that you will need to use DSGetStageInfo() to retrieve a list of link names, and from each link DSGetLinkInfo() can return information about the link. However, there...