Warning Messages

Warning messages appear onscreen. These messages are also written to the log file. If tracing is enabled, these messages are captured in the trace file. See Log and Trace Files. These messages are prefixed by the timestamp hh:mm:ss, where hh is hours, mm is minutes, and ss is seconds.

"-t 1" option ignored as this would create a second copy of the log file

This message indicates that for the Client to process this option, additional bits must be set in the trace mask to differentiate the resulting trace file from the log file.

AA values for DataSet name[/rectype] are no longer valid, ds_mode set to 0 to force a re-clone

This message occurs during a redefine command or when running the Client Configurator. It indicates that the specified data set needs to be re-cloned since its AA Values are no longer valid after a DMSII reorganization.

AA values for DataSet name[/rectype] no longer valid

This message, which can occur during a process command, indicates that a DMSII structural reorganization has invalidated the specified data set that uses AA values as a key. The program automatically marks such a data set as needing to be recloned by setting its ds_mode to 0.

AA values for DataSet name[/rectype] are no longer valid after reorg

This message, which can occur during a redefine command, indicates that a DMSII structural reorganization has invalidated the keys for the specified data set, marking the data set as needing to be recloned (ds_mode to 0). The specified data set uses AA values as the a key.

Adding AA values to a table is not supported -- you need to reclone

This message, which can only occur during a redefine command or when running the Client Configurator, indicates that the command detected that the table uses AA values, which were previously not used. Since we cannot assign the correct values for this column in the existing record, you must reclone the data set.

AFN nnn has no StateInfo updates

This message appears when an audit file that contains no quiet points is processed.

All database API functions disabled by 'z' option

This message occurs during a dbutility process or clone command with the -z option. The Client loads the Client control table entries for the selected data source, after which it connects to the host and sets a global flag that disables all relational database functions.

The -z option is a debugging tool that can indicate the non-database time required to extract data for a data set. Always enable the -v option when you use the -z option as you will want to see the record counts generated. For more information, see dbutility Command Line Options.

All members of the variable format DataSet name must be recloned, ds_mode set to 0 for rectype rectype

If the ds_options bit DSOPT_Split_Vfmt_ds is set or the configuration parameter split_varfmt_ds is enabled, the DATABridge Client won't support the cloning of only certain members of variable format data sets.

Archive file was created by a newer version of the program, extra fields will be ignored

This message can occur during a reload command when you attempt to read an archive file that has a higher version than the program. There is no guarantee that this always works, as the program just reads the number of fields it knows about and ignores the rest. We do not recommend trying to read archive files with a higher version than the program.

Attempt to clear duplicate records for table 'name' failed

During the data extraction, it is possible to get duplicate records. When a record is moved, it appears more than once in the table. The Client remedies this by running the script script.clrduprec.tabname to delete all records that appear multiple times in the table and then reinstates the correct copy of the record by referring to the update that caused the record to move. If the script fails, this error results. See the SQL errors the precede this message to determine why the script failed.

Keys that allow null may cause problems with this script and require that you manually remove the duplicate records and recreate the index. Then, you can set the ds_mode for the data set back to 1 and restart the Client.

Attempt to drop procedure U_name failed

This message, which only occurs during a configure or dropall command, indicates that the Client was unable to drop the specified stored procedure (U_name, where name refers to a control table name). Refer to the database API error messages that precede this message to determine the cause of this error. This error will occur if your userid has inadequate privileges for dropping a stored procedure.

Attempt to modify record in table 'name' after failed insert was unsuccessful (AFN=afn, ABSN=absn, SEG=seg, INX=inx) - Keys: columnname = value, ...

This message, which can occur during a process or clone command, indicates that the recovery for an insert failed. Normally, the Client tries to recover by doing an update instead of an insert. When the update fails, the Client tries to recover by doing a delete insert operation. If the specified table is an OCCURS table, all of the rows for the given record are deleted and reinserted. Under normal circumstances, the Client should recover from this situation. This warning indicates that the table likely has missing rows or extra rows, either of which are causing the update to fail.

Attempt to propagate global stateinfo for DataSets failed

This message can occur after an audit file switch during a process or a clone command. It indicates that the program’s attempt to propagate the global state information to data sets with their in_sync columns set to 1 failed.

Attempt to set MARS failed -- reverting to single thread operations

When multi-threaded updates are enabled, the SQL Server Client enables MARS (Multiple Active Result Sets), a Microsoft ODBC extension option. MARS allows multiple queries that get results to be executed simultaneously. This is done by a SQLSetConnectAttr ODBC call. If this ODBC call gets an IM006 error indicating that the operation failed, this warning is issued and multi-threaded updates are disabled. This warning always occurs when enabling multi-threaded updates in SQL Server 2000.

Attempt to set parameter param_name to value1 rejected by DBEngine; using value2 instead

This message indicates that DATABridge Engine did not set a parameter value as specified by the Client because it was not within the configured allowable range. To change the configured allowable range, contact the administrator for the DATABridge host software on the mainframe.

Attempt to update stateinfo for DataSets in tracking mode failed

The attempt to update the DATASETS table failed, see SQL errors that precede this message to determine why the operation failed.

Bad DMS Timestamp 0xhhhhhhhh received, Timestamp set to NULL

This message can occur during a process or clone command when processing a stateinfo record that has a bad time stamp. This indicates an internal error from which the program recovers by setting the timestamp to NULL to prevent a SQL error.

Bad DMS TIME(60) value 0xhhhhhhhhhhhh received

This message can appear during a process or clone command. It indicates that the value of a DMSII REAL or ALPHA(6) item, which is being interpreted as a TIME(60) value, is illegal. This can be caused by one of the following problems:

  • Bad DMSII data
  • Attempting to interpret data that is not a DMSII TIME(60) as a TIME(60)
  • The Client recovers by setting the value of the item to a NULL.

bcp delimiter value incompatible with char mode bcp, a delimiter of TAB will be used

This message, which is only applicable to the SQL Server Client, indicates that you are attempting to use char mode bcp, with the bcp delimited set to something other than TAB. When this occurs, the program ignores the bcp delimiter you specified and uses TAB instead.

Bulk copy record count (mmm) and actual record count (nnn) differ for table 'name'

This message, which only appears if the configuration parameter verify_bulk_load is set to 1, indicates a mismatch between the number of rows in the table and the number of rows that the Client loaded. Check the bulk loader log file and the discards directory for a discard file for the given table. If the parameter verify_bulk_load is set to 1, the Client ignores the error. However, if it is set to 2, you get a similar error and the Client abends.

Bulk load failure has occurred, continuing with process command

