Host Messages That Appear on the Client
The following host messages may appear onscreen and in the log file of the Client. If tracing is enabled, messages are also captured in the trace file.
All host messages are followed by a second message that provides an error number.
HOST ERROR: hosterrortext
Error Text: text
where hosterrortextis a message from the Client, as listed in this section.
| 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. This message typically identifies the API (Engine entry point) being called and provides additional about the task being performed, whenever this is relevant. |
| text | A message from the DBEngine or DBServer on the host, or Enterprise Server. All such messages contain a number whose range determines the origin of the message. DBEngine messages start at 0000, DBServer messages start at 1000, and Enterprise Server messages start at 1100. |
HOST ERROR: 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 RPC; DBServer 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.
HOST ERROR: Databridge call failed for baselist, error number = number
The Client uses this API to get the structure numbers of the real data sets from which a virtual
data set is derived. It only does this when the parameter automate_virtuals is set to True
and the parameter miser_datebase is set to False.
HOST ERROR: Databridge call failed for connect, error number = number
The Client is unable to connect to the Databridge Server (DBServer or DBEnterprise Server). 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 DBServer parameter file and that the mainframe, the Databridge Engine, and DBServer are running. If you are connecting to DBEnterprise Server, you also need to make sure that the DBDirector service is running.
HOST ERROR: Databridge call failed for datasets, error number = number
The Databridge Engine 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 Databridge Engine or the Databridge Server.
HOST ERROR: 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.
HOST ERROR: Databridge call failed for DB_DeSelect on DataSet name[/rectype], error number = number
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 RPC
failed.
HOST ERROR: Databridge call failed for DB_PumpMsg, error number = number
DB_PumpMsg is an RPC to DBServer 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 RPC failed.
HOST ERROR: 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 RPC, which is used to request updates from the Engine.
HOST ERROR: Databridge call failed for DB_Select on table datasetname, error number = number
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. As part of initialization, the
Client send a DB_Select request for every data that it to be cloned or tracked. The DB_Select
RPC data include the stateinfo for the data set, which includes the mode and the audit location
from which to resume tracking changes. If the data set is to be cloned, the stateinfo consists of
all zeroes.
HOST ERROR: 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 RPC. This message appears only if the use_dbwait parameter is set to true in the
client configuration file (or you use the /w command line switch to toggle it to true). Instead of
returning a DBM_AUD_UNAVAIL (7) status to the Client, the Engine enters a wait-and-retry
loop. It retries every max_retry_secs until either more updates become available, or,
max_wait_secs elapses (without any updates becoming available). In the case of the latter,
the Engine sends the Client a DBM_AUD_UNAVAIL (7) status, which causes the Client run to
terminate.
HOST ERROR: 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 RPC. This error can also occur during a process or
clone command. The Client uses this RPC to determine if the update level of the DMSII
database has changed and makes the appropriate change to the update level value in the
DATASOURCES Client control table when the Client ignores an update level change. It also uses
this information to inhibit clones during periods where there is a DMSII reorganization that the
client has not yet caught up to.
HOST ERROR: Databridge call failed for initialize, error number = number
The Databridge initialize remote procedure call could not initialize the session between
DBServer 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.
HOST ERROR: Databridge call failed for initialvalue, error number = number
The Client uses the initialvalue remote procedure call (RPC) to get the initial value for a data
set. It uses this information to assign values to columns that are added as a result of a DMSII
reorganization. This message only occurs during a redefine command.
HOST ERROR: 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.
HOST ERROR: Databridge call failed for layout, error number = number
Databridge was unable to retrieve information on the layout of a data set. This message can
occur when you run a define or redefine command.
HOST ERROR: 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. A nullrecord is a DMSII record for a data set where all items are set to NULL using
the null values defined in the DASDL. The Client uses this information to construct the
nullrecord file, which is used to determine if items are NULL.
HOST ERROR: 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.
The Client also uses this API during process commands to ensure that the Engine uses the
correct description file when processing DMSII data. When the client has not yet caught up
with a DMSII reorganization, the proper description file must be used.
HOST ERROR: 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.
HOST ERROR: 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.
HOST ERROR: 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.
HOST ERROR: Databridge call failed for parameters TG_TRANS, error number = number
The Client could not override the Databridge Engine parameter CHECKPOINT every nnn
TRANSACTIONS during the execution of a process or clone command.
HOST ERROR: 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.
HOST ERROR: 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.
HOST ERROR: 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.
HOST ERROR: 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.
HOST ERROR: Databridge call failed for server_option INHIBIT_WFL, error number = number
The Client was unable to set the server option that inhibits the running of a WFL when an audit file is processed by the Engine. Normally such a WFL would be used to remove the audit files, once the Engine is done with them.
HOST ERROR: Databridge call failed for server_option STOP_{BEFORE | AFTER}_NAME, error number = number
The Client was unable to set the server option that causes the Engine to stop processing audit files when the specified task name is encountered is in the audit trail. The Engine can stop at the quiet point before or after the specified task is encountered. These values are defined in the client configuration file using the parameters stop before task or stop after task.
HOST ERROR: Databridge call failed for server_option STOP_{BEFORE | AFTER}_TIME, error number = number
The Client was unable to set the server option that causes the Engine to stop processing audit files when the specified time is reached. These values are defined in the client configuration file using the parameters stop before task or stop after task.
HOST ERROR: Databridge call failed for server_stats, error number = number
The Client was unable to obtain the server statistics using the DB_WorkerInfo RPC.
HOST ERROR: Databridge call failed for set_option DOC, error number = number
Databridge could not set the DBServer 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.
HOST ERROR: Databridge call failed for set_option DOC_AFN, error number = number
Databridge could not set the DBServer option that requests DOC records to be sent when 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.
HOST ERROR: Databridge call failed for set_option Embedded Extract w/o IndependentTrans, 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.
HOST ERROR: Databridge call failed for set_option GLOBAL_SI, error number = number
The Client could not set the DBServer option that requests global stateinfo records to be sent during audit file processing instead of sending stateinfo records for each data set. The Engine only honors this request when all data sets are in mode 2 and they have identical stateinfo values (that is, they are all in sync).
HOST ERROR: 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.
HOST ERROR: Databridge call failed for set_option LONGTRANS, error number = number
The Client could not set the Databridge Engine parameter CHECKPOINT LONG TRANSACTIONS during the execution of a process or clone command.
HOST ERROR: Databridge call failed for set_option MAXRECS, error number = number
The Client was unable to set the DBServer MAXRECS option using the DB_ServerOption RPC. The MAXRECS option causes the DB_datasets RPC to set the max_records field to the maximum number of records that the data set can hold without expanding. This is quite useful in estimating the size of a table. In the case of variable format data sets, the number is meaningless, as it uses the size of the fixed part to compute the value of max_records.
HOST ERROR: 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.
HOST ERROR: 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.