| Option | Source File | Description |
|---|---|---|
| AIM/DB Environment | COBOL | Specifies how the parser treats AIM/DB-environment-related code or its absence. |
| C/C++ Parser Parameters | C, C++ | Specifies the parameters used to compile the application. |
| CAP Processor predefined variables | Netron Specification Frame | Specifies the values of predefined environment variables the parser uses to compile Netron Specification Frames. Select each predefined variable you want the parser to recognize, then enter its value. Add variables as necessary. |
| CICS Environment | Assembler, COBOL, PL/I | Specifies how the parser treats CICS-environment-related code or its absence. |
| Compiler Directives | COBOL | Specifies directives to be used during compilation. To add a directive, select
Use project-specific compiler directives, then right-click in the Compiler Directives field and select
Add from the context menu. The format is:
<directive>="<value>".
Using the context menu you can also delete, edit, select, unselect, move up/down the directives. Note: Project-level compiler directives override workspace-level directives.
|
| Context-Sensitive Value Analysis | COBOL | Specifies that the parser perform context-sensitive automatic decision resolution for Unisys MCP COMS analysis. Choosing this option may degrade verification performance. |
| Dialect Specific Options | COBOL | Specifies dialect-specific options, including the conditional constants the parser uses to compile programs in the project. Select the Cobol dialect, then choose the constant in the Macro Settings pane. Add constants as necessary. |
| DMS Environment | COBOL | Specifies how the parser treats DMS-environment-related code or its absence. |
| DMSII Environment | COBOL | Specifies how the parser treats DMSII-environment-related code or its absence. |
| DPS routines may end with error | COBOL | Specifies that the parser perform call analysis of Unisys 2200 DPS routines that end in an error. Error-handling code for these routines is either analyzed or treated as dead code. |
| Enable Data Element Flow | COBOL, Natural, PL/I, RPG | Enables the Global Data Flow, Change Analyzer, and impact trace tools. |
| Enable Execution Flow | COBOL, PL/I | Enables the Execution Path tool. |
| Enable Impact Report | COBOL, Natural, PL/I, RPG | Enables the impact trace tools. You must also set Enable Data Element Flow to perform impact analysis. |
| Enter classpath to JAR Files and/or path to external Java file root directories | Java |
Specifies any combination of:
Note: This option is checked before the identical option in the workspace verification options. Setting it here effectively overrides
the setting in the workspace verification options.
|
| Helproutines | Natural Map | Specifies how you want the parser to treat helproutines, as programs or helpmaps. |
| IDMS Environment | COBOL | Specifies how the parser treats IDMS-environment-related code or its absence. |
| IMS Environment | COBOL | Specifies how the parser treats IMS-environment-related code or its absence. |
| Java Classpath | JSP | For JSP files that reference Java types or packages defined in JAR files, external Java files, or Java files, specifies a list of patterns used to resolve the location of the files. For more information, see "Resolving the Location of Java Types and Packages Referenced in JSP Files" in the "JSP Support" section of the help. |
| Java Source Level | Java | Specifies the Java version. Set this option if your application uses constructs that are incompatible with the latest Java version. You would set this option to 1.4, for example, if your application used "enum" as an identifier, since "enum" is a reserved word in Java 5. |
| Job to Schedule Ids File | CA-7 Schedule | Specifies the full path of a file that supplies schedule IDs for CA-7 jobs triggered by the creation of a dataset. |
| Libraries | Natural | When Libraries support is selected in the Verification > Settings tab of the Workspace Options window for Natural files, specifies the order in which the parser searches for library names when it resolves program calls. Place a check mark next to a library to include it in the search. The parser always searches for the current library first. For more information, see "Natural Support" in the online help. |
| List of Include Directories | C, C++ | Specifies the full path of folders for include files (either original folders or Repository Browser folders if the include files were registered). Choose a recognized folder in the List of Include Directories pane. Add folders as necessary. |
| Limit Maximum Array Size | PL/I | Controls the maximum size of arrays to be calculated during analysis. The default is 75. |
| Maximum Number of Variable’s Values | COBOL | Specifies the maximum number of values to be calculated for each variable during verification for advanced program analysis. Limit is 200. |
| Maximum Size of Variable to Be Calculated | COBOL | Specifies the maximum size in bytes for each variable value to be calculated during verification for advanced program analysis. |
| Override CICS Program Terminations | COBOL, PL/I | Specifies that the parser interpret CICS RETURN, XCTL, and ABEND commands as not terminating program execution. Error-handling code after these statements is either analyzed or treated as dead code. |
| Perform COMS Analysis | COBOL | Specifies that the parser define relationships for Unisys MCP COMS SEND statements. |
| Perform Generic API Analysis | COBOL, PL/I | Specifies that the parser define relationships with objects passed as parameters in calls to unsupported program interfaces, in addition to relationships with the called programs themselves. |
| Perform Program Analysis | COBOL | Enables program analysis and component extraction features. |
| Perform Unisys Common-Storage Analysis | COBOL | Specifies that the parser include in the analysis for Unisys COBOL files variables that are not explicitly declared in CALL statements, but that participate in interprogram communications. You must set this option to include Unisys COBOL common storage variables in impact traces and global data flow diagrams. |
| Perform Unisys TIP and DPS Calls Analysis | COBOL | Specifies that the parser perform Unisys 2200 TIP and DPS call analysis. |
| Report Writer Environment | COBOL | Specifies how the parser treats Report Writer-environment-related code or its absence. |
| Resolve Decisions Automatically | COBOL, Natural, PL/I, RPG | Specifies that the parser autoresolve decisions after successfully verifying files. |
| SQL Environment | Assembler, COBOL, RPG | Specifies how the parser treats SQL-environment-related code or its absence. |
| Support CICS HANDLE statements | COBOL | Specifies that the parser detect dependencies between CICS statements and related error-handling statements. |
| Use overwritten VALUEs | COBOL | Specifies that the parser use constants from VALUE clauses as known values even if they are overwritten in the program by unknown values. |
| Use Precompiled Header File | C, C++ | Specifies that the parser verify the project with the precompiled header file you enter in the adjacent field. Do not specify the file extension. Using a precompiled header file may improve verification performance significantly. The content of the header file must appear in both a .c or .cpp file and a .h file. The precompiled header file need not have been used to compile the application. |
| Use VALUEs from Linkage Section | COBOL | Specifies that advanced analysis tools not ignore parameter values in the Linkage Section. |