Search found 42189 matches
- Fri Jan 07, 2005 8:29 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Job set the own parameters
- Replies: 8
- Views: 3835
What wnogalski is suggesting is you take your job control code and put it into a custom routine. Pass the value of the parameter that it looks up back out as the 'Ans'wer. Then, you can use it in the Sequencer job just before the Job Activity stage that needs it. Use a Routine Activity stage to run ...
- Fri Jan 07, 2005 7:55 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: DSExecute to connect to oracle and update table...
- Replies: 2
- Views: 1627
I would agree. DataStage tends to screw with your quotes when you are trying to do something like you are doing. Best solution is what Ken posted, build a shell script to do all of the dirty work and then use DSExecute to call the script, passing in parameters. The other thing to realize is that you...
- Thu Jan 06, 2005 8:09 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: How to run multiple instances of sequencer using dsjob
- Replies: 4
- Views: 3902
This is hacked from a longish post over in the Server forum:
Edit: (waves at Vincent)
Mike wrote:The easiest way to have a child job inherent the same invocation id as the parent sequence job is to us the macro DSJobInvocationID in the expression for the child job's invocation id.
Edit: (waves at Vincent)
- Thu Jan 06, 2005 6:15 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: reusability concepts
- Replies: 9
- Views: 3187
I agree... you are defeating the whole purpose of using an ETL tool if you push the processing off to stored procedures. Now, I've seen times when that was the only option, like two-phased commits or other situations that DataStage doesn't handle. Other than that, I personally see no reason to have ...
- Thu Jan 06, 2005 3:22 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Return Values from Routine Activity
- Replies: 2
- Views: 1289
Sounds like you are using the new feature to 'automatically handle jobs that fail'. Routines that return a non-zero value are considered to have failed when that option is turned on. Two things to try: 1) turn off the option 2) Add an 'otherwise' trigger so that it thinks you are handling the error ...
- Thu Jan 06, 2005 10:32 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Set Commit After Set Number of Rows
- Replies: 4
- Views: 1457
I don't have access to a 7.5 server right now, so can't check the DRS stage right now. Be careful of the Transaction Size on the General tab, it is mostly there for backwards compatibility with older releases - at least that's the case with the OCI stages. If there is a specific Transaction Handling...
- Thu Jan 06, 2005 10:08 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Set Commit After Set Number of Rows
- Replies: 4
- Views: 1457
- Thu Jan 06, 2005 8:44 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Parameters not passed to an ExecuteCommand Stage
- Replies: 5
- Views: 1650
The 'GUI' solution is to write a routine that uses DSExecute to launch the script. You can then use the Routine Activity stage rather than the Execute Command stage, which will take parameters. I think this may be fixed in 7.5 but would have to check the readme. Sorry, just noticed that this is basi...
- Thu Jan 06, 2005 8:38 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Pulling the most recent file out of a directory
- Replies: 10
- Views: 5074
However, if you look at the original post you'll see they are (hopefully) on a Windows server. So, a Windows solution would be something similar with 'dir': dir /b /od This gets you a 'bare' listing (just filenames) sort in date order ascending. I'm not aware of any way to reverse the listing, so yo...
- Wed Jan 05, 2005 9:08 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Inserting Oracle Date and Time data
- Replies: 3
- Views: 1468
Exactly! Set the data type to Date or Timestamp and the Oracle stages will automatically use the appropriate TO_DATE function. That's why it's important to make sure the fields are properly formatted before they hit the output stages. BTW, as noted, only two digits for the seconds are allowed in an ...
- Wed Jan 05, 2005 7:39 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Clearing log file from Unix
- Replies: 3
- Views: 1399
- Wed Jan 05, 2005 7:36 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Execution of Shell Scripts in DataStage jobs
- Replies: 2
- Views: 1442
- Wed Jan 05, 2005 7:30 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: What is the difference between log and status files?
- Replies: 1
- Views: 534
Well, not knowing the gory details of the substructure, or what you consider to be 'the obvious', this will be the Reader's Digest Condensed version. The Status 'file' basically holds exactly that - the current status information for the job. Running, Aborted, Ran Ok... possibly even if the job is o...
- Tue Jan 04, 2005 12:55 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Job Aborts After 50 Errors Logged
- Replies: 5
- Views: 2181
If it was really set to 'No Limit', it wouldn't abort after 50 warnings. The question is - How are you running the job? By hand from Director, you get a chance to set the warning threshold. If you are running it from job control or a Sequencer job, then it will inherit the setting from the controlli...
- Mon Jan 03, 2005 12:06 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: truncate table
- Replies: 2
- Views: 807