You can use several FSISYS.INI file control groups and options to control the way the system processes DAL functions and scripts. These options let you:
This table shows the various control groups and options, along with a description of what you should enter for each option.
The system also provides a number of specialized INI Functions.
Option |
Explanation |
|
Enter No to maintain the defined target variables and their contents from the previous form set. The default is Yes, which tells the system to delete DAL target variables between form set processing. |
||
Enter the cutoff year for determining the century. For instance, if you enter 50 for this option, the system assumes a two-digit year greater than or equal to 50 should be prefaced by 19. If you omit this option, the system assumes the current century when it encounters a two-digit year. All internal date manipulation is performed using four-digit years. |
||
Enter a period and an extension. The default is DAL. Use this option to define the file extension used for external DAL scripts and file names. |
||
Enter DLLMOD->FunctionName. This option defines the DLL-based DAL functions that are automatically registered and made available to the scripts executed in the session. This option is used by the DAL runtime tool (DALRUN). |
||
Enter Yes to compile each DAL library file when loaded. In situations where you are processing a lot of transactions and you have a lot of DAL functions which are used during processing, this can speed performance. The default is No. |
||
Use this option to specify the DAL library file to be loaded. You can specify multiple files. There is no default for this option. |
||
Enter a file name. Use this option to specify the file name of the script to execute. You can use any file extension. If you omit the extension, the system assumes if is DAL. |
||
Enter a title.The default is DALRUN - Document Automation Language Runtime |
||
Enter Yes to clear DAL internal variables set by the previous transaction before the subsequent transaction is processed. Use the Retain function to identify DAL variables you do not want cleared. The default is No. |
||
Enter Yes to have the system create debug information related to the execution of library subroutines. The default is No. |
||
Enter Yes to create debug date related to the execution of each DAL function or procedure that is executed. The default is No. |
||
Enter the name of the DAL script for which you want to generate debug data. You can also enter All, which tells the system to generate data for all DAL scripts. Be sure to set the DALLib option to Yes if you use the DumpDAL option. The system sends the output to the file you specified with the TraceFile option in the Data control group or your default trace file. |
||
Enter the name of the DAL script you want the system to use. Store this script in the DefLib directory or in MASTER.LBY if you are using Library Manager. |
||
Enter the name of the DAL library file that contains your section trigger scripts (DAL triggers). The default is the name stored in the FormsetTriggers option in the MasterResource control group. If this option is omitted, the system looks for SetRcpTb. |
© Copyright 2017, Oracle and/or its affiliates. All rights reserved. Legal Notices