The QMINI data set

We can use the QMINI dataset to specify properties that are to be read and processed during queue manager initialization.

Characteristics of the QMINI data set

The QMINI data set is a VSAM sequential dataset with a maximum record length of 80 bytes (72 bytes for data and eight bytes for the line number).

Data Set Name . . . . : QM01.QMINI 
General Data                        Current Allocation 
Management class . .  : STANDARD    Allocated tracks  . : 1 
Storage class  . . .  : STANDARD    Allocated extents . : 1 
Volume serial . . .   : P5P21E 
Device type . . . .   : 3390 
Data class . . . . .  : **None** 
Organization  . . .   : PS          Current Utilization 
Record format . . .   : FB          Used tracks . . . . : 0 
Record length . . .   : 80          Used extents  . . . : 0 
Block size  . . . .   : 3120 
1st extent tracks .   : 1           
Secondary tracks  .   : 1           Dates 
Data set name type    :             Creation date . . . : 2020/08/11
Data set encryption   : NO          Referenced date . . : ***None***
                                    Expiration date . . : ***None***
SMS Compressible  .   : NO

• The sample contents for a QMINI data set in CSQ4QMIN.
• An example of the data set we need to supply to the //CSQMINI DD card, in the queue manager startup JCL, in started task procedures CSQ4MSTR and CSQ4MSRR.

Notes:

• The code that parses the dataset only parses the first 72 bytes of each record.
• Line numbers are ignored so it is not necessary to specify line numbers.
• If a line starts with an asterisk character (*), the line is treated as a comment.

The TransportSecurity stanza

From IBM MQ for z/OS Version 9.2.0, the QMINI data set supports the TransportSecurity stanza. This stanza provides similar function to that provided by the SSL stanza in the qm.ini file on IBM MQ for Multiplatforms.

AllowTLSV13

Whether a queue manager is able to use the TLS 1.3 CipherSpecs; valid values are: TRUE/T/YES/Y or FALSE/F/NO/N.

AllowedCipherSpecs

A custom list of CipherSpecs.

See Providing a custom list of ordered and enabled CipherSpecs on IBM MQ for z/OS for more information on this property.

Important:

1. Duplicate CipherSpec names in the list are ignored.
2. For migrated queue managers, TLS 1.3 is not enabled by default. We can enable TLS 1.3 by defining a QMINI dataset with the TransportSecurity stanza and AllowTSV13=TRUE.
3. For newly created queue managers, TLS 1.3 is enabled by default, if the version of z/OS that the queue manager is being run against is greater than Version 2.3.

   For newly created queue managers, running on z/OS 2.4 or above, TLS 1.3 is enabled by default.

4. The contents of the QMINI data set are parsed during queue manager startup. If the contents are parsed successfully, message CSQM578I is issued in the queue manager job log. If any errors are encountered during parsing, error messages, for example CSQM573E, will be issued in the queue manager job log but the queue manager still starts.

   Check for error messages, and resolve any issues in the contents of the QMINI data set.

   If we do not resolve any issues, and the queue manager is unable to parse the QMINI data set, we will be able to start the channel initiator, but we will not be able to start any channels that are configured to use SSL or TLS. The reason for this is that with potential errors in the QMINI data set, the queue manager and channel initiator are unable to firmly deduce the intended security configuration settings.

5. If you make any updates to the data set after you have started the queue manager, we must restart the queue manager to pick up the changes.

Parent topic: Customize the initialization input data sets