DSXchange

The three new columns get added by a transformer before you pivot them so they can pivot together. So you have four columns coming in and you add three more: Name: ABS CellNum: 123 WorkNum: 456 HomeNum: 789 CellDesc: "Cell" WorkDesc: "Work" HomeDesc: "Home" And then you...

Hey, you're the one that said you had a "single primary key (numeric) column in table". :wink: So these duplicates... do have the duplicates in the file itself, or is there just a single instance of the key value in the file which may or may not exist in the table? The answer changes how y...

I thought "always on" was an option when you deployed the job rather than something you are forced into... however it's been a long dang time since I've played with them. Anyway, why not have it always on? It can still be invoked "on demand" and you don't have to wait for the job...

Transformer.

That's a horizontal pivot. Only thing 'tricky' about it is you have to add three new columns with your hardcoded values ('cell', etc) so you can pivot the numbers in pairs.

devesh_ssingh wrote:my daily scheduled should repeat to pick all those file to finish my loading till end of day.

While you may find some people here familiar with Tivoli, you really would be better served posting this question in a Tivoli support forum if you really don't want to change the DataStage jobs.

That stage is strictly one-to-one, there's no facility to ouput multiple records. You'd need to split it in two first and send both to it, which could be as simple as Field() in a transformer with two output links followed by a Funnel.

Can you try what I posted in my second post, the UNIX command? That will let us know if you have the MKS Toolkit installed and if it works would greatly simplify things: wc -l D:\APP_DATA\VBS\PAS\CIA\REJECTS\SOURCE\ALISSourceRejects.csv Worth a shot before we burn any more braincells on a DOS soluti...

Was thinking about my answer and realized it was a little... terse. So for grins, here's the longer explanation: When a job starts, all target stages are opened / initialized. It is at that time that they do whatever they need to do to "get ready". A database stage connects to the database...

Can you not use the Start & End Loop stages in the Sequence job so it runs the load once for each file and only completes after all files are processed?

Hmmm... hard to say based on what was posted. For a "combo" action to work the first action must fail before the second option will fire. So the update must update zero records before the insert is attempted. It sounds like that happens and then you get an PK violation on the insert, yes? ...

You can't.

First let me get you into your own post and in the proper forum. No idea why you decided to jump on the end of this post but I've split yours out so you have control over the fate of the topic. Done!

Let me know if you're not on an 8.x release on a UNIX server.

Similar != same, off you go to your own post.

Exactly. Not sure what about that is difficult... tedious perhaps but not difficult.