When the Client detects a bulk load failure, it adds the data set to a list of data sets that encountered bulk loader failures during the data extraction phase and then it prints this message.

When the data extraction phase ends, the Client displays a message for each data set in the list. This message is the initial indication of the failure, which is reported again when the data extraction completes. Note that if the verify_bulk_load parameter is set to 2, the client abends as soon as it get the first bulk loader failure.

Bulk loader discard file created for table 'name'

This message indicates that the program detected the existence of a bulk loader discard file (bcp.name.bad in the case of Microsoft SQL Server and sqlld.name.bad in the case of Oracle) after table loading was complete. This is an indication that the bulk loader was not able to load all of the records. Look at the bulk loader discard and log files to determine why these errors occurred.

Bulk loader thread appears to be hung; main thread waiting

This message indicates that the main bulk loader thread could not continue after passing a temporary data file to the bulk loader. Typically, this occurs because the amount of temporary data file storage exceeds the value of max_temp_storage.

Cannot drop primary key or index for table 'name'

This message indicates that the Client encountered a SQL error while trying to drop an index. The index was being dropped because a bad value in dt_options of the DATATABLES table caused the index type to be wrong. See the SQL errors that precede this message to determine why the operation failed.

Cannot get Oracle version

This message can occur during any Client command. It indicates that the Client was unable to read the Oracle system table that contains the product version.

Cannot get SQL Server version

This message, which applies to only the Client for Microsoft SQL Server, can occur during any command. It indicates that the Client was unable to read the SQL server version using a "select @@version" SQL statement. Contact Attachmate Technical Support.

Cannot reorganize table 'name'

This message can occur during a redefine command or when running the Client Configurator It is usually preceded by other messages that indicate why the table cannot be reorganized.

Client operations inhibited between hh:mm and hh:mm

This message indicates that the Client cannot execute a process or clone command because a blackout period is in effect. Blackout periods are defined by the blackout_period parameter in the scheduling section of the Client configuration file.

Clone of DataSet name[/rectype] failed during bulk load

When the data extraction phase ends, the Client creates a list of all data sets that encounter bulk loader failures so that you don't have to look through the log file to find the data sets.

Clone of DataSet name[/rectype] was not completed

When Enterprise Server encounters a situation that forces it to restart the clone using remote regions (also referred to as "indirect disk"), it aborts the clone. The Client tracks this fact for the affected data sets. After the data extraction phase is completed, if any of these data sets have a mode of 0 (that is, the clone was not successfully completed), the Client displays this message.

Column name 'name' already in use, using 'name' instead

This message can occur during a define or redefine command. It indicates that a duplicate column name was changed to the specified name.

Command will have no effect until the next scheduled execution time

This message, which only applies to Windows, indicates that the user entered a SCHED command while the Client was idle.

Data Source name has INDEPENDENTTRANS set, extract_embedded parameter ignored

This message indicates that INDEPENDENTTRANS is set to True and therefore, your setting for the extract_embedded parameter is disregarded. If INDEPENDDENTTRANS is False, and extract_embedded parameter is True, DATABridge allows the data extraction of embedded data sets, even though these data sets cannot be cloned.

Database API functions previously disabled by 'z' option are now enabled

This message, which occurs during a process or a clone command with the -z option, indicates that the -z option is no longer in effect.

Database update level change ignored

This message can occur during a process or clone command and indicates that the Client ignores the change in the DMSII update level because none of the selected data sets were affected by the DMSII reorganization.

DATABridge Client operations inhibited until hh:mm by stop_time settings

This message, which is only applicable to dbutility, can occur process or a clone command. It indicates that the program cannot run due to the current values in the data source stop_time and end_stop_time columns. This can happen as soon as you start a process or clone command or after you get a commit. In other words, once the data extraction phase is started, the stop times are ignored until the start of the fixup phase (or update phase if you are running older host software).

DataSet name[/rectype] affected by reorg ds_mode set to 0

This message can occur during a redefine command with the -v option. For details, see Reorganizations, Filler Substitutions, and Initializations.

DataSet name[/rectype] allows duplicates, no updates will be allowed

This message indicates that the specified DMSII data set contains keys that allow duplicate records. The records will be cloned the first time; however, subsequent runs of dbutility process will not update them. The only time you receive this message is when you run a generate command. There is no message during the update. The solution is to create a composite key, as explained in Creating Indexes for Tables.

DataSet name[/rectype] can be reorganized, run reorg command: ds_mode set to ddd

This message, which occurs when running a redefine command or the Client Configurator, indicates that the program has generated scripts to reorganize the tables for the specified data set and avoid recloning it.

Make sure that you examine the scripts for problems and back up your database before you run a reorg command that will alter the tables.

DataSet name does not exist -- reload will not be performed

This message can occur during a dbutility reload command, if a list of data sets is specified on the command line and one of them is found not to exist. This message is just a reminder that the parameter was ignored.

DataSet name[/rectype] does not have a valid AA value, Include_AA option ignored

This message can occur during a define or redefine command and indicates that the Client ignores the include_AA option because the specified data set does not have a valid AA value.

DataSet name[/rectype] does not have a valid AA value, Use_AA_Only option ignored

This message, which occurs during a define or redefine command, indicates that the Client is ignoring the Use_AA_Only option, because the specified data set does not have a valid AA value.

DataSet name[/rectype] has been added

During a process command, the Client compares the new data set list from the Engine to the old data set list when a DMSII reorganization has been detected. If the new data set list contains additional data sets, this message is displayed. The ensuing redefine command will pick up these data sets unless the configuration parameter suppress_new_datasets is set to True.

DataSet name[/rectype] has been deleted

During a process command, the Client compares the new data set list from the Engine to the old data set list when a DMSII reorganization has been detected. If the new data set list is missing any data sets, this message is displayed. The DATABridge Engine does not always flag these data sets as being reorganized.

DataSet name[/rectype] has been purged

This message can occur during a process or clone command and indicates that the specified data set has been purged.

DataSet name[/rectype] has been reorganized

This message can occur during a dbutility process or clone command if the DATABridge Engine detects a structural reorganization or a change in item counts (for example, a filler substitution). For every data set affected by the reorganization, the DATABridge Engine sends the Client a stateinfo record whose ds_mode field has a value of 3. The Client sets the DS_Needs_Redefining bit in the status_bits column of the corresponding DATASETS entry and displays this message.

Important: Remember to back up the client control tables before starting the redefine command.

DataSet name[/rectype] has been reorganized, you must first execute a redefine command

