1.2 Terminology

 < Day Day Up > 



There are several unique words and phrases associated with WebSphere Studio Asset Analyzer. What follows is a brief discussion of some of the more common ones:

  • Site

  • Application

  • Concatenation set

  • Asset (also known as artifact)

Each of these terms is described in the following sections.

1.2.1 Site

In WSAA’s online help you can find the word, site, defined as:

“An enterprise system that users can access through either an HTTP IP address or a functional subsystem IP address.”

This definition is quite formal and, we believe, limited in scope. A site can, perhaps, be better explained as:

The focal point or name by which an organization wants to be known to accommodate that organization’s production application source code.

For example:

Elixir Foodstuffs (a fictional company) has 18 data centers operating worldwide. Each data center runs a z/OS system that supports one or more unique organizational units, and has one or more logical partitions (LPARs).

If Elixir Foodstuffs installed only one copy of WSAA for use by all of the data centers, there would be only one site, and it could be defined as “ELIXIR.” However, if the company installed one copy of WSAA in each data center, the site would be defined based on either the locale or the organizational unit (for example, USA43 or SEASIA02).

Restriction:  

WebSphere Studio Asset Analyzer Version 2 Release 2 only lets you define one site during product installation. Choose your site name carefully.

During inventory collection, WSAA associates the site with each of the components that is scanned into the database. It then organizes the components based on a hierarchy, which is built as a tree structure below the declared site.

1.2.2 Application

WSAA’s online help defines an application as:

“A user-defined grouping of components. You can assign CICS transactions, IMS transactions, and members as part of an application.”

An application is another level that WSAA builds as part of its hierarchy. An application name will exist below the site name in the logical hierarchy. The application entry represents any grouping of source, JCL, CICS, and other components that you choose. It is possible to build application names in WSAA that include cross-application groupings as needed by your site’s requirements.

For our purposes, an application is a group of components that represent a corporate entity. Your site may have production data sets that contain a variety of different applications’ code, or you may have specific data sets for each application. In either case, most applications invariably use some kind of mnemonic device to indicate their function. For example: Payroll systems may use PYR or PAY as the first three characters of each member name. Bookkeeping systems may use BKP as the first three characters of their member names. Each site undoubtedly has its own standards.

WSAA gives you the ability to define components and associate them with these corporate entities either when you load the database or afterwards. WSAA even allows you to create hierarchies of applications. For example, you may have a Client Billing subsystem within the Major Fixed Accounts system. When you create an application, WSAA has a field that will let you define a “parent” application. As long as you define the parent applications before the child applications, you can use the hierarchy when you explore the database for relationships (or to correct errors following inventory collection).

Refer to 3.3, “When do I use an application?” on page 57 for details regarding the specific steps you would take to create an application.

1.2.3 Concatenation set

Again, we refer to WSAA’s online help, which defines a concatenation set as:

“An ordered list of libraries to be searched to resolve references to included source (for example, JCL PROCs, assembler macros, or COBOL copybooks).”

During inventory collection, WSAA will attempt to resolve the location of each of the included components found in main programs. An analysis concatenation set — or simply, concatenation set — is a specific group, or pool, of libraries, which has a unique name, that can be used to shorten the analysis phase when the source code is scanned.

A concatenation set is the equivalent of the data sets used in a SYSLIB DD in a batch compile or specified in the ORDER parameter of a JCLLIB statement. In a similar manner, WSAA uses a top-down search through the libraries defined in the concatenation set to determine the appropriate member to use.

Refer to 3.4, “What is a concatenation set?” on page 62 for details regarding the specific steps you would take to create an analysis concatenation set.

1.2.4 Asset

Finally, WSAA’s online help defines an asset as:

“A programming asset, such as a file, an object, documentation, or code.”

Some earlier WSAA documentation refers to artifacts; the current documentation refers to assets. We prefer to use the word components.

Irrespective of how you refer to them, these are the essential elements that comprise your application portfolio. They include, but are not limited to:

  • Programs

  • Run units

  • Batch jobs

  • CICS transactions

  • Data sets

  • Data stores

  • DD names

WSAA even considers applications, concatenation sets, and projects to be assets. This is because they also make up the information that relates to your application portfolio.



 < Day Day Up > 



IBM Redbooks - Websphere Studio Asset Analyzer
Adobe InDesign CS2 @work: Projects You Can Use on the Job
ISBN: 067232802X
EAN: 2147483647
Year: 2004
Pages: 84

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net