DSXchange

Leave off the Oconv() function. DB2 stage wants internal format.

Type 2 isn't really that appropriate for timestamp. Try type 18, or perhaps Type 5. At 51 bytes per record, separation 1 is fine, but separation 2 or 4 may be more efficient because of matching the physical page size used in your hardware. Finally, try choosing a prime number as the modulo. The hfc....

The 6 in $TZ indicates UTC+6. The CDT part flags daylight saving (summer) time offset is in use.

You can readily map ECMP tp 5678 using a Convert() function, but you still need to be aware of whether or not daylight saving offset is in effect.

The best solution is to upgrade to version 8.5, where there's a totally re-architected XML Transformer stage (in the parallel canvas).

Otherwise track down a copy of XML Best Practices. (Search DSXchange to find one.)

The Job activities that run the subsequences need to have "reset if required, then run" option selected.

Take a look at the score - have all stages in the job been consolidated into one APT_CombinedOperatorController? If this is the case you may be able to disable combination selectively (on a per-stage basis) or globally (by including APT_DISABLE_COMBINATION environment variable as a job parameter set...

Have your DBA monitor the session to see whether it is hanging around in Oracle for a long time. As a test, have your DBA disconnect the session manually, to see how DataStage handles that.

Not unless you can shed some light on what process created the fifo lock in the first place.

At a guess it may have been a lost connection between your job and the job monitor application (JobMonApp), but you do not supply enough information to allow that guess to be any more than a guess.

Probably not. The first sequential operator will go to the first available node, the second to the second, and so on. At least that's how I understand the process from observation.

I don't think what you're trying to do (BETWEEN) is possible - when you use a Lookup stage DataStage pre-loads the entire reference data set into memory and performs "=" (or range) comparisons against that.

What kind of DB2 stage, and what write method are you using? A reject link from the Transformer stage is the way it's supposed to work.

I though you said these are environment variables. Where are the "$" characters?

Does the word "Reject" appear in the constraints area of that link within the Transformer stage?

Read the error message carefully - the problem reported there relates to the values being passed for user and password parts of the connection string.

I think this is new functionality in version 8.