CMS - Technology editors on Documentation - V2

CMS - Analyzing multiple C/C++ projects via a .castexedesc file

Mon, 01 Jan 0001 00:00:00 +0000

Analyzing multiple C/C++ projects via a .castexedesc file

When C/C++ projects do not have .vcproj files, the CAST Delivery Manager Tool cannot detect a project or projects and therefore no Analysis Unit will be created automatically by the CAST Management Studio when a version is set as current (see the Delivery tab in the Application editor). In this situation you will need to create an Analysis Unit manually (see the Current Version tab in the Application editor) so that the CAST Management Studio can analyze your source code.

CMS - ASP Reference Guide

Mon, 01 Jan 0001 00:00:00 +0000

Reference Guide (ASP)

This document provides some more detailed information about the objects and links that are stored in the Analysis Service. Other technical information may also be available.

Object Types

Objects detected by the analyzer are summarized in the following table:


	Analysis
	Application
	Collection
	Collection Item, Instance, Property, Variable
	Method, Sub
	Object
	Property
	Com Objects Folder
	Constant
	Folder, URL Folder, URL Group Folder
	External URL Application Folder
	File
	Class
	Event
	Function
	Property Get, Property Let, Property Put, Property Set
	Method Group, Other Group
	Global Variables Folder
	Object
	Site
	Virtual Directory

In addition, client side objects such as:

CMS - ASP Technology options

Mon, 01 Jan 0001 00:00:00 +0000

ASP Technology options

The ASP Technology editor contains various tabs. Each is explained below.

Notes

The options in this Technology editor are the default options that will be used to populate the same fields in Applications and Analysis Units. If you need to define specific options for a specific Application or Analysis Unit, then please use the Application editor (Analysis tab) or the Analysis Unit editor.
If you make a change to a specific option at Application or Analysis Unit level, and then subsequently change the same option via this editor, this setting will NOT be mirrored back to the Application or Analysis Unit - this is because specific settings at Application and Analysis Unit level have precedence if they have been changed from the default setting available in this editor.
The ASP Reference Guide contains miscellaneous technical information about the ASP analysis process.

Analysis tab

Default Source Options/File Extensions - only visible at Technology and Application level.

CMS - C/C++/Objective-C Technology options

Mon, 01 Jan 0001 00:00:00 +0000

C/C++/Objective-C Technology options

The C/C++/Objective-C Technology editor contains various tabs. Each is explained below.

Notes

The options in this Technology editor are the default options that will be used to populate the same fields in Applications and Analysis Units. If you need to define specific options for a specific Application or Analysis Unit, then please use the Application editor (Analysis tab) or the Analysis Unit editor.
If you make a change to a specific option at Application or Analysis Unit level, and then subsequently change the same option via this editor, this setting will NOT be mirrored back to the Application or Analysis Unit - this is because specific settings at Application and Analysis Unit level have precedence if they have been changed from the default setting available in this editor.
The C++ Reference Guide contains miscellaneous technical information about the C/C++ analysis process.

Analysis tab

Global settings

CMS - C++ Analyzer FAQ

Mon, 01 Jan 0001 00:00:00 +0000

C++ Analyzer FAQ

Q: Are there any limitations with virtual functions?

A: Yes, there are limitations with virtual functions. The limitation that we have is that we are not always able to know which function is called. The following example will provide a clearer understanding of what happens:

class CMother {
public:
virtual void TheFunction() { MessageBox( NULL, “CMother..”, “CMother..”, MB_OK); }
};

class CDaugther : public CMother {
public:
void TheFunction() { MessageBox( NULL, “CDaugther..”, “CDaugther..”, MB_OK); }
};

CMS - C++ Reference Guide

Mon, 01 Jan 0001 00:00:00 +0000

C++ Reference Guide

This document provides some more detailed information about the objects and links that are stored in the Analysis Service. Other technical information may also be available.

Object Types

