Skip to main content

Same identical data file shows two different record lengths when accessed in Net Ex 3.1 vs. Visual COBOL.  See attached screen captures.  Have tried cleaning solution/project, reboot etc.  Currently seeing warning messages about Comp-5 redefinition.  I have another project in the solution with Comp-5 redef in the FD and I don't have an issue there.  Any idea why this would occur?

 

Select statement is as follows:

SELECT CASE-DBF ASSIGN TO DYNAMIC LOCCASEDBF

ORGANIZATION IS INDEXED

ACCESS IS DYNAMIC

LOCK MODE IS AUTOMATIC WITH LOCK ON RECORDS

RECORD KEY IS AIRRS-CDB-KEY

FILE STATUS IS FILE-STATUS.

 

Begin Net X Images

Begin Visual COBOL Images


#VisualStudio
#netexpress
#Comp-5
#VisualCOBOL
#Redefinition

Same identical data file shows two different record lengths when accessed in Net Ex 3.1 vs. Visual COBOL.  See attached screen captures.  Have tried cleaning solution/project, reboot etc.  Currently seeing warning messages about Comp-5 redefinition.  I have another project in the solution with Comp-5 redef in the FD and I don't have an issue there.  Any idea why this would occur?

 

Select statement is as follows:

SELECT CASE-DBF ASSIGN TO DYNAMIC LOCCASEDBF

ORGANIZATION IS INDEXED

ACCESS IS DYNAMIC

LOCK MODE IS AUTOMATIC WITH LOCK ON RECORDS

RECORD KEY IS AIRRS-CDB-KEY

FILE STATUS IS FILE-STATUS.

 

Begin Net X Images

Begin Visual COBOL Images


#VisualStudio
#netexpress
#Comp-5
#VisualCOBOL
#Redefinition

additonal images


#Redefinition
#Comp-5

Same identical data file shows two different record lengths when accessed in Net Ex 3.1 vs. Visual COBOL.  See attached screen captures.  Have tried cleaning solution/project, reboot etc.  Currently seeing warning messages about Comp-5 redefinition.  I have another project in the solution with Comp-5 redef in the FD and I don't have an issue there.  Any idea why this would occur?

 

Select statement is as follows:

SELECT CASE-DBF ASSIGN TO DYNAMIC LOCCASEDBF

ORGANIZATION IS INDEXED

ACCESS IS DYNAMIC

LOCK MODE IS AUTOMATIC WITH LOCK ON RECORDS

RECORD KEY IS AIRRS-CDB-KEY

FILE STATUS IS FILE-STATUS.

 

Begin Net X Images

Begin Visual COBOL Images


#VisualStudio
#netexpress
#Comp-5
#VisualCOBOL
#Redefinition

Hi, could you attach a file containing the SELECT and FD statements please?

Same identical data file shows two different record lengths when accessed in Net Ex 3.1 vs. Visual COBOL.  See attached screen captures.  Have tried cleaning solution/project, reboot etc.  Currently seeing warning messages about Comp-5 redefinition.  I have another project in the solution with Comp-5 redef in the FD and I don't have an issue there.  Any idea why this would occur?

 

Select statement is as follows:

SELECT CASE-DBF ASSIGN TO DYNAMIC LOCCASEDBF

ORGANIZATION IS INDEXED

ACCESS IS DYNAMIC

LOCK MODE IS AUTOMATIC WITH LOCK ON RECORDS

RECORD KEY IS AIRRS-CDB-KEY

FILE STATUS IS FILE-STATUS.

 

Begin Net X Images

Begin Visual COBOL Images


#VisualStudio
#netexpress
#Comp-5
#VisualCOBOL
#Redefinition

Attached casedbf_sl_fd.txt.

