DSXchange

No, you still need at least one machine with DataStage on it. That's where status gets recorded and events get logged. There is no "run time only" potential.

COMO ON can not take a pathname. It only takes a simple file name, and creates this file in the &COMO& directory in your project. If you want to use a different location you might like to investigate the DIVERT.OUT command as an alternative but even then you will need to create a file point...

The Oracle Enterprise stage is only available for parallel jobs.

When you open its help, the word "Parallel" should feature in the background image.

Use the Field() function. To get the rightmost field, count the delimiters (space characters). Field(InLink.Address, " ", Count(InLink.Address, " ") + 1, 1) An even better approach would be a QualityStage STAN (standardization) job, which can accurately parse free...

Every record has a minimum 13 byte storage overhead, usually larger. There are forward and backward pointers, each 32 bits or 64 bits, and another "flag word" of the same size. There is a single byte between the key and data (a "segment mark"), a single byte between each field (a "field mark"), and ...

Another technique is to use a hashed file updated in real time. This technique is taught on IBM's Advanced DataStage (Server) class.

Welcome aboard. :D You are using a non-English Windows on your client machine, that uses code page 936. However you have installed DataStage server without NLS, or you have failed to specify that the client is using code page 936. To correct the first, simply re-install DataStage server, checking th...

But it wouldn't hurt, if you decide to do it "just to be sure". One of the new goodies that you won't get in 6.0 is the Multi-Job Compile tool, though there are third party tools, such as CompileWitch (written by Wolfgang Huerter) or Compile-All (from Tools4DataStage) that can do a similar thing.

Another possibility is to expose the DB2/390 tables as if they were local using DB2 Connect. The fact that they are actually on the mainframe is then transparent to DataStage.

Or:
SeeBeyond
Control-M
UC4

There are lots of third-party schedulers out there.

You can even write your own! Even in DataStage BASIC, as a job control routine that runs continuously (or almost continuously).

There is a .profile file (on UNIX) for each user who can log in. It is the "auto start" script for that user, and typically sets environment variables, alias definitions and the like. If the interactive user is likely to need DataStage commands on the server then you might like to include the DataSt...

The FieldStore() function can insert a value into a delimited string. Research it in on-line help or in the DataStage BASIC manual.

It's also useful - if you don't set it in dsenv - to set it in the .profile of the dsrpcd user.

It's also good to know that Jim Tsimis is still with the product. He has a happy knack of being able to solve the really strange errors. It was Jim, way back, who proved that the "replace delimiters with line terminators and write to sequential file" method of vertical pivoting was very fast. (Note ...

No. DataStage parallel jobs execute osh (Orchestrate shell) scripts. This (the osh executable) is part of DataStage and must be available in order to execute osh scripts. So must all the various libraries it calls in order to connect to data and so on. When you run parallel jobs on a cluster (an MPP...