This message can appear during a process or clone command if you try to clone a data set whose format level is not current. The Client sets the DS_Needs_Redefining bit in the status_bits column of the DATASETS entry for the data set. It also sets a flag that causes dbutility to exit with an exit status value of 2 immediately after all the data sets have been selected. It does not stop immediately so that it can catch all such data sets before you run a redefine command. The redefine command will most likely require that run a reorg or generate command before resuming operations.

DataSet name[/rectype] has been reorganized (fmtlevel: mmm -> nnn)

During a process command, the Client compares the new data set list from the DATABridge Engine to the old data set list when a DMSII reorganization has been detected. This message only appears when the DATABridge Engine fails to detect the fact that a data set has been reorganized. The Client handles the reorganized data set accordingly.

DataSet name[/rectype] has ds_mode=0, run a reorg (or generate) command before re-cloning it

This message, which occurs when running a redefine command or the Client Configurator, indicates that the specified data set will be recloned and program scripts must be generated (that is, via the generate command). If other data sets are involved, the generate command is automatically invoked when you run a reorg command. If you do not run a reorg command, you must execute a generate command before you reclone the data set.

DataSet name[/rectype] has ds_mode=mm, mode set to 0

This message occurs during a redefine command or when running the Client Configurator. It indicates that a data set has an invalid ds_mode and will be recloned as a result.

DataSet name[/rectype] has embedded datasets, AA values will be used as keys

When embedded data sets are cloned, their parent data sets use AA values as keys; AA values are the only way to implement the parent-child relationship. The DATABridge Engine has only the AA value of the parent data set for managing updates of embedded data sets.

DataSet name[/rectype] has invalid AA_Values, it will not be selected

This message, which occurs during a process or clone command when data sets are selected, indicates that the Client encountered a data set whose ds_mode is 12 and whose active column is 1. The ds_mode value of 12 indicates that the AA values for the data set are no longer valid. The Client treats this type of data set as if its active column was 0 until it is re-cloned. To force a re-clone, you must set ds_mode to 0 using the DATABridge Client Console or the relational database SQL query tool, or run a redefine command.

DataSet name[/rectype] has no active tables; active column set to 0

This message, which can occur during a process or clone command, indicates that the active columns have been set to 0 in all tables resulting from the specified data set. In this case, the Client automatically sets the data set's active column to 0, as there are no tables to populate.

DataSet name[/rectype] has no index, it will not be selected

This message can occur during a process or clone command and indicates that the specified data set will not be selected because its ds_mode had a value of 11, which indicates that it has no index.

DataSet name[/rectype] has no unique keys, AA values will be used as keys

This message can occur during a define or redefine command. It indicates that the Client will use AA values as the keys for the specified data set. For details, see Creating Indexes for Tables.

DataSet name[/rectype] which contains embedded DataSets does not have valid AA values

This message can occur during a define or redefine command and indicates that the specified data set contains embedded data sets but no valid AA values.

DataSet name[/rectype] which contains links does not have valid AA values

This message can occur during a define or redefine command and indicates that the specified data set contains link items but no valid AA values.

DataSet name[/rectype] will be recloned because DataSet name1[/rectype1] is being recloned

The process command will reclone the specified data set because the following conditions exist:

  • The configuration parameter automate_virtuals is set to True.
  • The specified data set is the secondary source for a virtual data set that gets its input from more than one DMSII data set. This data set was cloned previously but does not have a ds_mode value of 0.
  • The data set that is the primary source for the virtual data set has a ds_mode of 0 (it is being recloned).

For example, assume that SV‑HISTORY and SAVINGS both provide data for the virtual data set SV‑HISTORY‑REMAP, and SV‑HISTORY is the primary source. When the process command finds that SV-HISTORY is being recloned, it ensures that SAVINGS is also recloned. Unlike the clone command, which produces an error in this case, the process command simply reclones the specified data set after issuing this warning.

DataSet name[/rectype] will be treated as if its active column was 0 - execute a redefine command to remove its definitions from the client control tables

This message is displayed during a process or clone command when the program selects the data set and gets an invalid structure number error for DBEngine. This can happen at sites that create new data set structures that replace old ones with the same name. To avoid this problem, run a redefine command followed by a generate command to get the new structure defined. Then, reclone the data set in question. To avoid recloning, you must record the old stateinfo and reinstate it to get the program to produce exactly the same layout for the tables.

DBEnterprise audit files origin changed from AF_origin1 to AF_origin2

The Client displays this message when the audit file origin for DATABridge Enterprise Server changes. This message is not displayed if the previous value of the audit file origin is unknown (255).

DBEnterprise audit files origin is AF_origin

The Client displays this message when the audit file origin for Enterprise Server changes from unknown (255) to a value different than that specified by the configuration parameter dbe_dflt_origin. For example, the parameter is set to DirectDisk, but the new value is IndirectDisk.

"discard_data_errors" parameter overrides "alpha_error_cutoff" parameter

This message can appear during any dbutility command, it indicates that configuration file specifies two mutually exclusive configuration parameter settings. The discard_data_errors parameter forces the alpha_error_cutoff parameter to be set to 0, indicating that even if one character is in error, the Client should treat the data as bad and discard the record.

DMSII reorganization has occurred; AA values for DataSet name[/rectype] no longer valid - {execute a redefine command to handle this situation| it will be automatically recloned}

This message indicates that a DMSII garbage collection reorganization has invalidated the specified data set that uses AA values as a key. You must reclone the affected data set. The DATABridge Client sets the ds_mode column of such a data set to 12.

If the message states "it will be automatically recloned" (that is, the auto_reclone parameter is set to True), the Client automatically reclones the data set.

If the message states "execute a redefine command to handle this situation", the Client deselects the specified data set and continues the command. The next time you run a process command, the Client will not select data sets whose mode is 12. You can force a reclone by setting ds_mode to 0. Do not set ds_mode to 2 unless you create a composite key to ignore my_aa. See Changing an Index from AA Values to a Composite Key.

DTOPT_Preserve_Deletes bit erroneously set for table 'name' -- option reset

This message indicates that the program encountered a table whose DTOPT_Preserve_Deletes bit in the dt_options column of the DATATABLES entry is set even though there are no user_columns that are required to implement delete preservation. Make sure that you did not inadvertently set this bit.

DTOPT_PrimaryKey option does not match index type for table 'name'; attempting to recover

This error message can occur during a reorg command when the client tries to drop an index. If the dt_options bit for the table is wrong, the client realizes this and recovers by using the right SQL to drop the index.

