Re-platform from mainframe to a distributed platform with Gen. The target options could be either C# on Windows or C on Windows/Unix. One of the key characteristics addressed by the mainframe is that of performance. In any re-platform the equivalent (or improved) performance of the re-platformed applications is key. Given the nature of many of the applications built with Gen, replicating as a minimum the current levels of performance can be mission-critical. Does anybody have any related experiences they can share, things to look out for, know pinch-points, common considerations that specifically need to be addressed to ensure performance levels are maintained for re-platformed applications?
Batch Packaging/Generation for .NET/C# is not supported.
Also the alternative Online Packaging for PSteps with Step Properties set to Online="no Display" is not supported for C# code generation.
The only feasible option is to create a batch type process by creating a .NET hand-coded application which uses the Gen .NET Proxy to call a Gen .NET server.Thanks,Steve H.
Thanks Steve, that is what I thought.
Vänliga hälsningar Britt-Marie Kronfjäll Alecta Postadress: 103 73 Stockholm Besöksadress: Regeringsgatan 107 Telefon: 08-441 93 03
Besök oss gärna på alecta.se
Yes, Generating C works. But not C#. The preferred language here is C#.
I was wondering what people who generate C# for their online stuff did for their batch programs. It seems they generate servers and use some form of client to kick it off. Not really what we would want to do. I personally prefer defining online no screen and generating C.