Disclaimer, I know next to nothing about the COBOL ecosystem. Please excuse my ignorance on this.

We have been using a Net Express installation to access a DLL provided to us by our suppliers. Now they upgraded to Visual COBOL and we've been trying to get it to work with COBOL Server, with no luck so far.

We used to install the license with the `aslmpclocate` and the `aslmpcsilent` utilities. Are those still relevant? Do you use them in the same way as with Net Express? If not, what's the alternative?

We also tried installing a `.mflic` file with the License Administration utility, which it accepted, but we get the 245 error code, which seems to indicate (if my googling didn't fail me) that a different type of license is required. Is this accurate, and what license would that be, and where could I find it? Our company should have access to it, though I don't know where to find it.

Furthermore, what files do we need to redistribute? We used to only have a `cblrtss.dll` and `cblrtsm.dll` which we shipped with our application. This has worked so far (though not sure if that was the proper way to handle it - none of the migration guides I read seem to have a setup like this). Do we need those same files again? Our runtime package did not contain a `cblrtss.dll`, but did contain a `cblrtsm.dll`, along with many other files. These were provided by our supplier, but we're not sure which of these would be useful to us.

Unfortunately, our supplier does not seem to know the answers to these questions, we did try solving this with their help, to no avail. Any help on this would be appreciated.

Hi Stjepan,

There is a different licensing system for Visual COBOL and COBOL Server than was used in Net Express, the asmlp... utilities are not used.
You cannot copy the files from the Visual COBOL development system onto your production server. You need to use the files from the COBOL Server installation as they use different licensing. The .mflic file should be correct if you use the COBOL Server license and have the COBOL Server files copied. If you have a COBOL Server license installed and you copied the run-time files from Visual COBOL then that would explain the 245.

We highly recommend that you install the entire COBOL Server product on your production machine so that you have all required files including the License Manager.

Are you installing this on a server and then running the application on that server or are you accessing it from client workstations on which no products have been installed? If you are using client workstations then you will need to set this up for a network deployment.

See the documentation here

BTW, cblrtss.dll is no longer supported in Visual COBOL. This was the single-threaded run-time system. In Visual COBOL the multithreaded version cblrtsm.dll is used instead.