Duplicate record encountered during a two step modify for table 'name' which has unique keys - Program automatically recovers from this error by doing a delete/insert instead (AFN=afn, ABSN=absn, SEQ=seg, INX=inx)- Keys: columnname = value, ...

This warning, which can occur during a process or clone command, indicates that the Client was unable to update a record in the specified table during a two-step modify. A two-step modify occurs when the value of the depends item for an item with an OCCURS DEPENDING ON clause changes. The Client first updates the rows that remain in the OCCURS table and later deletes the rows that are no longer present, or adds rows that were inserted. This warning appears if the update for one of the rows fails because the target row is not in the table. The Client recovers by deleting all of the rows in the OCCURS table for the given key and inserting all of the rows that are present in the after image. This only happens when the OCCURS table is corrupt.

Duplicate record encountered for table 'name' which has unique keys

- Program automatically recovers from this error by doing an update instead (AFN=afn, ABSN=absn, SEQ=seg, INX=inx) - Keys: columnname = value, ...

This message can occur during the fixup phase of a dbutility process or clone command if the -v option is enabled. It is unconditionally displayed if this situation occurs during the update phase as this is not expected behavior. The Client attempts to deal with this situation by changing the failed insert into an update instead.

Error in creating index for table 'name'

This message indicates that an error occurred when creating an index for the specified table. This can happen if: you have a very large table and your log space is too small; you have duplicates in a table that is defined with a unique key; or you created an invalid composite key. When this error occurs, the Client runs the script script.clrduprecs.name. If the DATASETS ds_options bit DSOPT_ClrDuprecs (0x8000) is set to 1 and the scripts run successfully, the index is re-created. If that bit is not set, the Client sets ds_mode to indicate that the data set has at least one table that does not have an index. This puts the data set temporarily out of commission until you fix the problem. To create the index for the specified table, issue a runscript command for script.index.tablename, as follows:

dbutility -n runscript dbscripts\script.index.tablename

Error in dropping DataSource name

An error occurred during a dbutility dropall command. Check the previous error messages (on screen or in log file) for details on what went wrong. If you attempted a dropall command and the scripts for the specified datasource could not be found, you probably did not point your current directory to the proper place. If this is the case, change to the proper directory and repeat the dropall command.

This error does not stop the execution of the dropall command. Instead, the Client informs you via this message and then proceeds to the next data source. When the dbutility dropall command is finished with all of the data sources, it leaves the Client control tables. This allows you to fix the problem (for example, the scripts are in a different directory). You can then rerun the dropall command.

Note: It is strongly recommended that you enable message logging (via the -t or -d option) when executing a drop or dropall command so that you have a complete record of what happened. Many errors are possible during the dbutility drop or dropall commands.

Error in purging table 'name'

The specified table was not dropped and recreated successfully. Check the error messages that appear prior to this one for more details.

Error in reading Null Record file "datasource_NullRecs.dat"

This message can occur during a process or clone command and indicates that the Client encountered and error while reading the specified file.

Error in reading value in BI for depends item 'name' in table 'name', using maximum of nnnn instead

This warning, which can occur during a process or a clone command, indicates that the Client detected a data error while retrieving the value of the depends item from the before-image of the record. A depends item is an item pointed to by an OCCURS DEPENDING ON clause, which is in the form "OCCURS N TIMES DEPENDING ON item_name." The Client also tests the value of the depends item to make sure it does not exceed the maximum specified in the OCCURS DEPENDING clause.

Error in reading value of depends item 'name' in table 'name', using maximum of nnnn instead

This warning, which can occur during a process or a clone command, indicates that the Client detected a data error while retrieving the value of the depends item from the after-image of the record. A depends item is an item pointed to by an OCCURS DEPENDING ON clause, which is in the form "OCCURS N TIMES DEPENDING ON item_name." The Client also tests the value of the depends item to make sure it does not exceed the maximum specified in the OCCURS DEPENDING clause.

fixed_delay scheduling overrides daily scheduling

See "sched_delay_secs" in [Scheduling].

Illegal split offset for item 'name' in table 'name' will not be performed

This message is a result of a bad user script that attempt to split an item by specifying a bad offset. You will not see this error when using the Client Configurator as it will not allow you to specify an illegal offset.

Index column 'name' in table 'name' has NULL attribute, this may cause updates to fail

This message indicates that the index includes a column that allows nulls. If you try to create a Primary Key constraint, it will fail. However, if you create an index, it will appear to work. Any update where this column is NULL, will fail; when the value is NULL, the where clause will be unable to satisfy the test for equality. In MISER databases, the Client handles this column by generating an additional stored procedure that does updates and deletes.

Index for tables in data set name[/rectype] contains a date that allows nulls; you will need to run a redefine command

This message, which is limited to MISER databases, indicates that the Client encountered an unregistered MISER date column that allows nulls. Running a redefine command will correct this problem, which only occurs when you upgrade to 6.1 in an environment where the NULL attributes of this columns were set using user scripts, rather than a configuration parameter that make the client take additional steps.

Index name 'name' already in use by another DataSource, using 'name1' instead

This message, which occurs during a define or redefine command, indicates that an index name that was not unique across data sources was renamed. The new index names are constructed by appending the smallest possible integer (for example, 1, 2, 3,...) to the name to make it unique. If this causes the name to become too long, the last few characters of the index name are changed to digits.

Index name 'name' already in use, using 'name1' instead

This message, which occurs during a define or redefine command, indicates that an index name that was not unique was renamed. For example this message can occur when the index name gets truncated, therefore making it indistinguishable from another index name.

The new index names are constructed by appending the smallest possible integer (for example, 1, 2, 3,...) to the name to make it unique. If this causes the name to become too long, the last few characters of the index name are changed to digits.

IO error writing to trace file "trace_filename", file closed; errno = number (errortext)

This message can appear during any dbutility command when the -t option is enabled. It indicates that there was an I/O error writing to the specified trace file. Use the error number and error message to determine the error. The system error that is included in this message should explain why the error occurred.

Item 'name' in table 'name' contains an illegal character in data - Keys: columname = value...

This message, which is limited to Windows servers using a translation DLL, indicates that the DLL detected an illegal character (for example, an EBCDIC character that translates to a value reserved for the starting bytes of a DBCS character, which is encountered when not in double byte mode). Even though this is not a fatal error, the Client discards the record because the discard_data_errors parameter is set to True.

Item 'name' in table 'name' contains an illegal character in data, record will be discarded - Keys: columname = value...