Same identical data file shows two different record lengths when accessed in Net Ex 3.1 vs. Visual COBOL.  See attached screen captures.  Have tried cleaning solution/project, reboot etc.  Currently seeing warning messages about Comp-5 redefinition.  I have another project in the solution with Comp-5 redef in the FD and I don't have an issue there.  Any idea why this would occur?

 

Select statement is as follows:

SELECT CASE-DBF ASSIGN TO DYNAMIC LOCCASEDBF

ORGANIZATION IS INDEXED

ACCESS IS DYNAMIC

LOCK MODE IS AUTOMATIC WITH LOCK ON RECORDS

RECORD KEY IS AIRRS-CDB-KEY

FILE STATUS IS FILE-STATUS.

 

Begin Net X Images

Begin Visual COBOL Images


#VisualStudio
#netexpress
#Comp-5
#VisualCOBOL
#Redefinition

Further checking, I have at least one other file with the same situation.  The copybooks used in Net Ex included the directive $set DATACOMPRESS"1" and $set NODATACOMPRESS"1" .  Could this be the issue?  I am attaching the original copybooks for the Select and FD as well.

 

Same identical data file shows two different record lengths when accessed in Net Ex 3.1 vs. Visual COBOL.  See attached screen captures.  Have tried cleaning solution/project, reboot etc.  Currently seeing warning messages about Comp-5 redefinition.  I have another project in the solution with Comp-5 redef in the FD and I don't have an issue there.  Any idea why this would occur?

 

Select statement is as follows:

SELECT CASE-DBF ASSIGN TO DYNAMIC LOCCASEDBF

ORGANIZATION IS INDEXED

ACCESS IS DYNAMIC

LOCK MODE IS AUTOMATIC WITH LOCK ON RECORDS

RECORD KEY IS AIRRS-CDB-KEY

FILE STATUS IS FILE-STATUS.

 

Begin Net X Images

Begin Visual COBOL Images


#VisualStudio
#netexpress
#Comp-5
#VisualCOBOL
#Redefinition

Further checking, I have at least one other file with the same situation.  The copybooks used in Net Ex included the directive $set DATACOMPRESS"1" and $set NODATACOMPRESS"1" .  Could this be the issue?  I am attaching the original copybooks for the Select and FD as well.

 

Same identical data file shows two different record lengths when accessed in Net Ex 3.1 vs. Visual COBOL.  See attached screen captures.  Have tried cleaning solution/project, reboot etc.  Currently seeing warning messages about Comp-5 redefinition.  I have another project in the solution with Comp-5 redef in the FD and I don't have an issue there.  Any idea why this would occur?

 

Select statement is as follows:

SELECT CASE-DBF ASSIGN TO DYNAMIC LOCCASEDBF

ORGANIZATION IS INDEXED

ACCESS IS DYNAMIC

LOCK MODE IS AUTOMATIC WITH LOCK ON RECORDS

RECORD KEY IS AIRRS-CDB-KEY

FILE STATUS IS FILE-STATUS.

 

Begin Net X Images

Begin Visual COBOL Images


#VisualStudio
#netexpress
#Comp-5
#VisualCOBOL
#Redefinition

Original Case FD

Same identical data file shows two different record lengths when accessed in Net Ex 3.1 vs. Visual COBOL.  See attached screen captures.  Have tried cleaning solution/project, reboot etc.  Currently seeing warning messages about Comp-5 redefinition.  I have another project in the solution with Comp-5 redef in the FD and I don't have an issue there.  Any idea why this would occur?

 

Select statement is as follows:

SELECT CASE-DBF ASSIGN TO DYNAMIC LOCCASEDBF

ORGANIZATION IS INDEXED

ACCESS IS DYNAMIC

LOCK MODE IS AUTOMATIC WITH LOCK ON RECORDS

RECORD KEY IS AIRRS-CDB-KEY

FILE STATUS IS FILE-STATUS.

 

Begin Net X Images

Begin Visual COBOL Images


#VisualStudio
#netexpress
#Comp-5
#VisualCOBOL
#Redefinition

