[z/OS]

Create the bootstrap and log data sets

Use the supplied program CSQJU003 to prepare the bootstrap data sets (BSDSs) and log data sets.

  • Repeat this task for each IBM® MQ queue manager.
  • [Long Term Support]If you are using z/OS® data set encryption to protect the BSDS or active log data sets, you must configure this option before the data sets are allocated in this step.
  • You do not need to perform this task when migrating from a previous version.

    [Long Term Support]If you are migrating a queue manager and adding z/OS data set encryption for active log data sets or BSDS, you need to convert the data sets.

    See the section, confidentiality for data at rest on IBM MQ for z/OS with data set encryption. for more information about configuring z/OS data set encryption and converting existing IBM MQ data sets to be encrypted.

The sample JCL and Access Method Services (AMS) control statements to run CSQJU003 to create a single or dual logging environment are held in thlqual.SCSQPROC(CSQ4BSDS). Customize and run this job to create your BSDSs and logs and to preformat the logs.
Important: You should use the newest version of CSQ4BSDS, or update your JCL manually to use RECORDS(850 60).
The started task procedure, CSQ4MSTR, described in Create procedures for the IBM MQ queue manager, refers to BSDSs in statements of the form:

//BSDS1   DD DSN=++HLQ++.BSDS01,DISP=SHR
//BSDS2   DD DSN=++HLQ++.BSDS02,DISP=SHR
The log data sets are referred to by the BSDSs.
Note:
  1. The BLKSIZE must be specified on the SYSPRINT DD statement in the LOGDEF step. The BLKSIZE must be 629.
  2. To help identify bootstrap data sets and log data sets from different queue managers, include the subsystem name in the high level qualifier of these data sets.
  3. If you are using queue sharing groups, you must define the bootstrap and log data sets with SHAREOPTIONS(2 3).

See Planning on z/OS for information about planning bootstrap and log data sets and their sizes.

From IBM MQ 8.0, the 8 byte log RBA enhancement improves the availability of a queue manager, as described in Larger log Relative Byte Address. To enable 8 byte log RBA on a queue manager before the queue manager is first started, perform the following steps after creating your logging environment.
[MQ 9.2.5 Feb 2022]Note: For queue managers created at IBM MQ 9.2.5 or later 8 byte log RBA is already enabled, so the following steps are not necessary.
  1. Using IDCAMS ALTER, rename the version 1 format BSDSs (created using the CSQJU003 program) to something like ++HLQ++.V1.BSDS01.
    Note: Ensure that you rename the data and index components as well as the VSAM cluster.
  2. Allocate new BSDSs with the same attributes as the ones already defined. These will become the version 2 format BSDSs that will be used by the queue manager when it is started.
  3. Run the BSDS conversion utility (CSQJUCNV) to convert the version 1 format BSDSs to the new version 2 format BSDSs.
  4. Once the conversion completes successfully, delete the version 1 format BSDSs.
Note: If the queue manager is in a queue sharing group, all queue managers in the queue sharing group must have been started as follows before 8 byte log RBA can be enabled:
  • If the queue manager is at IBM MQ 9.0.0 LTS it must have been started with OPMODE(NEWFUNC,900) or OPMODE(NEWFUNC,800)
  • If the queue manager is at IBM MQ 9.0.n CD, or IBM MQ 9.1.0 LTS, or later, it needs to have been started at that level