AMT 82
Released: 05 Feb 2021.
For availability, please contact the Avanade Service Portal for information on downloading new releases.
Special attention items:
AMT 82
- C2101-043 – Moving a multi-item array into a single variable is not allowed anymore. Please check your AMT COBOL programs to see if this affects your code!
- 330168 – Array-items now set as elements instead of array-items if ElementFormDefault is set to unqualified. A ‘Reload WSDL’ is required for all your CWS!
Product | Cat | Subcat | Description | Type | Version | Priority |
---|---|---|---|---|---|---|
AMT LION | Runtime | AmtScreens | 329990 Information/error popups could be hard to read in AMT Screens. First steps have now been taken to allow users to adjust fonts in AMT Screens in Local Settings, resulting in better readability of system information in AMT Screens. |
FIX | AMT 82 | Low |
AMT LION | Runtime | AmtScreens | 329742 AMT Screens did not accept a '0' in an Editbox as a decimal character with Forcedecimalkeys set to True, whereas LionScreens always converted '0' to a decimal character. AMT Screens now also converts '0' to a decimal character in all cases. |
FIX | AMT 82 | Medium |
AMT LION | AMT COBOL | Control Center | Security | C2012-056 The security module in the ASP.NET version of the AMT Control Center relied on multiple cookies to track AMT sessions. A new security module has been created for the forthcoming AMT ASP.NET Core Control Center, which does not rely on these cookies, but uses session keys in the System database instead. |
CHANGE | AMT 82 | High |
AMT COBOL | Developer | Code Logic | 330060, 330123 Fix on COBOL EVALUATE statement: when fractional values are used, C# 'if/else if' is now generated instead of 'switch...case' in order to avoid C# errors. Fix on COBOL 88-level condition: a C# error on PIC 9 generation was caused by a missing check on Alpha variables; this check has now been added. Fix on COBOL COMPUTE statement: all parts in a COMPUTE statement are now checked on being numeric. Fix on COBOL numeric variable declaration: warnings/errors appear when a non-numeric value is specified (an error where a C# error would result, a warning in other cases). |
FIX | AMT 82 | High |
AMT COBOL | Runtime | Various | 330122 In the AMT Application Center, if all sessions were used, it should be possible to clean up sessions. This did not work anymore. This has been resolved; sessions can now be cleaned up again and a new session can then be opened to work in. |
FIX | AMT 82 | Medium |
AMT LION | Developer | Various | C2012-106 Support for creating constructors on classes has been added. This logic is applied whenever a global or local class is created, with the exception of deserialization with FromXml/FromJson. Also, the Class window now shows the routines tree node. |
NEW | AMT 82 | Medium |
AMT LION | Developer | Web Services | 330185 Web services raised generation errors 'No element was found' and 'Double to Decimal cast error'. Request was wrapped but detected as unwrapped and a decimal was generated instead of a double, both issues have been corrected. |
FIX | AMT 82 | High |
AMT LION | Runtime | Web Client | 329578 If an invalid date was entered in the Calender by setting a value in LION code, '//' was shown. The validation of Date values has been altered so that, if an invalid date is entered, the last saved valid Date or 'empty' is shown. |
FIX | AMT 82 | Low |
AMT LION | Developer | Web Services | 329978 Request class name could not be empty when a WSDL for a Consumable Web service was read, as Document Literal Wrapped and Unwrapped were not detected correctly. Wrapped and unwrapped Soap services are now correctly detected. |
FIX | AMT 82 | High |
AMT LION | AMT COBOL | Developer | Various | C2101-028 The AMT Developer (LionDev.exe) and AMT Generator (LionDevGenNet.exe) reported the absence of 'Microsoft.AspNetCore.App', but as neither executable is an ASP.NET Core application, 'Microsoft.AspNetCore.App' is not required. The AMT Developer and AMT Generator both had a dependency on a project that required the 'Microsoft.AspNetCore.App'; this dependency has now been removed. |
FIX | AMT 82 | Medium |
AMT LION | Generator | Various | 330167 WSDL namespace reading had 2 issues: 1. Namespaces of individual elements within complex types were not used. 2. Namespaces of Message Parts were not used. Both issues have been resolved, by using parameter element namespace and message part namespace (located in Soap message body), respectively. |
FIX | AMT 82 | High |
AMT COBOL | Runtime | Various | 330044 / C2101-035 AMT COBOL online 2200 transaction did not work, input fields were not sent to the AMT Transaction Server. AMT COBOL online 2200 transaction now works again, the check on form-name / transaction-name has been corrected. |
FIX | AMT 82 | High |
AMT LION | AMT COBOL | AmtTools | Reo | 329246 The AMT Reorganize program in batch mode had a sequence problem, the Reorganize actions were done before the Analyse phase had been completed. The Analyse is now completed before the Reorganize actions are started. |
FIX | AMT 82 | High |
AMT LION | Developer | Web Services | 330209 Reading WSDL was not working correctly with nested types and caused invalid routine parameters. Reading WSDL has now been improved for Document Literal by better reading of nested types. |
FIX | AMT 82 | Medium |
AMT LION | Runtime | Various | 330162 If a WSDL contained an empty Soap-action, AMT incorrectly forced it to be filled, whereas the provider expected it to be empty. This issue has been resolved by making it impossible for the user to force a Soap-action and then leave it empty. |
FIX | AMT 82 | High |
AMT COBOL | Runtime | Various | 330171 / 330224 / 330077 / C2101-043 Moving a whole array into a single variable resulted in exceptions in AMT at runtime. Moving a whole array into a single variable is not allowed anymore. It is not supported by official COBOL standards, except if the array only contains one element. The AMT COBOL parser has been changed to Error if moving a whole array to a singled item, and to provide a warning if moving an array with one element. This change may mean that some COBOL programs need to be changed when upgrading to AMT 82 or beyond. |
CHANGE | AMT 82 | High |
AMT LION | Developer | Web Services | 330100 / 329323 Only Soap bindings are supported by AMT, so from now on when the WSDL is (re)loaded, all unsupported bindings are skipped. |
FIX | AMT 82 | High |
AMT COBOL | Generator | Various | 330240 / C2101-051 SELECT CURRENT_TIMESTAMP query in AMT COBOL did not execute, because of optimizations for IBM COBOL. The generator has been changed, it now additionally checks if the query has been performed on SYSDUMMY1, if not, the query is executed after all. |
FIX | AMT 82 | High |
AMT LION | AMT COBOL | Control Center | Security | 330243 Creating a user in the forthcoming ASP.NET Core version of the AMT Control Center did not work properly and caused freezes and crashes in the web API. The issue has been resolved by calling the correct member in AmtMembershipProviderService.CreateUser. |
FIX | AMT 82 | Medium |
AMT LION | AMT COBOL | Control Center | Various | 330218 Adding job schedules and several other actions did not work properly in the forthcoming ASP.NET Core version of the AMT Control Center, and raised error messages. The issues have been resolved by fixing issues in JavaScript, JSON and Ajax implementations. |
FIX | AMT 82 | Medium |
AMT COBOL | Developer | Code Logic | 330215 / C2101-062 When commenting out code, the part of the code text after the word PIC stayed in its 'active' text colour. When code is commented out, the entire line now changes into green text. |
FIX | AMT 82 | Medium |
AMT LION | AMT COBOL | Runtime | Various | 330285 / 330286 / C2101-064 The changes that made for the migration of several AMT components to .NET Core were causing problems with some of the consumable and provided webservices, due to the mixture of .NET Framework and .NET Core assemblies in the ..\Lion\Support\ folders. The .NET Framework and .NET Core assemblies in the ..\Lion\Support\ folders have now been separated. This resolves the problems with the consumable and provided webservices. |
FIX | AMT 82 | High |
AMT LION | AMT COBOL | AmtTools | Reo | C2101-065 System databases created with AMT versions 69-76 could have DECIMAL(9,0) field types instead of INTEGER. Changes for C2010-096 triggered an AMT Reorganize on these fields, resulting in errors. With this fix AMT Reorganize is not triggered anymore. |
FIX | AMT 82 | High |
AMT LION | AMT COBOL | AmtTools | Prodinstall/Pinstall | 330262 ProdInstall/PInstall 'Enabled' state was changed too early between different phases of the process, resulting in the use of a wrong set of data for a following phase. The timing of updating the 'Enabled' state has been corrected. |
FIX | AMT 82 | Medium |
AMT COBOL | Runtime | Various | 330182 / C2101-067 The AMT Transaction Agent loaded the FormsDefinition.dll from the Server\Bin folder. The AMT Transaction Agent now loads the FormsDefinition.dll from the working folder, so this dll can be renewed for new generations, while the AMT Transaction Server remains running. |
FIX | AMT 82 | Medium |
AMT LION | Runtime | Various | 329617 Namespace was missing for complex type array-items. Namespaces have been added for array-items that are complex types. |
FIX | AMT 82 | High |
AMT LION | Generator | Various | 330168 Array-items are now set as elements instead of array-items if ElementFormDefault is set to unqualified. In order for this and the other web service issues to result in a correct generation, a 'Reload WSDL' is required for all consumable webservices. |
FIX | AMT 82 | High |
AMT LION | Developer | Web Services | 330209 In the Consumable Web Service definitions, some classes were created/written (by clicking (re)load WSDL) that were never used, which could cause generation errors. In the new version of CWS definitions, each class is checked for actual use, before being written to the definitions. |
FIX | AMT 82 | Medium |
AMT LION | AMT COBOL | Runtime | Various | C2101-102 Since AMT 81, the Forms Authentication method was no longer working for the AMT Application Center and AMT Control Center. This issue was introduced by changes for the migration of the AMT Application Center to .NET Core (C2011-032). The issue has been resolved by reverting some of the changes. |
FIX | AMT 82 | Medium |