Meta-schema Manager error messages

A list of Meta-schema Manager error messages. For messages that are not self-explanatory, additional information is provided.

Table 1. Meta-schema Manager Error Messages
Number Description
GS-11000

Unexpected error.

An unexpected error occurred.

GS-11001

Error while reading file schema: description.

An error occurred while reading the file file.

The details about the error can be found in the description part of the message.

GS-11002

Cannot find codec.

The appropriate codec cannot be found to read a file.

GS-11003

Cannot find codec for encoding encoding.

The appropriate codec for encoding encoding cannot be found.

GS-11004

Error while creating new schema document.

The Meta-schema Manager failed to create a new document.

GS-11005

Dynamic property property not found for node node.

A dynamic property used in the meta-schema is not found in the current template. Check the appropriate template is selected before opening the meta-schema.

Failed to read dynamic property.

An error occurred while reading dynamic properties. The meta-schema file might be corrupted.

GS-11050

Schema file defined in GSTSCHEMANAMES cannot be found in FGLDBPATH.

The file cannot be found.

GS-11051

Failed to load file file.

An error occurred while loading the file file .

GS-11052

Failed to open file file for writing.

Check the file permissions and those of its owner directory.

GS-11053

Failed to open file file for reading.

Check the file permissions and those of its owner directory.

GS-11054

File already exists.

Check the filename and directory.

GS-11100

Failed to locate node.

The specified database object cannot be found in the schema.

GS-11101

Unexpected schema.

An unexpected schema object has been found in the 4db or 4dbx document. The schema file is corrupted and cannot be read.

GS-11102

Missing schema name.

The schema name cannot be found. This property is required and the loading of the schema file cannot continue.

GS-11103

Missing schema property property.

This property is required, but it cannot be found. The loading of the schema file cannot continue.

GS-11104 Invalid schema property property.

The schema property property has an invalid value. The loading of the schema file cannot continue.

GS-11105

Schema contains no table or column.

No valid tables have been found in the schema. A valid table is a table in which is not flagged has been removed and which contains at least one column in which is not flagged has been removed.

GS-11106

Empty schema file.

The schema document contains no information.

GS-11107

File is saved using a newer version of Genero Studio. Please upgrade Genero Studio.

The schema document has been saved with a newer version of Genero Studio. You will need to upgrade Genero Studio to be able to open it.
GS-11108

Schema name is not lowercase, its use in 4GL source will generate errors.

The schema name contains uppercase characters. Using it in Genero programs might generate compilation errors. Use lowercase for the Schema name.

GS-11109

The usage of both CHAR/VARCHAR and NCHAR/NVARCHAR columns is not supported by all databases.

The schema contains columns with mutually exclusive types. For instance it contains both CHAR / VARCHAR and NCHAR / NVARCHAR columns.

GS-11110

Schema name is invalid, its use in BDL source will generate errors.

The schema name contains characters not supported by the Genero language.

GS-11111

Unexpected table.

An unexpected table object has been found in the 4db or 4dbx document. The schema file is corrupted and cannot be read.

GS-11112

Missing table name.

The table name cannot be found. This property is required and the loading of the schema file cannot continue.

GS-11113

Missing table property property.

The table property property is required but it cannot be found. The loading of the schema file cannot continue.

GS-11114

Invalid table property property.

The table property property has an invalid value. The loading of the schema file cannot continue.

GS-11115

Schema already contains a table table.

The table has already been found in the 4db or 4dbx document. The document cannot contain two tables with the same name.

GS-11116

Table table is not found. Creating temporary table.

The table cannot be found, and it is required by another database object. A surrogate table will be created.

GS-11117

Table contains no columns.

The table does not contain any columns.

GS-11121

Unexpected column.

An unexpected column object has been found in the 4db or 4dbx document. The schema file is corrupted and cannot be read.

GS-11122

Missing column name.

The column name cannot be found. This property is required and the loading of the schema file cannot continue.

GS-11123

Missing column property property.

The column property property is required but it cannot be found. The loading of the schema file cannot continue.

GS-11124

Table table already contains a column column.

The column has already been found in the table. The document cannot contain two columns with the same name within the same table.

GS-11125

Constraint or index index already contains a column column.

The column has already been found in the index. The document cannot contain two columns with the same name within the same index.
GS-11126

Foreign key key already contains a column column.

The document cannot contain two columns with the same name within the same foreign key.

GS-11127

Column column is not found in table table. Creating temporary column.

The column cannot be found in the table and it is required by another database object. A surrogate column will be created.

GS-11128

Column column in table table has unsupported type: type.

The type is not supported for column within table. An unsupported type is of form encoded=(type, length), and can be generated while extracting database schemas.

GS-11129

Column column in table table has invalid type: type.

The type is invalid for column within table. An invalid type is not handled by the BDL language.

GS-11131

Unexpected foreign key.

An unexpected foreign key object has been found in the 4db or 4dbx document. The schema file is corrupted and cannot be read.

GS-11132

Missing foreign key name.

The foreign key name cannot be found. This property is required, and the loading of the schema file cannot continue.

GS-11133

Missing foreign key property property.

The foreign key property property is required, but it cannot be found. The loading of the schema file cannot continue.

GS-11134

Schema already contains a foreign key key.

The foreign key has already been found in the 4db or 4dbx document. The document cannot contain two foreign keys with the same name.

GS-11135

Schema already contains a foreign key key. Renaming user-defined foreign key to name.

The foreign key has already been found in the 4db or 4dbx document. The document cannot contain two foreign keys with the same name.

The foreign key will be renamed to name.

GS-11136

Foreign key key is not found. Creating temporary foreign key.

The foreign key key cannot be found, and it is required by another database object. A surrogate foreign key will be created.

GS-11137

Table table is not found for foreign key key.

The table the foreign key refers to cannot be found. The loading of the schema file cannot continue.

GS-11138

Column column is not found in table table for foreign key key.

The column the foreign key refers to cannot be found in the table. The loading of the schema file cannot continue.

GS-11139

Foreign key key does not contain any table column.

The foreign key does not contain any columns.

GS-11140

Foreign key key columns column and reference have different data types.

The foreign key columns have mismatching data types.
GS-11141

Unexpected constraint or index.

An unexpected index object has been found in the 4db or 4dbx document. The schema file is corrupted and cannot be read.

GS-11142

Missing constraint or index name.

The index name cannot be found. This property is required and the loading of the schema file cannot continue.

GS-11143

Missing constraint or index property property.

The index property is required but it cannot be found. The loading of the schema file cannot continue.

GS-11144

Table table already contains a constraint or index named index.

The index has already been found in the table table. The document cannot contain two indexes with the same name within the same table.

GS-11145

Table table already contains a constraint or index named index. Renaming user-defined constraint or index to name.

The index has already been found in the table. The document cannot contain two indexes with the same name within the same table. The index will be renamed to name.

GS-11146

Constraint or index index is not found. Creating temporary constraint or index.

The index cannot be found in the table and it is required by another database object. A surrogate index will be created.

GS-11147

Column column is not found in table table for constraint or index index.

The column that the index refers to cannot be found in the table. The loading of the schema file cannot continue.

GS-11148

Table table contains more than one primary key.

The table contains more than one primary index. Only one primary index can be defined for a table.

GS-11149

Constraint or index index does not contain any table column.

The index does not contain any columns.

GS-11150

Column column allows null values but is referred by primary key primary key.

A column referred in a primary key doesn't have its NOT NULL flag set.

GS-11151

Unexpected column validation attributes.

An unexpected index object has been found in the 4db or 4dbx document. The schema file is corrupted and cannot be read.

GS-11152

Missing column name for validation attributes.

The column name cannot be found. This property is required and the loading of the schema file cannot continue.

GS-11153

Column '%1' already contains validation attributes.

Column validation attributes have already been defined for the column. The loading of the schema file cannot continue.

GS-11154

Column '%1' is not found in table '%2' for column validation attributes.

Column validation attributes refer to a non-existing column. The loading of the schema file cannot continue.

GS-11161

Unexpected column video attributes.

An unexpected index object has been found in the 4db or 4dbx document. The schema file is corrupted and cannot be read.

GS-11162

Missing column name for video attributes.

The column name cannot be found. This property is required and the loading of the schema file cannot continue.

GS-11163

Column '%1' already contains video attributes.

Video attributes have already been defined for the column. The loading of the schema file cannot continue.

GS-11164

Column '%1' is not found in table '%2' for column video attributes.

Column video attributes refer to a non-existing column. The loading of the schema file cannot continue.

GS-11171

Unexpected user attributes.

An unexpected user attribute has been found in the 4db or 4dbx document. The schema file is corrupted and cannot be read.

GS-11172

Missing user attribute name.

The user attribute name is required but cannot be found. The loading of the schema file cannot continue.

GS-11173

Missing user attribute property '%1'.

The user attribute property property is required but cannot be found. The loading of the schema file cannot continue.

GS-11174

Object already contains a user attribute '%1'.

A user attribute has already been defined for the database object. The loading of the schema file cannot continue.

GS-11181

Unexpected layout data section.

An unexpected layout section has been found in the 4db or 4dbx document. The schema file is corrupted and cannot be read.

GS-11182

Missing layout data property property.

The layout property property is required but it cannot be found. The loading of the schema file cannot continue.

GS-11191

Unexpected database data section.

An unexpected data section has been found in the 4db or 4dbx document. The schema file is corrupted and cannot be read.

GS-11192

Missing database data property property.

The data property property is required but it cannot be found. The loading of the schema file cannot continue.

GS-11193

Document already contains database value for identifier.

Database data has already been found in the 4db or 4dbx document. The document cannot contain twice data for the same identifier.

GS-11194

Document contains invalid identifier identifier for database value (value: value). Database value will be ignored and removed.

The database data identifier doesn't match any database object. The associated value is ignored and will be discarded upon save.

GS-11201

Unexpected dynamic property.

An unexpected dynamic property has been found in the 4db or 4dbx document. The schema file is corrupted and cannot be read.

GS-11202

Missing dynamic property attribute attribute.

The dynamic property attribute attribute is required but it cannot be found. The loading of the schema file cannot continue.

GS-11203

Object doesn't support dynamic property property.

A dynamic property has been read for a database object but this property is not defined for this object. Check the appropriate template is selected before opening the meta-schema.

GS-11204

Object already contains a dynamic property property.

A dynamic property has been defined twice for a database object.

GS-11210

Invalid model node info version.

Model node info for type type not found.

Failed to add property property to model node info: a dynamic property with this name already exists

Failed to add property property to model node info: a static property with this name already exists

Failed to add property property to model node info: a property with this name was not found

Information about model node is invalid.

GS-11220

Name cannot be empty.

The name of a database object is empty.

GS-11221

Same name cannot be applied to more than one table.

Two tables cannot have the same name in the meta-schema.

GS-11222

Same name cannot be applied to more than one column of same table.

Two columns of the same table cannot have the same name in the meta-schema.

GS-11223

Same name cannot be applied to more than one foreign key.

Two foreign keys cannot have the same name in the meta-schema.

GS-11224

Same name cannot be applied to more than one constraint or index of same table.

Two constraints or indexes of the same table cannot have the same name in the meta-schema.

GS-11225

Table name is invalid.

A table cannot be named with the provided name.

GS-11226

Column name is invalid.

A column cannot be named with the provided name.

GS-11227

Database object name contains invalid character(s).

The name of the database object contains invalid characters.

GS-11228

The name name has been converted to other name as database object name contains invalid character(s).

The original name of the database object contains invalid characters. The database object has been renamed to a new name.

GS-11270

Unexpected extraction options.

An unexpected extraction options section has been found in the 4db or 4dbx document. The schema file is corrupted and cannot be read.

GS-11271

Unexpected extraction settings.

An unexpected extraction settings section has been found in the 4db or 4dbx document. The schema file is corrupted and cannot be read.

GS-11272

Unexpected generation options.

An unexpected generation options section has been found in the 4db or 4dbx document. The schema file is corrupted and cannot be read.

GS-11273

Unexpected generation settings.

An unexpected generation settings section has been found in the 4db or 4dbx document. The schema file is corrupted and cannot be read.

GS-11303

The database object name has been newly added in schema.

The database object has been added to the schema and is not yet found in the database. Creating a database update script will generate SQL instructions to add this object to the database.

GS-11304

The database object name has been marked as removed from schema.

The database object has been removed from the schema and can still be found in the database. Creating a database update script will generate SQL instructions to remove this object from the database.

GS-11310

Name has been modified from name to other name.

The database object has been renamed in the schema and can still be found in the database. Creating a database update script will generate SQL instructions to update this object in the database.

