The
New Method Wizard is used to create a new method, which is the extraction proposal containing the set of operations needed for the creation
of the test environment. During method creation, all the information concerning the method is saved locally in a directory
indicated by the user
Reduction can be obtained for data stores of a certain size and/or a particular type. In this case, you must be knowledgeable
about the application to determine the appropriate selections. However, the
Data Subset Extraction module can recognize and automatically create a first subset containing a series of files (called register table files) that
are initially brought into the new test environment. Identifying register table files has the following advantages:
- You can create a method to extract only the register table file subset, which is normally valid for the creation of any test
environment independently of the selection criteria applied. Once this method has been saved and confirmed, it can be run
whenever necessary.
- You can create a second file subset, which filters the register file subset you created, to produce a file subset that is
reduced even further.
To create a simple method:
-
Launch the
New Method Wizard ().
-
In the
Machine ID list, click
DATAEXPRES.
-
In the
Company list, click
DEMO.
Files belonging to different workspaces cannot be included.
-
Click
Next to go to the next screen.
Note: If a group has not previously been defined in the
Work with Groups area, it can be defined from this screen, by simply specifying its name and description in a specific field.
-
In the
Group name box, click
SIMPLESUB.Text in the
Group description box populates automatically.
-
In the
Method box, type
SIMPLEDB2.
-
In the Method description box, type:
SIMPLE DB2 METHOD.
-
Click
Next.
-
Select
Import all non-register table Data Stores to include demographic files are registered in a dedicated elaboration step of the method.
-
Click to clear the
Import all register table Data Stores box.
-
Click
Next to go the next screen.
-
Select NAME to be used as the primary extraction criteria.
-
Click
Next.
The
Data Subset Extraction module automatically extracts all the environment files containing the selected classes, entering them into a specific step.
Once the method has been created, the remaining files (that is the files that are not sensitive to the selected classes) will
initially be excluded from elaboration. During the
Method Confirmation phase, they can be included in the method again. These files will then be integrally copied into the new environment generated
by the method involved.
The primary extraction criteria are listed in the
Selection class field.
-
For this tutorial, specifying a selection class in the Other Class is not necessary because you are creating a method for
only one data store. You do not need another class. Note that both the DB2 and sequential data stores used throughout these
tutorials both use the class NAME. Click Finish.
-
Click
Yes.
The
Data Subset Extraction module automatically extracts all the environment files containing the related classes and inserts them in a further elaboration
step.
The
Create Method window is displayed:
-
Click
Start.
-
Click
OK.
-
Click
Confirm.
During method confirmation, specified filters are applied to the classes needed to perform the extraction, and the method
information is imported from a temporary file to the Knowledge Base.
In this example, we will simply create a method based on the data stores that use the class NAME.
-
In the
Prefix box, type:
URADAR.DEMOT.SUB.DB2CUST.
-
Click to clear the
Move excluded data stores into new step box.
-
Click
OK.
-
In the
Choose a Filter Type list, click
FILTER BY VALUE LIST.
-
In one of the boxes on the lower left side, type:
Rick.
-
Click
OK to close the
Set Filter to Selection Classes window.
-
In the
Unload Output Data Store Name box, type:
URADAR.DEMOT.SUB.DB2CUST
-
Click
OK to confirm the method.
-
In the
Work with Method window, click
Properties:
-
Click
Active.
-
Click
OK.
-
Click
OK.
-
Continue to the next section.