Skip to main content

[archive] Creating and finding NetEvents.ini

  • December 17, 2006
  • 1 reply
  • 0 views

[Migrated content. Thread originally posted on 15 December 2006]

We are using a .NET control from within our Cobol application. The dlls will not be held in the Global cache.

I have a couple of queries.

Is there any way to know where the WRUN32 was launched from? I would like to be able to create NetEvents.INI in the Cobol Install directory.

Where would you expect to find NetEvents.ini when running ThinClient? On the server, or on the Client, sharing a directory with ACUTHIN.EXE?

Thanks

Linda

1 reply

[Migrated content. Thread originally posted on 15 December 2006]

We are using a .NET control from within our Cobol application. The dlls will not be held in the Global cache.

I have a couple of queries.

Is there any way to know where the WRUN32 was launched from? I would like to be able to create NetEvents.INI in the Cobol Install directory.

Where would you expect to find NetEvents.ini when running ThinClient? On the server, or on the Client, sharing a directory with ACUTHIN.EXE?

Thanks

Linda
As you apparently is targeting Windows, you can use the GetCommandLine function from the Windows API, this will give you a memory pointer, for which the first will be the full path to the runtime. To be able to use this you will have to copy the data to a cobol variable first.¨

As for netevents.ini, generally speaking, assembly dlls that are not in the GAC should be located together with the runtime. For thin client this will then imply acuthin.exe. Thus, also the NetEvents.ini file should reside with the executable.