Viewing the Program Summary
When you open a program in the Workbench COBOL Editor or Workbench PL/I Editor and the Code Insights perspective, the program is parsed and analyzed to build the program structure chart and provide in-depth information about the program. The Code Insights perspective includes a Program Summary view that provides valuable information about the program being charted. The Files Defined, Files Opened, and Files Used values can be expanded to list the associated DD names. The DB2 Tables Defined and DB2 Tables Used values can be expanded to list the associated DB2 tables. Differences can help identify files and tables that are defined but never used. The Maintenance Effort can be expanded to list the associated maintenance effort factors.
The two columns of the Program Summary view, Measurement and Value, contain the following data:
Measurement | Value |
|---|---|
Lines of Code | The total number of source lines in the program (excluding blank lines). |
Comment Lines | The total number of commented lines in the program (excluding lines that contain executable code and a comment). |
Statements | The number of executable lines of code in the program. |
Files Defined | The number of files that are defined in the program. This field can be expanded to list the DD names defined. |
Files Opened | The number of files that are opened in the program. This field can be expanded to list DD names opened. |
Files Used | The number of files that are used in a Read or Write statement. This field can be expanded to list DD names used. |
DB2 Tables Defined | The number of DB2 Tables that are defined in the program. This field can be expanded to list the DB2 tables defined. |
DB2 Tables Used | The number of DB2 Tables that are used in an SQL statement within the program logic. This field can be expanded to list the DB2 tables used. |
Maintenance Effort | A measure of the effort required to maintain the program, based on program clarity, computed as the ratio of volume to level. The lower the number, the easier the program will be to maintain. This is a relative number that can be compared to other programs to determine the maintenance effort for various programs. |
Unique Operators [n1] | The unique number of verbs and elements other than data elements occurring in your program. Operators are syntactic elements such as +, -, <, >. |
Unique Operands [n2] | The unique number of data elements referenced in your program. Each data element is only counted the first time it is referenced. Operands consist of literal expressions, constants, and variables. This is not a count of all data elements defined, but those that are actually used in the program. |
Total Operators [N1] | The total number of verbs and elements other than data elements occurring in your program. Paired operators such as BEGIN .. END, DO .. UNTIL , FOR .. NEXT are treated as a single operator. |
Total Operands [N2] | The total number of data elements occurring in your program. Each time the data element is referenced it is added to this count. Operands consist of literal expressions, constants, and variables. This is not a count of all data elements defined, but those that are actually used in the program. |
Vocabulary | The number of unique operators and operands in your program, n, computed n1+n2. This is an estimation of the size of the program's vocabulary (the number of things that must be known to understand the program). |
Length | The length of your program, N, computed N1+N2. |
Computed Length | A prediction of program length, N^, computed n1log2n1+n2log2n2. It has been experimentally observed that computed length is in close agreement to program length. |
Volume | A measure of the size of a piece of code (computed Nlog2n) compared to potential volume (n*log2n*), where n* is the size of potential vocabulary. (Potential volume is independent of the language.) |
Level | The ratio of potential volume to actual volume, a measure of how abstractly the program is written. |
Intelligence Content | The total content of your program, computed by multiplying program level and volume. It is shows the complexity of a given algorithm independent of the language used to express the algorithm. |
For more information, see: