USYS$UD6_PARAMS Settings Reference

OptionPossible
values
Description
NOKEYCHECK ENABLEDISABLE*Do not check for duplicate primary keys on write. This option should be used only when importing a repository.

Note: The UD6 driver only ever checks the PRIMARY key (key number 1) for uniqueness, not other ‘candidate’ keys.


NOEMPTYTRIGENABLE*,
DISABLE
Do not write empty triggers. Requires triggertag enable (default). This is a useful option when there will be a need to compare/version control repositories from multiple versions of uniface (where additional triggers may have been added in later versions).

This setting is used by default in UD6 2.1.


NOCOMPSTAMPENABLE,
DISABLE*
Do not write the COMPSTAMP field. This is particularly useful when loading a repository for the first time into version control. You may wish to load several repositories (production, test, development), where some forms will only vary in compilation time. This option should not be used in a production environment since it has high overheads.

NOUVERSENABLE,
DISABLE*
Do not write the UVERS field. This is particularly useful when loading a repository for the first time which was once stored using UVCS. You may wish to load several repositories (production, test, development), where some forms will only vary in UVERS stamp. This option should not be used in a production environment since it has high overheads.

FORCEDATEdatetime
DISABLE*
FILE
E.g.: 2001-03-02T09:00:00. Writes the TIMESTAMP field of the UFORM with this value. This is particularly useful when loading a repository for the first time into version control. You may wish to load several repositories (production, test, development), where some forms will only vary in last modified date/time. This option should not be used in a production environment since it has high overheads.

The FILE setting can be used to set the TIMESTAMP field of UFORM to the value of the last modification timestamp on the file.


NOTIMESTAMPENABLE,
DISABLE*
Do not write the TIMESTAMP field of the USMENU, USITEM, UCRELSH, and USOURCE. Also do not write the U_INDB field of UXGROUP for HEADER/TRAILER/BREAK frames. This is particularly useful when loading a repository for the first time into version control. You may wish to load several repositories (production, test, development), where some forms will only vary in modified time. This option should not be used in a production environment since it has high overheads.

OPTLOCKINGENABLE,
DISABLE*
If set use optimistic locking as default.

NUMFORCEN Force default numeric size to N.

If a number is defined as Data Type:N / Interface:N, UD6 uses a default size of 20 characters (ie, the same as interface:N20), whereas the Uniface Oracle driver uses a size of 4. For compatibility this can be set by the user.

Valid values are from 1 to 32.


BOOLFORCEN Force booleans to format N.

1:ASCII Boolean (0|1)
2:ASCII Boolean (F|T)
3:ASCII Boolean (N|Y)
4:Binary Boolean (0|1)
5:Binary Boolean (0|-1)


DATEFORCEN Force dates to format N.

1:ASCII Date dd-mmm-yyyy
2:ASCII Date yyyymmdd
3:ASCII Date ddmmyyyy
4:ASCII Date yymmdd
5:ASCII Date ddmmyy
6:Binary Date yymd
7:Binary Date dmyy
8:Binary Date ymd
9:Binary Date dmy
10:Binary Date yymmdd
11:Binary Date ddmmyy
12:ASCII Date mm/dd/yyyy
13:ASCII Date yyyy-mm-dd


BEATFORCEN Force time to format N.

1:ASCII Time hh:nn:ss
2:ASCII Time hhnnss
4:Time hh:nn:ss
5:Time hh:nn:ss.s
6:Time hh:nn:ss.ss


TIMEFORCEN Force datetime to format N.

1:SYBASE linear four-byte Date and four-byte Time
2:RMS linear Datetime
3:ASCII Date ddmmyyyy Time hh:nn:ss
4:ASCII Date ddmmyyyy Time hhnnss
5:Ingres Date dd-mmm-yyyy Time hh:nn:ss
6:ORACLE internal Datetime format
7:SYBASE ASCII Date mm/dd/yyyy hh:nn:ss.tt
8:ASCII Datetime yyyymmddhhnnss (like 2)
9:SYBASE binary Small Datetime
10:ASCII Datetime yyyy-mm-dd hh:nn:ss
11:Rdb date yyyy-mm-dd Time hh:nn:ss
13:Rdb date yyyy-mm-dd Time hh:nn:ss.ss


