Messages BBMZL400 through BBMZL499

This topic contains messages for the 

BMC AMI Ops Infrastructure

product.

Number

Description

BBMZL400I

MVI/NGL INITIALIZATION COMPLETE

Explanation: All initializations for MVI and NGL are complete.

User response: No action is necessary.

BBMZL401E

DBC ARG ARRAY INVALID

Explanation: MVI Agent has encountered an invalid array pointer from the DBC.

User response: Contact BMC Support.

BBMZL402I

VERSION systime / sysdate


Explanation: This message displayes the MVI Agent release date and time of the BBM9ZLNG module.

User response: Contact BMC Support.

BBMZL403I

DBC QIF ADDRESS INVALID

Explanation: MVI Agent detected an invalid QIF control block from DBC. Initialization is incomplete.

User response: Contact BMC Support.

BBMZL404I

DBC ARG2 ADDRESS INVALID

Explanation: MVI Agent detected an address from DBC argument that is invalid. Initialization is incomplete.

User response: Contact BMC Support.

BBMZL405I

UNABLE TO LOCATE NGLID IN PARM, RETRY 

Explanation: MVI Agent could not locate the PIID for NGL. Initialization is incomplete.

User response: Locate the XML that specifies the PARMS value and make sure it specifies the NGLID keyword. Contact BMC Support.

BBMZL406W

NGLID NOT PASSED IN PARMS 

Explanation: MVI Agent could not locate the NGLID.

User response: Locate the XML that specifies the PARMS value and make sure it specifies the NGLID keyword. For more information, contact BMC Support.

BBMZL407E

SEND TO DBC FOR SUBSCRIBE FAILED. 

Explanation: MVI Agent was unable to subscribe to the DBC.

User response: Locate the XML that specifies the PARMS value and make sure it specifies the NGLID keyword. For more information, contact BMC Support.

BBMZL408W

WARNING CLIENT LOADLIBS NOT LOADED 

Explanation: MVI Agent was unable to load the LOADLIB data sets to be used for viewing.

User response: Contact BMC Support.

BBMZL409E

UNABLE TO CREATE GLOBAL NAME/TOKEN 

Explanation: MVI Agent was unable to create a GLOBAL name token.

User response: Contact BMC Support.

BBMZL410E

ERROR LOAD NEWCOPY OF BBM9ZLSP 

Explanation: MVI Agent was unable to LOAD module BBM9ZLSP.

User response: Check your SMPe install jobs. If you need further, contact BMC Support.

BBMZL411I

NGLTERM RECEIVED. TERMINATING 

Explanation: MVI Agent has received a termination request from NGL to Shutdown.

User response: No action is necessary.

BBMZL412I

NGLSTART RECEIVED INITIALIZING. 

Explanation: MVI Agent has received an initialization request from NGL. This indicates that an MVI agent will start initializing.

User response: No action is necessary.

BBMZL413E

POSSIBLY NOT ALL CONVERTED DATA WILL FIT 
DSMAX=XXXXXXXX . NEEDED DSMAX=XXXXXXXX

Explanation: MVI Batch log conversion to NGL will not fit in the current allocation structure with possibly wrapping the current logs. The current DSMAX and SPACE values are used to determine if the data will fit without wrapping the NGL logs. For your current DSMAX and SPACE values, see member MVINGIxx.

User response: Review the ALLOWLOGWRAP=YES/NO keyword. In this case, NO was specified, meaning that all data will attempt to be loaded without wrapping and possibly losing data. If YES is specified, all data will be loaded no matter if the logs wrap. Review DSMAX in member MVINGIxx. The required value for DSMAX to make sure it does not wrap is the 'NEEDED DSMAX=XXXXXXXX'.

BBMZL414I

TERMINATION REQUESTED 

Explanation: MVI Agent received a termination request from DBC/NGL.

User response: No action is necessary.

BBMZL415E

UNABLE TO LOAD AND START BBM9ZLCS 

Explanation: MVI Agent could not load the console support module.

User response: Contact BMC Support.

BBMZL416I

MVI AGENT TERMINATION ENTERED 

Explanation: MVI Agent is processing termination of this agent.

User response: No action is necessary.

BBMZL417I

CONSOLE SUPPORT SHUTDOWN 

Explanation: Termination of console support started.

User response: No action is necessary.

BBMZL418W

MVI AGENT TERMINATION INCOMPLETE 

Explanation: Termination of MVI Agent did not completely finish.

User response: No action is necessary.

BBMZL419I

MVI AGENT TERMINATION COMPLETE 

Explanation: Termination of MVI Agent completed successfully.

User response: No action is necessary.

BBMZL420E

UNABLE TO ALLOCATE GLOBAL WORKAREA 

Explanation: MVI Agent was unable to allocate storage for an internal control block.

User response: Initialization is stopped and the MVI agent is not started. Contact BMC Support.

BBMZL421E

ERROR ON DBC READ 

Explanation: DBC read request failed.

User response: Initialization is stopped and the MVI agent is not started. Contact BMC Support.

BBMZL422E

DBCIAPI LOAD FAILED 

Explanation: DBC API failed.

User response: No further action is required. Initialization is stopped and the MVI agent is not started. Contact BMC Support.

BBMZL423W

CONNECT WAS UNSUCCESSFUL 

Explanation: MVI Agent's attempt to connect to an NGL LOGSET was unsuccessful.

User response: The LOGSET is unusable and no other processing can be done for the LOGSET. For more information, contact BMC Support.

BBMZL424W

INFO CALL UNSUCCESSFUL 

Explanation: MVI Agent issued an INFO call for a LOGSET. An invalid return code was returned.

