Compiler error VC 5.0 only release

only release mode

Please provide more detail as to what you are doing and what error you are receiving.

There are copybooks missing that are referenced by the copybooks that are present so I cannot compile the program.

Please upload all required copybooks.

Thanks.

here a new zip with all copybooks!

only in release mode Comes this Errors/warnings with vc5.0

I also need copy "typen.cpy".

Thanks

new xy.zip included with "typen.cpy"

Sorry for my failure!

Thanks Chris!

This compiles fine for me in both Debug and Release configurations.

Using VC 5.0 PU3 I created a 32-bit native console project, added the files to it and compiled using the default directives.

What is the error you are receiving?

Can you provide me with any additional directives you might be using?

Chris,

i have only PU2 at disposition!

Where can i download pu3?

Here the errors:

Compiling C:\\adm\\cbl\\ADRESS.CBL
C:\\adm\\gxcopy\\DATIO.CPY (256,34-42) : warning COBCH1111 : Boundary violation. Processed as written.

C:\\adm\\gxcopy\\DATIO.CPY (672,48-57) : warning COBCH1111 : Boundary violation. Processed as written.

First warning:

           if B-LtzReadOk-m                               and
              xSatz-l (K-POS-KEY0:K-LG-KEY0) = DATEI-Key0

it mus be xSatz-l (K-POS-KEY0:K-LG-KEY0)

Second warning:

                    string K-DATEI " : Eintrag nicht vorhanden ("
                           xSatz-l (K-POS-KEY0:K-LG-KEY0) ")"
                           delimited size into xStatustext-l

it must be xSatz-l (K-POS-KEY0:K-LG-KEY0) ")"

Those are not errors, they are warnings and I get them too in both Debug and Release builds but only if I change my project warning level to include warnings.

These are valid warnings that the code might cause a problem at run-time. You are specifying reference modification on a one byte PIC X field to include 7 characters. (1:7).

Since the field is only one byte long this could cause an error at runtime. The field is in the linkage section so you are probably setting the address dynamically or you are passing in a parameter that is longer than one byte which is perfectly valid to do.

If you do not wish to be informed of this potential issue then you can turn this off with the compiler directives that I specified previously.

NOWARNINGS
or
CHANGE-MESSAGE"CH1111 N"

If you are using a Visual COBOL project then you could simply change the list box on the COBOL tab of the property page so that the warning level does not include warnings.