>>>>>>>>>>>
[NOTE: END THIS EDITOR SESSION TO RETURN TO THE vtstty SCREEN]
>>>>>>>>>>>

At any given time, only one "panel" or "box" is highlighted.  This panel
will be surrounded by asterisks.  You must first highlight a panel before
you can change or select an option in that panel.  The following are
the common keyboard commands used to navigate through vtstty:

TAB		shifts focus to another panel
RETURN		depending on the context, either:
			-display a menu, or
			-select and apply a choice			
SPACEBAR	Select or deselect (toggle).  Spacebar can be used only
		in "checkboxes", indicated by "[ ]".  A "selected" checkbox
		is indicated by "[*]". Eg, selecting or deselecting a test 
		group in the tests panel.
ARROW KEYS	to move around between items in a highlighted panel
BACKSPACE	deletes text in a text field
ESCAPE		Discard a popup menu or window.
<CTRL>X		quit vtstty only, leave vtsk running
<CTRL>L		refresh the vtstty screen

SELECTING AND DESELECTING TESTS:
-------------------------------
To select/deselect all tests in a group:
- shift focus to tests panel
- highlight checkbox next to desired group
- press SPACEBAR.  This will toggle the selection.

To select/deselect individual tests
- shift focus to tests panel
- highlight desired group
- press RETURN; all tests belonging to this group will be 
  displayed in a popup menu
- highlight checkbox next to the desired test.
- press SPACEBAR to toggle.

To select all/none/default tests:
- Highlight the main control panel.  
- Use arrow keys to move to "tests".
- Press RETURN
- Highlight "all", "none" or "default" and press RETURN

                      SunVTS Session 
                      --------------
Table Of Contents:

   1. Introduction
   2. Sequencing of Tasks
   3. Fine Scheduling Control provided by Custom Mode
   4. Creating Session File
   5. Loading and running session

1. Introduction
---------------

The session feature in SunVTS can be used to run complex sequence
of test runs. This involves composing XML format based session file 
that can be used anytime later to run that session. 

Session feature primarily provides following capabilities :

  I.   Sequencing: Ability to run sequence of tasks one after another.
  II.  Fine scheduling control provided by Custom Mode

2. Sequencing of Tasks
----------------------

    The SunVTS Option file mechanism can be used for running
fixed combination of tests in any single mode. For example, 
if one has to run functional mode (offline mode) testing for 10 hours--
then a SunVTS option file can be created and used for this purpose.

However, if one has to run 10 hours of offline mode testing followed by
5 hours of exclusive mode testing, then single SunVTS option file can 
not be used for this but a session file can.

A session file is composed of sequence of tasks. Each task is similar
to sunvts option file. Hence a session file is kind of a collection
of option files composed into single XML session file. 
Each task in session file is created by importing any existing sunvts option 
file during session composition. 

        Session   :=  Sequence of Tasks [task1, task2, task3, ...]
        Task      :=  Composed from SunVTS Option File

After starting the session, all tasks are executed one after another.
A task is complete when the testing status becomes "idle", at which point,
the next task is picked up for execution. For example, if a sunvts option file 
specifies system level threshold option "Max System Time" to be 10 hours, 
and when this option file is imported as a task, the task will complete 
after 10 hours.

3. Fine scheduling control provided by Custom Mode
---------------------------------------------------

New test mode called "Custom Mode" has been introduced to support 
advanced control over tests scheduling. For powerful customized 
session capability, it is supported to import sunvts option file
created in custom mode into a session file as a task. 

For example, in exclusive mode testing, each stressful sunvts test runs 
one after another. However, for some targeted failure modes, it is desired
to run certain specific combination of exclusive mode tests together at 
same time. 

The new custom mode allows mixing of multiple tests to run in different
offline and/or exclusive stress level. Also the order of execution can be
precisely controlled. 

The "Custom Mode" offers following important scheduling option:
Note: This option is supported only in custom mode:

   From main UI, Options -> Custom ->
           Custom Mode Scheduling Policy :  Parallel OR Serial

If User chooses to specify "Serial", then the test invocations
would be strictly in sequential order within each group. 
For example, after invoking one test in a group (like "Processors"
logical group), for next invocation, the next remaining test in 
the same group would be considered.  When all tests in a specific
group has been visited, the invocation will move to next group.