Objects detected by the analyzer are summarized in the following table:

	Class
	Folder for Classes, Unions and Structures Dependencies Folder Globals Folder File Scope Folder
	Constructor
	Destructor
	Enum
	Enum Item
	File
	Function
	Global Variable
	Macro
	Member
	Method
	Project
	Struct
	Class Template
	Class Template Specialization
	Constructor Template
	Constructor Template Specialization
	Function Template
	Function Template Specialization
	Method Template
	Method Template Specialization
	Template Parameter
	Typedef
	Union
	CLR Event (Managed C++)
	CLR EventAddon (Managed C++)
	CLR EventRaise (Managed C++)
	CLR EventRemoveOn (Managed C++)
	CLR Property (Managed C++)
	CLR PropertyGetter (Managed C++)
	CLR PropertySetter (Managed C++)

Object modifiers (static, private, public etc.) and signatures (for functions/methods etc…) are retrieved and stored. They are also taken into account when the resolution is carried out.

CMS - Cobol Advanced Configuration via XML file

Mon, 01 Jan 0001 00:00:00 +0000

Cobol Advanced Configuration via XML file

It is possible to configure the Mainframe Analyzer (for Cobol) via an XML file (called Parametrization_Cobol.xml and located in the configuration\parametrization\cobol folder hierarchy within your CAST installation folder).

This file uses rules to indicate to the Mainframe Analyzer:

Category 1 > when to create links from subprogram calls to other objects (first category of rules)
Category 2 > when to deactivate Use links created via a grep search on literals used by specific statements (second category of rules)

The file will automatically be taken into account when the analysis is run.

CMS - Common Technology options

Mon, 01 Jan 0001 00:00:00 +0000

Common Technology options

The Common Technology editor contains various tabs. Each is explained below.

Notes

The options in this Technology editor are common to all Applications and Analysis Units

Production

Escalate Links

Activating the option will cause Escalated Links to be saved in the Analsysi Service when any analysis is run. Selecting this option can negatively impact analysis performance time, particularly when you are working with large projects - as such the option is deactivated by default.

When the option is deactivated, Escalated Links not to be saved in the Analysis Service and is the recommended setting for optimal performance.

CMS - Dependencies tab (targets)

Mon, 01 Jan 0001 00:00:00 +0000

Dependencies tab

This tab governs the default dependency Targets configured for the current Technology:

Dependency Targets are part of a wider feature called Dependency Rules - these rules are managed at Application level in the Dependencies tab. A Dependency Rule consists of a Source and a Target:

When a dependency rule exists in the Dependencies tab at Application level and during the analysis process, source code corresponding to the Technologies/Analysis Units in the Source column is scanned for references to objects in source code corresponding to the Technologies/Analysis Units in the Target column. If any matches are found, then a link between the two objects will be created (this will be visible in CAST Enlighten or in the CAST Discovery Portal).

CMS - External Files (JCL)

Mon, 01 Jan 0001 00:00:00 +0000

External Files (JCL)

The Mainframe Analyzer (for JCL) can handle programs (called by JCL Jobs) that call one or more external files. These files are declared in the DD cards that form part of the steps. They contain a DSN or DSNAME property. For each of these DD cards, the Mainframe Analyzer will create an object file (“JCL Data Set” type) sorted by an index whose path equals the DSN or DSNAME property.

CMS - JCL Advanced Configuration via XML file

Mon, 01 Jan 0001 00:00:00 +0000

JCL Advanced Configuration via XML file

It is possible to configure the Mainframe Analyzer - specifically for JCL - via an XML file. This file indicates to the Mainframe Analyzer any specific links that need to be created or any special utilities called by the JCL cards.

CAST provides a default XML configuration file called AdvancedJCL.xml which is located at the root of the CAST installation folder - this contains various generic configuration settings that may be useful. You can:

CMS - Mainframe Reference Guide

Mon, 01 Jan 0001 00:00:00 +0000

Mainframe Reference Guide

This document provides some more detailed information about the objects and links that are stored in the Analysis Service. Other technical information may also be available.

