Skip to content
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

PL1 Column 1 Significance #21

Open
asatklichov opened this issue Jan 20, 2025 · 0 comments
Open

PL1 Column 1 Significance #21

asatklichov opened this issue Jan 20, 2025 · 0 comments
Assignees
Labels
priority-medium Should be resolved in 1-3 sprints severity-low A bug that makes the usage of the Zowe less convenient but doesn't impact key use cases

Comments

@asatklichov
Copy link

These special columns should be detected and ignored. Typically, source code (PL/I statements) appears between columns 2–72.
Column 1 is for printer control and columns 73–80 for sequence numbers. The source code may indicate its own format with a line such as *PROCESS MARGINS(2,72) [compiler option]. In many cases, this line doesn't exist, and the columns are either defined with a compiler switch or system default values are used.

Currently, If we use Column 1 - PL/I compiler gives an error like "The END statement has no matching BEGIN, DO, PACKAGE, PROC, or SELECT. This may indicate a problem with the syntax of a previous statement..."

VSCode extension gives different errors once you use Col1:
"Could not resolve reference to LabelPrefix named ..." or "Expecting token of type ':' but found ..." maybe there are more.

In this case we need to validate column 1 with error message like "Column 1 is reserved by PL/1 for internal usage, please start coding from Column 2" once user uses Col1 for coding.

@asatklichov asatklichov added severity-low A bug that makes the usage of the Zowe less convenient but doesn't impact key use cases severity-medium A bug where workaround exists or that doesn't prevent the usage of the Zowe or the use case priority-medium Should be resolved in 1-3 sprints and removed severity-medium A bug where workaround exists or that doesn't prevent the usage of the Zowe or the use case labels Jan 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority-medium Should be resolved in 1-3 sprints severity-low A bug that makes the usage of the Zowe less convenient but doesn't impact key use cases
Projects
None yet
Development

No branches or pull requests

2 participants