Limitations

Limitations when using z/OSMF with IBM MQ .

1. The provision.xml workflow currently automates the following highlighted queue manager customization tasks:

   Task	Description
   1	Identify the z/OS® system parameters
   2	APF authorize the IBM MQ load libraries (provision.xml does APF authorize some libraries)
   3	Update the z/OS link list and LPA
   4	Update the z/OS program properties table
   5	Define the IBM MQ subsystem to z/OS
   6	Create procedures for the IBM MQ queue manager
   7	Create procedures for the channel initiator
   8	Define the IBM MQ subsystem to a z/OS WLM service class
   9	Select and set up your coupling facility offload storage environment
   10	Set up the coupling facility
   11	Implement your ESM security controls
   12	Update SYS1.PARMLIB members
   13	Customize the initialization input data sets
   14	Create the bootstrap and log data sets
   15	Define your page sets
   16	Add the IBM MQ entries to the Db2® data-sharing group
   17	Tailor your system parameter modules (some)
   18	Tailor the channel initiator parameters (some)
   19	Set up Batch, TSO, and RRS adapters
   20	Set up the operations and control panels
   21	Include the IBM MQ dump formatting member
   22	Suppress information messages
   23	Update your system DIAG member for Advanced Message Security
   24	Create procedures for Advanced Message Security
   25	Set up the started task user Advanced Message Security
   26	Grant RACDCERT permissions to the security administrator for Advanced Message Security
   27	Grant users resource permissions for Advanced Message Security

2. Customization tasks that are not highlighted in bold text need to be performed manually, if required.
3. The sample INP1 and INP2 members are currently used as is. If required, additional properties can be defined to control the resources defined by these members.
4. Comments pertaining to specific properties listed in the properties file indicate any limitations of using those properties. For more details, see Running the workflows.