Process and Clone Commands Messages

The following messages appear in response to the DATABridge Client process and the dbutility clone commands.

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

Attempting to clear duplicate records for table 'name'

This message indicates that following the failure to successfully create an index for a table during the data extraction phase, the program will attempt to run the script "script.clduprecs.tablename" to remove duplicate records from the table. This situation can occur if the DATABridge Engine sees the same record twice during data extraction. This is much more likely in the case of compact data sets where records can move around in the data set when their sizes change.

Aux STMT Statistics:

Configured_max = nnn, Max_used = mmm, Recycled_stmt_cnt = rrr

STMT reuse stats: min_sql_ops = nnn, max_sql_ops = mmm, avg_sql_ops = rrr.rr

STMTs never reused = nnn, min_sql_ops = mmm, max_sql_ops = ddd, avg_sql_ops = rrr.rr

This message shows the statistics for the auxiliary statement used by the Client.

In the first line, the value nnn represents the value of the aux_stmts parameter in the client configuration file. The value mmm indicates that maximum number of statements that were used.

The first line shows nnn, the value of the aux_stmts parameter in the client configuration file, and mmm, the maximum number of statements that were used. The recycled statement count, rrr, indicates how many statements were reused. If the rrr value is high (or if the nnn and mmm values are the same) you may not have enough statements configured. If you change these values, keep in mind that higher values can result in better performance but will require more memory.

The second line represents the number of SQL statements that were executed using a given auxiliary statement. The minimum, maximum and average values are shown. The minimum value is typically 1, if you have tables that a very rarely updated. A high value for the maximum is encouraging, but it can be misleading if you have a small number of tables that get updated a lot. If the average value is high, this indicates that you have enough auxiliary statements. Any statement that is reused will run much faster than one that executes for the first time, as the first execution requires additional I/O. This is particularly visible in the Oracle client, where the speed up is quite visible.

The third line represents the minimum, maximum, and average number of SQL operations that were executed by these SQL statements and the number of SQL statements that have not been reused. If this number is close to the number of configured auxiliary statements, you might benefit from increasing the value of the parameter aux_stmts. This would allow more SQL operations to re-use statements, thereby improving performance.

Begin populating/updating database [from AFN = afn, ABSN = absn, Seg = seg,
INX = inx, DMSII Time timestamp]

This message appears at the start of the dbutility process or clone commands after all the data sets have been successfully selected. The absence of any audit file information indicates that all of the selected data sets need to be cloned and that the DATABridge data tables have been successfully created. The audit file location information indicates that a process command has found at least one data set ready to receive DMSII updates.

Important: If the Client stops processing after this message, see the issue that corresponds to this message in Troubleshooting Table.

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.

Bulk load count verification for table 'name' complete: number rows

This message only appears when the configuration parameter verify_bulk_load is set to 1 or 2 and the number of records from the table (from the relational database) is equal to the number of loaded records.

Bulk_loader thread no longer hung, main thread resuming

(Windows only) The bulk loader thread, which had fallen so far behind the main thread that it caused the main thread to block, has caught up and allowed the main thread to unblock and start running again. If this situation occurs again, you must investigate why the bulk loader is running so slowly. If you are using a remote connection over Oracle, try increasing sql_bindsize to 1 MB.

Bulk_loader thread {started | ready | exiting}

(Windows only) These messages, which only displays if the -v option is enabled, indicate the state the of the bulk loader thread.

started indicates that the thread was started. The thread is only started when there are tables to be bulk loaded.

ready indicates that the thread is ready to process requests to run the bulk loader. The bulk loader thread gets the load request from its work queue. If there is none, it blocks until one becomes available.

existing indicates that the thread is no longer needed and is exiting. At this point, the Client is ready to start processing audit files as soon as the index thread finishes creating indexes for all of the tables that were cloned.

Bulk_load_initiator thread ready

(Windows only) The bulk loader thread is about to start processing the next load request in its work queue. If there is none, it blocks until one becomes available. This message only appears if the -v option is enabled.

Bulk_load_initiator thread started

