I have a DXL script that loops through some modules and in each module, loops through the Views. Some views in these modules are stale and make references to now-deleted attributes. In some cases the filters saved in these views do too. As my script runs, DOORS pops up dialog boxes that pause my script, waiting for the user to acknowledge that the view that was just loaded refers to attribute XYZ but attribute XYZ doesn't exist. Then my script can resume.
Is there a way to programmatically catch these View errors and not require the user to deal with them? Or is there some other way to suppress these errors?
Thanks!
-Bob3
SystemAdmin - Mon Mar 05 19:13:33 EST 2012 |
|
Re: Catch or Suppress 'View Errors'
SystemAdmin - Mon Mar 05 22:23:33 EST 2012
As far as I know, when executing a DXL script that opens modules so that they are visible, you cannot suppress or auto close error dialogues that pop up and require a user to select a button such as "OK" or "Close". The DXL noError() function will suppress DXL run time errors but not dialogues that pop up due to the GUI having a problem, such a loading a view with a filter but one or more attributes in the filter no longer exist. I'm sure that Louie L or Mathias M will contribute and correct me if I'm wrong.
I think the only way to do this is to use Batch Mode to execute the script from the command line and use the -W switch to suppress user interactive dialogues - click here to see an IBM Tech Note about Batch Mode and the -W switch.
A quick test using the DXL module read\edit functions with the Display argument set to false doesn't seem to suppress these errors as the quick test I did revealed that the View with the problem just doesn't load at all.
Paul Miller
Melbourne, Australia
|
|
Re: Catch or Suppress 'View Errors'
SystemAdmin - Mon Mar 05 23:22:01 EST 2012 SystemAdmin - Mon Mar 05 22:23:33 EST 2012
As far as I know, when executing a DXL script that opens modules so that they are visible, you cannot suppress or auto close error dialogues that pop up and require a user to select a button such as "OK" or "Close". The DXL noError() function will suppress DXL run time errors but not dialogues that pop up due to the GUI having a problem, such a loading a view with a filter but one or more attributes in the filter no longer exist. I'm sure that Louie L or Mathias M will contribute and correct me if I'm wrong.
I think the only way to do this is to use Batch Mode to execute the script from the command line and use the -W switch to suppress user interactive dialogues - click here to see an IBM Tech Note about Batch Mode and the -W switch.
A quick test using the DXL module read\edit functions with the Display argument set to false doesn't seem to suppress these errors as the quick test I did revealed that the View with the problem just doesn't load at all.
Paul Miller
Melbourne, Australia
-Bob3
|
|
Re: Catch or Suppress 'View Errors'
SystemAdmin - Tue Mar 06 21:57:40 EST 2012 SystemAdmin - Mon Mar 05 23:22:01 EST 2012
Thanks for your input Paul, I appreciate it!
-Bob3
|
|
Re: Catch or Suppress 'View Errors'
develop_per - Tue Mar 13 08:39:36 EDT 2012
I know someone that has created an excel workbook that suppress the DOORS error message behavior described.
I saw a demo of the excel workbook where a dxl script opened over six thousand views that had over 300 dxl errors. The workbook allowed the dxl script to continue to open the views without the user having to click on the error message.
I’ve tried to get this person to sell the workbook, but he is reluctant because of potential problems and continues to use it for his own personal use.
Maybe if there is enough interest express we might get him to distribute the workbook. Does anyone have any suggestion on how he can distribute the workbook while limiting his liability?
|
|
Re: Catch or Suppress 'View Errors'
llandale - Tue Mar 13 13:48:59 EDT 2012
I'm pretty sure that surrounding your "read(module)" or "load(view)" commands with noError() and lastError() will suppress DXL run time errors, such as no such attribute.
-
noError()
-
load(view)
-
string ErrMess = lastError()
-
if (!null ErrMess) then log "load view error " ErrMess
This won't suppress interpret errors such as cannot see an include file.
-Louie
|
|