Load error : file 'CBL_FN_INTEGER0OF0DATE_IBM' error code: 173, pc=0, call=1, seg=0 173 Called program file not found in drive/directory 12:52:56.
Does anyone know what the file name is for this routine and in which folder does this date routine go? Also, much appreciated if you have a copy of this routine and can attach it to this request.
Thanks!
Load error : file 'CBL_FN_INTEGER0OF0DATE_IBM' error code: 173, pc=0, call=1, seg=0 173 Called program file not found in drive/directory 12:52:56.
Does anyone know what the file name is for this routine and in which folder does this date routine go? Also, much appreciated if you have a copy of this routine and can attach it to this request.
Thanks!
Hi.
The RTS173 error means it cannot locate this program. As far as I know there is no routine in the Micro Focus Visual COBOL library with that name and I don't find a reference for it in the IBM docs either.
It sounds like it might be calling the intrinsic function INTEGER-OF-DATE which is documented here.
Are you moving your application from an environment where this call did work?
What COBOL compiler and platform was that?
Hi.
The RTS173 error means it cannot locate this program. As far as I know there is no routine in the Micro Focus Visual COBOL library with that name and I don't find a reference for it in the IBM docs either.
It sounds like it might be calling the intrinsic function INTEGER-OF-DATE which is documented here.
Are you moving your application from an environment where this call did work?
What COBOL compiler and platform was that?
Yes, the program calling this function works on a different environment. However, it fails on another environment. Just wondering why it fails on one environment.
It appears that we are missig this intrinsic function from one of the installation. Hence, the question.
eg: -
FUNCTION INTEGER-OF-DATE (FIX-DATE)
Any thoughts!
Yes, the program calling this function works on a different environment. However, it fails on another environment. Just wondering why it fails on one environment.
It appears that we are missig this intrinsic function from one of the installation. Hence, the question.
eg: -
FUNCTION INTEGER-OF-DATE (FIX-DATE)
Any thoughts!
The error doesn't seem to be because the intrinsic function itself is missing but because the application is trying to call a program called CBL_FN_INTEGER-OF-DATE_IBM' and it cannot find it. Do you have a program with that name that did not get moved over to the new platform?
What is the old platform and COBOL compiler that you are running and what is the new platform and COBOL compiler?
The error doesn't seem to be because the intrinsic function itself is missing but because the application is trying to call a program called CBL_FN_INTEGER-OF-DATE_IBM' and it cannot find it. Do you have a program with that name that did not get moved over to the new platform?
What is the old platform and COBOL compiler that you are running and what is the new platform and COBOL compiler?
No, I do not have a program with that name. I assumed that when I'm calling the above function, its converting the call to that name and again asuming its a conversion made internally by Microfocus.
No, I do not have a program with that name. I assumed that when I'm calling the above function, its converting the call to that name and again asuming its a conversion made internally by Microfocus.
What is the old platform and COBOL compiler that you are running and what is the new platform and COBOL compiler?
What is the old platform and COBOL compiler that you are running and what is the new platform and COBOL compiler?
Both the Cobol compilers are in the same platform. However, one is a new region created for testing and apparently I believe we are missing few elements in the new environment. Hence, trying to find out what we are missing.
Cobol is compiled using .net Cobol 6.x in VS 2019.
Both the Cobol compilers are in the same platform. However, one is a new region created for testing and apparently I believe we are missing few elements in the new environment. Hence, trying to find out what we are missing.
Cobol is compiled using .net Cobol 6.x in VS 2019.
Sorry, yes you are correct, it is a Micro Focus routine which appears to be part of the run-time system, cblrtsm.dll. I am not sure why it cannot be found in your case as the program could not run without cblrtsm.dll.
Does this occur in your development environment too or just in your run-time environment? Are you installing the COBOL Server product or are you just copying selected files?
Sorry, yes you are correct, it is a Micro Focus routine which appears to be part of the run-time system, cblrtsm.dll. I am not sure why it cannot be found in your case as the program could not run without cblrtsm.dll.
Does this occur in your development environment too or just in your run-time environment? Are you installing the COBOL Server product or are you just copying selected files?
Yes, it occurs in one of the test environment. Not in most of the other environments. We are using .gnt for our compiled cobol programs. Do you know what folder has cblrtsm.dll. I am guessing it will be in an MF installation folder. It's working in few other regions, hence should be able to copy from a different region/environment.
Yes, it occurs in one of the test environment. Not in most of the other environments. We are using .gnt for our compiled cobol programs. Do you know what folder has cblrtsm.dll. I am guessing it will be in an MF installation folder. It's working in few other regions, hence should be able to copy from a different region/environment.
I did a scan and found that cblrtsm.dll was under bin folder in an environment where calling this routine is not failing. (...\\Enterprise Developer\\bin). Can I copy this module to the missing environment?
Yes, it occurs in one of the test environment. Not in most of the other environments. We are using .gnt for our compiled cobol programs. Do you know what folder has cblrtsm.dll. I am guessing it will be in an MF installation folder. It's working in few other regions, hence should be able to copy from a different region/environment.
32-bit cblrtsm.dll is in the bin folder of a standard install and the 64-bit version is in the bin64 folder..
I did a scan and found that cblrtsm.dll was under bin folder in an environment where calling this routine is not failing. (...\\Enterprise Developer\\bin). Can I copy this module to the missing environment?
Yes, you can copy it as long as it is the same version. We always recommend that you install the full products so that you are sure to have all dependant modules installed.
Yes, you can copy it as long as it is the same version. We always recommend that you install the full products so that you are sure to have all dependant modules installed.
After checking the installation on the "failing" server, cblrtsm.dll was present. However, the MF version (6.0.00255) was older than the version where the program runs successfully. (6.0.00322)
Any thoughts on why the older version is failing? Do we have to re-install the newer version of MF?
Thanks!
After checking the installation on the "failing" server, cblrtsm.dll was present. However, the MF version (6.0.00255) was older than the version where the program runs successfully. (6.0.00322)
Any thoughts on why the older version is failing? Do we have to re-install the newer version of MF?
Thanks!
Those versions are very far apart. I dont believe that you have any of the patch updates installed on the older version. If the .gnt was produced with the newer version then there could be a problem. I would recommend that you upgrade to the same or a newer patch update version.