Host Messages

Host messages appear onscreen. These messages are also written to the log file. If tracing is enabled, these messages are captured in the trace file. See Log and Trace Files.

All host messages are followed by a second message that provides an error number, as follows:

HOST ERROR: hosterrortext

Error Text: DBServer/n: nnnn: text

These numbered errors are listed in Appendix A of the DATABridge Host Administrator’s Guide.

Where

Is

hosterrortext

A message from the Client, as listed in this section. Host messages are prefixed by the timestamp hh:mm:ss, where hh is hours, mm is minutes, and ss is seconds.

n

A number identifying the Server Accessory worker

nnnn: text

A message from the Server Accessory on the host. Server Accessory error messages begin with 1nnn and are documented in Appendix A of the DATABridge Host Administrator’s Guide.

DATABridge call failed for ATMEcho, error_number = number

The Client uses this API to verify that the transport layer is operational. This is always the first API call; the Server Accessory echoes the test pattern back to the Client. This message indicates that the Client received an unrecoverable error. The Client recovers from a timeout error or from receiving bad data by disconnecting and reestablishing the connection. When the -v option is used, the Client displays the message "Disconnecting and restarting transport initialization" for timeouts.

DATABridge call failed for connect, error number = number

The Client is unable to connect to the DMSII database. Make sure that the host name is correct (that is, it matches the host name in the DATASOURCES table) and the domain name server is running.

—or—

Change the host name in the DATASOURCES table to the IP address and try the Client command again. Verify that the port number matches the port number in the Server Accessory parameter file and that the mainframe, the DATABridge Engine, and the Server Accessory are running.

DATABridge call failed for datasets, error number = number

DATABridge was unable to retrieve the requested information on data sets. This message can occur when you run a define or redefine command and get an error from the host or the DATABridge Engine.

DATABridge call failed for DB_ClientKey on DataSet name{/rectype], error number = number

The Client was unable to register the Client keys with the DATABridge Engine for the specified data set, which has the KEYCHANGEOK attribute.

DATABridge call failed for DB_DeSelect on DataSet name[/rectype], error number = number

DB_DeSelect is an API call to the DATABridge Engine on the host. This error can occur during a process or clone command. It indicates that the Client attempted to request that the DATABridge Engine stop sending updates for the data set (or data set record type combination in the case of a variable-format data set) and that the API call failed.

DATABridge call failed for DB_PumpMsg, error number = number

DB_PumpMsg is an API call to the Server Accessory on the host that creates data traffic to test the speed of the TCP/IP connection. This error can occur during a tcptest command and indicates that the API call failed.

DATABridge call failed for DB_Read call, error number = number

This message indicates that an error occurred during a process or clone command for the specified DB_Read API call.

DATABridge call failed for DB_Select on table datasetname, error number = number

DB_Select is an API call to the DATABridge Engine on the host. This error can occur during a process or clone command, and it indicates that the DATABridge Engine was unable to select the requested data set.

DATABridge call failed for DB_Wait call, error number = number

This message indicates that an error occurred during a process command for the specified DB_Wait API call. This message appears only if you are using the max_retry_secs and max_wait_secs parameters.

DATABridge call failed for dbinfo, error number = number

This message, which can occur when you run a define or redefine command, indicates that the Client was unable to retrieve information about the DMSII database from the DATABridge Engine using the DB_Info API call.

DATABridge call failed for initialize, error number = number

The DATABridge initialize remote procedure call could not initialize the session between the Server Accessory and the Client. This message occurs after three unsuccessful attempts for a TCP/IP connection. This message can occur when you run a define, redefine, process, clone, or switchaudit command.

DATABridge call failed for keys, error number = number

DATABridge was unable to retrieve information on keys. This message can occur when you run a define or redefine command.

DATABridge call failed for layout, error number = number

DATABridge was unable to retrieve information on database layout. This message can occur when you run a define or redefine command.

DATABridge call failed for nullrecord, error number = number

The Client was unable to retrieve the nullrecord information for a data set. This message can occur during a define or redefine command when the parameter read_null_records is set to True.

DATABridge call failed for open_audit, error_number = number

