Amt 39

Cat	Subcat	Description	Version
Developer - Other	Various	ALL C1801-066 Label authorisation policies In AMT 39, new functionality has been added to the AMT Developer Studio for assigning user group permissions to labels. This will give administrators the ability to allow or deny certain users from assigning objects to a label. E.g. A administrator can deny a Test user from assigning objects to the development label. Administrators can implement these restrictions by entering the Label Management screen, selecting a label, press the properties button and select the "Security" tab. Here is a list of permissions that have been added: Administrator User groups with this permission have also all below permissions and they can modify label management security. Look into User groups with permission can view the contents of the label Create Label User groups with this permission can create new (sub)labels Modify Label Users groups with this permission can modify the label name Delete Label Users groups with this permission can delete the label Assign Objects User groups with this permission can assign objects to the label Delete Objects User groups with this permission can delete objects within the label	AMT 39
Developer - Other	Various	ALL 307861 [Work in progress] Added support for script in the repository. In AMT 39, we've added the first stages for versioning support of scripts in the repository. We've made changes to the import/export/revision/label/etc. For now all changes, are hidden under a switch, so nothing is visable in the current release.	AMT 39
Runtime	Web Client	ALL 325607 Limits for input in edit box (webclient) should be equal to the desktop client. Editboxes in the webclient were allowed to take in more decimals than was indicated in the AMT Developer Studio. This was caused by the fact that the position of the decimal separator would be replaced by a value (number) too. This is why the edit box (in the webclient), for example, allowed input that resembled input equal to a Numeric value with the format 7.0 but was actually declared as a Numeric with the format 6.2. The editboxes in the webclient will now only allow the length and decimals specified in the AMT Developer Studio	AMT 39
Developer	Forms	AMT LION 326114 Groupbox was smaller than the caption In the AMT Developer Studio, the painting of the groupbox was incorrect due to the size of groupbox and the caption width. Therefore, the groupbox caption exceeded the groupbox when the size of the groupbox was smaller than the caption. The caption is now cropped to fit within the groupbox. The behavior now resembles how it would look at runtime.	AMT 39
Developer	Various	AMT LION [FIX] 326825 Public routines not shown in routines view After adding one or more public routines to a global performable routine, the new public routines didnt't show up in the routines-view (tree-view) on the left pane. Only the 'normal',non public, routines were shown. Now public routines will show-up in the tree-view. For global performables, created in a previous versions, the validation process will refresh the tree-view and show the public routines.	AMT 39
Developer	Various	ALL 326897 The show difference window would not show differences in the use of spaces. The 'Show Difference' window would not look into differences in the use of spaces, therefore, it was not able to show differences in cases where spaces are important, like for instance, spaces used inside a variable (var-na me-01). In AMT 39, we made changes to the behaviour of the parser, so that it will ignore unimportant differences in the use of the spacebar. EG. "target := source" is equal to " target := source". As these differences could exist due to differences in alignment and won't impact the functionality, but will of course report important differences when for example a space is in a string literal. For AMT COBOL, we've also added support for comparing a commented line and string literals with double quotes.	AMT 39
Migration	COBOL	AMT COBOL C1806-081 The DMS2200 statement MOVE AREA-KEY, AREA-NAME returned a "Not Implemented" exception while generating in AMT COBOL. DMS2200 specific MOVE AREA-KEY, AREA-NAME for RUN-UNIT, RECORD, AREA, SET, DB-KEY was not accepted by AMT COBOL. The code validation and generator both returned a "Not Implemented" error. It is now possible to use the DMS2200 MOVE AREA-KEY, AREA-NAME statement in AMT COBOL. Example: 01 ARNM USAGE IS AREA-NAME. MOVE AREA-NAME RUN-UNIT TO ARNM. DISPLAY ARNM.	AMT 39
Generator	Various	AMT VS C1806-085 Various minor AMT COBOL to VS generation issues related to the usage of copybooks. This change will have no influence on existing AMT COBOL customers. It will only effect new migration projects, when moving from AMT COBOL to VS	AMT 39
Runtime	Various	AMT COBOL C1806-086 AMT COBOL DMS2200 STORE statement, wrong database key calculated when database or area is empty. When a record, from a migrated DMS2200 platform, is inserted, a new unique database-key is calculated. This key was used by DMS2200 internally, but it was possible to find a record through all or part of this, resulting in the area key. AMT COBOL calculated the first key wrong when an area was empty. This could result in error when a fetch area-key, area-name was done. With this fix AMT COBOL calculates a correct database-key. Converted databases are not hit by this issue while there are no empty areas. New keys were already calculated right using the highest database-key in the database.	AMT 39
Runtime	Jobs/Batches	AMT COBOL 326951 The SORT failed if the file descriptor was greater than 65,500 bytes. Since AMT34, the SORT failed if the file descriptor was greater than 65.500 bytes, as the Filecontroller did not allocate enough memory to be able read and write the file into the internal buffers AMT 39 can now handle these large files and will allocate enough memory to read and write the file into the buffers. From now on the machine memory will determine the limit. However, it can swap the file content and load the rest of the file again in the buffers. The number of records can be declared or will be determined by the Framework.	AMT 39
Generator	Various	ALL C1807-005 Modify behavior of numeric encoding setting. It was possible to set the numeric encoding in the application options and as generation set parameter. The generator will now check that the numeric encoding setting is done in one location, either in the application options or as generation set parameter. Also a numeric encoding value has been added in the list box for the numeric encoding in the application options: "Not set".	AMT 39
Control Center	Configuration	ALL FIX C1807-006 Missing error messages and exclamation marks in the ControlCenter. Normally, you would expect to see red icons with an exclamation mark and a warning message when required data was missing the menus of Control Center. However, due to a bug, administrators would not get properly informed about the fact that certain fields were incorrectly filled or left empty. In addition, Control Center would not throw an error message in all cases. As a result, in some cases, changes would not be implemented because the form was not filled correctly, without displaying an error message. We fixed this functionality in AMT 39.	AMT 39
Migration	COBOL	AMT COBOL C1807-007 Improved Performance and Logging in AMTCOBOL for migrated DMS2200 and IMS databases. Due to a check in the generator (part of) the database was loaded/generated multiple times during a whole system gen. In The generation log, the Database Summary appeared several times. Problem occurred only in test application that was migrated from the DMS2200 platform.Apllications migrated from RDMS don't show this behaviour. The check was changed to skip loading when the database objects already loaded. Resulting in better performance and less logging.	AMT 39
Runtime	Web Client	AMT LION 326868 SetFocus failed when fieldname contained a hyphen SetFocus on an occurrence fieldname containing a hyphen failed in the web client. Web client has been corrected to allow a SetFocus on a fieldname containing a hyphen is supported	AMT 39
Runtime	Jobs/Batches	ALL 326599 Non unique printfiles lost due to clean up Printfiles that would be overwritten every day by a reoccurring report will be lost after the cleanup process started to clean old print files. This only occurs with printfiles that are located in the same directory and don't use a unique name, for instance, based on a value and a date. The cleanup procedure will now check if there are newly created printrequest for the same file.	AMT 39
Migration	COBOL	AMT COBOL C1806-014 AMT COBOL parser improved for sources migrated from IBM COBOL. The AMT generator stopped in error in the following two instances: 1. Null reference exception on variable OCCURS DEPENDING ON EIBCALEN. 2. Not a literal number exception on: 01 VAR PIC Z9 88 BOOLVAR VALUE 'B' AMT COBOL now supports these code constructs as follows: 1. EIBCALEN was an IBM system variable, not handled properly in the DEPENDING ON clause. A check on null was added for the variable causing the exception. 2. The generator now generates C# code for literal number exception instead of ending in error.	AMT 39
Developer	Forms	[AMT LION\|AMT COBOL] C1807-016 The developer didn't show a signed label correctly when it had thousand separators set and no caption. There were not enough "~" chars displayed. Now also "~" is displayed for the 1000/decimal separators and also for the sign so the correct max length is displayed for this field.	AMT 39
Developer	Forms	AMT LION AND AMT COBOL C1707-018 Changing the Grid Style option in the Personal Options of the AMT DEV Studio had no direct effect. When changing the Grid Style option in the Personal Options (F10), any open forms needed to be closed and reopened for the change to take effect. Now from AMT39 this is applied immediately after closing the Personal Options window, and does not require the closing and reopening of the form to take effect.	AMT 39
Runtime	Web Client	AMT LION C1807-020 Pre-selected focus would be overridden. In Runtime, when you load a Listview, in a form for the first time, there will normally be a focus on the preselected row. This row, on which the focus lies, can be indicated in the AMT Developer Studio. However, the indicated row, in the List view, would not be selected in the webclient. The row would not be selected as the change, presented in AMT 38 (C1805-092), caused the original focus (defined focus) to be overridden by a inaccurately focus call. The listview will now ignore the next focus call when a focus on row call was performed.	AMT 39
Developer	Code Logic	ALL 326749 A format containing a space corrupts the print. The format ZZZ ZZZ,99 is not well formatted on the print layout and a possible workaround would be ZZZBZZZ,99. Now, the formatting allows the use of a space in the format and will behave the same as using the format character B. The general solution for this behavior is that the format is inspected at runtime and will be replaced by space when the characters before and after are 'Z' or '9' and the value is still zero.	AMT 39
Migration	DB2	AMT COBOL and AMT-VS C1807-027 DB2 and RDMS embedded SQL implementation improved in AMT COBOL. We have added the FAST_FORWARD attribute to the DECLARE CURSOR statement to achieve possible performance gains. By defining these attributes, of a Transact-SQL server cursor, in some cases performance will increase for read only, forward reading cursors Cursors on a MS SQL database now use a FAST_FORWARD cursor when possible for better performance. This is implemented for all EXEC SQL including OS2200 RDMS and IBM DB2. This may increase cursor performance for read only, forward reading cursors. FAST_FORWARD is not used when the cursor is updated or read in other directions (FETCH FIRST/PRIOR/LAST). For optimizing DB2 handling, we've also added the following cursor attributes - cursor FOR UPDATE (OF columns); - cursor/select OPTIMIZE FOR n ROW(S); - cursor/select WITH UR (uncommitted read).	AMT 39
Migration	DB2	AMT COBOL FIX C1807-028 EXEC DB2 statement LOCK TABLE IN SHARE MODE was not supported and caused validation/generation errors. The EXEC DB2 statement which locks a table – in SHARE or EXCLUSIVE mode –was not supported within our product. The LOCK TABLE statement could be used by using the following statement: ' LOCK TABLE '. Because it wasn't implemented it would cause validation and generation errors. As of AMT 39, this is supported in AMT Cobol framework. The generator will generate a call to the LockTable method. This also applies for OS2200 customers (for which a call was generated to a RdmsLock method in the OS2200). The functionality of the RdmsLock method is now included in the Lock method.	AMT 39
Developer	Code Logic	AMT COBOL C1807-029 Implementation of the SYNC clause for COMP-1 and COMP-2 (floating point) variables. With change C1805-046 (applied in AMT 37) we have implemented the COMP-1 and COMP-2 floating-point variables in AMT COBOL. However, the SYNC clause in COBOL, which was implemented previously with change C1804-016 (AMT 36), was not implemented for these new floating-point variables. The SYNC clause is now also implemented for COMP-1 and COMP-2 variables. Depending on the mainframe origin, these items, when using the SYNC clause, are now aligned on their natural boundaries (doubleword or word).	AMT 39
Runtime	Web Client	AMT-LION CHANGE C1807-031 Underline labels incorrectly removed After submitting a form in the web client, it incorrectly removed the underline of numeric labels when their value was set to 0 and ShowLeadingZeros was set to None. After submitting a form in the web client, the underline will correctly remain for numeric labels after their value is set to 0 and ShowLeadingZeros is set to None.	AMT 39
Developer	Code Logic	AMT COBOL C1807-033 In IBM DB2 it is possible to include declarations from an external file Double clicking on a filename/copy name in EXEC DB2 INCLUDE statement should show the content of the used COBOL Copy. It is now possible to quickly view the source of the included file by double clicking on the filename/copyname.	AMT 39
Runtime	Various	AMT LION 326984 Dividing negative values by -10, -100, -1000 could result in a negative value. When a signed numeric with a negative value was divided by another signed numeric with a negative value of -10, -100, -1000, -10000 the result would become negative instead of positive. Dividing a negative signed numeric by another negative signed numeric will now result in a positive value.	AMT 39
Runtime	Web Client	ALL 326940 Auto search in comboboxes always start from beginning When one would perform an autosearch on a combobox, which holds multiple items of which a few share the few characters, only the first item would be selected when you type another character in the search bar. For example, if you have the words: mark and marketshare, entering mm would show mark in all occasions. Now the search will select the second item, third item, etc. when typing the first character multiple times.	AMT 39
Developer	Various	[AMT COBOL\|AMT LION] [FIX] 326919 In AMT Developer Studios, the group permission "create interface" was not honored and its name was confusing. In AMT Developer Studios, the group permission "create external interface" is now honored correctly. Also, in the permission assignment, the term "create interface" is now called "create external interface".	AMT 39
Migration	COBOL	AMT COBOL C1807-038 Incorrect values generated in C# for COBOL SPECIAL-NAMES class (hex-)values. When using multiple THRU combinations in a single special-names class, only the first combination was generated out correctly in C#. For the following combinations "THRU" was also seen as a value and all hex-values were generated out incorrectly. Both problems are resolved.	AMT 39
Generator	Various	AMT COBOL C1807-039 [work in progess] Two-dimensional array of screen-items did not compile well The COBOL code in Forms was not properly generated when one would add a two-dimensional array of screen-items to the form. The underlying C# code would be compiled, however in runtime the screen-items , that were part of a two-dimensional array, were not used at all. This has been resolved.	AMT 39
Runtime	Web Client	AMT LION 326970 Parameter order and class member casing not correct implemented in consumable web services In the previous versions, the parameter order and the casing of class members were not added in the correct order to the soap-envelop, which is being sent to the web service. Instead of adding these in the order of the contract they would be added in an alphanumeric order instead. Now the parameter order and member casing are correct as specified in the WSDL.	AMT 39
Developer	Code Logic	AMT COBOL C1807-052 Right clicking on a table field which is defined with EXEC DB2 DECLARE TABLE caused an exception in the AMT Developer Studio. The exception occurred because of a null reference when resolving the table. This is solved by checking for null and using another object.	AMT 39
Generator	Various	[AMT LION\|AMT COBOL] C1807-070 Initial research for signing assemblies to check any functional impact on the product. Changes are made to the parser to investigate the possibility of signing assemblies in the future.	AMT 39
Developer - Other	Various	AMT LION\| AMT COBOL FIX C1807-073 Show difference incorrect with multiple spaces or help texts. A difference in spaces in a report descriptions for example was not shown as difference. Also when having multiple line help text the show differences showed the wrong colours on the lines below this. Both also effected the new preview merge function. In the show diff we are ignoring none important spaces (Because of the alignment functions). This was done on all data kinds (options/screen/logic/etc) now its only done for the logic part. Any space difference in a report description (and others) are now also shown in the show difference/merge window. When having help text (and other multiple line values) in the form designer then the show difference/merge window now shows the correct lines. Especially when difference in the number of help lines.	AMT 39
Runtime	LionScreens	AMT LION C1807-081 [work in progress] Preview version AMTScreens Asysco proudly presents the first preview version of AMTScreens. Please, note that, since AMTScreens is a preview, it will not contain all the functionalities. Here is a brief description of all the tab sheets in this preview. MAINMENU The tab sheet formerly known as HOME will show the name of the current form. It is not a fixed caption. It will display the actual application, that's equivalent to the Application Center ( Web application). The appearances and dimensions will now be equal to what you see in the AMT Development Studio because the 'What-you-see-is-what-you-get' principle (WYSIWYG) has been applied to AMTScreens. MESSAGES The Messages tab will display the message (SME’s) thrown by a job or form. However, Currently, the “go back” button is not presented. RTQUERY RTQuery is in an early preview stage and not yet functional. JOB MESSAGES The Jobmessages tab sheet, formerly known as “Report messages/Requests”, displays messages sent by a job. When a job requires input, this can be entered in this screen (respond to input requests). USERS In this screen, it is possible to see the connected users. However, it is not possible to perform any actions. The user screens still needs some visual adjustments, as not all data is displayed correctly. (Also due to an existing issue it is possible that not all existing connections will be shown.) JOB MANAGEMENT Job management, formerly known as “report management”, is fully functional. Several issues with sorting that were present in Lionscreens have been solved in this AMTscreens preview. START JOB A filter was added to the 'start job' screen which allows the sorting on jobtypes. This screen is fully functional. MENU Not all menu options are currently implemented. (For example the options menu) The following features are not yet present: RTQuery functionality Macros Part of the security settings IMPORTANT NOTE: .NET Framework 4.6.1 is now a requirement on every client. The AMT Update for AMT 39 includes instructions on enabling this preview mode.	AMT 39