(Windows only) This message, which only appears if the -v option is enabled, indicates that the bulk loader thread was created successfully and has started executing. The "Bulk_load_initiator thread ready" message always appears after this message.

Bulk_load_time = sss.sss secs, (dd.dd% of total time)

(Windows only) This message appears at the end of the data extraction phase only if the configuration file parametershow_perf_stats is enabled. It indicates the amount of time that the main thread spent waiting for the bulk loader operations. When spawn_bulk_load is enabled, sss.sss is the amount of time in seconds that the main thread spent waiting on resources tied up by the bulk loader thread and dd.dd is the corresponding percentage of total elapsed time. If spawn_bulk_load is not enabled, the time represents the actual time spent waiting for the bulk loader operations to complete.

Bytes Received nnn.nn KB in sss.sss secs, total throughput = ddd.dd KB/secs

This message appears at the end of the data extraction phase, at the beginning of the fixup phase, and after every audit file switch if the configuration file parameter show_perf_stats is enabled. nnn.nn represents the number of kilobytes received. sss.sss represents the elapsed time (in seconds). ddd.dd represents the corresponding throughput. Bytes received includes all TCP/IP data received from the server.

Cleaning up table 'name' [fully]

This message indicates that the Client is deleting selective records from the specified table and recreating it at the beginning of the data extraction phase instead of dropping the table. This action is taken only in special cases, such as when deleted records are preserved. Another case is when a table that gets its input from more than one data set is partially recloned. The presence of the word "fully" indicates that the script "script.cleanup2.table" is being run, as opposed to the script "script.cleanup.table".

Clear duplicate records script ran successfully

This message confirms that the script "script.clrduprecs.tablename" was successfully run. The purpose of this script is to delete records that appear multiple times in the table. The fixup process will reinsert the correct copy of these records. This situation is rare, but tends to happen when compact data sets are involved.

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.

Clone of selected DataSets completed

This message indicates that the clone command for the specified data sets completed successfully.

Closing file "bcppipe.name[_number]"

This message, which applies only to SQL Server and appears only if the -v option is enabled, indicates that the specified temporary file has been successfully closed prior to being queued for bulk loading.

Closing file "lpipe_number[_number].dat"

This message, which applies only to Oracle and appears only if the -v option is enabled, indicates that the specified temporary file has been successfully closed prior to being queued for bulk loading.

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 and 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 and nnnn is the TCP/IP port number.

Console Input: 'text'

This message, which only appears in the log file, contains the console command text as entered by the operator. The Client logs all console commands issued by the operator, ensuring a record of all such commands.

Console RPC: {Quit | Quit At hhmmss | Quit After AFN dddd | Quit Now | Get_Server_Stats | Switch_Log_File | Switch_Trace_File | Set_Parameter (param, val) | Trace_options set to 0xhhhh | verbose flag set to (true | false} | Get_Parameter (param, val) }

These messages, which are only applicable to DBClient, are only written to the log file. They provide a log of the console command RPCs that were received by the Client.

Console_Reader thread {starting | ready | issuing Get_IPC_Request() call | exiting }

These messages, which only appears if the -v option is enabled, indicate a state change in the Console thread. The command line Client uses this thread to read console input commands from the keyboard. The service-based Client (DBClient) uses this thread to handle console commands that originate in the GUI Console and are passed to the Client as RPCs. The various states indicate the following:

starting indicates that the thread was successfully started.

ready applies only to dbutility and indicates that the thread is waiting for keyboard input.

issuing Get_IPC_Request() call applies only to DBClient. It indicates that the thread is waiting for the next Console command (RPC).

exiting means that the thread is about to exit.

Creating index 'name' for table 'name'

This message shows the progress of the data set being cloned and indicates that the Client is creating an index for the specified table.

Creating stored procedure for control table 'name'

The Client uses host variables to speed up the updates to the client control tables. Such updates are done by stored procedures called U_tablename, where tablename is the name of the client control table. If this procedure does not exist, the Client creates it and then appears s this message.

Creating table 'name'

This message shows the progress of the data set being cloned. Indicates that the specified table is being created in the relational database.

