Amt 31

Cat	Subcat	Description	Version
Runtime	Web Client	318874 Minor corrections to alignment in web client. Vertical text was truncated in Microsoft Edge. Vertical fieldset legends were not aligned with text in Chrome, Edge, and Firefox. Horizontal Text beginning with " " was misaligned. Code change deployed to correctly position elements in Edge, Chrome and Firefox.	AMT 31
Runtime	Various	C1801-041 The "MainframeOS" property of the ComScript object wasn't described in the helpfiles. But the new (renamed) property "ApplicationKind" should be described, since existing customer which are currently using the "MainframeOS" property should change it into "ApplicationKind" with the correct value. Depending on the required application behavior the new property "ApplicationKind" should be set to one of the following values: - LionASeries (default) - LionOS2200 - LionUnix - CobolASeries - CobolIbmCics - CobolOS2200 - CobolMiFoUnix If the "ApplicationKind" property is left empty, the default behaviour "LionASeries" is used. The old property "MainframeOS" could have the following values: - ASERIES - OS2200 - IBM - UNIX Customers which are currently using the "MainframeOS" property, by setting it to a specific value in the script library (or scripts itself), should change it to the "ApplicationKind" property. "MainframeOS" property with the value ASERIES should be changed into: "ApplicationKind" property with the value: LionASeries (or just leave it empty) "MainframeOS" property with the value OS2200 should be changed into: "ApplicationKind" property with the value: LionOS2200 or CobolOS2200 (depening on if AMT LION or AMT COBOL) "MainframeOS" property with the value IBM should be changed into: "ApplicationKind" property with the value: CobolIbmCics "MainframeOS" property with the value UNIX should be changed into: "ApplicationKind" property with the value: CobolMiFoUnix For example, the following PowerShell code: $global:Com = New-Object Asysco.Amt.Scripting.Comscript $global:Com.SysIniFile = $global:AmtSettings.IniFile $global:Com.AppName = $global:AmtSettings.AppName $global:Com.JobName = [System.IO.Path]::GetFileNameWithoutExtension($MyInvocation.ScriptName) $global:Com.MainframeOS = "IBM" $global:Com.Connect() Must be changed into: $global:Com = New-Object Asysco.Amt.Scripting.Comscript $global:Com.SysIniFile = $global:AmtSettings.IniFile $global:Com.AppName = $global:AmtSettings.AppName $global:Com.JobName = [System.IO.Path]::GetFileNameWithoutExtension($MyInvocation.ScriptName) $global:Com.ApplicationKind = "CobolIbmCics" $global:Com.Connect()	AMT 31
Developer	Various	324054 Fixed the highlighting issues in the Developer and in the Debugger Variable declarations and labels with hyphens were not getting the correct colours assigned. In some cases it would only partially highlight the declaration / label, when you've changed, for instance, the keyword colours in the personal options. As of AMT 31, Labels and variable declarations are now displayed correctly	AMT 31
Developer	Various	322502 The Layout and behaviour of the authority windows changed. The Access tab found in the Authority window (Security window) of the AMT Developer still displayed some LION features in the COBOL product. The Security access tab now shows only the access items of the actual version setting when a Group and Application is selected. The layout has also been updated to be more consistent through the whole Authority window.	AMT 31
Generator	Various	C1711-041 "No routine expected" error unnecessary thrown. When you would use an event on a control in an insertable the developer would show a false error message. However, this construction would just work. We made changes to the insertable form, a few versions ago, to make this possible. The false error is removed as of AMT 31.	AMT 31
Runtime	Various	326026 Configurable case-sensitivity added to the IndexOf command. In LION6, IndexOf was not case sensitive. IndexOf has been updated with an optional boolean parameter for case sensitivity. The default value is True.	AMT 31
Control Center	Configuration	326089 Hex value printer filter couldn't not be set to a different state. The "Hex value printer filter" can not be set in the Runtime behaviour config. When you would tick one or two options and then apply this choice, your selected values would not be set, the setting would be set to the previous setting and your choice would be emptied out again We've corrected the behaviour to correctly save the selected values to the database and it now works as expected again.	AMT 31
Control Center	Configuration	323899 Additional user diagnostics added to Control Center. When troubleshooting load balanced environments it was difficult to track user sessions between servers. Additional user details such as IP address, GUI Server, Logic Server, Client Version, and SessionID are now accessible through Server Control in Control Center.	AMT 31
Control Center	Various	326104 We've corrected a few remaining display ( LION / COBOL) leftovers for Control Center COBOL specific elements shouldn't been shown when the system is set to be a LION application and vice versa: Here's summary of all the changes: LION & COBOL: 'Print service: Station/Office name', LION & COBOL: 'Jobtype dropbox', COBOL: 'Process Control' in menu 'Applications text', COBOL: menu 'System Configuration text', COBOL: menu 'Security text'. LION & COBOL: menu 'Processed text', COBOL: Forms in general, 'Available Forms' in particular. COBOL specific items are now hidden when the system is set for LION and vice versa.	AMT 31
Runtime	Scripts	326131 Scheduled Jobs could break due to changes in the Jobnames. In particular cases, a scheduled job wouldn't start anymore due to a change in the script name or scriptpath in Control Center. The AMT framework would then delete the old instances from the 'Available Jobs and Reports' sections and create a new instance of the Form or Report with a new Job ID. Unfortunately, JobID's would not change for Scheduled Jobs, so, the scheduler could not find the job. In AMT 31, the behaviour of the automatic update function has been changed to better handle changes in available Forms/Jobs and Scripts. The function will now perform a check based on job name instead of filename.	AMT 31
Developer - Revision Control	Various	305106 The Developer will now allow comparison of two different objects. As of AMT 31, two objects of the same type (and within the same application) can be compared in the revision history menu in AMT Developer Studio. Additionally, the Show Differences window allows the selection of another revision within that object.	AMT 31
Developer	Code Logic	C1801-039 Syntax check of an invalid query caused AMT Developer Studio to crash. When code validation occurred for a cursorquery or tablequery without a defined table, the developer would crash. The parser has been fixed to handle a missing table definition.	AMT 31
Developer	Code Logic	C1801-053 Improved exception handling added for naming conflicts between global routines and local variables. Local variable have higher priority than global routines, so if they have the same name, the developer will give an error. As of AMT 31, the local variable can now be used when this condition is true, but the global routine will still result in an error. In summary, local is preferred above global and mixed use is prohibited.	AMT 31
Runtime	Various	C1801-056 Added COBOL "IN" keyword functionality to the AMT Debugger. COBOL variable names require the "IN" keyword so that the same name may be used within different structures. "IN" keyword support added for watches in the AMT Debugger.	AMT 31
Runtime	Various	C1801-057 Resolved watch tooltip scaling issues in AMT Debugger. Tooltip scaling grew too large for the screen in some cases due to automatic scaling. A maximum width of 500px has been set for the element.	AMT 31
Developer	Various	C1801-060 Minor bug fixes and changes for OS2200 COBOL DMS objects in AMT Developer. DMS object handling caused exceptions and crashes when editing. Code fixes deployed to resolve errors.	AMT 31
AmtTools	Prodinstall/Pinstall	C1801-074 ProdInstall improvements for AMT COBOL and AMT LION. Reported issues with ProdInstall for AMT Cobol: -Deleted files pop-up did not display. -Deleted files did not include COBOL folders. (programs/subprograms) -Private Debug files not copied when debug checkbox enabled. -ClientGui folder created for AMT COBOL even though it is exclusive to AMT LION. Minor bug fixes deployed along with the following enhancements: -Base folders only created when "Scan Directories" used. -Delete empty folders following sync. (excluding base folders) -Always delete debug files for previous version.	AMT 31

