DSXchange

Not really, unless you can show us how the v_... variables and the ReportText variable get their values. DSLogWarn requires two arguments. There's no value trying to close a file if you failed to open it. The variable "t.fvar" is what's called a "file variable" or "file handle" - effectively a point...

It's used internally in DataStage to identify distinct runs of a job (for example the reset run from the prior aborted run). It provides only uniqueness. You get no information from it.

You need to:

spell DSGetParamInfo correctly

put quotes around the name of the parameter (or assign its name to a variable)

Welcome aboard. :D The message is "unable to open hashed file LOG_PRE_DAILY_BAL_DUP_HASH4". Can you prove to us (with an ls -l listing, for example) that this hashed file exists and that you have appropriate permission to open it? Can you also confirm how the Hashed File stage refers to it - in the ...

That's an American billion. An English billion is a million million (from "bi"- and "million") and thus has thirteen digits: 1,000,000,000,000.

Knowledge of data is required here. I read between the lines of the original specification. Technically you also need to take into account AD/BC and dates beyond 9999-12-31 (to avoid introducing Y10K problems). Are you rigorous in this also?

The message is "login failed". This means that connection was made to SQL Server, but your authentication information (user ID and password) were not valid. I don't see any mention of a password in the connection string.

Does this occur reliably or occasionally? Is there a pattern - for example does it occur for some values of job number in RT_LOGnnnn and not for other values?

Why are you using UNNEST (normalizing on FULL.TEXT)? I don't think it's necessary for selecting.

There's no simpler way given that you've chosen to use a routine rather than the Job Activity to run the job.

Period:


Year:

Double click on the event in the DataStage Director log view.

Do you have one column or more than one column making up the primary key?

What I said before stands; a hashed file will not accept null as a primary key value. If all of the key columns are null, the record will be rejected.

Doesn't Search work for you?

Paste it in as user-defined SQL and make sure that the Columns grid contains the appropriate (accurate data type) columns to receive all the columns generated in the query result set.

Why not just