Writer instructions | |
|---|---|
Page title | For most spaces, this page must be titled Space announcements. For spaces with localized content, this page must be titled Space announcements l10n. |
Purpose | Provide an announcement banner on every page of your space. |
Location | Move this page outside of your home branch. |
Guidelines | |
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 MVMMTopic Service. | None |
MQS0111W | This message appears after a connection attempt by the extensible agent (QPEA) to the MVMMTopic Service has failed. It does not indicate why the connection attempt failed but indicates that QPEA continues to attempt to connect to the MVMMTopic Service. | See message MQS0113W |
MQS0113W | An attempt to connect to the MVMMTopic 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 MVMMis 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 MVMMcannot 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 MVMMto 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 | WebSphere 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 WebSphere 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 MVMMagent extended monitoring task for the specified queue manager is beginning initialization. | None. |
QPZ0002I | The MVMMagent extended monitoring task for the specified queue manager is beginning termination. | None. |
QPZ0011I | The MVMMagent extended monitoring task for the specified queue manager has initialized. | None. |
QPZ0012I | The MVMMagent 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 Websphere 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 Websphere 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. |
BTM z/OS agent error messages
Message ID | Description | Response |
|---|---|---|
BTM0001I | The BTM address space has completed its initialization without error and is ready for monitoring. Build= is followed by the date and time that the BTMMAIN code was last modified. | None. This information is requested by BMC Support. |
BTM0002I | The Websphere MQ monitoring exit has been loaded into storage. The level of the loaded exit is also shown. | None. This information is requested by BMC Support. |
BTM0003I | Successful communication between the Websphere MQ monitoring exit and BTM has been established. The level of the exit is also shown. | None. This information is requested by BMC Support. |
BTM0004I | This is the storage location and length of the BTM Websphere MQ monitoring exit. | None. This information is requested by BMC Support. |
BTM0005I | The BTM monitoring control subtask has started successfully. Build= is followed by the date and time that the BTMMCS code was last modified. | None. This information is requested by BMC Support. |
BTM0006I | The BTM monitoring control subtask has been notified of a configuration change. | None. |
BTM0007W | The BTM monitoring control subtask could not find a matching queue manager for one of the configuration requests. | Check the queue managers specified in the model processed by MVMM Configuration Agent and verify against the defined queue managers on the target system. |
BTM0010I | BTM is in the process of terminating. Under normal circumstances this is the result of issuing the Stop command. | None |
BTM0011I | BTM has completed its termination process; this is immediately followed by address space termination. | None |
BTM0015I | The BTM task has been terminated with a request to remove the Websphere monitoring exit and it has been removed successfully. | None. |
BTM0016W | The name/token delete request issued at BTM task termination failed with the indicated return code. | This message is issued when the BTM task is terminated with a request to remove the Websphere monitoring exit and an error occurred when removing the name/token entry. The exit code has been removed. This is generally not a problem and should not affect the next start of the BTM task. If the message persists, contact BMC Support with all of the available information. |
BTM0020E | BTM has determined that another BTM address space, using the same jobname, is currently active in this z/OS image. The BTM address space terminates following this event. | If the desire is to have one active BTM address space, then no action is required. Under normal circumstances there is no need for more than one BTM address space to be active, although if you are trying to run multiple BTM address spaces on the same z/OS image then each additional BTM address space must have a unique jobname. Change the jobnames of the additional BTM address spaces and resubmit the jobs. |
BTM0021E | An error occurred while attempting to ENQ on a BTM resource. The error code returned by the ENQ service is indicated in the rc field. | Contact BMC Support with all of the available information. |
BTM0030I | Queue manger qmgr has terminated. BTM reconnects to the queue manager when it is available. | If the queue manager terminated under normal circumstances then no action is required. If queue manager termination was unexpected, determine the cause of the problem and restart the queue manager. |
BTM0031I | BTM has detected the start of queue manager qmgr and can resume monitoring. | None |
BTM0032W | The PCW entry for the specified queue manager was not found. | If this is the first time a model has been configured for this queue manager, this is not a problem. However, if it does occur with a previously modeled queue manager, recycle the BTM task. If the message persists, contact BMC Support with all of the available information. |
BTM0033I | The BTM monitoring task for the specified queue manager terminated by user request. | None. |
BTM0034I | The specified queue manager is not being monitored by BTM. | This is usually caused by having a queue manager active at one time, terminating it, then specifying the queue manager in a new model. Check the model and queue manager status and make changes as necessary. |
BTM0035I | The specified queue manager is not currently being monitored by BTM. | This is usually caused by having a queue manager active at one time , specifying it in a model, terminating it, then specifying the queue manager in a new model. Check the model and queue manager status and make changes as necessary. |
BTM0044W | Unable to load diagnostic routine. The system was unable to load the BTMDIAG module. | None. If an abend occurs, limited diagnostic information is printed. |
BTM0045W | A different version of the BTMPC module was detected at startup, possibly due to an upgrade or a regression. The control block structure is compatible between the versions, so the older code was replaced. | Verify that the version of the code was changed, whether by upgrade, regression, or by applying a fix. If the version was not changed, contact BMC Support with all of the available information. |
BTM0046W | A different version of the BTMPC module was detected at startup, possibly due to an upgrade or a regression. The control block structure is incompatible between the versions, so the older code and control blocks were deleted, and the BTM environment was reinitialized. | Verify that the version of the code was changed, whether by upgrade, regression, or by applying a fix. If the version was not changed, contact BMC Support. Do not use PARM='REMOVE' unless requested by BMC Support, as this can cause loss of ECSA. |
BTM0047E | The load library containing BTM load modules must be APF authorized. | Add the BTM load library to the system APF authorized library list and restart the BTM address space. Consult with your MVS Systems Programmer for more information regarding this procedure. |
BTM0048E | An error occurred attempting to load program QPMSGS from the BTM load library. | Ensure BTM was installed properly and that program QPMSGS is available to the BTM address space, then restart the job. |
BTM0049E | An error occurred attempting to load program BTMMSGS from the BTM load library. | Ensure BTM was installed properly and that program BTMMSGS is available to the BTM address space, then restart the job. |
BTM0050I | MVMM Configuration Agent issued a configuration change request. | None. |
BTM0051E | An internal error occurred while processing a change request for the specified queue manager. | Contact BMC Support with all of the available information. |
BTM0052W | Communication has been lost with the specified queue manager. | If the queue manager has been shut down, this is a normal message. Otherwise, investigate why the queue manager is no longer active. |
BTM0053I | Communication has resumed with the specified queue manager. | None. |
BTM0054I | All configuration changes requested by MVMMConfiguration Agent for the specified queue manager are complete. | None. |
BTM0055I | All configuration changes requested by MVMMConfiguration Agent are complete. | None. |
BTM0056I | MVMMConfiguration Agent requested that monitoring stop for the specified queue manager. | None. |
BTM0057I | Changes requested by MVMM Configuration Agent for the specified queue manager (already being monitored) are complete. | None. |
BTM0058I | Changes requested by MVMMConfiguration Agent for the specified queue manager (newly being monitored) are complete. | None. |
BTM0059I | Changes requested by MVMMConfiguration Agent for the specified queue manager (already being monitored) are complete. Significant differences in the monitored data were specified. | None. |
BTM0060E | BTM has found no queue managers defined to this z/OS image. | If there are no queue managers defined to the z/OS image then no action is required. If a queue manager is defined, then contact BMC Support with all of the available information. |
BTM0061E | An error occurred while attempting to establish the console services subtask. The error code returned by the MCS service is indicated in the rc and rsn fields. | Consult the chapter discussing MCSOPER REQUEST=ACTIVATE in IBM manual MVS Auth Assembler Services Reference Vol 3: LLA-SDU for information regarding the meanings of the return and reason codes. If you are unable to determine and correct the cause of the problem, contact BMC Support with all of the available information |
BTM0062E | An unrecoverable error occurred during console services processing. The error code returned by the MCS service is indicated in the rc and rsn fields. | Consult the chapter discussing MCSOPMSG REQUEST=RESUME in IBM manual MVS Auth Assembler Services Reference Vol 3: LLA-SDU for information regarding the meanings of the return and reason codes. If you are unable to determine and correct the cause of the problem, contact BMC Support with all of the available information |
BTM0063I | The specified queue manager is defined in IEFSSNnn but is not active. Monitoring does not start. | None. |
BTM0064I | The specified queue manager was in a monitoring request; however, no queues were specified to be actually monitored. | Check the model definition and change if necessary |
BTM0070E | Module load failure (@@@@@@@@) | Ensure BTM was installed properly and that the BTM load library is available to the BTM address space, then restart the job. |
BTM0071W | The QPMAT program was unable to be loaded, so generic list monitoring support has been disabled. | Recycle the BTM task. If the message persists, check the console log for messages indicating problems with the loading of the QPMAT module, and contact BMC Support with all of the available information. |
BTM0072W | Another BTM task is already monitoring CICS in this system. | Only one BTM task can monitor CICS in a system. Check the EXEC PARM for inadvertent duplication. If the message persists, contact BMC Support with all of the available information. |
BTM0073W | This BTM task was unable to start monitoring CICS. A return code is specified. | Recycle the BTM task. If the message persists, contact BMC Support with all of the available information. |
BTM0074I | CICS monitoring is available. | None. |
BTM0080E | Storage was unable to be obtained for the Websphere MQ monitoring exit. | 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. |
BTM0081E | The requested storage was unable to be obtained for a list of items to be monitored for the specified queue manager. The return code from the storage request is also shown. | 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. |
BTM0082W | Storage was unable to be obtained for generic monitoring of queues. | 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. |
BTM0083E | Storage was unable to be obtained for communication between the Websphere MQ monitoring exit and BTM. Monitoring is disabled. | 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. |
BTM0084E | The requested storage was unable to be obtained for a list of generic items to be monitored for the specified queue manager. The return code from the storage request is also shown. | 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. |
BTM0086I | The CICS monitoring subtask has started. | None. |
BTM0087W | The BTM configuration watchdog did not start. BTM is not notified of configuration changes. | Recycle the BTM task. If the message persists, check the console log for messages indicating problems with the starting of the watchdog task, and contact BMC Support with all of the available information. |
BTM0088E | An error occurred attempting to initiate a message processing thread for queue manager qmgr. The error code returned by the thread initiation service is indicated in the rc field. | Contact BMC Support with all of the available information. |
BTM0089E | The CICS monitoring subtask could not be started. | Recycle the BTM task. If the message persists, check the console log for messages indicating problems with the starting of the CICS monitoring task, and contact BMC Support with all of the available information. |
BTM0090E | An error occurred during SRB execution used to establish the environment required to monitor queue manage message traffic. The comp, code, and rsn values are returned by the SRB scheduling service and indicate the cause of the error. | Consult the chapter discussing IEAMSCHD in IBM manual MVS Auth Assembler Services Reference Vol 2: ENF-IXG for information regarding the meanings of the error codes. If you are unable to determine and correct the cause of the problem, contact BMC Support with all of the available information. |
BTM0091E | An unexpected and undetermined error has occurred that prevents BTM from successfully initializing. | Locate any abend or system messages that precedes this message, correct the error, and restart the BTM address space. If you are unable to determine or correct the error, contact BMC Support with all of the available information. |
BTM0092E | The internal limit on the number of times BTM recovers from message processing errors and restart message processing threads has been reached. In order to prevent recursive abends, BTM is terminating. | This message follows other error messages that have been issued by BTM. Review the job log for previous errors and respond based on the specific errors. |
BTM0093W | An error has occurred in the message processing agent and the BTM main task is attempting to recover from the error and restart the process. If recovery is successful, message BTM0094I follows. If recovery is not successful, message BTM0085E follows. | None |
BTM0094I | The BTM main task has successfully recovered from a message processing agent failure and has restarted the agent. | None. |
BTM0095E | The BTM main task was unable to recover from a message processing agent failure and must terminate. | Check the job log for messages regarding the error that preceded the restart attempt and take appropriate action. |
BTM0096E | An error occurred in the BTM console services subtask from which the BTM main task could not recover. BTM terminates following this message. | Check the job for messages regarding the error that occurred in the console services subtask and take appropriate action. |
BTM0097E | An error occurred attempting to attach the message processing agent. The error code returned by the attach service is indicated in the rc field. | Consult the chapter discussing ATTACHX in IBM manual MVS Auth Assembler Services Reference Vol 1: ALE-DYN for information regarding the meanings of the return code. If you are unable to determine and correct the cause of the problem, contact BMC Support with all of the available information |
BTM0098E | An error occurred attempting to attach the console services subtask. The error code returned by the attach service is indicated in the rc field. | Consult the chapter discussing ATTACHX in IBM manual MVS Auth Assembler Services Reference Vol 1: ALE-DYN for information regarding the meanings of the return code. If you are unable to determine and correct the cause of the problem, contact BMC Support with all of the available information. |
BTM0099E | BTM terminating due to initialization failure, RC=@@ | Locate the error that precedes this message, correct the error, and restart the BTM address space. If you are unable to correct the error, contact BMC Support with all of the available information. |
BTM0100I | BTM has successfully connected to and is actively monitoring queue manger qmgr. This normally occurs following queue manager or BTM initialization, or as a result of a monitoring configuration change. | None. |
BTM0101I | BTM has stopped monitoring queue manager qmgr. This normally occurs during queue manager or BTM termination, or as a result of a monitoring configuration change. | None. |
BTM0102I | Configuration information has instructed BTM to monitor queue manager qmgr, but the queue manager is currently inactive and unable for monitoring. | If it is normal for the queue manager to be inactive, then no action is required. If not, start the queue manager and BTM automatically connects to the queue manager following successful initialization. |
BTM0103I | BTM was instructed, via console modify command (F qpbtm,CON=qmgr), to connect to queue manager qmgr' but BTM is already actively monitoring the queue manager. | None. |
BTM0104I | BTM was instructed, via console modify command (F qpbtm,DIS=qmgr), to disconnect from queue manager qmgr' but BTM is already disconnect and is not actively monitoring the queue manager. | None. |
BTM0105I | The BTM configuration watchdog module has been loaded. | None. |
BTM0106E | The QPBTMWD module was unable to be loaded, so BTM is unable to be notified of configuration changes. | Recycle the BTM task. If the message persists, check the console log for messages indicating problems with the loading of the QPBTMWD module, and contact BMC Support with all of the available information. |
BTM0109W | An invalid modify command has been issued to BTM. The command identified in the invalid-modify-command field of the message and the command is ignored. | Correct and reissue the command. |
BTM0120E | The BTMSNAP DD statement, required for generating diagnosis information, is missing. | Add the BTMSNAP DD statement to the BTM task JCL per the instructions from BMC Support, and recycle the BTM task. |
BTM0130W | A storage shortage has occurred in the BTM task address space. Monitoring has been temporarily disabled until the shortage clears. Information is lost during the shortage. | 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. |
BTM0131I | The storage shortage identified in the prior BTM0130W message has been relieved. Monitoring has resumed. | None. |