AMT 62
Released: 06 Dec 2019.
For availability, please contact the Avanade Service Portal for information on downloading new releases.
Special attention items:
AMT 62
- Make sure that with use of the new AMT Screens, the DLL files of the older version have all been deleted from the ClientGUI folder!
- If you use the new File Uploader, you have to re-add the object to the form for it to work.
Product | Cat | Subcat | Description | Type | Version | Priority |
---|---|---|---|---|---|---|
AMT LION | AmtTools | Reo | C1811-082 In previous versions of AMT LION, index logic fields were initialized with an empty value if they were nullable. For consistency reasons, this has been abandoned. AMT Developer and AMT Reorganize now give a warning when nullable fields are used, so the programmer can check the index logic or change the column to non-nullable. |
CHANGE | AMT 62 | |
AMT LION | AMT COBOL | Runtime | ComScript | 327706 After the connection to the database was lost, caused by a Virtual Machine snapshot, the calling process was not ended, and an extensive bug report was generated by the Comscript Accept function. The reported error was: 'Prepare requires an open and available Connection. The connection's current state is closed'. The problem has been solved in Comscript, by adding database retries to waiting functions that potentially take a long time to finish: 'Accept/start job with wait/print.' |
FIX | AMT 62 | |
AMT LION | Runtime | AmtScreens | 328084 Encrypted and Secure (password) properties on EditBoxes could have different values for different languages. Encrypted and Secure (password) properties on EditBoxes are now updated for other languages when the value in any language changes. When a generation is executed, the value in the default language is used to ensure that old configurations are generated correctly. |
FIX | AMT 62 | |
AMT LION | Runtime | AmtScreens | 327711 When a popup was opened, the sub-session of the form or popup creating it was re-created on the client side. This failed to include a language, so it detected a change and re-created the form without changes from the user or DISPLAY_MAIN. This caused sorting on Listviews to disappear and charts to disappear entirely. Additionally, Fill Color for shapes was not supported as a property to be sent to the server, so when a popup was closed and the original form had to be re-created, changes to the Fill Color were not implemented. When a new sub-session is created that doesn't have a language, the parent session's language is used, so no change to the creating form is detected when a popup is opened, and changes to the original form are kept. Support has been added to send changes to the Fill Color of a shape to the server, so such changes will be maintained when the form is re-created. Besides this, BUTTONGROUPS and RADIOBUTTONS are now enabled after a popup has been closed. |
FIX | AMT 62 | |
AMT LION | AmtTools | Prodinstall/Pinstall | 325428 Prodinstall used to log only the start and end of a group of objects like applications or forms being synchronized. Now it is possible to set logging severity to 1 or 99, 1 being the old situation, where only the start and end of groups was logged, and 99 being extensive logging, where each object that is copied is individually processed (this can however result in large log files). The chosen setting can be saved to the AmtProdInstall.config file by hitting the Save Config button after changing or adding it to the config file. |
CHANGE | AMT 62 | |
AMT LION | Developer | Database | 328356 When a new table and/or indexes were created, they could be assigned to another generation set while it hadn't been checked in yet, resulting in a corrupt database. Now an error message is raised when an attempt is made to assign an object locked in another generation set. |
FIX | AMT 62 | |
AMT LION | Runtime | AmtScreens | C1909-111 / C1911-073 AmtScreens.exe referenced various .dll files, all in the ClientGui directory. To have the option to copy AmtScreens.exe to different locations, for instance for different configurations, all referenced .dll files have been compiled into AmtScreens.exe as resources. The old referenced .dll files in the ClientGui directory need to be deleted. |
CHANGE | AMT 62 | |
AMT COBOL | Runtime | Various | C1910-029 Performance of reading indexed files in SQLite was poor. By reading the files asynchronously, as was already done with non indexed files, performance has improved considerably. |
CHANGE | AMT 62 | |
AMT LION | Runtime | AmtScreens | 328649, 328489 When multiple messages were sent to client AMT Screens, the tab 'messages' appeared. This tab disappeared when other tabs were navigated to, which made it impossible for the end user to switch back to the message, for any helpful information. This behavior has been changed in such a way that the message tab only disappears on the next transmit of the form. Also, the navigation form message tab to application tab has been improved. |
FIX | AMT 62 | |
AMT LION | AMT COBOL | AmtTools | Reo | C1910-077 When Amt Reorganize changed an Array of strings a memory error could occur depending on the size and number of the arrays, and incorrect logging messages were then produced. Sometimes this change didn't work at all in Oracle. Amt Reorganize logging messages, when an Array of strings is changed, have been clarified. The change can now also be executed in Oracle without problem. The possible memory error has also been solved. |
FIX | AMT 62 | |
AMT LION | Runtime | AmtScreens | 327838 If a cell required much room for its contents in AMT Screens, it could be given an unlimited width. The initial width of columns is now limited to the screen width of the user's monitor. |
FIX | AMT 62 | |
AMT LION | Runtime | AmtScreens | 328537 In RTQuery it was impossible in Oracle databases to identify the identity column. So while the ROWID column header was hidden, its data was not, and the data moved the other data to the right. Now the identity column is determined while the database schema is loaded, also for Oracle databases. This determination also considers what the user configured as the identity column. RTQuery uses this data to select the column to base changes on. For Oracle databases ROWID remains immutable even if another column is configured as the identity column. |
FIX | AMT 62 | |
AMT COBOL | Runtime | Various | C1910-117 For former MicroFocus applications only: the fix for C1909-105 caused AMT COBOL to write rubbish values into the database if the field was a COMP-3 array field. This issue has now been fixed. |
FIX | AMT 62 | |
AMT COBOL | Runtime | Various | C1910-141 Data stored in a VSAM file was trimmed, so the record size was altered. Especially with variable record sizes and SQLite files, record size should match the configured record size. This issue has been fixed. |
FIX | AMT 62 | |
AMT LION | AMT COBOL | AmtTools | Debugger | C1911-004 When a lot of objects were generated for debug, updating the Object Explorer in the debugger was slow. Lazy loading has been improved further, and not all file information is parsed when the list of debug objects is loaded, which speeds up the loading. |
FIX | AMT 62 | |
AMT COBOL | Runtime | Web Client | C1911-007 For former A-Series COBOL applications only: an error message should have been shown if the FORMKEY function couldn't find the form specified, or if a user wasn't authorized for the form. The following error message is now shown if a form can't be found, or if the user isn't authorized: 'FORMKEY ( |
CHANGE | AMT 62 | |
AMT COBOL | Runtime | Various | C1911-008 For former A-Series COBOL applications only: online programs without a defined conversation area in the COMS input/output header were causing a NULL reference exception at runtime. To resolve this issue, NULL checks before the conversation area is referenced have been added. |
FIX | AMT 62 | |
AMT COBOL | Runtime | Various | C1911-011 For former A-Series COBOL applications only: the GET-INTEGER-USING-DESIGNATOR function in AMT COBOL didn't support the LSN option. The LSN option has now also been implemented in AMT COBOL. |
CHANGE | AMT 62 | |
AMT LION | Runtime | Web Client | C1911-012 Styles for control codes were not always applied in the Web, and the blink character also blinked text in front of the blink control code in AMT Screens. The way styles are applied to control codes in the Web and blinking in AMT Screens has been fixed. |
FIX | AMT 62 | |
AMT COBOL | Runtime | Various | C1911-014 Stopping a transaction agent in the Transaction Server led to a high CPU load. If the connection to a transaction agent is lost, the connection is now properly closed, which prevents a high CPU load. |
FIX | AMT 62 | |
AMT LION | Runtime | AmtScreens | C1911-015 Commands for RTQuery queries were made available to the user based on the database type. However, for some commands the system database was opted for instead of the application database, which was incorrect. Now, the application database type will always be chosen when commands for RTQuery queries are made available. |
FIX | AMT 62 | |
AMT LION | AMT COBOL | AmtTools | Reo | C1911-017 The Amt Reorganize Service Configuration file was overwritten with the installation of an AMT release. File Default_AmtReorganizeService.Exe.Config is now delivered as a default/sample file for the AmtReorganizeService.exe.Config, so this won't be overwritten anymore. Also the help text invoked by the AmtReorganize /? option has been improved. |
FIX | AMT 62 | |
AMT COBOL | Runtime | Various | C1911-018 On an A-Series mainframe, you can define different justification settings (left, right) for the input, output and screen (display) of an SDF form field. In AMT COBOL you only had one setting. In order to make it possible to use different justification settings for input and output, the RIGHT-JUSTIFY and LEFT-JUSTIFY functions have been added to AMT COBOL. These functions can be used in the WS-TO-FORM and FORM-TO-WS sections of an AMT COBOL Form. |
FIX | AMT 62 | |
AMT LION | Control Center | Various | C1911-022 When a lot of data was passed from the Business Logic to the Control Center or Application Center via JSON, a serialization error could occur because the max length was exceeded. The max length has been increased to 10 million characters, and can be overridden by adding a key to the web.config. Example: <add key="maxJsonLength" value="2147483644" /> |
CHANGE | AMT 62 | |
AMT COBOL | Runtime | Various | C1911-024 On an A-Series mainframe the COBOL CLOSE statement (without a specified option) retains the file and does not change its FILEUSE attribute. In AMT COBOL the CLOSE statement (without a specified option) deleted the file, if it was temporary. In AMT COBOL the CLOSE statement (without a specified option) now also retains the file, including temporary files. |
FIX | AMT 62 | |
AMT COBOL | Runtime | Web Client | 328643 Modifying an input field in the Web Client that was defined as a NUMERIC with an assumed (virtual) decimal point (9V99) was not possible, because AMT COBOL explicitly checked for a decimal point and showed an error message if it didn't find one. The Web Client has been fixed in such a way it no longer shows an error message if the numeric field is defined with an assumed (virtual) decimal point. |
FIX | AMT 62 | |
AMT COBOL | Runtime | Various | C1911-031 Microfocus and IBM support files with Organization: Line Sequential. AMT supported these as sequential files with Carriage Return/Line Feed record ending and fixed record size. With this fix, Line Sequential files are handled as text files. Trailing spaces are removed when the files are written, and Line Feed only line endings (Unix) is supported in reading. Rewrite and Delete statements are not allowed on them. Note for customers already using LINE SEQUENTIAL files: these files have trailing spaces stripped when they are created. Size will be different and they might look different in an editor but the change is not breaking. |
FIX | AMT 62 | |
AMT LION | Developer | Various | C1911-035 The FNAME parameter of the AMT Developer Import/Export command line interface did not accept spaces in the file path. This issue has been resolved. |
FIX | AMT 62 | |
AMT COBOL | Runtime | Various | C1911-041 On an A-Series mainframe, a transaction program keeps running, meaning that the values of working-storage variables are retained. This was not supported in AMT COBOL. In AMT Cobol, the 'Reentrant' program type has now been implemented. A transaction program that is defined as 'Reentrant' in the Program Control section of the AMT Control Center, is now reused for each transaction request. NOTE: the system database reorganize (version upgrade 48 to 49) sets the program type to 'Default' for all programs currently defined in the Program Control section of the AMT control Center. This is done to ensure nothing changes for current customers. |
CHANGE | AMT 62 | |
AMT LION | Runtime | AmtScreens | 328617 In AMT Screens, on the Start job tabsheet the first printer was always selected; if this was a physical printer then the output was always printed. Now no printer is selected by default. |
FIX | AMT 62 | |
AMT COBOL | Runtime | Various | C1911-044 When an Abend occurred while a Handle Abend had been set, no bug report was written: EXEC CICS HANDLE ABEND LABEL(ABEND-LABEL) END-EXEC. Now when an Abend occurs a bug report is always written, so the cause of the abend can be traced. |
FIX | AMT 62 | |
AMT COBOL | Runtime | Various | C1911-045 For CICS AMT COBOL a ReadNext or ReadPrev returned a NotFound status, after a failed StartBr. AMT COBOL now returns an InvReq status if a ReadNext or ReadPrev is performed after a StartBr, because this is not allowed. |
FIX | AMT 62 | |
AMT COBOL | AmtTools | Debugger | C1911-047 The Transaction Agent did not close when the Web Client was closed during online COBOL debugging. The (debug) Transaction Agent is now closed together with the Web Client, during online debugging in COBOL with a Transaction Server. |
FIX | AMT 62 | |
AMT LION | Runtime | AmtScreens | C1911-050 For security reasons, logfiles could not be written in the ClientGui directory by program AMT Screens. Also, too much logging was done. The logfiles can now be found in the user's personal directory or in the roaming directory if the user has a roaming profile. In app.ini there an extra setting that can be added for the severity of the logging at start-up. For example: LOGSEVERITY=4 gives all logging for warnings and lower. The highest severity level is 7. |
CHANGE | AMT 62 | |
AMT COBOL | AmtTools | Various | C1911-058 .dll Files that were changed by generating objects were not picked up correctly by Transaction Agents, which caused a hanging system. An Agent switch after the code has been generated now correctly restarts the agents with the new .dll files and the transaction continues normally with the updated .dll files. |
FIX | AMT 62 | |
AMT COBOL | Runtime | Web Client | C1911-059 For AMT COBOL, ALPHA and NUMERIC EditBoxes were not always aligned in the same way. The Web Client padding has been changed so the EditBoxes are identical for left (ALPHA) and right (NUMERIC) aligned fields. NOTE: In order for this to work, the updated Amt.Css file has to be used. |
FIX | AMT 62 | |
AMT LION | AMT COBOL | AmtTools | Debugger | C1911-062 The AMT Debugger was reporting duplicate insertion exceptions, even though the 'Duplicate records' option in the AMT Developer Generation set definition was set to 'No warning'. When the 'Duplicate records' option was set to 'Abort', the COBOL program kept on running even when a duplicate insert was encountered. Changes have been made on the server side of the Debugger, to ensure exception messages are only sent to the client if the exceptions have not been handled. A change has also been made on the runtime side, which makes sure that an exception is reported if the 'Duplicate records' option in the Generation set is set to 'Abort'. |
FIX | AMT 62 | |
AMT LION | Runtime | AmtScreens | 328651 In AMT Screens a very specific ComboBox selection could raise an AMT-COMMODULE Internal Error. The Amt ComboBox logic has been improved so this specific situation does not occur again. |
FIX | AMT 62 | |
AMT LION | AMT COBOL | AmtTools | Reo | C1911-068 AMT Reorganize used on a DB2 database raised errors when an Index, Stored procedure or Function was created. AMT Reorganize has been changed in such a way that now all indexes are correctly created, and Stored procedures or Functions don't raise errors anymore. |
FIX | AMT 62 | |
AMT COBOL | Runtime | Various | 328684 The EIBCPOSN field in AMT IBM CICS (online) was set to an incorrect value when the cursor was in a field on the first column. The EIBCPOSN field is now set to the correct cursor position. |
FIX | AMT 62 | |
AMT COBOL | Generator | Various | 328676 When EXEC DB2 queries were parsed with a FROM clause containing multiple tables, the columns in the query could be mapped to the wrong table. This issue has been fixed. |
FIX | AMT 62 | |
AMT LION | Runtime | AmtScreens | 328673 When the user selected a screen by typing text in the search box for the first time, he was brought to the selected screen. The second time, however, the user had to type the text into search box all over again. This is unwanted behaviour. The solution that has been implemented is for the selected screen name to be cached in the search box, so that typing one or two letters brings up the screen name. In addition the search box is prefilled with the last selected screen name. |
CHANGE | AMT 62 | |
AMT COBOL | Runtime | Various | C1911-077 The implementation of the TransactionHook up till now was not sufficient to implement all COMS processing item functionality. Various changes have been applied to the current implementation of the TransactionHook to remedy this. |
CHANGE | AMT 62 | |
AMT COBOL | AmtTools | Debugger | C1911-083 Focus was not correctly set to the active line after loading an object in the debugger the first time. Setting of the focus has now been fixed and the debugger scrolls down to the active line when the document is loaded the first time. |
FIX | AMT 62 | |
AMT COBOL | Runtime | JCL | C1911-084 ftp.AppendFile kept looping if a FileController connection was used to upload a file. ftp.AppendFile now properly uploads and appends the file. |
FIX | AMT 62 | |
AMT COBOL | Control Center | Server Control | C1911-085 General information shown in the Control Center of a Transaction Server contained duplicate information, which led to incorrect alignment, because the duplicate information was not added correctly to the list. The duplicate information has been removed and is no longer shown. This has automatically solved the alignment issue. |
FIX | AMT 62 | |
AMT LION | Runtime | AmtScreens | C1911-086 The amount of results returned per query did no longer have a limit in AMT Screens RTQuery for table queries. This source was renewed a while ago but the counter was still pointing to an old variable. This has been modified. |
FIX | AMT 62 | |
AMT COBOL | Runtime | Various | C1911-087 On an A-Series mainframe the COMS output status-key is set to 89 (BAD MESSAGE SIZE) if the length of the output message is larger than the defined text length. In AMT COBOL this was the other way around, which was incorrect. This issue has been resolved. |
FIX | AMT 62 | |
AMT LION | Runtime | AmtScreens | 328672 A single mouse click selected the whole text, and a double click set the cursor on the required spot in an EditBox. This has been turned around, so that a single click will position the cursor and a double click selects the whole text. |
FIX | AMT 62 | |
AMT COBOL | Runtime | Various | C1911-089 Closing a Web Client for which the debug session had been killed, crashed the Transaction Server. Errors while logging off or closing debug Transaction Agents can now safely be ignored, and will not stop the Transaction Server anymore. |
FIX | AMT 62 | |
AMT LION | Developer | Forms | C1911-097 The AMT File Uploader was not saved to the repository in a way consistent with the other controls. It is now saved correctly to the respository, but this means that AMT File Uploader needs to be readded. NOTE: Please make sure the AMT File Uploader has been readded to the repository! |
FIX | AMT 62 | |
AMT COBOL | Generator | Various | C1911-098 In AMT COBOL, any form item was always visible at runtime, regardless of the value (True or False) of its ‘Visible’ property. A fix has been applied to the generator, so that an appropriate initialization line is generated in the form's ScreenDefinitions object to make the field invisible, if this has been specified in the form designer. |
FIX | AMT 62 | |
AMT LION | Runtime | AmtScreens | C1911-103 Sometimes the custom query in AMT Screens RTQuery would not return the correct amount of results, because it was limited by the SpinEdit that was used for table queries. To solve the issue the link between custom queries and the SpinEdit has been removed. |
FIX | AMT 62 |