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.

All garbage data successfully flushed

This message, which only appears if the -v option is enabled, indicates that the Client was able to read the faulty TCP data after receiving an incorrect length response to the test pattern. This message always follows the message "Flushing garbage data". You should not see this message under normal circumstances.

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

This message, which only appears if the -v option is enabled, indicates that the client and server were able to exchange the given test patterns using the ATM_Echo RPC. If the patterns do not match, the client attempts to recover from this situation by flushing any data that is stuck in the TCP output queue on the host.

Begin processing configuration file "name"

This message, which only appears if the -v option is enabled, confirms that the Client is reading the specified text-based configuration file.

Beginning updates of DataSource definitions

This message indicates that the data source definitions are being redefined. Old client control table entries that correspond to data sets which need to be redefined (for the specified data source) are deleted first.

Client exit code: dddd[(nnn)] - exit_code_text

This message displays when the command completes. On UNIX, the 8-bit exit code is shown only if it differs from the actual exit code.

Configuration information read from binary file "name"

This message, which only appears if the -v option is enabled, confirms that the Client has successfully read the specified binary configuration file.

Connected to host, port nnnn

This message, which only appears if the -v option is enabled, indicates that the Client has successfully established a connection to the port on the host. host is the name or IP address of the host. nnnn is the TCP/IP port number.

Connecting to host, port nnnn

where host is the name or IP address of the host, and nnnn is the TCP/IP port number. This message indicates that the DATABridge Client is trying to establish a connection to the specified port.

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.

DataSet name contains global data for the database, active column set to 0

This message indicates that the Client automatically disabled cloning for the indicated data set. Normally, the data in global data sets is not cloned because it's not very useful.

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 configuration file parameter suppress_new_datasets parameter 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 configuration file 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] is a remap of DataSet name2[/rectype], active column set to 0

The term remap is a DMSII term that is roughly equivalent to the term view in a relational database term. In DMSII, a data set can have one or more remaps. The original data set is referred to as the base structure. It is also possible to have a remap for a variable-format data set. Note that /rectype only appears for variable-format data set records that have a nonzero record type (that is, contain a variable part). By default, the Client only clones the base data set and sets the active column to 0 for all remaps.

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 if the -v option is enabled, indicates that the specified data set will be redefined

DB_Info: database_ts = timestamp, database_name = name

This message, which is only written to the log file, shows the database timestamp and the database name for the data source being accessed.

DB_Info: update_level = ddd, update_ts = timestamp, highest_strnum = ddd

This message, which is only written to the log file, shows the database update level, the database update timestamp and the highest structure number in the database for the data source being accessed.

DB_Info: update_level = ddd, update_ts = timestamp, highest_strnum = ddd

DB_Info: database_ts = timestamp, database_name = name

[DB_Info: OptionFlags={[ITRANS], [DBI_FLATFILE]}]

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 data source 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, which only appears when there is something to report, indicates whether or not INDEPENDENTTRANS is set for the DMSII database (ITRANS) and whether or not the data source is a FileExtract file (DBI_FLATFILE).

DBEngine Version: version_string

This message, which is only written to the log file, shows the version of DATABridge Engine being used on the mainframe.

DBEnterprise Version: version_string

This message, which is only written to the log file when using DATABridge Enterprise Server, shows the version of Enterprise Server.

DBServer Version: version_string

This message, which is only written to the log file, shows the version of Server Accessory being used on the mainframe.

DBSupport Version: version_string

This message, which is only written to the log file, shows the version of the DATABridge Support Library being used on the mainframe.

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.

Disconnecting and restarting transport initialization

This message, which only appears if the -v option is enabled, indicates that the response to the ATM_Echo API call timed out. The Client recovers from this error by disconnecting from the server and trying to restart the connection process (up to three times). In some cases, this error occurs because the timeout value is too low for a busy mainframe. If that is the case, increase the value of the configuration parameter echo_rpc_timeout. See "shutdown" in Server Option Parameters.

End processing configuration file "name"

This message, which only appears if the -v option is enabled, confirms that the Client has processed the specified text-based configuration file.

Flushing garbage data

This message only appears if the -v option is enabled. The Client exchanges a test pattern with the Server Accessory to verify that the transport layer works correctly. This message indicates that Client did not get a response that had the right length or an incorrect pattern, and it attempted to recover from this situation. You should not see this message under normal circumstances

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 only appears if the -v option is enabled, indicates that the DMSII layout for the data set in question is being mapped to the corresponding relational database tables.

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

This message, which is only written to the log file, shows the protocol that the client and the server will be using. This value is the lesser of the client protocol and the server protocol levels. The second part of the message contains the major and minor version numbers of the server (for example, 6.1).

No Further Action Required - Processing can continue

This message is a confirmation that the redefine command did not detect any layout changes and you can resume processing audit files.

Oracle version: major_vers.minor_vers

This message, which is only written to the log file when using Oracle client, shows the Oracle version.

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 - to remove it run the script 'script.drop.tabname'

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 suppress_new_column_parameter 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), 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 the 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 the 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 the DMSII reorganization, the specified column was added to the specified table. If the suppress_new_column_parameter is set to True, the Client sets the active column of this entry (in DATAITEMS) to 0. If the suppress_new_column_parameter 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 the 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 data, which is a key, has been encountered when the configuration file parameter use_nullable_dates parameter 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 use_dbconfig parameter.

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 when the -v option is enabled, 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 when the -v option is enabled, 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.

Retrying ATMEcho RPC after flushing input

This message, which only appears if the -v option is enabled, indicates that the Client is testing the Server Accessory response after an unsuccessful attempt. The Client retries the ATM_Echo API call once after receiving a response that is the wrong length.

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, the log records the number of rows in the control tables that have been changed. For details, see the preceding message.

Server communications initialization complete

This message, which only appears if the -v option is enabled, indicates that the Server Accessory or Enterprise Server has successfully executed the DBINITIALIZE API call.

SQL Server version: major_vers.minor_vers

This message, which is only written to the log file when using the Microsoft SQL Server client, shows the SQL Server version. Note that SQL Server 2000 is version 8, SQL Server 2005 is version 9, SQL Server 2008 is version 10, and SQL Server 2008 R2 is version 10.5.

System: host_system_desc

This message, which is only written to the log file, shows information about the type of Unisys mainframe being used (for example, System: LX7000:1631 SSR 53.189.8432).

Update of definitions of DataSets completed

The definitions for the data sets have been updated.

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

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”.