HP 86037B, Instruction Manual

Page: 81 / 204

4-9
Remote Control
Setting up a Measurement
Note that it is also possible for the user to access the collections for the Sys-
tem, Test Plan, or Test Group levels individually. In this case one of the follow-
ing methods can be used:
TESMngr.ParmMngr.LoadSystemParms colSystemParms, ""
TESMngr.ParmMngr.LoadTestPlanParms colTestPlanParms, ""
TESMngr.ParmMngr.LoadTestGroupParms colTestGroupParms, ""
Each of the above methods return just the one collection, whereas the expres-
sion used previously,
TESMngr.Controller.LoadParms “”, “”, “”, “”
loads all levels of the parameter collections.
There are some limitations with using these more primitive statements. First
the test executive supports scoping of parameters. That is, if a parameter
occurs at the Test Group level with one value and at the Test level with
another value, you need to use the value from the lower level (for example,
the second value) when running the test. If the variable is missing from the
Test Group level then you need to use the value from the Test Plan level. The
other limitation is that the parameter collections at the Test level are expected
to be TEScollections and the result of the
LoadTestParms
is a Visual Basic collec-
tion. The example file illustrates the procedure for obtaining the collections
individually, but once obtained, any changes are saved as a single group.
The above code requires knowledge of the test parameter names in the
testparm.mdb
database. These test parameters are the same as the information
displayed and entered in the system GUI. The
testparm.mdb
database contains
all of the setup information required in the execution of the individual tests.
All of the constants required by the GUI for parameter checking are also
included in this database. Each parameter is located in a single location in the
database. The location depends upon the type of parameter and how it is uti-
lized in the system software. Full information including the definition of the
parameter in the database that is associated with each field in the GUI and
documentation of the location of the parameter is supplied in
“TES Parame-
ters” on page 4-21 .
In order to correctly deal with the parameter scoping described above, the
complete test plan hierarchy is shown
“Complete test plan hierarchy” on page
4-10 . The hierarchy names defined must be used exactly as shown in order to
manipulate data within the
testparm.mdb
database.