FIXCHARENABLE,
DISABLE*
Return the size of fixed length character strings as fixed (to maximum size) to Uniface.

IGNORELINESstringIgnore lines at the start of the XML file that begin with this string. This is not implemented in UD6 but can be used for documentation purposes, in UD6 all lines before <?xml version="1.0"?> are ignored, e.g.: comment ; CONT_ID.

OPTION PACKdllname,
DISABLE*
Setting this option indicates that you are licensed for the March Hare Form ToolKit, and have a copy of the mhgfp140.dll.

With this option set in conjunction with the ofields option and file, the UD6/CMtool passes the contents of the FORMPIC of UFORM to the Form ToolKit for translation to and from XML.

This produces a human-readable form paint tableau.


UPGRADEFTIENABLE,
DISABLE*
Set this option if you are now using the OPTION PACK setting but when the sources were loaded it was not set.

Component source code will be updated on write. This setting incurs a performance penalty, so should only be used when required.


GOLDENABLE*,
DISABLE
Setting this option forces the UD6/CMtool driver to convert the TRX representation of GOLD characters to the XML equivalent (this also effects the correct translation of tilde). This option is enabled by default, but may be disabled for compatibility with UD6 Version 1.00.00, or to improve performance.

This setting will only be used if the SINGLE INTERPRET option is switched on (on by default). If the setting NOTRX is used then the setting MMF BINARY must also be used to enable GOLD conversion.


GOLDV2ENABLE,
DISABLE*
enable compatibility with earlier version of the gold interpretation.

CONVERT CSVENABLE,
DISABLE*
Setting this option forces the UD6/CMtool driver to convert the input file from delimited text to XML. It is the responsibility of the user to ensure that an appropriate application model is defined. To correctly handle LONG fields the LONG field should be a) the last field in the comma separated file, and b) the TABLE in Uniface should be defined with an interface definition of U.

In the DEMO driver this option is limited to processing only 10 rows.

When used in this mode, the UD6/CMtool driver reads delimited text files (e.g.: comma separated format) and writes XML files.

For this to function, you need to name the file TABLENAME.XML, and alter the OVERFLOWS file (which is in the Uniface bin directory by default) so that it contains a line for the (overflow) table. Eg:



            OCSVDATA:LONG_FIELD+

See the section How to use the driver to load CSV files with LONG fields for more information.


CONVERT SEPSPACE*,
a single
character
or an escaped
character
This option specifies the separator character used when loading CSV files (see the CONVERT CSV option). By default this uses a comma.
\aalert (bell) character
\\backslash
\bbackspace
\?Question mark
\fformfeed
\’single quote
\nnewline
\"double quote
\rcarriage return
\ooooctal number
\thorizontal tab
\xhhhexadecimal number
\vvertical tab

See the section How to use the driver to load CSV files with LONG fields for more information.


NOTRXENABLE,
DISABLE*
This provides rudimentary NLS support. Please see the section How to use the driver to load CSV files with LONG fields and UD6/CMtool NLS support for more information.

Note: This setting should be used in conjunction with the USYS$UD6_PARAMS=mmf binary, setting if used to store the Uniface repository.

NOTE: You cannot use UD6/CMtool to store the UGLYPH or UCSDIA entities when ‘notrx’ is specified. This may cause unstable behavior in the driver.

Since GLYPHS usually remain fairly stable in the life cycle of a software development, March Hare recommend storing these using the DB3 driver, which will generate 2 files plus indexes for the entire table. These files can then be controlled using your CM or VM tool.


