AMT 164
Released: 28 Nov 2025.
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 COBOL | Developer | Code Logic | #85778
In AMT COBOL, a conditional expression consisting of SPACE(S) & Integers wasn't allowed. For example (SPACES AND 12). The parser was updated to allow such combinations. |
FIX | AMT 164 | MEDIUM |
| AMT LION | AMT COBOL | Generator | Various | #87019
We’ve separated the AMT Generator’s business logic into a dedicated AMT Generator Business Logic Library. This is an important step toward making AMT Generator cross-platform and easier to integrate into automated pipelines. |
CHANGE | AMT 164 | MEDIUM |
| AMT LION | AMT COBOL | Developer | Code Logic | #96310
SQL smallint data types were not supported for stored procedures in the AMT Developer Studio. We added smallint data type to the generator and parser. |
NEW | AMT 164 | MEDIUM |
| AMT LION | Debugger | Various | #96819
INC: 1371504 Previously, when debugging an AMT Lion form that used a routine from a global class, customers were unable to step into the class routine. Additionally, the debug file for the class would not open. We’ve fixed this issue so that when the class is generated in debug mode, its debug file loads correctly. Customers can now step into the class routine and debug all lines of code as expected. |
FIX | AMT 164 | MEDIUM |
| AMT LION | Runtime | AMT Screens | #96940
INC: 1354824 When refreshing a form in AMT Screens that contains encrypted fields, an exception occurred: “Invalid hex value in string.” This suggests the system tried to decrypt a field twice. The second attempt to decrypt the field value in the AMT library code was removed. This prevents the error from happening during form refresh. |
FIX | AMT 164 | MEDIUM |
| AMT COBOL | Generator | Code Logic | #97022
A mismatch between host variable types and database column types caused inconsistencies during processing of AMT COBOL EXEC DB2 statements. We’ve fixed this by ensuring the host variable type is overridden to match the column type, improving data consistency and preventing errors. |
FIX | AMT 164 | MEDIUM |
| AMT COBOL | Developer | Code Logic | #97510
The AMT COBOL parser incorrectly added empty parentheses () for column names when parsing EXEC DB2 INSERT INTO statements without specified columns. We’ve fixed this so that empty parentheses are no longer added when no columns are specified in the INSERT INTO statement. |
FIX | AMT 164 | MEDIUM |
| AMT COBOL | Generator | Code Logic | #97640
In AMT COBOL, host variables were not generated in SQL Common Table Expression (CTE) sections, leading to incomplete SQL statements. We’ve fixed this issue so that host variables are now properly generated within CTE sections. |
FIX | AMT 164 | MEDIUM |
| AMT COBOL | Generator | Code Logic | #97644
In AMT COBOL, EXEC DB2 statements with subqueries in the FROM clause were missing comma separators, resulting in invalid SQL syntax. We’ve fixed this issue so that the generator now correctly adds comma separators for subqueries in the FROM clause. |
FIX | AMT 164 | MEDIUM |