New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Large copybooks cannot be resolved #313
Comments
Can you and all the thumbs uppers conform that this is happening with z/OSMF only? Anyone observing this in RSE? The theory is that it is caused by zowe/zowe-cli#1920 and we had thought that we worked around it, but perhaps we missed a case. Investigating. |
Yes, using z/OSMF |
Hi, Is the copybook retrieved locally from the remote z/OS system truncated after a certain position, or is this a problem with handling the declarations present in the copybook after a certain position? For my part, I understand from the description of the issue that it is the treatment of the text replacement of the copybook by the COBOL Language Server which seems to be in question: from a certain position in the copybook, the replacement is no longer realized and all references by the COBOL program to statements after this position appear unresolved. The value 16742 reminds me of a storage capacity problem in a working variable of the Language Server, (developed in Java ?). |
As far as I am concerned, the copybook is not truncated. |
We believe we fixed this in v3.1.0. Please reopen if you still observe this behavior in the new version. |
java -version
and paste the details here): 11Problem Description
I have a cobol module that has a copy-statement to a copybook that contains the following:
Level 01: 1
Level 02: 108
Level 05: 351
Lines: 612
Total Characters: 27771
It will resolve everything in the copybook up untill Line: 370, 370 being excluded.
Amount of levels that can be resolved:
Level 01: 1
Level 02: 63
Level 05: 203
Lines: 369
Total Characters: 16742
Any reference to variablesnames inside my cobol module, that comes after line: 369 will be shown with the error: "Unable to resolve reference to SOMEVAR"
The text was updated successfully, but these errors were encountered: