DSXchange

Copy/Paste?

More stuff to learn! Aaaarrrggh!!

The archive from Oliver has been there since day 1. Third from the top under Data Services in the DSXchange Forum Index.

For server jobs the main things are to ensure that logs are purged regularly (set project-wide defaults in Administrator), and that unneeded files in &PH& (which is most of them) are deleted regularly. They're on your system backup anyway, so you don't need to keep them for long. Apart from ...

You might try increasing the transaction isolation level in the stage doing the SELECT to at least Read Committed. No guarantees, but I've seen this work in a similar situation (years ago, so details are hazy).

Alas being self-employed I could not justify the A$7400 plus foregone revenue. I'll actually be teaching DS390 while AscentialWorld is happening. Oh, well, this post is another three points! (Don't know where the other 100 came from.)

You usually need CALL to invoke a stored procedure from an ODBC, or ODBC-based, client.

This confusion is one of the reasons those new fields appear at the top when you post a new message. If the OP had signalled that server jobs were implied in the question, an answer pertinent to parallel jobs would have been less likely to have been given.

Search the archives. Some folks have had issues, and worked around them by not upgrading the Oracle client software, and continuing to use the ORAOCI8 stage, even though the TNSNAMES.ORA entry points to an Oracle 9i instance.

The reporting assistant (documentation tool) is to be preferred for another reason. If your data source names, user IDs, passwords, pathnames and the like are parameterized, which is recommended best practice as they can differ between development and production systems and/or can change over time, ...

Beware of an anomaly.

/etc/rc2.d/S99ds.rc (your path may differ) is executed when UNIX is started (or if invoked directly).

$DSHOME/sample/ds.rc is executed when ds -admin -start is used.

You can have two links from Job Activity 1 into a Job Sequencer with its rule set to "Any" and a link from the Job Sequencer into Job Activity 2.
One link has "OK" as its trigger, the other has "Warning".

This isn't a bad idea - it's part of "best practice" for the INTEGRITY product to maintain a cross-reference file containing a (generated) unique key to rows in source data.

Alternatives, depending on the target database server's capabilities, include using a sequence in the database (for example, in Oracle, SEQNAME.NEXTVAL) or using a serial (auto-incrementing integer) data type for the key column.

Can you start another thread for this? It's entirely unrelated to the original question. The name is that of the DataStage BASIC subroutine generated by compiling a particular Transformer stage; the actual name of the stage is incorporated in the first ten-digit string in the file name, and is docum...