The bootstrap data set (BSDS) is the catalog IBM MQ consults when it must answer recovery questions: which log data sets exist, where does each archive range begin and end, what was the last checkpoint, and how do we find the right tape or DASD volume after an outage. Message bodies live in page sets; log records live in active and archive logs; BSDS ties them together so restart is not guesswork. Operators rarely DISPLAY BSDS daily, but every successful archive cycle and every warm restart depends on BSDS integrity. Dual BSDS pairs exist because a single corrupted catalog should not end the enterprise messaging tier. This tutorial explains BSDS contents conceptually, relationship to Log RBA and archive logs, dual copy behavior, utilities that manage BSDS, backup and restore considerations, and failure scenarios beginners hear in operations reviews.
| Component | Holds | BSDS link |
|---|---|---|
| Page sets | Messages and queue metadata on disk | Checkpoint RBA points into logs |
| Active logs | Recent change records | BSDS lists active log data sets |
| Archive logs | Historical log ranges | BSDS registers name and RBA range |
| BSDS | Inventory and control | Central index |
| Checkpoint | Recovery start optimization | Recorded in BSDS |
BSDS entries include active log data set names and status, archive log data set names with starting and ending RBA, timestamps of archiving operations, and checkpoint information. Relative byte address (RBA) is the logical position in the log stream—recovery uses RBA to know which records to apply after a given point. Beginners should treat RBA like page numbers in a book index: BSDS is the table of contents, logs are the chapters.
IBM MQ maintains two bootstrap data sets—commonly called BSDS1 and BSDS2. Updates alternate or synchronize so one copy can recover the other after certain failures. Allocation during queue manager creation defines both; JCL and storage groups must place them on reliable volumes, often different from each other for media isolation. Losing both BSDS copies without backup is a major incident; restore procedures from IBM documentation and site DR plans apply.
When an active log fills, archiving copies log records to archive data sets and updates BSDS with new archive entries. Operators monitor that archiving completes—stalled archive leaves active logs full and stops durable puts. BSDS growth and entry count can require maintenance utilities in long-lived queue managers; capacity planning includes BSDS size not only page sets.
123456/* Conceptual operator flow 1. Active log reaches threshold 2. Archive process writes archive log data set 3. BSDS updated with archive name and RBA range 4. Active log space reusable Review CSQ messages and DISPLAY LOG output */
Log management utilities documented in IBM MQ for z/OS process BSDS under operator control—rebuilding, converting, or recovering BSDS after incidents. Exact utility names and JCL procs vary by release; systems programmers maintain standardized jobs. Never attempt ISPF edit on BSDS; corruption may force full recovery from backups.
| Symptom | Possible cause | Action direction |
|---|---|---|
| Restart fails log open | BSDS/log mismatch | IBM recovery utilities; support |
| Archive not registered | Stalled archive job | Complete archive; check BSDS update |
| Duplicate archive name | Manual intervention error | Follow IBM cleanup procedures |
| RBA gap in recovery | Missing archive volume | Restore archive from tape |
Logs are books on the shelf. BSDS is the card catalog telling you which book holds which chapter range. Without the catalog, finding the right chapter after a fire takes forever.
BSDS is the list that says which diary notebooks exist and which pages they cover, so MQ knows which notebook to read after a nap.
Draw relationships between page set, active log, archive log, and BSDS during a persistent put.
Explain why dual BSDS matters when one DASD volume fails.
Write DR checklist items specific to BSDS backup and restore.
1. BSDS stands for:
2. BSDS tracks:
3. Dual BSDS provides:
4. Manual BSDS edit: