DSXchange

I just did. The entire job design is in the previous response.

I think Ken was referring to the ol' dynamic array as an argument trick. (Indeed, you can use any delimited string, but a field-mark delimited dynamic array gives you more flexible parsing options as well as the hint mechanism for extra speed.)

You have to lie in your DataStage job. You have to specify col1 and col2 as keys (search keys) for the purposes of the reference lookup. Only in this way will they be passed to the WHERE clause.

It's an environment variable, for goodness' sake! You can change it after dsenv has been executed, for example using an Execute Command activity in your job sequence. If you're really brave you could add to the LOGIN paragraph in the project - but be prepared to reinstate this after an upgrade, whic...

I am also getting the same error. The error reads as : ANSHMANP..Output_Number.DSLink5: DSD.SEQOpen Failed to open Number_Manipulation.txt in directory c:\output_data_ds STATUS = 2. I was able to read another file in the same directory for some other transformer job. I dont have any permission issu...

Anywhere you like, but typically in the Input Values field when using ExecSH as a before-job or before-stage subroutine.

If that's true then all records satisfy the constraint expression, which clearly would need refinement. Make sure that the reject-handling link is executed last.

Please post the warning message that is generated. Clearly if the SQL works from query analyzer and not from DataStage, either it's not exactly the same SQL from DataStage (you can verify using stage tracing or SQL tracing), or something unexpected is occurring with the data. Only by inspecting the ...

Welcome aboard. :D Import IS a manual proecss. During import you specify the file's pathname manually, and then its format (in your case the delimiter character, the quote character and whether the first line is column headings). You keep clicking on Preview until the display makes sense, then move ...

Using separate triggers to detect the abort of S3 (and any other job) will help - these can be directed to a Terminator, that can issue stop requests to any other running job, then to a Routine that invokes UtilityAbortToLog that logs a fatal message and aborts S0.

There are some views that you can use for reporting from MetaStage. The database itself is quite (impossibly, some say) complex in its inter-relationships, so reporting from it directly is discouraged.

Only in parallel jobs, as far as I am aware, where there is an SAS Dataset stage.

Please post the message that leads you to your assertion that "it was not accepting". Ereplace is an intrinsic function - it must be accepted by the Expression Editor. Perhaps someone has edited your DSParams file, but let's not leap to conclusions without your next post. The best solution is to hav...

If you're working with 7.5 you can use an expression directly in the job parameter value allocation.

would do it. Or you could use the DS Transform

Not a runnable job can mean not compiled, but it can also mean a status of aborted, stopped, validation failed, crashed.

You need to check every job status in the control hierarchy.