Developer - Other

Various

ALL C1801-066 Label authorisation policies In AMT 39, new functionality has been added to the AMT Developer Studio for assigning user group permissions to labels. This will give administrators the ability to allow or deny certain users from assigning objects to a label. E.g. A administrator can deny a Test user from assigning objects to the development label. Administrators can implement these restrictions by entering the Label Management screen, selecting a label, press the properties button and select the "Security" tab. Here is a list of permissions that have been added: Administrator User groups with this permission have also all below permissions and they can modify label management security. Look into User groups with permission can view the contents of the label Create Label User groups with this permission can create new (sub)labels Modify Label Users groups with this permission can modify the label name Delete Label Users groups with this permission can delete the label Assign Objects User groups with this permission can assign objects to the label Delete Objects User groups with this permission can delete objects within the label

AMT 39

Developer - Other

Various

ALL 307861 [Work in progress] Added support for script in the repository. In AMT 39, we've added the first stages for versioning support of scripts in the repository. We've made changes to the import/export/revision/label/etc. For now all changes, are hidden under a switch, so nothing is visable in the current release.

AMT 39

Runtime

Web Client

ALL 325607 Limits for input in edit box (webclient) should be equal to the desktop client. Editboxes in the webclient were allowed to take in more decimals than was indicated in the AMT Developer Studio. This was caused by the fact that the position of the decimal separator would be replaced by a value (number) too. This is why the edit box (in the webclient), for example, allowed input that resembled input equal to a Numeric value with the format 7.0 but was actually declared as a Numeric with the format 6.2. The editboxes in the webclient will now only allow the length and decimals specified in the AMT Developer Studio

