Application

This folder contains the application wide settings.

ApplicationRt.java

The ApplicationRt.java file contains the Application Options for this application.

loadApplicationOptions

The following table describes the available application options.

Option	Description	Type
setInitialTransaction	The opening transaction within the application.	String
setTerminalForm	The name of the terminal form.	String
setSignEncoding	The overpunch encoding used for signed numerics when overpunch is used. See Overpunch for more information.	SignEncoding (enum) value
setDefaultLanguage	The default language of the application.	String
setDecimalSign	Separator used for decimal characters.	Char
setSeparator1000Sign	Character used as thousand separator.	Char
setParamSize	The size of System item SI-PARAM to use for this Application. Maximum size is 64K	Integer
setSetDbStatus	This setting is not applicable for COBOL applications. If set to false, the execution of Forms and Reports will be aborted if certain database errors occur, such as deadlocks etc. If set to true, the execution of the Form or Report will continue and SI-DBSTATUS will be set to the specific error. It is the programmers' responsibility to check SI-DBSTATUS after every database access in that case. In the Form/Report options, it is possible to override this default setting.	Boolean
setPrintingLfStyle	If the option "PrintingLfStyle" is set to true, for each print layout in the application: every line will be followed by a carriage return (cr). This means that the printer position is set to the beginning of the line. every new line will be preceded with a line feed (lf). This means that the printer position is set to the next line. This option makes it possible to print a new line over another line. If the first line on a print layout should not be preceded with a line feed, you can use the suboption NOSKIP in the PRINT instruction. The line number value will then be decremented with one. Attention! This option can have unpredicted consequences for the formfeed. If you are contemplating the use of this option, it is recommended to test this thoroughly to find out the exact consequences for your environment.	Boolean
setReadFileSharedMode	If set to true, Readfiles will be executed in Shared Mode instead of the default Locked Mode .	Boolean
setDatabaseUnicode	If set to true, alpha fields in all tables can contain Unicode. If exporting Unicode data to ASCII files, non ASCII characters are replaced by question marks.	Boolean
setFilesUnicode	If set to true, sets Unicode as the default option for all extracted files. This can be overwritten using the following syntax in the file definition: FILE SECTION. FD MYFILE ENCODING IS UTF16 Or: ENCODING IS ASCII	Boolean
setFileRecordEnding	Defines how records will be delimited in a text based data file. This setting is used as default and can be changed when adding a file-id. Possible values are: - DEFAULT the line seperator setting of the system - CR_LF Carriage return plus line feed - CR Carriage return only - LF Line feed only - NONE No delimiting. Records are seperated based on record length only.	FileRecordEnding (enum) value
setDuplicateRecordAction	Action to perform on a duplicate record insert. Possible values are: - ABORT - WARNING_MESSAGE - NO_MESSAGE	DuplicateRecordAction (enum) value
setDateConvertInfo	An instance of the DateConvertInfo class needs to be set by calling the getDateConvertInfo method. A description of the members of this class is located in the table below.	DateConvertInfo object

DateConvertInfo

The following table describes the DateConvert options.

Option	Description	Type
useRegMthShort	When set to true short three letter names will be used for the months names. Only one of the properties UserRegMthShort and UseRegMthLong should be set to true at the same time	Boolean
useRegMthLong	When set to true the normal full month names will be used. Only one of the properties UserRegMthShort and UseRegMthLong should be set to true at the same time.	Boolean
useRegDaylong	When set to true the full day names will be used.	Boolean
monthLongNames	A list of full month names. E.g. "JANUARY".	List<String>
monthShortNames	A list of month names shortened to 3 characters. E.g. "FEB".	List<String>
daylongNames	A list of full day names. E.g. "WEDNESDAY".	List<String>
validDateFrom	Sets the start year of the Valid date range.	Integer
validDateTill	Sets the end year of the Valid date range.	Integer
allow1DigitMonth	Set to True to allow 1-digit month numbers in date formats using a '-' separator	Boolean
useIso8601Week	Set to True to use Iso8601 standard for week numbering.	Boolean
dateSeparator	Set the character to be used as date separator.	Char
baseYear	Contains the year of which the 1st of January represents the day number zero. This value is used in calculation with relative day numbers (number of days after the BaseYear) to calculate a date value for the class. Although the property has a setter, it's value should never be changed in the code of the application. Normally this value should be 1900.	Integer
shiftingTimeframe	Get or set the Shifting time frame value in two digit format (YY). This value is used to determine the first two digits for the year-definitions to be added when only the last two digits for the year are specified. The deviation between the current year (yy) and the shifting time frame determines the "splitting point". If the last year digits (yy) are specified but the century digits (cc) are omitted in a date value, and the year value is equal to or higher than the splitting point value, the century digits will be set to "19". Otherwise, the century digits will be set to "20". If the shifting time frame is set to 56 and the current year is 2003, the splitting point will be set to 59. This means that conversion of 6 digit dates (DDMMYY) to 8 digit dates (DDMMCCYY) will be as follows: The YY values from 59 to 99 will lead to CCYY values of 1959 to 1999 and the YY values of 00 to 58 will lead to CCYY values of 2000 to 2058.	Integer