DSXchange

It is better to get it straight from the horse's mouth, see IBM/Ascential pages on this topic to get accurate information.

One of the switches in the Oracle stage lets you enable the reject link, look for it towards the bottom of the list.

The "reject" link in PX needs to come out of the Oracle Enterprise Stage, not the transformer (as it would be done in server jobs).

Since the USS environment is running on a mainframe it benefits from the architecture of that platform. It is like asking why DS will run faster on a multi-CPU Sun/HP/IBM platform than on my home PC.
And the USS version of DataStage runs EE.

dsguy - this site is staffed by unpaid volunteers, the premium memberships help defray the costs of running this site. Since posters have a choice of which questions to respond to, you have the best chances of receiving help if your post details exactly what your problem is and what you've tried to ...

You will need to talk to your DBA in order to make this decision, if you have no business rules for this. The less commits you make, the faster a load can be, but the more the rollback segments fill up. If they reach their limit you will have errors. If you commit too often when you don't have to yo...

Kamal - can you compile this job that has a transform stage?

If you use the default settings in the sequential file read, the job will fail at the first bad record. Craig - I just tested it to make sure; the warning limit doesn't apply since the first row read with incorrect column counts causes and errors with something like "row 3, column two, required colu...

Try to compile the job and post the compile error (if any), that will show whether or not you have the correct compiler installed and configured.

It aborts as soon as it hits the error, be it the 1st or the n-millionth.

No, you cannot parameterize the Job Name in a Job Activity stage. But if you look at the code that is generated (look at the Job Control tab) you will see that it is a relatively short series of calls; so you can create your DataStage routine which will take the job name and the list of parameters a...

By default the job will stop at the 51st record with an error, since all of the sequential line's data will go into the first column and the second column will trigger an error. You can change this behaviour, if you wish to do so, by setting the missing column attributes.

Which stage are you doing this in? In some you cannot modify this property.

...when i am trying to get a parameter of type encrypted from the atached job even though the value is encrypted i could see th value clearly... You cannot see the value of an encrypted parameter in cleartext. What you may be doing is looking at a value in a sequence that you then pass as an encryp...

DataStage internally has no effective limit for the length of strings (as long as it can malloc() the space) so I don't think that a run will fail due to this. The message "pane" is a client side only object.