Set Project to Compile before execute

PhilHibbs · Post by **PhilHibbs** » Mon Feb 23, 2009 9:54 am

sometimes the job fails it seems i have to recompile the job in order to rerun it

No, you don't. You need to Reset the job, not recompile it.

I have found at least two instances where a job had to be re-compiled because the reset mechanism didn't work. One of them was a few years ago, and I think the problem was something to do with a hashed file having been deleted so it couldn't do one of the reset operations. The other was today, we had to abort an EDA extract job (we use the IBI EDA plug-in stage), and resetting the job didn't work, we had to re-compile it in order to get it to run again.

chulett · Post by **chulett** » Mon Feb 23, 2009 10:59 am

Perhaps something specific to that plug-in, I don't recall ever having a time where a reset didn't work and I had to fall back on a recompile. For whatever that is worth.

aasaif · Post by **aasaif** » Mon Feb 23, 2009 2:17 pm

does anyone see the issue with this

Job1 = DSAttachJob("AuxTimeFactLoad", DSJ.ERRORNONE)
Job1=DSPrepareJob(Job1)

Error
Invalid job handle 0

chulett · Post by **chulett** » Mon Feb 23, 2009 2:18 pm

Which statement generated the error? I'd hazard a guess that your attach failed.

aasaif · Post by **aasaif** » Mon Feb 23, 2009 2:46 pm

correct

chulett · Post by **chulett** » Mon Feb 23, 2009 2:56 pm

Then your job name doesn't exist.

aasaif · Post by **aasaif** » Mon Feb 23, 2009 3:45 pm

i apologize its happening on the second line

chulett · Post by **chulett** » Mon Feb 23, 2009 4:52 pm

You need to put a little effort into figuring this out. Add some calls to DSLogInfo() after each step. The second step will fail if the first is not successful and you need to check to see that the handle returned is valid before proceeding to the next step. Don't write code that lives in fantasy land and assumes that everything works every time. Add some error handling steps in there, log enough information to help you figure out what in the heck is happening.

ray.wurlod · Post by **ray.wurlod** » Mon Feb 23, 2009 9:09 pm

I typically use a "harmless" function (get job name) right after the call to DSAttachJob() function. This is a quick way to test whether the attach succeeded; if it didn't the harmless function returns DSJE.BADHANDLE.

Code: Select all

Job1 = DSAttachJob("AuxTimeFactLoad", DSJ.ERRORNONE) 
TheJobName = DSGetJobInfo(Job1, DSJ.JOBNAME)
If TheJobName = DSJE.BADHANDLE
Then
   Msg = "Unable to attach job AuxTimeFactLoad"
   Call DSLogWarn(Msg, "Control")
End
Else
   Job1=DSPrepareJob(Job1) 
   ...
End

chulett · Post by **chulett** » Mon Feb 23, 2009 10:25 pm

Interesting. I've basically adopted the same code that the 'Add Job' button or a Sequence job will generate for a Job Activity:

Code: Select all

hJob1 = DSAttachJob(<JobName>, DSJ.<errorlevel>)
If Not(hJob1) Then
  <Error handling here>
End Else
  hJob1 = DSPrepare(hJob1)
  <etc>
End

Rather than explicitly testing the validity of the handle, make sure the returned handle isn't zero. Figured if it was good enough for Ardent / Ascential / IBM / whomever...

ray.wurlod · Post by **ray.wurlod** » Tue Feb 24, 2009 6:07 am

It wasn't good enough. Their manuals explicitly stated that you should never make any assumption about the data type of the job handle variable - you should treat it as opaque. Then they go and break their own rules.

When IBM do change it's data type from integer row number in internal table of job handles to a true pointer, then you'll ALL be ruined!!!!
Ah hahahahahahaha!!!!!

chulett · Post by **chulett** » Tue Feb 24, 2009 6:26 am

Yup, I know just what little bit of advice you are referring to and also thought it was amusing that they didn't really seem to follow it.

[wanders off, waiting to rue the day, still hearing that maniacal laughter ringing in his ears]

aasaif · Post by **aasaif** » Tue Feb 24, 2009 1:13 pm

I tried something like this and the job wouldnt run:
and the job would just freeze

hJob1 = DSAttachJob("AuxTime".DSJ.ERRFATAL)
If NOT(hJob1) Then
Call DSLogFatal("Job Failed: AuxTime","Job")
Abort
End
ErrCode = DSRunJob(JJob1, DSJ.RUNNORMAL)
Status = DSGetJobInfo(hJob1, DSJ.JOBSTATUS)

chulett · Post by **chulett** » Tue Feb 24, 2009 1:31 pm

Something like this or this exactly? You need a comma between the job name and DSJ.ERRFATAL, not a dot. And you've got "JJob1" in the DSRunJob call rather than "hJob1". Details are important, you know.

aasaif · Post by **aasaif** » Wed Feb 25, 2009 8:25 am

sorry i posted my original before i fixed it

this is what i put in the job control and the project just started but wouldnt run

hJob1 = DSAttachJob("AuxTime",DSJ.ERRFATAL)
If NOT(hJob1) Then
Call DSLogFatal("Job Failed: AuxTime","Job")
Abort
End
ErrCode = DSRunJob(hJob1, DSJ.RUNNORMAL)
Status = DSGetJobInfo(hJob1, DSJ.JOBSTATUS)