AMT 39

Developer

Forms

AMT LION 326114 Groupbox was smaller than the caption In the AMT Developer Studio, the painting of the groupbox was incorrect due to the size of groupbox and the caption width. Therefore, the groupbox caption exceeded the groupbox when the size of the groupbox was smaller than the caption. The caption is now cropped to fit within the groupbox. The behavior now resembles how it would look at runtime.

AMT 39

Developer

Various

AMT LION [FIX] 326825 Public routines not shown in routines view After adding one or more public routines to a global performable routine, the new public routines didnt't show up in the routines-view (tree-view) on the left pane. Only the 'normal',non public, routines were shown. Now public routines will show-up in the tree-view. For global performables, created in a previous versions, the validation process will refresh the tree-view and show the public routines.

AMT 39

Developer

Various

ALL 326897 The show difference window would not show differences in the use of spaces. The 'Show Difference' window would not look into differences in the use of spaces, therefore, it was not able to show differences in cases where spaces are important, like for instance, spaces used inside a variable (var-na me-01). In AMT 39, we made changes to the behaviour of the parser, so that it will ignore unimportant differences in the use of the spacebar. EG. "target := source" is equal to " target := source". As these differences could exist due to differences in alignment and won't impact the functionality, but will of course report important differences when for example a space is in a string literal. For AMT COBOL, we've also added support for comparing a commented line and string literals with double quotes.