Creating temp file "name" for table 'name'

(Windows only) This message shows the progress of the clone during the data extraction phase. Indicates that dbutility is creating a temporary file named bcppipe.name or lpipe_tablenumber.dat.

Cumulative Statistics:

This message contains statistics for the entire run (compared to incremental statistics, which apply only to the data extraction phase of each individual audit file processed). This message is written to the log file at the end of the run. For a description of each field, see "Incremental Statistics" in this section.

Data Errors: dddddd SQL rows discarded, dddddd SQL rows in error

This message is printed at the end of incremental and cumulative statistics when one or more of the processed records had data errors or were discarded. This message only appears when the show_perf_stats parameter is set to True.

Data Extracted nnn.nn KB in sss.sss secs, throughput = ddd.dd KB/sec

This messages appears at the end of the data extraction phase if the configuration file parameter show_perf_stats is enabled. nnn.nn represents the number of kilobytes of DMSII data received. sss.sss represents the elapsed time (in seconds). ddd.dd represents the corresponding throughput. This message is always followed by the message "Bytes Received nnn.nn KB in sss.sss secs, total throughput = ddd.dd KB/sec," which shows the total data throughput rather than the actual DMSII data throughput.

Data Extraction Phase 1 Statistics:

This message precedes a list of statistics that are printed to the log file at the end of the first phase of the data extraction, provided the following is true:

  • Virtual data sets that get their input from more than one data set are involved
  • The automate_virtuals parameter is set to True

Data extraction phase for table 'name' complete, num DMSII records processed, num SQL rows loaded [,num rows in error][num rows discarded]

Indicates that the data extraction phase for the specified table is complete. It also reports the DMSII record count, the corresponding number of rows that were loaded into the relational database, the count of records that had data errors, and the discarded records, which are placed into the program discard files (tablename.bad).

Data Extraction Statistics:

This message precedes a list of data extraction statistics that are printed to the log file.

Database clone/update completed

This message appears when you run dbutility process and the clone or update completes successfully. This message can also appear when the DATABridge Engine has successfully read the available audit files but there was no updated data to pass on to the Client.

DataSet name[/rectype] will be cloned

This message, which applies to the clone command, indicates that the specified data set will be cloned. /rectype only appears for variable-format data set records that have a nonzero record type (contains a variable part). See Variable-Format Data Sets.

DataSets purged by DBEngine

This message appears when the DATABridge Engine sends the Client a status indication that one or more data sets have been initialized (emptied). This message is preceded by one or more of the following messages that occur during the purging of a data set: "Dropping tablename"; "Creating tablename"; and "Creating index name for tablename". The last message won't appear if the configuration file parameter auto_reclone is enabled.

DBServer = task#/mix# title

This message indicates that communication to the Server Accessory is established. It supplies the task number and mix number of the Server Accessory job and the title of the Server Accessory program. An example of the file title is (USERCODE)OBJECT/DATABRIDGE/SERVER ON DBASE. This message is only printed in the log file.

Deleting file "name"

(Windows only) The specified file is being deleted. Instead of initiating the bulk loader, the temporary data files are deleted since the -z option implies that the database cannot be updated. This message only appears if you use the -z option.

DMSII data: offset = dddd (0xhhh), len = dd half bytes 0000 xx xx ...

This message appears after a data error warning if the parameter display_bad_data is enabled. These errors contain bad digits in numeric data and control characters or 8-bit characters in ALPHA data. xx xx represent the DMSII values of the data bytes that make up this field.

End fixup phase for cloned DataSets

This message indicates that the fixup phase for the cloned data sets is ending. At this point, all tables in the relational database that are mapped from active data sets are synchronized.

End populating/updating database at AFN = afn, ABSN = absn, SEG = seg, INX = inx, DMSII Time = timestamp

The process or clone command ends at the audit file location that corresponds to the given AFN, ABSN, SEG, INX, and DMSII timestamp values. The next process command starts at this point.

End processing configuration file "name"

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

File_I/O_time = sss.sss secs, (dd.dd% of total time)

