Messages will be put into queue SYSTEM.ADMIN.QMGR.EVENT when the queue manager has one of more of the following controls enabled.

• AUTHOREV (some sort of authority issue, such as a bad username/password)
• INHIBTEV (inhibit)
• LOCALEV (local event)
• REMOTEEV (remove event)
• STRSTPEV (some issue starting or stopping something)

The display qmgr command can be used to determine which of these controls are enabled. This example is based on IBM MQ running on a Linux system, and the name of the queue manager is MANAGER01.

~]$ echo "display qmgr AUTHOREV INHIBTEV LOCALEV REMOTEEV STRSTPEV" | runmqsc MANAGER01
   QMNAME(MANAGER01)                       AUTHOREV(ENABLED)
   INHIBTEV(ENABLED)                       LOCALEV(DISABLED)
   REMOTEEV(DISABLED)                      STRSTPEV(ENABLED)

The amqsbcg command can be used to view the messages in SYSTEM.ADMIN.QMGR.EVENT. The output can be helpful in getting something useful, such as the name of the application that is attempting to do something, or the target queue or topic or channel.

<mq install>/samp/bin/amqsbcg SYSTEM.ADMIN.QMGR.EVENT MANAGER01

AMQSBCG0 - starts here
**********************

 MQOPEN - 'SYSTEM.ADMIN.QMGR.EVENT'

 MQGET of message number 1
****Message descriptor****
  StrucId  : 'MD  '  Version : 2
  Report   : 0  MsgType : 8
  Expiry   : -1  Feedback : 0
  Encoding : 546  CodedCharSetId : 850
  Format : 'MQEVENT '
  Priority : 0  Persistence : 0
  MsgId : X'414D51207361575749447474405D30033563DB8'
  CorrelId : X'000000000000000000000000000000000000000000000000'
  BackoutCount : 0
  ReplyToQ       : '                                                '
  ReplyToQMgr    : 'MANAGER01                                       '
  ** Identity Context
  UserIdentifier : '            '
  AccountingToken :
   X'0000000000000000000000000000000000000000000000000000000000000000'
  ApplIdentityData : '                                '
  ** Origin Context
  PutApplType    : '7'
  PutApplName    : 'MANAGER01        '
  PutDate  : '19970417'    PutTime  : '15115208'
  ApplOriginData : '    '
 
  GroupId : X'000000000000000000000000000000000000000000000000'
  MsgSeqNumber   : '1'
  Offset         : '0'
  MsgFlags       : '0'
  OriginalLength : '104'

****   Message      ****
 
 length - 104 bytes
 
00000000:  0700 0000 2400 0000 0100 0000 2C00 0000 'RFH.............'
00000010:  0100 0000 0100 0000 0100 0000 AE08 0000 '....MQSTR   ....'
00000020:  0100 0000 0400 0000 4400 0000 DF07 0000 '........<mcd><Ms'
00000030:  0000 0000 3000 0000 7361 7475 726E 2E71 'd>jms_text</Msd>'
00000040:  7565 7565 2E6D 616E 6167 6572 2020 2020 '</mcd>  ...L<jms'
00000050:  2020 2020 2020 2020 2020 2020 2020 2020 '><Dst>queue:///Q'
00000060:  2020 2020 2020 2020 2020 2020 2020 2020 'UEUE01</Dst><Tms'
00000070:  2020 2020 2020 2020 2020 2020 2020 2020 '>1552628162482</'
00000080:  2020 2020 2020 2020 2020 2020 2020 2020 'Tms><Dlv>2</Dlv>'
00000090:  2020 2020 2020 2020 2020 2020 2020 2020 '</jms>  Hello Wo'
00000100:  2020 2020 2020 2020 2020 2020 2020 2020 'rld             '

 No more messages
 MQCLOSE
 MQDISC

Additionally, the AMQ error log may have something useful, like this.

----- amqalmp0.c : 610 --------------------------------------------------------
mm/dd/yyyy hh:mm:ss - Process(2925.32) User(mqm) Program(amqrmppa)
                    Host(server1.example.com) Installation(Installation1)
                    VRMF(9.1.0.3) QMgr(MANAGER01)
                    Time(yyyy-mm-ddThh:mm:ss.sss)
                    RemoteHost(10.1.2.3)
                    CommentInsert1(10.4.5.6)
                    CommentInsert2(TCP/IP)
                    CommentInsert3(CHANNEL01)

AMQ9209E: Connection to host '10.1.2.3' for channel 'CHANNEL01'
closed.

EXPLANATION:
An error occurred receiving data from '10.1.2.3' over TCP/IP.  The
connection to the remote host has unexpectedly terminated.

The channel name is 'CHANNEL01'; in some cases it cannot be determined
and so is shown as '????'.
ACTION:
Tell the systems administrator.

After you determine what caused messages to be put into SYSTEM.ADMIN.QMGR.EVENT, you may want to use the clear qlocal command to purge the messages from SYSTEM.ADMIN.QMGR.EVENT.

echo "clear qlocal ('SYSTEM.ADMIN.QMGR.EVENT')" | runmqsc MANAGER01