On the other hand, if user chooses to specify "Parallel", then
the testing is spread across groups. (like Processors, Memory, disks,
etc). After each invocation of any test, the next invocation would
consider any test in next group. 

Another important scheduling parameter is system/group level 
concurrency. This is not specific to custom mode and is also 
available for tuning under offline mode. The system level
concurrency specifies the maximum number of tests that can be
executed at any point of time. The group level concurrency specifies
the maximum number of tests that can be running at same time in
that specific group. The concurrency value of 0 means unlimited. 

By properly tuning the custom mode scheduling policy parameter along 
with system level and group level test concurrency, fine control over 
the scheduling can be achieved in custom mode.

Once a SunVTS option file is created in custom mode, this can also be 
imported as a task during session composition.

Note:  

  - The "system level concurrency" and "custom mode scheduling policy" are
    independent of each other. Choosing "Serial" policy does not imply 
    concurrency value of 1. Similarly choosing "Parallel" policy does not
    imply concurrency value of 0 (unlimited). The policy just decides the
    order of execution not the concurrency.

  - In custom mode, when scheduling policy is chosen as "Serial" and
    concurrency > 1, multiple tests can be executed at the same time,
    in the sequential order with in each group. 

  - The "Serial" scheduling policy is useful to allow equal number of
    passes among tests irrespective of how long it takes for single pass.

  - Currently the scheduling mechanism in offline mode is equivalent
    to that of "Parallel" scheduling policy in custom mode with
    all default concurrencies set to 0 (means unlimited).

  - On switching to Custom mode all tests which support offline mode are
    selected by default. Later, additional tests can be selected and
    individual tests can be selected to run in higher (exclusive mode)
    stress levels along with other tests.


4. Creating Session File
------------------------

     To compose a session file, invoke following menu option: 
           Session -> Edit  

    You will be presented with session edit dialog box with following 
    options:

     - Specify a new session name or select an existing session to edit.

     - To create a new task, click on "Create New Task ..." button.
       A new dialog box appears with a list of available sunvts option files.
       Select the desired option file which will be imported as a task. 
       Specify a new task name. Note that the task name can be different from
       the option file name. Click on "Import" to complete task creation.
       The new task would appear in available tasks.
       Note that the "Export" button can be used any time to export any of
       the available task to create the sunvts option file.

     - Import as many tasks as needed from one or more option files.

     - Compose the desired tasks sequence using "<<Insert" button that inserts
       tasks in the sequence from the available tasks.

     - Select "Run on Error:" as Enable or Disable. By default it is enabled.
       If enabled, then a running session will pickup next task when there
       is an error encountered in current task. If disabled, then the
       session will terminate when the current running task terminates with
       an error-- the next task won't be picked up for execution.

     - Loop Count: Specify the number of iterations that the sequence of
       the tasks in the session file should be executed before the session
       stops.

     - Max Session Time Limit: Specify the session time out limit in minutes(??)
       The session would stop after this time elapses.
       
     - Description: Enter a brief description about the session file that is
       being composed. This will be saved as part of the session option file
       for informational purposes.

     - Save/Save As/Delete/Close/Help: These options are self explanatory.

5. Loading and Running Session
------------------------------

     5.1 From UI
     -----------

     To load already composed session using UI, invoke:
         Session -> Load 

     Following options would appear in new dialog box:

     Session Name: Select the session name from the available pulldown menu.
     Info: If you click on "Info" button, the description about the selected
           session file would appear in another new window.
     OK: Click OK to load the session file.
     Cancel/Help: These options are self explanatory.

     To start running the session, press the "Start" button from the main UI.

     5.2 From Command Line
     ---------------------

     To load session file from command line, execute following vts_cmd option:
    
       # /opt/SUNWvts/bin/vts_cmd  session load <session-name>

     To start the session after load, execute following command line:

       # /opt/SUNWvts/bin/vts_cmd  start

>>>>>>>>>>>
[NOTE: END THIS EDITOR SESSION TO RETURN TO THE vtstty SCREEN]
>>>>>>>>>>>