Because the Mainframe analyzer can handle Cobol, JCL, IMS and CICS, this Reference Guide will contain information valid for all languages:

Cobol Object Types

Cobol objects detected by the analyzer are summarized in the following table:


Icon	Object Type	Description
	Program	Cobol code that can be executed by a process. The program contains a “procedure division” that consists of various sections or paragraphs.
	Copy Book	File written in Cobol included in a program or another copy book. A copy book often contains declarations that are common to several Cobol programs.
	Paragraph	Piece of Cobol code located in a program. It can be executed inside a program if the resolution rules described below are respected.
	Section	Piece of Cobol code located in a program or a group of paragraphs. It can be executed inside a program if the resolution rules described below are respected.
	Division	A Program consists of several Divisions that group together specific instructions (e.g.: program identification, execution environment, data declaration, processes etc.). A division can be divided into sections (e.g.: the DATA DIVISION can contain a FILE SECTION, WORKING-STORAGE SECTION, LINKAGE SECTION etc.).
	File Link (Sequential, Partitioned, VSAM)	This a logical file specific to the program. It is used to read/write data.
	Data Link	File used to implement a sort
	Class	Cobol files containing the implementation of a class (please note that classes are detected but not analyzed).
	Directory/Root Directory	Folder/directory located on the hard driver containing the analyzed files.
	Entry Point	Entry point for executing Cobol programs
	Interface	Cobol files containing the implementation of an interface.
	Program Specification Block	PSB specifications for handling IMS databases
	Database Definition	IMS database for mainframe
	IMS Segment	Segments for an IMS database

Cobol conditional test	Conditional values of a field in a Cobol variable
	Cobol data	Field in a Cobol variable
	Cobol literal	Literal
Cobol structure data	Structure data containing several fields
Cobol constant data	Constant data
	External File	CICS files not resolved
	Transaction	CICS Transaction not resolved
	Screen Map	CICS Screen Map not resolved
	Transient Data	CICS TD Queue not resolved
	Project	Top level item

JCL Object Types

JCL objects detected by the analyzer are summarized in the following table:

CMS - Mainframe Technology options

Mon, 01 Jan 0001 00:00:00 +0000

Mainframe Technology options

The Mainframe Technology editor contains various tabs. Each is explained below.

Notes

The options in this Technology editor are the default options that will be used to populate the same fields in Applications and Analysis Units. If you need to define specific options for a specific Application or Analysis Unit, then please use the Application editor (Analysis tab) or the Analysis Unit editor.
If you make a change to a specific option at Application or Analysis Unit level, and then subsequently change the same option via this editor, this setting will NOT be mirrored back to the Application or Analysis Unit - this is because specific settings at Application and Analysis Unit level have precedence if they have been changed from the default setting available in this editor.
The Mainframe Reference Guide contains miscellaneous technical information about the Mainframe analysis process.

Analysis tab

Default Source Options/File Extensions - only visible at Technology and Application level.

CMS - MS SQL Server / Sybase Reference Guide

Mon, 01 Jan 0001 00:00:00 +0000

MS SQL Server / Sybase Reference Guide

This document provides some more detailed information about the objects and links that are stored in the Analysis Service. Other technical information may also be available.

Object Types

Objects detected by the analyzer are summarized in the following table:


Object	Name
	Instance
	Database
	Schema
	Trigger
	Function
	Procedure
	Table
	View
	Table Column / View Column
	Index, Foreign Key Constraint, Primary Key Constraint, Unique Constraint

Note that Synonyms are not supported: any reference to a synonym is silently ignored by the analyzer (no message issued).

CMS - MS SQL Server /Sybase Technology options

Mon, 01 Jan 0001 00:00:00 +0000

MS SQL Server / Sybase Technology options

The MS SQL Server /Sybase Technology editor contains various tabs. Each is explained below.

Notes

