Gen Toolset generation for Java crashes (abg.exe)
search cancel

Gen Toolset generation for Java crashes (abg.exe)

book

Article ID: 403178

calendar_today

Updated On:

Products

Gen Gen - Host Encyclopedia Gen - Workstation Toolset

Issue/Introduction

Currently re-platforming Gen application from Mainframe z/OS (COBOL) to Linux (Java) and having issues with the Toolset Java generation.
The abg.exe generator crashes for some of the action diagrams without any warning/error message and only shows "failed" in the Toolset.
The problem seems to be a specific "Use statement"
The Windows Event Log shows:

Faulting application name: abg.exe, version: 8.6.0.9343, time stamp: 0x6643d8e9
Faulting module name: abg.exe, version: 8.6.0.9343, time stamp: 0x6643d8e9
Exception code: 0xc0000005
Fault offset: 0x0021869a
Faulting process id: 0xa474
Faulting application start time: 0x01dbc5b0847af6ee
Faulting application path: C:\Program Files (x86)\CA\Gen_r86\Gen\abg.exe
Faulting module path: C:\Program Files (x86)\CA\Gen_r86\Gen\abg.exe
Report Id: f20bd88a-85c8-461e-800a-846023832ae2
Faulting package full name:
Faulting package-relative application ID:

There were no previous problems with the COBOL generation of the same code.

The current model was originally stored on a Host Encyclopedia (HE) and has been copied to a Client Server Encyclopedia (CSE).
Both Encyclopedias are in use.

Environment

Gen 8.6 Java Generation

Resolution

It is likely that there is a model corruption in the model and Gen Support/Engineering will need to help to remove that corruption.

For this particular scenario the problem only occurred when the whole model was checked out, but it may occur with a subset checkout.
It also occurred with both CSE and HE models.
Engineering thought the corruption was most likely caused by a Toolset problem from a long time ago. It looks like the delete of a Use statement did not completely delete everything and left some partially orphaned objects.
On researching the generator code they came to the conclusion that the COBOL generation would not run into this problem. This would explain why the model corruption did not cause a problem until code was generated for Java.

NEXT STEPS:

Create a support case documenting the error and:

  • If a model/subset checkout.trn can be provided that demonstrates the problem upload that file (zipped) and also the name of the relevant action block being generated. This step is recommended. 

  • If it is not possible to provide a model/subset checkout.trn file create a support case referencing this article to request next steps from Gen Support.