changeda - Change Data Area Deployment

Listed below are the syntax options available for changeda. When you use changeda, you must specify one and only one of the following: -b, -c, -d, -f, -i, -m, -p, -s, -I, or --listbusclasspatterns.

changeda -b [attribute=value] [OPTIONS] dataarea [businessclass_pattern ...]

changeda --listbusclasspatterns

changeda -c [attribute=value] [OPTIONS] dataarea file [all | column ...]

changeda -d [attribute=value] [OPTIONS] dataarea

changeda -f [attribute=value] [OPTIONS] dataarea [files...]

changeda -i [attribute=value] [OPTIONS] dataarea file [all |index ...]

changeda -I [OPTIONS] datarea directivefile

changeda -m [attribute=value] [OPTIONS] dataarea [modules ...]

changeda -p [attribute=value] [OPTIONS] dataarea [filename_pattern ...]

changeda -s [attribute=value] [OPTIONS] dataarea space ...

Data area attributes in the data area deployment file ($LACFGDIR/dict/dataarea.xml) control many aspects of the data area configuration.

Note: Before the April 2021 Landmark update, the dataarea.xml file was located in $LASRCDIR/dict. The April 2021 update and later updates will attempt to move the dataarea.xml file to $LACFGDIR/dict. If the file cannot be moved, the system will continue to use the dataarea.xml file in $LASRCDIR/dict.

The deployment file specifies attributes such as:

default values for each data area
the modules included in the data area
the database space assignment for the data area or its files

Note:

The data area deployment file is used by the system and should only be modified using the provided changeda utility.

The data area attributes you can set for different components of the data area using the changeda utility are described in more detail in Infor Landmark Technology Data Access Guide using <Database>. You can also delete an attribute by specifying the name of the attribute and then providing no value, for example, lobsize=


