3.1 How to load your WSAA database

---

You, as a WSAA system or product administrator, can load the WebSphere Studio Asset Analyzer (WSAA) database immediately after your site’s systems programmer has completed the initial verification process for the product.

Important:  

A discussion of how to install WSAA is beyond the scope of this redbook; however, Appendix D, “WSAA installation notes” on page 195 contains pertinent information and some of our observations of installations at actual customer sites.

After you have a working database environment, you need to:

• Identify your production source code components

• Define your applications and analysis concatenation sets

• Load the database with online information

• Load the database with source code

• Resolve errors

When you identify your production source code components, you engage in a form of requirements gathering for your project. Once you have that information, you define your applications and concatenation sets using WSAA’s Web browser interface. After you build these prerequisite elements, you load your online information using WSAA’s ISPF interface and your source code using WSAA’s Web browser. After each unit of data is loaded, you use the Web browser to check the results and to resolve any errors.

Each of these topics is covered in greater detail throughout the rest of this chapter.

Note 

We wondered whether it made any difference if a site’s CICS information was loaded before or after the MVS source components.

Our research indicates that it does not. WSAA will resolve your transaction-to-program relationships irrespective of the order in which you load the database.

We describe how to load CICS information before we describe how to load source code simply because it fits better within the framework of this chapter.

---