You must now consider how you are going to implement any security controls for WebSphere MQ.
If you use RACF(R) as your external security manager, see Setting up security, which describes how to implement these security controls.
If you are using queue-sharing groups, ensure that the user IDs associated with the queue manager, channel initiator, and the utilities (as specified in step 6) have authority to establish a RRSAF connection to each DB2(R) subsystem with which you want to establish a connection. The RACF profile to which the user ID requires READ access is DB2ssid.RRSAF in the DSNR resource class.
If you are using the channel initiator, you must also do the following:
Those queue managers that will access the Coupling Facility list structures require the appropriate security access. The RACF class is FACILITY. The queue manager user ID requires ALTER access to the IXLSTR.structure-name profile.
If you are using RACF, provided you use the RACF STARTED class, you do not need to IPL your system (see RACF authorization of started-task procedures).
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
csq834f |