Skip to content

Command Messages

This section includes messages that occur when you issue a command using either the commandline client or the Client Console in conjunction with the Client Manager Service.

Common Log Messages

These messages, common to almost every command, are listed in the section below instead of repeating them for each command. We also include a few common messages that are generated at the start of the run for the commands that connect to the Databridge Server (DBEngine or Enterprise Server). These commands include define, redefine, process, clone, switchaudit and tcptest commands. These messages are marked as “(Server connection only)”.

All garbage data successfully flushed

(Server connection only) This message, which appears in the trace file when the TR_VERBOSE bit in the trace mask is set, indicates that the Client was able to read all of the false TCP data after receiving an incorrect length response to the test pattern. It always follows the message "Flushing garbage data". This message does not appear under normal circumstances.

ATM_ECHO: Pattern = 'string1', Response = 'string2'

(Server connection only) This message, which appears in the trace file when the TR_VERBOSE bit in the trace mask is set, indicates that the client and server successfully exchanged the given (matching) test patterns using the ATM_Echo RPC.

Begin processing configuration file "name"

This message, which appears in the trace file when the TR_VERBOSE bit in the trace mask is set, confirms that the Client is reading the specified text-based configuration file.

Client exit code: dddd[(nnn)] - exit_code_text
[(Client will try to recover from this error)]

This message appears any time a Client command completes. On UNIX, the 8-bit exit code is shown only if it differs from the actual exit code. The daemon uses the actual exit codes. You only need to deal with 8-bit exit codes in scripts that control the running of dbutility.

In the case of the command line Client (dbutility) a few exit codes cause a process command to restart itself after a brief delay. When this happens you will see the additional text "Client will try to recover from this error".

These exit codes include DBM_AUD_EOF (9), DBM_WRONG_ABSN (92), DBM_BLOCKTOOLONG (1179), DBM_LOC_MISMATCH (33) and DBM_ABSNMISMATCH (1180).

Additionally, if the client is terminated because a relational database deadlock was detected, dbutility will also attempt to recover by restarting after a brief delay.

Clustered System (nnn nodes)

(Windows only) This message, which is only written to the log file when running on a clustered system, displays the number of nodes in the cluster (typically 2).

Configuration information read from binary file "name"

This message, which appears in the trace file when the TR_VERBOSE bit in the trace mask is set, confirms that the Client has successfully read the specified binary configuration file.

Connected to host, port nnnn

(Server connection only) This message, which appears in the trace file when the TR_VERBOSE bit in the trace mask is set, indicates that the Client has successfully established a host connection, where host is the host name or IP address and nnnn is the TCP/IP port number.

Connecting to host, port nnnn

(Server connection only) Indicates that the Client is establishing a connection to the host, where host is the host name or IP address and nnnn is the TCP/IP port number.

Current date is: Day Mon dd, yyyy

This line appears, following a line of dashes, in the log file section for every Client run to identify the date on which the Client run was made. This line is also logged when the date changes after midnight, as all log messages only have a time prefix.

Databridge Client, Version vvv (nn-bit) {ODBC | OCI}/{SQLServer | Oracle} [vv/OS]

The version string vvv (e.g., 6.6.0.000) identifies the Databridge Client that you are running. The value of nn (64) identifies the CPU type. ODBC and OCI are the APIs used to access the relational database (SQL Server or Oracle). For UNIX platforms, the Oracle version for which the client is built (e.g., 11g) and the operating system (e.g., Linux) is also listed.

Databridge Configuration Server, Version vvv (nn-bit) {ODBC | OCI}/{SQLServer | Oracle} [vv/OS]

The version string vvv (e.g., 6.6.0.000) identifies the secondary Databridge Client (DBClntCfgServer) that you are running. The value of nn (64) identifies the CPU type. ODBC and OCI are the APIs used to access the relational database (SQL Server or Oracle). For UNIX platforms, the Oracle version for which the client is built (e.g., 11g) and the operating system (e.g., Linux) is also listed. This program provides database access to the Client Console and the supports the Client Configurator. Unless you use the Client Configurator, this program only runs for brief periods of time and shuts down automatically after a minute of inactivity.