GS-11311

Database object name has an invalid uuid. A new one has be generated (uuid).

The internal identifier of the database object is invalid and has been replaced with a new one.

GS-11315

Column type has been changed from type to other type.

The type of the column has been changed in the schema. Creating a database update script will generate SQL instructions to update the column in the database.

GS-11316

Not null property has been changed from value to other value.

The value of the 'Not null' property of the column has been changed in the schema. Creating a database update script will generate SQL instructions to update the column in the database.

GS-11318

Column column in table table uses Informix specific type: type.

The column uses an Informix® specific data type.

GS-11319

Invalid qualifiers for column '%1' in table '%2'.

DATETIME or INTERVAL qualifiers break the qualifiers rules for the data type. See the Genero Business Development Language User Guide for further details.

GS-11320

Constraint or index type has been changed from type to other type.

The type of the constraint has been changed in the schema. Creating a database update script will generate SQL instructions to update the constraint in the database.

GS-11322

Constraint or index columns of name has been changed from columns to other columns.

The columns of the constraint have been changed in the schema. Creating a database update script will generate SQL instructions to update the constraint in the database.

GS-11323 Constraint or index name column order of name conflicts with column order of foreign key.

Indicates the order of columns in the foreign key is not the same as the one defined for the constraint or index.

GS-11325

Foreign key table has been changed from table to other table.

The table associated to the foreign key has been changed in the schema. Creating a database update script will generate SQL instructions to update the foreign key in the database.

GS-11326

Foreign key referenced table has been changed from table to other table.

The reference table associated to the foreign key has been changed in the schema. Creating a database update script will generate SQL instructions to update the foreign key in the database.

GS-11327

Foreign key columns of foreign key has been changed from columns to other columns.

The columns associated to the foreign key have been changed in the schema. Creating a database update script will generate SQL instructions to update the foreign key in the database.

GS-11328

Foreign key referenced columns of foreign key has been changed from columns to other columns.

The reference columns associated to the foreign key have been changed in the schema. Creating a database update script will generate SQL instructions to update the foreign key in the database.

GS-11329

Cascade delete property has been changed from value to other value.

The value of the 'Cascade delete' property of the foreign key has been changed in the schema. Creating a database update script will generate SQL instructions to update the foreign key in the database.

GS-11330

Foreign key name column order of column conflicts with column order of other column.

Several columns are defined in the foreign key with the same order. The order of the column is automatically updated to solve the issue.
GS-11340

Constraints or indexes constraint and other constraint are defined on same set of columns.

Both constraints are defined on the same set of columns.

GS-11341

Foreign key foreign key references columns which are not part of primary key or unique constraint.

No primary key or secondary key is defined on the columns referenced by the foreign key.

GS-11342

Constraint cannot be placed on a BYTE or TEXT column.

A unique constraint has been defined on column of type BYTE or TEXT.

GS-11343

Non-unique index index conflicts with constraint constraint.

A non-unique index has been defined on the same set of columns has a unique constraint.

GS-11360

Foreign key references an inactive table.

The table referenced by the foreign key is flagged as inactive whereas the table associated to the foreign key is active.

GS-11361

Foreign key table is inactive.

The table associated to the foreign key is flagged as inactive whereas the table referenced by the foreign key is active.

GS-11370

Name has been modified to '%1' but matches value in database.

The property of the database object has been changed in both the meta-schema and the database with the same value. The change becomes useless and can be reverted.

GS-11371

Column type has been changed to '%1' but matches value in database.

The property of the database object has been changed in both the meta-schema and the database with the same value. The change becomes useless and can be reverted.

GS-11372

Not null property has been changed to '%1' but matches value in database.

The property of the database object has been changed in both the meta-schema and the database with the same value. The change becomes useless and can be reverted.

GS-11373

Constraint or index type has been changed to '%1' but matches value in database.

The property of the database object has been changed in both the meta-schema and the database with the same value. The change becomes useless and can be reverted.

GS-11374

Constraint or index columns of '%1' has been changed to '%2' but matches value in database.

The property of the database object has been changed in both the meta-schema and the database with the same value. The change becomes useless and can be reverted.

GS-11375

Foreign key columns of '%1' has been changed to '%2' but matches value in database.

The property of the database object has been changed in both the meta-schema and the database with the same value. The change becomes useless and can be reverted.

