RESLEVEL security profiles control the number of userids checked for API-resource security. RESLEVEL security will not be implemented due to the following exposures and limitations: RESLEVEL is a powerful option that can cause the bypassing of all security checks. Security audit records are not created when the RESLEVEL profile is utilized. If the WARNING option is specified on a RESLEVEL profile, no warning messages are produced. To protect against any profile in the MQADMIN or MXADMIN class, such as ssid.**, resolving to a RESLEVEL profile, a ssid.RESLEVEL profile will be defined for each queue manager with UACC(NONE) specified and no users or groups specified in the access list. Ensure the following items are in effect: Note: ssid is the queue manager name (a.k.a., subsystem identifier). A RESLEVEL resource (i.e., ssid.RESLEVEL) is defined for each queue manager to the MQADMIN or MXADMIN resource class with a UACC(NONE). Access authorization to these RESLEVEL resources restricts all access. No users or groups must be specified in the access list. A set of sample commands is provided below to implement the profile necessary for proper security. RDEF MQADMIN <ssid>.RESLEVEL UACC(NONE) OWNER(ADMIN) AUDIT(ALL(READ)) DATA('MQADMIN PROFILE REQUIRED BY ZWMQ0060') SETR RACL(MQADMIN) REF Note that an additional WebSphere MQ Refresh may be required for active queue managers. This is done from the CONSOLE: The example is for a queue manager named QMD1: >QMD1 REFRESH SECURITY(*)