DSXchange

How many environment variables do you have set?

Only if you can tell us what changed in the system. Clearly "nothing" is not the correct answer. You have some detective work to do.

Ceil() is for parallel jobs only.

Do you need this count before the job runs, or as a result from the DataStage job?

In the first case get the result of wc -l pathname and subtract 2.
In the second case get the last value of @INROWNUM and subtract 2. The Aggregator stage can give a Last value.

Good luck. There are many situations where server jobs are faster (finish sooner) than parallel jobs implementing the same logic. Parallel jobs will typically win if the volume of data to be processed is huge and can be processed truly in parallel (for example using Data Sets rather than Sequential ...

VLIST is a diagnostic tool for working with DataStage BASIC code. There is no way to "implement it in your scenario".

No, those ones would be replaced by something like "#@!&!"

Yes it can. A segmentation violation can occur for many causes, most of which your search would have revealed. If any of these causes occurs in future (for example an attempt to load 15 characters into a Char(12) field) then you will get a segmentation violation.

Yes, using a message handler.

chulett wrote:Hell, it takes me longer than that to come up with a new job's name.

Methinks you need simpler job naming standards.

Are these "image" fields binary? That may cause some issues. Also, what are the numbers? If these are COBOL-style level numbers, you have an ugly structure with which to deal, though DataStage can manage it.

You can not demote/suppress based on anything but message ID.

Therefore it looks like you are going to need to address the cause of the warnings; check for RI constraint violations before attempting to load data.

Have you tried?