3.3 When do I use an application?

 < Day Day Up > 



As described in 1.2, “Terminology” on page 9, an application is defined as:

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

Your site may have production data sets that contain a variety of application code, or you may have specific data sets for each application. In either case, most applications usually use some kind of mnemonic to indicate their function.

For example:

  • Payroll systems uses PYR as the first three characters of each member name.

  • Bookkeeping systems use BKP as the first three characters of their member names.

When you assign components to an application, all of their subordinate components become part of that application.

WSAA lets you use up to sixteen characters to create an application name. In fact, it goes one step further: it lets you create a hierarchy of applications based on a parent/child structure. For example:

  • The Statements group in your Payroll department uses STM for their programs. You first create the application for Payroll. Then, you create the application for Statements and indicate that Payroll is the parent application. WSAA represents this as:

    STM * PYR

Whether your production source code is maintained in a source code management system (SCM) or a group of partitioned data sets, WSAA lets you define how your site’s applications are categorized.

3.3.1 How to define an application

So, if you want WSAA to recognize your application code as a unique entity, you must create an application. To do so, perform the following steps:

  1. In your Web browser, open the Home page of WebSphere Studio Asset Analyzer.

  2. There are two ways to open the Application summary page:

    1. Click Explore -> MVS assets. The Explore MVS assets page is displayed.

    2. Click the number (link) next to Application under the Inventory heading. ora. Click Assets by Application on the Home page.

    The Application summary page is displayed, as shown in Figure 3-1.

    click to expand
    Figure 3-1: Application summary page

    Note 

    If you think it is a little strange to use the Explore function to create an object for inventory collection, you are not alone. We think so too!

  3. Click Create a new application under the Actions heading. The Application definition: Create page is displayed, as shown in Figure 3-2.

    click to expand
    Figure 3-2: Application definition: Create page

  4. Enter the details of your application.

    1. Enter the name of your application. For this example, we use the name TEST1.

      Note 

      As you can see, we used all capital letters for the application name. We suggest that you do the same. While WSAA will let you enter mixed or lower case letters, using upper-case characters will make it easier for you to locate all of your applications and to differentiate them from other entries in the database.

    If you look back at Figure 3-1 on page 58, you see two entries for WSAARedbook. As we work with WSAA, we periodically have to remind ourselves which one to use. Avoid the confusion — use caps!

    1. Enter the full name of your application. This textual description appears on the Application summary page. For this example, we use the name Redbook Test1. In this field you can use mixed case characters.

    2. If this is a parent application, do not change the value in the Select parent application name list box. Otherwise, select the appropriate name from the list. For this example (our first), we have no parent application.

    3. Enter a full description of your application. This is a free-form text field. Each site can create the rules that govern what to enter in this field.

      Note 

      One of the things we suggest that you include in the description is the appropriate application contact (or owner) information. That way, you will know who to call for assistance if you have any problems or questions during inventory collection.

  5. Click the Create application button. The Application details: Assign components page is displayed, as shown in Figure 3-3.

    click to expand
    Figure 3-3: Application details: Assign components page

    Because you have not yet collected any inventory, the numbers next to the fields under the Component heading will be zero.

    Note 

    We developed this scenario in a WSAA database on the DemoMVS system and other groups’ components are displayed.

  6. You are finished; the application TEST1 has been entered in the database!

    Click MVS assets to return to the Explore MVS assets page.

    You can now create all of your site’s applications in a similar manner.

When you collect your inventory, you will be able to easily assign your components to these “pre-built” applications while the components are being loaded. Refer to 3.5.4, “Assign CICS components to an application” on page 77 and 3.6.1, “How to load data set resources” on page 81 for ways in which you can assign an application to components.



 < 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