Runtime

Web Client

318874 Minor corrections to alignment in web client. Vertical text was truncated in Microsoft Edge. Vertical fieldset legends were not aligned with text in Chrome, Edge, and Firefox. Horizontal Text beginning with " " was misaligned. Code change deployed to correctly position elements in Edge, Chrome and Firefox.

AMT 31

Runtime

Various

C1801-041 The "MainframeOS" property of the ComScript object wasn't described in the helpfiles. But the new (renamed) property "ApplicationKind" should be described, since existing customer which are currently using the "MainframeOS" property should change it into "ApplicationKind" with the correct value. Depending on the required application behavior the new property "ApplicationKind" should be set to one of the following values: - LionASeries (default) - LionOS2200 - LionUnix - CobolASeries - CobolIbmCics - CobolOS2200 - CobolMiFoUnix If the "ApplicationKind" property is left empty, the default behaviour "LionASeries" is used. The old property "MainframeOS" could have the following values: - ASERIES - OS2200 - IBM - UNIX Customers which are currently using the "MainframeOS" property, by setting it to a specific value in the script library (or scripts itself), should change it to the "ApplicationKind" property. "MainframeOS" property with the value ASERIES should be changed into: "ApplicationKind" property with the value: LionASeries (or just leave it empty) "MainframeOS" property with the value OS2200 should be changed into: "ApplicationKind" property with the value: LionOS2200 or CobolOS2200 (depening on if AMT LION or AMT COBOL) "MainframeOS" property with the value IBM should be changed into: "ApplicationKind" property with the value: CobolIbmCics "MainframeOS" property with the value UNIX should be changed into: "ApplicationKind" property with the value: CobolMiFoUnix For example, the following PowerShell code: $global:Com = New-Object Asysco.Amt.Scripting.Comscript $global:Com.SysIniFile = $global:AmtSettings.IniFile $global:Com.AppName = $global:AmtSettings.AppName $global:Com.JobName = [System.IO.Path]::GetFileNameWithoutExtension($MyInvocation.ScriptName) $global:Com.MainframeOS = "IBM" $global:Com.Connect() Must be changed into: $global:Com = New-Object Asysco.Amt.Scripting.Comscript $global:Com.SysIniFile = $global:AmtSettings.IniFile $global:Com.AppName = $global:AmtSettings.AppName $global:Com.JobName = [System.IO.Path]::GetFileNameWithoutExtension($MyInvocation.ScriptName) $global:Com.ApplicationKind = "CobolIbmCics" $global:Com.Connect()

AMT 31

Developer

Various

324054 Fixed the highlighting issues in the Developer and in the Debugger Variable declarations and labels with hyphens were not getting the correct colours assigned. In some cases it would only partially highlight the declaration / label, when you've changed, for instance, the keyword colours in the personal options. As of AMT 31, Labels and variable declarations are now displayed correctly

AMT 31

Developer

Various

322502 The Layout and behaviour of the authority windows changed. The Access tab found in the Authority window (Security window) of the AMT Developer still displayed some LION features in the COBOL product. The Security access tab now shows only the access items of the actual version setting when a Group and Application is selected. The layout has also been updated to be more consistent through the whole Authority window.

AMT 31

Generator

Various

C1711-041 "No routine expected" error unnecessary thrown. When you would use an event on a control in an insertable the developer would show a false error message. However, this construction would just work. We made changes to the insertable form, a few versions ago, to make this possible. The false error is removed as of AMT 31.

AMT 31

Runtime

Various

326026 Configurable case-sensitivity added to the IndexOf command. In LION6, IndexOf was not case sensitive. IndexOf has been updated with an optional boolean parameter for case sensitivity. The default value is True.

AMT 31

Control Center

Configuration

326089 Hex value printer filter couldn't not be set to a different state. The "Hex value printer filter" can not be set in the Runtime behaviour config. When you would tick one or two options and then apply this choice, your selected values would not be set, the setting would be set to the previous setting and your choice would be emptied out again We've corrected the behaviour to correctly save the selected values to the database and it now works as expected again.