MMF BINARYFONT font,
ENCODING string,
DISABLE*
This enables bold, gold and frame conversion when NOTRX is enabled.

If this setting is not used when NOTRX is enabled, then Bold, Gold and Frame characters will not be converted to XML. See also GOLD and BOLD settings.

The FONT setting sets the default Uniface font (Font 1=51). If the encoding is ISO-8859-1, then characters 160-254 are set to Uniface font 1, regardless of the setting for FONT. The FONT information for individual characters can be specified in the nlsn file (where n is the number of the codepage, usually 0).

The ENCODING setting sets the default encoding for the XML and XSL files, and is used when setting the default FONT, see above for more information.


UNICODENOENCThis sets the driver to write the XML files as Unicode files (Windows only). The NOENC setting should be used if you want to be able to view the files with IE5.

MMF FILESnumberSet the maximum number of files to allow "open" and "cached" at any one time.
Default size of mmf files.
Windows255
Non-WindowsFOPEN_MAX

This setting should be the same as the MAXFILES setting in the [SETTINGS] section of the assignment file.

NOTE 1: This may not be set to a value larger that what is supported by your operating environment. Details of how you can determine the correct value for your operating environment are in the UD6 Installation Guide.

NOTE 2: This feature increases the speed of similar information being frequently accessed (eg: Model definitions, templates etc), by maintaining it in memory. The larger the value for mmf files the more files that will be kept open and in memory. UD6 assumes that there will be enough available memory to cache the number of files you request. If there is insufficient memory UD6 will abort and the IDF may crash. The amount of memory per file varies, but is typically around 24K per mmf file on Windows NT 4..


MMF KEEP-READsecondsSet the maximum time to keep an inactive file open (for read). Default is 360 seconds (5 minutes).

MMF KEEP-WRITEsecondsSet the maximum time to keep an inactive file open (for write). Default is 60 seconds (1 minute).

NODENYENABLE,
DIALOG,
FILENAME filename,
DISABLE*
This allows you to compile forms that are read-only, and ignore other write errors.

The NODENY setting can either specify that ALL write failures are ignored, or only on certain tables (as specified in the file declared by FILENAME filename), or the user is given a choice at run-time (DIALOG).

Note: The DIALOG setting is only available on Windows, and when Polyserver is NOT being used. Since March Hare recommend the use of Polyserver with UD6, there are very few installations where the Dialog setting is useful.

This setting is most often used because during the compilation of a form, Uniface writes to it the last compiled date/time, and also updates the descriptor information. The NODENY option tells UD6 to not report Access Denied messages on Update/Delete/Write for joined files.

Note: Since the descriptor information is stored in the form.xml file, the resulting .frm file may not be able to execute due to ‘old’ descriptor information.

To avoid this store the descriptors either in a different data format (eg: DB3) or in a different XML file (specified using the joins configuration file). e.g (assignment file).:

[ENTITIES]

USIMPL.DICT   $DB3:USIMPL.*

USOPER.DICT   $DB3:USOPER.*

USISPARM.DICT $DB3:USISPARM.*

USPARM.DICT   $DB3:USPARM.*

USIOPER.DICT  $DB3:USIOPER.*

USIPARM.DICT  $DB3:USIPARM.*

USSPEC.*      $DB3:USSPEC.*

The next most common use is to ignore spurious write/update requests from the IDF on certain tables, when you are just browsing, but the IDF has inadvertently modified the form causing a write to occur.

The FILENAME filename may be any you wish, and is located in the current working directory unless otherwise specified in the assignment file. E.g.:

USYS$UD6_PARAMS=nodeny dialog filename c:\nodenys.txt

The format of the NODENYS file is:

; Write failures to these entities are ignored

:UFORM:

:UCTABLE:

:UCSCH:

BUFFERsizeBuffer Input operations with a buffer size bytes. This value is set to 8100 bytes by default, and for optimal speed, should be set to the average record length.

FORCEDATEdatetimeForces all fields of data type E to be given this value. Format of the datetime should be:

