AMT 166
Released: 09 Jan 2026.
For availability, please contact the Avanade Service Portal for information on downloading new releases.
Special attention items:
There are no special attention items for this release.
| Product | Cat | Subcat | Description | Type | Version | Priority |
|---|---|---|---|---|---|---|
| AMT LION | Debugger | Various | #84010
Previously, when debugging a Lion form in LionDebugger through AMT Screens or a web browser, closing the form caused the debugger buttons to remain locked. Users had to disconnect and reconnect before they could debug again. We’ve improved this process: now, when you close the browser tab or AMT Screens session, the debugger buttons reset automatically. This means you can start a new debugging session right away without extra steps. |
FIX | AMT 166 | MEDIUM |
| AMT COBOL | Developer | Code Logic | #96798
In AMT COBOL, adding parentheses around parts of an EXEC DB2 query previously caused parsing errors. The parser has been updated to correctly handle parentheses before SELECT statements, ensuring accurate interpretation of queries that include grouped expressions. |
FIX | AMT 166 | MEDIUM |
| AMT COBOL | Developer | Code Logic | #96800
Previously, PL/SQL-style comments (using --) were not correctly recognized in AMT COBOL EXEC ORACLE sections. This caused the parser to ignore the comment and the remainder of the line, which could lead to incomplete or incorrect processing of SQL statements. We’ve updated the parser to properly handle PL/SQL comments, ensuring that your Oracle code is parsed accurately and behaves as expected. |
CHANGE | AMT 166 | MEDIUM |
| AMT COBOL | Developer | Code Logic | #97538
The parser in AMT COBOL did not recognize SQL comments using the /* ... */ notation, which caused errors whenever comments were included in SQL code. We’ve improved the parser so that SQL comments are now safely ignored during processing. This means your SQL code with comments will no longer trigger errors. |
FIX | AMT 166 | MEDIUM |
| AMT COBOL | Generator | Various | #97594
The COBOL statement SELECT NEXT VALUE FOR RDS_CONTROL_NBR_SEQ was being converted incorrectly for PostgreSQL. The AMT Generator now correctly converts COBOL statements that retrieve the next sequence value into database-specific syntax. For example, SELECT NEXT VALUE FOR RDS_CONTROL_NBR_SEQ is now properly converted to SELECT nextval('RDS_CONTROL_NBR_SEQ') for PostgreSQL. Improvements for sequence handling have been applied for DB2 and other supported databases, ensuring accurate and consistent sequence handling across platforms. |
FIX | AMT 166 | MEDIUM |
| AMT LION | AMT COBOL | Control Center | Various | #98047
When passing parameters from the StartJob section in ControlCenter, negative values were incorrectly interpreted as PowerShell parameter names. This has been fixed by adding a validation check: if the part after the hyphen is numeric, it’s treated as a value rather than a parameter name. This ensures accurate distinction between parameter names and values. |
FIX | AMT 166 | MEDIUM |
| AMT COBOL | Developer | Code Logic | #98085
The parser in the AMT COBOL now correctly processes EXEC DB2 SELECT statements that include the QUERYNO clause followed by additional keywords such as FOR FETCH ONLY. Previously, the parser stopped parsing after encountering QUERYNO, which caused errors like “Word FETCH not understood.” The parser has been updated to ignore QUERYNO and continue parsing the full statement, ensuring accurate handling of DB2 syntax. |
FIX | AMT 166 | MEDIUM |
| AMT COBOL | Developer | Code Logic | #98246
The AMT COBOL parser now correctly handles READ statements that include both AT END and NOT AT END clauses. Previously, this combination caused parsing errors because NOT AT END was misinterpreted as other NOT clauses. The parser has been updated to accurately recognize these clauses, ensuring reliable processing of COBOL READ statements. |
CHANGE | AMT 166 | MEDIUM |
| AMT COBOL | Developer | Code Logic | #98418
The parser in AMT COBOL incorrectly added COBOL variables from COPY statements to parameterized SQL queries, which caused invalid SQL method invocations. We fixed this by removing the logic that parsed copy node markers and updating the parsing logic to handle structures without explicit children. These changes ensure the generator creates accurate COPY statements and SQL queries. |
FIX | AMT 166 | MEDIUM |