Search found 35 matches

by nigel
Thu May 16, 2002 7:56 am
Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
Topic: Job missing in Director
Replies: 3
Views: 1685

Hi

It looks like some sort of corruption.Try this:Log all users out and do a project cleanup in Administrator. You must be logged in a a super user (root or NT Administrator) to do this.

Best of Luck

Nigel
by nigel
Wed May 08, 2002 8:14 am
Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
Topic: Calling a subroutine
Replies: 1
Views: 708

Hi Nancy If suppose you want to call the subroutine from the job control section of designer. If that is the case, then here is your solution. If your routine is call "MyRoutine" for example which has one argument "InputArg" ie. MyRoutine(InputArg), then you need to produce the f...
by nigel
Wed May 08, 2002 1:12 am
Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
Topic: DataStage job log and control job inconsistancies
Replies: 2
Views: 1618

Thanks for the update. We are also using Ds on Solaris. I will implement the NOTIFY change and see what happens. I found another archive entry on this site regarding the same problem. It is as follows: Use an active wait techinque in job control to replace the DSWaitForJob routine. The controlling j...
by nigel
Tue May 07, 2002 3:00 am
Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
Topic: Removing all log files
Replies: 2
Views: 1867

I suppose you require clearing all the logs instead of deleting them. If so you can write a routine to select all the jobs from the DS_JOBS datastage system hash file. You can then obtain the job numbers for each log by looping through each entry. Once in the loop, you could issue a retrieve command...
by nigel
Tue May 07, 2002 2:53 am
Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
Topic: DataStage job log and control job inconsistancies
Replies: 2
Views: 1618

DataStage job log and control job inconsistancies

Hi All I'm using DS 4.0xx. I am experiencing errors where a control/batch job "hangs" because it has not received a completion response from a child /controlled job. The child job completes normally but the control job still hangs. Sometimes the child job hangs, but the log entries indicat...