DSXchange

Determine the environment variable's value however you like, for example using Call DSExecute("UNIX", "echo $HASHPATH", HashDirPath, Code) The result is in the variable called HashDirPath. Build your SETFILE command. Command = "SETFILE " : HashDirPath : "/&...

You won't see a variable called $R61 in the code; this is a temporary variable used to hold some intermediate value in an expression. It will, therefore, be that more difficult to track down. Test your Routine rigorously; make sure there is no path through it in which any variable (including the arg...

Re-read what you asked, which Mike has highlighted. The purpose of a lookup is to find what's there. If it's not there you can't find it! Therefore there will be no "unmatching records". As Mike said, it appears that you're seeking to perform a full outer join (or union); all values irrespective of ...

In earlier releases, $? returned the exit status of dsjob , not necessarily of the DataStage job itself. In recent releases (7.1 and later?) this behaviour was changed. For a couple of interim releases, it was necessary to specify -jobstatus rather than -wait to have the exit status report the final...

RTI Services is an add-on (= more money) and comes with a manual describing the APIs for Java, COM and C. More precisely, the Quality Stage Real-Time client includes this manual. It's not horribly difficult; there are only six classes in each API, and the methods and properties are pretty much what ...

You need to monitor the server with the $DSHOME/bin/list_readu command, to establish what locks are held. Also have support advise which part of the code generates this particular message. The only time I've seen it is while an administrative function that requires exclusive action is running. Could...

Try changing AS LINK_NAME (which sets up an alias) with COL.HDG 'LINK_NAME' (which merely sets up a column heading). I got the same alias problem; changing to COL.HDG fixed it. You may get repeats (for example in jobs where two input links run into the same hashed file stage). You can, of course, el...

It is not possible. DataStage does not permit retrogression via exports (or by any other means of which I am aware).

Document your job from 7.5, perhaps using the Reporting Assistant. Then re-design the job (yes, manually) in 7.0.1.

You don't have to configure the template, it works fine as is. You can configure the template if you want to - that's an entirely different thing! Fairly complete instructions are within the template itself. Take a look at the DSSendMailTester routine (category Built-In\Utilities), which allows you ...

This can also occur trying to access a topic from "n new posts", which I guess is a search under the covers. There is a workaround; you can get to the forum via its link, rather than to the topic via its link. Of course, with new posts they're always at the top; for subject-based searches it's not s...

The best, and easiest, way to do this is to involve the DataStage Real Time Interface (RTI) Services. You can read the marketing blurb on the Ascential web site . Essentially, the RTI Services allow you to: run DataStage jobs in batch mode run DataStage jobs that use an RTI Output stage so can deliv...

Because, for server jobs, it is immaterial whether the table is partitioned, so the check is not performed.

It is not permissible to change the value of a job parameter once the job has started. Job parameters are read into a static area when the job is started, and are ineligible to be changed. Even if you can change the value of the environment variable upon which a job parameter is based, the value of ...

The problem is, what becomes of the result of the SQL query in the first job? Presumably this is being written to a sequential file. Your Job Sequence, therefore, should run the first job then introduce some way to determine whether the file has zero length or not (use a Command Activity with the te...

Probably easier to do it via editing an export file than trying to get at parameter values through the Repository tables themselves. Remember there are three sets of parameter values if you do it the latter way; the design time default values, the run time default values (set in Director), and the a...