This message, which is only applicable when using the translation DLL, indicates that the DLL detected an illegal character (such as an EBCDIC character that translates to a value that is reserved for the starting bytes of a DBCS character, which is encountered when not in double byte mode). Leaving this character in the data causes the next character to be interpreted as byte 2 of a DBCS sequence, which can lead to a SQL syntax error if this is the last character in the sequence (the closing quote will be lost). The DLL handles this error, and typically does so by changing such a character to a question mark (?). If the DLL determines that there are too many errors, it causes the record to be set to NULL, in which case the last clause of this message will be included.

Item 'name' in table 'name' contains an illegal digit 0xdigit, number set to NULL value - Keys: columnname = value,...

This message can appear during a process or clone command. It indicates that the program encountered a value other than 0–9 (excluding the sign digit of a signed numbers). Numeric items that contain nothing but the digit 0xf are recognized as NULL; these are not flagged as in error except if they are keys, in which case they are discarded. This is not a fatal error and the number is stored as NULL unless the item is a key in which case the record is discarded, resulting in a different message.

Item 'name' in table 'name' contains an illegal digit 0xdigit, record will be discarded - Keys: columnname = value,...

This message can appear during a process or clone command. It indicates that the Client encountered a value other than 0–9 (excluding the sign digit of signed numbers). The Client recognizes numeric items that contain nothing but the digit 0xf as NULL and does not flag them as errors except if they are keys in which case the Client discards them. Even though this is not a fatal error, the record is being discarded because the discard_data_errors parameter is set to True.

Item 'name' in table 'name' has 8-bit characters in alpha data[; too many errors field set to NULL] - Keys: columnname = value, ...

This message can appear during a process or clone command, only when the configuration file parameter inhibit_8_bit_data is set to True. It indicates that the Client has changed all 8-bit characters to question marks. This is not a fatal error.

If the Client determines that more errors occurred than allowed by the value of the alpha_error_cutoff parameter, it sets the item to NULL, and the last clause of the sentence will be included in the message.

Item 'name' in table 'name' has 8-bit characters in alpha data, record will be discarded - Keys: columnname = value, ...

This message can appear during a process or clone command and appears only when the configuration file parameter inhibit_8_bit_data is set to True. It indicates that the Client has changed all 8-bit characters to question marks (?). This is not a fatal error, but the Client discards the record because the discard_data_errors parameter is set to True.

Item 'name' in table 'name' has control characters in alpha data, record will be discarded - Keys: keyname = value, ...

This message can appear during a process or clone command, and it indicates that the Client encountered illegal control characters in the data. The configuration file inhibit_ctrl_chars parameter determines whether or not some control characters are stored in the database or flagged as errors. This is not a fatal error, but the Client discards the record because the discard_data_errors parameter is set to True.

Item 'name' in table 'name' has control characters in alpha data[; too many errors field set to NULL] - Keys: keyname = value, ...

This message can appear during a process or clone command. It indicates that the Client has changed all control characters to question marks. This is not a fatal error. The configuration file inhibit_ctrl_chars parameter determines whether or not some control characters are stored in the database or flagged as errors.

If the Client determines that more errors occur than the value of the alpha_error_cutoff parameter allows, it sets the item to NULL, and the last clause of the sentence will be included in the message.

Item 'name' in table 'name' split into multiple columns

This message, which occurs during a define or redefine command, can occur if a DMSII ALPHA item is too big for the relational database to handle and the DIOPT_Split_Item bit (4) is set in the di_options column of the corresponding DMS_ITEMS table. When this happens, the item is stored in multiple columns.

Item 'name' in table 'name' was truncated to ddd characters

This message, which occurs during a define or redefine command, can appear if a DMSII ALPHA item is too big for the relational database to handle and the DIOPT_Split_Item bit (4) is not set in the di_options column of the corresponding DMS_ITEMS table. When this happens, ALPHA items that are too large are truncated.

Key_Item 'name' in table 'name' contains an illegal character in data, record will be discarded - Keys: columnname = value,...

This message indicates that the translation DLL detected illegal characters (such as an EBCDIC character that translates to a value that is reserved for the starting bytes of a DBCS character, which is encountered when not in double byte mode). Since this is item is a key, the Client tolerates no data errors.

Key_Item 'name' in table 'name' contains an illegal digit 0xdigit, record will be discarded - Keys: columnname = value,...

This is not a fatal error; the record is written to the discard file and is otherwise ignored. For more information on discard files, see Special Handling of Key Items in Discard Files.

Key_Item 'name' in table 'name' has 8-bit characters in alpha data, record will be discarded - Keys: columnname = value,...

This is not a fatal error; the record is written to the discard file and otherwise ignored. For more information on discard files, see Special Handling of Key Items in Discard Files.

Key_Item 'name' in table 'name' has control characters in alpha data, record will be discarded - Keys: columnname = value,...

This is not a fatal error; the record is written to the discard file and otherwise ignored. For more information on discard files, see Special Handling of Key Items in Discard Files.

Key_Item 'name' in table 'name' is NULL, item will be treated as blank
- Keys: columnname = value, ...

This message can appear during a process or clone command when the value of a key item of type ALPHA is NULL. If the DSOPT_Keep_Null_Alpha_Keys bit (128) of the ds_options column of the corresponding DATASETS entry is set, the program treats the NULL value as blanks instead of discarding the record. This warning is just a reminder that a NULL key was changed to blanks. This action can sometimes lead to duplicate records.

Key_Item 'name' in table 'name' is NULL, record will be discarded
- Keys: columnname = value, ...

This message can appear during a process or clone command when the value of a key item of type ALPHA is NULL. The program typically treats a NULL key as a non-fatal error; the record is written to the discard file and otherwise ignored. You are given the option to make the program treat NULL ALPHA keys as blanks instead of NULL. To do this, the DSOPT_Keep_Null_Alpha_Keys bit (128) of the ds_options column of the corresponding DATASETS entry must be set using user scripts.

Link item_name values for DataSet name[/rectype] no longer valid

This message can occur during a process or clone command and indicates that the link items for the specified data set are invalid because the target data set’s AA values were invalidated by a DMSII garbage collection or structural reorganization. You must reclone both data sets.

Malformed AF_header DOC record ignored

DATABridge Engine and Enterprise Server use this type of DOC header to pass information about an audit file to the Client when it starts processing updates from the given file. This message indicates that the record that has been sent is malformed. This is an internal error that should never occur.

Miser database requires "automate_virtuals" to be set to true; parameter enabled

This message indicates that the configuration parameter miser_database, which is required when using a MISER database, is set to the wrong value. Set this parameter to True.

Miser database requires "default_date_format" to be set to 1; parameter set to 1