This message appears at the end of the data extraction phase if the configuration file parameter show_perf_stats is enabled. It indicates the amount of time that the main thread spent waiting for file I/O operations to complete. For Windows, this represents the I/O writing the temporary files. For UNIX, it represents the amount of time spent writing to the UNIX pipes. These times also include any blocking time when the bulk loader falls behind the main process. In all cases, sss.sss is the amount of time (in seconds) the program spent waiting on file I/O operations to complete. dd.dd is the corresponding percentage of total elapsed time.

Incremental Statistics:

This message contains a set of incremental statistics, which apply only to the data extraction phase of each individual audit file processed.

Processed nnn.nn KB in sss.sss secs, throughput = ddd.dd KB/sec, lag time = hh:mm:ss

nnn.nn represents the number of kilobytes of DMSII data received. sss.sss represents the elapsed time in seconds. ddd.dd represents the corresponding throughput.

Received nnn.nn KB from DBServer in sss.sss secs, total throughput = ddd.dd KB/sec

nnn.nn represents the number of kilobytes of total data received (including the packet headers and the non-data packets). sss.sss represents the elapsed time in seconds. ddd.dd represents the corresponding throughput.

DMSII Buffers Used = dd (configured_max = mm), Audit access rpc = {DBRead | DBWait}, Audit file origin = AF_origin

dd is the actual number of DMSII buffers used and mm is the configured maximum. If the configured value is 0, the maximum value is computed by the program. The rest of the line indicates whether DBRead or DBWait was used to get updates from the DATABridge Engine and the method by which the audit file is being read. The possible values for AF_origin are HostAudit, DBTanker, DirectDisk, IndirectDisk, and DBECache (the last three apply to Enterprise Server).

TCP/IP_time = sss.sss secs, (dd.dd% of total time)

sss.sss represents the amount of time (in seconds) that the program spent waiting for TCP/IP data to appear from the host. dd.dd is the corresponding percentage of total elapsed time.

SQL_exec_time = sss.sss secs, (dd.dd% of total time)

sss.sss is the amount of time (in seconds) that the main thread of the program spent waiting for the execution SQL statements to complete. dd.dd is the corresponding percentage of total elapsed time.

TXN_exec_time = sss.sss secs, (dd.dd% of total time)

sss.sss represents the amount of time (in seconds) the main thread of the program spent waiting for commits to complete. dd.dd is the corresponding percentage of total elapsed time.

[buf_wait_time sss.sss secs, (dd.dd % of total time)

This line only applies to multi-threaded updates. sss.sss represents the amount of time (in seconds) the main thread of the program spent waiting for a DMSII buffer to become available. dd.dd is the corresponding percentage of total elapsed time.

ws_wait_time sss.sss secs, (dd.dd % of total time)

This line only applies to multi-threaded updates. sss.sss represents the amount of time (in seconds) that the main thread of the program spent waiting for a DMSII buffer to become available. dd.dd is the corresponding percentage of total elapsed time.

thr_wait_time sss.sss secs, (dd.dd % of total time)]

This line only applies to multi-threaded updates. sss.sss represents the amount of time in seconds that the main thread of the program spent waiting for the updater threads to finish processing updates.

Server_Packet_Counts:

CREATE:ddd DELETE:ddd MODIFY:ddd MOD_BI:ddd MOD_AI:ddd STATE:ddd
LINK_BI:ddd LINK_BI:ddd COMMIT:ddd DOC:ddd COMMIT:ddd ROLLBK:ddd

These values represent the counts of the various record types and commits received from the DATABridge Server. CREATE represents insertions into the database and records extracted during the data extraction phase. DELETE and MODIFY represent delete and update operations during audit file processing. MOD_BI and MOD_AI represent updates that are before and after image records for updates. STATE represents StateInfo records. LINK_BI and LINK_AI represents before and after images of link items. COMMIT represents commits. ROLLBK represents rollbacks. DOC represents documentation records.

Server_Rolledback_Packet_Counts:

CREATE:ddd DELETE:ddd MODIFY:ddd MOD_BI:ddd MOD_AI:ddd STATE:ddd

