Runtime behaviour configurations

The Runtime behavior configurations describes the runtime behaviour of the applications.

 
If view, add, edit or copy is clicked  the following popup window will appear

A Runtime behaviour has 6 tabsheets, General behaviour, Form behaviour, Form appearance, Web behaviour, Database behaviour and Maintenance.

Tab General behaviour

• Call Timeout: The maximum number of seconds that the calling process waits for the call to be executed
• Always write printer Macros: General setting for writing printermacros. Can be overruled per printer in printersettings
• Always write form depth: Always write the max number of lines to the printfile. 
• Overwrite printfile: If this option is selected, a report which produces multiple print copies will always overwrite the previous one with the last copy.
• Hex value printing filter: Depending on the selected filter option(s) the Print Controller can remove Hex00, Hex01 and/or HexFF characters from the print data.
  The default setting is to filter out HexFF characters but leave Hex00 and Hex01 characters in the print data. HexFF characters are used to denote PCL Codes. When HexFF is filtered out, AMT will check for any printer macro code and translate it.
  
  Note: Previous to AMT-20 the default behaviour was to filter out both Hex 00 and Hex 01 characters. For environments created before AMT-20, this behaviour will be kept after reorganizing the system database, which will enable both filter options automatically.
  Since AMT-44 Hex FF was added to the filter by default, which was also the previous behaviour. Only now there is the option to leave the Hex FF character in the print data when needed.
• Save copy of printfile in print folder: If this option is selected, printfiles created outside the print-folder will be copied to the printfolder into today's date, with its original filename with batch Id attached to the filename to make it unique.
  
  
• Do not register empty printfiles: When this option is selected, reports producing no output will not be visible in the Prints menu option of the Control Center. 
• Logging level: integer, 0 to 5. 0 = no logging, 5 = full logging 
• Development: If this option is selected, the behavior of the application is as it is developed for the development environment. Developers can enable or disable code by referring to the system item "DEVELOPMENT" (which is set to "TRUE" if the Development version option is selected).
  
   
• Use date: For testpurposes. Gives the possibility to run the application with a 'today' date that is specified in this field. The format should be ccyymmdd, so use 20110101 for january the first, 2011. When no date has to be specified use 0.
• Batchcontroller startreport hook: Path to a dll that has to be started when a report is started.
• Printcontroller printfile hook: Path to a dll that has to be started when a printing command is given. This makes it possible to manipulate data before its printed. See Print File Hook.
• Transaction execution hook: Path to a dll that can be used to manipulate the transaction data. The hook is called twice, right before executing the transaction program, and after executing the transaction program. See Transaction Execution Hook.
• Stack size [MB]: The stack size, in megabytes, to be used by batchcontrollers and transaction servers when creating new threads. The default setting is a stack size of 1 MB.
• Exception on array out of bounds: When set to Yes an exception will be raised when in the runtime an array is accessed out of bounds, When set to No element zero will be returned and it will be empty on read.

 

Tab Form behaviour

• Xmit Timeout: Here you specify the maximal number of seconds to wait for a response from the transaction server after a transmit. 
  The default setting is 300 seconds (5 minutes), this should be high enough for most environments. This setting should be changed when users regularly receive transmit timeout messages, when this happens it is advised to contact the Asysco Customer Service to determine the recommended timeout value for that specific environment. Allowed values are 1 to 2000000 (two million). Please note, if the Xmit timeout is set higher than 900 seconds, the asyncTimeout value in the web client web.config file should also be increased to the same value. This web.config file can be found in the client folder of your application.
  Note: This timeout is not used for AMT Debugger sessions.
• Session Data Timeout (hours): The time before the Session Data times out in hours. Zero means there will be no data timeout for 8 hours. Note: for web sessions also the IIS recycle time should be taken into account.
• Auto tab numeric fields: If this option is checked, automatic tab is enabled in Numeric edit fields.
• HelpText ShowTime: The number of seconds a help text should be shown in AMT Screens when the user put the mouse on an item. Default is 3.5 seconds and for unlimited enter -1 (as long as the mouse is on the item). Note: this feature can only be used in AMT Screens due to browser restrictions.

Tab Form appearance

• Show application description in caption: When this option is checked, the description of the application will be displayed in the browser tab when accessing the application.
• Show formname in caption: Not used in AMT COBOL.
• Show database in caption: Not used in AMT COBOL.
• Show sessionnr in caption: Not used in AMT COBOL.
• Caption additional text: Not used in AMT COBOL.
• Show screen description in tabsheet caption: When this option is checked, the description of the screen will be added to the name of the form  that is displayed in the tab of the tabsheet.
• Background color: When set to a single hexadecimal RGB value (E.g. #AABBCC) all the forms will get that color as background color. When the format #rgb;#RGB is used (E.g. #c0c0c0;#AABBCC) all the forms with background color #c0c0c0 will be given the background color #AABBCC. Note: #c0c0c0 is the default AMT-COBOL background color.

 

Tab Web Behaviour

• Use an alert box for messages: There are three options,
  • Use Div if multiple messages (Default)
  • Use AlertBox if multiple messages
  • Use AlertBox if any messages

 

Tab Database behaviour

• Database lock Timeout: The number specifies the number of seconds that a screen waits before a database-lock is released. If the lock is not released after this time, the user will get an error message that the transaction has been timed out.
• Database lock Timeout reports: The number specifies the number of seconds that a report waits before a database-lock is released. If the lock is not released after this time, the report will retry it for a number of times.
• SQL Command Timeout: The number specifies the number of seconds that a screen or report waits for a SQL Command to be performed. If the command is not performed after this time, the user will get an error message that the SQL command has been timed out.
• Database replication: Select this when replication is used in the MSSQL database.

 

Tab Maintenance

• Automatically update available forms: When checked the Batch Controller will detect newly added Forms and add them to the list of Available Forms.
• Automatically update available programs: When checked the Batch Controller will detect newly added Programs in the Programs folder and add them to the list of Available Jobs. Newly added External Windows Programs will also be detected and added.
• Automatically update available scripts: When checked the Batch Controller will detect newly added Scripts in the Scripts folder and add them to the list of Available Jobs.