How must we proceed to install Visual cobol 5.0 trial?

- Windows 10 x64 Version 1909 with all updates

- Visual Studio 2019 preview

- vcvs2019_50.exe first, then vsvs2019_pu02_242792.exe

When wanting to install vcbt_50.exe we become following message, 0x81f40001 Micro Focus Visual COBOL for Visual Studio 2019 5.0 must be uninstalled before continuing. 
Is this correct to deinstall VC 5.0

How must we proceed to install the vc_build_tools_dockerfiles_5.0_windows.zip?

By compiling i missed the btrieve object files used in Netexpress5.x (_btrv.obj) What file must be used in VC5.0?

Many Warnings comes by using microfocus dialog systems copy files as dslang.cpy, ds_call.cpy, pan2link.cpy, userctrl.cpy

C:\\adm\\copy\\dslang.cpy (641,19-21) : warning COBCH1125 : Punctuation character not followed by a space.  Assume space.

C:\\adm\\copy\\ds-call.cpy (45,60-66) : warning COBCH1168 : COMP-5 redefinition.

C:\\adm\\copy\\pan2link.cpy (708,56-62) : warning COBCH1168 : COMP-5 redefinition.

a new directive must be used for sql: 

C:\\adm\\copy\\sqldb.cpy (52,22-23) : warning COBES0100 : SQL(BEHAVIOR) not set, BEHAVIOR=OPTIMIZED used as default

COBCH1140 VALUE in FILE or LINKAGE SECTION - only used with INITIALIZE statement.

COBCH1111 Boundary violation. Processed as written.

COBCH1168 COMP-5 redefinition.

Who can help solving this problems or answer this question?

Thanks

Hi.

To answer your installation issue.

Its not possible to have Micro Focus Visual COBOL for Visual Studio 2019 5.0 and Visual COBOL Built Tools installed on the same machine.

If you are planning on using the Docker installation then you just need to unzip the Docker files, vc_build_tools_dockerfiles_5.0_windows.zip, on your Docker Server machine.  Then run the bld.bat file found in the VCBuildTools sub directory.  This will take you through all the steps to setup VC Build Tools within a Docker container.  There is also a README file in this directory with all the details.

For your other questions:

The separate _BTRV.obj file that was used in Net Express is no longer required. The BTRV and _BTRV entry points have been moved to the file handler MFFH.DLL. This is loaded automatically at run-time whenever the first COBOL OPEN statement is executed on a file. If you are not opening any files via OPEN but are using the CALL "BTRV" instead then you might have to load this .dll manually. You can do this by adding the directive $SET INITCALL"MFFH" to your program.

There are some new warning messages in Visual COBOL that might not have appeared when compiling under Net Express. You also might have been setting a different value for the WARNING directive under NX than you are setting under VC so that warnings that did not appear under NX, do appear under VC.

You can set the directive $SET NOWARNING to turn off all warnings or you can selectively turn off warnings using the CHANGE-MESSAGE directive.

Example:  $SET CHANGE-MESSAGE"CH1168 N"

It looks to me like the compiler is finding a different version of the DS copy files than the default versions provided by Visual COBOL which are in the C:\\Program Files (x86)\\Micro Focus\\Visual COBOL\\cpylib folder.

Your error messages indicate that they are in C:\\adm\\copy\\ds-call.cpy

Are these the older NX versions?

I am not sure if these differ at all but you might try pointing to the default copyfile path for VC instead.

This is only a warning and does not indicate that the construct is obsolete at all. The warning is to inform you that redefining comp-5 fields can cause portability problems because of the different byte ordering between big-endian and little-endian systems. You can turn this off if this is not an issue for you.

It looks to me like the compiler is finding a different version of the DS copy files than the default versions provided by Visual COBOL which are in the C:\\Program Files (x86)\\Micro Focus\\Visual COBOL\\cpylib folder.

Your error messages indicate that they are in C:\\adm\\copy\\ds-call.cpy

Are these the older NX versions?

I am not sure if these differ at all but you might try pointing to the default copyfile path for VC instead.

This is only a warning and does not indicate that the construct is obsolete at all. The warning is to inform you that redefining comp-5 fields can cause portability problems because of the different byte ordering between big-endian and little-endian systems. You can turn this off if this is not an issue for you.