4.2.1 Visual relationships

 < Day Day Up > 



As you have seen, there are three key visuals that WSAA uses to help you understand your application:

  • Impact analysis diagram

  • Graphic run-time flow

  • Program structure

We describe aspects of each in further detail in this section.

Impact analysis diagram

The impact analysis diagram is one of the more powerful displays in WSAA. In one concentrated view, you can see the number of components that are directly and indirectly affected by a change to a data element.

Figure 4-13 shows the results of our earlier search for CUST-NM. Let’s take a few moments to describe some of the key features of this image.

click to expand
Figure 4-13: Impact analysis diagram

On the left-hand side of the image, WSAA displays the Direct impacts. On the right-hand side of the image, WSAA displays the Indirect impacts. In both cases, it distinguishes between online (CICS and IMS) transactions and Batch jobs.

The Direct impacts identify the number of data elements that are affected and the number of programs that use them.

In the center of the image is the data set and data store information. In this case, the data sets are physical files; the data stores are the DD (or file) names that refer to the physical files.

The Indirect impacts also identify the number of data elements that might be affected and the number of programs that use them.

Graphic run-time flow

When you click Batch jobs, and click the link to one of them (in this case DEMOTRDB), the lower portion of the Impact analysis results: Batch job details page contains the run-time flow of the batch job. Figure 4-14 shows these results.

click to expand
Figure 4-14: Graphic run-time flow

Reading this image from left-to-right, you can see the JCL by its execution name, DEMOTRDB. This has a direct connection to the run unit (notice the icon of a jogger), TRADERB. Each of the DD names referenced by the JCL and the program are also displayed. In three cases, the physical files to which they are connected are displayed.

It is important to note that you can only click on the images that have underscores (which represent links) to obtain the corresponding Details page for the component. Not every icon in this image has a link associated with it.

Program structure

When you click TRADERB, the lower portion of the Impact analysis results: Run unit details page contains the program structure of the run unit. Figure 4-15 shows these results.

click to expand
Figure 4-15: Program structure for a run unit

Reading this image from top-to-bottom and from left-to-right, you can see the entry point for this program, TRADERB, which matches the internal name of the program. Each of the input and output files is designated, along with a call to the COBOL run-time program CEE3ABD.

As is the case with the run-time flow, you can only link to detailed information if the icon contains an underscore.



 < 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