LINK_BI:ddd LINK_BI:ddd COMMIT:ddd DOC:ddd

These values represent the counts of the various record types that were rolled back. This message is only written to the log file to avoid cluttering the screen.

Processed: dddd bytes of before image data, rrrr redundant SQL updates skipped

This line only appears when using the optimize_updates feature. dddd represents the number of bytes of DMSII before image data received (the cause) and rrrr represents the number of redundant SQL updates that were eliminated (the effect). A low value of rrrr and a high value of dddd is a clear indication that the optimize_updates feature is not helpful in this case.

Data Errors: eeeeee SQL rows discarded, dddddd SQL rows in error

If there are data errors or discard records, this line is printed to show the number of records that had data errors or were discarded.

Index_creator thread {started | ready | exiting}

These messages, which only display when the ‑v option is enabled, indicate the state of the index creator thread.

started indicates that the thread was started because there are tables for which indexes must be created.

ready indicates that the thread is ready to process requests to create indexes for tables. The index creator thread gets the index creation request from its work queue. If there is none, it blocks until one becomes available.

exiting indicates that the thread is no longer needed and is exiting. At this point, the Client is ready to start processing audit files.

Initializing tables for DataSet name[/rectype]

This message, which only appears if the -v option is enabled, specifies the data sets that are being selected at the beginning of a process or clone command. It gives you a chance to ensure that you have selected the data sets you intended to select.

Initiating process command for DataSource name

This message indicates that a scheduled dbutility process command (via the scheduling parameters in the dbridge.cfg file) is about to begin.

Key change detected in MODIFY for DataSet name[/rectype], handling it as a DELETE/INSERT instead

This message, which only appears if the -v option is enabled, indicates that the Client detected a change in the value of one or more key_items. To resolve this situation, the Client deletes the before‑image and inserts the after‑image into the relational database. This message only appears when using the DATABridge Engine 6.0 or earlier. When using DATABridge Engine 6.1 or later, the DATABridge Engine handles this situation by sending the updates to the client as MODIFY records when the keys are not changed or as MODIFY BI/AI pairs when the keys change. For information about the DSOPT_CheckKeyChanges bit in "ds_options" and check_key_changes, see DATASETS Client Control Table.

Loading control tables for datasource

This message indicates that the client control tables are being loaded for the data source you specified with the process or clone command.

Log file switched to "filename" (reason)

This message appears under the following conditions, which cause the Client to close the current log file and open a new one:

  • The logsw_on_size configuration file option is selected and file size exceeds the configured maximum during an audit file switch.
  • The logsw_on_newday configuration file option is selected and the Client notices that the date has changed.

Mainframe Time 'hh:mi:ss'; {ahead | behind} by hh:mi:ss

This message, which appears at the start of a process command, shows the time difference between the mainframe and the DATABridge server system clocks. This value is factored in to all lag time calculations.

MODIFY occurs depending on, item = 'name', bi_count = ddd, ai_count = nnn

- Keys: columnname = value,...

This message, which only appears if the -v option is enabled, shows the old and new values of the depends item for an OCCURS DEPENDING ON clause. The values determine how the update is handled when the OCCURS is not flattened.

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 use (that is, the lesser of the Client and server protocol levels). The host version value is the major and minor version numbers of the server (for example, 6.1).

Next update for DataSource name will run at hh:mm (delay = nn secs)

This message appears only when you have configured the scheduling parameters for dbutility in the configuration file. It tells you when to expect the process command to run again. hh:mm corresponds to the daily parameter and nn represents the length of this delay (in seconds). See Scheduling dbutility Updates.

Optimized update failure initiated rollback starting

This message, which only applies when using multi-threaded updates, indicates that an update failed and the client did a rollback to recover from this situation.

Oracle version: major_vers.minor_vers

This message, which applies only to Oracle and appears only in the log file, shows the Oracle version.

Processed: nnnn DMS recs, rrrr SQL rows [;DataSet = name (str_index)]