DBEngine Version: version_string

(Server connection only) This message, which is only written to the log file, shows the version of the Databridge Engine being used on the mainframe. It is only present in commands that connect to the Databridge Server (or Enterprise Server).

DBEnterprise Version: version_string

(Server connection only) This message, which is only written to the log file, shows the version of the Databridge Enterprise Server being used. It is only present in commands that connect to the Databridge Enterprise Server.

DBServer Task Number: nnnn

(Server connection only) This message, which is only written to the log file, shows the DBServer task number on the MCP system.

DBServer Version: version_string

(Server connection only) This message, which is written to the log file shows the version of DBServer used. It is present in commands that connect to the Databridge Server (or Enterprise Server).

DBSupport Title: file_title

(Server connection only) This message, which is only written to the log file, shows the file title of the Databridge Support Library being used on the mainframe (for example “(DB66)OBJECT/ DATABRIDGE/SUPPORT/DEMODB ON DPACK”). It is only present in commands that connect to the Databridge Server (or Enterprise Server).

DBSupport Version: version_string

(Server connection only) This message, which is only written to the log file, shows the version of the Databridge Support Library being used on the mainframe. It is only present in commands that connect to the Databridge Server (or Enterprise Server).

Disconnecting and restarting transport initialization

(Server connection only) This message, which only appears in the trace file when the TR_VERBOSE bit in the trace mask is set, indicates that the response to the ATM_Echo remote procedure call (RPC) timed out. The Client recovers from this error by disconnecting from the server and trying to restart the connection process (up to three times).

DMSIISupport Title: file_title

(Server connection only) This message, which is only written to the log file, shows the file title of the Databridge DMSII Support Library being used on the mainframe (for example “(DB66)OBJECT/ DATABRIDGE/DMSIISUPPORT/DEMODB ON DPACK”). It is only present in commands that connect to the Databridge Server (or Enterprise Server).

DMSIISupport Version: version_string

(Server connection only) This message, which is only written to the log file, shows the version of the Databridge DMSII Support Library being used on the mainframe. It is only present in commands that connect to the Databridge Server (or Enterprise Server).

End processing configuration file "name"

This message, which only appears in the trace file when the TR_VERBOSE bit in the trace mask is set, confirms that the Client has processed the specified text-based configuration file.

Filter: filter_name

(Server connection only) This message, which is only written to the log file, shows the name of the FILTER being used in the Support Library on the mainframe. It is only present in commands that connect to the Databridge Server (or Enterprise Server).

Flushing garbage data

(Server connection only) This message only appears in the trace file when the TR_VERBOSE bit in the trace mask is set. To verify that the transport layer works correctly, the Client exchanges a test pattern with DBServer. If the Client receives a response that has an incorrect pattern or length, the Client attempts to recover from this situation and returns this message. You should not see this message under normal circumstances.

Negotiated protocol level = number, Host version = major_vers.minor_vers

(Server connection only) This message, which is only written to the log file, shows the protocol level that the Client and the server use, which is the lesser of the client and server protocol levels (the 6.6 release uses a protocol level of 33). The second part of the message contains the major and minor version numbers of the server (e.g., 6.6).

ODBC driver: "name", version = vv

This message, which only applies to the SQL Server Client, identifies the name and the version of the ODBC driver used.

Oracle database name: name

This line is written to the log file only when the database parameter in the Client configuration file has no assigned value and the command line -D option has not been used to specify the database name. It indicates that the default database name is used. This is not typically done in a production environment, but it could be done when using Oracle Express to evaluate the product. The preferred way of doing things is to create an entry for the database in the file “tnsnames.ora” in the “network/admin” folder in the Oracle files.

Oracle version: major_vers.minor_vers

This line, which is only written to the log file, displays the major and minor version of the Oracle database you are using (e.g., 11.2). This message is present for all commands that connect to the Oracle database.

OS version: version_string

This line, which is only written to the log file and is only applicable to UNIX clients, displays the Operating System version string (e.g., 6.1 on an AIX platform). This message is present for all commands that connect to the relational database. This information is crucial to support to determine if you are using a supported platform. For a complete list of supported platforms and system requirements, see the Databridge Installation Guide.

