Skip to main content

Hi,

When building our project we get:

COBCH0803 = - 'procob' is not recognized as an internal or external command. 

We are on:

Windows Server 2016 + Visual Studio 2022 + Visual Cobol 8.0 PU 1

Oracle Client 19.0.0 is installed.

The system PATH variable contains:

<drive>:\\ORACLE\\product32\\19.0.0\\client_1\\bin

procob can be started from a command window.

Any idea why this is not working from within Visual Studio?

Property screen shots attached.

Thanks

Stefan


#PROCOB
#procobol

Hi,

When building our project we get:

COBCH0803 = - 'procob' is not recognized as an internal or external command. 

We are on:

Windows Server 2016 + Visual Studio 2022 + Visual Cobol 8.0 PU 1

Oracle Client 19.0.0 is installed.

The system PATH variable contains:

<drive>:\\ORACLE\\product32\\19.0.0\\client_1\\bin

procob can be started from a command window.

Any idea why this is not working from within Visual Studio?

Property screen shots attached.

Thanks

Stefan


#PROCOB
#procobol

I believe that this is because Visual Studio 2022 is a 64-bit product and your Oracle client (procob) is a 32-bit version.

Try installing the 64-bit Oracle client.

I believe that this is because Visual Studio 2022 is a 64-bit product and your Oracle client (procob) is a 32-bit version.

Try installing the 64-bit Oracle client.

Actually, I just tested this with both the 32-bit and the 64-bit Oracle client and I get the same error as you are seeing.

We are currently looking into this...

Actually, I just tested this with both the 32-bit and the 64-bit Oracle client and I get the same error as you are seeing.

We are currently looking into this...

Hi,

Thanks for checking.

Waiting for your feedback.

Kr,

Stefan

Actually, I just tested this with both the 32-bit and the 64-bit Oracle client and I get the same error as you are seeing.

We are currently looking into this...

Hello Chris

Last monday, ING asked me to have a meeting with them about this case this morning.
I did the consulting at ING for the Net Express / Server for COBOL to Visual COBOL update.

I saw you comments. I will keep you informed.

Regards

Roch

Hello Chris

Last monday, ING asked me to have a meeting with them about this case this morning.
I did the consulting at ING for the Net Express / Server for COBOL to Visual COBOL update.

I saw you comments. I will keep you informed.

Regards

Roch

Hi Chris

We have a meeting this morning with ING.

I found a workaround but it's a bit strange.

a) If we run Visual Studio 2022 starting it from the icon on the desktop, procob is not found.
b) If we start a Visual COBOL 32 bit prompt and we run the Visual Studio 2022 executable devenv.exe from the Visual COBOL 32 bit Prompt, procob is found. 

The PATH environment variable references correctly the bin Oracle directory.

I will try to understand why they have this behaviour with Visual Studio 2022 (VC 8) and not with Visual Studio 2019 (VC 9).

Regards

Roch

Terms & ConditionsAccessibility statement