User Input File Requirements

Transaction Prototypes File

Transaction Prototypes File locates each transaction procedure source file and keywords that will be used in an experiment. The user must provide the path to this file through the user interface before an experiment can be executed.

  File Name Restriction

None

  Content Convention

The Transaction Prototypes File consists of two sections -- prototype section and keyword section; the two sections are separated by a line with the mark '%%' :

prototype definitions

%%

keyword definitions

The "prototype definitions" section specifies what transaction procedures will be used for an experiment. Each procedure is represented by its signature written in the format:

ReturnType TransactionName ( ParameterType1 ParameterName1, ParameterType2 ParameterName2, ...) ;

Each signature should correspond to the signature in the corresponding Transaction Procedure Source files.

The "keyword definitions" section specifies any session or terminal keywords that will be involved in an experiment. Each keyword must correspond to a parameter name defined in one of the transaction prototypes.

To define session keywords, write the definition in the format of:

Session Keywords:
keyword1
keyword2

:
:

Similarly, terminal keywords must be defined in the format of :

Terminal Keywords:
keyword1
keyword2

:
:

The order of session keyword definition and terminal keyword definition is interchangeable.

  Sample File (without keywords)

If there are no keywords required, left the keywords definition blink.

int Login ( Connection con, String user, String passwd) ;
int AddCourse ( Connection con, String user, String course ) ;
int DropCourse ( Connection con, String user, String course ) ;

 

  Sample File (with keywords)

int Login ( Connection con, String user, String passwd) ;
int AddCourse ( Connection con, String user, String course ) ;
int DropCourse ( Connection con, String user, String course ) ;

%%


Session Keywords:
user
passwd

Terminal Keywords:
user
passwd
course


Back to User Input File Requirements

Back to Help Contents