Hello out there,

I'm using  Enterprise Developer for z/Enterprise V. 2.2. I've created a Remote Mainframe COBOL Project and trying to create a single executable file. Additional Object-Files (say, myfile.o), which need to be linked to the single executable file, reside on a remote path, e.g. "/mypath/repo", on the UNIX system. The remote path is accessible from the MFED-system using Samba.

So the complete path to the object file on the remote machine looks like this: /mypath/repo/myfile.o

I've tried to add it via MicroFocus Build Configuration "additional link file - add external file"s. I can browse the UNIX file system and add it and in the item list the path looks ok, just like given above. However, when I build, the path is being converted to the Windows-format and it is not found:

[cobollink] Linking (64-bit) myprog...
[cobollink] cob64 -g -x -omyprog myprog.o C:\\mypath\\repo\\myfile.o -U
[cobollink] cob64: error opening: C:\\mypath\\repo\\myfile.o

Another thing I've tried is to link "/mypath/repo" as a "remote folder" to my MFED project. Then with "additional link file - add files..." I can add the object file. The file will be shown in the item list relative to the project path, e.g. "myproject/repo/myfile.o". However, when I try to build, the linked folder is not resolved, the compiler does not follow the link but instead looks for it under the project folder:

[cobollink] Linking (64-bit) IF9C12...
[cobollink] cob64 -g -x -omyprog myprog.o /remoteprojectpath/myproject/repo/myfile.o -U
[cobollink] cob64: error opening: /remoteprojectpath/myproject/repo/myfile.o

Can someone please advise how to add external object files, that reside on the remote system, to the linkage process?

What is it that I am doing wrong? I'd appreciate your hints

Hello out there,

I'm using  Enterprise Developer for z/Enterprise V. 2.2. I've created a Remote Mainframe COBOL Project and trying to create a single executable file. Additional Object-Files (say, myfile.o), which need to be linked to the single executable file, reside on a remote path, e.g. "/mypath/repo", on the UNIX system. The remote path is accessible from the MFED-system using Samba.

So the complete path to the object file on the remote machine looks like this: /mypath/repo/myfile.o

I've tried to add it via MicroFocus Build Configuration "additional link file - add external file"s. I can browse the UNIX file system and add it and in the item list the path looks ok, just like given above. However, when I build, the path is being converted to the Windows-format and it is not found:

[cobollink] Linking (64-bit) myprog...
[cobollink] cob64 -g -x -omyprog myprog.o C:\\mypath\\repo\\myfile.o -U
[cobollink] cob64: error opening: C:\\mypath\\repo\\myfile.o

Another thing I've tried is to link "/mypath/repo" as a "remote folder" to my MFED project. Then with "additional link file - add files..." I can add the object file. The file will be shown in the item list relative to the project path, e.g. "myproject/repo/myfile.o". However, when I try to build, the linked folder is not resolved, the compiler does not follow the link but instead looks for it under the project folder:

[cobollink] Linking (64-bit) IF9C12...
[cobollink] cob64 -g -x -omyprog myprog.o /remoteprojectpath/myproject/repo/myfile.o -U
[cobollink] cob64: error opening: /remoteprojectpath/myproject/repo/myfile.o

Can someone please advise how to add external object files, that reside on the remote system, to the linkage process?

What is it that I am doing wrong? I'd appreciate your hints

Hello out there,

I'm using  Enterprise Developer for z/Enterprise V. 2.2. I've created a Remote Mainframe COBOL Project and trying to create a single executable file. Additional Object-Files (say, myfile.o), which need to be linked to the single executable file, reside on a remote path, e.g. "/mypath/repo", on the UNIX system. The remote path is accessible from the MFED-system using Samba.

So the complete path to the object file on the remote machine looks like this: /mypath/repo/myfile.o

I've tried to add it via MicroFocus Build Configuration "additional link file - add external file"s. I can browse the UNIX file system and add it and in the item list the path looks ok, just like given above. However, when I build, the path is being converted to the Windows-format and it is not found:

[cobollink] Linking (64-bit) myprog...
[cobollink] cob64 -g -x -omyprog myprog.o C:\\mypath\\repo\\myfile.o -U
[cobollink] cob64: error opening: C:\\mypath\\repo\\myfile.o

Another thing I've tried is to link "/mypath/repo" as a "remote folder" to my MFED project. Then with "additional link file - add files..." I can add the object file. The file will be shown in the item list relative to the project path, e.g. "myproject/repo/myfile.o". However, when I try to build, the linked folder is not resolved, the compiler does not follow the link but instead looks for it under the project folder:

[cobollink] Linking (64-bit) IF9C12...
[cobollink] cob64 -g -x -omyprog myprog.o /remoteprojectpath/myproject/repo/myfile.o -U
[cobollink] cob64: error opening: /remoteprojectpath/myproject/repo/myfile.o

Can someone please advise how to add external object files, that reside on the remote system, to the linkage process?

What is it that I am doing wrong? I'd appreciate your hints