AMT 39

Migration

COBOL

AMT COBOL C1806-081 The DMS2200 statement MOVE AREA-KEY, AREA-NAME returned a "Not Implemented" exception while generating in AMT COBOL. DMS2200 specific MOVE AREA-KEY, AREA-NAME for RUN-UNIT, RECORD, AREA, SET, DB-KEY was not accepted by AMT COBOL. The code validation and generator both returned a "Not Implemented" error. It is now possible to use the DMS2200 MOVE AREA-KEY, AREA-NAME statement in AMT COBOL. Example: 01 ARNM USAGE IS AREA-NAME. MOVE AREA-NAME RUN-UNIT TO ARNM. DISPLAY ARNM.

AMT 39

Generator

Various

AMT VS C1806-085 Various minor AMT COBOL to VS generation issues related to the usage of copybooks. This change will have no influence on existing AMT COBOL customers. It will only effect new migration projects, when moving from AMT COBOL to VS

AMT 39

Runtime

Various

AMT COBOL C1806-086 AMT COBOL DMS2200 STORE statement, wrong database key calculated when database or area is empty. When a record, from a migrated DMS2200 platform, is inserted, a new unique database-key is calculated. This key was used by DMS2200 internally, but it was possible to find a record through all or part of this, resulting in the area key. AMT COBOL calculated the first key wrong when an area was empty. This could result in error when a fetch area-key, area-name was done. With this fix AMT COBOL calculates a correct database-key. Converted databases are not hit by this issue while there are no empty areas. New keys were already calculated right using the highest database-key in the database.