This message appears if the display_statistics parameter or the -v option is enabled. This message is useful when you are not sure if the client is running or if it has stopped operating, especially when the cloning requires several hours. When the command finishes, an additional message that has no data set specification is displayed to show the final counts. The data set information of this message is not included during the processing of fixups and updates, as this information is meaningless.

Processed: nnnn DMS recs, rrrr SQL rows[, bbbb SQL rows rolled back]

This message contains the count of SQL updates that were rolled back when this count is non-zero. For more information, see the preceding message.

Processing updates from: AFN = afn, ABSN = absn, SEG = seg, INX = inx, DMSII Time timestamp

This message appears before the incremental statistics, which are displayed when the client encounters the first quiet point in a new audit file. This message indicates that the Client is processing updates from the specified AFN, ABSN, SEG, INX, and DMSII time stamp.

Queue_DMS_Response: table='name', work_desc=0xnnnnnnnnn, ws_desc_pool=dd, work_desc_sem=dd (work_desc)

This message, which is limited to multi-threaded updates and only appears if the -v option is enabled, indicates that an update was queued for the specified table. The message provides the address of the work descriptor block used. It also shows some internal counts, which are only useful in chasing potential deadlocks that might occur if the system runs out resources.

Redundant update for table 'name'; Keys: columnname = value,...

This message only appears when the following conditions are met: the -v option is enabled; the configuration file parameter optimize_updates is set to true; and the data set has been marked to receive before- and after-images. The message indicates that the program found a redundant update for the record with the specified keys in the given table.

ReleaseSemaphore for name reached maximum value, retrying after brief delay

(Windows only) This message, which only appears if the -v option is enabled, indicates that the Client has exceeded the maximum posting limit for the work queue by attempting to post too many requests to the bulk loader or index threads. The Client will stall until the index threads catch up to the requests. This message should appear only when you have attempted to clone a large number of empty data sets.

Restarting fixup phase for previously cloned DataSets

This message appears at the start of a process command (after the message "Begin populating/updating database from AFN = afn, ABSN = absn, ...") if there are data sets in fixup mode (ds_mode = 1) and no data sets need to be cloned (ds_mode = 0).

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 following the receipt of a response that is the wrong length.

Running script "script_file_spec"

This message appears only when a data table creation user script or an index creation user script is run.

Running user defined stored procedure 'm_tabname'; Keys: columnname = value, ...

This message, which only appears if the -v option is enabled, is specific to MISER databases. The program is handling an insert by calling the stored procedure m_tablename instead of the procedure i_tablename. The DTOPT_UserSP bit in the dt_options column of the DATATABLES client control table controls this action.

Server communications initialization complete

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

SQL Server version: major_vers.minor_vers

This message, which contains the SQL Server version information, applies only to the Microsoft SQL Server client and is only written to the log file. 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.

Starting bcp for table 'name'

This message, applies only to the Microsoft SQL Server client and is only written to the log file. This message helps to determine the amounts of time that are spent writing temporary files during the data extraction phase and running bcp.

Starting command: "filename"

(UNIX only) The given shell script that runs the bulk loader is being started. The shell script (load.tablename.sh) runs the bulk loader and establishes a named pipe used to communicate data between the main process and the bulk loader process that is spawned from the script.

Starting fixup phase for cloned DataSets

This message indicates that the Client has finished extracting data and is starting the fixup phase for the cloned data sets.

Starting sql*loader for table 'name'

(Windows only) This message, which only applies to the Oracle client is only written to the log file, indicates that the SQL*Loader process is beginning for the specified table.

Starting update statistics for table 'name'

This message, which applies only to the SQL Server client, indicates that the program is executing an “update statistics tablename” command following the creation of an index for the table in question.

Stopping: All available audit information has been processed (status)

This message indicates either that no more audit file information is available on the host (that is, a normal stopping point) or that audit files are available, but there are no updates.

Note: If the DATABridge Engine finds updates but reaches the end of the audit file before a commit, the Client rolls back the updates. The discarded updates are included when the next audit file or quiet point becomes available.

