DSXchange

Your jobs should run as normal. There have been a couple of threads suggesting a couple different metadata warning or error messages could occur so you need to test all jobs. The lookup stage is much easier to use and looks more like the transformer stage. It shouldn't affect the design of your jobs...

Thirty job activity stage, youch! Do you have the same common parameter names appearing in most if not all of those jobs? Consider dragging and dropping your jobs onto the canvas and then exporting to dsx, open in a text editing tool and use search and replace to set your parameter values. A lot fas...

If you hook up the servers and install DataStage what you have is a cluster. A lot of manual configuration is required in the DataStage config files to get the jobs to run over the cluster. If you add grid management software what you get is a grid. This is far more clever at load balancing and allo...

The message handler only works on parallel jobs, not sequence jobs. I'm surprised it aborts your job, I thought it was a non fatal warning message. You could redesign your load id logic so it is retrieved from within the sequence via a Set Variables stage. For example storing it in a configuration t...

Read the FAQ How do I remove duplicate rows from a data source? It shows several options.

The only time I've had to disable it was when I had a lookup stage followed by a transformer stage and rows were being passed down the wrong reject link. Don't remember the exact details but it had something to do with the lookup being set to continue so the transformer could handle and reject faile...

Monitoring of CPU usage, RAM usage and I/O bottlenecks will give you a more complete picture of why your performance is slow. I would prefer to see each node using resource and scratch space in different locations to make it easier to monitor and improve.

The click pack web log reader stage is very efficient and it comes with some server routines that help parse things such as URLS. Are they still charging extra money for it? Thought it would be free by now.

You can add an environment variables to your project specific environment variables (which gives you more control over them) and add it to your job as a job parameter using the add environment variable button. It can then be used in the transformer using the $VariableName syntax. You can only add en...

You can also run your existing BASIC routines from sequence jobs. This can be more convenient then putting it in after-job as you get triggers for controlling when it gets run. I've got to admit I don't think I've ever chosen to use a before-job or after-job routine, I've always opted for doing it a...

I never trust these saved table definitions. You should be able to access all stage column names within MetaStage. I use stage naming conventions to identify the name of the table (for db stages) or file (for sequential file stages) to help with metadata reporting. Makes it easy to follow source and...

The pump307 user is not a genuine forum user, the five posts from this user are meaningless single line messages designed to put the gambling site advertising in front of forum members, I'm sure this person is doing it on a lot of other forums as well. The login and the profile should be deleted by ...

You do have DataStage SOA Edition don't you? My understanding is you have an XML Input and/or XML Output to your job and SOA Edition magically turns it into an EJB.

That's right. You set it up for a generated upsert and that gives you a generate insert and update statement. You copy your insert statement into the clipboard. You switch it to user-defined update and then paste the insert statement into the entry screen and modify it to suit.

Wish I had a dollar for every time a QualityStage job runs better when executed from the client then from a plugin or command line. First check your data directory, is the job running in stream mode? Is it trying to write out a data file for each step or carrying the data through in memory? Second c...