OS: Windows [Server] version_name

This line, which is only written to the log file, displays the name of the Windows operating system. For servers you get the word "Server" followed by one of the following: 2008, 2008 R2, 2012, 2012 R2 or 2016. For desktop systems version_name is one of the following: Vista, 7, 8, 8.1 or 10.

Retrying ATMEcho RPC after flushing input

(Server connection only) This message, which only appears in the trace file when the TR_VERBOSE bit in the trace mask is set, indicates that the Client received a response of the wrong length from DBServer and is retrying the ATM_Echo RPC.

Server communications initialization complete

(Server connection only) This message, which only appears in the trace file when the TR_VERBOSE bit in the trace mask is set, indicates that DBServer or Enterprise Server has successfully executed the DBINITIALIZE RPC.

SQL Server version: major_vers.minor_vers

This line, which is only written to the log file, displays the major and minor version of the Microsoft SQL Server database you are using. Note that SQL Server 2008 is version 10.0, SQL Server 2008 R2 is version 10.5, SQL Server 2012 is version 11.0, SQL Server 2014 is version 12.0, SQL Server 2016 is version 13.0, and SQL Server 2017 is 14.0. This message is present for all commands that connect to the SQL Server database.

System: host_system_desc

(Server connection only) This message, which is only written to the log file, shows information about the type of Unisys mainframe being used (for example, System: CS790 :7003 SSR 56.189.8111). It is only present in commands that connect to the Databridge Server (or DBEnterprise Server).

Configure Command Messages

The following messages appear in response to the Databridge Client configure command.

"locks" directory created

This message appears when the configure command creates the locks subdirectory in the global working directory. The global working directory and the locks directory are created only if they do not already exist.

"name" sub-directory created

This message appears when subdirectories for the client's working directory are created. These subdirectories are config, logs, dbscripts, discards, and scripts.

Beginning Databridge Client configuration

This message indicates that the process of creating the control tables and their indexes has begun.

Client configuration file "dbridge.cfg" created in "config" sub-directory

This message appears when the Client creates the binary configuration file dbridge.cfg in the config subdirectory. If the directory already exists and contains an old configuration file, this file will be used instead.

Creating control table name

This message indicates that the specified control table and its associated index are being created in the relational database.

Databridge Client configuration completed

This message indicates that the dbutility configure command is complete and that all of the empty control tables were successfully created in the relational database.

Dropping control table name

This message indicates that the specified control table is being dropped from the relational database. When a Client control table is found to exist, this command will drop it before creating it again. This message appears when you have previously executed a dbutility configure command and for some reason are executing it again using the -u option.

Generating control tables...

This message indicates that the Databridge Client is creating the control tables.

Working directory "path" created

This message appears when the command creates the global working directory for the Client (that is, the working directory for the service). This directory and the locks subdirectory are created only if they do not already exist.

Define Command Messages

The following messages appear in response to the Databridge Client define command.

"locks" directory created

This message appears when the define command creates the locks subdirectory in the global working directory. The global working directory and the locks directory are created only if they do not already exist.

"name" sub-directory created

This message appears for each subdirectory of the Client’s working directory that is created. These subdirectories are config, logs, dbscripts, discards, and scripts.

Beginning New DataSource definition

The data source with the host name and port number specified on the command line is being defined. The dbutility define command will get an error if the specified data source is present in the control tables. To resolve this error, use the –u option to force delete old entries in the Client control tables.

Client configuration file "dbridge.cfg" created in "config" sub-directory

This message appears when the Databridge Client creates the config subdirectory and a binary configuration file, dbridge.cfg, in that directory. If the config directory already exists, the existing configuration file is used.

Creating file "source_NullRec.dat"

The Client is creating the file, source_NullRec.dat to hold the NULL VALUES for data set records from the specified data source. source is the data source specified in the data_source column of the corresponding DATASOURCES Client control table.

DataSet name is a global data set, active column set to 0