The status received from the Server Accessory is one of the following:

  • AUD_UNAVAIL indicates a normal exit.
  • LIMIT_NAME indicates that the run stopped because the DATABridge Engine encountered a task name that satisfied the stop condition. This condition can be specified using a STOP statement in the Server Accessory parameter file or the Client configuration file.
  • LIMIT_TIME indicates that the run stopped because the DATABridge Engine is processing an audit file record whose time stamp satisfies the stop condition. This condition can be specified using a STOP statement in the Server Accessory parameter file or the Client configuration file.

Stopping: Audit information not available (status)

For an explanation of statuses, see the preceding message. This message occurs when no audit files on the host have been read by the DATABridge Engine. This can indicate that no audit files are available (that is, no audit file is closed) or that the DATABridge Engine does not have visibility to the audit files. In this case, try again when an audit file is closed. Typically if READ ACTIVE audit is set to FALSE in the Engine Control file, you will get this message when if the client tries to open the active audit when it starts.

Stopping: Client operations inhibited between hh:mm and hh:mm

This message indicates that the Client stopped the processing of audit files because it is entering a blackout period defined by the configuration file parameter blackout_period in the scheduling section.

In the case of dbutility, this message also applies to a blackout period defined using the stop_time and end_stop_time columns in the DATASOURCES table entry for the data source. To use this feature, which can be associated with the shutdown parameter, set the configuration parameter controlled_execution to True.

Stopping: Database reorganization – execute a redefine command followed by a reorg command

This message appears when you run a process command, and the DATABridge Engine detects a DMSII structural reorganization of filler substitution that occurred. See Reorganizations, Filler Substitutions, and Initializations.

Note: You must execute a redefine command followed by a reorg command, as explained in Recovering after a DMSII Reorganization.

Stopping: Database update level changed -- execute a redefine command

This message appears when you run a process command and the DATABridge Engine detects a DMSII structural reorganization that does not affect any of the selected data sets. In this situation, the client will stop only if:

  • The configuration parameter redef_all_active_ds is set to True.
  • There are added data sets and the configuration parameter suppress_new_datasets is set to False.

In all other cases, the client ignores this situation and continues processing audit file after displaying the warning “Database update level change ignored”.

Stopping: Errors occurred during data extraction [and index_creation]

This message appears before the fixup phase if discard files were created and (if the last part of the message is present) index creation errors occurred. Instead of entering the fixup phase, the program stops and gives you a chance to look into the problem before continuing.

Stopping: Errors occurred during index creation

This message appears before the fixup phase if index creation errors occurred. Instead of entering the fixup phase the program stops and gives you a chance to look into the problem before continuing.

Stopping: Garbage collection reorganization has occurred

This message indicates that the processing of updates is being interrupted. This message appears at the first quiet point after a garbage collection reorganization if the stop_after_gc_reorg parameter is enabled.

Stopping: Operator issued a "quit" command

This message indicates that a QUIT command was issued for the Client or that a SIGTERM signal was issued for dbutility in UNIX using a kill command.

Stopping: Processing of fixup records deferred to next process command

This message appears when the program typically enters the fixup phase if the configuration parameter defer_fixup_phase is enabled (the -c option toggles this command). Instead of entering the fixup phase, the program stops. This procedure is useful when using parallel cloning.

Stopping: Processing of updates deferred to next process command

This message, which appears at the end of the fixup phase if the stop_after_fixups parameter is enabled, indicates that updates will be processed at the next process command.

Stopping: Processing through requested AFN completed

This message appears when the value of an audit file goes past the audit file stored in the stop_afn column of the DATASOURCES Client control table. This message only appears if the configuration parameter stop_after_given_afn is enabled. The program resets this column to zero before stopping, thus removing the stopping condition.

System: host_system_desc

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

Thread[nn]:

SQL_time = sss secs, (nn.nn% of total time), update_cnt = dddd

Idle_time = sss secs, (nn.nn% of total time)

This message, which only appears when multi-threaded updates are enabled, is included in the incremental and cumulative statistics (after thr_wait_time). There is one message for each update thread, where nn is the thread number (1 to 16).

