DSXchange

As a start, I'd take the advice in the error message to set your PWD environment variable to a value that will work on all nodes of your system.
Then see whether the other error still happens. Certainly the generated code isn't rocket science!

Use the correct tool. That's not what DataStage is designed to do. If you must process header and trailer information, do it separately from the detail rows. Perhaps in other jobs or in commands or routines invoked from a job sequence. 1. Create the target files with the header information. 2. Appen...

PLAN what you need to do. Write it out in ordinary language. Convert this to pseudo-code, so you get the logic right. Consult the Parallel Job Developer's Guide , particularly Chapters 15 and 54, for information on how to implement. Within Chapter 15 is a section on the Expression Editor, which (amo...

chulett wrote:I think you'll find that 'Player' is specific to the Orchestrate underpinnings that power PX.

True. Orchestrate gives you a Conductor and a number of Players. Wonder where they got their terminology?

The hot key for invoking the Filter dialog is Ctrl-T

Try a search of the Forum; others have encountered this before.

Hint: use "all terms" when searching for reject datasets

See, for example http://www.dsxchange.com/viewtopic.php?t=85439

Read the chapter on DataStage Developer's Kit (Chapter 52), in particular the section on Command Line Interface (dsjob) in the Parallel Job Developer's Guide.

You specify storage in the configuration file for the job. (You can have more than one configuration file, for example small jobs may not need as many processing nodes as larger jobs.) For each processing node in the configuration file you can specify as many data and scratch locations. Read Chapter...

Read the chapter on DataStage Developer's Kit (Chapter 52), in particular the section on Command Line Interface (dsjob) in the Parallel Job Developer's Guide.

Why would you want to? If you want to write routine then I could explain how. You would need to get the job number from DS_JOBS. Next you would need to delete that record plus records in DS_JOBOBJECTS and several hash files associated with that job like: RT_STATUSxx RT_LOGxx RT_BPxx RT_BPxx.O DS_TE...

Check that the storage of particular data types remains compatible. I think it does, but don't have the means to check. For example INTEGER should be four bytes (if they've made it eight bytes this may lead to problems unless its data type is now reported as LONG INTEGER).

Export/import does not copy hashed files. After all, these are intended as temporary storage.
If you have copied hashed files such as SDKSequences, you now need to create pointers to them in the VOC file. To do this use the SETFILE command. Search the Forum for details.

Are you trying to INSERT or SELECT? In either case, specify sequencename.NEXTVAL (as indicated earlier) If it's a SELECT (your ORAOCI stage is extracting rows from Oracle) you can specify it in the derivation column. If it's an INSERT, the easiest way is to write your own SQL, adapting the generated...

We received this error on numerous occasions due to a lack of resources. DataStage and SQL server were running on the same machine, the administrator of the box being a SQL fan, treated DS like an orphan and had it share the operating system's cpu while allocating all the other cpu's to SQL. When w...

Jump into a UNIX shell and learn about the sort command (man sort), in particular how to specify sort keys. It's quite a powerful command. Or you could invest in the CoSort stage, and invoke it from DataStage to perform the sorting. There is a Sort stage (no extra charge) in DataStage. It's the slow...