Skip to main content

I would like to open the main COBOL program and drill down to the copybooks, then the IDE “remembers” the variables used in the main program and don’t mark them as unused (strikethrough), but if this feature is “faraway” I would suggest to be able to turn off the feature only for copybooks.

I would like to open the main COBOL program and drill down to the copybooks, then the IDE “remembers” the variables used in the main program and don’t mark them as unused (strikethrough), but if this feature is “faraway” I would suggest to be able to turn off the feature only for copybooks.

We added a new feature in Visual COBOL 2.0 which hopefully resolves this issue for you.

Look at the documentation on COBOL Copybook Context here:

If you open the copybook in context to the main program that it is in then variables that are referenced will not appear with the strikeout through them.

The COBOL Explorer View documentation can be found here:

Thanks.

I would like to open the main COBOL program and drill down to the copybooks, then the IDE “remembers” the variables used in the main program and don’t mark them as unused (strikethrough), but if this feature is “faraway” I would suggest to be able to turn off the feature only for copybooks.

I have tested and the function worked on local projects but not on remote projects.

I would like to open the main COBOL program and drill down to the copybooks, then the IDE “remembers” the variables used in the main program and don’t mark them as unused (strikethrough), but if this feature is “faraway” I would suggest to be able to turn off the feature only for copybooks.

I have tested and the function worked on local projects but not on remote projects.

I would like to open the main COBOL program and drill down to the copybooks, then the IDE “remembers” the variables used in the main program and don’t mark them as unused (strikethrough), but if this feature is “faraway” I would suggest to be able to turn off the feature only for copybooks.

We tested this on a remote project also and it appears to work fine as long as you are opening the copybook in the Content of the main program that is referencing the data item.

We tested on Visual COBOL Eclipse 2.0 for Windows connected to Visual COBOL Dev Hub 2.0 on Redhat 5.5.

What is your system configuration?

Terms & ConditionsAccessibility statement