DSXchange

You can do more. You can challenge. One of the biggest DataStage sales in the Asia region was made because the pre-sales engineer (not I, btw) had the guts to stand up and tell them their model was wrong (and why, and how it should be) rather than just kowtowing to this very important company. Find ...

There is no common key on which a lookup can be based. Please describe the algorithm you would use to generate the output if DataStage were not available.

Is this repeatable, or did it happen only once? How heavily loaded was your server at the time? What is the value of the APT_ORCHHOME environment variable, and does this point to PXEngine?

It should be picked up from your Windows regional settings.

DataStage is not a scheduler.

It happens to contain a GUI so that you can use cron or at but it is not a scheduler.

Sounds like a huge waste of money if that's all they're using DataStage to do.

The diagnostic method is to read all the information supplied in the error message.

A job sequence is nothing more than a GUI for writing job control.

That's why the prohibition is stupid.

Simply redirect output into your file using the ">" redirection operator.

Note, however, that SQL can not be executed from UNIX, no matter how much you may want to do so, because UNIX is not a database environment. You need some kind of wrapper, such as exemplified in earlier posts.

A routine can not set a job parameter unless that same routine runs the job. You can use the routine to calculate the job parameter value, and use the return value from the routine to set the parameter value in a downstream Job activity.

I would also like to know how you can pass dynamic parameters to a macro in DataStage. Can someone else fill in the blanks? DataStage macros are defined in JOBCONTROL.H, which is to be found in the DSINCLUDE directory. If you inspect how they are defined, it will become clear that there is no capac...

jharvat wrote: I would also like to know how you can pass dynamic parameters to a macro in DataStage. Can someone else fill in the blanks?

See separate thread in server forum.

Thanks for posting the solution. I use a very similar configuration, but have never seen this problem.

Alas, no. It's purely data-driven, so only generates DDL to create tables, primary key and foreign key constraints. I may have to review my assertion about large objects, however - next time I'm playing with ProfileStage and encounter data that include any. I suspect it reportes them as Long VarChar...

Use whatever utility you are using to invoke the job. If a job sequence, pick up the file name from the job sequence; if the dsjob command pick up the file name (parameter value) from a -param option on the command line.

Try 009. If you read the documentation more completely, you will find that a three digit decimal number is treated as an ASCII code. You can also specify Unicode as a hexadecimal number.