This message indicates that the configuration parameter miser_database, which is required when using a MISER database, is set to the wrong value. Set this parameter to True.

Miser database requires "flatten_all_occurs" to be set to true; parameter enabled

This message indicates that the configuration parameter miser_database, which is required when using a MISER database, is set to the wrong value. Set this parameter to True.

Miser database requires "use_nullable_dates" to be set to true; parameter enabled

This message indicates that the configuration parameter miser_database, which is required when using a MISER database, is set to the wrong value. Set this parameter to True.

Missing trailing double-quote after WORKINGDIR value

This message indicates that the configuration parameter miser_database, which is required when using a MISER database, is set to the wrong value. Set this parameter to True.

More than one nullable date found in index for table 'name', updates will fail if column name is NULL

This message occurs when using a MISER database with the SQL Server client if you have more than one MISER date set as a key. The only solution is to use an RSN instead of the SET.

Multisource DataSet name[/rectype] must be recloned, run reorg command: ds_mode set to 34

This message occurs during a redefine command when a multisource data source is reorganized. It indicates that the specified data source must be recloned. You may need to wait until other data sources are caught up with the reorg before doing this. However, the reorg command can determine if the data source can be recloned.

Multisource DataSet name[/rectype] processing stopped until other sources are reorged – mode 35

This message, which can occur during a process or clone command involving a multisourced data sets, indicates that the data set has a mode of 35. This means that the source is waiting for all other data sources to be reorganized.

Multi-threaded updates need at least 2 DMSII buffers per thread to be effective

This message, which only occurs when processing a text-based configuration file, indicates that the number of DMSII buffers must be increased to support multi-threaded updates. For best results, set the parameter n_dms_buffer to 0 to let the Client determine the appropriate value.

Name 'name' is an SQL reserved word, using 'newname' instead

This message can occur during a define or redefine command. It indicates that a table, column, or index name is a SQL reserved word (for example, order or update) and that the specified new name is being used in its place. The newname is the original name with a suffix of _x.

No data received from server for number minutes

If the Client waits for TCP/IP input from the DATABridge Server past a certain threshold, the timer thread returns this message with that wait time.

This message is reissued (after 5 minutes, after 15 minutes, and then in 30 minute increments) until the Client receives input from the DATABridge Server. The timer is reset when the Client receives input. When you get this message make sure to check whether the DATABridge software requires operator response.

No DataSources found in client control tables

This message which can occur during an unload command, when a data source name of _all is specified. It indicates that the dbutility program did not find any data sources to unload.

No items except keys were active in occurs table 'name', active column set to 0

This message can occur during a generate command. It indicates that the Client disabled cloning of the specified secondary table because it contained nothing but keys.

No items were active in table 'name', active column set to 0

This message can occur during a generate command. It indicates that there are no data items to be cloned for the specified table. This message can occur in the following circumstances:

  • When you set all of the active columns in the DATAITEMS table to 0. Unless you intended for all the active columns to be set to 0, reset the active columns and run the process again.
  • When you change a table name in the DATATABLES Client control table but fail to make the same change in the DATAITEMS table.

No value specified max_temp_storage in config file, the default value will be used

This message appears only when you explicitly set max_temp_storage to 0 when spawn_bulk_load is enabled. To correct this error, change the max_temp_storage back to the default setting.

Null argument specified for T option, using prefix "trace"

