DSXchange

It depends on whether good metadata management practices have been followed, and the linkages to the Repository have been preserved. If they have been broken (for example by modifying the table definition in the job design) then the answer is a simple no. Otherwise, the reference to the table defini...

Welcome aboard! :D You've posted this in the TX forum. Are you asking specifically about an FTP connector for DataStage TX, or more generally about the FTP stage used within DataStage? Search this forum and Ascential Developer Net for ideas about connecting using the FTP stage and using scripts (whi...

Yes, since there's no mechanism for installing it in the Template from which projects are created. Maybe there a need for an enhancement request here.
All plug-in stages installed via the Package Installer are installed directly in projects, not in the Template.

Presumably by "spaces" you mean "white space" (which includes tab characters) for non-NLS or characters designated as TRIMMABLE in the CTYPE locale category where NLS is enabled?

Check that the 32-bit Oracle library occurs ahead of the 64-bit library in LD_LIBRARY_PATH. Make sure that you export LD_LIBRARY_PATH, not LD_LIBRARY_HOME. Also make sure in dsenv that there's no space either side of the "=" character when setting values for environment variables. And what's the "#"...

Check that the 32-bit Oracle library occurs ahead of the 64-bit library in LD_LIBRARY_PATH. Make sure that you export LD_LIBRARY_PATH, not LD_LIBRARY_HOME. Also make sure in dsenv that there's no space either side of the "=" character when setting values for environment variables. And what's the "#"...

It would not be difficult to create a server job (with routines) that could capture all of the required information from an entire project and, indeed, email the results. Gathering information about the platform is more difficult but, again, not impossible. This could be distributed to anyone intere...

When you open a Job Activity it must request a (sorted) list of all jobs in the project with which to populate the drop-down list of job names. My guess, therefore, is that you have thousands of jobs in your project. If my guess is correct there is no cure unless you remove any jobs that you no long...

Search the forum for the UNLOCK command. This should provide information as to how to identify the recalcitrant lock and how to clear it.

Restarting DataStage necessarily clears all locks, since it re-builds the lock tables in memory.

There are two sections in DSParams; one for the environment variable definitions, the other for their values. The latter, from memory, is headed [EnvVarValues].

COUNTRY_ID=HR can never be right, unless HR is a column in the table.

COUNTRY_ID='HR' is needed if COUNTRY_ID has an SQL data type of CHAR or VARCHAR. Note the use of quotes around a string literal.

If you're going to hack a DSX file, make sure that you export including properties with default values (you set this on the Options tab).

If you use RCP there are columns "appearing from nowhere" as far as the Repository is concerned. That is, since the table definition on the output link was not loaded from the Repository, there is no link established in the first place, so no way for MetaStage to do its thing.

Yes, though you may need user-defined SQL if you need to constrain on dimensions, for example. Haven't done this with Sybase, but have done so with SQL Server.

Searching here, of course, and also the UniVerse 9.6 manuals on the IBM website.