Space banner

   

This space provides the same content as before, but the organization of the home page has changed. To help you quickly find the content that you need, topics are now organized based on logical branches instead of legacy book titles

Connecting to a distributed system queue manager by using proxy

When connecting MainView for MQ to a distributed systems queue manager by using proxy, MainView for MQ requests are sent between the BBI subsystem and a queue manager on a non-MVS system by routing them through a local proxy queue manager on the MVS system.

Connection by proxy requires MainView for MQ channels and is considered inbound monitoring. The preferred method of monitoring distributed systems queue managers from MainView for MQ is by using a Node Manager Agent and requires BMC Performance Manager forMQ (formerly named PATROL forMQ) to be licensed and running on the distributed systems platform.

To connect to a distributed system queue manager by using proxy

  1. Define the MQ objects that are necessary for connectivity.

    For an example of how to define transmission queues and channel queues for an MVS queue manager, see member BBSMQSCL in your copy of the BBSAMP library.

    For an example of how to define transmission queues and channel queues for a distributed queue manager, see member BBSMQSCD in your copy of the BBSAMP library.

    Note

    If you create channels with a transmission queue name that is different from the remote queue manager name, you must create a remote queue definition with that transmission queue name for this step to work properly.

  2. Define the queue manager target names.

    Both the distributed systems queue managers and the MVS queue managers must be defined.

  3. Define the Queue Manager Profile.

    Each queue manager target name requires a profile that specifies the properties of the queue manager.

    For more information about creating QMPROF definitions, see Defining queue manager profiles.

    Note

    When defining the QMPROF definition, if you specify the security user ID as USER, then the TSO user ID for each user will also have to be defined and assigned mqm authority on the distributed systems platforms.

  4. Set up security.

    For more information, see Security for Windows and UNIX platforms.

    Note

    For Windows, the user ID of the PAS must be defined in uppercase. For the UNIX operating system, the user ID of the PAS must be defined in lowercase. In addition, the user ID of the PAS must also be assigned to the mqm group.

To test the connection

  1. Validate that the channels are started.
  2. Validate that the command server is started on the distributed systems platforms.
  3. Type CON distributedSystemsQueueManagerName on the COMMAND line.
  4. On the EZMQS view, select the Queue Manager Details menu option to see information about the queue name that you specified in step 3.

    You should be able to see the distributed systems queue managers.

    Note

    If you cannot connect, follow the instructions in Problem determination for return code 07F1 when using a proxy.

    Not all views and functions apply in a proxy environment. For more information, see Viewing information on MVS proxy and agent based systems.

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

Comments