There is a dedicated Technology editor for MS SQL Server and one for Sybase ASE, however, their options are identical and are therefore described here in one page.
The options in this Technology editor are the default options that will be used to populate the same fields in Applications and Analysis Units. If you need to define specific options for a specific Application or Analysis Unit, then please use the Application editor (Analysis tab) or the Analysis Unit editor.
If you make a change to a specific option at Application or Analysis Unit level, and then subsequently change the same option via this editor, this setting will NOT be mirrored back to the Application or Analysis Unit - this is because specific settings at Application and Analysis Unit level have precedence if they have been changed from the default setting available in this editor.

Production tab

Process Settings - Inference Engine

CMS - Oracle Forms and Reports Technology options

Mon, 01 Jan 0001 00:00:00 +0000

Oracle Forms and Reports Technology options

The Forms Technology editor contains various tabs. Each is explained below.

Notes

The options in this Technology editor are the default options that will be used to populate the same fields in Applications and Analysis Units. If you need to define specific options for a specific Application or Analysis Unit, then please use the Application editor (Analysis tab) or the Analysis Unit editor.
If you make a change to a specific option at Application or Analysis Unit level, and then subsequently change the same option via this editor, this setting will NOT be mirrored back to the Application or Analysis Unit - this is because specific settings at Application and Analysis Unit level have precedence if they have been changed from the default setting available in this editor.

Analysis tab

Directory for Code Viewer files

If you would like to be able to view the source code of your Forms/Reports analyses in CAST Enlighten, the CAST Discovery Portal or the CAST Engineering Dashboard, then you need to configure this option: enter a full path to a local or network folder. During the analysis, the Forms analyzer will create the files in the selected folder necessary for source code to be viewed by the CAST applications listed above. A sub-folder will be created for each analysed Application that contains Forms/Reports Analysis Units.

Note the following:

CMS - Oracle Forms Reference Guide

Mon, 01 Jan 0001 00:00:00 +0000

Oracle Forms Reference Guide

This document provides some more detailed information about the objects and links that are stored in the Analysis Service. Other technical information may also be available.

Analysis Unit types
Object types
Link types

Analysis Unit types

The following Analysis Units will be created after deploying and using the set as current version option:

One FORMS Analysis Unit (pointing to .uaxdirectory file) for each:

.fmb
.olb
.mmb
.pll

One Oracle Reports Analysis Unit (pointing to .rex file) for each

CMS - PL/SQL Reference Guide

Mon, 01 Jan 0001 00:00:00 +0000

PL/SQL Reference Guide

This document provides some more detailed information about the objects and links that are stored in the Analysis Service. Other technical information may also be available.

Object Types

Objects detected by the analyzer are summarized in the following table:


Icon	Object Type	Parent Object
	Collection Nested Table Type	Schema
	Collection Varray	Schema
	Cursor	Package Header
	Database Link	Schema
	Function	Schema, Package
	Function (Private)	Function
	Instance	-
	Index, Foreign Key Constraint, Primary Key Constraint, Check Constraint and Unique Key Constraint	Schema
	Object Type (Incomplete, Body and Header)	Schema
	Package Body	Schema
	Package Header	Schema
	Procedure	Schema, Package
	Procedure (Private)	Procedure
	Schema	Instance
	Schema (Unknown)	Instance
	Sequence	Schema
	Synonym (Public/Private)	Schema
	Oracle Table	Schema
	Oracle Table Column	Table
	Trigger	Schema
	Unknown Object	Schema
	View (Normal and Materialized)	Schema
	View Column	View

Object Properties

All object properties that are supported by the current release of the SQL Analyzer are described in the following table:

CMS - PL/SQL Technology options

Mon, 01 Jan 0001 00:00:00 +0000

PL/SQL Technology options

The PL/SQL Technology editor contains various tabs. Each is explained below.

Notes