The Client automatically disables cloning for the indicated data set. Normally, the data in the global data set is not cloned because it is not very useful. If you need to clone this data set, simply set active = 1 in the corresponding row of the DATASETS Client control table using a user script or the Client Configurator. If you are not using the Client Configurator, you will need to rerun the define command with the -u option (or run a redefine command with the -R option) to make the change take effect.

DataSet name is a restart data set, active column set to 0

The Client automatically disables cloning for the DMSII restart data set.

DataSource definition completed

This message indicates that the define command is complete. This means that a row with the data source name, host name, and port number has been added to the DATASOURCES control table. In addition, a row for each data set has been created in the DATASETS control table. The DMSII layout information has been downloaded to the DMS_ITEMS control tables; and the corresponding relational database table layout information has been created in the DATATABLES and DATAITEMS control tables.

DB_Info: update_level = ddd, update_ts = timestamp, highest_strnum = ddd
DB_Info: database_ts = timestamp, database_name = name
[DB_Info: OptionFlags=options]

These messages are only written to the log file. The first line provides the database update level and timestamp, and the highest structure number in the database for the data source being accessed. The second line provides the database timestamp and the database name for the data source being accessed. A third line of comma-separated options appears when any of these options are true: IndependentTrans (INDEPENDENTTRANS is set for the DMSII database); AccessActive (READ ACTIVE AUDIT is set in the Engine Control File); RDB (the DMSII database is an RDB secondary database); FileXtract (the data source is a FileXtract file); and LINKS (LINKS is set to TRUE in the Engine Control File).

Defining table entries for DataSet name[/rectype] (struct_number)

The Client control table entries for the specified data set are being defined. /rectype appears only for variable-format data set records that have a nonzero record type (they contain a variable part). For more information, see "Variable-Format Data Sets" in the Databridge Client Administrator's Guide. struct_number is the DMSII structure number of the data set. The Databridge Engine processes data sets in structure number order; the structure number is an indication of how close the define command is to completing.

Inserting data into control tables...

This message indicates that data is being inserted into the control tables.

Launching makefilter utility to create the binary filter file "dbfilter.cfg" in the config directory

This message indicates that the client is launching the makefilter utility to compile the filter "dbfilter.txt" that was found in the config subdirectory. The makefilter output is written to a separate log file named "prefix_flt_yyyymmdd.log" (where prefix is the prefix used for the client log file and defaults to "db").

Loading control tables for datasource

This message appears at the beginning of the second phase of the define command, when the Client reloads the control tables in order to pick up updates that result from the running of user scripts that alter the DMSII layout (script.user_layout.primary_tablename).

Mapping table entries for DataSet name[/rectype] (struct_number)

This message, which normally only appears in the trace file when the TR_VERBOSE bit in the trace mask is set, indicates that the DMSII layout for the data set in question is being mapped to the corresponding relational database tables. It only appears in the log file if the status_bits column in the corresponding DATASETS table entry has the DS_Needs_Mapping bit (4) set.

Rows updated = ccc

This message, which only appears in the log file when the -v option is enabled, shows the row count for all SQL statements that are executed when processing user scripts. A value of 0 is usually an indication that the user script is in error. At this point, it's a good idea to rerun the command with user script tracing and log output tracing enabled (that is, -t 2049). Log output tracing creates a trace file with both row counts and the SQL statement, which can be hard to match up otherwise.

Running script script_file_spec

This message is a confirmation that the Client is running the specified script. For each SQL statement in the script, when the -v option is enabled, the Client writes the number of rows that have been changed to the log file. See the preceding message, "Rows updated = ccc", for more information.

Working directory "path" created

This message appears when the define command needs to create the global working directory for the Client (that is, the working directory for the service). This directory and the locks subdirectory are created only if they do not already exist.

Redefine Command Messages

The following messages appear in response to the Databridge Client redefine command. These messages can also appear when running the Client Configurator from the Client Console.

Beginning updates of DataSource definitions

This message indicates that the data source definitions are being recreated. Old Client control table entries that correspond to data sets which need to be redefined (for the specified data source) are deleted first. However, any customization that was done to them using the Client Configurator will be preserved. In the case of dbutility this is normally achieved by using user scripts, unless the configuration parameter use_dbconfig is set to True.

Command returned a status of nnn