This message can appear during any dbutility command where you use the -T option without specifying a log file name. If you do not specify a log file name, the Client uses the prefix "trace" (for example, traceYYYYMMDD[_HHMISS].log.

Open failed for script file "name", errno=number (errortext)

This message can occur during a process or clone command when the check_user_scripts parameter is enabled.

Overflow error in translation DLL for Item 'name' in table 'name'[, record will be discarded]

- Keys: columnname = value, ...

This message can appear during a process or clone command. It indicates that the character translation DLL called by the Client returned an overflow error status. This is not a fatal error, but when the configuration parameter discard_data_errors is set to True, the Client discards the record. If the item is a key, the Client also discards the record but displays a different message.

Overflow error in translation DLL for Key_Item 'name' in table 'name', record will be discarded
- Keys: columnname = value, ...

This message, which can appear during a process or clone command, indicates that the character translation DLL called by Client returned an overflow error status while translating the data for an item that is a key. This is not a fatal error; the record is written to the discard file and otherwise ignored. See Special Handling of Key Items in Discard Files.

Parameter use_ctrl_tab_sp requires that aux_stmts be greater than 0 - use_ctrl_tab_sp parameter disabled.

This warning indicates that the parameter aux_stmts is zero; it cannot be set to True if there are no database API stmt structures required to support the host variables. When the parameter use_ctrl_tab_sp is True, (default) all of the control tables updates use host variables.

Parameter Use_Global_Stateinfo requires that Optimize_Stateinfo be enabled - Optimize_Stateinfo parameter enabled.

This message appears during any Client command if you disable optimize_stateinfo without disabling use_global_stateinfo. For more information, see preserve_deletes. For optimal efficiency of the Client, avoid changing the values of deprecated parameters.

Parameters bcp_decimal_char and bcp_delim cannot be equal - bcp_delim set to "|"

This message, which is limited to the Oracle Client, can occur when a text-based configuration file is being processed. It indicates that you are attempting to use the same character as the field delimiter and the decimal character for SQL*Loader data. To resolve this problem, set the bcl_delim value to “|”.

Parameters convert_ctrl_char and inhibit_ctrl_chars are mutually exclusive

This message can occur when a text-based configuration file is being processed. It indicates that you need to set one of the specified parameters to False.

Parameters stop_after_gc_reorg and auto_reclone cannot both be enabled - auto_reclone parameter disabled.

This message, which can occur when a text-based configuration file is being processed, indicates that the specified parameters are mutually exclusive and ignore auto_reclone will be disabled.

Parameters stop_after_gc_reorg and auto_reclone cannot both be enabled

This message, which can occur when updating the binary client configuration file from the Console or the Client Configurator, indicates that the two specified parameters are mutually exclusive. This message is the result of a problem in the Console or the Client Configurator and generally,should not happen.

Parameters use_decimal_aa and use_binary_aa are mutually exclusive

This message can occur when a text-based configuration file is being processed. It indicates that the specified parameters are mutually exclusive and that you need to set one of them to False.

Parent_AA values for DataSet name[/rectype] no longer valid

This message can occur during a process or clone command and indicates that the Parent_AA values for the specified embedded data set are no longer valid because the DMSII database was reorganized. You must reclone both data sets.

Performance statistics cannot be disabled to support multi-threaded updates, parameter ignored

When running multi-threaded updates, you must have performance statistics enabled, as the Client uses the table statistics to balance the load between threads. Except for show_table_stats, statistics parameters should be left enabled.

'quit' command is only meaningful during process or clone commands

This message indicates that the operator issued a command-line QUIT command. The program only honors this command during a process or clone command.

'quit' command will take effect at the start of audit file processing

This message indicates that the operator issued a command-line QUIT command during data extraction. The QUIT command is not acted on during the data extraction phase; it will be acted on at the start of audit file processing.

Received unexpected result: seq_no = hexnumber; expected seq_no = hexnumber

This message indicates that the host sent an unexpected response to the DATABridge Client. Typically, this occurs when the previously executed DATABridge command had an error. Since this happens often at session startup where the expected sequence number is 1, this message is not printed when the sequence number is 1 unless the -v option is enabled. This message is displayed unconditionally for any other expected sequence number as this is a symptom of a protocol error between the DATABridge Server and the Client.

The DATABridge Client typically recovers from this condition by discarding the unexpected message, which is left over from a previous session.

Redefine command found nothing to do

The redefine command is driven by the bit settings of status_bits and active column in the DATASETS Client control table. This message indicates that the command found nothing in the status_bits columns that indicated that something needed to be redefined or remapped and that all the data sets that needed mapping had their active column set to 0. If you want the command to do something, except for the processing of changes caused by DMSII reorganizations, you need to set the DS_Needs_Remapping bit in the status_bits column of the data sets that you want remapped. In the case of data sets that were not previously mapped, setting the active column to 1 prior to running the redefine command is all that is needed. If you execute the redefine command without doing these things, this message appears to remind you that nothing happened.

Session initialization script name failed

This message indicates that the specified script failed. Check the preceding API or SQL error to see why it failed.

Set name is not usable as an index as it has too many keys

This warning occurs if you have a DMSII SET that has more keys than the relational database allows in an index. Consider using an RSN, which allows 16 keys for SQL Server and 32 keys for Oracle.

Set name of data set name[/rectype] allows key changes

This warning appears when a data set whose optimum SET has the KEYCHANGEOK attributes is encountered (during a define or redefine command) when using DATABridge Engine 6.0 or earlier. It is intended to warn you of the resulting increase in TCP/IP overhead. With the older Engines, the Client requests that all MODIFY records be passed to the Client as MODIFY BI/AI pairs. With the newer Engines, this decision is made by the Engine after comparing the old and new values of the keys in the index. The Client must register the keys it uses with the Engine in order for the Engine to perform this test.

Setting n_update_threads to 1 will not improve performance, set it to 2 or higher

Using one update thread makes the program work in single-threaded mode, except that all updates are queued to the worker. There is almost no overlap in SQL execution , as the main thread only handles the updates of the DATASETS table. The program will queue updates to the update worker and use all available DMSII buffers. Using one update thread is not likely to help performance.

Table 'name' cannot be altered data truncation would occur

This message indicates that the size of a column has decreased as a result of a reorganization or a change in a user script. The relational database will not let you do an alter command that does something like changing a column from a NUMBER(10) to a NUMBER(8).

Table 'name' cannot be altered, this type is alter is not supported

This message indicates that it is not possible use an alter command to fix a column whose data type has changed. You may be able to handle this manually by creating a new columns and populating the new column using the old values. The only other alternative is to reclone.

Table 'name' contains more than one nullable key that is a MISER date - updates will fail if the column col_name is null

This message, which is only applicable to MISER databases, indicates that you have more than one MISER date that allows NULLS in the index. The Client only handles one such key. To get past this error, reset the da_options bit DAOPT_Nulls_Allowed (1). However, if the date in question hhappens to be NULL when you attempt to update the table, the update will fail. Then, the solution is to use an RSN or a composite key as the index.

Table name 'name' already in use by another DataSource using 'newname' instead.

This message can occur during a define or redefine command. It indicates that specified table name was already in use by another data source. The new table name is constructed by appending the smallest possible integer (for example, 1, 2, 3,...) to the name to make it unique. If this causes the name to become too long, the last few characters of the table name are changed to digits.

Table name 'name' already in use, using 'newname' instead.

This message can occur during a define or redefine command. It indicates that a table name that was not unique was renamed. This is different from tables being renamed when they are the result of a split data set. For example this message can occur when the table name gets truncated, therefore making it indistinguishable from another table name.

The new table names are constructed by appending the smallest possible integer (for example, 1, 2, 3,...) to the name to make it unique. If this causes the name to become too long, the last few characters of the table name are changed to digits.

Table 'name' exceeds max record size of dddd bytes; table 'name1' will be used for additional columns

This message applies to the DATABridge Client for Microsoft SQL Server, and it can occur during a dbutility define or redefine command. It indicates that the specified table was split because the maximum size limit for a relational database record was reached. Keys in the primary table are replicated into the split table; the tables are not linked in any way. See Relational Database Split Tables.

Table 'name' has more than ddd columns; table 'name1' will be used for additional columns

This message can occur during a define or redefine command. It indicates that the specified table had to be split because the maximum column size limit (ddd) for the relational database was reached. The following is a list of maximum relational database column size limits: 1024 for Microsoft SQL Server; 1000 for Oracle. The keys in the primary table are replicated into the split table; the tables are not linked in any way. See Relational Database Split Tables.

Table 'name' is using a PRIMARY KEY, index column 'name', which is a MISER date, cannot have the NULL attribute

This message, which is only applicable to Miser database users, indicates that you are attempting to use a Primary Key constraint as the index for a table that has keys that are MISER date columns and allow nulls. To make the client use a Unique Index instead, you must clear the dt_options bit DTOPT_PrimaryKey (0x800).

Tcptest length exceeds maximum value of 16000, using 16000 instead

This warning indicates that the tcptest length parameter specified on the command line is too large. The value 16000 is used instead.

The clone of DataSet name[/rectype] will deferred until the client catches up with all pending DMSII reorgs

This warning, which appears at selection time during a process or clone command, indicates that the Client has not yet caught up with outstanding DMSII reorganizations and the requested clone cannot be performed at this time. The clone will be performed as soon after the Client processes that last outstanding DMSII reorganization.

The configured number of stmts (nn) is insufficient for k threads

When using multi-threaded updates, you need a minimum of 20 database API STMTs plus the number of threads. When not using multi-threaded updates, the minimum number of API STMTs required is 20.

This command will drop all DATABridge tables, do you really want to do this? - To bypass this check, use the 'u' option for the dropall command

This message appears during a dropall command when you enter the dropall command without the -u option. The -u option is required as a safeguard against accidentally dropping the DATABridge tables.

To avoid excessively large log files, we recommend setting "suppress_dup_warnings" to true

This message, which only occurs when the miser_database parameter is enabled, is a reminder to set this parameter to True.

Too many data errors for DataSet name[/rectype] -- additional errors will not be {displayed | logged}

This message can appear during a process or clone command. It indicates that the count of data errors for the given data set has just crossed the display or log cutoff threshold and that no more data errors will be displayed or logged for this data set. See error_display_limits.

"trace 1" command ignored as this would create a second copy of the log file

This message is displayed in response to a dbutility console TRACE command, which specified a trace mask of 1. The Client won't process this option unless additional bits are set in the trace mask, resulting in a trace file that can be differentiated from the log file.

Transaction group aborted; number SQL operations rolled back

This message, which is only displayed when the -v option is enabled, occurs when the Client aborts some updates at the end of the last audit file processed. These updates are picked up when the next audit file is processed.

Truncation error in translation DLL for Item 'name' in table 'name'[, record will be discarded]

- Keys: columnname = value,...

This message can appear during a process or clone command. It indicates that the character translation DLL called by Client returned a truncation error status. This is not a fatal error. However, when the configuration parameter discard_data_errors is set to True or the item is a key, the Client discards the record. If the item is a key, the Client also discards the record.

Unable to clear change column in {DATASETS | DMS_ITEMS} for data source name

This warning can occur when running a redefine command or when using the Client Configurator. It indicates that the Client was unable to clear the change column for the entries in the specified table. Check the SQL error that precedes this warning to determine why the update failed.

Unexpected held buffer for DataSet name[/rectype]; buffer discarded

This warning indicates that an internal error occurred causing a before image record to not be immediately followed by an after image record. Contact Attachmate Technical Support if you ever get this error.

Unknown error (0xdd) in translation DLL for Item 'name' in table 'name' [, record will be discarded] - Keys: columnname = value, ...

This message can appear during a process or clone command. It indicates that the character translation DLL called by the Client returned an undefined error status of 0xdd. This message is a catchall for any new error status that may be added to the data translation DLL. This is not a fatal error, but when the configuration parameter discard_data_errors is set to True, the Client discards the record. If the item is a key, the Client also discards the record but displays a different message.

Unknown error (0xdd) in translation DLL for Key_Item 'name' in table 'name', record will be discarded

- Keys: columnname = value, ...

This message can appear during a process or clone command. It indicates that the character translation DLL called by the Client returned an undefined error status of 0xdd. This message is a catchall for any new error status that may be added to the data translation DLL. This is not a fatal error. However, when the configuration parameter discard_data_records is set to True or the item is a key, the Client discards the record.

Update for table 'name' had no matching row, changing it to a delete/insert (AFN=afn, ABSN=absn, SEG=seg, INX=inx) - Keys: columnname = value, ...

This message can appear during a process or clone command. It indicates that the executed update SQL statement for a user table resulted in a row count of zero, indicating that the update did not find any matching rows. Furthermore, the update involved an item with an OCCURS clause, so instead of just turning the update into an insert, the program first deletes any partial data that may be in the occurs table and inserts the after image of the update.

Update for table 'name' had no matching row, changing it to an insert (AFN=afn, ABSN=absn, SEG=seg, INX=inx) - Keys: columnname = value,...

This message can appear during a process or clone command. It indicates that the execution of an update SQL statement for a user table resulted in a row count of zero, indicating that the update did not find any matching rows. The program turns these updates into inserts and tries them again.

Update for table 'name' had no matching row when optimizing updates, {update | transaction group} will be reprocessed without optimization

This message indicates that the Client will take somewhat drastic meaures to ensure that all updates are processed and data integrity is not compromised. If an update finds no matching rows while update optimization is enabled, you can run the risk of ignoring updates that should be there. If you get this error often, you should consider disabling update optimization.

User index creation script "name" failed

This message indicates that the execution of the index creation user script for the specified table (script.user_index.tablename) failed. See the preceding database API error message to determine the cause of the failure. The most likely reason is that the script is in error.

User table cleanup script name failed

This message can occur during a process or clone command and indicates that the specified script failed. Cleanup scripts are used to remove records from special tables that cannot be dropped.

Value of item 'name' in table 'name' exceeds maximum allowed, value set to NULL

This message indicates that the value of a DMS item of type REAL(n) or REAL(m,n) is too large for the client to be able to handle. The client uses the precision and scale to create the corresponding relational database column, therefore attempting to use such a value could result in an SQL error.

Value mmm for "maximum_columns" too large for {Oracle| SQL Server} Vm,Vn using nnn instead

When the Client determines which version of SQL Server or Oracle it is connected to, it checks the value of the configuration parameter maximum_columns to make sure that this value does not exceed the maximum number of column supported by the database. You will only get this error if you use a very old version of SQL Server or Oracle.

Virtual DataSet name has no index; all DataSets involved with it will not be selected

This message can occur during a process or clone command and indicates that no data sets associated with the given virtual data will be selected, because the virtual data set has no index.

Virtual DataSet name will not be selected because its parent structure was not selected

This message can occur during a process or clone command and indicates that the virtual data set will not be selected because the data set from which it was derived was not selected.

You are about to overrwrite your input configuration file "name" - To bypass this check, use the 'u' option for the import command

This message indicates that the input and output filenames are the same for an import or export command. If you want to convert the text-based configuration file dbridge.cfg to a binary file in addition to specifying the input file using the -f option, you must also set the -u option.

You are attempting to run a createscripts command for a data source that was not created using the Client Configurator - The control tables need to be upgraded by running "dbscriptfixup" before you can safely do this

This message, which only occurs when you run a createscripts command, indicates that the client control tables are not compatible with the Client Configurator. You must first run the dbscriptfixup program; this will fix the client control tables and create new set of user scripts that reflect changes to be implemented. The Client Configurator uses an additional bit in the various xx_options columns in the control tables and the xx_bmask columns to keep track of table entries that were changed during customization.

You are attempting to run a redefine command with the parameter "use_dbconfig" set to true - The control tables need to be upgraded by running "dbscriptfixup" before you can safely do this

This warning is a reminder to run the dbscriptfixup program before using the Client Consfigurator. The dbscriptfixup program fixes the control tablesand creates a new set of user scripts from which you can recover a corrupted relational database. It also sets the use_dbconfig parameter in the binary configuration file to True, which is required for the Client Configurator to run. (Attempting to edit this or other parameters in the binary configuration file will only corrupt the file.)