The options in this Technology editor are the default options that will be used to populate the same fields in Applications and Analysis Units. If you need to define specific options for a specific Application or Analysis Unit, then please use the Application editor (Analysis tab) or the Analysis Unit editor.
If you make a change to a specific option at Application or Analysis Unit level, and then subsequently change the same option via this editor, this setting will NOT be mirrored back to the Application or Analysis Unit - this is because specific settings at Application and Analysis Unit level have precedence if they have been changed from the default setting available in this editor.
The PL/SQL Reference Guide contains miscellaneous technical information about the PL/SQL analysis process.

Production tab

The Production tab is only visible at Technology and Application level.

CMS - PowerBuilder Reference Guide

Mon, 01 Jan 0001 00:00:00 +0000

PowerBuilder Reference Guide

This document provides some more detailed information about the objects and links that are stored in the Analysis Service. Other technical information may also be available.

Object Types
Link Types
Dynamic Links found by the analyzer (inference engine)
Calling PB system functions

Object Types

Objects detected by the analyzer are summarized in the following table:

PB Program/Analysis

PB Library

- PB Program

PB Window

- PB PBL

PB User Object

- PB PBL

PB DataStore

- PB PBL

PB DataWindow

- PB PBL

PB Structure (Global)

- PB PBL

PB Menu

- PB PBL

PB Application

- PB PBL

PB Function Global

- PB PBL

PB Control

- PB Window

- PB User Object

CMS - PowerBuilder Technology options

Mon, 01 Jan 0001 00:00:00 +0000

PowerBuilder Technology options

The PowerBuilder Technology editor contains various tabs. Each is explained below.

Notes

The options in this Technology editor are the default options that will be used to populate the same fields in Applications and Analysis Units. If you need to define specific options for a specific Application or Analysis Unit, then please use the Application editor (Analysis tab) or the Analysis Unit editor.
If you make a change to a specific option at Application or Analysis Unit level, and then subsequently change the same option via this editor, this setting will NOT be mirrored back to the Application or Analysis Unit - this is because specific settings at Application and Analysis Unit level have precedence if they have been changed from the default setting available in this editor.

Analysis tab

Dashes in identifiers allowed

This option is identical to the PowerBuilder option of the same name.

Activating this option (the option is activated by default) will force the analyzer to take into account code that includes dashes in identifiers. For example:

CMS - Reference Pattern tab

Mon, 01 Jan 0001 00:00:00 +0000

Reference Pattern tab

The Reference Pattern tab enables you to create a Reference Pattern to search for links (i.e. a word, series of words or string (based on Regular Expressions)) between Source and Target code. Reference Patterns are an extension of the Dependency Rules feature managed in the Dependencies tab in the Application editor.

Reference Patterns are particularly useful when standard Dependency Rules based solely on simple word based matches between Technologies or Analysis Units are either too broad (creating too many “false” links between objects) or do not detect the links you require. Since Reference Patterns are based on Regular Expressions, you can define very specific search strings to identify the links between source code that you require.

CMS - SAP/ABAP Reference Guide

Mon, 01 Jan 0001 00:00:00 +0000

SAP/ABAP Reference Guide

This document provides some more detailed information about the objects and links that are stored in the Analysis Service. Other technical information may also be available.

Object Types

Objects detected by the analyzer are summarized in the following table:

Project Items


	ABAP Project

ABAP Objects


	ABAP Alias
	ABAP Badi
	ABAP Class
	ABAP Class Pool
	ABAP Constructor
	ABAP Event
	ABAP Event Block
	ABAP Event Method
	ABAP File Level Code
	ABAP Flow Logic File
	ABAP Form
	ABAP Function
	ABAP Function Pool
	ABAP Include
	ABAP Interface
	ABAP Interface Pool
	ABAP Macro
	ABAP Member
	ABAP Method
	ABAP Module
	ABAP Module Pool
	ABAP Package
	ABAP Program
	ABAP Type Pool
	ABAP Unresolved Folder
	ABAP Unresolved Object
	ABAP User Exit

SAP objects, Processing Screens & Selection Screens

CMS - SAP Technology options

Mon, 01 Jan 0001 00:00:00 +0000

SAP Technology options

