DSXchange

Welcome aboard. The default value is whatever you set it to. There is no default default except in very specific circumstances such as when the field is null and you try to load it into a non-nullable field. You can construct your own test to learn what values are used in these cases.

Active stages are those whose active/passive property is "active", passive stages are those whose active/passive property is "passive".

When's the interview?

Welcome aboard.

AIX on hardware suitable for Windows may struggle - it's designed for (what I'm guessing are) larger systems than the typical Windows box. Why not consider Linux?

abhilashnair wrote:will iconv() oconv() work in this case ?

These functions belong in server jobs or BASIC Transformer stage. They are extremely clever at handling date formats, but are not available in the parallel Transformer stage.

JobStatus is a DataStage macro, and therefore a reserved word. The macro will be expanded when you compile the expression, almost certainly causing syntax errors. Choose a different name.

Can you cite this reference? Have you challenged IBM with it? I can certainly see how it can be done with a user-defined STAGE variable, but not with a User Variables activity. Unless, of course, the User Variables activity invoked a function such as the one I supplied, or one of the key management ...

Based on ur description ... you can handle this in unix itself ... file_name=filenanme_ddmmyyyy date=passed_date grep $date $file_name rc=? if $rc = 0 rundsjob OR exit 0 and run the ds job separately from scheduling tool else print " wt ever " exit 1 Additionally you can use cut command t...

Use this routine inside the loop rather than a user variables activity. FUNCTION GetCounter(aValue) * Argument is ignored but must be supplied. * Returns 1 the first time invoked, 2 the second time, and so on. COMMON /GetCounter/TheCounter Ans = TheCounter + 1 TheCounter = Ans RETURN(Ans)

No, there's no bug, it's doing precisely what you ask. Look at it in BASIC code: y can only ever be x + 1, and x is unchanging.
Now answer my question about it being a counted loop or not.

Not if you need the job to abort.

If you don't need the job to abort, but only to process rows for which the date matches, then go with the single output link.

None of which addresses the question of using more than one parameter reference in the SQL statement.

Constrain the output from the Transformer stage such that the incoming date field is equal to the parameter value. Create an extra output from the Transformer stage. Mark this as Otherwise/Log and set a row limit on it of 1. The first mismatch will cause your job to abort. I really don't like writin...

Suddenly we're in a Transformer stage. So you intend to check the file name for every row you process? Where is the source of this "incoming date field"? Why do you want to abort the job?

No, this is only available in sequences.

However you could script dsjob -jobinfo to determine the job's status then dsjob -run -mode RESET if necessary then dsjob -run -mode NORMAL to actually run the job. (Option -mode NORMAL can be omitted.)

You need the -jobstatus option, which causes the exit status of dsjob to be the exit status of the job itself (1 = OK, 2 = Warnings, 3 = aborted and so on). Use -jobstatus instead of -wait option.