Overview

We try to keep the need to install PTFs to a minimum for QMessage Monitor. Unfortunately, this cannot be avoided if the APIs that we use have errors that require correction. This topic provides a brief explanation of which API or MI interface the PTF is fixing and whether it is a mandatory or an optional requirement.

 

V7R2M0

SI57660, superseded by SI57959

If you're using the IBM i built-in email server to send out emails from QMessage Monitor, you must install this PTF. If you don't install it, your QMSF jobs could end suddenly, which would cause email delivery for the IBM i built-in email server to stop. See APAR SE62717 for IBM’s explanation.

QMessage Monitor can send out email using one of three methods: (a) using the IBM i built-in email server, (b) using the QMessage Monitor SMTP client, and (c) using QRemote Control. Most new users will use (b). If you're using method (b) or (c), you don't need to apply the PTF. Note: If you're using escalation to send out emails from QMessage Monitor, and the escalation users have notification routes with the Pager Company set to “MM” or “RC” only, then you're using method (b) or (c) and don’t need to apply the PTF.

 

V7R1M0

SI49254

Mandatory

If you use the QHST monitoring function, you must install this PTF. If you don't install it and you notice “Function check. MCH5803 unmonitored by QMHOLHST at statement *N, instruction X'013B'” messages in a joblog, your system might be going down. See APAR SE54643 for IBM’s explanation.

SI46653, superseded by SI52642

If you use the Database Server monitoring function and are also using QSystem Monitor and you then notice “MCH0601: Message . . . . : Space offset X'0000200C' or X'0000000000000000' is outside current limit for object” messages in a joblog you can install this PTF to remove the problem. See APAR SE48665 (superseded by APAR SE51782) for IBM’s explanation.

 

V6R1M0

SI30590

Mandatory

You can now use new message data types (*UTC, *UTCD, *UTCT) in message descriptions. Some IBM-supplied messages have changed to use the new UTC message variable data types, for example CPF1124 (Job started) and CPF1164 (Job ended). The underlying API will not return the correct data without this PTF. See APAR SE31769 for IBM’s explanation.

SI46144

Mandatory

If you use the QHST monitoring function, you must install this PTF. If you don't install it and you notice “Function check. MCH5803 unmonitored by QMHOLHST at statement *N, instruction X'013B'” messages in a joblog, your system might be going down. See APAR SE50788 for IBM’s explanation.

SI46652, superseded by SI50447

If you use the Database Server monitoring function and are also using QSystem Monitor and you then notice “MCH0601: Message . . . . : Space offset X'0000200C' or X'0000000000000000' is outside current limit for object” messages in a joblog you can install this PTF to remove the problem. See APAR SE48665 (superseded by APAR SE51782) for IBM’s explanation.

 

V5R4M0

SI39982, superseded by SI44836

This PTF is not compatible with QMessage Monitor. To prevent compatibility issues, remove SI39982 or install SI35216.

SI27853 and SI43447
(SI43447 is superseded by SI48028)

If the MM4000 job fails on start-up and you notice a sequence that contains MCH3601, CPF4204 and SQL0901 messages in the program dump, the resolution is to load and apply SI27853 and SI43447. See APAR SE47807 for IBM’s explanation.

 


Still have questions? We can help. Submit a case to Technical Support.

Last Modified On: January 11, 2018