Gen EDGE

Hi All;

CG /8.5, Encyclopedia/Host Encyclopedia HE, Language /Java OS/ windows  platform /client server 

Any recommendation about how I can improve generation performance time by CA Gen

Target Java  web Client & Server

Currently  in development  &  integration  environment, we generate  the  whole model by  the "ToolSet"   even the  change  in one Action  block  which takes a long of time some Modles takes more than 4 hours 

The future plan will be transfer to use a CSE encyclopedia with GuardIEn 

Any Currently recommendation?

Generally it is not necessary to generate the whole  model.  Limit yourself to generate only changed items.  Take care to to include in the generation any collateral changes.  This may take some getting used to, but it should drastically cut back the generation time.

By the way, this is what GuardIEn does.

For scenarios where toolset generation of a complete model is needed.

The toolset generation is single threaded/serial so it does not take full advantage of modern cpu technologoes.

It is also not possible to open the same model multiple times in multiple toolset sessions and activate parallel generations of different dialog/server/window managers because the read only setting in the additional sessions disables the generation option. 

Using an Encyclopedia for generation is definitely the best option.

Hi All 

Thanks for reply

I can fix  the generation time issue  by More Hardware capacity  

But still How  can run impact  of the change  by  Toolset in big and very old  Model 

GuardIEn  is the best in that 

Yes ... GuardIEn is the best at determining the impacted objects and just building what is required.

This is usually via the release pack features and system updates.

It generates code in parallel (controlled by system parms) and builds sequentially.

It also has an 'intelligent regeneration' type feature which builds code that has been changed recently but not generated yet. This is useful at the dev environment level and good to run overnight (or once a week) to ensure a reasonable stable dev environment.

The Host Ency had an intel regeneration feature (from memory) . That also only built what had changed for an environment/model.