Mistakes with dxl script in Batch Mode

SystemAdmin - Mon Feb 21 05:30:28 EST 2011
I'm not an expert on batch mode but I need the experience! So here goes!

If I was to put my finger on the problem, I think it's either the myDB Dialogue Box call or the statement "print "Error occured: " s "\n" or both.

Batch mode cannot raise the DXL Interaction window to display the print statement during batch mode. Same goes for any dialogue boxes.

Do I get any marks or did I fail miserably?

VBdo - Mon Feb 21 05:38:53 EST 2011
I have another Script, that also has print statement, and works without problems!

Mathias Mamsch - Mon Feb 21 06:25:32 EST 2011
There are two possible reasons for this:

1. In batch mode your script will be executed at a different context as in "Interactive Mode". In Interactive mode DOORS will create its own DXL context and add { attrDxlName = ...; obj__ = ...; your script goes here } to your script, I think that won't happen in batch mode. Therefore in batch mode your script will conflict, since "parent" is already defined on top level (and is a function).

2. In batch mode other include files than in interactive modes are loaded at startup. It may be that one of the includes already defines a 'parent' variable or function.

So you should:
a) use a different name for your variable
(or b) wrap your program in curly braces to avoid the name clash.

Regards,Mathias

VBdo - Mon Feb 21 07:37:42 EST 2011
Thank you Mathias,
a) was right for me!

llandale - Mon Feb 21 11:55:26 EST 2011
b) is also right. Well "right" in the sense of getting rid of this problem; my batch scripts have been working fine for a long time without it, but that's primarily because I write modular code and rarely have anything much defined in the "main" context anyway.

• Louie

lsand - Thu Apr 14 16:28:31 EDT 2011
I don't understand option b)...can you explain a little more? I am having the same problems when I try to run in batch mode...

lsand - Thu Apr 14 16:30:00 EDT 2011
I changed my variable name and now I get a bunch of errors regarding an invalid argument type.

lsand - Thu Apr 14 16:32:02 EDT 2011
I take that back. After I changed the variable name, I ran it without saving thus all the errors. works great, but would still like to hear more about option b.

SystemAdmin - Mon Feb 21 05:30:28 EST 2011
I'm not an expert on batch mode but I need the experience! So here goes!

If I was to put my finger on the problem, I think it's either the myDB Dialogue Box call or the statement "print "Error occured: " s "\n" or both.

Batch mode cannot raise the DXL Interaction window to display the print statement during batch mode. Same goes for any dialogue boxes.

Do I get any marks or did I fail miserably?

vasgyuszi - Tue May 17 10:26:06 EDT 2011

Dear Experts,

I've got a very similar problem, but the receiver error messages point to DOORS internal sources and not to mine.

The situation:
1) script runs in interactive mode perfectly
2) in batchmode (-b "Windows path to the dxl file") receive errors, but my script itself delivers perfect results
3) I've turned off the visibility of the loaded basilne within my script (which makes the result useless) and than runs through even in batchmode withouot errors.

Weird...

The error messages are:

-E- DXL: <config/colmenu.inc:24> incorrect arguments for function (createItem)
Included from:
    <config/formal:20> 
        <Line:1> 
-E- DXL: <config/colmenu.inc:24> undeclared variable (alwaysOn)
Included from:
        <config/formal:20> 
        <Line:1> 
-E- DXL: <config/colmenu.inc:28> incorrect arguments for function (createItem)
Included from:
        <config/formal:20> 
        <Line:1> 
-E- DXL: <config/colmenu.inc:28> undeclared variable (columnSelected)
Included from:
        <config/formal:20> 
        <Line:1> 
-E- DXL: <config/colmenu.inc:34> incorrect arguments for function (createItem)
Included from:
        <config/formal:20> 
        <Line:1> 
-E- DXL: <config/colmenu.inc:34> undeclared variable (alwaysOn)
Included from:
        <config/formal:20> 
        <Line:1> 
-E- DXL: <config/colmenu.inc:37> incorrect arguments for function (createItem)
Included from:
        <config/formal:20> 
        <Line:1> 
