Getting Started with Code Insights
This topic will help you prepare to start using Code Insights.
To use Code Insights for mainframe data, you must define an HCI host connection and connect Workbench for Eclipse or Eclipse/RDz to a mainframe system. To define your connection, click Window > Preferences. Then expand BMC > Host Connections and add an HCI host connection before continuing.
A host connection between the mainframe host and Workbench should have already been defined during the installation and configuration of Workbench for Eclipse. If you do not have host connection information (typically a port number and a hostname), contact your system administrator to obtain specific connection configurations for your site for establishing Host Connections. For system administrators, see the BMC-AMI-DevX-Workbench-for-Eclipse-Installation-Guide for additional information on installing Workbench for Eclipse.
To enable Code Insights, you must also set the URL for BMC AMI Common Enterprise Services. For more information, see the Installing.
Usage restrictions
All Languages
Code Insights does not support DBCS, the pound sterling character in 1004, Desktop Publishing code page, or 852, Latin Multi-Lingual code page.
COBOL
- Nested programs are not supported. Only the first program is analyzed.
- Report Writer syntax is not supported.
- Object-oriented COBOL is not supported, only tolerated.
- Code Insights does not support the omission of the PROCEDURE DIVISION header or label.
PL/I
- PL/I programs containing preprocessor directives other than the following must have the directives resolved before they can be analyzed:
- %INCLUDE
- %NOPRINT
- %SKIP
- %PROCESS
- The following are supported:
- %IF/%ELSE statements
- %DO blocks (including loops)
- %INCLUDE
- Assignment statements
- %ACTIVATE / %DEACTIVATE
- %DECLARE
- Procedures that return a value
- GOTO (within procedures)
- The following built-in functions are supported:
- NOTE (within procedures)
- LENGTH
- INDEX
- SUBSTR
- PARMSET (within procedures)
- Partial support is provided for the following:
- Typed variables. (In many cases variables are treated as strings and converted to numbers as needed.)
- Procedure calls using named parameters.
- The following are not supported:
- Use of compile options RULES(LAXPUNC), BLANK, and NAMES
- Alternate Include processor IDs specified via the PP(INCLUDE(ID(“..”)) compile option
- Multiple level zero procedures (Likewise, statements outside the level zero procedure are ignored.)
- %ACTIVATE / %DEACTIVATE for procedures (Once defined a procedure is always active.)
- Calls to procedures without specifying parenthesis (no parameters)
- Calls made to a procedure before that procedure is declared.
- The EBCDIC/ASCII host code page should be used when downloading or file transferring PL/I programs; otherwise, some PL/I-specific characters may be translated incorrectly.
- Every statement within a PL/I program must be terminated by a semicolon.
- Label variables are not supported on GOTO statements, only tolerated.
For more information, see: