110 WebSphere Studio Asset Analyzer for Multiplatforms 3.1
You may also start the scanner from the command line, use the assetLocatorRun.bat
command, found in the bin subdirectory of your WebSphere Studio Asset Analyzer Windows
install directory. When the inventory is complete, the DB2 results database on the host
contains an inventory of assets taken by the scanner and analyzed by the appropriate
analyzer. At this point, users can perform queries against scanned data using the WebSphere
Studio Asset Analyzer Web-based interface. Scanner logging displays both in the scanner
GUI and in the log files. The log files are stored in the log file paths that you set in the
Common.cfg configuration file. You can stop the scanner by clicking Stop in the Crawler
Console. You have completed the inventory process. You can begin exploring distributed
3.11 Notes for the practical
Each of these notes is designed to help you establish your environment with a minimal
amount of consternation. If you have faithfully read through the previous portions of this
chapter, you know that it requires a certain amount of tenacity to set up and load WSAA.
Because each site is unique, it is entirely possible that you will run into something we did not.
We hope these notes help you.
Here is our collected list of notes for the practical:
Preload analysis concatenation sets.
Load include members before main member.
Run your inventory collection during off-hours.
Add system-level programs to the mix.
We describe each of these topics in the following sections.
3.11.1 Preload analysis concatenation set libraries
In 3.4.1, “How to create a concatenation set” on page 59, we told you how to build a
concatenation set. We also explained that the first time you create one, you would not find any
libraries in the list. You can, in fact, do something about that.
We recommend that you preload your include library names into the database so that you can
build your concatenation sets
before you perform an inventory collection. You can accomplish
this by loading the database with a non-existent member.
Here are the steps you must take to do this:
1. In your Web browser, open the Home page of WebSphere Studio Asset Analyzer.
2. Click the Inventory tab.
3. Select MVS Default Catalog for the scan method.
4. Enter the name of your include library in the MVS PDS or PDSD library field.
not assign this component to an application.
6. Enter the string, xyzzy, in the Limit member search field.
This procedure will work only if you do not have a member with that name in your data set!
7. Click the Submit button to submit the batch job.
8. After the batch job finishes, click the Explore tab.
9. Click the number (link) next to Library under the Inventory heading.
Chapter 3. Collecting your inventory 111
10.Locate your library in the list and click the name of your library.
11.If the member, XYZZY, appears on the Library details page, click delete under the Actions
column. If it does not, then you are finished.
Repeat these steps for each include library on your list.
Later, when you create your analysis concatenation sets, you will be able to add the
appropriate data sets, in the correct sequence, to allow your inventory collection to run as
efficiently as possible.
3.11.2 Load include members before main members
The existing WSAA documentation instructs you to scan the included components (COBOL
copybooks, Assembler macros, and procs) before you scan the main members. This is
significant because WSAA will always attempt to resolve any included components during an
We created a data set checklist in Table 3-1 on page 51 for you to list all of the production
libraries your site uses. We instructed you to research the order in which these libraries are
used in your site’s compilation procedures.
Make it your business to load the subordinate members first! Start at the lowest level in the
concatenation. Load the libraries — the ones in your concatenation sets — from the bottom of
the list up!
3.11.3 Add system-level programs to the mix
After you complete an inventory collection of each library, one of the items you must review is
the Run units with missing source. Figure 3-53 on page 112 shows the upper portion of this
summary page, along with some familiar components.