01-Feb-2001T12:55:15.


NOUVERSENABLE,
DISABLE*
Remove the field <uvers> before write..

NOCOMPSTAMPENABLE,
DISABLE*
Remove the field <ucompstamp> before write..

STEP SIZEsizeThe CMtool driver supports a stepped hitlist, and uses a value of 10 by default.

SILENT To disable the version message when the CMtool driver is loaded. This cannot be disabled in the demo version.

CONFIGdirectoryThe CMtool driver must be told which directory to look in for the configuration files: overflows, joins, ofields, nls0 and xlink. The default is the current working directory (on Unix) or the Uniface bin directory (on Windows).

CSSDIRdirectoryThe CMtool driver can optionally create CSS & XSL files (stylesheets) to assist in the display of the XML files when used in conjunction with Internet Exporer, and also XML Schema's to assist in the automated use of the XML files. By default these files are created in the same irectory as the XML files. The CSSDIR setting can be optionally used to set a single directory to contain all these "support:" files.

TEMPdirectoryThe CMtool driver can be told which directory to create directory listings and other temporary files. Under unix the default is /tmp and under Windows the default is either the directory specified in the environment variable TMP or TEMP, the Windows directory or the current directory.

If a temporary file cannot be created in the temp directory for any reason, the driver may unexpectedly fail (e.g.: out of disk space).


RELOAD LIST This command is only intended to be used from the SQL workbench or the sql "reload list","$ud6" proc statement.

This command forces the driver to reload the list of currently renamed files (useful for when a configuration manager is being used to specify that a file is ‘checked out’).


FONTMAP This command is only intended to be used from the SQL workbench or the sql "fontmap","$ud6" proc statement.

This command forces the driver to reload the default font mapping from the nls0 configuration file.


CLEANMMF This command is only intended to be used from the SQL workbench or the sql "cleanmmf","$ud6" proc statement.

This command forces the driver to release all cached open file handles. SCM tools like PVCS require that a file not be open, even for READ-ONLY access before they can be checked back in. Use this command from the SQL workbench with the data path set to UD6 to release these open files.

If you have just made changes to a component, and want the file ‘unlocked’, the correct sequence should be:

1) close current component
2) open another component
3) open SQL workbench and set path to UD6 and enter the SQL/DML command CLEANMMF and press the 'SQL' button.

The CLEANMMF AUTO or CLEANMMF HARD AUTO option may be used in the ASN file to instruct the driver to close files as soon as possible. This option may negatively impact performance.


CLEANMMF HARD See CLEANMMF. This technique tries "harder" to close files. This should be used with caution.

LISTDIRdirectory/filenameThe CMtool driver must be told which directory / filename to look in for the list of currently ‘checked out’ files. See RELOAD LIST for more information.

This allows each developer or workgroup to have their own ‘list’. Files checked out by other developers or workgroups will not be seen, so therefore the ‘reference copy’ of those files will be used.

The default directory/filename is ‘inuse’ in the current working directory.


SHADOW-FOLDERdirectoryIf the source code control tool you are using does not support triggers for chechout/checkin actions (e.g.: Visual Source Safe), the functionality of the INUSE file can be replaced with the shadow-folder and sandpit settings.

The shadow-folder setting specifies which directory is the ‘root’ for the read-only copy of the files (from the workstation). If for example, all workstations mount the NT Share on v:\ then the setting would be :

            shadow-folder v:\

This setting must agree with the directory names specified in the JOINS file, e.g.:

    UFORM:ULABEL:ULABEL::v:\components\*

    UCTABLE:U_VLAB,U_TLAB:U_VLAB,U_TLAB::v:\tables\*

    UCGROUP:U_GLAB,U_VLAB:U_GLAB,U_VLAB::v:\sub-types\*


SANDPITdirectoryIf the source code control tool you are using does not support triggers for chechout/checkin actions (e.g.: Visual Source Safe), the functionality of the INUSE file can be replaced with the shadow-folder and sandpit settings.

