DSXchange

Most maintenance tasks are on the design-time tables, so you could create a BASIC program that sets a table-level lock (FileLock) on the relevant tables (particularly DS_JOBS and DS_ROUTINES). Running jobs should not affect most maintenance tasks.

Director. Status view.

"ASCII" or binary transfer? Take DataStage out of the picture - do an FTP without DataStage to determine whether your FTP mechanism is the culprit.

Welcome aboard. :D First, please read this post which explains the purpose of the FAQ discussion thread. In future please post in the correct forum. Second, the last release of DataStage to be built on UniVerse (note the capitalization) was version 5.2. So, unless you are on this version or earlier,...

An "all items" search for "not open RT_CONFIG" yields 22 hits, some with answers.

More concerned for now how to use a Wait For File activity on UNIX to await the appearance of a file in a Windows folder, which it appears is what vsi wants to do.

Interesting thought, Ross, but probably not the culprit. SDKSequences is created as a tiny static-hashed hashed file (fits on a single page), so there is an almost 100% certainty that it can't be corrupted. A quick test would involve the following commands, issues from the Administrator client Comma...

"Hardcore" is a good word, if inadvertent. To do this in a single query would be impossible (recursive SQL does not exist in DataStage Repository). You would need to identify job sequences in DS_JOBS then, for each, generate a list of the jobs run under its control based on records in DS_JOBOBJECTS....

It specfies that, whatever your DSN is, it loads a driver called the "20101 driver". I have no idea what that is. Look in your .odbc.ini file for the definition of the DSN in question, and determine from there what is, and perhaps what should be, in the entry. Particularly with regard to the driver.

This will be quite a tricky exercise if DataStage really is on a UNIX server. Do you use samba or some similar protocol to make Windows folders visible to UNIX? Unless this is the case, I doubt that DataStage-on-UNIX is the correct tool for this task.

Welcome aboard. :D

Each new release is accompanied by a "readme" file which lists the changes in that release. The vendor's web site, or the DeveloperNet website, are probably the best place to source these documents. Or request them via your support provider.

If you are in a country with official postal certification (such as CASS in the USA or SERP in Canada) then you can get data files containing known postal addresses and certify against these. QuaityStage includes the capacity to work with these data files.

They look like the genuine routines - the only difference is that one hangs on to the lock (via WriteU) while the other releases it (Write). No indication why this might create slowness - most users have found this to be an adequately fast mechanism. If you can load the initial value of the sequence...

If you're going to write this routine you could write it as a job control routine, and invoke the jobs directly. This might be a bother to maintain, however. Alternately use a job sequence with Job activities started in parallel but subject to the list of country codes containing the particular code...

Does the folder E:\TEMP exist? Do you (the DataStage executing user) have permission to write into it?