This message, which only appears when using the Client Configurator, shows the result of the Compare Layouts operation, which determines if the relational database layout has changed as a result of the data source being redefined. Possible values for nnn: - 0 indicates that the layouts are unchanged - 2032 indicates that a generate command is required (most likely because there are some datasets that have tables that need to be cloned or recloned) - 2033 indicates that a reorg command is required, as the changes can be made without having to reclone anything. - Any other exit status indicates that an error has occurred while comparing the layouts. In this case, there should be earlier error messages you need to look at. The same message is also used to indicate that a remote procedure call by the Client Configurator returned a non-zero status, which means that the RPC encountered an error.

Command returned a status of nnn (text)

This message, which only appears when using the Client Console, shows the result of a Define/Redefine command issued by the Client Console. The message text gives a brief explanation of the error and can be one of the following: - No Futher Action Required - processing can continue -In the case of an existing data source this indicates that the redefine command does not require that a reorg or generate command be issued. - You need to run a Reorganize command - In the case of an existing data source this indicates that the redefine command has found differences between the old and new database layouts and that you need to run a Reorganize command to alter the tables. - You need to run a Generate command - This indicates that the scripts in the dbscripts directory need to be generated before you can run a process command.

Comparing old and new relational database layouts

This message, which only appears when using the Client Configurator, indicates that old and new relational database layouts are being compared. The results of this operation determine if the data source needs any special attention prior to resuming normal operations, such as running a generate or reorg command.

Creating file "datasource_NullRec.dat"

This message indicates that the Client is creating the file, datasource_NullRec.dat to hold the NULL VALUES for data set records from the specified data source. datasource is the source specified in the data_source column of the corresponding DATASOURCES Client control table. A redefine command with the -R option (“Redefine All Data Sets” when using the Client Console) recreates the Null Record file. If you accidentally delete this file, this how you go about recreating it.

DataSet name[/rectype] did not previously exist -- you will need to run a generate command

This message indicates that a new data set was added to the DMSII DASDL since the last time a define command or a redefine command was executed and is a reminder that you need to execute a generate command before cloning the new data set. This message only appears when the parameter suppress_new_datasets is set to False.

DataSet name[/rectype] did not previously exist, defined with the active column set to 0

This message indicates that a new data set was added to the DMSII DASDL since the last time a define command or a redefine command was executed. This message only appears if the parameter suppress_new_datasets is set to True. In this case, the active column for the new data set is set to 0 in the DATASETS table.

DataSet name[/rectype] no longer exists

The specified data set was deleted from the DMSII DASDL since the last time a define or redefine command was executed.

DataSet name[/rectype] unaffected by reorg ds_mode is n[, however a generate command is required as status_bits=ssss]

The layout of the relational database table mapped from the specified data set was not affected by the database reorganization. Therefore, the specified data set does not require recloning. In the unusual case where the command requires that you execute a generate command, the full message is shown.

DataSet name[/rectype] will be re-defined

This message, which only appears in the trace file when the TR_VERBOSE bit in the trace mask is set, indicates that the specified data set will be redefined

DB_Info: update_level = ddd, update_ts = timestamp, highest_strnum = ddd
DB_Info: database_ts = timestamp, database_name = name
[DB_Info: OptionFlags=options]

These messages are only written to the log file. The first line shows the database update level, the database update timestamp and the highest structure number in the database for the datassource that is being accessed. The second line shows the database timestamp and the database name for the data source that is being accessed. The third line lists comma-separated options and only appears when any of the following is true: IndependentTrans (INDEPENDENTTRANS is set for the DMSII database), AccessActive (READ ACTIVE AUDIT is set in the Engine Control File), DBPlus (DBPlus is being used by the Engine), RDB (the DMSII database is an RDB secondary database), FileXtract (the data source is a FileXtract file) and LINKS (LINKS is set to TRUE in the Engine Control File).

Defining table entries for DataSet name[/rectype] (struct_number)

The client control table entries for the specified data set are being defined. /rectype appears only for variable-format data set records that have a nonzero record type. (They contain a variable part.) struct_number is the DMSII structure number of the data set. Because the Databridge Engine processes data sets in structure number order, the structure number is an indication of how close the define command is to completing.