In the line SQL_exec_time, sss.sss is the amount of time (in seconds) that the thread spent waiting for the execution SQL statements to complete. dd.dd is the corresponding percentage of total elapsed time.

In the line Idle_time, sss.sss represents the amount of time (in seconds) that the thread spent waiting for work. dd.dd is the corresponding percentage of total elapsed time

TranCommit, AFN = afn, ABSN = absn, SEG = seg, INX = inx, DMSII Time = timestamp

This message, which only appears if the -v option is enabled, indicates that the last group of SQL statements were committed on the relational database, along with the DMSII time and the ending audit file stateinfo.

Transaction group aborted by DBEngine, nnn operations rolled back

This message appears when the DATABridge Engine sends the Client an abort status (instead of a commit status). The DATABridge Engine rolls back the current transaction group and reapplies some of the updates when a program on the mainframe aborts a transaction.

Update Worker thread[nn] running, DataTable = name, ws = 0xnnnnnnnn

This message, which only appears if the -v option is enabled, indicates that the specified update worker is performing an update for the given table. This message shows the address of the work descriptor storage block that is used to queue the request. This information is only useful if you are diagnosing a problem that deals with the management of work descriptor storage blocks.

Update Worker thread[nn] {started | ready | exiting}

These messages, which only appears if the -v option is enabled, show the state changes in the update threads.

started indicates that the thread was started. The update threads are started at the start of the process command.

ready indicates that the thread is ready to process requests to execute updates. The update worker threads get the update requests from their work queue. If there is no request in the queue, the thread blocks until one becomes available.

exiting indicates that the thread is no longer needed and that it is exiting. This only happens when the client is shutting down.

Updates by table:

name updates name updates name updates

This message, which is only written to the log file when the show_table_stats parameter is set to True, shows the number of updates for each table. Tables that have no updates are omitted from this list.

Updating links of table 'name', AA_value = hex_value

This message, which only appears if the -v option is enabled, indicates that one or more links of the record with the given AA_value are being updated. Link updates appear as separate records from the update records, which only affect the data.

Updating res_flag for item in table 'name'; Keys: columnname = value, ...

This message, which is specific to MISER databases, only appears when the -v option is enabled. It indicates that the Client is handling an insert for a MISER history table by calling the stored procedure r_tablename instead of the procedure i_ tablename. The DSOPT_MultiInput bit in the ds_options column of the DATASETS Client control table controls this action.

Updating table 'name' for {create | delete | modify}; Keys: columnname = value,...

These messages, which only appears if the -v option is enabled, show the progress during dbutility process or dbutility clone operations when processing updates.

Create indicates that this table is being updated with records that were added to the DMSII database.

Delete indicates that the records that were deleted from the DMSII data set are being deleted from the corresponding DATABridge data table.

Modify indicates that this table is being updated with records that were changed in the DMSII database.

Waiting for bulk_loader thread to finish

(Windows only) This message, which only appears if the -v option is enabled, indicates that the bulk_loader thread is not finished loading tables. The main thread, which is ready to enter the fixup phase, must wait for these operations to complete before updates can be processed. When the bulk loader thread is finished it displays the message "Bulk_loader thread exiting."

Waiting for index_creator thread to finish

(Windows only) This message, which only appears if the -v option is enabled, indicates that the index_creator thread is not finished. The main thread, which is ready to enter the fixup phase, must wait for these operations to complete before updates can be processed. When the index creator thread is finished, it displays the message "Index_creator thread exiting."

Waiting for index_process to finish

(UNIX only) This message, which only appears if the -v option is enabled, indicates that the index_creator process is not finished creating all the indexes. The main process, which is ready to enter the fixup phase, must wait for these operations to complete before the processing of audit files can begin. When the index_creator process is finished, it displays the message "Index_creator process exiting, exit_status = status."

Watchdog timer updating table statistics

This message, which only appears if the -v option is enabled, indicates that the watchdog timer thread is updating the table statistics. Table statistics are used to get the update rates for the various tables. The statistics are used in the computations to balance the load between the various update worker threads when using multi-threaded updates.