The sandpit setting specifies which directory is the ‘working directory’ for the checkout out copy of the files (on the workstation). For this reason each developer would typically have their own personal ASN file set to their own sandpit. If the developer has several sandpits, and needs to switch between them, they can use the ‘sandpit’ command from the SQL workbench (set Path to UD6).

            sandpit c:\sandpit

Within this directory, the checked out files must still exist in the same ‘tree’, e.g.:

    C:\sandpit\components\basu0011.xml

    C:\sandpit\tables\csaaa-customer.xml

    C:\sandpit\sub-types\customer-csaaa-customer.xml

If the source code control tool you are using supports the use of triggers, using the triggers to activate the add2list and del2list utilities to maintain the INUSE file will provide significantly greater performance than use of the SANDPIT setting.


PERFORMANCE0-255*The IDF version 7.2.04 has various performance limitations due non-optimal use of the Uniface repository relationships. This can severely impact the performance of the driver.

The performance parameter is a bitwise value, where each bit sets a performance optimisation ON. The value zero (0) turns all performance optimisation off. See performance parameter for more information.

If there are compatibility problems with later releases of the IDF it is advisable to turn this setting off by specifying ‘performance 0’ in the assignment file.

The setting ‘performance’ is the same as specifying ‘performance 127’ which is also the default.

Once you have created your XML files by loading your repository into UD6 you should not modify this setting, as most of the values effect the names of tables via the joins mechanism.


REFRESHsecondsSpecifies the minimum default refresh interval between directory "listings". Default is 10 seconds.

SINGLEENABLE,
INTERPRET*,
DISABLE
Write and read overflow segments and the ‘main’ segment in one action.

With the INTERPRET option the TRX encoding is converted to readable format.

This is a functional and performance enhancement.

Entity closing tags must finish in an end of line character, eg: </XMLuform>

not: </XMLuform><XMLuform><label>PM0001</label>


OFIELDSENABLE*,
DISABLE
Setting this option forces the UD6/CMtool driver to convert the TRX codes in the variable length portion of the record to XML comments based on the information in the ofields file.

March Hare recommend this option be disabled if you experience performance limitations. However if you are satisfied with the performance of your system (e.g.: using polyserver), then it may be used.

See the Installation guide section on the Ofields file.


XMLSCHEMAIE5,
W3C,
DISABLE*
Setting this option forces the UD6/CMtool driver to generate XML Schema files for each table, or for a collection of joined tables. Note: This significantly decreases the performance of the driver, so if you are using UD6 to store your repository, March Hare recommend that you use this setting only when initially importing your source code.

NOTE: It is not possible to change this setting from IE5 to W3C. If your Schema.XML files were generated using one setting, do not change the setting to the alternative. This can cause unreliable behaviour and possibly crashes in the driver. Delete the existing Schema.XML files before changing this setting from IE5 to W3C or W3C to IE5 (IE5 schemas have the tag <Schema ...> wheras W3C schemas have the tag <schema ...>).


XSLIE5*,
W3C
For a web browser to display the contents of an XML file, it requires an additional file (a stylesheet) to explain the formatting. These files are produced automatically by the driver for all entities listed in the ofields configuration file.

Specify IE5, to produce an XSL file compatible Microsoft Internet Explorer 5 or greater. Use W3C to produce an XSLT file compatible with a browser that supports W3C standard XSLT files.

The W3C setting gives preliminary support for the W3C XSLT standard.


BOLDENABLE*,
DISABLE
Setting this option forces the UD6/CMtool driver to convert the TRX codes for BOLD, UNDERLINE, ITALIC, BOLD-UNDERLINE and BOLD-ITALIC, to the more readable <html:b>string</html:b> etc. This option is enabled by default, but may be disabled for compatibility with UD6 Version 1.01.00, or to improve performance.

