ABAP_to_the_Future

Mass Checks 4.2
In the Description field, at the top you will s ee some variables (for example, &
DOW&); these get dynamically replaced by the day of week when the job runs. That
is, if you define the job as &DOW& and set it to run every day, then the first run will
be called MONDAY, the second TUESDAY, and so forth. You can get a list of such variables
by pressing (F1) while in the Description field; there are only four, and
they are all shown in Figure 4.6.
Moving down the screen, the next step is to define the Check Variant field. The
Check Variant field controls what sort of checks are going to be run against the
custom objects (a possible check variant definition can be seen in Figure 4.1)—for
example, whether you check security, performance, or everything possible.
Finally, you fill out the Object Selection area of the screen, which controls what
custom objects are going to have the ch ecks defined in the check variant run
against them. You can choose By Query to enter objects directly—all Z packages,
for example—or By Object Set to reuse a Code Inspector object set (such an
object set can be seen in Figure 4.3). The final box at the bottom of the screen
changes deepening on which radio button you choose; for example, if you choose
By Object Set, then the Object Set selection box appears, and you then have to
define that set in the Obj. Set Variant field. Otherwise, the Object Selection
Details box appears, in which you say what packages you are interested in. As an
example, you could have your ALL_Z_OBJECTS variant running every month, COM-
MONLY_USED_OBJECTS running once a week, and VITALLY_IMPORTANT_OBJECTS running
every day.
After you save your entry, you are still on the screen that is accessed from Transaction
ATC via the menu path atc administration 폷 Runs 폷 Schedule Runs. This
screen has the title Run Series: Browse Configurations at the top . On this
screen, you have a list of possible mass check runs that you can schedule. Click
the job definition you’ve just created (e.g., ZCS_MONSTERS) and then click the
Schedule icon, which looks like a blue wheel; the screen in Figure 4.7 appears.
There are three boxes here: Header, Execution, and Postprocessing. In the
Header box, you choose the Series Config. Name for the batch job that you
defined in the screen shown in Figure 4.6. Then, there are some checkboxes to
make this “official” (regular jobs scheduled by an administrator), as opposed to a
“local” ad hoc check, which is perfor med by a developer when he’s changed
something and wants to make sure he hasn’t broken anything related. Set to
Active Result means that after this check run has been executed you will see a
183