AMT 39

Runtime

Jobs/Batches

AMT COBOL 326951 The SORT failed if the file descriptor was greater than 65,500 bytes. Since AMT34, the SORT failed if the file descriptor was greater than 65.500 bytes, as the Filecontroller did not allocate enough memory to be able read and write the file into the internal buffers AMT 39 can now handle these large files and will allocate enough memory to read and write the file into the buffers. From now on the machine memory will determine the limit. However, it can swap the file content and load the rest of the file again in the buffers. The number of records can be declared or will be determined by the Framework.

AMT 39

Generator

Various

ALL C1807-005 Modify behavior of numeric encoding setting. It was possible to set the numeric encoding in the application options and as generation set parameter. The generator will now check that the numeric encoding setting is done in one location, either in the application options or as generation set parameter. Also a numeric encoding value has been added in the list box for the numeric encoding in the application options: "Not set".

AMT 39

Control Center

Configuration

ALL FIX C1807-006 Missing error messages and exclamation marks in the ControlCenter. Normally, you would expect to see red icons with an exclamation mark and a warning message when required data was missing the menus of Control Center. However, due to a bug, administrators would not get properly informed about the fact that certain fields were incorrectly filled or left empty. In addition, Control Center would not throw an error message in all cases. As a result, in some cases, changes would not be implemented because the form was not filled correctly, without displaying an error message. We fixed this functionality in AMT 39.

