Studio Developer 8.7.4.0007 introduces a new feature for DDL Generation.

You can now set the generation mode to ‘Alter Column’. This compares the columns in the model database design with a physical database and generates ALTER TABLE DDL for new, removed and modified columns.

   

xTrace 2.6.0 is now available. 

The main change in this release is that the Monitor and Windows xtService have been upgraded to use Visual Studio 2015 and CA Gen 8.6 runtimes.

A new version of the xTrace host runtime has also been produced but the 2.6 Monitor is compatible with earlier releases of the xtService and host runtime software and therefore the Monitor can be upgraded without needing to upgrade the host software.

It is recommended that you install the 2.6.0 host software since future fixes and enhancements will be provided to the 2.6 release.

Studio Developer is a modern Eclipse based alternative to the CA Gen toolset. Designed to be easier to use and learn, Studio Developer has been enthusiastically adopted by several CA Gen sites who report very positive feedback from both new and experienced developers. 

To help train new developers in CA Gen, IET have started to produce a series of short videos that show how to build applications using CA Gen with Studio Developer.

Each module will be concise with the idea that a new developer can watch the video and then practice the concepts learnt.

The first module is now available. In this module we dive straight in and build a simple 'Hello World' application. Future modules will cover concepts like action diagramming, common action blocks, UI design, views, data modelling, client/server and more.

The videos are available on YouTube: https://www.youtube.com/playlist?list=PL...k_mZDIZ8sS

For best results, please adjust the video quality to 1080p when playing the videos.

We welcome feedback on the format of the videos.

A new Remote Generation feature has been added to GuardIEn for the Host Encyclopaedia in Release 8.7.4.

Code generation on the CA Gen Host Encyclopaedia is limited to MVS/COBOL target environments. This means that if you need to generate code for other platforms (for example clients, proxies or non-MVS server environments), you have to download models or subsets to generate code locally on the toolset. This approach requires manual intervention by a developer and has been practically impossible to automate until now with the release of GuardIEn Remote Generation and Studio Developer Automated Generation.

Remote Generation is a new component of GuardIEn's automated system updating facility which enables the generation of code remotely. The remote generation step automatically scopes and downloads a subset containing those objects that need to be regenerated along with a control file which specifies what objects require generation and installation.

Automated Generation is a new feature in Studio Developer which automatically checks for the remote generation control files (which have been transferred to the workstation by GuardIEn) and then prepares the subset and generates / installs the code as specified in the control file. 

With the combination of GuardIEn Remote Generation and Studio Developer Automated Generation, users of the CA Gen host encyclopaedia can now completely automate the generation and build of their application across all target platforms - clients, proxies, web services and both MVS and non-MVS server code.

   

Release 8.7.4 brings a new feature to Studio Developer - Automated Generation.

Studio Developer Automated Generation enables code generation and build process to be automatically initiated based on data in a control file. When the control file is transferred to a folder on the workstation, the generate and build process is automatically started by the Studio Developer Automated Generation Monitor. It can be used in combination with the GuardIEn Host Encyclopaedia Remote Generation feature or the control files can be created using other methods.

The CA Gen Host Encyclopaedia (HE) only supports direct generation for MVS targets, so non-MVS code (for example GUI or Web clients, proxies or non-MVS servers) cannot be generated directly from the HE. GuardIEn on the Host Encyclopaedia incorporates a new feature for system updating called Remote Generation which creates the control files and performs the subset scoping and download tasks to be able to automatically perform the generation and build using Studio Developer Automated Generation.

   

New service packs have been released for Release 8.7 (SP4) and Release 8.6 (SP10).

GuardIEn features in the latest edition of the Broadcom Mainframe Newsletter in an article on DevOps. For more information omn how GuardIEn helps enable DevOps best practices for CA Gen, view this paper: DevOps Tool Support for CA Gen.

   

Studio Developer 8.7.3.0022 is now available:

Opening Read-only models
Read-only models can now be opened from the Local Models view without needing to use the separate File->Open Model (Read-only) menu.

Stopping Background Generation
Use the Local Models Generate->Stop Background Generation menu item to stop the background generation.

Override Generation Source Path
You can now specify an alternative generation source path in the options to override the local model path.

Studio Developer 8.7.3.0021 is now available with two new features to enhance code generation.

Background Code Generation
Studio Developer now supports the ability to generate code in the background. 

Building Load Modules
There is now an option to build load modules directly from Studio Developer rather than via the Build Tool.

A new feature in Studio Developer allows you more control over the optionality of newly created views.

Entity/Group View Optionality specifies the optionality for new entity and group views:

• Default – Mandatory for BAA Action Blocks, Optional for BSD/Pstep action blocks (same as Gen toolset)
  
• Optional – the view is optional
  
• Mandatory – the view is mandatory
  

• Same as parent view – the optionality is the same as the parent entity view
  
• Optional - the view is optional
  
• Mandatory - the view is mandatory
  
• Same as attribute definition – the optionality is the same as the attribute’s optionality