DSXchange

There is no certification exam for Ascential DataStage.

Welcome aboard! :D There is no training material in the public domain (though you can learn a lot from this site!). Ascential does offer web-based as well as instructor-led and site-based training, details of which can be obtained from them (or their web site). There is no demonstration version of D...

In parallel jobs there are two, very different, stage types. One is called the Transfomer stage, the other is called the BASIC Transformer stage. Parallel jobs do not use the DataStage BASIC run machine; instead they use a C-based environment that is/was called osh (from "Orchestrate shell", Orchest...

Arun, As you will see in the code, it is intended to determine whether the DSAttachJob function was called successfully. Therefore the code is inserted around the DSAttachJob function that is invoked to get a job handle used to run the job. If you're using multi-instance jobs and using an invocation...

And, if you've used job parameters for table names, this can be quite a messy query! The table name is a property of the passive stage's input or output link. So, given a job name, you need to determine a list of that job's stage names (from DSStages Where JobName = 'name'). Then you need to determi...

Make the hashed file with three key columns (Key, Level, Code). Perform two (separate) lookups. The first uses inlink.Key 1 inlink.Account_Level1 as the three reference key expressions. The second uses inlink.Key 2 inlink.Account_Level2 as the three reference key expressions. One of them should succ...

Answering only the second question, you get two "from previous run" messages because there were (at least) two active stage types that had aborted without writing their information into the job log. Or one from the job, and one from the Transfomer stage KDW1RDOSInvoiceShipHeaderS002. That there's an...

Any reason you can't use an FTP stage? One of the capabilities in UniVerse that is not in DataStage is the set of functions collectively known as CallHTTP. That is, DataStage does not have the capability natively. I hope someone can help you with an operating system script. If it's a well-formed scr...

The Transformer stage in parallel jobs can NOT access BASIC functions, etc. It uses a completely different expression editor, with a largely equivalent list of operators, and a different, though overlapping, list of functions and other operands (but they're not BASIC functions and operators). The BA...

Can you show us what you're trying to do? It's certainly possible to pass an array to a function. Do you mean a dynamic array - which is only a character string, so ought not to present any problem? Or do you mean a dimensioned array, in which case there are some rules you must heed. Read about the ...

I suspect you are confusing a Transform (which is a discrete DataStage object, an encapsulated, pre-stored expression, stored in the Transforms branch of the Repository) with a Transformer stage (which is not a discrete DataStage object but, instead, must exist within a DataStage job). I have just c...

Welcome aboard! :D You can't reset the job itself from within an after-job subroutine because, while the after-job subroutine is executing, the status of the job is still "running". The job does not stop running until after the after-job subroutine returns. You can not reset a job if its status is "...

But you can not automate this within the job itself, unless by a reverse of the procedure I outlined earlier. Change the name of (or copy) the file to a generic name with ExecSH called as a before-job subroutine. Then have DataStage process from the generic file name. Perhaps remove or rename the pr...

The preceding post was based on the assumption that you're reading from the file. If you're writing to the file there is another way. Write to a generic file (say, blacklist.txt) then use an after-job subroutine to change its name. This has been discussed a number of times on this Forum; do a search...

It is not possible to do it within the job. Filenames, whether or not they contain resolved parameter values, are determined when the job starts; they can not be changed subsequently. You must calculate values for job parameters before the job is started. This is a fundamental rule for DataStage jobs.