This setting will only be used if the SINGLE INTERPRET option is switched on (on by default). If the setting NOTRX is used then the setting MMF BINARY must also be used to enable BOLD conversion.


BOLDV1ENABLE,
DISABLE*
enable compatibility with earlier version of the bold/style interpretation.

BOLDV2ENABLE,
DISABLE*
Enable compatibility with earlier version of the bold/style interpretation. This version is compatible with UD6 1.02.44 and earlier.

TRIGGERTAGENABLE*,
DISABLE
Only valid if a ofields file is present. Setting this option forces the UD6/CMtool driver to convert the TRX codes in the variable length portion of the record to XML trigger tags based on the information in the ofields file.

March Hare recommend this option be disabled if you experience performance limitations. However if you are satisfied with the performance of your system (e.g.: using polyserver), then it may be used.

See the Installation guide section on the Ofields file.

The format of the tag is

<trigger name="name">text</trigger>


CVSWEBversionIf you are using the source code control tool CVS with CVSWEB, then this setting can be used to force references to external XSL, XDR, GIF and XML files to contain a ‘version’ and load directly from CVSWEB.

NOTE: When you try and view the files with a web browser NOT from within CVSWEB, the load of these external files will fail. The opposite behavior is true if this is not set.


NEWSUBTYPESENABLE*,
DISABLE
Use the 1.03 method for storing sub-types in the same directory as tables and ULANA records.

For backward compatibility with UD6 1.02 and earlier use:

USYS$UD6_PARAMS=newsubtypes disable

For backward compatibility with UD6 1.03 Beta 2 use:

USYS$UD6_PARAMS=newsubtypesb2 enable


MALLOPT MXFASTsizeAvailable on HP-UX and AIX only.

Improves efficiency of allocating small amounts of memory. The HPUX memory allocation algorithm allocates all blocks below the size of size in large groups, then doles them out very quickly. The default value for maxfast is zero.

Eg: USYS$UD6_PARAMS=mallopt mxfast 64 nlblks 200

WARNING: if the combination of NLBLKS and MXFAST is too high, the UD6 driver may fail with -1016 (cannot create buffer this size) errors.


MALLOPT NLBLKSsizeAvailable on HP-UX and AIX only.

Improves efficiency of allocating small amounts of memory. The HPUX memory allocation algorithm allocates all blocks below the size of MALLOPT MXFAST in large groups each containing size blocks. Numlblks must be greater than 1. The default value for numlblks is 100.

Eg: USYS$UD6_PARAMS=mallopt mxfast 64 nlblks 200

WARNING: if the combination of NLBLKS and MXFAST is too high, the UD6 driver may fail with -1016 (cannot create buffer this size) errors.


PLOCKENABLE,
DISABLE*
Available on HP-UX and AIX only.

Indicates that the HPUX operating system should not swap out the DATA area of the UD6 driver. Requires that the user running IDF or Polyserver has the MLOCK privelege.

Eg: USYS$UD6_PARAMS=plock


WORKING SETMIN nnn MAX nnnAvailable on Windows NT/2000 only.

Specifies a minimum and maximum working set size for the process.

MIN The virtual memory manager attempts to keep at least this much memory resident in the process whenever the process is active.

MAX virtual memory manager attempts to keep no more than this much memory resident in the process whenever the process is active and memory is in short supply.

Eg: USYS$UD6_PARAMS=working set min 16384 max 32768

NOTE: both minimum and maximum must be set, the process must had PROCESS_SET_QUOTA access rights and SE_INC_BASE_PRIORITY_NAME privilege (Administrators and Power Users groups generally have this privilege).

The current working set minimum and maximum are displayed in the message frame if the listoptions setting is used.


TABLESWITHSPACEStablename[;tablenale...]By default UD6 does not support tables with spaces in the primary key. Only the UGLYPH table in the Uniface repository allows spaces in the primary key. Support for UGLYPH is included in UD6.

