We are trying to update to Visual Cobol DevHub 8.0 (Patch Update 9) from DevHub 7/DevHub 6. and we are getting below error when compiling a cobol program. The program or the compilation script is not changed and module is getting compiled without any error in DevHub 6 and 7. Even in DevHub 8 the module is getting compiled without any program errors but when creating .o file, below error is displayed. Kindly help to resolve the issue

Current Configuration :
Base Directory : /projects/pr/server/server
** -- **
Compiling : BATCHCON.cbl
Member Name is : BATCHCON.cbl
Member is : BATCHCON
Compiling COBOL Program with SQL Options ...
cob64 -x -v -V -t -C DIR"/projects/pr/server/scripts/cobol.dir" BATCHCON.cbl -o BATCHCON -L /usr/mqm/lib64 -lmqicb_r -L /db2inst1/sqllib/lib64 -ldb2 /opt/microfocus/VisualCOBOL/lib/cobdb264.so /opt/microfocus/VisualCOBOL/lib/cobrtxml64.so /opt/microfocus/VisualCOBOL/lib/libxerces-c64.so
* Micro Focus COBOL V8.0 revision 000 Compiler
* (C) Copyright 1984-2023 Micro Focus or one of its affiliates.
* Accepted - verbose
* Accepted - reentrant
* Accepted - NOBOUND
* Accepted - CHECKNUM
* Accepted - SPZERO
* Accepted - DIR"/projects/pr/server/server/scripts/cobol.dir"
* Total Messages: 0
* Data: 73776 Code: 33257
* End of cross reference listing
* Micro Focus COBOL Code Generator
* (C) Copyright 1984-2023 Micro Focus or one of its affiliates.
* Accepted - verbose
* Accepted - anim
* Generating BATCHCON
* Data: 0 Code: 36794 Literals: 14400
cob64: Entry points defined in module: BATCHCON.o
*BATCHCON
cc: error: /opt/microfocus/VisualCOBOL/lib/libxerces-c64.so: No such file or directory

I checked the lib folder and could not find libxerces-c64.so file  in DevHub 8 installation folder but this file is available in Devhub 6 & 7

However i could find file libxerces-c64-3.2.so in DevHub 8 lib folder, should we use this file instead of libxerces-c64.so. Kindly advise. Please let us know for further information

Hello Saravanan Paramasivam,

I'm checking into this question. I have confirmed the name change that you noticed in Visual COBOL 8, where the Xerces shared object in $COBDIR/lib is now named libxerces-c64-3.2.so.

It's been suggested that items in the $COBDIR/lib directory don't usually require explicit references to link them in on a cob command, as the link may pull these modules in automatically. You might try removing the reference to: 
   /opt/microfocus/VisualCOBOL/lib/libxerces-c64.so

from your cob command, and check to see if the module still builds and runs correctly.

Hi Blair,

Thank you for the response, I was able to compile the module after removing the reference to /opt/microfocus/VisualCOBOL/lib/libxerces-c64.so but i have to run couple of test scenarios to confirm that it is working as expected which i will be doing by setting up one more instance of my application with the references removed to /opt/microfocus/VisualCOBOL/lib folder in the compilation script.

But for now to complete the update of Visual Cobol 8 development region which im currently working on, is it fine to use the libxerces-c64-3.2.so to compile the above module or is there any difference between using libxerces-c64-3.2.so & libxerces-c64.so. Kindly advise