DSXchange

In your Designer do a right mouse click on the repository window and turn on "Show stage types". Go to the Stage Types - Parallel - Processing folder. You should see BASIC Transformer second on the list. Drag and drop it into your Palette. Your palette is made up of short cuts to your stage types li...

I don't think parallel jobs can be exported to the Reporting Assistant. They certainly do not turn up on the "Jobs" tab when I run it. MetaStage is a better option and by the next release we will probably see the Reporting Assistant disappearing altogether to be replaced by better metadata reporting...

Yes there is an extra step! You need to define your XML path statements using the comments column of your XML output stage. Have a look at the XML Pack PDF as it has some examples of this. A good way to define this tab is to manually create the XML file that you want to achieve in notepad and import...

There is a FAQ now on how to set and use project specific environment variables. You can change them by modifying the DSParams file directly or by using the DataStage Administrator tool and finding the Environment Variables button. If you want an encrypted parameter your only option is to set it thr...

You're in luck, this is straight forward mult instance functionality. If you look at the job properties of your server job you will see a check box for "allow multiple instances" which lets you run multiple copies of a job by adding a suffix to the job name: jobname . instancename Eg. JobProcessServ...

Well I can take a stab in the dark, the line that reads: SQFS_data,0: Bad record delimiter after fixed-length record: expected "\n", got " " seems to indicate that you have too many space characters on your first line. Your column widths probably don't add up. FTP the file to the server and try to i...

QualityStage only partially uses the DataStage log mechanism. Most of the informative QualityStage log messages will be written to QualityStage directories such as the QS manager log file or the QS project log directory. While your job is running go to the QS project and look at the dates of the fil...

I'd forgotten about that, the sequence job passes run time settings through to the child job, so the warning limit is passed through. The number of rows to process is also passed through for called server jobs.

I found a message in the Orchestrate Operators Reference that did not make it into the DataStage documentation that suggests we should not use this stage: The diff operator has been superseded by the changecapture operator. While the diff operator has been retained for backwards compatibility, Ascen...

We are currently on DataStage 7.1 and want to go to 7.5. Ascential tell us this version is not certified for DB2 version 7 and we need to upgrade to DB2 version 8. Has anyone thrown caution to the win and run against DB2 version 7 despite the lack of certification?

Create a debug version of your job and use the Test button to try all combinations. Once it is working remove the debug statements: RoutineName = 'EkbeAsnQty' Deffun DSRMessage(A1, A2, A3) Calling "*DataStage*DSR_MESSAGE" Result = 0 Debug = "" Mange = 0 IF IsNull(Meng...

I have sent a simple difference stage example through to Ascential support to get the final word. I am calling the job from a Sequence job so I cannot get around the 50 warning limit.

When I use the Difference stage I get three warning messages in my log for each column being compared: Difference_1:When checking operator: Dropping component "fielda" because of prior component with same name Difference_1:When checking operator: Dropping component "fieldb" because of prior componen...

The first time I worked on a project that combined DataStage with QualityStage there was a lot of confusion over what tasks should be done in each product since they both have ETL and text transformation functionality. Since this is a problem of handling and validating free text it is reasonable to ...

Version 7.1 and beyond supports the creation of an encrypted project level environment variable that is set by the Administrator tool and can be added to a project as an encrypted environment job parameter and used in a database stage. I think it's time to add a new FAQ! You need to set the value of...