original caseque FD

Same identical data file shows two different record lengths when accessed in Net Ex 3.1 vs. Visual COBOL.  See attached screen captures.  Have tried cleaning solution/project, reboot etc.  Currently seeing warning messages about Comp-5 redefinition.  I have another project in the solution with Comp-5 redef in the FD and I don't have an issue there.  Any idea why this would occur?

 

Select statement is as follows:

SELECT CASE-DBF ASSIGN TO DYNAMIC LOCCASEDBF

ORGANIZATION IS INDEXED

ACCESS IS DYNAMIC

LOCK MODE IS AUTOMATIC WITH LOCK ON RECORDS

RECORD KEY IS AIRRS-CDB-KEY

FILE STATUS IS FILE-STATUS.

 

Begin Net X Images

Begin Visual COBOL Images


#VisualStudio
#netexpress
#Comp-5
#VisualCOBOL
#Redefinition

original caseque FD

Same identical data file shows two different record lengths when accessed in Net Ex 3.1 vs. Visual COBOL.  See attached screen captures.  Have tried cleaning solution/project, reboot etc.  Currently seeing warning messages about Comp-5 redefinition.  I have another project in the solution with Comp-5 redef in the FD and I don't have an issue there.  Any idea why this would occur?

 

Select statement is as follows:

SELECT CASE-DBF ASSIGN TO DYNAMIC LOCCASEDBF

ORGANIZATION IS INDEXED

ACCESS IS DYNAMIC

LOCK MODE IS AUTOMATIC WITH LOCK ON RECORDS

RECORD KEY IS AIRRS-CDB-KEY

FILE STATUS IS FILE-STATUS.

 

Begin Net X Images

Begin Visual COBOL Images


#VisualStudio
#netexpress
#Comp-5
#VisualCOBOL
#Redefinition

Original caseque Select.  This file has the same record length issue.

Same identical data file shows two different record lengths when accessed in Net Ex 3.1 vs. Visual COBOL.  See attached screen captures.  Have tried cleaning solution/project, reboot etc.  Currently seeing warning messages about Comp-5 redefinition.  I have another project in the solution with Comp-5 redef in the FD and I don't have an issue there.  Any idea why this would occur?

 

Select statement is as follows:

SELECT CASE-DBF ASSIGN TO DYNAMIC LOCCASEDBF

ORGANIZATION IS INDEXED

ACCESS IS DYNAMIC

LOCK MODE IS AUTOMATIC WITH LOCK ON RECORDS

RECORD KEY IS AIRRS-CDB-KEY

FILE STATUS IS FILE-STATUS.

 

Begin Net X Images

Begin Visual COBOL Images


#VisualStudio
#netexpress
#Comp-5
#VisualCOBOL
#Redefinition

If you add the IBMCOMP directive to the additional directives you should see the record size match NX 3.1.

NX 5.1 and Visual COBOL do not have the IBMCOMP directive on by default.

Same identical data file shows two different record lengths when accessed in Net Ex 3.1 vs. Visual COBOL.  See attached screen captures.  Have tried cleaning solution/project, reboot etc.  Currently seeing warning messages about Comp-5 redefinition.  I have another project in the solution with Comp-5 redef in the FD and I don't have an issue there.  Any idea why this would occur?

 

Select statement is as follows:

SELECT CASE-DBF ASSIGN TO DYNAMIC LOCCASEDBF

ORGANIZATION IS INDEXED

ACCESS IS DYNAMIC

LOCK MODE IS AUTOMATIC WITH LOCK ON RECORDS

RECORD KEY IS AIRRS-CDB-KEY

FILE STATUS IS FILE-STATUS.

 

Begin Net X Images

Begin Visual COBOL Images


#VisualStudio
#netexpress
#Comp-5
#VisualCOBOL
#Redefinition

This was successful, thank you for the help.

Terms & ConditionsAccessibility statement