I work with a set of code that verifies data and emails when something is wrong so these problems can be dealt with right away. It runs overnight as a phantom started by a linux cron job.
The often changing nature of this code means it can be more prone to bugs like a variable not assigned. That's fine, I can see the problems in the runtime-errors next day and fix.
My problem is this program quits when it runs into a runtime error but if I run the same code in the foreground it doesn't.
Is there a setting where I can control this behavior?
Environment is D3 10.2 on CentOS
------------------------------
Bob Frank
Software Developer
Joseph N Golubov Associates Inc
Leesburg FL US
------------------------------
Page 1 / 1
I work with a set of code that verifies data and emails when something is wrong so these problems can be dealt with right away. It runs overnight as a phantom started by a linux cron job.
The often changing nature of this code means it can be more prone to bugs like a variable not assigned. That's fine, I can see the problems in the runtime-errors next day and fix.
My problem is this program quits when it runs into a runtime error but if I run the same code in the foreground it doesn't.
Is there a setting where I can control this behavior?
Environment is D3 10.2 on CentOS
------------------------------
Bob Frank
Software Developer
Joseph N Golubov Associates Inc
Leesburg FL US
------------------------------
The often changing nature of this code means it can be more prone to bugs like a variable not assigned. That's fine, I can see the problems in the runtime-errors next day and fix.
My problem is this program quits when it runs into a runtime error but if I run the same code in the foreground it doesn't.
Is there a setting where I can control this behavior?
Environment is D3 10.2 on CentOS
------------------------------
Bob Frank
Software Developer
Joseph N Golubov Associates Inc
Leesburg FL US
------------------------------
1) The D3 system ID
2) A WHICH CAD from the system
3) A summary of the issue
------------------------------
Brian S. Cram
Principal Technical Support Engineer
Rocket Software
------------------------------
I work with a set of code that verifies data and emails when something is wrong so these problems can be dealt with right away. It runs overnight as a phantom started by a linux cron job.
The often changing nature of this code means it can be more prone to bugs like a variable not assigned. That's fine, I can see the problems in the runtime-errors next day and fix.
My problem is this program quits when it runs into a runtime error but if I run the same code in the foreground it doesn't.
Is there a setting where I can control this behavior?
Environment is D3 10.2 on CentOS
------------------------------
Bob Frank
Software Developer
Joseph N Golubov Associates Inc
Leesburg FL US
------------------------------
The often changing nature of this code means it can be more prone to bugs like a variable not assigned. That's fine, I can see the problems in the runtime-errors next day and fix.
My problem is this program quits when it runs into a runtime error but if I run the same code in the foreground it doesn't.
Is there a setting where I can control this behavior?
Environment is D3 10.2 on CentOS
------------------------------
Bob Frank
Software Developer
Joseph N Golubov Associates Inc
Leesburg FL US
------------------------------
------------------------------
Brian S. Cram
Principal Technical Support Engineer
Rocket Software
------------------------------
BTW, once the support case is resolved, we can post information about the solution herein.
------------------------------
Brian S. Cram
Principal Technical Support Engineer
Rocket Software
------------------------------
------------------------------
Brian S. Cram
Principal Technical Support Engineer
Rocket Software
------------------------------
Even though that option was parsed out of tclread to mean, email the results, the option still passed through to the d3 runtime.
From d3 reference manual "run command"...
e Enters debugger on any error condition. This option forces the operator to either accept the error by using the debugger, or exit to TCL.
------------------------------
Bob Frank
Software Developer
Joseph N Golubov Associates Inc
Leesburg FL US
------------------------------
I was inadvertently using an (e option to run my code from tcl.
Even though that option was parsed out of tclread to mean, email the results, the option still passed through to the d3 runtime.
From d3 reference manual "run command"...
e Enters debugger on any error condition. This option forces the operator to either accept the error by using the debugger, or exit to TCL.
------------------------------
Bob Frank
Software Developer
Joseph N Golubov Associates Inc
Leesburg FL US
------------------------------
Even though that option was parsed out of tclread to mean, email the results, the option still passed through to the d3 runtime.
From d3 reference manual "run command"...
e Enters debugger on any error condition. This option forces the operator to either accept the error by using the debugger, or exit to TCL.
------------------------------
Bob Frank
Software Developer
Joseph N Golubov Associates Inc
Leesburg FL US
------------------------------
------------------------------
Brian S. Cram
Principal Technical Support Engineer
Rocket Software
------------------------------
Sign up
Already have an account? Login
Welcome to the Rocket Forum!
Please log in or register:
Employee Login | Registration Member Login | RegistrationEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.
77 4th Avenue
Waltham, MA 02451 USA
