Hi Ahmet, could you possibly attach the contents of the copy files as well as the main source file, so that I can try to reproduce this issue?  It looks as though it may be a problem due to the combination of the ILSMARTLINKAGE directive and SQL syntax, but I will need to try this out.

Robert.

account-service-record is the file content, it was visible when I copied it -I'm using Visual COBOL 2.2

Regards

Ok, by deleting the two COPY statements, I was able to compile this (single) program with ILSMARTLINKAGE.  However, I am not seeing any error.  It occurs to me that the error is not necessarily associated with this first program, and it might be worth systematically removing one program at a time from the project until the problem goes away.  This should be a good indication that the last one removed is the one causing the problem.

Alternatively, if this doesn't lead anywhere, could you raise a support incident and attach the whole project?

Ahmet,

Please zip up your project and e-mail it to me at chris.glazier@microfocus.com so that I can take a look.

Thanks.

Sorry, I had forgotten that things have changed somewhat in the 2.2 Update 1 version of the product.  With the Update 1 version you should find that, instead of all the cryptic messages that you report, you will get a simple message: ILSMARTLINKAGE class 'xxx' has multiple definitions.

Obviously this is better, but doesn't help you a great deal.

So, when the project contains multiple programs referring to the same named linkage record (and ILSMARTLINKAGE is on), currently the compiler will give 'duplicate class' type errors, because it is attempting to generate multiple versions of the same ILSMARTLINKAGE class.

One way of avoiding this is to use the additional ILSMARTNEST directive.  This causes these ILSMARTLINKAGE classes to be generated as nested classes within the class generated for the individual procedural COBOL program, and therefore disambiguates them.

The only downside to this is that, for instance, a C# program that wants to call different COBOL programs using the same linkage records will have to construct instances of different classes for each program.