GS-11376

Foreign key referenced columns of '%1' has been changed to '%2' but matches value in database.

The property of the database object has been changed in both the meta-schema and the database with the same value. The change becomes useless and can be reverted.

GS-11377

Cascade delete property has been changed to '%1' but matches value in database.

The property of the database object has been changed in both the meta-schema and the database with the same value. The change becomes useless and can be reverted.

GS-11378

Foreign key table has been changed to '%1' but matches value in database.

The property of the database object has been changed in both the meta-schema and the database with the same value. The change becomes useless and can be reverted.

GS-11379

Foreign key referenced table has been changed to '%1' but matches value in database.

The property of the database object has been changed in both the meta-schema and the database with the same value. The change becomes useless and can be reverted.

GS-11400

Unknown tag tag.

The meta-schema document contains unknown data. The schema file is corrupted and cannot be read.

GS-11550

Wrong line format.

The data contained in the file being imported to a meta-schema has an unsupported format. The data cannot be imported.

GS-11551

Can't convert type for column column of table table.

The type of the table column defined in the imported table is unsupported. The data cannot be imported.

GS-11552

Can't convert length for column column of table table.

The length of the table column defined in the imported table is invalid. The data cannot be imported.

GS-11553

Can't convert order for column column of table table.

The column has an unsupported order value. The import of the sch file cannot continue.

GS-11600

Compilation generated an empty sch file.

The compilation of the schema document generated an empty sch file. This can happen when no valid table columns have been found in the document.

GS-11650

The extraction process task can't be generated.

An error occurred while trying to create the database extraction process.

GS-11651

Database name can't be empty.

An empty database name has been found while trying to set up the database connection.

GS-11652

Schema filename can't be empty.

An empty filename has been found while trying to generate the schema document.

GS-11653

Preparing schema extraction...

This message indicates the schema extraction process is being set up.

GS-11654

Schema extraction started...

This message indicates the schema extraction process has started.

GS-11655

Merging extracted schema with existing one...

This message indicates the schema extraction process tries to merge the existing schema document with the extracted one.

GS-11656

Generating schema id...

This message indicates a new schema identifier is being generated.

GS-11657

Schema extraction successful.

This message indicates the schema extraction process has successfully completed.
GS-11658

Schema extraction failed.

The schema extraction process has failed at some point. Refer to other messages to get additional information.

GS-11659

Schema extraction aborted.

The schema extraction process has been aborted by the user.

GS-11660

Failed to move temporary schema file to destination.

An error occurred while trying to move the temporary schema file to its destination.

GS-11661

Failed to create schema backup file.

An error occurred while trying to create a backup of the schema file.

GS-11662

Failed to remove schema backup file.

An error occurred while trying to delete a backup of the schema file.

GS-11700

The connection test process task can't be generated.

An error occurred while trying to create the database connection test process.

GS-11750

Generating documentation for meta-schema...

This message indicates documentation for the schema is being generated.

GS-11751

Documentation generated at location

This message indicates documentation for the schema has been generated and is saved at the given location.

GS-11755

Invalid command line arguments

Check command line help for valid options. See The gsdbdoc command for more information.

GS-11756

Failed to generate documentation.

An error prevented the generation of the documentation. See The gsdbdoc command for more information.

GS-11760

Invalid log level.

Only VERBOSE is allowed. See The gsdbdoc command for more information.

GS-11761

Schema file is required.

The tool requires a database schema file. See The gsdbdoc command for more information.

GS-11762

Empty schema file path.

The provided path to the database schema is empty. See The gsdbdoc command for more information.

GS-11763

Schema file cannot be found.

The database schema file cannot be accessed. See The gsdbdoc command for more information.

GS-11764

Cannot access output path.

The provided output path cannot be accessed. See The gsdbdoc command for more information.

GS-11765

Style file not found.

The provided style file cannot be accessed. See The gsdbdoc command for more information.

GS-11766

Failed to copy style file.

The provided style file cannot be copied into the output directory. See The gsdbdoc command for more information.

GS-11767

Template directory not found.

The provided template directory cannot be accessed. See The gsdbdoc command for more information.

GS-11768

Failed to load template settings.

The settings from the provided template directory cannot be loaded. See The gsdbdoc command for more information.

GS-11780

Using template directory 'directory'.

