IBMQREP_RECVQUEUES table

The IBMQREP_RECVQUEUES table contains information about the IBM® MQ local queues that are used by a Q Apply program to receive transactions from the source. Each Q Apply program can work with multiple receive queues. Each receive queue is uniquely identified by a row in the Q Apply receive queues table.

Server: Q Apply server

Default schema: ASN

Primary key: RECVQ

Unique index: REPQMAPNAME

Important: Do not alter this table by using SQL. Altering this table inappropriately can cause unexpected results and loss of data.

Table 1 provides a brief description of the columns in the IBMQREP_RECVQUEUES table.

Table 1. Columns in the IBMQREP_RECVQUEUES table
Column name	Description
REPQMAPNAME	Data type: VARCHAR(128); Nullable: No The name of the replication queue map that includes this receive queue.
RECVQ	Data type: VARCHAR(48); Nullable: No The name of the receive queue for this Q subscription.
SENDQ	Data type: VARCHAR(48); Nullable: Yes The name of the send queue that is used by the Q Capture program for this Q subscription.
ADMINQ	Data type: VARCHAR(48); Nullable: No The name of the administration queue that is used by the Q Apply program to send control and error messages to the Q Capture program.
NUM_APPLY_AGENTS	Data type: INTEGER; Nullable: No, with default The number of agent threads that the Q Apply program uses to concurrently apply transactions from this receive queue. A value of 1 requests that transactions be executed in the order that they were received from the source table. Default: 16. Maximum number of agent threads: 128.
MEMORY_LIMIT	Data type: INTEGER; Nullable: No, with default The maximum amount of memory in megabytes that the Q Apply program can use as a buffer for messages that it gets from this receive queue. The default value is 64 MB; the maximum value is 2 GB.
CAPTURE_SERVER	Data type: VARCHAR(18); Nullable: No The name of the database where the Q Capture program that uses this receive queue runs. On z/OS, this value is a location name.
CAPTURE_ALIAS	Data type: VARCHAR(8); Nullable: No The DB2® database alias that corresponds to the Q Capture server that is named in the CAPTURE_SERVER column.
CAPTURE_SCHEMA	Data type: VARCHAR(128); Nullable: No, with default The schema of the Q Capture program that uses this receive queue. Default: ASN
STATE	Data type: CHAR(1); Nullable: No, with default A flag that shows the current status of the receive queue. A (default) Active: The Q Apply program is processing and applying the transactions from this queue. I Inactive: A severe error was encountered on the queue.
STATE_TIME	Data type: TIMESTAMP; Nullable: No, with default The timestamp in the local time of the Q Apply server of the last state change for this receive queue. Default: Current timestamp
STATE_INFO	Data type: CHAR(8); Nullable:Yes The number for the ASN message about the queue state. For details, see the IBMQREP_APPLYTRACE table, or the Q Apply diagnostic log.
DESCRIPTION	Data type: VARCHAR(254); Nullable: Yes A user-supplied description of the replication queue map that contains this receive queue.
SOURCE_TYPE	Data type: CHAR(1); Nullable: Yes, with default The value of this attribute indicates the type of data source for each record. C Classic data source D DB2 data source Default: NULL
MAXAGENTS_CORRELID	Data type: INTEGER; Nullable: Yes, with default The maximum number of Q Apply agents that can concurrently apply transactions that have the same correlation ID. The correlation ID identifies transactions that were started from the same z/OS® job on the Q Capture server. You can use the MAXAGENTS_CORRELID value to limit parallelism for batch jobs that might have many dependencies that could cause lock contention. You can set the value by using the CREATE REPLQMAP or ALTER REPLQMAP commands. The value for the MAXAGENTS_CORRELID column cannot be greater than the value for the NUM_APPLY_AGENTS. If MAXAGENTS_CORRELID value is 1, the transactions will be applied serially. If the value is greater than one, for example 4, the first four transactions will be applied in parallel and the following transactions are marked as dependent to any one of the transactions. When a transaction finishes, a dependent transaction with the same correlation ID is applied. Default: ' '
BROWSER_THREAD_ID	Data type: VARCHAR(9); Nullable: Yes, with default The correlation ID for the browser thread that is processing this receive queue. Default: NULL
PARALLEL_SENDQS	Data type: CHAR(1); Nullable: No, with default A flag that indicates whether the Q Capture program uses multiple send queues to replicate transactions to this receive queue. N (default) Q Capture uses one send queue. Y Q Capture uses multiple send queues. Each send queue uses a separate transmission queue and channel. Transactions from all send queues that are defined for the replication queue map funnel to the single receive queue that is defined for the queue map. Important: If the value of the NUM_PARALLEL_SENDQS column in the IBMQREP_SENDQUEUES table is greater than 1, the PARALLEL_SENDQS column must be set to Y.
MCGNAME	Data type: VARCHAR(64); Nullable: Yes, with default The name of the multiple consistency group that this receive queue is part of. For IBM GDPS® active/active continuous availability, the value is the GDPS active/standby workload name. Default: NULL
BIDIAPPLY_SCHEMA	Data type: VARCHAR(128); Nullable: Yes, with default In a bidirectional replication configuration, the schema of the other Q Apply program. Default: NULL
MRI_MEMORY_LIMIT	Data type: INTEGER; Nullable: No, with default The maximum amount of memory in kilobytes that each Q Apply agent thread can use as an input buffer for multi-row inserts. The size of the input buffer determines how many rows can be inserted in one SQL operation. A larger value for this parameter can enable the Q Apply program to group more rows into each multi-row insert operation. Default: 1024 You can only use this option if the value of the MULTI_ROW_INSERT column in the IBMQREP_APPLYPARMS table is Y (yes).
AGENT_STMT_CACHE_SZ	Data type: INTEGER; Nullable: No, with default The number of prepared SQL statements that the Q Apply program caches per agent for this receive queue. The default is 300; valid values are from 50 to 500. A lower value can reduce the amount of memory that the Q Apply program uses. For tuning information, see Reducing Q Apply memory requirements.
ROLLBACK_R_REPORT	Data type: CHAR(1); Nullable: No, with default Reserved for future use.
RI_DEPENDENCY_BY_VALUES	Data type: CHAR(1); Nullable: Yes, with default A flag that specifies whether the Q Apply program uses foreign key data values to determine whether transactions should be serialized (applied in source commit order) because of referential integrity dependencies. N (default) Q Apply does not use foreign key data values for RI dependency checking. Y Q Apply uses foreign key data values to perform dependency checks for row changes between parent and child tables. Note: If you specify RI_DEPENDENCY_BY_VALUES=Y, you must also specify SEND_RI_COLUMN_VALUES=Y in the IBMQREP_SENDQUEUES table to enable the Q Capture program to send foreign key data values.