DSXchange

WHY does it all have to be done in UNIX?!!

Parse the output from dsjob -jobinfo

Helping you to write the script, well, that's "professional services" and attracts a fee. Particularly since the requirement is regarded as silly.

Trace files for stage tracing are stored in the &PH& directory. Trace files for server side tracing are stored in the &COMO& directory. They are kept indefinitely; there is no auto-purge mechanism for these.

Welcome aboard! :D

Did you check that DS.REINDEX was actually successful? Or did it skip reindexing one or more tables because exclusive access could not be obtained?

Every database uses locks of some kind to prevent data anomalies (for example lost data caused by two processes trying to change the same data at the same time). This is a big topic. Ask your DBA to explain. The DataStage process doing inserts or updates will request locks. If there is some other pr...

On the DataStage server is better, because you're not introducing the network as a bottleneck.

However, the only actual requirement is accessible from the DataStage server.

The easiest - and correct - way in server jobs is to do nothing . :D Because there are no data types, context governs the use of the result of an expression. Your expression '3 + 2 = 7 - 5' (whether quoted or not) returns 0 which, in a Boolean context, is interpreted as "false" - for example if it w...

Your Sequential File stage allows you to specify how NULL is represented, on the Format tab. By default "" is interpreted as NULL. If you want "" to be passed through, specify a different representation of NULL, such as "<<NULL>>". You might also like to change the pad character to a space. Click on...

You need the executable (excel.exe or msaccess.exe) as well as the ODBC driver. As far as I am aware there is no UNIX variant of either of these.

If there's more data than you've allowed for the write cache (by default 128MB) there's no gain. As a hashed file is populated, writes are to random locations within its structure, as determined by its hashing algorithm. On disk-based hashed files this results in a lot of unproductive seek activity ...

The job is running in MetaStage proxy mode, and DataStage is attempting to determine information from MetaStage about the job in question (the same information is also stored in DataStage - it is seeking to compare the two). What I suspect is happening is that your job was created in an earlier vers...

Try DS.REINDEX ALL when no-one is using any DataStage client. It's possible that the reindexing, though run, was prevented from gaining the exclusive access to one of the Repository tables it needs. If you want, you can check the status of individual table indexing, for example: LIST.INDEX DS_JOBS A...

Unless you have any Solaris-specific commands in your scripts executed from DataStage (which isn't really a DataStage issue)...

Welcome aboard! :D Do you understand that UTF8 is one of many possible encodings of Unicode? You are right in that, theoretically, each code point may be represented by one to four bytes under this encoding. Are you certain that this is how your external data are encoded? The NLS map converts betwee...

Self join? User-defined SQL or, if you're feeling ambitious, generated SQL with one alias in the Table Name field, aliases in the column derivations, and an appropriate WHERE clause with the other alias.

Either delete the file first (so that OpenSeq takes its Else clause) or include a WeofSeq statement in the Then clause of OpenSeq and change the logic so that the loop is executed in either case.