The Client uses this API during the redefine command to force the DATABridge Engine to use the correct description file by opening the audit file that was being read when the DMSII reorganization was detected. This technique makes it possible to process multiple reorganizations when the Client is far behind DMSII. If this creates a problem, you can disable this call by setting the configuration parameter open_audit_file to No.

DATABridge call failed for parameters CONCURR_EXTR, error number = number

The Client could not override the DATABridge Engine parameter WORKERS = n during the execution of a process or clone command.

DATABridge call failed for parameters TG_BLOCKS, error number = number

The Client could not override the DATABridge Engine parameter CHECKPOINT every nnn AUDIT BLOCKS during the execution of a process or clone command.

DATABridge call failed for parameters TG_ELAPSED, error number = number

The Client could not override the DBEngine parameter CHECKPOINT every nnn SECONDS during the execution of a process or clone command.

DATABridge call failed for parameters TG_UPDATES, error number = number

The Client could not override the DATABridge Engine parameter CHECKPOINT every nnn UPDATE RECORDS during the execution of a process or clone command.

DATABridge call failed for primary_key, error number = number

The Client was unable to retrieve information on the primary keys for a data set. This message can occur when you run a define or redefine command.

DATABridge call failed for primary_set, error number = number

The Client was unable to retrieve information on the primary_set for a data set. This message can occur when you run a define or redefine command.

DATABridge call failed for reset_option LONGTRANS, error number = number

The Client could not reset the DATABridge Engine parameter CHECKPOINT LONG TRANSACTIONS during the execution of a process or clone command.

DATABridge call failed for server_option INHIBIT_WFL, error number = number

The Client was unable to call the Server Accessory with the specified server option.

DATABridge call failed for server_option STOP_ {BEFORE | AFTER} _NAME, error number = number

The Client was unable to set the Server Accessory with the specified stop_before_task_name or stop_after_task_name parameter using the DB_ServerOption API call.

DATABridge call failed for server_option STOP_ {BEFORE | AFTER} _TIME, error number = number

The Client was unable to set the Server Accessory with the specified stop_before_time or stop_after_time parameter using the DB_ServerOption API call.

DATABridge call failed for server_stats, error number = number

The Client was unable to obtain Server Accessory statistics using the DB_WorkerInfo API call.

DATABridge call failed for set_option DOC, error number = number

DATABridge could not set the Server Accessory option that requests DOC records to be sent during audit file processing. This message can occur at the beginning of a process or clone command when the Client uses the DBSetOption remote procedure call to request that the DATABridge Engine provide documentation (DOC) records while reading the audit file.

DATABridge call failed for set_option DOC_AFN, error number = number

DATABridge could not set the Server Accessory option that requests DOC records to be sent whan a new audit file is open during audit file processing. This message can occur at the start of a process or clone command. The Client uses the DBSetOption remote procedure call to request that the DATABridge Engine provide documentation (DOC) records for all audit files when the Engine starts processing them.

DATABridge call failed for set_option Embedded Extract, error number = number

The Client could not set the DATABridge Engine option that indicates that embedded data sets should be extracted even though INDEPENDENTTRANS is reset. Such data sets cannot be tracked.

DATABridge call failed for set_option GLOBAL_SI, error number = number

The Client could not set the Server Accessory option that requests global stateinfo records to be sent during audit file processing.

DATABridge call failed for set_option ITEMCOUNT, error number = number

The Client could not set the DATABridge Engine option that indicates it should use the new method for calculating the item counts of data sets.

DATABridge call failed for set_option MAXRECS, error number = number

The Client was unable to set the Server Accessory MAXRECS option using the DB_ServerOption API call.

DATABridge call failed for set_option QPT_GROUP, error number = number

This message applies to the obsolete commit_each_quiet_pt parameter. If this message still appears, contact Attachmate Technical Support.

DATABridge call failed for sets, error number = number

DATABridge was unable to retrieve information on sets. This message can occur when you run a define or redefine command.

DATABridge call failed for switch_audit, error number = number

The Client remote procedure call on the DBSWITCHAUDIT API failed. This message can occur during a switchaudit command.