Messages LG1100 through LG1199

ERROR DURING INITIALIZATION

Explanation: The initialization routine was unable to initialize the LGTASK. BBI will continue without the journal logging task.

User response: Contact BMC Support.

COULD NOT ACCESS BBISSPxx MBR

Explanation: An attempt was made to access BBIPARM library member BBISSPxx to get the current settings for the MVLOG and MVLOGSS keywords. The access attempt has failed. Processing terminates with return code 16.

User response: Verify that the parmlib member shown in the message is available and retry the request that failed. If the problem persists, contact BMC Software for assistance.

CONNECT FAILED. MV LOGGER(xxxx) NOT DEFINED

Explanation: An attempt to connect the Logger identified by SSID xxxx has failed. The identified logger is not currently active in the LPAR. Processing terminates with return code 16.

User response: Verify that the named Logger is available in the same LPAR as the BBI-SS PAS and retry the request. The Logger SSID is derived from the BBISSPxx specification for MVLOGSS.

• Review BBPARM member BBISSPxx for MVLOG and MVLOGSS parameters. MVLOGSS can be used to override the default MV Logger SSID.
• If BMC AMI Ops Automation is active in this PAS, also review BBPARM members AAOEXPxx, AAOALSxx, or AAOPRMxx for various Logger options.

BBI Control Command .D BB,L can be used to determine which BBPARM members are in use in this PAS.

If the problem persists, contact BMC Software Support for assistance.

CONNECT FAILED. MV LOGGER ABENDED. RSN(nnnn)

Explanation: An attempt to connect the MV Logger has failed. The MV Logger API has reported that MV Logger has abended and is not currently available. Processing terminates with return code 16.

User response: Make the required MV Logger available in the same LPAR as the BBI-SS PAS and retry the request. If the problem persists, contact BMC Software for assistance.

API CALL REJECTED, MV LOGGER(xxxx) INACTIVE

Explanation: An attempt to connect the MV Logger has failed. The MV Logger API has rejected the call. The SSID (xxxx) of the MV Logger is shown in the message. Processing terminates with return code 16.

User response: Make the required MV Logger available in the same LPAR as the BBI-SS PAS and retry the request. If the problem persists, contact BMC Software for assistance.

CONNECT FAILED. MV LOGGER(xxxx) WAS STOPPED

Explanation: An attempt to connect the MV Logger has failed. The MV Logger started task was stopped by some external process and cannot be accessed. The SSID (xxxx) of the MV Logger is shown in the message. Processing terminates with return code 16.

User response: Make the required MV Logger available in the same LPAR as the BBI-SS PAS and retry the request. If the problem persists, contact BMC Software for assistance.

CONNECT FAILED. MV LOGGER(xxxx) HAS DATA SPACE WRAP

Explanation: An attempt to connect the MV Logger has failed. The MV Logger API has reported that the MV Logger task is experiencing a problem due to a wrap-around problem with its data space. The SSID (xxxx) is shown in the message. Processing terminates with return code 16.

User response: Correct the problem in MV Logger and retry the request. If the problem persists, contact BMC Software for assistance.

MV LOGGER(xxxx) CONNECT FAILED. RC=rr RSN=nn

Explanation: An unexpected return code was received from the MV Logger API during a connection attempt. The SSID (xxxx) of the MV Logger is shown in the message along with the return code (rr) and the reason code (nn). Processing terminates with return code 16.

User response: Correct the problem in MV Logger and retry the request. If the problem persists, contact BMC Software for assistance.

MV LOGGER CONNECTION MADE WITH: ssss, jjjjjjjj

Explanation: A successful connection has been completed with the MV Logger identified by SSID of ssss and job name of jjjjjjjj. Processing continues normally.

User response: No action is required.

ALREADY CONNECTED TO MV LOGGER ssss, jjjjjjjj

Explanation: The current BBI-SS PAS already has an active connection to the MV Logger identified by SSID of ssss and job name of jjjjjjjj. Processing continues normally.

User response: No action is required.

MV LOGGER LOGGING STOPPED WITH: ssss, jjjjjjjj

Explanation: The active connection with the MV Logger identified by SSID of ssss and job name of jjjjjjjj. Processing continues normally.

User response: No action is required.

MV LOGGER LOGGING NOT ACTIVE...STOP NOT NEEDED

Explanation: No active connection with the MV Logger identified by SSID of ssss and job name of jjjjjjjj was found. The STOP command is ignored and processing continues normally.

User response: No action is required.

MV LOGGER(xxxx) WRITE FAILED. RC=rr RSN=nn   

Explanation: An attempt to log (write) a record to the MV Logger identified by xxxx in the message has failed. The return code (rr) and reason code (nn) from the MV Logger API interface are shown. The attempt to log the journal record to Logger is discarded and the discarded count is increased by 1. The PAS will assume that this error requires a reconnection to Logger. After this error, the PAS will attempt to reconnect every 60 seconds for the next hour. After the first hour, reconnect attempts will occur every 5 minutes. During this period, journal records will not be logged in Logger.