If you wish to store the contents of another entity in UD6 (eg: a user defined menu system), and those tables allow spaces in the primary key name - you must specify the table names with this setting.

Eg: USYS$UD6_PARAMS=tableswithspaces ;menu_choice;menu_set;, listoptions, etc etc


NOCR2LFENABLE, DISABLEThis setting prevents UD6 from performing Carriage Return (CR) to Line Feed (LF) translation on "Character" type fields (such as UDESCR). When UD6 is used with Uniface Six or Seven this is disabled, with Uniface eight this is enabled.

EXCLUSIVEWRENABLE, DISABLE*This setting instructs UD6 to attempt to lock files to prevent two users making changes to the same file at the same time.

Version Control should be used to prevent more than one developer gaining write access to the same file at the same time - however the EXCLUSIVEWR option is provided for situations where this is not practical.

USYS$UD6_PARAMS=exclusivewr, cleanmmf hard auto, optlocking disable

On Microsoft Windows platforms the file is exclusively locked. Other users will not be able to read or write the file while it is locked. If another user or process attempts to access a locked file and their copy of UD6 has cached the contents of the file and the file has not yet changed then that user may still be able to read the file.

On Unix platofrms the lock is a write-only lock and other users may still read the file.


JAPANFONTENABLE*, DISABLEThis setting instructs UD6 correctly handle large font numbers. This setting should only be disabled to provide backwards compatibility with older releases of UD6.

NOLOCKENABLE, DISABLEDuring a Select or Fetch ignore failed lock requests on the UCTABLE records. Uniface 7.2.06 does a read/lock on UCTABLE during a browse, and this setting allows the browse to continue.

Default is ENABLE for Uniface Six and Seven and DISABLE for Uniface Eight.


TOUCHfilenameWindows ONLY.

Set the last modified time of the filename to the current time.


HYPHENcharacter,
COMMA
Sets the character used to delimit key fields in a filename to character. Must commonly used to set the character to COMMA for CM Synergy.

XDRNAMEfilenameSets the name of the XSL or XSLT file that is used to format the XML Schema. By default this is "xdr-schema".

ASNFILEfilenameSets the name of the ASN file which defines where the *.frm, *.svc, *.rpt and other compiled components are stored. The Windows version of UD6 can determine this name for itself, however when using UD6 with Polyserver or Userver on Unix then this should be set.

MAKEFILESENABLE,
DISABLE,
CHECKOUT,
WAIT,
NOWAIT,
FILENAME filename
This is enabled by default in UD6 2.1 when the Option Pack is used (ENABLE WAIT).

This setting enables the automatic generation of a Makefile. A Makefile is a standard file that specifies the relationships of various "source code" files to an object code (compiled) file. Eg: the compiled form TEST.frm is made up of the source TEXT.xml and tables.dir/CUSTOMER.xml. This allows a tool such as MAKE to automatically re-compile forms when the source (entities etc) changes.

The WAIT setting (default) causes UD6 to keep trying to gain write access to the Makefile (wait until write access is permitted). If NOWAIT is specified then changes will not be written to the Makefile and may result in incomplete build management.

FILENAME should be the last setting specified. This is the full name and PATH of the Makefile. The default in Windows is makefile.mak and Unix is Makefile. The file is created in the current directory by default.

The CHECKOUT command is not currently supported but will enable a future version of UD6 to automatically include a "checkout" line before the compile line in the Makefile.


FASTERUNOTALL
THRESHOLD count
MEMSTEP size
Improves the performance of reading and writing large triggers (entities or components) when there are a large number of gold! or gold; characters. It is usually best to use the memory step size and threshold defaults.

Note * = default.

If the "Possible values" column is blank, this indicates that the option is disabled by default and enabled if the option is listed, eg: USYS$SOL_PARAMS listoptions enables this feature.

Related articles:

$Revision: 1.22 $ $Date: 2014/07/18 01:55:16 $[go to top]