User Input File Requirements
Terminal Script Files
A Transaction Script File defines a sequence of transactions that will be executed on one simulated terminal. If a terminal finishes executing all the transactions in its corresponding script file before the experiment execution time runs out, it loops back to the beginning of the file and re-executes the script.The user must provide a script file for each terminal he would like to simulate. The path to the directory that contains all script files must be provided by the user before an experiment can be executed.
File Name Restriction
"Terminal" + TerminalNumber + ".scp"
In order to run an experiment, the user must specify the total number of terminals he would like to simulate. The first terminal gets the terminal number "0", the second gets the terminal number "1", and so on. If, for example, the total number of terminals is 10, then the script files must be named "Terminal0.scp", "Terminal1.scp", "Terminal2.scp", ... and "Terminal9.scp".
Content Convention
A Transaction Script File consists of several transaction sessions. Each transaction session contains a number of transactions that will be simulated to be executed by one client of the user database application. Transactions are represented using the transactions procedure names defined in Transaction Prototypes File. Transaction sessions are separated by a line with the sign ">>" . For example,
>>
... transaction session 1...>>
... transaction session 2...>>
... transaction session 3...... ...
Sample File
In a Student Registration System, for instance, there might be several students waiting on line to use a terminal for registering courses. Thus, a typical transaction script file representing transactions executed by these students on a terminal may look as follows:
(File name: Terminal0.scp)
>>
Login
AddCourse
AddCourse
DropCourse
Logout>>
Login
AddCourse
AddCourse
Logout>>
Login
SearchCourseInfo
ViewGrades
Logout... ...
Back
to User Input File Requirements
