Define Command Messages

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

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

All garbage data successfully flushed

This message, which appears only if the -v option is enabled, indicates that the Client was able to read all of the false 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 appears only 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 appears only if the -v option is enabled, confirms that the Client is reading the specified text-based configuration file.

Beginning New DataSource definition

The data source with the host name and port number is being defined. Old entries in the control tables that correspond to the specified data source are deleted first.

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.

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

This message indicates that the Client is establishing a connection to the host. host is the name or IP address of the host. nnnn is the TCP/IP port number.

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 contains global data for the database, active column set to 0

The Client automatically disabled cloning for the indicated data set. Normally, the data in global data sets is not cloned because it is not very useful. name is the name of the data set containing global data.

DataSet name1[/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. 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 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 dbutility define command is complete and that the DATASOURCES client control table now contains the data source name, host name, and port number. It also indicates that the DMSII layout information has been downloaded into the control tables and that the corresponding relational database table layout information has been created.

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 provides the database update level, the database update timestamp, and the highest structure number in the database for the data source being accessed. The second line gives the database timestamp and the database name for the data source being accessed. The third line, which only appears when there is something to report, indicates whether the INDEPENDENTTRANS is set for the DMSII database (ITRANS) and if 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 the 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 DBServer 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). 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.

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" in the appendix of the DATABridge Client Administrator's Guide.

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

Inserting data into control tables...

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

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 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 level that the Client and the server use (the lesser of the client and server protocol levels). The second part of the message contains the major and minor version numbers of the server (for example, 6.1).

Oracle version: major_vers.minor_vers

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

Retrying ATMEcho RPC after flushing input

This message, which only appears if the -v option is enabled, indicates that the Client received a response of the wrong length from DBServer and is retrying the ATM_Echo API call.

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 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, the log records the number of rows in the control tables that have been changed. See the preceding message, "Rows updated = ccc", for more information.

Server communications initialization complete

This message, which only appears if the -v option is enabled, indicates that DBServer 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 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).