D3 and mvBase

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
------------------------------

Hi, Bob. Sorry for the late reply. I think it would be a good idea to open a support case for this. If you can open cases in RBC ( Rocket Business Connect ), please do so. If not, simply send and email to support@rocketsoftware.com which contains:

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
------------------------------

Original Message:
Sent: 07-08-2022 16:15
From: Bob Frank
Subject: program stopping on variable not assigned

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
------------------------------

BTW, once the support case is resolved, we can post information about the solution herein.

------------------------------
Brian S. Cram
Principal Technical Support Engineer
Rocket Software
------------------------------

Original Message:
Sent: 07-08-2022 16:15
From: Bob Frank
Subject: program stopping on variable not assigned

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
------------------------------

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
------------------------------

Original Message:
Sent: 07-12-2022 09:37
From: Brian Cram
Subject: program stopping on variable not assigned

BTW, once the support case is resolved, we can post information about the solution herein.

------------------------------
Brian S. Cram
Principal Technical Support Engineer
Rocket Software

Original Message:
Sent: 07-08-2022 16:15
From: Bob Frank
Subject: program stopping on variable not assigned

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
------------------------------

Thanks, Bob. I'm going to post this in the case so that someone searching case history for a similar problem will be able to see the whole story.

------------------------------
Brian S. Cram
Principal Technical Support Engineer
Rocket Software
------------------------------

Original Message:
Sent: 07-15-2022 12:40
From: Bob Frank
Subject: program stopping on variable not assigned

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

Original Message:
Sent: 07-12-2022 09:37
From: Brian Cram
Subject: program stopping on variable not assigned

BTW, once the support case is resolved, we can post information about the solution herein.

------------------------------
Brian S. Cram
Principal Technical Support Engineer
Rocket Software

Original Message:
Sent: 07-08-2022 16:15
From: Bob Frank
Subject: program stopping on variable not assigned

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
------------------------------