![]() |
![]() |
![]() |
![]() |
![]() |
Logging the Execution
The following types of interaction during simulation can be logged to file:
- The commands issued by the user.
- The complete interaction with the user, i.e. commands issued and resulting print-outs. In other words, all texts visible in the Simulator UI's text area or in the terminal window.
- The signals sent to, from and via a unit in the system.
The logging of MSC events to file is described in MSC Trace and Logging.
Logging Commands
To start logging of all issued monitor commands from now on:
- Select Start Command Log from the Log menu, or enter the command Command-Log-On. This command takes one parameter, the name of the log file.
- Select or enter a log file name; on UNIX preferably with the suffix .com.
To stop the logging, select Stop Command Log from the Log menu, or enter the command Command-Log-Off.
After logging has been stopped, it can be continued on the same log file, i.e. the existing log file is appended, or on a new log file.
To continue logging of monitor commands:
- If using the Simulator UI's menu commands, select Start Command Log from the Log menu. Select or enter the same file name as before, or a new file name.
- Click Append to append the existing log file. Click Create to overwrite the existing log file.
- If using monitor commands, enter the command
Command-Log-On, with or without a file name parameter.All monitor commands issued by the user so far in the Simulator UI session can also be saved on a command file, without starting continuos logging of commands. To do this, select Save from the popup menu on the input line and select a command file.
A command log file may later be read in and executed to repeat the same command session. To do this:
- Choose Script in the Execute menu, or enter the command Include-File. This command takes one parameter: the name of a file containing monitor commands.
- Select or enter the name of an existing command file. When the file has been specified, it is read and the commands in the file are executed exactly as they are stated in the file.
Logging the User Interaction
Complete logging of all user interaction works in the same way as logging of monitor commands, described above. The only difference is the name of the menu choices and commands. Either select Start Complete Log and Stop Complete Log from the Log menu, or enter the commands Log-On and Log-Off.
Logging Signal Interaction
The signals that are sent to, from or via a unit in the system can be logged on file. The signal log file will contain a line for each signal sent, including the simulation time, the name of the signal, the sender process instance and the receiver process instance. Values of signal parameters are also printed.
More than one signal log can be active at a time, each one in a separate log file.
- Enter the command Signal-Log (this command has no associated button). This command takes two parameters: a unit in the system, and the name of a log file.
- Select or enter a unit whose signals are to be logged. A unit can be one of the following:
- A channel or signalroute. Signals sent through the channel or signalroute are logged.
- A process type or process instance. Signals sent to and from any of the process instances are logged.
- A block or a system. Signals sent within, to and from the system or block are logged.
- The process "env." In this way, the signal interface between the system and the environment is logged.
- Select or enter a file name of the signal log file.
To list the active signal logs, enter the command List-Signal-Log (this command has no associated button). The list contains an entry number, the unit name and the log file name.
- Enter the command Close-Signal-Log (this command has no associated button). This command takes one parameter, an entry number in the signal log list.
- Enter an entry number. To see what entry number is associated with the timer instance, list the active signal logs as described above. If only one signal log is active, the entry number is not needed.
http://www.ibm.com/rational |
![]() |
![]() |
![]() |
![]() |