DSXchange

ray.wurlod

Because some of the Vn descriptions are embedded (for example row #3) this is a non-trivial task. Do you want to handle V8 as well as V-8 (and, if so, do you want to handle them differently)? This task is easier with a BASIC Transformer stage using a MatchField function. You could, of course, create...

ray.wurlod

You're going to have to do the detective work with your data. We can't see it. For example, you might have an int8 column (which can cope with numbers in the range -128 through +127 only), but your job tries to put a number outside this range into the column. That's one form of "numeric value out of...

ray.wurlod

It may also be possible that your data are not partitioned based upon the join key (in addition to any other potential cause). Check that also.

ray.wurlod

UVTEMP is a setting in the uvconfig configuration file. You can get its value using the analyze.shm command.

Code: Select all

$DSHOME/bin/analyze.shm -t | grep UVTEMP

ray.wurlod

And ALL of those fields except IsHoliday can be generated using DataStage functions - specifically Oconv(). You can even use a before-job subroutine to generate internal format dates in your desired range (job parameters) into a file, then process that file as your source of dates. Holidays, of cour...

ray.wurlod

roblew wrote:ha ha. very funny. I'm not the original poster... I used the search (like I'm supposed to), and just wanted to show my appreciation. :D

Yes, you did. Thank you. And well done for searching before asking - there are many answers floating around in DSXchange.

ray.wurlod

It's tricky calling C functions from server jobs.

However, you could write BASIC functions to effect the same functionality.

ray.wurlod

Or, slightly simpler:

Code: Select all

DateFromDaysSince(-1, StringToDate(DateToString(DSLink2.col1, "%yyyy-%mm") : '-01', "%yyyy-%mm-%dd"))

ray.wurlod

Are you telling us what actually happened, or what you think will happen? Your job sequence (note, not "sequencer") has no Exception Handler nor any Terminator activity, so why should a failure of Job2 affect Jobs 5, 7 and 8? Do you have "automatically handle activities that fail" checked? Read the ...

ray.wurlod

As noted, I didn't. 7.5.1A on Red Hat AS3.0 Linux.

ray.wurlod

0 (= all) rows/transaction. Can not be done via an environment variable.

ray.wurlod

Use a Custom trigger, perhaps one that handles a non-negative return as being satisfactory.

ray.wurlod

You CAN set to $PROJDEF. It's just that encrypted job parameters only echo "*" characters as they're being typed in.

ray.wurlod

The downstream jobs execute in different processes, so will not share the same environment. Therefore your putative method is doomed to failure.

ray.wurlod

I've never seen this behaviour. What default value do you give the job parameter that references this environment variable?

Search found 53125 matches