![]() |
![]() |
![]() |
![]() |
![]() |
Batch Mode
Using the Targeting Expert in the batch mode means starting taexbatch instead of sdttaex.
The commands have to be given one after another by hand or in a command file. (Please see an Example of a Batch File.) In this case the Targeting Expert has to be started with taexbatch < commandfile
Syntax of Batch Mode Commands
Command Names
You may abbreviate a command name by giving sufficient characters to distinguish it from other command names. A hyphen ('-') is used to separate command names into distinct parts.
Abbreviation of Commands
You may abbreviate any part as long as the command does not become ambiguous.
Commands used in command files should not be abbreviated because future implementations may conflict with those abbreviations.
Parameters in Commands
Parameters are separated by one or several spaces. Parameters containing spaces have to be given in quotation marks.
Case Insensitivity in Commands
In command names there is no distinction made between upper and lower case letters.
Some more Detailed Description of Parameter Types
- <flagname>
- For Cadvanced a description of allowed flags can be found in section Some Configuration Macros.
- For Cmicro see Compilation Flags for a more detailed description.
- For Cextreme see Optimization and Configuration.
- <boolvalue>
- <stringvalue>
- <entry>
- Allowed entries depend on the class used in the command. Please see <class>. Parameters of type <entry> are case insensitive.
- <class>
- Allowed classes and the depending entries are shown in the table below. Parameters of type <class> are case insensitive.
- For all allowed combinations of classes and entries the commands Get-Setting and Default-Setting can be used.
Description of Batch Mode Commands
In this section, the batch mode commands are listed in alphabetical order, along with their parameters and a description.
Add-PR
Further PR files can be specified here which should be considered by the SDL to C compiler.
The first PR file has to be given by using Open-PR command.
Add-Setting-String
<class> <entry> <stringvalue>The list <entry> will be extended for the item <stringvalue>.
Add-UserSection-String
<stringvalue>The <stringvalue> will be added in the user section of ml_mcf.h (Cmicro), sct_mcf.h (Cadvanced) or extreme_user_cfg.h (Cextreme).
Analyze
<none>The SDL system will be analyzed.
Append-Setting-String
<class> <entry> <stringvalue><stringvalue> will be appended to the current value of <class> <entry>.
Clear-UserSection
<none>The complete user section of ml_mcf.h (Cmicro), sct_mcf.h (Cadvanced) or extreme_user_cfg.h (Cextreme) will be removed.
Default-Setting
<class> <entry>The default value of the given <entry> will be restored.
Exit
<none>The Targeting Expert exits (same as Quit).
Generate-Code
<none>A code generation for the selected component is done using the SDL to C compiler selected in the associated settings.
Generate-Code-Full
<none>A full code generation for the selected component is done using the SDL to C compiler selected in the associated settings.
Generate-Makefile
<none>A makefile will be generated for the selected component. The makefile's name is taken from the associated settings.
Get-Setting
<class> <entry>The current contents of <entry> will be printed on the screen.
Include
<batch-filename>All the commands listed in <batch-filename> will be processed.
Help
<none>A list of all commands with their needed parameters is printed.
Make-All
<none>For the application or all the nodes and components that are configured (combined or separate configuration) the steps of analysis, code generation, makefile generation and compilation/linkage will be performed.
Make-Clean
<none>All the object files will be removed.
Make-Selected
<none>The make tool will be executed using the associated make tool and the associated makefile of the selected component.
Open-PDM
<filename>The partitioning diagram file <filename> will be loaded.
Open-PR
<filename>The PR file <filename> will be loaded and internally converted into a partitioning diagram model.
Open-SDT
<filename>The system file <filename> will be loaded and internally converted into a partitioning diagram model.
Prepend-Setting-String
<class> <entry> <stringvalue><stringvalue> will be prepended to the current value of <class> <entry>.
Qualifier
<SDL-qualifier>The given <SDL-qualifier> will be used for building a part of the SDL system.
Quit
<none>The Targeting Expert exits (same as Exit).
Replace-Setting-String
<class> <entry> <old-stringvalue> <new-stringvalue>The string <old-stringvalue> of <entry> will be replaced with <new-stringvalue>.
Save-Settings
<none>The modified settings of all the available applications, nodes and components will be saved.
Select
[<application-node-component>]The entry specified by <application-node-component> in the partitioning diagram will be selected. This step has to be executed before you can generate.
One of the commands Open-PDM, Open-PR or Open-SDT has to be executed before.
Set-Compiler
<compilername>The given <compilername> will be set as the used compiler. The <compilername> must be available in the default settings of the Set-Integration.
The command Set-Integration has to be executed before.
Set-Flag-Bool
<flagname> <boolvalue>The SDL to C compiler's library flag <flagname> will be set/reset due to the <boolvalue>.
Set-Flag-String
<flagname> <stringvalue>The SDL to C compiler's library flag <flagname> will be set to the <value>.
There is no check for upper and lower limits. You must be aware to set a value that is in the allowed range!
Set-Integration
<integration>The pre-defined integration settings <integration> will be set.
To set a Realtime Simulation for example, the <integration> has to be given in quotation marks, i.e.
In batch mode there is no check if the selected integration fits to the component settings!
Please have a look to Distributed Pre-defined Integration Settings for more information.
The command Select has to be executed before.
Set-Setting-Bool
<class> <entry> <boolvalue>The boolean <entry> will be set to its new value.
Set-Setting-String
<class> <entry> <stringvalue>The non-boolean <entry> will get the new content <stringvalue>.
Start-Download
<none>The download application selected in Download Application will be invoked.
Start-Testtool
<none>The test application specified in Test Application will be invoked.
system
<systemcommand>Executes the <systemcommand> on the underlying OS. The following placeholders can be used in <systemcommand> and will be replaced before execution:
%s %b %tsub target directory (the one calculated depending on the selected component and integration)
%e %iTarget
<target>The <target> becomes the SDL system's part to build. The generated files will be placed in a subfolder with <target> as part of the folder name.
Write-Log
<filename>All the output to stdout and stderr will also be written into the file <filename>.
Example of a Batch File
The following batch file can be used to build a Simulator using the Targeting Expert batch mode.
Example 489 : Simple batch file
Open-SDT access.sdtselect access-node-componentset-integration Simulationset-Compiler MicrosoftGenerate-CodeGenerate-MakefileMake-selectedExit
The items application, node and component depend on the partitioning diagram model used.
http://www.ibm.com/rational |
![]() |
![]() |
![]() |
![]() |