Scanning source code

You can take an inventory of the following types of non-binary source:

• COBOL
• PL/I
• Assembler
• JCL
• DBD
• PSB
• BMS

On z/OS® this source can reside in a variety of containers:

• As files in PDS/PDSE libraries
• As source in SCM containers, such as IBM® SCLM.  

Any file with an unsupported language type is marked with a type of UNK.

During the inventory process, Rational Asset Analyzer performs three tasks, as follows:

• Identification: It scans the assets in the containers that you specify and identifies what assets are there. 
• Classification: It classifies what the files are. Thus it determines the language type, line counts, and other characteristics. This phase of inventory also determines whether the files are main files: that is, whether they reference other source (for example, with COPY or INCLUDE statements), contain DLI calls or preprocessor statements (such as EXEC CICS®, EXEC SQL, or EXEC DLI), or contain calls to WebSphere® MQ APIs.

  This initial inventory looks only at the files in the container that you specify, and not at any files that those files reference. However, the phase does store the names of included copy files.

  If the source contains unsupported code as described in Interpreting the results of inventory, then Rational Asset Analyzer does not classify the file and marks the file with a type of UNK.

• Analysis: It determines what the members contain. This phase involves main files and the source that they reference. This phase extracts details about data declarations, statements, calls, entry points, files, databases, data stores, and literals.

Scanning source code consists of some or all of the following tasks. Although the source code that is operated upon is on the host, you perform the following tasks from the browser interface.