Web service calling native Cobol

In Visual Studio 2012 I have created a C# WCF service (based on the WCF service library project template).

This weservice calls a managed Cobol class, which in turn calls native Cobol modules.

When I test the webservice the first call is handled correctly. But when I invoke the webservice again I get strange results.

After some analysis I learned that the cause of the problem is that when the native Cobol modules are called in the second webservice request the state of their Working-Storage is still as it was left after the first invocation of the webservice. In other words, the native modules are still in memory and their state has bee preserved.

Does anybody know how I can solve this?

In Visual Studio 2012 I have created a C# WCF service (based on the WCF service library project template).

This weservice calls a managed Cobol class, which in turn calls native Cobol modules.

When I test the webservice the first call is handled correctly. But when I invoke the webservice again I get strange results.

After some analysis I learned that the cause of the problem is that when the native Cobol modules are called in the second webservice request the state of their Working-Storage is still as it was left after the first invocation of the webservice. In other words, the native modules are still in memory and their state has bee preserved.

Does anybody know how I can solve this?

In Visual Studio 2012 I have created a C# WCF service (based on the WCF service library project template).

This weservice calls a managed Cobol class, which in turn calls native Cobol modules.

When I test the webservice the first call is handled correctly. But when I invoke the webservice again I get strange results.

After some analysis I learned that the cause of the problem is that when the native Cobol modules are called in the second webservice request the state of their Working-Storage is still as it was left after the first invocation of the webservice. In other words, the native modules are still in memory and their state has bee preserved.

Does anybody know how I can solve this?

In Visual Studio 2012 I have created a C# WCF service (based on the WCF service library project template).

This weservice calls a managed Cobol class, which in turn calls native Cobol modules.

When I test the webservice the first call is handled correctly. But when I invoke the webservice again I get strange results.

After some analysis I learned that the cause of the problem is that when the native Cobol modules are called in the second webservice request the state of their Working-Storage is still as it was left after the first invocation of the webservice. In other words, the native modules are still in memory and their state has bee preserved.

Does anybody know how I can solve this?

In Visual Studio 2012 I have created a C# WCF service (based on the WCF service library project template).

This weservice calls a managed Cobol class, which in turn calls native Cobol modules.

When I test the webservice the first call is handled correctly. But when I invoke the webservice again I get strange results.

After some analysis I learned that the cause of the problem is that when the native Cobol modules are called in the second webservice request the state of their Working-Storage is still as it was left after the first invocation of the webservice. In other words, the native modules are still in memory and their state has bee preserved.

Does anybody know how I can solve this?

In Visual Studio 2012 I have created a C# WCF service (based on the WCF service library project template).

This weservice calls a managed Cobol class, which in turn calls native Cobol modules.

When I test the webservice the first call is handled correctly. But when I invoke the webservice again I get strange results.

After some analysis I learned that the cause of the problem is that when the native Cobol modules are called in the second webservice request the state of their Working-Storage is still as it was left after the first invocation of the webservice. In other words, the native modules are still in memory and their state has bee preserved.

Does anybody know how I can solve this?

In Visual Studio 2012 I have created a C# WCF service (based on the WCF service library project template).

This weservice calls a managed Cobol class, which in turn calls native Cobol modules.

When I test the webservice the first call is handled correctly. But when I invoke the webservice again I get strange results.

After some analysis I learned that the cause of the problem is that when the native Cobol modules are called in the second webservice request the state of their Working-Storage is still as it was left after the first invocation of the webservice. In other words, the native modules are still in memory and their state has bee preserved.

Does anybody know how I can solve this?

In Visual Studio 2012 I have created a C# WCF service (based on the WCF service library project template).

This weservice calls a managed Cobol class, which in turn calls native Cobol modules.

When I test the webservice the first call is handled correctly. But when I invoke the webservice again I get strange results.

After some analysis I learned that the cause of the problem is that when the native Cobol modules are called in the second webservice request the state of their Working-Storage is still as it was left after the first invocation of the webservice. In other words, the native modules are still in memory and their state has bee preserved.

Does anybody know how I can solve this?