DSXchange

I don't see any junk.

Do you mean line terminators?
These are converted to field marks (@FM) when the file is loaded into a string, so that there's a consistent interface whether the operating system is UNIX (single-character line terminators) or Windows (dual-character line terminators).

Writing a sequential file necessarily can only use one node.

How many nodes are mentioned in your configuration file (whose pathname is set by APT_CONFIG_FILE environment variable)?

Also, have you rolled in all the fixes for DataStage? There were - if my memory serves - one or two issues with updating remote XMETA databases. Or was it non-DB2 XMETA databases? Anyway, check whether the cumulative fixes have been rolled in.

Have you checked that the executing user ID has sufficient permission to /home/p139pkg/odbc/source/lib/pgr7_mt_lt.so including "x" to the shared object itself?

Look CAREFULLY at the error message.

WHAT is not found? Gosh, it's a shared library (".so" suffix)!

Could it be, one wonders, that your shared library search path (probably the one set in dsenv) does not include the parent directory of libvmdsapi.so ?

The error message suggests that the tnsnames.ora file was found successfully, but the configuration therein for the given TNS name was incorrect. It is that that I would be checking.

The Engine Resource Service IS working properly. However, it has nothing to do with locks (unless it is not running, since one of its roles is to prevent Windows from "cleaning up" the lock tables from shared memory). Restarting the service involves stopping it, which clears the shared memory contai...

Do you have a firewall somewhere blocking port #31538 ?

Any activity (except a Sequencer) has a "do not checkpoint run" checkbox. If this is selected that activity is always executed, even if checkpoints are enabled.

Sequencers don't have routine activities. Job sequences do.

Indeed, sequencers only have one property, "Any" or "All".

You can NOT convert it into a DataStage job until you understand the logic of what the SQL is doing! And no-one here is going to profit from doing that analysis, which is why I am insisting that you do it. Converting the SQL into a DataStage job will make no difference whatsoever to how "reporting p...

Your design is good (provided the job activity name is correctly spelled and cased when used in the job parameter expression). What value are you getting? (Look in the log for the parameter value.)

[urlhttp://www.pickwiki.com/cgi-bin/wiki.pl?Date_Conversion_Demystified]This article[/url] will aid your understanding of using the Oconv() and Iconv() functions with dates.

Wolfgang, the USA can be a pretty sheltered, packaged, environment sometimes!

Depending on where the command output came from you may need to trim field marks (@FM) from it before applying the Iconv() function. Otherwise you are on the right track.