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

CAST AIP 8.3.30 contains all fixes from the following previous CAST AIP releases:

  • 7.3.0 - 7.3.11
  • 8.0.0 - 8.0.5
  • 8.1.0 - 8.1.7
  • 8.2.0 - 8.2.16
  • 8.3.0 - 8.3.30

The following table lists all bugs fixed in CAST AIP 8.3.31 and that are not already listed in the "Resolved Issues" lists of the above mentioned releases. There are 17 issues listed below. The column "Internal ID" is used only as an internal reference ID.

Ticket IDSituationSymptomsInternal ID
22833During analysisMissing link between Oracle Forms Menu Item and Oracle Forms ModuleAIPCORE-2044
25676During import assessment modelToo many client message and CMS blockedAIPCORE-2521
26062While analyzing the codeFew java files are not analyzed from new codeAIPCORE-2783
26308When looking at the results of an analysisMissing links from JCL to Cobol Program when CALL syntax is used. This is now fixed and after an upgrade your existing results may be impacted.MAINFRAME-498
27056During analysisFalse Violation for the QR: Avoid SQL injection vulnerabilitiesAIPCORE-2792
27169While analyzing the source codeDouble links are created between two objectsAIPCORE-2784
27174While analyzing PowerBuilderGeneration of SRD files in PowerBuilder analysis is not consistent. Missing files are not generated again.

An improvement to the PB Analyzer has been implemented in this release of AIP Core: in order to produce more consistent analysis results, the behaviour of the .pbl data extraction process has been changed. Previously, source code was extracted from .pbl files only when it was considered necessary (i.e. no previous extraction had been completed for a given .pbl file, or when the .pbl file had changed since the last extraction). In this release of AIP Core, .pbl files will always be extracted to ensure that successive analysis results are consistent over time. As a result of this change, an error message will be recorded in the analysis log when extracted source code from a previous analysis is available, but the corresponding .pbl cannot be located in the new source code delivery. This indicates an issue with the organisation of your delivered source code which will need to be resolved. Example error message: "Error while retrieving information about a PB library, bad library name : path\to\my.pbl".
AIPCORE-2782
27267While analyzing the source codeDouble links are created between two objects after UKBAIPCORE-2797
27269, 27274While adding a version in CAST-MSCAST-MS with special characters in it's version name does not throw an error (AIP Console throws an error).AIPCORE-2798
27285When looking at the results of an analysisMainframe Utilities (such as default utilities for zOS, AS400, IBM MQ etc.) are wrongly categorized as "Unknown Programs".MAINFRAME-533
27311While running the update cast knowledge base (UKB) toolWhile running the update cast knowledge base tool following error is displayed: ERROR: relation "§ctv_links" does not existAIPCORE-2820
27334During snapshot (after analysis)False violation for QR: "Avoid Uncontrolled format String"AIPCORE-2805
27356During snapshot (after analysis)Object name is truncated in Knowledge Base and Dashboard for COBOL TechnologyAIPCORE-2804
27374During analysisAnalysis is fails with the ERROR: relation "§uax_import_instances" does not existAIPCORE-2843
27398While upgrading few applications.Application upgrade is failing in import package step with nullpointer exception.AIPCORE-2814
27554While analyzing codeMainframe exclude copybook parameter is not active post upgrade (after migrating from 8.3.3 to 8.3.29)AIPCORE-2852
23758While looking at the documentation for the rule 7266 "Call 'base.Dispose()' or 'MyBase.Finalize()' in the "finally" block of 'Dispose(bool)' methods".3 reference links out of 4 are invalid.DOTNET-1108
  • No labels