Program option or attribute	Value
`-b` or `--busclasspattern`	Change attribute values for all files in a data area that contain a business class pattern.
`-c` or `--column`	Change attribute values for all or specified columns in a file.
`-d` or `--default`	Change default data area attribute values for the data area.
`-f` or `--file`	Change attribute values for specified files within the data area.
`-i` or `--index`	Change attribute values for specified indexes within the data area.
`-I` or `--inputfile`	Read directives from an input file.
`-m` or `--module`	Change attribute values for specified modules within the data area.
`-p` or `--filenamepattern`	Change attribute values for all files in a data area whose names match a regular expression.
`-s` or `--space`	Update space attributes.
`-r` or `--remove`	Remove rather than update the module attribute.
`--uselpl`	Access metadata from LPL files on disk instead of dictionary.
`dataarea`	The data area to change module attributes for.
`modules`	One or more modules to change attributes for. If a module is not specified, the value is assigned or changed for all modules in the data area.
`files`	One or more files to change attributes for.
`--listbusclasspatterns`	Lists the available business class pattern names for use with the `-b` (`--busclasspattern`) option.
`businessclass-pattern`	The pattern that determines which files' attributes are modified.
`filename-pattern`	A regular expression that matches one or more LPL file names.
`attribute` (default)	`space` (database space name), `charset` (character set name), `splitlobstorage` (`yes` or `no`), `pmyincludedeleteflag` (`yes` or `no`), `varchar` (`yes` or `no`), or `utf8lobs` (`yes` or `no`). For `varchar`, enter `yes` to specify that the database driver should use a var char rather than a char type for the Lawson Alpha, AlphaUpper, and AlphaRight data types. The default is `no`. See below for more information about `splitlobstorage` and `pmyincludedeleteflag`. Note: The space must already exist in the data area if you want to assign it as the default.
`attribute` (file)	`space` (database space name), `varchar` (`yes` or `no`), `ddloptions` (a valid DDL statement), `splitlobstorage` (`yes` or `no`), or `pmyincludedeleteflag` (`yes` or `no`), or `utf8lobs` (`yes` or `no`). For `varchar`, enter `yes` to specify that the database driver should use a var char rather than a char type for the Lawson Alpha, AlphaUpper, and AlphaRight data types. The default is `no`. See below for more information about `ddloptions`, `splitlobstorage`, and `pmyincludedeleteflag`.
`attribute` (index)	`indexed` (`yes` or `no`) or `ddloptions` (a valid DDL statement). See below for more information about `ddloptions`.
`attribute` (module)	`space` (database space name), `splitlobstorage` (`yes` or `no`), `pmyincludedeleteflag` (`yes` or `no`), or `utf8lobs` (`yes` or `no`). For `varchar`, enter `yes` to specify that the database driver should use a var char rather than a char type for the Lawson Alpha, AlphaUpper, and AlphaRight data types. The default is `no`. See below for more information about `splitlobstorage` and `pmyincludedeleteflag`.
`attribute` (space)	Space attributes are: `dbtype` (`empty`, `msf2008`, `msf2016`, `oracle`, or `proxy`) `dbname` (database name - same as section name in db.cfg. If you provide no value, the value defaults from `dbtype`.) `tablespace` (the name of a tablespace - Oracle) `indexspace` (the name of the tablespace for an index - Oracle) `lobspace` (name of a tablespace for LOB objects - Oracle) `schema` (schema name) `isview` (`yes` or `no`) - indicates a space managed by a different system `sqltype` (`s3classic`, `landmark`, or `foreign`) `charset` (charset name) `supplementalindexes` (`yes` or `no`) `copy` (space name) - to copy the attributes from another space and apply them to the space you are modifying with `changeda`. `oracle_lobcache` (`yes`, `no`, or `audit`) - On Oracle, a value of `yes` sets the LOB storage to CACHE, a value of `no` sets the LOB storage to NOCACHE, and a value of `audit` will use CACHE for AuditLog and EffectiveDatedLog only. New data areas are created with a value of `audit` so that audit logs are cached by default but all other LOBs are not cached. Existing data areas will maintain their current behavior where LOBs are not cached. `oracle_lobcompression` (`no`, `low`, `medium`, or `high`) - On Oracle, the level of compression to use when storing LOB files. `readonly` (`yes` or `no`) - to designate a space as read-only. You can only set this attribute to `yes` if the `isview` attribute is set to `yes`. See below for more information about `dbtype`, `sqltype`, and `ddloptions`.
`attribute` (column)	`ddloptions` (a valid DDL statement) See below for more information about `ddloptions`.
`-v displayoptions`	`errorlevel`, `tracelevel`, and `verbose` specified in any order, where: errorlevel = {n}none \| {f}atal \| {e}rror \| {w}arning (warning is the default) tracelevel = 0:6 where 0 is no message and 6 is everything verbose = whether to display exception stacktrace

Detailed Descriptions of Selected Attributes


Attribute	Description
`ddloptions`	The `ddloptions` attribute enables you to include a string with valid DDL statements. This replaces the functionality formerly provided by LAW_DBA_TABLES.
`splitlobstorage`	For updates to the default, file, and module attributes, you can set the `splitlobstorage` attribute. If you set this to `true`, LOBs will be placed in separate tables and these tables will not be included in a database reorganization unless necessary. For a new installation, the default value of this attribute is `true`. For systems being updated from pre-10.0.0.2 Landmark, you must run `changeda` to set the value to `true`.
`pmyincludedeleteflag`	For updates to the default, file, and module attributes, you can set the `pmyincludedeleteflag` attribute. If you set this to `true`, the system more efficiently processes searches against primary indexes that have deleted records. For a new installation, the default value of this attribute is `true`. For systems being updated from pre-10.0.0.2 Landmark, you must run `changeda` to set the value to `true`.
`dbtype`	For defining a space, Use `msf2008` if the database is MS SQL 2012 or MS SQL 2014.
`sqltype`	Use `sqltype` to indicate the field naming convention system the space is for: `s3classic` Generated SQL is compatible with Infor Lawson System Foundation naming standards. `landmark` Generated SQL maps SQL names in upper or lower case, as appropriate for the database. `foreign` Generated SQL uses the name exactly as specified in the LPL business class definition.