AMT 40
Released: 20 Aug 2018.
For availability, please contact the Avanade Service Portal for information on downloading new releases.
Special attention items:
AMT 40
- Due to changes to the AMT framework tables the REO will throw a warning with the message: “The field length is smaller” and “this field will be truncated”. Note that this is thrown due to changes in the AMT Framework tables and they will be truncated due to this change. This won’t affect user data. The REO does need to perform changes to all databases.
| Product | Cat | Subcat | Description | Type | Version | Priority |
|---|---|---|---|---|---|---|
| Various | Various | C1807-093 The usage of pointer variables inside structures is causing null reference exceptions on runtime. The problem was that the (initial) value of the pointer variables is set by using the Value property, just before the memory is allocated, which is causing a null reference exception. This has been resolved. | AMT 40 | |||
| Developer | Various | AMT LION 314826 The shapes in the AMT Dev Studio look different than they do in LIONScreens and the web client Shapes in the AMT Dev Studio would have a different appearance than they would in LIONScreens (the desktop client) or the web client, making it difficult for Developers to create exactly what they required. In this version, AMT 40, the AMT Dev Studio has been adjusted so that the AMT Dev Studio displays the same as in the AMTscreens and LIONScreens client. The display of forms in the Web application has also been improved to match exactly what you see in the AMT Dev Studio. We have also improved the display of forms in the Web application to match up with what you see in the AMT Dev Studio as well. Please note that Internet Explorer and Edge will still deviate a bit from what you see in the view of the AMT Dev Studio. In these browsers the raised and sunken edges won't be clearly noticeable. | AMT 40 | |||
| Runtime | AMTScreens | AMT LION C1805-049 Start Report functionality in AmtScreens (still in preview) The Start Report screen in AmtScreens (still a preview) has been renamed Start Job to be consistent with Control Center. Furthermore, the functionality has been added, as available in LIONScreens already. It is now possible to start reports, scripts, executable files and more from this screen. The look and feel should otherwise be much the same as the previous LIONScreens Start Report screen. | AMT 40 | |||
| Developer | Various | ALL 326467 The Security section of the AMT Dev Studio would show incorrect Authorization information and inappropriately enabled the buttons When a new user group was added within the security window (SEC), one would observe undesirable behaviour. When one subsequently opens this group in the 'access' tab in a specific generation set, one would first see the checkboxes uncheck as supposed to, yet, when one would subsequently scroll down it would stand out that the "select Generation priority" and "enable get all newest" are unintentionally checked. After scrolling up "look into" would also be unintentionally checked. The behaviour of the security section has been corrected. Permissions will now work as supposed and the checkboxes are only checked when supposed to. | AMT 40 | |||
| Migration | Various | All 1807-019 Changes to improve the performance of FreeJoin- and RDMS-Queries and the TransactionServer. Changes have been made to the way the backend logic that creates FreeJoin Queries (AMT-LION) and RDMS Queries (AMT-COBOL) to provide improved performance. In addition, changes have beeen made to the transaction server to improve the performance. - Migrated IBM CICS LINK, calls are now loaded and run in the same thread as the calling program, rather than a new thread, which improves performance. - MSMQ connection between the transaction server and transaction agent, are now read in a synchronised way. This gives better reliabillity unders stress, and performance is also improved. | AMT 40 | |||
| Generator | Various | AMT COBOL and AMT VS C1807-044 AMT Generator consumes huge amounts of memory generating AMT COBOL to AMT VS. The AMT Generator was consuming a huge amount of memory, when generating an AMT COBOL application for VS. This was caused due to the amount of data that was stored in memory for every data/procedure division copy. By storing only the data that is really needed, the amount of memory used by the AMT generator is reduced. This change will have no affect on existing AMT-COBOL customers. It will only bring about new migration projects when moving to AMT-COBOL-VS. | AMT 40 | |||
| Migration | COBOL | AMT COBOL C1807-047 Migrated DB2 functions CHAR and SUBSTR now supported in AMT COBOL with MS SQL Server AMT COBOL now supports migrated DB2 functions, that will be mostly used in migrated IBM applications, like CHAR and SUBSTR on an MS SQL database when used in an EXEC SQL command. | AMT 40 | |||
| Migration | COBOL | AMT COBOL C1807-048 Support of two new DB2 Structures added to migrated IBM applications. Support for two new embedded SQL is added for two IBM DB2 functions in AMT COBOL. In embedded SQL for applications migrated from IBM DB2, it is now possible to use a group, a structure, as a hostvar to service a number of fields in the query. Support of special structure used for variable length character fields is now added. This group consists of 2 level 49 fields in the COBOL, the first a S9(4) COMP contains the length of the field and the second, PIC X(n) contains the data. | AMT 40 | |||
| Runtime | Web Client | AMT LION 326835 Fontsettings for listview rows and cells can now be dynamically changed during the runtime. It is now possible to dynamically change the Font settings (Bold,Colour, Italic, Fontname, Fontsize and Underline) in Runtime for single rows or cells. For instance, the following Font settings can now be set for single rows and/or cells of a listview: E.G. for rows: listview_1.items[1].fontbold or for cells: listview_1.items[1].fontcolor[2] If you would like to learn more about this, please check the helpsite for more information. https://help.myasysco.com/lion/listview.html | AMT 40 | |||
| Developer | Code Logic | AMT COBOL 326624 Quick access to section names didn't work in the SORT statement. Double clicking on the section / label used in the SORT statement did not result in a jump to the corresponding section/label in the source. In AMT 40, we have fixed the behaviour of the sections / labels, in a Sort statement, to make it possible to jump to the corresponding section with a double click. By double click you will jump to the definition or usage of the section/label. | AMT 40 | |||
| Developer | Various | AMT COBOL 327028 Form content lost due to full screen. Users of the AMT COBOL product, migrated from Micro Focus environments had issues with losing information when the screen would be full. After passing line 25, the current data of the last lines would be lost, due to the scroll up action. In AMT 40, the old information on the screen will scroll up, making it possible for new information appears on the screen, without clearing the old information. So, when passing the end of the available rows to display, The content of the last line stays available and will scroll upwards and will display it at line 24 instead of clearing line 24. | AMT 40 | |||
| Runtime | Various | AMT LION C1807-084 Several layers authorisation rights are added in AMTScreens. Following the earlier provided preview of AMTScreens, that is still delivered as a preview, the possibility to customize authorization rights is now added, as available in LIONScreens already. Authorisation rights can now, for instance, be set for: * Set rights to open certain tabs (job management, Job messages etc.) * Rights to prevent users to change menu items have been added, like for instance, Printer Options * Right for options in certain tabs have been added, like for instance, 'Print Save As' in the Jobmanagement section (formerly known as report management) | AMT 40 | |||
| Runtime | AMTScreens | AMT LION C1807-085 AMT Screens settings can now be saved as an XML file A new feature was added to AMTScreens which allows saving the AMT settings as an XML file. Instead of making use of the Windows Registry, two XML files will be used to store the settings. Settings will be written to the Appdata/ roaming folder and Appdata/ local folder and is in both cases called SettingsV1.xml. | AMT 40 | |||
| Runtime | Various | AMT COBOL 327047 Incorrect initialization of signed comp-3 fields Incorrect initialization of signed comp-3 fields when they are inside a structure with an occurrence. For instance a zero would become 300. The "initialize" on a structure with an occurrence now sets the value of the comp-3 sub items correctly to zero instead of 300. | AMT 40 | |||
| Developer | Code Logic | AMT COBOL C1807-095 Added checks at validation and generation to ensure variable names are used unambiguously. It was possible to define variables with the same name inside structures and then use them without specifying the containing structure. This created uncertainty about which variable was actually used. This fix has added checks at validation and generation to ensure that the variables are used with the containing structure specified by using "OF". This ensures that the variable meant by the developer is actually used. | AMT 40 | |||
| Developer | Various | AMT LION and AMT COBOL C1807-101 Behaviour of checkboxes in huge lists would in some case be wrong. In the AMT Dev Studio, the lists(listviews) with checkboxes, like for instance the lists within the export window where you can select the forms, would not always work as supposed within the IDE. In somecase checkboxes, in lists that have 1000+ items, could be set for objects that should not be set at all. I those cases the checkbox would apply to another object, so, they wouldn't bind correctly. Now the IDE has the correct binding for large lists(listviews) inside the IDE, solving the bug found during the preview implementation of scripts in the IDE and adding 1000+ scripts with selecting some of the items. | AMT 40 | |||
| Control Center | Various | AMT COBOL and AMT Lion 327049 Start job didn't filter on long job names. Start job didn't filter on long job names that are approximatly 50 characters and containing underscores in the name. The Framework would added % and escapes for underscores, what caused the value to be longer then 50. Because the value would be truncated to 50 characters, it would not filter these long job names. The application and control center can now filter on long job names and also on other filters where the filter value is reaching the maximum length. | AMT 40 | |||
| Runtime | AMTScreens | AMT LION C1807-103 Position and size of AMTScreens (preview) in file AMTScreens, that is still in preview, will write its previous position and sizes to the setting file, called SettingsV1.xml, allowing it to open again just the way as it was closed. In LIONScreen these values would be added to the registry instead. | AMT 40 | |||
| Developer | Various | AMT LION and AMT COBOL C1807-105 Increase the current object name limit in the developer. In order to accommodate future Script versioning in the AMT Dev Studio, the object name limit has been increased to 128 characters. In addition, the system database name, and system item SI-LEVELBREAK are also increased to allow for 128 Characters. Database tables are still limited to 26 chars because the fact that some database engines won't support the use of more characters. Please note that the database changes will require performing a REO after installion, that will change instances in all databases. The REO will throw a warning with the message: "The field length is smaller" and "this field will be truncated". Note that only AMT Framework tables will be truncated due to this change, this won't affect user data. | AMT 40 | |||
| Developer | Code Logic | AMT COBOL 1808-010 COBOL FUNCTION UPPER-CASE, LOWERCASE, CURRENT-DATE and CHAR implementations are improved. The COBOL funtions FUNCTION UPPER-CASE as well as FUNCION LOWER-CASE were not implement correctly. This multiple errors in Therefor they would not parse correctly when proceeded by a substring (1:2) like for instance in this example IF FUNCTION UPPER-CASE(value)(1:2) = value. The second implementation error was that the output of these functions were not considered to be alpha and would therefore cause warnings when it would be compared to an alpha. Now the FUNCTION UPPER-CASE and LOWER-CASE are correctly parsed when preceded by a subsription like (1:2). Also, the following functions are now considered to be ALPHA: UPPER-CASE, LOWER-CASE, CURRENT-DATE and CHAR. | AMT 40 | |||
| Generator | Various | AMT COBOL C1808-015 Improved COBOL analysis for WRITE statement. In some cases the command WRITE to a Printfile was not detected, causing a C# error on generation. The error was caused because the process within the AMT COBOL Framework would try to read the file, though, this should not be possible within the framework. Now, the parser detects WRITE to a Printfile before generating the source code and will throw a clear error instead. | AMT 40 | |||
| Developer | Various | AMT LION and AMT COBOL 314368 [WORK IN PROGRESS] Print options are updated In AMT Dev Studio the screen's printing options, to be able to print an object, were lacking or outdated. This applies to all objects like for instance: Reports and Programs and Global Definitions All the screens have been checked and updated to the screen's options to print the relevant information. | AMT 40 | |||
| Runtime | Web Client | AMT COBOL 327101 The previous defined accept value would be displayed. A previous versions, the accept value (the date that was accepted) was displayed when using accept commands inside a loop. For MicroFocus only, simple accept commands without screen positions are now starting with a blank value in depended on the passed value. For the syntax version with screen positions you need to pass also the "UPDATE" option as operand. | AMT 40 | |||
| Developer | Code Logic | AMT COBOL C1808-020 LENGHT OF would throw a warning. The COBOL expression LENGTH OF was not correctly implemented and therefore not recognized as numeric. Therefore the AMT Dev Studio would throw a warning. COBOL expression LENGTH OF is now recognized as numeric so no longer gives an warning when used in a COMPUTE. | AMT 40 | |||
| Runtime | Scripts | AMT COBOL and AMT LION 327105 File printed from script is not displayed in the prints tab. File printed from scripts, for instance powershell scripts, were not shown in the prints tab of the Control Center (or application center) when the file was an extract file and the script (library) didn't call the Comscript function AddPrintFile first. The following generic warning would be showed when this error occured: "The PrintController was processing the request". Comscript is changed that when executing the PrintFile function on the print object (IPrint) and the file is an extract file that it creates the right records in the system database so the print does now show in the print tab. | AMT 40 | |||
| Control Center | Various | AMT COBOL and AMT LION 327098 Printer name not shown in the details of a print. The printer name would be left empty in the details of a print when looking at a queued print in the application and control center. Also in the Application center the column name was left blank in the details sections. Both would show in the overall list with prints. When looking at the details of a queued print in the Control Center and Application Center, the printer now has the right name. Also, when looking at the details of a printed prints in the Application Center's left column now shows "Printer" in the left column. It was blank. | AMT 40 |