Messages BBSX700 through BBSX799

BBSX701W

JOBNAME MQTQPINI INIT CALL, RC=xxxxxxxx RSN=yyyyyyyy DANB=zzzzzzz

Explanation: This is a Warning message indicating that the connection to the Logger was attempted.

User response: If this is a console message, Contact BMC support for further instructions. If this message is in BMCMSGLG and not in SYSLOG then you may ignore it unless you are experiencing no data being logged by this queue manager.

BBSX702W

JOBNAME MQTRTERM Xyyyy CELLS EXHAUSTED. AS A RESULT THERE WERE Xzzzzzzzz STORAGE OBTAINS IN MQ PRIVATE

Explanation: This is a Warning message indicating that the MQTCPOOL was exhausted if zzzzzzzz is non-zero.

User response: If zzzzzzzz is a large number, increasing MQTCPOOL for the next start of BMC Extensions for MQ will reduce the number of storage.

BBSX703I

MQE request for ssid

Explanation: This is an informational message indicating that the request to make the change in MQE status was requested from the PAS.

User response: None.

BBSX704I

command using ddname:dsname

Explanation: This is an informational message indicating that the DSN used for DDNAME in the message, this is related to BBSX703I message.
User response: See message BBSX705I and/or the queue manager job log for more information

BBSX705I

command RC=nnn(xxxxxxxxx) Response: <text response data

Explanation: This is an informational message indicating that the response to the request referred to in the BBSX703I message.

User response: None.

BBSX706I

JOBNAME ******** MQTASSRB ended for QMGR

Explanation: This is an information message to indicate that the ZIIP processing routine MQTASSRB running in JOBNAME for QMGR has terminated

User response: If MQE is not ending because of Queue Manager Shutdown, JOBNAME ending or removal or replacement for MQE, contact BMC support for MVMQ.

BBSX709W

JOBNAME MQTAINIT DBCID REQUIRED FOR EXTERNAL LOGGING, USING NGL INTERNAL LOGGING.

Explanation: NGL is required for external logging when PASDATA is set. MQE will not log to MVLOGGER in this mode. Trace data will be logged to an area in the PAS dataspace, and will not be hardened.            

User response: Change EXITOPT to include the information for NGL to harden the data to NGL logfiles. Remove the LOGSSID and LOGSET parms to log internally and not see this message.

BBSX710I

JOBNAME MQT*MLOG - LOGGER INSERT CALLS SUCCESSFUL, TRACE RECORDS WRITTEN TO LOGGER

Explanation: This is an informational message indication that data is being written to logger.

User response: NONE

BBSX711W

JOBNAME MQT*MLOG - LOGGER INSERT CALLS FAILING, TRACE RECORDS NOT WRITTEN TO LOGGER, RC=xxxxxxxx RSN= yyyyyyyy

Explanation: This is a Warning message indicating that trace data is not being logged, because the connection to the logger is unavailable. When the logger is available will be written to the logger. 

User response: Verify that DBC and NGL are active. Check EXITOPT that NGL parms (LOGSSID, LOGSET and DBCID) are specified properly. If everything appears correct, contact BMC customer support.