DSXchange

Commit immedately (transaction size = 1) and keep your transaction isolation level to the minimum possible setting. Otherwise write all the updates to a staging area, and run another job to effect all the updates in a single run.

StringToDecimal() conversions?

Even so, your tsort operators will still be constrained by any limit set explicitly in the Sort stage or by APT_TSORT_STRESS_BLOCKSIZE environment variable. You will probably need to increase one of these also.

Wait For File activity in job sequence.

Given your requirement that the job can not start until and unless the file is present means that some external agency (such as a job sequence) must be used to "kick off" the job.

You can use other techniques, too, such as third party schedulers.

Looks to me like DataStage is still attempting to use rsh. ##I IIS-DSEE-TFPM-00185 22:15:12(016) <main_program> lcetldbd1 - ##I IIS-DSEE-TFPM-00187 22:15:12(017) <main_program> rsh issued, no response received ##E IIS-DSEE-TFPM-00247 22:15:12(018) <main_program> Unable to contact one or more Section...

"They", whoever they are, are wrong. The requirement to have the MQ Series server co-resident with the DataStage server no longer applies. This is one of the features of the new version. You only need an MQ Series client, if that's the way you want to do things. The MQ Series client is con...

Do you understand how COMMON storage works? In particular are you aware that it persists for the duration of one process? Examine the Key Management routines for opening a hashed file into a variable in COMMON, so that it need be opened only once, rather than once per row. If follows, therefore, tha...

ssh and rsh are different mechanisms. Also can you be sure that it's the same user? (Tip: put ExecSH into a job as a before-job subroutine and execute the id command - you may be surprised.)

This is an all-volunteer site - people post as and when they can. Asking for accelerated response is moot. What is the data type of the incoming signed numeric data? The signs should produce no difficulty for loading into a database table. If you do have an error generated, post the actual error mes...

It's an unusual approach, but it's not wrong per se provided you create an updatable view - which implies that there are already extant tables (on which the view is based) that can actually store the data you push into the view.

devanars wrote:our server is unix and client(designer) is on windows. we need to apply a patch to datastage designer but not to the server. you have given the syntax for the server i believe.

Clearly this is not the case, because a Windows pathname to installer.jar was given.

Did the CREATE VIEW statement complete successfully?

Usually a CREATE VIEW statement includes a SELECT clause.

Read the DB2 documentation about how to create updatable views.

Or just type dsjob -logsum and dsjob -logdetail alone, which throws an error message that includes syntax/usage information,

And doubtless the proponents of Perl will recommend that route.