The SAP Technology editor contains various tabs. Each is explained below.

Notes

The options in this Technology editor are the default options that will be used to populate the same fields in Applications and Analysis Units. If you need to define specific options for a specific Application or Analysis Unit, then please use the Application editor (Analysis tab) or the Analysis Unit editor.
If you make a change to a specific option at Application or Analysis Unit level, and then subsequently change the same option via this editor, this setting will NOT be mirrored back to the Application or Analysis Unit - this is because specific settings at Application and Analysis Unit level have precedence if they have been changed from the default setting available in this editor.
The SAP/ABAP Reference Guide contains miscellaneous technical information about the SAP/ABAP analysis process.

Analysis tab

This tab is only visible at Application and Analysis Unit level.

CMS - Universal Technology options

Mon, 01 Jan 0001 00:00:00 +0000

Universal Technology options

The Universal Technology editor contains various tabs. Each is explained below.

Notes

The options in this Technology editor are the default options that will be used to populate the same fields in Applications and Analysis Units. If you need to define specific options for a specific Application or Analysis Unit, then please use the Application editor (Analysis tab) or the Analysis Unit editor.
If you make a change to a specific option at Application or Analysis Unit level, and then subsequently change the same option via this editor, this setting will NOT be mirrored back to the Application or Analysis Unit - this is because specific settings at Application and Analysis Unit level have precedence if they have been changed from the default setting available in this editor.

Production tab

Process Settings

CMS - VB Reference Guide

Mon, 01 Jan 0001 00:00:00 +0000

VB Reference Guide

This document provides some more detailed information about the objects and links that are stored in the Analysis Service. Other technical information may also be available.

Object Types

Objects detected by the analyzer are summarized in the following table:

	Class Module
	Constant
	Control
	Designer
	Event
	External Function
	External Sub
	Form
	Function
	MDI Form
	Module
	Control Project
	EXE Project
	Group Project
	OLE DLL Project
	OLE Exe Project
	Get Property
	Let Property
	Page Property
	Set property
	Sub
	User Control
	User Document
	Variable
	Com CoCLass
	Com Disp Interface Com Interface
	Com Method Com Property Com Get Property Com Put Property Com Put Ref Property
	Com Type Lib Com External Type Lib

Link Types

The following table describes references that are detected by the analyzer and the context in which corresponding links are traced and stored in the Analysis Service:

CMS - Visual Basic Technology options

Mon, 01 Jan 0001 00:00:00 +0000

Visual Basic Technology options

The Visual Basic Technology editor contains various tabs. Each is explained below.

Notes

The options in this Technology editor are the default options that will be used to populate the same fields in Applications and Analysis Units. If you need to define specific options for a specific Application or Analysis Unit, then please use the Application editor (Analysis tab) or the Analysis Unit editor.
If you make a change to a specific option at Application or Analysis Unit level, and then subsequently change the same option via this editor, this setting will NOT be mirrored back to the Application or Analysis Unit - this is because specific settings at Application and Analysis Unit level have precedence if they have been changed from the default setting available in this editor.
The VB Reference Guide contains miscellaneous technical information about the VB analysis process.
See also the Web Services (VB) Reference Guide.

Analysis tab


Compare references by filename	If you select this option, the analyzer will compare ActiveX references in the .VBP file using the filename only. If the option is left blank, references are compared using the full path instead.
Default Handling	During the analysis, when this option is selected, the analyzer will take into account predefined constants and any #Const directives contained in the project.

Custom Environment Profiles - only visible at Application and Analysis Unit level

CMS - Web Services (VB) Reference Guide

Mon, 01 Jan 0001 00:00:00 +0000

Web Services (VB) Reference Guide

This document provides some more detailed information about the objects and links that are stored in the Analysis Service. Other technical information may also be available.

How does CAST handle Web Services?

CAST supports those implementing Web Services throughout their set of applications via as follows:

Store (in the Analysis Service) objects that represent the description of Web Services using only the contents of WSDL files.