AMT 49
Released: 01 Mar 2019.
For availability, please contact the Avanade Service Portal for information on downloading new releases.
Special attention items:
AMT 49 –
- In AMT 49, we have added the new AmtReorganize as a preview. We do want to warn you about the fact that, although the new REO is tested with Microsoft SQL Databases and Oracle Databases, we anticipate that more in depth tests are needed for Oracle Databases still. This is only meant for early preview.
| Product | Cat | Subcat | Description | Type | Version | Priority |
|---|---|---|---|---|---|---|
| AMT LION | AMT COBOL | Developer | Database | C1809-071 Table names are limited to 26 characters Previously, table names were limited to 26 characters. This was to ensure that the table name was not too large for the older database engines. Table names are no longer limited to 26 characters anymore, the REO will validate if the length of the name is supported by the database engine. | CHANGED | AMT 49 | |
| AMT COBOL | Runtime | Various | C1901-075 Fix Bms Screenfield attributes. No need for WorkingStorage copy in CicsBms forms. Bms screenfield attributes did not work properly, but this has been fixed Ws-To-Form and Form-To-Ws are no longer needed in CicsBms forms. The working storage copy is not needed anymore. All this work is automatically done on runtime. No need for any changes in current forms, the ws-to-form and form-to-ws will remain working. This change will not affect existing users. | FIX | AMT 49 | |
| AMT LION | Runtime | AmtScreens | C1901-093 AMT Screens crash Previously, when a row was selected it would not reset after the load, so, when the selected row was larger then the available rows AMT Screens would crash. Now, the last selected row is reset when the rows are reloaded to prevent the crash. | FIX | AMT 49 | |
| AMT LION | Runtime | AmtScreens | C1901-103 AMT Screens enhancements A timeout has been added to RTQuery so that it is no longer possible to get more data after the timeout has expired. After the RTQuery time out expires, the buttons will be greyed out. The timeout can be set in the Control Center, in the Runtime behaviour settings. | NEW | AMT 49 | |
| AMT LION | Runtime | AmtScreens | C1901-114 AMT Screens deleting of macros added Previously, macros could not be deleted in AMT Screens. Macros can now be deleted in AMT Screens. | NEW | AMT 49 | |
| AMT LION | Runtime | AmtScreens | C1901-115 AMT Screens keyboard shortcuts added to the macro editor and macro list Previously, AMT Screens keyboard shortcuts were missing in the macro editor and macro list. Like for instance the keyboard shortcut Alt-C: the close action command. Now, AMT Screens keyboard shortcuts are available in the macro editor and macro list. | NEW | AMT 49 | |
| AMT LION | Runtime | AmtScreens | C1901-116 Macro security screen added. There is no way to configure the macro roles and users in AMT Screens. This Macro security screen was not added to AmtScreens yet. Now a new screen is added for changing the security regarding Macros. Macros can now be linked to a user or a role. The behaviour of AMT Screens will be the same as it was in LIONScreens. | NEW | AMT 49 | |
| AMT LION | Runtime | AmtScreens | C1901-126 The Cut and Copy behaviour was swapped when editing macro commands. The Copy command within the Macro Editor of AMT Screens would instead act as the Cut command. The behaviour was swapped causing the Copy command to Cut instead and vice versa. The behaviour of the Copy command is fixed. It will now copy instead of cutting the selected information in the Macro Editor. | FIX | AMT 49 | |
| AMT LION | AMT COBOL | AmtTools | Reo | C1901-128 AmtReorganize should check if the database is used before it will execute. The new AmtReorganize did not check whether users were still connected to the database before it started to perform Reorganize process. The new AmtReorganize will check if there are no users connected to the database anymore when it starts to execute the Reorganize process. | FIX | AMT 49 | |
| AMT COBOL | Developer | Code Logic | C1902-004 Support ATTRIBUTE being a variable name instead of only a COBOL keyword. Using a variable named ATTRIBUTE was not supported in AMT COBOL. The AMT Developer would just ignore this COBOL syntax in this case. The ATTRIBUTE string is no longer removed/ignored when parsing COBOL source code. Checks are made to determine if the COBOL keyword is meant or if ATTRIBUTE was meant as a variable. | FIX | AMT 49 | |
| AMT LION | Runtime | AmtScreens | 327690 Memory leakage in the application server High memory usage occurs when global routines use large arrays and are not freed when doing multiple calls. Memory leakage was partly resolved AMT 45 and improved upon in AMT 48. | FIX | AMT 49 | |
| AMT COBOL | Runtime | FileController | 327724 Extra checks were added before clearing a client connection in the FileController when the client was no longer processing. Previously, FileController was logging messages like "Disconnecting client. Client no longer processing. object/client (CobolProgram-Online)". Although this was correct, the FileController was sometimes closed while the client was still connected. Now, if the web session is still active the connection to the FileController will not be closed. | FIX | AMT 49 | |
| AMT COBOL | Generator | Various | C1902-027 Declaring duplicate variable names for applications migrated from MicroFocus. Declaring duplicate variable names was not supported for applications migrated from MicroFocus. If one would declare a duplicate variable name in the AMT Developer, the generator would throw an error. When duplicate variable names are declared a warning is now reported (instead of an error). Nevertheless, in a case when it is unclear which variable is used an error will be thrown. | FIX | AMT 49 | |
| AMT LION | AMT COBOL | Runtime | Various | C1902-029 Setting redefined structures to pointer address didn't update the redefine structure. Code example (for AMT COBOL): 01 STRUCT1. 05 STRUCT1-VAR PIC X(10). 01 STRUCT2 REDEFINES STRUCT1. 05 STRUCT2-VAR PIC X(1) OCCURS 10 TIMES. 01 TEST-VAR1 PIC X(10) VALUE 'CONTENT1'. 01 TEST-VAR2 PIC X(10) VALUE 'CONTENT2'. Worked okay: SET ADDRESS OF STRUCT1 TO ADDRESS OF TEST-VAR1 Did not work okay: SET ADDRESS OF STRUCT2 TO ADDRESS OF TEST-VAR2 STRUCT1 remained having content of TEST-VAR1 | FIX | AMT 49 | |
| AMT LION | AMT COBOL | Runtime | Various | C1902-030 Changes to retrieving (DB2) DATE/TIME field values in the incorrect format. We've made some changes for the Easytrieve conversion tool that are around retrieving (DB2) DATE, TIMESTAMP and TIME field values. Therefore, we have made changes to our AMT Runtime Libraries and/or AMT Generator, however, these changes should not cause any behaviour changes for existing customers. | CHANGE | AMT 49 | |
| AMT LION | AMT COBOL | Runtime | Web Client | C1902-031 Application Center startup parameters were not handled correctly Startup parameters sent to the Application Center were not passed to the client application. Therefore it was not possible to use the startup parameters, within the application. Startup parameters sent to the Application Center are now passed to the client application. | FIX | AMT 49 | |
| AMT LION | AMT COBOL | Developer | Various | 327827 AMT Developer Studio username greater than 17 characters and now supports up to 64 characters. When adding a user in the AMT Developer with a username that was longer than 17 characters, the user would not be granted any access even after setting the security rights. This is because after restarting the developer it would create a new truncated record of the username. The AMT Developer would compare the full name against the truncated value. Also, you were not able to sort the usernames. The max username length has been increased to 64 characters and the security dialogue now sorts the usernames. | FIX | AMT 49 | |
| AMT LION | AmtTools | Various | 327864 Error in the messages when running 2 print controllers on the same print queue. When running 2 print controllers on the same print queue the alerts & messages in the ControlCenter showed "PrintRequestId [nnnn] cannot be found". Also the message could be send out twice, creating two entries pointing to the same filename. Now, when having multiple print controllers pointing to the same print queue they place a lock on the print request so only one of them is processing it. In the case of a print controller crash then the other print controller will pick the request up. | FIX | AMT 49 | |
| AMT COBOL | Generator | Various | C1902-039 Level 78 variables (MicroFocus COBOL) Level 78 variables (MicroFocus COBOL) were not supported in AMT. The AMT Developer would throw an error when a level 78 variable was used in the source code when attempting to be validated. Level 78 variables (MicroFocus COBOL) are now supported in AMT. | FIX | AMT 49 | |
| AMT LION | AMT COBOL | Runtime | Jobs/Batches | 327859 Kill of a job now always executed. When you had two Batch Controllers running on the same job queue, killing of a job in the Control Center was not always executed. Now, the Batch Controller that started the job is killing the job. The other Batch Controller no longer removes the request just before it is executed. | FIX | AMT 49 | |
| AMT LION | AMT COBOL | Generator | Licenses | 327502 Generator reboot through Azure. In Azure, a reboot of the generator server caused too much change to the server signature sending an invalid license error. License check for Azure will react less tense on the ever changing temporary signature. | FIX | AMT 49 | |
| AMT LION | AMT COBOL | Developer | Various | C1902-042 The storing of scripts inside the AMT Repository is now out of preview mode. | NEW | AMT 49 | |
| AMT COBOL | Generator | Various | C1902-044 BINARY fields in Easytrieve (IBM) should have the sign in the right-most byte. We have applied changes to the BINARY fields used in Easytrieve (IBM). Within Easytrieve (IBM) programs the sign should be in the right-most byte, but currently the sign is in the left-most byte. Therefore, we have made some changes to the Easytrieve converter and AMT Generator. These changes should have no further impact on existing AMT Environments. | FIX | AMT 49 | |
| AMT COBOL | Runtime | Various | C1902-045 Terminal Id is now generated instead of using Station Name The Terminal Id (TERM-ID) is now generated by the TransactionServer, this is a PIC X(4) values between '0000' and 'ZZZZ' Each Terminal Id is now unique within the current running Application environment. For Cics this TERM-ID is automatically moved to the system variable EIBTRMID. This will not affect the exsisting customers using AMT COBOL. | CHANGED | AMT 49 | |
| AMT COBOL | Generator | Various | C1902-053 Variable named UPPER-CASE and using FUNCTION UPPER-CASE in the same source not supported. Variable named UPPER-CASE and using FUNCTION UPPER-CASE in the same source not supported. The parser would resolve the function as variable which resulted in errors being reported. This is now supported in the parser, so it is now possible to use a variable named UPPER-CASE and use FUNCTION UPPER-CASE in the same source. | FIX | AMT 49 | |
| AMT COBOL | Generator | Various | C1902-059 Using index +1 into a multidimensional array with the array indices separated by commas Previously, using index +1 (The statement +1 for a positive value) into a multidimensional array with the array indices separated by commas was not supported. This is now supported. When encountering array indices separated by commas, resolving it is now simplified by splitting the indices part by commas. | FIX | AMT 49 | |
| AMT LION | AMT COBOL | Control Center | Security | C1902-060 Control Center Security users gives an error In some cases opening the Control Center Security user screen would throw an error "The contract name 'Asysco.Amt.Security.Service.IAmtSecurityService' could not be found in the list of contracts implemented by the service 'SecurityService'." We have corrected the web.config configuration file and also improved internal naming of SecurityService to AmtSecurityService. | FIX | AMT 49 | |
| AMT LION | Runtime | Various | 327888 The .Load caused a FileController error when the file was not found or locked. The .Load caused a FileController error when the file was not found or locked, but it kept on running. The .Load no longer causes a FileController error because the file is now read under shared mode causing less lock issues. | FIX | AMT 49 | |
| AMT LION | AMT COBOL | Control Center | Various | 327015 Keepalive request failure did not provide a clear error. When the Keepalive request fails, for example due to a connection error, a pop-up would appear showing an empty error box with no information. This could message could appear in the Control Center, Application Center and a No-Framework application. The Keepalive request can fail due to network related issues, this error is now detected and an error message with more infoormation is now shown in the pop-up. | FIX | AMT 49 | |
| AMT COBOL | Generator | Various | C1902-065 Using a GO TO a section name was not supported in AMT COBOL. Using a GO TO a section name was not supported in AMT COBOL. This is now corrected, internally a label is added to the beginning of the section so the GO TO will be performed to that label. | FIX | AMT 49 | |
| AMT LION | AMT COBOL | AmtTools | Reo | C1902-066 Oracle trigger creation The trigger creation for Oracle by the Reo did not include a referencing clause, this clause is not mandatory. To make the trigger creation for Oracle by the Reo more specific the referencing clause 'REFERENCING OLD AS OLD NEW AS NEW' has been added. | FIX | AMT 49 | |
| AMT LION | AMT COBOL | AmtTools | Reo | C1902-067 AmtReorganize: New Reorganize wants to make a field for the structure The New AmtReorganize - the New REO, that is now available in preview- wanted to create a structure database field when it was changed, this is not needed because the structure fields are stored. Corrected the new Reorganize so its ignores the structure database fields. | FIX | AMT 49 | |
| AMT LION | AMT COBOL | AmtTools | Reo | C1902-069 AmtReorganize Administration table versions and Reo Running is now performed correctly The administration of table and DLL versions was not done within the new AmtReorganize. The AmtReorganize is now available in preview mode. The new AmtReorganize updates the table versions at the end of a reorganize execution. Also the administration regarding Reo running performed correctly. | FIX | AMT 49 | |
| AMT LION | AMT COBOL | Runtime | Jobs/Batches | C1902-071 Long print file names caused a database error. The logical filename length was not correct in the database. The new length will now match the length of the "filename" field in the AMTsysprintfile table. Keep in mind that you will need to run a REO. | FIX | AMT 49 | |
| AMT COBOL | Runtime | Various | C1902-072 Bytes difference between BINARY fields in applications migrated from Easytrieve and applications migrated from IBM COBOL. We have applied some changes to our internal variable libraries for making a behaviour difference between applications migrated from IBM COBOL and applications migrated from Easytrieve. BINARY (COMP) fields defined in IBM COBOL occupy 2, 4 or 8 bytes of storage. BINARY fields defined in Easytrieve occupy 1,2,3,4,5,6,7 or 8 bytes of storage. These changes were made in the Runtime Libraries and the AMT Generator, however, this should have no further impact on existing AMT environments. | FIX | AMT 49 | |
| AMT COBOL | Runtime | Various | C1902-074 Program was looping because of redefined group on a Subprogram call in AMT COBOL The program was in a loop sending a transaction to the Transaction server. This was cause of a group-item that was redefined when calling a Subprogram. The program works okay now. The redefined item is not added to an internal list anymore, when it is already in the list. | FIX | AMT 49 | |
| AMT LION | AMT COBOL | AmtTools | Reo | C1902-087 AmtReorganize warning that it is still in preview to warn users to be careful. Before executing a reorganization within the new AmtReorganize the operator will get a warning that it still in preview. | NEW | AMT 49 |