DSXchange

ray.wurlod

For consistency of approach and to allow for the possibility that there may be other Transforms created that end up calling the same routine. For example look at the Transforms TIMESTAMP, TIMESTAMP.TO.DATE and TIMESTAMP.TO.TIME, all of which process timestamps, and all of which invoke the same routi...

ray.wurlod

Look in JOBCONTROL.H (in the dsinclude directory) to learn that -1 means "invalid job handle". You have not properly specified the first argument (the job handle) for DSGetLinkInfo. Or you have used DSJ.ME as the first argument for DSGetLinkInfo in a routine but not loaded the contents of the JOBCON...

ray.wurlod

Because, as Shawn rightly said, implicit row buffering only occurs on a link that joins two active stages. Your job design only has one active stage (the Transformer stage).
Explicit IPC stages force a process boundary to exist.

ray.wurlod

Beware that hashed file names not only must be spelled correctly but also are case-sensitive.

ray.wurlod

Please visit the SQL tab on the link properties and post the SQL that you find there.

ray.wurlod

That sounds like a challenge! It would be a particularly horrible SQL query, and probably end up exceeding the maximum permissible length for a query statement. Even if you knew the internal structure for records in the DataStage Repository. And if you use job parameters for table names, the problem...

ray.wurlod

Go to Ascential web site and search for "benchmark". Read the first article.

ray.wurlod

Welcome aboard! :D Have the column definitions been edited and/or loaded more than once? If the column name has been replaced, it may not have been properly deleted in the Repository, leading to this error. Try removing ALL column names from this link, and then re-loading them. Note that the collect...

ray.wurlod

Is it always this particular hashed file? If so, this particular hashed file may be damaged. You can verify this using the uvfixfile utility or the fixtool utility. Otherwise, as Ollie suggested, there may be too many dynamic hashed files open system-wide. Use the command analyze.shm -d to find out ...

ray.wurlod

You can not use LOGTO from the Administrator client. It is one of a select number of commands (HELP is another) that are explicitly blocked. If you type DS.TOOLS (which brings up a badly-formatted menu) then respond with 5 (which brings up an equally badly-formatted menu), then respond with a zero-l...

ray.wurlod

This may be more efficient. Both the Fmt() function and the Iconv()/Oconv() function can perform rounding/truncation. Rounding is the default.

Code: Select all

If Num(Arg1)
Then
    Ans = Iconv(Arg1, "MD0")
End
Else
    Ans = (If Alpha(Arg1) Then 0 Else @NULL)
End

ray.wurlod

Craig summed it up well. Things will not break, if that's what you were concerned with. However, there is a computational penalty (recall that DataStage is primarily a 32-bit environment, so has to construct 64-bit numbers) as well as a space penalty (there are three or five pointers per record, so ...

ray.wurlod

The lookup will not even be performed if any S.columnname is null.

ray.wurlod

Which part of "requires" don't you understand? Seriously, though, CDC uses the primary key as the mechanism for identifying the row(s) that it needs to select. I don't believe that you'll find a workaround. If my memory serves, CDC uses a persistent queue (such as the transaction log) to identify ch...

ray.wurlod

Welcome aboard! :D You're going to have to do some diagnosis. SQLAllocStmt is part of the ODBC API, so I deduce you're using an ODBC stage or a stage type that employs ODBC protocols. Have you correctly configured the ODBC data source name (DSN)? You need to do this not only in .odbc.ini, but also i...

Search found 53125 matches