DSXchange

A job cannot change its own parameter values during runtime. The job control tab is used to control other jobs. Search this forum, we've covered job control and job parameters ad nauseum. If you which to feed job parameters, use the controlling Sequence, Batch, or command line options under dsjob to...

Type it in, or add another job and replace the name and parameters with the appropriate information. Not necessarily clean, but it does work.

Yes. The API's documented in your DS manual are the same ones used by Batch and Sequencer jobs. There is no difference between any job types (Batch, Server, Parallel, Sequencer, etc) when it comes to running them.

If your column is that wide in content you will want to inspect the contents from the command line as the client job has limited functionality to do so. You cannot resize a column wider than the screen, as you can't stretch the column big enough. Plus, the left-to-right scrolling is not well built. ...

You must build an exit strategy into BASIC or Batch jobs. Either poll a directory periodically for a "touch" flag file and stop when found, or put a timeout. One way to kill is to use kill on Unix and Task Manager on Windows. In your case, you must have access to the server console. Another option i...

Other than using manager to mass move jobs (doesn't require renaming, just select all and right-click Move-To option) you would have to use a hack at the internal folder structure attribute in DS_JOBS file or do an export and textsearch/replace in the .dsx file.

Your link.column value either has an case mismatch or leading/trailing spaces, from what I can guess. I suggest you find out the exact contents, and either apply a TRIM and/or UPCASE function where appropriate.

Make sure you use quotes around literal values being compared to character columns. If you use literal values that are numeric and compare them to character or numeric columns, then you're okay. x is integer x=10 is okay x=A is bad x='A' is okay x is char x=10 is okay x=A is bad x='A' is okay

You just can't use any specialized keywords or comments that only ORACLE recognizes such as rownum, sysdate, to_date, or hints like +PARALLEL(xyz,10) or +USE_HASH(abc,xyz) or +INDEX(xyz,xpkxyz) as those aren't transportable to other databases.

The before/after routines are for doing something either before the first row enters the transformer or after the last row exits the transformer. If we understood what you're trying to do we could answer better. To call the routine simply write it in DS Manager, compile it, and it will appear on the...

You can only import older versions of DataStage into a equal or newer version of DataStage. You also cannot import jobs that contain plugins for which you haven't installed. You also cannot import PX jobs onto a Windoze implementation.

While grid computing (Seti@Home) is cool, I have a hard time imagining this type of processing paradigm being used. That's what PX on Windoze will ultimately be like, grid computing. PX is great in that you can harness a handful of servers, both SMP and MPP, to leverage all technologies to move the ...

Why start with 5? Let's walk down memory lane and start with 1 and don't leave out all of the companion products.

You need to have access to the server. Under the control panel should be a big A for Ascential icon. Click on that to see the services. Alternatively, you could find the Services icon and look for the engine that way.

The point is always use WEOFSEQ will be required if you are opening an existing file. If you fail to use it, you could potentially have a "merged" effect of what you just wrote with what already existed in the file. This is absolutely an issue if you write fewer characters to the file than what curr...