XMA: Msg#:217 Level:Critical Msg:ServerClass MQREADER (\node.$XMA) Maximum retries (24) reached on email alerts

XMA: Msg#:217 Level:Critical Msg:ServerClass MQREADER (\node.$XMA) Maximum retries (24) reached on email alerts

The setting for the max retries can be configured from XMA_MANAGER.  The steps to change the configuration of the max retries are as follows:
 
TACL> Volume <XMA installation SUBVOLUME> (ie. VOLUME $<VOL>.XYGATEMA)
TACL> XMA INSTALL (To attach the XYGATEMA TACL segment)
TACL> XMA_MANAGER
Select 2:  MOVERS
Select 17: CONFIGURE MAIL QUEUE SERVER
Select 5:   MAXIMUM RETRIES
Press ENTER at this prompt for the default or enter a new value: Please enter the Maximum retries <24>  ?
Select R: RUN
Select X: to EXIT the XMA_Manager
 
To verify if there is any data in the mail files located in the XMADAT SUBVOL, run the following statements from SQLCI:
 
TACL> VOLUME $<VOL>.XMADAT
TACL> SQLCI
=select count (*) from mailbody browse access;
=select count (*) from mailids browse access;
=select count (*) from mailto browse access;
 
Note:  If the SQL replies shows that records exist in any one of those tables, the user should pay attention to the timestamp. If that timestamp is recent, then SLSENDER may not have got them out yet. However, if the timestamp is old, the user needs to determine why those emails are being sent.
 
If this article did not provide a solution, please open a case with our support team by sending an email message to support@xypro.com.