Hello,

i have written a python script to execute multiple jobs one after another with a user defined UMAT and changing user materials. Very few jobs tend to bring the analysis or rather the UMAT in an endless loop (or anything), so that it get stuck. Right now i'm trying to find the "error" in the UMAT, but i want to keep the script running to get the results from the other jobs. 

I tested and know that a job doesn't take longer than 150 seconds. Here comes the waitForCompletion(150) in handy, because in theory it should kill the job after 150 seconds, but it doesn't do that. I tested this behavior for an analysis with my user defined UMAT and without it, but it never kills the job, even if i only gave him 5 seconds.

Script snippet:

analysisJob = mdb.Job(name=analysisJobName, model=myModel, userSubroutine=umatFilePath,    scratch=analysisJobWorkPath)
try:
    analysisJob.submit()
    analysisJob.waitForCompletion(150)
except AbaqusException, message:
    print "Job took longer than 150s", message

CMD run command:

abaqus cae script=pythonScript.py

So my question is, does somebody know how to get the timeOut argument working or what could may be my mistake?