Page tree
Skip to end of metadata
Go to start of metadata

Summary: This page explains how to prepare and configure the analysis of your Shell source code.

Source code requirements 

Only files with following extensions will be analyzed:

  • *.ksh
  • *.sh
  • *.ssh
  • *.csh
  • *.bsh
  • *.shell

Note that if any files intended for other applications are included in the delivery and which are renamed to supported Shell extensions, the following effects might be observed during an analysis:

  • inconsistent objects may get created
  • end of string ''' not found errors
  • if the file is binary: Invalid UTF-8 sequence found in text to be matched or searched for a regular expression

Source code preprocessing 

Shell source code needs to be preprocessed so that CAST can understand it and analyze it correctly. In previous releases of the extension, this preprocessing was a manual action that needed to be completed before the code was analyzed. However, in this release and all future releases, the code preprocessing is actioned automatically when an analysis is launched or a snapshot is generated (the code is preprocessed before the analysis starts). In other words you only need to package, deliver and launch an analysis/generate a snapshot for the preprocessing to be completed.

Note that the CAST Management Studio will use the LISA folder (see CAST Management Studio help for more information about this folder).


Versions 1.0.5 and above of the Shell extension requires a JAVA_HOME system environment variable to be present on the machine pointing to an installation of Java JRE 1.7, so that the preprocessor can run. See Prerequisites for more information.

Application Source Code Delivery and Snapshot generation 

When delivering your source code for analysis with CAST, you need to follow the same process as for technologies that are supported by CAST "out of the box". In other words:

Logging mechanism

Analysis log files

Analysis logs are stored in the default locations used by the CAST Management Studio.

Shell Preprocessor

Shell Preprocessor log files (the preprocessor is launched automatically during an analysis) are stored in the following locations:

CAST AIP releaseLocationLog file name


Note that the above location is the default, however, if you have modified the CAST_PLUGINS_ROOT_PATH variable in the CastGlobalSettings.ini file, this location may be different.<MAJOR_VERSION.MINOR_VERSION.MAINTENANCE_VERSION>.prepro_<YYYYMMDDHHMMSS>.log
8.3.xDefault location is set to %PROGRAMDATA%\CAST\CAST\Logs\<unique_application_id>\, but this location can be configured at will in the CAST Management Studio Preferences.

  • No labels