DSXchange

In the generated OSH you will see that each operator (stage, simplisitically) gets its input(s) from, and writes its output(s) to, a virtual Data Set, whose control file name has a suffix of ".v". Associated with these operators is the record schema that it processes. It is that that I asked to see.

Have you performed a Search?

Is this a server job (as marked) or a parallel job (as posted)?

Note that "" is not a valid value for data types other than VarChar.

You would need to check what else was happening at the time in Netezza. Any kind of lock on the table can prevent creation of a serializable transaction.

The term "printer segment" is a hangover from the UniVerse database which DataStage used to use for its Repository. There is one associated with each process. The word "phantom" - likewise originating in UniVerse - simply means "background process". That you have abandoned printer segments means tha...

Open Director client in Status view.
Disable display of Categories, using View menu.
Sort by Status.
Find "Running" in the Status column.

When done, re-enable display of Categories.

Create a table definition. On the Format tab of the import dialog specify the column widths. DO NOT include the redefines - limit yourself to non-overlapping elements. When using this table definition in a Sequential File stage make sure that the format is also set to fixed width, and load the colum...

Yuk. It is clearly an incomplete error message. No information is available about whence it was generated, which makes diagnosis difficult. Are you using non-default partitioning? Is there anything in the Transformer code (in RT_SCnnn directory, where nnn is the job number) that suggests that an arr...

Only from before/after subroutine if you want to use BASIC. You can, of course, invoke the DataStage API functions from C, which means that you could create parallel routines to do so, but there is nothing "out of the box".

What precisely do you mean by "not working"? Does it work in a DOS (CMD) shell? Try putting double quotes around both pathnames, and enclosing the entire command in single quotes. cmd = 'FC "E:\DataStageQa\ndw\work\stagingx\25\DEPLETF" "E:\DataStageQa\ndw\work\stagingx\25\DEPLETF"...

Is this the same project that samit_9999 is asking about?

Perhaps the "error" was in your diagnosis - after all "write caching disabed" is a message related to Hashed File stage, not to OCI stage.

Passing Char(250) as a parameter value should be perfectly legal. However to do so from the Job Run Options dialog (running job from Director or Designer) may well prove to be impossible. Create a job sequence - possibly containing just one Job activity - that will allow you to use an expression (an...