User response: The BBI Control Command .D MVL will display information about the connection to Logger. The output of this command will show you information such as the Logger STC name and SSID, as well as the date and time of the last failure. Determine the nature of the problem using the return and reason codes listed below, and correct any errors under your control. Report all other errors to BMC Software support. Most Return Code / Reason Codes indicate an internal error has occurred and should be reported to BMC Support. However, some errors are a result of site-specific problems and can be resolved without the assistance of Support. The most common error under the user's control is RC=08 RSN=04. Return code=08 Reason=04 indicates Logger is out of buffers, or rather that the rate at which records are being logged exceeds the buffers defined for this logspace. The user defines the buffer size in the DIVBLOCKS setting for Logger.

To increase the DIVBLOCKS for this logspace do the following:

• Increase the DIVBLOCKS=nnnn for the logspace.
• Increase the size of the DIV dataset indicated in DIVDSN.
• Stop and restart Logger with the RESET option such as:
  S mvlogger,RESET=RESET

Documentation for the implementation and customization of Logger can be found in:

• the section titled "Managing BMC AMI Ops Logger" in the "BMC AMI Ops Infrastructure" online documentation
• the section titled "Manual Customization" in the "BMC AMI Ops Infrastructure" online documentation

ATTEMPTING TO CONNECT TO MV LOGGER

Explanation: An informational message that indicates a (re)connection attempt is about to be made to Logger. Processing continues normally.

User response: Review the log for a following message that will indicate the outcome of the attempt. The Logger SSID is derived from the BBISSPxx specification for MVLOGSS.

If this message is unexpected, review options in BBPARM members:

• Review BBISSPxx for MVLOG and MVLOGSS parameters. MVLOGSS can be used to override the default MV Logger SSID.
• If BMC AMI Ops Automation is active in this PAS, also review AAOEXPxx for EMLOG parameters. 

BBI Control Command .D BB,L can be used to determine which BBPARM members are in use in this PAS.

AUTO-CONNECT WITH MV LOGGER(xxxx) ABANDONED

Explanation: The auto-connect feature of the BBI-SS journal has been unsuccessful. The system attempted to connect up to 60 times over the course of at least 60 minutes without success. No further automatic attempts to connect to the requested MV Logger will be made.

User response: Verify the state of the requested MV Logger and correct any problems with it. Then manually connect to the MV Logger using the .Start MVLOG BBI-SS command.

MV LOGGER NOT STARTED. LOGGING NOT REQUESTED

Explanation: A request to start MV Logger was processed but MVLOG=NO was specified (or defaulted to) in parmlib member BBISSPxx. A connection is not made and processing continues.

User response: No action is required.

MVLOG=YES IN BBISSP00 NOT RECOMMENDED. USE MVLOG=JRNL

Explanation: The 'YES' value for the MVLOG= keyword has been detected. The 'YES' value is functionally stabilized and will be removed entirely on Aug 31,2009. The 'YES' value has been superseded by the 'JRNL' value. Processing continues normally using the older format MV Logger records and the LOGMSG command/view.

User response: Change the MVLOG=YES parm to specify MVLOG=JRNL and begin using the new LOGJRNL command/view to access journal data in MV Logger. Specifying MVLOG=JRNL provides a richer interface to MV Logger via the LOGJRNL command/view. When using MVLOG=JRNL, the older LOGMSG command/view will not show any data. Only LOGJRNL will show data when MVLOG=JRNL is used.

EMLOG write failed on Logger xxxx. RC=rr RSN=nn

Explanation: An attempt to log (write) an EXEC Message Log (EMLOG) record to the MV Logger identified by xxxx in the message has failed. The The return code (rr) and reason code (nn) are shown. The EMLog record is discarded and the discarded count is increased by 1. The system will attempt to reconnect to the MV Logger every 60 seconds for the next hour.

User response: Determine the nature of the problem using the return and reason codes and correct the problem. If the problem persists, contact your BMC Software support representative.

MV LOGGER BUFFER CAPACITY EXCEEDED. REVIEW MV LOGGER DIVBLOCKS FOR LOGSPACE

Explanation: An attempt to log (write) a record to the Logger has failed. This return code and reason code indicates that Logger processing has exceeded the defined DIVBLOCKS for this logspace. This message is issued as a follow up to LG1132E to further describe the error. Processing continues as described in the explanation for LG1132E.

User response: The BBI Control Command .D MVL will display information about the connection to Logger. The output of this command will show you information such as the Logger STC name and SSID, the date and time of the last failure, the number of discarded messages, and other information. Return code=08 Reason=04 indicates Logger is out of buffers, or rather that the rate at which records are being logged exceeds the buffers defined for this logspace.  The user defines the buffer size in the DIVBLOCKS setting for Logger.

To increase the DIVBLOCKS for this logspace do the following:

1. Increase the DIVBLOCKS=nnnn for the logspace.
2. Increase the size of the DIV dataset.
3. Stop and restart Logger with the RESET option such as: S mvlogger, RESET=RESET

Documentation for the implementation and customization of MV Logger can be found in:

• the section titled "Managing BMC AMI Ops Logger" in the "BMC AMI Ops Infrastructure" online documentation.
• the section titled "Manual Customization" in the "BMC AMI Ops Infrastructure" online documentation.