|Summary: CAST AIP 8.3.22 introduces a number of features and changes as listed below. To view the impacts of these changes on analysis results, see: Changes in results post upgrade|
Support has been introduced for situations where JCL batches are executing Java. A new Mainframe object has been added for this situation:
Example code that is now taken into account:
//LMGHWRLD JOB (MY,ACCOUNTING,INFO),'HELLO WORLD', // CLASS=A,MSGCLASS=H,REGION=0M,NOTIFY=&SYSUID //STEP1 EXEC PGM=JVMLDM60, // PARM='com.foo.bar.HelloWorld' //STEPLIB DD DSN=<MY.LIBRARY.PATH>,DISP=SHR //SYSPRINT DD SYSOUT=* //SYSOUT DD SYSOUT=* //STDOUT DD SYSOUT=* //STDERR DD SYSOUT=* //STDENV DD * . /etc/profile . ~/.profile export CLASSPATH=~/HelloWorld for i in ~/HelloWorld/*.jar; do export CLASSPATH=$i:$CLASSPATH done //
|Note that this support requires the use of the Web Services Linker extension ≥ 1.6.10 delivered with CAST AIP ≥ 8.3.22.|
The following methods that can be used to process SQL/access database within JCL are now supported:
A new Mainframe object has been added for this situation:
JCL symbolic parameter values are now correctly propagated from JCL to procedures in the call chain.
The User Input Security feature has been updated and improved as follows:
Architecture Models attached to an application are now saved in the Dashboard schema during the snapshot computation, this is so that the graphical representation of the model can be reproduced in the CAST Engineering Dashboard along with the results of the associated rules (metrics). This is in preparation for a future release of the CAST Engineering Dashboard where this feature will be implemented.
When an extension is installed (on its own, as part of a schema installation or as part of a schema upgrade), more stringent consistency checks are now run on the metamodel XML file included in the extension:
These checks should not cause any issues with the installation of official CAST AIP extensions however, if you are using custom extensions that do not conform to the metamodel syntax, the extension installation process may fail (schema installation/schema upgrade may also fail).