AMT 31

Control Center

Configuration

323899 Additional user diagnostics added to Control Center. When troubleshooting load balanced environments it was difficult to track user sessions between servers. Additional user details such as IP address, GUI Server, Logic Server, Client Version, and SessionID are now accessible through Server Control in Control Center.

AMT 31

Control Center

Various

326104 We've corrected a few remaining display ( LION / COBOL) leftovers for Control Center COBOL specific elements shouldn't been shown when the system is set to be a LION application and vice versa: Here's summary of all the changes: LION & COBOL: 'Print service: Station/Office name', LION & COBOL: 'Jobtype dropbox', COBOL: 'Process Control' in menu 'Applications text', COBOL: menu 'System Configuration text', COBOL: menu 'Security text'. LION & COBOL: menu 'Processed text', COBOL: Forms in general, 'Available Forms' in particular. COBOL specific items are now hidden when the system is set for LION and vice versa.

AMT 31

Runtime

Scripts

326131 Scheduled Jobs could break due to changes in the Jobnames. In particular cases, a scheduled job wouldn't start anymore due to a change in the script name or scriptpath in Control Center. The AMT framework would then delete the old instances from the 'Available Jobs and Reports' sections and create a new instance of the Form or Report with a new Job ID. Unfortunately, JobID's would not change for Scheduled Jobs, so, the scheduler could not find the job. In AMT 31, the behaviour of the automatic update function has been changed to better handle changes in available Forms/Jobs and Scripts. The function will now perform a check based on job name instead of filename.

AMT 31

Developer - Revision Control

Various

305106 The Developer will now allow comparison of two different objects. As of AMT 31, two objects of the same type (and within the same application) can be compared in the revision history menu in AMT Developer Studio. Additionally, the Show Differences window allows the selection of another revision within that object.

AMT 31

Developer

Code Logic

C1801-039 Syntax check of an invalid query caused AMT Developer Studio to crash. When code validation occurred for a cursorquery or tablequery without a defined table, the developer would crash. The parser has been fixed to handle a missing table definition.

AMT 31

Developer

Code Logic

C1801-053 Improved exception handling added for naming conflicts between global routines and local variables. Local variable have higher priority than global routines, so if they have the same name, the developer will give an error. As of AMT 31, the local variable can now be used when this condition is true, but the global routine will still result in an error. In summary, local is preferred above global and mixed use is prohibited.

AMT 31

Runtime

Various

C1801-056 Added COBOL "IN" keyword functionality to the AMT Debugger. COBOL variable names require the "IN" keyword so that the same name may be used within different structures. "IN" keyword support added for watches in the AMT Debugger.

AMT 31

Runtime

Various

C1801-057 Resolved watch tooltip scaling issues in AMT Debugger. Tooltip scaling grew too large for the screen in some cases due to automatic scaling. A maximum width of 500px has been set for the element.

AMT 31

Developer

Various

C1801-060 Minor bug fixes and changes for OS2200 COBOL DMS objects in AMT Developer. DMS object handling caused exceptions and crashes when editing. Code fixes deployed to resolve errors.

AMT 31

AmtTools

Prodinstall/Pinstall

C1801-074 ProdInstall improvements for AMT COBOL and AMT LION. Reported issues with ProdInstall for AMT Cobol: -Deleted files pop-up did not display. -Deleted files did not include COBOL folders. (programs/subprograms) -Private Debug files not copied when debug checkbox enabled. -ClientGui folder created for AMT COBOL even though it is exclusive to AMT LION. Minor bug fixes deployed along with the following enhancements: -Base folders only created when "Scan Directories" used. -Delete empty folders following sync. (excluding base folders) -Always delete debug files for previous version.

AMT 31

AMT 31

Special attention items: