Search found 4605 matches

by kduke
Tue Sep 13, 2005 6:31 pm
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Checking the jobs in runnable state
Replies: 10
Views: 3685

You can modify that script to reset and run any job. Ray is correct in saying to reset every job in a category is not worth it. We do not mind helping you but try to be specific. Do not change your requirements in mid stream. We are doing this for fun. We do not get paid to answer these questions or...
by kduke
Tue Sep 13, 2005 7:29 am
Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
Topic: Reading Parameters From Database directly
Replies: 14
Views: 11795

We have done this a lot. It is usually dumped to a hash file with the parameter name as the key then it is easily read in job control or a routine. You could ask the job what parameters it has and then automatically look them up.
by kduke
Tue Sep 13, 2005 7:25 am
Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
Topic: Expression Evaluation
Replies: 17
Views: 4962

ITYPE brilliant answer. Does EVAL work in BASIC? Got to try it.
by kduke
Tue Sep 13, 2005 5:49 am
Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
Topic: How to build Time dimension table
Replies: 11
Views: 5529

I think you need to clear and then insert.
by kduke
Tue Sep 13, 2005 5:48 am
Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
Topic: Jobs Not Visible In Dev Server
Replies: 10
Views: 2427

Well, Ray not all the profiles are correct.
by kduke
Tue Sep 13, 2005 5:45 am
Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
Topic: ETL Testing
Replies: 2
Views: 1405

Can you spell test 7 different ways? :)
by kduke
Mon Sep 12, 2005 11:00 pm
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Job Activity In Sequencer
Replies: 3
Views: 1059

Ask IBM, there is a patch for this.
by kduke
Mon Sep 12, 2005 8:53 pm
Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
Topic: How to find a huge job log
Replies: 14
Views: 4639

If you are in Windows then good luck but UNIX:

Code: Select all

#!/bin/ksh
# 500mb
find . -size +500000000c -exec ls -l {} \;
by kduke
Mon Sep 12, 2005 8:51 pm
Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
Topic: Any new setting needed for running a job from Unix script
Replies: 3
Views: 1602

Next time before you install a new DataStage beckup critical files with: #!/bin/ksh set -x cd mkdir $HOME/SavedFiles cp .profile SavedFiles DSHOME=`cat /.dshome` cd $DSHOME sudo cp .[a-z]* $HOME/SavedFiles cp dsenv* $HOME/SavedFiles cp uvodbc* $HOME/SavedFiles cp uvconfig* $HOME/SavedFiles cd ../Pro...
by kduke
Mon Sep 12, 2005 8:38 pm
Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
Topic: Accessing .xls or .mdb files in a Unix directory
Replies: 18
Views: 7736

You can easily export and import csv files from either.
by kduke
Mon Sep 12, 2005 8:37 pm
Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
Topic: Jobs Not Visible In Dev Server
Replies: 10
Views: 2427

If you are on 7.5.1 and XP then you need to download the XP patch from Ascential.
by kduke
Mon Sep 12, 2005 8:35 pm
Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
Topic: How to build Time dimension table
Replies: 11
Views: 5529

This code overwrites the text file every time you run it. Should not be a problem.
by kduke
Mon Sep 12, 2005 8:33 pm
Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
Topic: How to get Job start and end time
Replies: 5
Views: 2432

Download EtlStats from my tips page.

Should have a Windows version soon. Got everything but email working. Changed everything to ODBC. Should be lots easier to install.
by kduke
Mon Sep 12, 2005 8:28 pm
Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
Topic: Any new setting needed for running a job from Unix script
Replies: 3
Views: 1602

Code: Select all

   
DSHOME=`cat /.dshome`
export DSHOME
LD_LIBRARY_PATH=$DSHOME/java/jre/lib/sparc/client:$DSHOME/java/jre/lib/sparc:`dirname $DSHOME`/branded_odbc/lib:$DSHOME/lib:$DSHOME/uvdlls:$LD_LIBRARY_PATH
export LD_LIBRARY_PATH


You should have these lines.