Highlighted
Absent Member.
Absent Member.
1320 views

Runtime Error

Jump to solution

I have a naïve code program that I put as a single project in a solution that is a single executable.  On the cobol link tab I have checked the add system files.  When the client runs the .exe from the server he gets an error ''cblrtsm.dll is missing'.  Should that not be included in the .exe at compile?

Thanks

0 Likes
1 Solution

Accepted Solutions
Highlighted
Micro Focus Expert
Micro Focus Expert

RE: Runtime Error

Jump to solution

Hi Kevin,

The system files that are linked in when checking that option include Adis, Adisinit, Adiskey, Adisdyna, and Mffh but the run-time itself is never included in the linked executable in Visual COBOL. This used to be an option in Net Express where you could specify a static link but that has been removed from Visual COBOL.

If you specify the dynamic option when linking it will search the registry at run-time to find out the location of the installed cblrtsm.dll and use that version. If you do not specify dynamic then the cblrtsm.dll needs to be located in the current folder with the executable or within one of the folders specified in PATH.

There is also a run-time launcher file available that allows you to specify the location of the run-time file in a config file instead of searching the registry or PATH.

Thanks.

View solution in original post

0 Likes
2 Replies
Highlighted
Micro Focus Expert
Micro Focus Expert

RE: Runtime Error

Jump to solution

Hi Kevin,

The system files that are linked in when checking that option include Adis, Adisinit, Adiskey, Adisdyna, and Mffh but the run-time itself is never included in the linked executable in Visual COBOL. This used to be an option in Net Express where you could specify a static link but that has been removed from Visual COBOL.

If you specify the dynamic option when linking it will search the registry at run-time to find out the location of the installed cblrtsm.dll and use that version. If you do not specify dynamic then the cblrtsm.dll needs to be located in the current folder with the executable or within one of the folders specified in PATH.

There is also a run-time launcher file available that allows you to specify the location of the run-time file in a config file instead of searching the registry or PATH.

Thanks.

View solution in original post

0 Likes
Highlighted
Absent Member.
Absent Member.

RE: Runtime Error

Jump to solution

Thanks

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.