DSXchange

That the underlying engine (uvsh) has generated a SIGINT doesn't help you to diagnose the problems; it uses signals for very many things. This requires specialist analysis; preserve the core file and report the problem to your support provider. They may need to analyse the core file. You may find a ...

There is substantial overlap between what ProfileStage (formerly MetaRecon) and AuditStage (formerly Quality Manager) do, but enough differences to warrant separate products - though "they" may merge the functionality one day. Both look at the actual data (rather than the metadata) to determine what...

It's usually in a constraint expression or output column derivation (occasionally in a reference key expression or stage variable initialization or derivation expression) left over after changing the name of an input link. If you ever change the name of any input link to a Transformer stage (particu...

1. What are the different types of Hashed files? Static (the number of groups is pre-set and does not change except through intervention) and dynamic (the number of groups can change dependent on the volume of data stored). For more information, search the forum. There are seventeen "types" of stat...

Except for the pathnames there are no differences between hashed files on UNIX and on Windows. The internal byte order may differ but that's governed by the type of CPU chip rather than by the operating system. There are, for example, some UNIX variants that run on Intel chips. In any case, the inte...

Server jobs have no data types. Parallel jobs are strongly types. As already noted, a Char(x) column (in a schema string[x]) must have precisely x characters. A decimal data type value must have not more than the correct number of scale digits (to the right of the decimal place). All numeric data ty...

I have x86 family process and Windows64 that can handle 32bit applications! So if we follow the terms of formal logic DataStage can be installed on Win64. Where "formal logic" breaks down here is that DataStage engines make calls to system functions that may not exist in Win64. That's why we have t...

Welcome aboard! :D My guess is that, on the original server, the parameter mentioned in the error message was passed from a controller (job sequence?) or environment variable but this is not occurring in the new server. Another possibility is an incomplete export/import, in which that parameter did ...

It matters for performance. FileA should be the larger.

Do it in a job sequence rather than trying to use a before-job subroutine; your search will reveal that a running job cannot change its own parameter values. In the job sequence use an Execute Command activity to execute the command. In the Job Activity that runs the job can set the parameter using ...

Version Control includes the ability to version directories (folders) that are not part of DataStage, for example in which you might store scripts. The way it's written it requires the directory to be in the project directory but I have found that it's happy if there's a symbolic link (shortcut) in ...

That record (J\328\V0) contains the layout of your design canvas. If it's not there you've got major problems. Get an experienced consultant to check the views from J\328\ROOT to determine whether there's a different base view. If not, you really will need to import a new version of the job and to d...

For example

Use DSExecute with the first (Shell) argument set to "DOS".
The third argument contains the output. All of the output, with each line returned as a field in a dynamic array.

Your maximum record size is 95 bytes plus overhead. You will get no value from decreasing LARGE.RECORD, as your record sizes are too homogeneous. SPLIT.LOAD provides a "safety overhead" per group. Groups on average will fill to this level. However we don't live in a perfect world, so some groups wil...