You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today I can setup truncation limit for COBOL, HLASM, JCL, REXX and PL1.
We also use Vscode with Zowe Explorer and z Open Editor for DDL, SQL and more and have a limitation of 72 characters for DDL and SQL.
Is it possible for you to add a function so we can add truncation warnings for more types like DDL, SQL etc.?
Looking very much forward to hear from you.
Lars Egeberg.
The text was updated successfully, but these errors were encountered:
As far as I know, IBM Z Open Editor can only intervene on the languages with which it is associated.
SQL as such is not part of them, although there is partial support for SQL embedded in another supported language.
Furthermore, regarding the control of line lengths, it seems to me that this functionality is delegated to the Language Server.
For pure SQL language, I would suggest addressing the issue to the excellent IBM Db2 for z/OS Developer extension, which fully manages the SQL language, whether DML or DDL, and also allows you to execute SQL queries or query the Db2 catalog.
As for IBM Z Open Editor, it seems to me that there are more priority needs such as support for the Java language, and by extension Groovy, in a z/OS-USS context, and the C/C++ language, also in a z/OS-USS context.
Also see for Python which seems to want to develop on z/OS-USS.
For these different languages there are VS Code extensions but they ignore the IBM z/OS context.
Hi IBM.
Today I can setup truncation limit for COBOL, HLASM, JCL, REXX and PL1.
We also use Vscode with Zowe Explorer and z Open Editor for DDL, SQL and more and have a limitation of 72 characters for DDL and SQL.
Is it possible for you to add a function so we can add truncation warnings for more types like DDL, SQL etc.?
Looking very much forward to hear from you.
Lars Egeberg.
The text was updated successfully, but these errors were encountered: