BSDS

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.

BSDS in the Recovery Architecture

Recovery components
ComponentHoldsBSDS link
Page setsMessages and queue metadata on diskCheckpoint RBA points into logs
Active logsRecent change recordsBSDS lists active log data sets
Archive logsHistorical log rangesBSDS registers name and RBA range
BSDSInventory and controlCentral index
CheckpointRecovery start optimizationRecorded in BSDS

What BSDS Records Describe

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.

  • Active log data set pairs and which is receiving writes.
  • Archive log volumes created by offloading active logs.
  • Ranges of log records available for forward recovery.
  • Checkpoint RBAs aligning page sets with log position.
  • Control information for log management utilities.

Dual BSDS

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.

Archiving and BSDS Updates

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.

text
1
2
3
4
5
6
/* 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 */

Utilities and Commands

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.

Backup Strategy

  1. Include BSDS in queue manager backup scope with page sets and CF structures as policy dictates.
  2. Coordinate backup timing with quiet log position or copy technology your site uses.
  3. Test restore in DR annually—untested BSDS backup is hope, not strategy.
  4. Document RBA and timestamp of backup for media recovery scenarios.

Failure Symptoms

BSDS-related problems
SymptomPossible causeAction direction
Restart fails log openBSDS/log mismatchIBM recovery utilities; support
Archive not registeredStalled archive jobComplete archive; check BSDS update
Duplicate archive nameManual intervention errorFollow IBM cleanup procedures
RBA gap in recoveryMissing archive volumeRestore archive from tape

Explainer: Library Index Cards

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.

Explain Like I'm Five

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.

Practice Exercises

Exercise 1

Draw relationships between page set, active log, archive log, and BSDS during a persistent put.

Exercise 2

Explain why dual BSDS matters when one DASD volume fails.

Exercise 3

Write DR checklist items specific to BSDS backup and restore.

Frequently Asked Questions

Frequently Asked Questions

Test Your Knowledge

Test Your Knowledge

1. BSDS stands for:

  • Bootstrap data set
  • Basic security data set
  • Batch script data set
  • Bridge sync data set

2. BSDS tracks:

  • Log and recovery metadata
  • Only TLS keys
  • Only topics
  • JCL libraries

3. Dual BSDS provides:

  • Redundancy
  • Faster channels
  • Larger messages
  • No archive

4. Manual BSDS edit:

  • Corrupts recovery — avoid
  • Recommended daily
  • Replaces RACF
  • Starts channels
Published
Read time22 min
AuthorMainframeMaster
Verified: IBM MQ 9.3 documentation