Capture all rejecting rows from job

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
akrzy
Participant
Posts: 121
Joined: Wed Dec 08, 2004 4:46 am

Capture all rejecting rows from job

Post by akrzy »

Hi,

It's me again :)

I know that I can capture rejecting rows from every Trnasformer separately.

But I'd like to collect all rejecting rows into one files indepednently.

Do you know any Macro or function to do that?

Thanks,
Anka
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

Hello akrzy,

you can capture all the reject rows into a database file, since databases are designed to automatically control concurrent writes. You cannot write to a flat (sequential) file from several different process concurrently. So if in your job you point all the reject links to, say, a DataStage hashed file, and ensure that all generate a unique key then subsequently you can read that hashed file into a sequential file.
Sainath.Srinivasan
Participant
Posts: 3337
Joined: Mon Jan 17, 2005 4:49 am
Location: United Kingdom

Post by Sainath.Srinivasan »

You can write into multiple sequential files and then concatenate them together. You can store them in DataSets for better performance.
akrzy
Participant
Posts: 121
Joined: Wed Dec 08, 2004 4:46 am

Post by akrzy »

But there aren't hashed files in DS PX.
Sainath.Srinivasan
Participant
Posts: 3337
Joined: Mon Jan 17, 2005 4:49 am
Location: United Kingdom

Post by Sainath.Srinivasan »

But you can store them in table as he said.
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

akrzy,

there are no hash file stages in Px as you said. You can write to UniVerse hash files from PX through ODBC (or, to be correct, by using the "Dynamic RDBMS" stage). It boils down to two generic choices - writing to several sequential files [each with 1W&NR access] and subsequently merging them into one sequential or file set OR writing to a single database table of your choice by all links. If you have many rejects then write to parallel sequential files for performance, if you have only a few rejects write to a consolidated table for simplicity. The choice is yours.
Post Reply