Format level change mmm -> nnn detected for DataSet name[/rectype]

This message, which is printed at the start of a redefine command, indicates that the format level for the given data set has changed. Every time a data set is changed in the DASDL, the format level for the data set is set to the database update level when the DASDL is recompiled. A format level change is an indication that the data set was affected by a DMSII structural reorganization.

Item count change mmm -> nnn detected for DataSet name[/rectype]

This message, which is printed at the start of the redefine command, indicates that the number of items in the data set has changed. This could be the result of a filler substitution reorganization or a change in the column filtering specified in GenFormat.

Loading control tables for datasource

The redefine command shows this message every time it loads the Client control tables. The redefine command always starts by loading the Client control tables. The Client control tables are also reloaded after running user scripts, at the end of the two main phases of the command, in order to pick up updates that result from the running of these scripts.

Mapping table entries for DataSet name[/rectype] (struct_number)

This message, which normally only appears in the trace file when the TR_VERBOSE bit in the trace mask is set, indicates that the DMSII layout for the data set in question is being mapped to the corresponding relational database tables. It only appears in the log file if the status_bits column in the corresponding DATASETS table entry has the DS_Needs_Mapping bit (4) set.

No Further Action Required - Processing can continue

This message, which only applies to the command line Client dbutility, is a confirmation that the redefine command did not detect any layout changes and you can resume processing audit files.

Redefine DataSet name[/rectype]: DSOPT_NoStoredProcs option bit was changed from aa to bb

This message indicates that the use of stored procedures for the data set in question has changed. This happens when you change the bit by either changing the use_stored_procs configuration parameter or by using a user script. The Client will ask you to run a reorg command to fix things up. The reorg command will create a new set of scripts and it will refresh the stored procedures for the data set. This means that when you go from using stored procedures to not using them, they will be dropped and conversely if you go from not using stored procedures to using them they will be created.

Redefine DataSet name[/rectype]: index name for table 'name' was changed from 'name1' to 'name2'

This message indicates that the name of the index for the given table has changed. The client simply renames the index using a reorg command to avoid problems at a later time.

Redefine DataSet name[/rectype]: index type for table 'name' was changed from index_type1 to index_type2

This message indicates that index type for the given table has changed (for example, from a unique index to a primary key). The client drops the old index and creates the new index using a reorg command.

Redefine DataSet name[/rectype]: Table 'name' no longer being used as a result of the DMSII reorg - Run the script 'script.drop.name' to drop the table and its stored procedures

As a result of the DMSII reorganization of the specified data set, the specified table was removed from the DATATABLES and DATAITEMS entries mapped from this data set. The table is not dropped. To drop the table and the stored procedures associated with it, execute the script noted in the message.

Redefine DataSet name[/rectype]: Table 'name' was added [--active column set to 0 in DATATABLES]

As a result of the DMSII reorganization of the specified data set, the specified table was added to the DATATABLES and DATAITEMS entries mapped from this data set. If the parameter suppress_new_columns is set to True, the Databridge Client sets the active column of this entry (in DATATABLES) to 0.

