Environment
AppManager 5.x
AppManager 6.0.x
AppManager for UNIX 6.5
NetIQ AppManager Managed Object for WebSphereMQ
Discovery_WebSphereMQUNIX Knowledge Script
Sun Solaris
SuSE Linux
Red Hat Linux
IBM AIX
HP-UX
FreeBSD
Situation
The completion code (mqcc) for the mqexecute commands is two, which is failure, but in the AppManager UNIX agent log (nqmlog), completion code is zero.
Log file reports: '... mqExecute][Command Test Exit]][MQCC:2 MQRC:0]'
Log file reports: '... mqExecute][Command Test Exit]][MQCC:2 MQRC:0]'
Resolution
Set
DEFPSIST to NO for SYSTEM.ADMIN.COMMAND.QUEUE.Cause
DEFPSIST to is set to YES for
Additional Information
Formerly known as NETIQKB52634
The MQDiscovery module does not specify the message persistence. When persistence is not explicitly defined, the value from the pre-set DEFPSIST variable is used.
Since the request message is a persistent message, the reply message is also persistent. Since the reply queue is a temporary dynamic queue, and requires messages to be non-persistent, the reply is put to the DEADQ.