Display information about an agent and its configuration including those statistics and operational parameters maintained in the configuration file.
Syntax
sqdconf display <cab_file_name>
[--status]
[--targets]
[--storage]
[--sysprint=<DDNAME> | --sysout=<DDNAME>]
Keyword and Parameter Descriptions
Keyword | Description |
---|---|
[--status] |
Only the messages SQDF901I and SQDF920I (the status) will be displayed. |
[--targets] | Only the messages relating to the subscribing target Engines will be displayed. |
[--storage] | Only the messages relating to the status and state of the transient storage will be displayed. |
[--sysprint=<DDNAME> | --sysout=<DDNAME>] | z/OS Only, specify alternative DDNAME for output. |
The message SQDF902I indicates the status of the agent which may contain one or more conditions as follows:
- MOUNTED - Agent is executing but not active
- NOTMOUNTED - Agent is not executing at all.
- MOUNTED/PAUSED - Agent is executing and able to capture but Publishing has been Paused.
- MOUNTED/STOPPED - Agent is executing but not Capturing/Publishing.
- MOUNTED/STARTED - Agent is executing, Capturing and/or Publishing to all Subscribers.
- MOUNTED/STARTED/STALLED - Agent is Executing and Capturing, however one or more Subscribers is not active and therefore Publishing has stopped.
- MOUNTED/STARTED/FULL - CDCSTORE is full, however data is being published. This is a symptom that downstream Apply Engines are running slow creating a backlog of data to be published. This is NOT a problem but a symptom of a potential problem.
- MOUNTED/STARTED/DEADLOCK - CDCSTORE is full and publishing cannot continue. This is a problem because a lack of free space in the transient data area managed by CDCSTORE is preventing one or more UOW's from being published because all the committed changed data from a predecessor UOW cannot be held. This is a rare situation but one that cannot be resolved without expanding the size of the CDCSTORE storage area.
Note:
- This command can be useful in a cron job. For example, a crontab entry could test every 10 minutes whether a given agent is STARTED and invoke another script if it is not.
- In addition to the status of the agent, display used with an active Capture / Publisher configuration (.cab) file will include other information including:
- The starting and current point in the log where data has been captured
- The number of inserts, updates and deletes for the session (i.e. the duration of the capture agent run)
- The number of inserts, updates and deletes since the creation of the configuration file
Example 1
Display the status of the Relational Capture transient storage.
sqdconf display /home/sqdata/db2cdc_store.cab
SQDC017I sqdconf(pid=0x99) terminated successfully
SQDF801I Configuration name : cdcstore
SQDF802I Configuration key : cab_964960E67A564AA3
SQDF850I Session Statistics -
SQDF851I Txn Max Record : 44
SQDF852I Txn Max Size : 42386124
SQDF853I Txn Max Log Range : 8207
SQDF855I Max In-flight Txns : 0
SQDF856I # Txns : 608
SQDF857I # Effective Txns : 104
SQDF861I # Commit Records : 82
SQDF858I # Rollbacked Txns : 21
SQDF859I # Data Records : 2775
SQDF860I # Orphan Data Records : 0
SQDF862I # Rollbacked Records : 924
SQDF863I # Compensated Records : 0
SQDF866I # Orphan Txns : 0
SQDF867I # Mapped Blocks : 0
SQDF868I # Accessed Blocks : 2
SQDF869I # Logical Blocks : 0
SQDF870I Life Statistics -
SQDF871I Max Txn Record : 44
SQDF872I Max Txn Size : 42386124
SQDF873I Max Txn Log Range : 24582
SQDF875I Max In-flight Txns : 0
SQDF876I # Txns : 76576
SQDF877I # Effective Txns : 27701
SQDF881I # Commit Records : 22154
SQDF878I # Rollbacked Txns : 5546
SQDF879I # Data Records : 752586
SQDF880I # Orphan Data Records : 0
SQDF882I # Rollbacked Records : 243513
SQDF883I # Compensated Records : 0
SQDF886I # Orphan Txns : 0
SQDF887I # Mapped Blocks : 48
SQDF888I # Accessed Blocks : 2006
SQDF889I # Logical Blocks : 48
SQDC017I sqdconf(pid=0x99) terminated successfully