DSXchange

You could if your data modeler has each history column set with the dates that each of the historical values occurred. Since type 2 has a beginning effective date and optional end effective date, you have to more than just pivot, you potential will merge instances of the row when two or more history...

That would be correct. The DS Engine uses dynamic hash files as its storage device for job designs, metadata, routines, and all run-time support files.

All jobs use dynamic hash files. The log, status, config, and temp hash files that go with every job design are dynamic. During a job's execution, it's logging messages to the log, updating the config and status files as it executes. Is this error happening when you have a lot of jobs simultaneously...

Well, sounds like tech support knows about it.

What's wrong with multiple projects? Are your concerns about consistency of standards, libraries, etc if copied into multiple projects? The solution for that problem is to use something like PVCS to library your source code. The lines are pretty solidly drawn on using projects, because categories ar...

Are you concerned about running jobs, viewing the log information, opening the job up and changing it, what's the driving issue behind your post?

Yeah, I know the pivot stage is the other way (columns to rows), but I wanted the poster to become familiar with the terminology. But I still gave the solution away...

You're doing what is called a pivot. You can checkout the Pivot stage. If you want to write something yourself, use stage variables, add an extra row to your input dataset to indicate it's the last row so that your logic in the transformer can output the last group its computed. All you need to do i...

Rather than focus on link collectors, here's some basic questions. There are row buffering and hash caching parameters setup at the project level in DS Administrator. Since you upgraded, are these values the same? You see, if your job is configured to use project defaults, and those defaults are now...

Forget out the deadlock daemon. Anytime the underlying job process is killed thru a kill statement or a server going down, there's no way to update the status of the job without manual intervention. A job is responsible for setting its statuses during run and at completion. So, if the job is killed,...

It will use the first, why don't you rewrite the query so that it stops on the first row, rather than find all rows?

Per the help If you are developing a job for users on another DataStage system, you must label the job as ready for deployment before you can package it. To label a job for deployment, you must release it. A job can be released when it has been compiled and validated successfully at least once in it...

You can always try the Search capabilities, or just skim the forum. No less that 2 days ago this exact same question was asked and answered.

http://www.dsxchange.com/viewtopic.php? ... eturn+code

I'll summarize for you what's been posted: There is NO 100MB limitation on DS. However, you can do many things to make it appear that there are arbitrary limits. For example, you may attempt to load a 100MB file into a table with commit set to 0 and blow thru your rollback space, thus giving the imp...

Because 2 rows have to "merge" into 1. Here's the same solution written in SQL: select key, max(col1), max(col2) from ( select key, col1 "COL1", null "COL2" from table1 union all select key, null "COL1", col2 "COL2" from table2 ) group ...