z/OS agent error messages
This section describes the informational, warning, and error messages for MainView Middleware Monitor (MVMM ) on z/OS.
Suffix key listed in order of severity:
- I=Information
- W=Warning
- E=Error
- S=Severe
- C=Critical
Message ID | Description | Response |
|---|---|---|
MQS0033S | A severe error has occurred. The agent is terminating with an abend. | Check the log for other messages and address appropriately. If necessary, contact Support with all of the available information. |
MQS0100I | These messages provide environmental information that might be useful in problem situations. The information displayed includes the version of LE and TCP/IP. | None. |
MQS0110I | These messages present information as related to the communication from the z/OS agent to the MVMM Topic Service. | None |
MQS0111W | This message appears after a connection attempt by the extensible agent (QPEA) to the MVMM Topic Service has failed. It does not indicate why the connection attempt failed but indicates that QPEA continues to attempt to connect to the MVMM Topic Service. | See message MQS0113W |
MQS0113W | An attempt to connect to the MVMM Topic Service has failed. | Determine if the MVMM Topic Service is available on the computer specified. The MVMM Topic Service host is in the preceding MQS0110I message. If you cannot ping the MVMM Topic Service host from the failing computer it is possible the host specified isn't resolving to the proper IP address or that the MVMM Topic Service computer is not available. If you determine the computer is available and that the MVMM Topic Service (Qpserver.exe) is running the problem is most likely a name resolution problem. You can verify this by specifying the IP address of the MVMM Topic Service host in the EAAXML file and restarting the extensible agent (Qpea). Consult with your TCP/IP systems programmer to resolve this. |
MQS0115I | The Extensible Agent (QPEA) has connected to the MVMM Topic Service. | None. |
MQS0120I | An agent is connecting to the extensible agent (QPEA). This message indicates that MVMM is establishing its inter process communication. | None. |
MQS0123W | Either the configuration (QPCFG) or monitoring agent (QPMON) was unable to establish a connection with the extensible agent (QPEA). | If QPEA has been started this usually indicates MVMM cannot determine the IP address of the local computer. The local IP address is determined with the gethostid API. If you issue the console command D TCPIP,xxxxx,N,HOME, replacing xxxxx with the TCP/IP started task name, the address that would be returned by this API is flagged with a P. This is the primary interface in your home list. In earlier releases of TCP/IP it is the first address in your home list. Your TCP/IP systems programmer should research the above issues. Call BMC Support for additional assistance. |
MQS0125I | An agent has established a inter process communication link to the extensible agent (QPEA). In the case of QPMON a link is established for each sub task. | None. |
MQS0126I | This message immediately follows MQS0125I and indicates a date and time the communication link was established. | None. |
MQS0128I | The Configuration Agent (QPCFG) is connecting to the extensible agent (QPEA) to initiate or complete a monitoring configuration change. | None. |
MQS0129I | This message immediately follows the MQS0128I message and indicates a date and time that a MVMM monitoring configuration change was initiated or completed. | None. |
MQS0131S | The TCPNAME= parameter was not in the parameter on the JCL EXEC statement. This is required for MVMM to establish a TCP/IP environment on the proper stack. | Check the PARM on your EXEC statement insure that TCPNAME= with the correct TCP/IP start task / job name. |
MQS0132S | Unable to establish the TCP/IP environment so the program ends. | See message MQS0131S |
MQS0133I | Each queue manager is monitored by a separate sub task. The sub task is being created. | None. |
MQS0135I | Information about page sets is not available when a queue manager is down. | Wait until the queue manager is started and retry the request. |
MQS0137I | A monitoring sub task has been created and monitoring for the selected objects has begun. | None. |
MQS0138W | A queue manager selected for monitoring is unavailable. The monitoring task tries to connect to the queue manager once per sample interval. Once the queue manager is available and monitoring has started a MQS0137I message is issued. | Ensure the queue manager is available and that the monitoring agent (QPMON) is permitted to use it. |
MQS0139I | Monitoring has stopped for the indicated queue manager. This message also appears when QPMON is being stopped or monitoring configuration changes are being made. If monitoring configuration changes are being made the message is followed by a MQS0137I message for the same queue manager, provided objects are still selected for monitoring. | None. |
MQS0201I | The QEDIT macro failed. Operator commands are not accepted. | Recycle the task (this might require use of the CANCEL command). If the message persists, contact Support with all of the available information. |
MQS0201W | MVMM was unable to establish communication with the operator console. The job or task might not respond to the stop command. Ex. P QPEA. | None. |
MQS0202I | The QEDIT macro failed and no CIB was available. Operator commands are not accepted. | Recycle the task (this might require use of the CANCEL command). If the message persists, contact BMC Support with all of the available information. |
MQS0202W | MVMM was unable to establish communication with the operator console. The job or task might not respond to the stop command. Ex. P QPEA. | None. |
MQS0203I | The task now accepts operator commands. | None. |
MQS0204I | An MODIFY (F) operator command was issued against the task. | None. |
MQS0205I | An STOP (F) operator command was issued against the task. | None. The task terminates. |
MQS0206W | The command is not known to the task and is ignored. | Check and retry the command. If necessary, contact BMC Support with all of the available information. |
MQS0301W | IBM MQ command server is not responding to MVMM requests. | Make sure that the command server has started and that MVMM has the authority needed to use it. |
MQS0302S | After multiple MQS0301W messages this message is issued. This indicates that the command server is still not responding to MVMM and it needs to be investigated. | See message MQS0301W. Investigate as soon as possible. Monitoring at this point is ineffective. Contact BMC Support for additional assistance. |
MQS0303S | Since IBM MQ command server is not responding to requests for information, monitoring on one or more queue managers is no longer functional. | See message MQS0301W. After addressing the problem restart QPMON. |
MQS0364W | Not in an APF authorized load library. Some functionality is not available. This functionality includes starting queue managers and monitoring Buffer Pools. | Consult with your systems programmer prior to taking any action. If you want the above functionality you might want to APF authorize the load library. To verify the accuracy of this message you can issue the D PROG,APF,ALL command. Note that if any library in the steplib concatenation is not APF authorized then none of the libraries are considered APF authorized. To APF authorize a library you can issue the SETPROG command. To insure that the library remains APF authorized you should update the PROGxx member of your SYS1.PARMLIB. |
MQS0401I | A name/token pair creation was attempted by the WAS extension, but it was already defined. | This usually occurs if another MVMM WAS extension is started with the same name as an already active one. Bring down the duplicate task, and start under another name, if necessary. |
MQS0403I | These messages provide environmental information for the WAS extension that might be useful in problem situations. The information displayed includes the version of LE and TCP/IP. | None. |
MQS0405I | An attempt was made by the WAS extension to delete a previously-established name/token pair, but the request failed. | This is generally not a problem and should not affect the start of the WAS extension. If the message persists, contact BMC Support with all of the available information. |
MQS0406I | The name/token delete request issued at WAS extension termination failed with the indicated return code. | This message is issued when the WAS extension task is terminated and an error occurred when removing the name/token entry. This is generally not a problem and should not affect the next start of the WAS extension. If the message persists, contact BMC Support with all of the available information. |
MQS0407I | The WAS extension is attempting to connect to TCP/IP. | None. |
MQS0408W | The TCP/IP connect failed. | Investigate and address appropriately. If the message persists, contact BMC Support with all of the available information. |
MQS0409I | The TCP/IP connection initialized successfully. | None. |
MQS0500S | Not enough region is available. | Increase the region as indicated in the message and restart the monitoring agent. |
MQS0700W | A general TCP/IP error occurred. Specific information might be present in the message | Check the log for other messages indicating what type of connect request failed and address appropriately. If the message persists, contact BMC Support with all of the available information. |
MQS0701W | A socket connect failed. | Check the log for other messages indicating what type of connect request failed and address appropriately. If the message persists, contact BMC Support with all of the available information. |
MQS0702W | These messages provide additional environmental information for the associated TCP/IP error that might be useful in problem situations. The information displayed includes the version of LE and TCP/IP. | None. |
MQS0704W | A socket accept failed. | Check the log for message MQS0755W which has more information about the error, and address appropriately. If the message persists, contact BMC Support with all of the available information. |
MQS0705W | A socket select failed. | Check the log for message MQS0755W which has more information about the error, and address appropriately. If the message persists, contact BMC Support with all of the available information. |
MQS0706W | Establishment of a socket failed. | Check the log for message MQS0755W which has more information about the error, and address appropriately. If the message persists, contact BMC Support with all of the available information. |
MQS0710W | TCP/IP environment initialization failed. | Check the log for message MQS0755W which has more information about the error, and address appropriately. If the message persists, contact BMC Support with all of the available information. |
MQS0755W | A TCP/IP Call has returned a non-zero return code. | This message is preceded by a message that indicates the API that had the problem. This message is followed by the numerical error code. The description of this error code can be found in the IBM TCP/IP documentation under the System error codes for socket calls. For TCP/IP version 3.2 these error codes are listed in section D.1 of the API reference. The API reference is document number SC31-7187-03 for TCP/IP 3.2. The API reference for Communications Server on z/OS 2.10 is SC31-8516-04. The API reference for Communications Server on z/OS 1.4 is SC31-8791-02. If you are unable to determine the cause of this problem and it persists, contact BMC Support for additional support. |
MQS0790I | The TCP/IP environment is being established. | None. |
MQS0791I | The connection to TCP/IP has been established. | None. |
MQS0793W | The connection to TCP/IP failed. | Determine if the named TCP/IP stack is available. See the preceding MQS0100I messages for information regarding the status of TCP/IP. Contact BMC Support. |
MQS0794W | No more space available on the EAAXML dataset. | Shut down the MVMM Extensible Agent and extensions. Back up your EAAXML. Allocate a larger EAAXML. Restore using your back up copy EAAXML. Start the MVMM Extensible Agent and extensions. |
MQS0801I | A request to allocate storage from the Language Environment (LE) heap failed. LE storage was not allocated for buffer pool monitoring. | Increase the LE heap allocation units on the QPMON EXEC card. |
MQS9999E | An error occurred when generating a WTO message. The message number is included. | Contact BMC Support with all of the available information. |
QPZ0001I | The MVMM agent extended monitoring task for the specified queue manager is beginning initialization. | None. |
QPZ0002I | The MVMM agent extended monitoring task for the specified queue manager is beginning termination. | None. |
QPZ0011I | The MVMM agent extended monitoring task for the specified queue manager has initialized. | None. |
QPZ0012I | The MVMM agent extended monitoring task for the specified queue manager has terminated. | None. |
QPZ0020E | The specified target queue manager is not at a supported version. | Change parameters so that the queue manager is not to be monitored. If this is a new release of IBM MQ, contact BMC Support for any maintenance or support information. |
QPZ0021E | The specified queue manager is not active or not defined. | Check the parameters and correct as necessary. If it persists, contact BMC Support with all of the available information. |
QPZ0046W | Storage could not be obtained to transfer a copy of an SMF record. Some information is not available. | Verify the various LE storage-related parameters, REGION and/or MEMLIMIT EXEC or JOB parameters, and/or the amount of limits being set by the IEFUSI SMF exit. If enough storage is being allocated, contact BMC Support with all of the available information. |
QPZ0047E | APF authorization is required for the use of SMF fields. The subtask is terminated. | Although APF authorization is usually optional, it is required to retrieve certain information about IBM MQ via SMF. See message MQS0364W for more information. |
QPZ0048C | The message routine could not be loaded. The task terminates. | Verify the REGION and/or MEMLIMIT EXEC or JOB parameters, and/or the amount of limits being set by the IEFUSI SMF exit. If enough storage is being allocated, contact BMC Support with all of the available information. |
QPZ0049C | The message table could not be loaded. The task terminates. | Verify the REGION and/or MEMLIMIT EXEC or JOB parameters, and/or the amount of limits being set by the IEFUSI SMF exit. If enough storage is being allocated, contact BMC Support with all of the available information. |
QPZ0070E | The specified program cannot be loaded. | Contact BMC Support with all of the available information. |
QPZ0071E | The name/token entry created by the agent cannot be found. The return code is shown. | Contact BMC Support with all of the available information. |
QPZ0090E | Unable to establish monitoring environment with Qmgr @@@@, | The type of system service is usually discernible from the keyword displayed. If possible, investigate the return and reason codes for the service and address appropriately. If the issue persists, contact BMC Support with all of the available information. |
QPZ0092E | The cross-memory environment could not be initialized. Return and reason codes are specified. | Contact BMC Support with all of the available information. |
QPZ0098E | The agent service task could not be attached. | Contact BMC Support with all of the available information. |