Indicates which BAM template is used.

GS-11781

Template directory is relative, using builtin directory to locate it.

Indicates that the BAM template used is a built-in template.

GS-11782

No output path provided, defaulting to current directory.

Indicates that the documentation will be generated in the current directory.

GS-11783

No style path provided, using default styles.

Indicates that default styling will be used.

GS-11784 Skipping style file matching output path.

This is an informational message indicating the provided style file is located in the output directory, and no copy of the file is required.

GS-11800

error (error_code): error_message

The execution of the DB Explorer query failed. Refer to the error message for a detailed explanation.

GS-11810

Warning: no row affected.

The executed DB Explorer query did not affect any row.

GS-11830

Executed query: query

This message displays the executed DB Explorer query.

GS-11831

Success: number_of_rows row(s) affected.

This message displays the number of rows affected by the DB Explorer query.

GS-11832

Select execution successful : number_of_rows row(s) returned.

This message displays the number of rows returned by a SELECT statement by the DB Explorer.

GS-11833

Sql command successful

The DB Explorer query was successful.

GS-11834

Limit of number_of_rows row(s) reached.

The DB Explorer query has returned more rows than the limit set in the DB Explorer preferences.

GS-11835

Connection id: connection_information

This message displays the connection parameter used by the DB Explorer to connect to the database.

GS-11850

Failed to extract database meta data.

The extraction of the meta-schema has failed. Refer to the previous messages for more information.

GS-11851

Failed to connect to database.

The connection to the database has failed. Ensure the appropriate connection information has been provided.

GS-11852

Cannot instantiate database driver driver.

The database driver cannot be loaded. Check the driver name is correct and accessible.

GS-11853

Unsupported database database.

This database engine is not supported by the extraction tool.

GS-11860

The type type of column "table.column" is unsupported - table is ignored.

The data type of the table column is not supported by the extraction tool. The extraction of the table is canceled.

GS-11861

type column table.column is ignored.

The data type of the table column has been flagged to be ignored by the extraction tool. The table definition will not contain this column.

GS-11862

Foreign key foreign key is ignored due to missing table.

The foreign key references a table that was not found during extraction. The meta-schema will not contain this foreign key.

GS-11863

Failed to extract indexes for table \"table\".

A SQL error occurred while indexes were extracted for the table.

GS-11864

Failed to extract foreign keys.

A SQL error occurred while the foreign keys were extracted from the schema.

GS-11865

No column extracted for table \"table\" - table is ignored.

No table column has been extracted by the extraction tool. The extraction of the table is cancelled.

GS-11866

Database object \"name\" is ignored.

The database object has been ignored by the extraction tool. This usually happens with objects generated by the database.

GS-11867

Table column \"table.column\" datatype [type] is unsupported and has been converted.

The data type of the table column is not supported by the extraction tool, but the tool converted it to a similar data type.

GS-11870

Unexpected conversion parameter.

The conversion method provided to the extraction tool is invalid.

GS-11871

Missing conversion method.

The conversion method is required by the extraction tool.

GS-11872

Missing auto-increment indicator.

The parameter required for the extraction of the table column is not found.

GS-11873

Missing charlen indicator.

The parameter required for the extraction of the table column is not found.

GS-11874

Missing column type indicator.

The parameter required for the extraction of the table column is not found.

GS-11875

Missing distinct types indicator.

The parameter required for the extraction of the table column is not found.

GS-11876

Missing identity indicator.

The parameter required for the extraction of the table column is not found.

GS-11877

Missing serial indicator.

The parameter required for the extraction of the table column is not found.

GS-11878

Missing datetime precision indicator.

The parameter required for the extraction of the table column is not found.
GS-11880

No database connection.

The connection to the database is not found.

GS-11881

Table name is required.

The name of the extracted table is required by the extraction tool.

GS-11882

Column name is required.

The name of the extracted table column is required by the extraction tool.

GS-11883

Database schema is required.

The database schema / table owner is required by the extraction tool.

GS-11890

Missing database driver.

The database driver has not been provided to the extraction tool.

GS-11891

Missing output file parameter.

The meta-schema file has not been provided to the extraction tool.

GS-11892

Failed to read user password.

The password is unreadable.

GS-11899

unexpected error

An unexpected error has been encountered. Refer to the error message for a detailed explanation.