What are the meanings of the attributes found in the IBM Rational Team Concert (RTC) Source Data Control Query section for Enterprise Extensions?
When creating a Source Code Data Query to be used to find source or to run with dependency builds, definitions for the attributes help to understand what are valid entries.
Below includes the options for the dependency build attributes and their definitions:
The file type of the source file, such as MAIN, INCL, MAP, etc
The logical name of the source file if it is an INCL file; otherwise NULL
The dependency's path. For zOS files, this is the DD Name
The dependency's reference type, such as COPY, SQL INCLUDE, MACRO, etc.
The dependency's file type, such as INCL, PROC, PSB (program specification block), etc.
The programming language of the source file, such as COB, PLI, etc.
The dependency's logical name. This will be matched to the logicalName of an INCL file.
This section includes the z/os default scanner attributes and definitions:
Number of blank lines in the source file
Number of comments in the source file
Number of DATA DIVISIONs in the source file (COBOL)
Number of Mapset definitions such as for BMS (basic mapping support) definition files
Number of entry points in the source file (uses ENTRY keyword)
Number of ENVIRONMENT DIVISIONs in the source file (COBOL)
Number of EXEC CICS statements in the source file
Number of EXEC SQL statements in the source file
Number of IDENTIFICATION DIVISIONs in the source file (COBOL)
Number of lines in the source file that are not comment lines
Number of PROCEDURE DIVISIONs in the source file (COBOL)
Total number of lines (records) in the source file
Number of splitting nodes in the source file (a splitting node is a branch point with more than one path leading to other nodes, a nonsplitting node has just one path leading to another node).
The filePath and fileName SCM attributes are self-explanatory.