AMT 39

Migration

COBOL

AMT COBOL C1807-007 Improved Performance and Logging in AMTCOBOL for migrated DMS2200 and IMS databases. Due to a check in the generator (part of) the database was loaded/generated multiple times during a whole system gen. In The generation log, the Database Summary appeared several times. Problem occurred only in test application that was migrated from the DMS2200 platform.Apllications migrated from RDMS don't show this behaviour. The check was changed to skip loading when the database objects already loaded. Resulting in better performance and less logging.

AMT 39

Runtime

Web Client

AMT LION 326868 SetFocus failed when fieldname contained a hyphen SetFocus on an occurrence fieldname containing a hyphen failed in the web client. Web client has been corrected to allow a SetFocus on a fieldname containing a hyphen is supported

AMT 39

Runtime

Jobs/Batches

ALL 326599 Non unique printfiles lost due to clean up Printfiles that would be overwritten every day by a reoccurring report will be lost after the cleanup process started to clean old print files. This only occurs with printfiles that are located in the same directory and don't use a unique name, for instance, based on a value and a date. The cleanup procedure will now check if there are newly created printrequest for the same file.

AMT 39

Migration

COBOL

AMT COBOL C1806-014 AMT COBOL parser improved for sources migrated from IBM COBOL. The AMT generator stopped in error in the following two instances: 1. Null reference exception on variable OCCURS DEPENDING ON EIBCALEN. 2. Not a literal number exception on: 01 VAR PIC Z9 88 BOOLVAR VALUE 'B' AMT COBOL now supports these code constructs as follows: 1. EIBCALEN was an IBM system variable, not handled properly in the DEPENDING ON clause. A check on null was added for the variable causing the exception. 2. The generator now generates C# code for literal number exception instead of ending in error.

AMT 39

Developer

Forms

[AMT LION|AMT COBOL] C1807-016 The developer didn't show a signed label correctly when it had thousand separators set and no caption. There were not enough "~" chars displayed. Now also "~" is displayed for the 1000/decimal separators and also for the sign so the correct max length is displayed for this field.

AMT 39

Developer

Forms

AMT LION AND AMT COBOL C1707-018 Changing the Grid Style option in the Personal Options of the AMT DEV Studio had no direct effect. When changing the Grid Style option in the Personal Options (F10), any open forms needed to be closed and reopened for the change to take effect. Now from AMT39 this is applied immediately after closing the Personal Options window, and does not require the closing and reopening of the form to take effect.

AMT 39

Runtime

Web Client