-E- DXL: <config/colmenu.inc:37> undeclared variable (columnSelected)
Included from:
        <config/formal:20> 
        <Line:1> 
-E- DXL: <config/formal:29> incorrect arguments for function (createItem)
Included from:
        <Line:1> 
-E- DXL: <config/formal:29> undeclared variable (lockSection)
Included from:
        <Line:1> 
  too many messages -- suspending error reporting-I- DXL: all done with 516 errors and 0 warnings
-E- DOORS: DXL contains 516 errors
-E- DXL: <config/formalheading:23> incorrect arguments for function (createItem)
Included from:
        <Line:1> 
-E- DXL: <config/formalheading:23> undeclared variable (alwaysOn)
Included from:
        <Line:1> 
-E- DXL: <config/formalheading:26> incorrect arguments for function (createItem)
Included from:
        <Line:1> 
-E- DXL: <config/formalheading:26> undeclared variable (columnSelected)
Included from:
        <Line:1> 
-E- DXL: <config/formalheading:45> incorrect arguments for function (createMenu)
Included from:
        <Line:1> 
-E- DXL: <config/formalheading:45> undeclared variable (canSortMap)
Included from:
        <Line:1> 
-E- DXL: <config/formalheading:47> incorrect arguments for function (createItem)
Included from:
        <Line:1> 
-E- DXL: <config/formalheading:47> undeclared variable (canSortAscending)
Included from:
        <Line:1> 
-E- DXL: <config/formalheading:47> undeclared variable (canSortAscendingMap)
Included from:
        <Line:1> 
-E- DXL: <config/formalheading:50> incorrect arguments for function (createItem)
Included from:
        <Line:1> 
  too many messages -- suspending error reporting-I- DXL: all done with 13 errors and 0 warnings
-E- DOORS: DXL contains 13 errors

and my script as follows:

string out_filename 
 
const string sourceModuleName = "/M3AR/Modules/HRCX/LLR_SW_HRCX"
 
Baseline b = baseline(2,0,"BASELINESET_CRCX_07.06_08.10")
 
const string colId = "Req.ID"
const string colCode = "Source Code"   
 
/*
* function for exporting the given module to csv file
* the columns to export are defined below
*/
string exportToCsvPld(string mName, string viewName)
{
    Module m = current
    string attrbName
    Object o
    string inhalt
    string separator = ","
    string hochkomma = "\""
 
    m = read(mName, false)
    if (null m) { errorBox "Failed to open module " mName "."; return }
    else current = m
 
    load(m,b,true)
    load view viewName
 
    out_filename = out_filename ".csv"
    if (canOpenFile(out_filename, false)) deleteFile(out_filename)
    Stream app = append out_filename
    
    app << hochkomma
    app << colId
    app << hochkomma
    app << separator 
    app << colCode 
    app << "\n"
    app << hochkomma
    app << "__View__"
    app << hochkomma
    app << separator 
    app << hochkomma
    app << "View: " viewName " / Baseline: " (major b)"."(minor b)" "(suffix b)
    app << hochkomma
    app << "\n"
    
    for o in current Module do {
        inhalt = o.colId
        app << hochkomma
        app << inhalt 
        app << hochkomma
        app << separator 
        app << hochkomma
        inhalt = o.colCode  
        app << inhalt 
        app << hochkomma
        app << "\n"
    }
    
    close app
    close m
    close current Module
    return("")
    
}//string exportToCsvPld(string mName, string viewName)
 
 
/* first count all Items */
Item m
int numberOfItems =0
Project p
for p in database do for m in p do if (type(m) == "Formal") numberOfItems++
 
/* read all modules to string array, for further use in list box */
string modules[numberOfItems]
int i =0
for p in database do {
    for m in p do {
        if (type(m) == "Formal") {
            modules[i]=fullName m
            i++
        }
    }
}
 
out_filename = (getenv "TEMP") "\\traceability\\requirements"
exportToCsvPld(sourceModuleName, "SW CPLD DO-Release view")
if (batchMode) exit_

Thanks in advance,
vasgyuszi