CMS - .NET Environment Profiles

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

.NET Environment Profiles

All discussion about custom .NET Environment Profiles can be found in doc.castsoftware.com, in the documentation provided for the .NET Analyzer extension.

CMS - C++ Environment Profiles

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

C++ Environment Profiles

A C++ Environment Profiles provide the means to configure two specific C++ analysis variables:

Include Paths > configure additional paths for files that have been specified in the #include part of your project files. This is to ensure the correct resolution of links to files located in other directories.

The analyzer will take into account the two “include” styles:
- #include “fileA.h”
- #include <fileB.h>
Include Paths can also be administered using the Include option (see C++ Technology editor). Include Paths defined in an Environment Profile will be processed AFTER any definitions made using the Include option.

CMS - EJB Environment Profiles

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

EJB Environment Profiles

Although it is still possible to create custom EJB Environment Profiles, it is no longer possible to attach them to an analysis, therefore they are redundant and will be removed in a future release.

CMS - Environment Profile details

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

Environment Profile details

This section provides more details about the CAST Predefined Environment Profiles:

C/C++


Profile	Content	Limitation	Prerequisite	Comments
Linux-2.6.17	Based on Ubuntu distribution of Linux 2.6.17	-	-	Should function for most Linux programs
Microsoft Managed C++	Microsoft Managed C++ extensions targeted at the Common Language Runtime (CLR).	-	-	-
Solaris 10 gcc 3.4.6 intel (Macros only)	-	-	-	-
STL for Unix	Coontains a basic emulation of the most common STL headers (i.e. , , etc.).	-	-	If STL header files are not available in your source code, select this profile. This will then force the CAST Management Studio to activate a basic (i.e. non exhaustive) emulation of the most common STL headers thus avoiding an incomplete analysis or ambiguous/erroneous analysis results in most circumstances.
VC++ XXX - Console	Based on the headers of version XXX (6.0, 2003, 2005, 2008, 2010 or 2012) of Microsoft Visual C++.	-	-	Additional items for specific console projects. This profile must be used in addition to the Mandatory Part Profile for the same version of Visual C++.
VC++ XXX - Mandatory Part	Based on the headers of version XXX (6.0, 2003, 2005, 2008, 2010 or 2012) of Microsoft Visual C++.	-	-	The relevant profile version is always selected during an analysis.
VC++ XXX - WIN32/MFC	Based on the headers of version XXX (6.0, 2003, 2005, 2008, 2010 or 2012) of Microsoft Visual C++.	-	-	Additional items for specific Windows (GUI) using MFC projects. This profile must be used in addition to the Mandatory Part Profile for the same version of Visual C++.

J2EE

Profile

Content

Limitation

Prerequisite

Comments

CICS Calls

Parameterization for cicseci-6.1.0.1.jar and ctgclient-6.1.0.1.jar in CICS archives.

This profile is required when you have CICS calls.

CMS - Importing/Exporting Environment Profiles

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

Importing/Exporting Environment Profiles

CAST provides a mechanism to import and export your user-defined “custom” Environment Profiles (it is not possible to export profiles created automatically by CAST).

Exporting Environment Profiles to file

To export your user-defined Environment Profiles, you need to:

Right click the Analysis Service in the Services view and select Environment Profile > Export
The following dialog box is displayed:

Yes

Choosing Yes allows you to select a folder where each individual environment profile will be saved in separate .aex files (i.e. fragments) within a folder specific to the type of environment profile:

CMS - J2EE Environment Profiles

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

J2EE Environment Profiles

All discussion about custom JEE Environment Profiles can be found in doc.castsoftware.com, in the documentation provided for the JEE Analyzer extension.

CMS - Mainframe Environment Profiles

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

Mainframe Environment Profiles

A Mainframe Environment Profile provides the means to configure:

Working Folders > a list of folders that will be searched in order to resolve Copybook links, Cobol program links, catalogued procedure links and include file links.

Working Folders can also be administered on an individual job basis at Analysis Unit level.

Creating a profile

After clicking the icon next to Mainframe Environment Profile, a new screen will be displayed enabling you to define a name for the profile and define your working folders.

CMS - Parametrization Environment Profiles (J2EE / VB)

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

Parametrization Environment Profiles (J2EE / VB)

When creating custom Environment Profiles for the J2EE and VB technologies, it is possible to define Method Parametrization so that analyzers can correctly identify links that are defined via custom methods:

You can either import existing Java/VB methods from the CAST Analysis Service (results from previous J2EE/VB analyses that have already been run) or add new custom Java methods or VB methods that cannot be imported as they do not form part of an existing analysis stored in the CAST Analysis Service. You then need to define your parametrization - i.e. the action that the analyzer needs to undertake when the method in question is encountered during an analysis.

CMS - VB Environment Profiles

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

VB Environment Profiles

A VB Environment Profile provides the means to configure:

Parametrization > For defining Method Parametrization

Notes

Please note that a selection of pre-defined profiles are available. These cannot be modified.

Creating a profile

After clicking the icon next to VB Environment Profile, a new screen will be displayed enabling you to define a name for the profile and define Parametrization.

Parametrization

Enter a name for the Environment Profile. Choose a name that is easily recognizable as this name will be displayed in the left hand collapsible list and will be used when you add the Environment Profile at Application or Analysis Unit level.

The Parametrization tab enables you to define Method Parametrization for your VB jobs so that analyzers can correctly identify links that are created with custom methods.

CMS - WSDL Environment Profiles

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

WSDL Environment Profiles

Although it is still possible to create custom WSDL Environment Profiles, it is no longer possible to attach them to an analysis, therefore they are redundant and will be removed in a future release.

CMS - Using the Environment Profile Manager on Documentation - V2

CMS - .NET Environment Profiles

.NET Environment Profiles

CMS - C++ Environment Profiles

C++ Environment Profiles

CMS - EJB Environment Profiles

EJB Environment Profiles

CMS - Environment Profile details

Environment Profile details

C/C++

J2EE

CMS - Importing/Exporting Environment Profiles

Importing/Exporting Environment Profiles

Exporting Environment Profiles to file

CMS - J2EE Environment Profiles

J2EE Environment Profiles

CMS - Mainframe Environment Profiles

Mainframe Environment Profiles

Creating a profile

CMS - Parametrization Environment Profiles (J2EE / VB)

Parametrization Environment Profiles (J2EE / VB)

CMS - VB Environment Profiles

VB Environment Profiles

Creating a profile

Parametrization

CMS - WSDL Environment Profiles

WSDL Environment Profiles