User response: The LOGSET is unusable and no other processing can be done for the LOGSET. For more information, contact BMC Support.

BBMZL425E

UNABLE TO ALLOCATE STORAGE FOR AMGG 

Explanation: MVI Agent was unable to allocate a 4K page ECSA storage boundary. Initialization is terminated and LOGSET information is retained.

User response: After ECSA has been relieved, restart the DBC.

BBMZL426W

DEFAULTLOGGER ALREADY ACTIVE 

Explanation: MVI Agent detected there is already a defaultlogger defined for your LPAR. The defaultlogger is not used for the SSID and LOGSPACE specified.

User response: Correct the LOGGERxx member that specifies DEFAULTLOGGER=YES and restart.

BBMZL427W

UNABLE TO ENQ BBM0ZLNG QNAME 

Explanation: MVI Agent was unable to enq on module BBM0ZLNG during initialization. Initialization waits until this ENQ can be obtained.

User response: No action is necessary.

BBMZL428E

LXRES FAILURE 

Explanation: MVI Agent was unable to process an LXRES request.

User response: Contact BMC Support.

BBMZL429E

ETCRE FAILURE 

Explanation: MVI Agent was unable to process an ETCRE request.

User response: Contact BMC Support.

BBMZL430E

ETCON FAILURE 

Explanation: MVI Agent was unable to process an ETCON request.

User response: Please contact BMC Support.

BBMZL431E

AMGG NOT FOUND 

Explanation: MVI Agent internal control block not found.

User response: Gather the DBC joblog and contact BMC Support.

BBMZL432W

UNABLE TO DEQ QNAME BBM0ZLNG 

Explanation: MVI Agent unable to dequeue on QNAME BBM0ZLNG. The QNAME resource was not available. Initialization continues for MVI Agent.

User response: No action is necessary.

BBMZL433I

Waiting for NGLSTART 

Explanation: MVI Agent waiting for NGL to post the NGLSTART message.

User response: No action is necessary.

BBMZL434I

PIID(xxxx) Located for NGL Processing 

Explanation: MVI Agent will located the NGL PIID for MVL processing.

User response: No action is necessary.

BBMZL435I

PIID(xxxx) Unable to locate NGL 

Explanation: MVI Agent was unable to locate out NGL for MVL processing.

User response: For more information, contact BMC Support.

BBMZL436I

PIID(xxxx) Locate NGL for MVL 

Explanation: MVI Agent will attempt to locate NGL for MVL processing.

User response: For more information, contact BMC Support.

BBMZL437E

Unable to start MVLOGGER/MVL Agent 

Explanation: MVI Agent was unable to complete initialization.

User response: For more information, contact BMC Support.

BBMZL438E

member MEMBER NOT LOCATED 

Explanation: MVI Agent initialization has stopped. member represents the LOGGERxx member that could not be located.

User response: Make sure all LOGGERxx members are located in either the PARMDSN= PDS value or using LOGS= keyword value. The PARMDSN keyword is found in member MVINGIxx. This member contains initialization values for 6.1.01.

The LOGS keyword is located in the startup XML used to define the MVI Agent. LOGGERxx members will be searched in one but not both of those locations. For more information about this member, see

Some content is unavailable due to permissions.

. Correct and restart the DBC.

BBMZL439W

Correct and continue 

Explanation: MVI Agent initialization has stopped. There was an error before this message describing the error.

User response: Correct the error and restart the DBC.

BBMZL440I

XXXXXXXX IS BEING USED FOR CONFIGURATION

Explanation: This informational message indicates the MVINGIxx member being used for configurations.

User response: No action is necessary.

BBMZL441E

ALLOC ERROR CODE(errorCode), REASON CODE(reasonCode)

Explanation: MVI Agent was unable to dynamically allocate all files needed for initialization. MVI Agent stops running.

User response: Gather JES log for the DBC and contact BMC Support.

BBMZL442W

NO LOGGERXX MEMBERS WERE PROCESSED

Explanation: MVI Agent found no LOGGERxx members to process. Either no SYSP= keyword value was found or the LOGGERxx members could not be located.

User response: Gather JES log for the DBC and contact BMC Support.

BBMZL443E

SEVERE ERROR(S) FOUND, CORRECT AND RETRY

Explanation: MVI Agent found errors during XML and LOGGERxx member processing. This message will be accompanied by another specific message.

User response: Gather JES log for the DBC and contact BMC Support.

BBMZL444E

SSID=ssid LOGSET=logset

Explanation: MVI Agent found errors during XML and LOGGERxx processing for the specified SSID and LOGSPACE/LOGSET.

User response: Gather JES log for the DBC and contact BMC Support.

BBMZL445E

DUPLICATE LOGSSID logssid SPECIFIED, RETRY

Explanation: MVI Agent found errors during XML and LOGGERxx for the specified SSID. You can only have one unique SSID specified per image.

User response: Correct the LOGGERxx member and restart the DBC.

BBMZL446E

DUPLICATE LOGSPACE logspace SPECIFIED, RETRY

Explanation: MVI Agent found errors during XML and LOGGERxx for the specified LOGSPACE. All LOGSPACE names must be unique for an SSID.

User response: Correct the LOGGERxx member and restart the DBC.

BBMZL447E

MVI/NGL INITIALIZATION NOT COMPLETE

Explanation: Initialization for MVI and NGL is not complete.

User response: Check for the messages that caused this error and take appropriate action.

BBMZL449I

CONNECTED TO DBCID=dbcid AND NGLID=nglid

Explanation: This informational message indicates the DBCID and NGLID being used for this MVI Agent.

User response: No action is necessary.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*