Redefine Table 'name': Column 'name' (Item# number), changed from dec_type(p1[,s1]) to dec_type(p2[,s2])

As a result of the DMSII reorganization, the data type of the specified column has changed. dec_type indicates the values of the sql_type column of the corresponding DATAITEMS table entries. p1 and p2 indicate the values of the sql_length columns. s1 and s2 indicate the values of the sql_scale column if applicable for the specified sql_type.

Redefine Table 'name': Column 'name' (Item# number) dms_subtype value changed from mmm to nnn

This indicates that the dms_subtype for the given column changed. If this is a date this means that the format of the DMSII data is now different. This usually means that you will need to reclone the data set.

Redefine Table 'name': Column 'name' (Item# number) item_key value changed from n(key#=k1) to m(key#=k2)

This indicated that the order of the columns in the index have changed. The numbers in parentheses are the actual positions of the columns within the index. As long as they're the same, the client ignores any changes in the item_key values.

Redefine Table 'name'': Column 'name'' (Item# number) masking_info value changed from 0xhhhh to 0xhhhh

As a result of a DMSII reorganization (or a change in customization for the column) the state of the masking for the column in question was changed. This will be handled by the ensuing reorg command which will ALTER the table.

Redefine Table 'name': Column 'name' (Item# number) NULL attribute changed from old_val to new_val

As a result of a DMSII reorganization, the NULL item attribute changed. In addition, the message shows both the old and new values. The client alters the column using the reorg command, which runs the reorg scripts created by the redefine command.

Redefine Table 'name': Column 'name' (Item# number) SQL length value changed from old_length to new_length

As a result of a DMSII reorganization, the SQL length for the specified column in the specified table changed. In addition, the message shows both the old and new values. The client alters the column using the reorg command, which runs the reorg scripts created by the redefine command.

Redefine Table 'name': Column 'name' (Item# number) SQL type value changed from old_type to new_type

As a result of a DMSII reorganization, the SQL type for the specified column in the specified table changed. In addition, the message shows both the old and new values. The client alters the column using the reorg command, which runs the reorg scripts created by the redefine command provided that the type of transformation is allowed. For example, if a column with a data type of int changes to date, the data set must be recloned; the alter command does not support this type of transformation.

Redefine Table 'name': Column 'name' (Item# number) was added [--active column set to 0 in DATAITEMS]

As a result of a DMSII reorganization, the specified column was added to the specified table. If the parameter suppress_new_columns is set to True, the Client sets the active column of this entry (in DATAITEMS) to 0. If the parameter suppress_new_columns is set to False, the client adds the column to the table using the reorg command, which executes a script that does the actual alter command.

Redefine Table 'name': Column 'name' (Item# number) was deleted

As a result of a DMSII reorganization the specified column in the specified table was removed. The client drops the column from the table using the reorg command, which executes a script that does the actual alter command. If you want to keep the column, modify the script not to drop the column. Make sure that the column has the NULL attribute or has a DEFAULT defined; the client will not provide a value for this column. Otherwise, the update will fail.

Redefine Table 'name': Column 'name' (Item# number) will be handled as a nullable key

This message, which is only applicable to MISER databases, indicates that a MISER date, which is a key, has been encountered when the parameter use_nullable_dates is set to True. The client will generate special code for the update stored procedure to handle the case when the value of the key item in question is NULL.

Note

This code is limited to one nullable date in the index of the table. If you have more, you must use a different index.

Restoring user changes to DATATABLES and DATAITEMS tables

This message only appears when the redefine command runs in Client Configurator compatible mode (that is, the configuration parameter use_dbconfig is set to True). If the data source was not created using the Client Configurator, you must run the dbscriptfixup program before you can enable the parameter use_dbconfig.

When run in this mode, the redefine command does not use user scripts. Instead, it restores the changes from the old copy of the control table. This message, which only appears in the trace file when the TR_VERBOSE bit in the trace mask is set, indicates that the customization changes for the relational database tables and their columns are being restored from the old copy of the control tables.

Restoring user changes to DMS_ITEMS table

This message, which only appears in the trace file when the TR_VERBOSE bit in the trace mask is set, indicates that the customization changes for the DMS_ITEMS entries are being restored from the old copy of the control tables. See the preceding message for details.

Rows updated = ccc

This message, which only appears if the -v option is enabled, shows the row count for all SQL statements that are executed when processing user scripts. A value of 0 is usually indicates that the user script is in error. When this occurs, it's a good idea to rerun the command with the user script tracing and log output tracing enabled (that is, -t 2049). This creates a trace that provides both the SQL statement and the row counts, which are otherwise hard to match up.

Running script "script_file_spec"

This message confirms that the Client is running the specified script. For each SQL statement in the script, if the -v option is enabled, the Client writes the number of rows that have been changed to the log file. For details, see the preceding message.

Update of definitions of DataSets completed

This message indicates that the redefine command is complete. As a result, the DMSII layout that the corresponding relational database table layout information has been updated in the Client control tables. If the layout has changed, the scripts that the reorg command executes are written to the working directory for the data source. Additionally, the original control tables are saved in the unload file named source_reorg_nnn.cct, where source is the data source name and nnn is the original update level of the DMSII database. If the command fails because of a bad user script, you can reload the control tables from this file and re-execute the command after fixing the bad user script.

You must also run a generate command for DataSet name[/rectype] which is to be recloned

This message is a reminder that the table layout for the data set in question has changed and a generate command must be run before the data set can be recloned. Failure to do so will simply result in the process command failing. This message sometimes follows the message “WARNING: AA values for DataSet name[/rectype] are no longer valid, ds_mode set to 0 to force a re-clone”.

Generate Command Messages

The following messages appear in response to the Databridge Client generate command.

Beginning script generation

This message indicates that the scripts for creating, populating, and updating the Databridge data tables in the relational database are being created in the dbscripts subdirectory.

Creating scripts for 'tabname'

This message indicates that scripts for each table that will be stored in the relational database are being created. This status message appears one time for each DMSII data set you are cloning.

Generate command found nothing to do -- all scripts are current

This message indicates that the generate command did not find any data sets whose DS_Needs_Generating bit in the status_bits column of the DATASETS Client control table were set. The program suppresses unnecessary script generation to avoid overwriting any changes users might have made to these scripts. To disable this safeguard, use the -u option for the generate command; or from the Client console, select the Generate All Scripts command.

Loading control tables for datasource

This message indicates that the DMSII and relational database layout information is being loaded into memory from the Client control tables.

Script generation completed

This message indicates that the generate command is complete and that the necessary script files have been written to the dbscripts directory.

Reorg Command Messages

The following messages appear in response to the Databridge Client reorg command.

Clearing DataSet name[/rectype] records

This message indicates that the cleanup scripts is being run for the all the tables of the specified multisource data set.

Creating history table 'name'

This message indicates that a history table is being created because the configuration parameter enable_dynamic_hist is set to True.

Creating index 'name' for history table 'name'

This message indicates that the index for a dynamically-added history table is being created.

Creating index 'name' for table 'name'

This message indicates that the reorg command is creating the index for a table whose reorganization requires the index to be dropped and recreated.

Creating scripts for 'tabname'

This message is printed as a result of the reorg command executing a generate command before it does anything else.

Dataset name[/rectype] successfully reorganized

This message is printed after a data set is successfully reorganized. It is meant to show the progress of the command that might sometime take a very long time to complete.

DataSource name successfully reorganized

This message is printed at the end of a reorg command to indicate that the command completed successfully. It is mainly meant to provide some feedback when the command is executed from the Client Console.

Dropping index for table 'name'

This message indicates that the reorg command is dropping the index for a table whose reorganization requires the index to be dropped and recreated.

Loading control tables for datasource

This message indicates that the DATASETS table and relational database layout information is being loaded into memory from the client control tables.

Multisource DataSet name[/rectype] ds_mode is 35
The multisourced table has been dropped as there are no records left
Set ds_mode to 0 for all of the sources to reclone

These messages indicate that a multisource data set was dropped and that the other data source has also been dropped. When the reorganization of both data sources is complete, set the ds_mode to 0 to reclone it. See the next message for more details.

Multisource DataSet name[/rectype] ds_mode is 35
Set ds_mode to 0 when all sources have been reorganized

These messages indicate that a multisource data set was dropped and that the other data source must be reorganized before further action can occur. When the reorganization of that data source is complete, set the ds_mode to 0 to reclone it.

Multisourced data sources get their inputs from two structurally identical DMSII databases (same DASDL) that reside on different systems (for example, two different branches of the company, each with their own database). The data is stored in the same tables in the relational database, using the source_id columns in all the tables to keep track of where the records originated.

When reorganizing a multisourced data source, the changes must be completed in both data sources before you can alter the tables. The data source that is reorganized first is placed in a waiting state until the remaining data source is reorganized. If the reorg command determines that the table contains no records that come from any of the other multisourced data sources, it issues this message to indicate that it is time to reclone the table.

Reorganizing DataSet name[/rectype]

This message is printed to the log file when a data set whose mode is 31 is found. When the reorganization is completed, the message “Dataset name[/rectype] successfully reorganized“ is shown.