AMT LION C1807-020 Pre-selected focus would be overridden. In Runtime, when you load a Listview, in a form for the first time, there will normally be a focus on the preselected row. This row, on which the focus lies, can be indicated in the AMT Developer Studio. However, the indicated row, in the List view, would not be selected in the webclient. The row would not be selected as the change, presented in AMT 38 (C1805-092), caused the original focus (defined focus) to be overridden by a inaccurately focus call. The listview will now ignore the next focus call when a focus on row call was performed.

AMT 39

Developer

Code Logic

ALL 326749 A format containing a space corrupts the print. The format ZZZ ZZZ,99 is not well formatted on the print layout and a possible workaround would be ZZZBZZZ,99. Now, the formatting allows the use of a space in the format and will behave the same as using the format character B. The general solution for this behavior is that the format is inspected at runtime and will be replaced by space when the characters before and after are 'Z' or '9' and the value is still zero.

AMT 39

Migration

DB2

AMT COBOL and AMT-VS C1807-027 DB2 and RDMS embedded SQL implementation improved in AMT COBOL. We have added the FAST_FORWARD attribute to the DECLARE CURSOR statement to achieve possible performance gains. By defining these attributes, of a Transact-SQL server cursor, in some cases performance will increase for read only, forward reading cursors Cursors on a MS SQL database now use a FAST_FORWARD cursor when possible for better performance. This is implemented for all EXEC SQL including OS2200 RDMS and IBM DB2. This may increase cursor performance for read only, forward reading cursors. FAST_FORWARD is not used when the cursor is updated or read in other directions (FETCH FIRST/PRIOR/LAST). For optimizing DB2 handling, we've also added the following cursor attributes - cursor FOR UPDATE (OF columns); - cursor/select OPTIMIZE FOR n ROW(S); - cursor/select WITH UR (uncommitted read).

AMT 39

Migration

DB2

AMT COBOL FIX C1807-028 EXEC DB2 statement LOCK TABLE IN SHARE MODE was not supported and caused validation/generation errors. The EXEC DB2 statement which locks a table – in SHARE or EXCLUSIVE mode –was not supported within our product. The LOCK TABLE statement could be used by using the following statement: ' LOCK TABLE '. Because it wasn't implemented it would cause validation and generation errors. As of AMT 39, this is supported in AMT Cobol framework. The generator will generate a call to the LockTable method. This also applies for OS2200 customers (for which a call was generated to a RdmsLock method in the OS2200). The functionality of the RdmsLock method is now included in the Lock method.

AMT 39

Developer

Code Logic

AMT COBOL C1807-029 Implementation of the SYNC clause for COMP-1 and COMP-2 (floating point) variables. With change C1805-046 (applied in AMT 37) we have implemented the COMP-1 and COMP-2 floating-point variables in AMT COBOL. However, the SYNC clause in COBOL, which was implemented previously with change C1804-016 (AMT 36), was not implemented for these new floating-point variables. The SYNC clause is now also implemented for COMP-1 and COMP-2 variables. Depending on the mainframe origin, these items, when using the SYNC clause, are now aligned on their natural boundaries (doubleword or word).

AMT 39

Runtime

Web Client

AMT-LION CHANGE C1807-031 Underline labels incorrectly removed After submitting a form in the web client, it incorrectly removed the underline of numeric labels when their value was set to 0 and ShowLeadingZeros was set to None. After submitting a form in the web client, the underline will correctly remain for numeric labels after their value is set to 0 and ShowLeadingZeros is set to None.

AMT 39

Developer

Code Logic

AMT COBOL C1807-033 In IBM DB2 it is possible to include declarations from an external file Double clicking on a filename/copy name in EXEC DB2 INCLUDE statement should show the content of the used COBOL Copy. It is now possible to quickly view the source of the included file by double clicking on the filename/copyname.

AMT 39

Runtime

Various

AMT LION 326984 Dividing negative values by -10, -100, -1000 could result in a negative value. When a signed numeric with a negative value was divided by another signed numeric with a negative value of -10, -100, -1000, -10000 the result would become negative instead of positive. Dividing a negative signed numeric by another negative signed numeric will now result in a positive value.

AMT 39

Runtime

Web Client

ALL 326940 Auto search in comboboxes always start from beginning When one would perform an autosearch on a combobox, which holds multiple items of which a few share the few characters, only the first item would be selected when you type another character in the search bar. For example, if you have the words: mark and marketshare, entering mm would show mark in all occasions. Now the search will select the second item, third item, etc. when typing the first character multiple times.

AMT 39

