Previous Home Site Map Contact Next
Wasmer Consulting BaseOps User's Guide Command-Line Options
The name of a BaseOps case file may be specified on the BaseOps command line. This file will be opened when BaseOps runs. This allows you to associate the extension .baseops with the BaseOps application, and invoke BaseOps by double-clicking on a case file from Microsoft Windows Explorer.
An old-format case file (i.e., a file with the extension .ops, .opx, or .bps) may also be specified on the command line. If a corresponding .baseops file exists (i.e., a file with the same base name, but with an extension of .baseops), it will be opened. Otherwise, a new .baseops case file will be created from the existing file.
Enclose file names containing spaces with double-quotes, as in...
C:\>baseops "My Case File.baseops"
Creates all relevant noise model input files for a BaseOps case. This includes the .ops and .opx files for NMap, the .ops files for AAM and RNM, and the .ins and .inx for MRNMap. If the BaseOps case contains multiple scenarios, then distinct input files are created for each scenario.
The effect is the same as if you manually performed the following steps.
Start BaseOps and load the case file
Go to the Run page
Choose to Run All Scenarios
For the run steps to perform, select Run Only The Following Steps
For each noise model, check those steps up through the creation of the relevant .opx, .opx, and .inx files, and uncheck all subsequent steps
Run the case
Change all of the run options back to the original values they had when the case was loaded
C:\>baseops -makeopx "My Case File.baseops"
This command line is intended to be used as part of a batch operation. BaseOps will exit after creating the relevant noise model input files. See Batch Mode Error Handling for a discussion of how errors are handled while processing this option.
The following command-line options cause BaseOps to open, perform a task, and then shut down.
These options are typically used when BaseOps is being run from a script or as a child process of another application. In this situation, BaseOps enters batch mode, which causes errors to be handled differently. Instead of an error message dialog box appearing, BaseOps writes the error message to a text file and then exits.
If an error does not occur, BaseOps deletes the error message file if it exists. Therefore, after BaseOps exits, the calling script or application can determine if an error occurred by checking for the existence of this file. If the file exists, it will contains a description of the error that occurred.
By default, the error message file is located in the BaseOps home directory (i.e., the same directory as BaseOps.exe), and is named BaseOpsBatchErrorFlagFile.txt. If desired, you can specify another name using the -BatchErrorModeFlagFile command-line option. This option should be followed by the desired error message file name.
If your script or application will be simultaneously running multiple instances of BaseOps, it is strongly suggested that you use -BatchErrorModeFlagFile to specify a different error file for each instance.
In addition to the error file, BaseOps also uses a non-zero return code to indicate that an error occurred.
Previous Home Site Map Contact NextCopyright © 1996-2017, Wasmer Consulting