DSXchange

Yes, the first is the prototype for DB2 Wire Protocol connections. This is in .odbc.ini when the product is installed. The other entry was added at, and is specific to, your site. The entry in uvodbc.config simply makes the DSN visible and identifies it as "true" ODBC or "UniVerse&quo...

Depends who's offering the service.

If you have Metadata Workbench you can create a lineage report that will show you exactly this information. If you do not have Metadata Workbench you probably build a query against DS_JOBOBJECTS and DS_JOBS that finds input links (for writes) or output links (for reads) that refer to the particular ...

Note also that these cheat sites are apparently not particularly reliable.

Why would you expect data to be there on a fresh installation. You have to provide the data.

Is the error Data Not Found or No Data Found ? These are different.

What style of user registry are you using?

we have to convert a large number of Server jobs to be rewritten as Parallel job. Why? Server jobs still work, and are not going to go away (not least because sequences are server jobs). As noted, maybe only attempt the ones that are performing poorly. There are no tools. Analyse the logic of the s...

Where is PORT-SUB defined?

Import the table definition from the FD.
Load the imported table definition into the Complex Flat File stage.
You can specify whether you want the OCCURS handled by creating a vector within a single column or by creating ten separate columns (flattening).

I sometimes even hide the Sequential File stage in a local container when I'm appending to /dev/null (as well as keeping the annotation with it).

1) All your sequences are non-restartable.
or
2) There's a bug.

That's a possibility. You still need to be aware of the hashed file size limit (default 2GB with 32-bit addressing asserted).

Assuming you're on version 8.7 or later, the Operations Console keeps and displays history. The underlying database DSODB is completely described, so you can create your own reports from there.

I can only suggest that you try encrypting them with encrypt.bat, plugging the results into the config.ini file and testing whether that works.

When you import or save jobs in DataStage, they are automatically stored in the common metadata repository, so Metadata Workbench and other tools can see them immediately.

Annotate your job design to warn people against trying a View Data on the Sequential File stage that accesses /dev/null

Use a server job reading the output of the Filter command DIR /B pathname/TU* which will give you a stream of file names that you can pass to the Routine in a Transformer stage. Or use a sequence with an Execute Command activity to generate the list of file names, and a loop containing a Routine act...