Developer

Various

[AMT COBOL|AMT LION] [FIX] 326919 In AMT Developer Studios, the group permission "create interface" was not honored and its name was confusing. In AMT Developer Studios, the group permission "create external interface" is now honored correctly. Also, in the permission assignment, the term "create interface" is now called "create external interface".

AMT 39

Migration

COBOL

AMT COBOL C1807-038 Incorrect values generated in C# for COBOL SPECIAL-NAMES class (hex-)values. When using multiple THRU combinations in a single special-names class, only the first combination was generated out correctly in C#. For the following combinations "THRU" was also seen as a value and all hex-values were generated out incorrectly. Both problems are resolved.

AMT 39

Generator

Various

AMT COBOL C1807-039 [work in progess] Two-dimensional array of screen-items did not compile well The COBOL code in Forms was not properly generated when one would add a two-dimensional array of screen-items to the form. The underlying C# code would be compiled, however in runtime the screen-items , that were part of a two-dimensional array, were not used at all. This has been resolved.

AMT 39

Runtime

Web Client

AMT LION 326970 Parameter order and class member casing not correct implemented in consumable web services In the previous versions, the parameter order and the casing of class members were not added in the correct order to the soap-envelop, which is being sent to the web service. Instead of adding these in the order of the contract they would be added in an alphanumeric order instead. Now the parameter order and member casing are correct as specified in the WSDL.

AMT 39

Developer

Code Logic

AMT COBOL C1807-052 Right clicking on a table field which is defined with EXEC DB2 DECLARE TABLE caused an exception in the AMT Developer Studio. The exception occurred because of a null reference when resolving the table. This is solved by checking for null and using another object.

AMT 39

Generator

Various

[AMT LION|AMT COBOL] C1807-070 Initial research for signing assemblies to check any functional impact on the product. Changes are made to the parser to investigate the possibility of signing assemblies in the future.

AMT 39

Developer - Other

Various

AMT LION| AMT COBOL FIX C1807-073 Show difference incorrect with multiple spaces or help texts. A difference in spaces in a report descriptions for example was not shown as difference. Also when having multiple line help text the show differences showed the wrong colours on the lines below this. Both also effected the new preview merge function. In the show diff we are ignoring none important spaces (Because of the alignment functions). This was done on all data kinds (options/screen/logic/etc) now its only done for the logic part. Any space difference in a report description (and others) are now also shown in the show difference/merge window. When having help text (and other multiple line values) in the form designer then the show difference/merge window now shows the correct lines. Especially when difference in the number of help lines.

AMT 39

Runtime

LionScreens

AMT LION C1807-081 [work in progress] Preview version AMTScreens Asysco proudly presents the first preview version of AMTScreens. Please, note that, since AMTScreens is a preview, it will not contain all the functionalities. Here is a brief description of all the tab sheets in this preview. MAINMENU The tab sheet formerly known as HOME will show the name of the current form. It is not a fixed caption. It will display the actual application, that's equivalent to the Application Center ( Web application). The appearances and dimensions will now be equal to what you see in the AMT Development Studio because the 'What-you-see-is-what-you-get' principle (WYSIWYG) has been applied to AMTScreens. MESSAGES The Messages tab will display the message (SME’s) thrown by a job or form. However, Currently, the “go back” button is not presented. RTQUERY RTQuery is in an early preview stage and not yet functional. JOB MESSAGES The Jobmessages tab sheet, formerly known as “Report messages/Requests”, displays messages sent by a job. When a job requires input, this can be entered in this screen (respond to input requests). USERS In this screen, it is possible to see the connected users. However, it is not possible to perform any actions. The user screens still needs some visual adjustments, as not all data is displayed correctly. (Also due to an existing issue it is possible that not all existing connections will be shown.) JOB MANAGEMENT Job management, formerly known as “report management”, is fully functional. Several issues with sorting that were present in Lionscreens have been solved in this AMTscreens preview. START JOB A filter was added to the 'start job' screen which allows the sorting on jobtypes. This screen is fully functional. MENU Not all menu options are currently implemented. (For example the options menu) The following features are not yet present: RTQuery functionality Macros Part of the security settings IMPORTANT NOTE: .NET Framework 4.6.1 is now a requirement on every client. The AMT Update for AMT 39 includes instructions on enabling this preview mode.

AMT 39

AMT 39

Special attention items: