Customizing MainView for MQ after installation

The information that is required for installing MainView for MQ from the distribution tape is provided in the Installation System Reference Manual.

When MainView for MQ is installed on your system, you must identify the product to the BBI subsystem. You must also provide access to IBM MQ, either manually or automatically, by performing customization within the Installation System. Later, you can establish your site’s security. For more information about establishing your site’s security, see Security settings.

To customize MainView for MQ after installation is complete


The DDNAME BMCMSGLG, which is used as a repository for diagnostic information, is allocated by the product dynamically. If the BBI-SS address space is started by using SUB=MSTR, the BMCMSGLG DDNAME must be added to the BBISS JCL. This DDNAME should point to a data set with DCB attributes of BLKSIZE=32760, MAX LRECL=32752, and RECFM=VB. This DDNAME can also be allocated to DD DUMMY with the appropriate DCB attributes.

  1. When you set the BBI-SS PAS environment, add the following product record to member BBISSP00 in your copy of the BBPARM parameter library (which you define by using the BBIPARM DD record in the BBI-SSMQ PAS job):

  2. To the STEPLIB DD record in the BBI-SS PAS job, add the following program libraries, which are authorized by IBM MQ:


    Theprefix value was defined when you installed IBM MQ.


    The program libraries must be APF-authorized.

  3. If you plan to manage non-MVS queue managers by using the Node Manager, consult with your TCP/IP programmer to determine whether the following steps are necessary:
    1. Add the following DD records to your STEPLIB concatenation:


      The variabletcpPrefix was defined when you installed TCP/IP.


      These program libraries must be APF-authorized.

    2. Depending on your system configuration, add the following DD record to the BBI-SS PAS job:

      //SYSTCPD DD DISP=SHR,DSN=tcpPrefix.tcpipData
    3. Create member BBTTCPxx in your copy of the BBPARM library.

      The variable xx is 00 or the suffix that you specify with the GTS parameter in member BBISSP00. Member BBTTCP00 defines your TCP/IP environment and has the following statement:


      TCPNAME is set to the Started Task name of your TCP/IP job.

  4. To support the creation of a dynamic reply-to queue, define a model queue named BBSMVMQS.COMMAND.REPLY.MODEL.

    The model queue should have attributes that are identical to the SYSTEM.COMMAND.REPLY.MODEL queue, and the model queue should be defined as permanent dynamic.

    MainView for MQ creates the reply-to queue by first looking for a model queue named BBSMVMQS.COMMAND.REPLY.MODEL. If this queue is not found, the SYSTEM.COMMAND.REPLY.MODEL queue is used. The model queue that is used must be a permanent dynamic queue. Using a temporary dynamic queue can cause the temporary dynamic queues to be deleted unexpectedly and errors while retrieving data.


    If you cannot create a BBSMVMQS.COMMAND.REPLY.MODEL permanent dynamic model queue, ensure that the SYSTEM.COMMAND.REPLY.MODEL queue is permanent dynamic.

  5. To support the editing of messages, define a queue named BBSMVMQS.REPLY.AUDIT with attributes that are identical to the BBSMVMQS.COMMAND.REPLY.MODEL queue.


    0 creates and uses multiple console support (MCS) consoles for issuing:

    • Commands to start queue managers and command servers

    • IBM MQ script commands (MQSC) with the MQSC global command

Was this page helpful? Yes No Submitting... Thank you