3.2 Identify your production source components

 < Day Day Up > 



To load the WSAA database, you need to know the names of the data sets that contain your site’s production source components.

Tip 

We recommend that you consult with your Change Management or Quality Assurance group manager to obtain a list of the current production libraries your site uses. We described some of the support they can provide you in Chapter 2, “Roles and responsibilities” on page 35.

When you perform this activity, you have four goals:

  1. You must identify the names of the source code libraries that hold both main and subordinate (or included) components.

  2. You must identify the specific applications that own (or use) the components.

  3. You must identify the concatenation order of the subordinate components.

  4. You must identify the various online components that your site uses.

We explain the details of each of these in the following sections.

3.2.1 Identify source code libraries

If you are going to load a database with all of the production source code your site has, you really need to make sure that you know what you are dealing with. You must have a complete list that contains the production data set names of the following items:

  • Source code, including:

  • COBOL

  • PL/I

  • Assembler

  • Copybooks

  • Macros

  • DCLGENs

  • JCL

  • Procs

  • Control cards

As you can see, this list contains both main program types and their various subordinate components. Many of your source code members will undoubtedly reference components in other libraries. For example, a JCL member can reference an external proc in one of its EXEC statements, a COBOL member will use a COPY statement to include source from another library, and an Assembler member can invoke a macro stored in a MACLIB.

This concept is carried over into the database, because WSAA also delineates between main and subordinate programs and internally maintains a hierarchical structure. The search order of the data sets containing subordinate components is used by WSAA in a similar manner. WSAA refers to this search order as a “concatenation set.” Refer to 3.4, “What is a concatenation set?” on page 62 for additional information.

Simply put, a concatenation set is a list of data sets, similar to those used in a SYSLIB DD in a batch compile or the ones specified in the ORDER parameter of a JCLLIB statement. In each instance, the members are scanned — in order — from the first library to the last library.

Source library checklist

Table 3-1 contains a generic framework of a checklist that you can use to obtain your site’s production data set names. Create one sheet for each language. Don’t forget to list the various system-level product libraries for your copybooks and macros!

Table 3-1: Generic data set information collection checklist

LANGUAGE: ______________________ (specify each language used)

Data set name

Main or Include

Application name

Notes® or comments

    
    
    
    
    
    
    
    
    
    

3.2.2 Identify your site’s applications

In addition to obtaining all of your site’s source data set names, you also need to keep in mind the corporate entities that own (or use) these data sets. Typically, you will need to identify various applications or components based on a local naming convention or standard.

Some sites may have one production source library in which all application code is placed. If that is the case in your shop, you will need to determine if there is a member naming standard that you can use to discern who owns what. Some library members may be shared across (or may be common to) multiple applications. You may need to implement a unique naming convention to support these components.

Some sites may have multiple production source libraries; one for each major application. If that is the case in your shop, you can more easily identify ownership.

Note 

If you have application development managers and programmers who require the ability to see their components to the exclusion of any others, you must create applications.

We describe how to tell WSAA about applications in 3.3, “When do I use an application?” on page 57.

Application checklist

Table 3-2 contains a generic framework of a checklist that you can use to obtain your site’s application names.

Table 3-2: Generic application information collection checklist

Application name

Mnemonic

Contact name

Contact phone

    
    
    
    
    
    
    
    
    
    

3.2.3 Identify concatenation libraries

While obtaining the source data set names is your primary concern, you also need to carefully review your site’s production compile procedures. These are probably located either in system programmer controlled libraries or within your software change management (SCM) system, for example, SCLM or ChangeMan. From these compile procedures, you must obtain the list of data sets used in the SYSLIB concatenation in the various compile steps.

You also need to review the search order your job scheduling system uses for your site’s proc libraries. If your JCL references procs from multiple libraries, you must establish a similar search sequence for WSAA to use. We recommend that you consult with your Scheduling group and the MVS systems programmer responsible for maintaining the scheduling software to obtain the order of the production proc libraries your site uses.

Tip 

When you collect the source data set information, use the “Notes or comments” field to indicate the approximate concatenation sequence. That may make it easier for you to validate your findings when you review the compiler SYSLIB and proc search order information.

We describe more about analysis concatenation sets in 3.4, “What is a concatenation set?” on page 62.

3.2.4 Identify online components

With WSAA you can scan the resources of your CICS and IMS regions and subsystems. Before you do so, you must identify the appropriate resources.

CICS

For CICS you must identify the names of your site’s production regions and the file name for each region’s CICS system definition (CSD) file. You should also determine the location of the start-up JCL (if any) and proc for the regions.

IMS

For IMS, you must identify the names of your site’s production IMS subsystems. You can analyze data sets, transactions, and control blocks (program specification blocks (PSBs), database descriptions (DBDs), and application control blocks (ACBs)) to obtain information about IMS components.

Note 

We did not work with IMS components during our residency. We focused our attention primarily on batch and CICS components.

We recommend that you consult with your CICS or IMS systems programmer (and possibly the Change Management or Quality Assurance groups) for the appropriate information.



 < 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