DSXchange

Hi,
In our project we want to implment reject handling.
Suppose there are 100 records at source & only 95 records moved to target. How can I capture those 5 records? The reason behind rejection might be anything.
Along with that, can I generate reason message for each record?

if they are being rejected from a Transformer stage you can click on the 'constraints' button (top left) and set up a reject link

Thanks for answering, few more questions -
Does it capture whole source row or only some referrence?
Does it capable of giving the reason of rejection?

Even though you posted in "General" you marked it as a PX question. Reject links in PX come off the output stage and reflect the input data as well as SQL or other errors where applicable.

Yeah, from next time onwards I'll post questions in PX.

So does it mean, if I want to implement Error Handling (reject records) at each process (Extract, Transform & Load), it is not possible.
I can handle only during load?

Handling of rejects is possible at any point in time in DataStage. You need to know what type of rejects you are looking for - the first response was assuming you had output to a database or output link which failed, other type of rejects such as bad column values are usually handled within the job itself.

jtsoong wrote:if they are being rejected from a Transformer stage you can click on the 'constraints' button (top left) and set up a reject link

The constraints to a particular link will NOT result setting up a Reject Link to a Trasformer Stage.

You might come to say that clicking on the Otherwise/Log in the Constraint of the particular Link and keeping that link at last in the Link Order could catch the (rejected) records which failed to meet constraints on all the previous output links.

For your information:

The conversion of Stream Output Link to Reject Link in a Transformer Stage will happen only when applying "Convert to Reject" action on the Stream Output Link.

Author(yuva010),

Give some extra care when using Otherwise/Log option in the Transformer Stage. Better refer Parallel Job Defveloper's Guide page# 449.

yuva010 wrote:Thanks for answering, few more questions -
Does it capture whole source row or only some referrence?
Does it capable of giving the reason of rejection?

1. Reject from only Source(if it is in Transformer Stage)

2. No. Reason for rejection should be user-described.

In 'Px', except transformer stage which are the
other stages where we can use reject link?
Merge, Lookup etc..?

Many parallel stage types support a reject link. The descriptions of each in the manuals will tell you which they are.

1. what type os rejection it is?

is that due to the data comes in source

or

while performing the validation rule in your requirement.

If data you are getting in the source not matches with the job developed those general warnings and errors you can get it in the reject link.

whereas if your requirement expects '1' and 'A' is coming in that if you want to reject the record then you need pull out those records and store it.

you should store the rejected, it won't come automatically

Ohhh Yeah.... Thats' true...
But I am expecting such a rejection will also get captured automatically as long as I have mentioned correct data types for target.

Not at all. AGE might be an integer, but - for a person - you'd expect to reject negative values and "too large" values (over 120, say).

It is based on your requirement. can you narrate what is your requirement. so that it wil be useful for the boarders to write the correct answers / solutions to your queries.

It is based on your requirement. can you narrate what is your requirement. so that it wil be useful for the boarders to write the correct answers / solutions to your queries.