DSXchange

The job design would look something like a long string of Transformer stages, each doing N lookups. For example, you might have 64 Transformer stages each doing 4 lookups. I think that would be a nice balance for 256 columns (your original specification). Each Transformer stage adds four new Char(1)...

You're welcome. My first week was in nineteen mumble mumble! There is a huge amount to learn in this product. It's really good but you have to learn what you can do (and where) and what you cannot do. Do take the Ascential training if you can. Otherwise, experiment! Especially in the Designer client...

How and where do you want to "recover" the file? What do you mean by this term? If what you are looking to do is read a file whose name contains a date, you need to generate the file name in a job parameter - perhaps in the calling sequence or job control code - before starting the job, then using t...

You can perform all the lookups in one job. The reference key expression is a constant in each case, for example "basic", "layer_number" and so on. You need a separate lookup for each input column - don't try to do them all in one Transfomer stage; you aren't allowed that many links in any case! For...

True, because in the WHERE clause you can only use valid SQL functions. ConvertMonth is a DataStage function, not an SQL function. Transforms, similarly, can not be used in place of SQL expressions in SQL statements. If your database has a "first of the month" and/or a "date diff" function, by all m...

... but you could not do that in a TRANSFORM, because Transforms do not have support for Job parameters.

The next goal, therefore, is to find the most efficient in-line expression possible. I believe that is more efficient than your construction.

So it is! Right at the very end. But who scrolls right through to the end of a help topic?

Thanks for tracking that down for us.

Yes. You open the job properties window and find "After Job Subroutine". Choose ExecDOS from the drop down list, and add the pathname of the BAT file in the Input Value window. Since you're on version 7.x, you can use the check box to require that the after-job subroutine is only executed if the job...

Welcome aboard! :D A couple of questions. I am assuming (from the TRANS function) that your lookup table is actually a hashed file. First is, can you post your code delimited by Code tags? (actually, I will do that here). File A:- basic layer_number r_lpg max ----------------------------------------...

This one's a DB2 configuration error, not a DataStage error. Check with your DB2 DBA, who will tell you why there isn't enough storage space in the heap in question.

The interesting thing to me is it only seems to handle 'logical' rejects. Actual 'physical' rejects, bounced back from a passive stage like OCI, don't seem to go down them. Does that sound like the correct behaviour to you? Is this little goodie actually documented anywhere? I couldn't find an ment...

I have none. I am not working with Japanese data at the moment. You might like to ask Ascential support - through your support provider, of course. It is always a problem to be certain about how Japanese data are encoded. It is rare that the data owner knows for sure. Take a look at the drop-down li...

Examine the code produced by any Transformer stage (in the RT_BPxx directory). This will answer your question. For each iteration of the main loop, REJECTED is initialized to @TRUE. If that row is processed on any output link, the value of REJECTED is changed to @FALSE. When processing a [Rejects] l...

The user status area isn't actually a variable; it's a field in the RT_CONFIGxxx table for the job. This is why the job's user status persists after the job has finished. So you're touching down to disk, and locking for update, for every row processed. I expect this is most of the explanation of the...

An after-job subroutine only executes once all rows have been processed by the job, and all files and connections to databases closed.