Installation error messages

This section describes messages, produced during execution of the BMC AMI Capacity Management products, which might be related to errors that occurred during product installation.

Each message listed is followed by an explanation of the likely problem and a suggested solution. Messages are grouped by product.

Number

Description

BES0001E

Not enough contiguous memory to load HMC

Explanation: Not enough memory is available to load the BMC AMI Capacity Management load module. The lack of available memory is probably due to one of the following:

  • Too small a region at log on.
  • Other products were loaded into memory before BMC AMI Capacity Management and did not leave enough available memory.
  • You specified a larger than intended load module (such as XLARGE instead of LARGE).

User response: The simplest way to handle this problem is to log on with a larger TSO region size. For example, type: LOGON yourid s(6000). See System-requirements-for-product-installation for specific product memory requirements.

Alternatively, you can try ending any split sessions or restarting ISPF.

BES0006E

ERROR in ALLOCATING: xxx

Explanation: Several data sets must be allocated for BMC products to run. This problem arises when a CLIST cannot allocate one of the data sets specified in Customization Section 1 of the CLIST.

User response: Make sure that the data set name associated with the error message has been specified correctly and refers to an existing data set.
Determine this by typing either of the following: 

  • From an ISPF command line
TSO LISTDS 'fully.qualified.dsname'
  • From native TSO

LISTDS 'fully.qualified.dsname'
In response, TSO provides the current status of this data set. If the data set is not found, unload the data set from tape and try again.

BES9003E

INVALID ALLOCATION DDNAME ALREADY ALLOCATED

Explanation: This problem arises when BMC AMI Capacity Management is unable to allocate a data set most likely the LOGFILE.

User response: Make sure to use the current B1 CLIST to run the product.

If you are using the current B1 CLIST, then you need to determine whether there are any conflicting allocations.

Type the following command on an ISPF command line:

TSO LISTA ST HIS

TSO describes your current file allocations. Make sure you have no potential conflicts by eliminating any noncritical allocations.

BGS0009E

CACHEC ERROR IN aaa ALLOCATIONS. EXECUTE THE CACHEC CLIST USING THE DEBUG OPTION TO DETERMINE THE CAUSE. IN ADDITION, CHECK MEMBER mmm OF THE CLIST LIBRARY hiqual.midqual.CLIST FOR CORRECT SYNTAX AND DATA SET NAME SPECIFICATIONS

Explanation: An allocation error has occurred. The string aaa identifies whether the error is an ISPF or CLIST allocation. The string mmm identifies a member in the CLIST library. The string hiqual.midqual. CLIST identifies the CLIST library.
If the error is in the ISPF allocations, most likely the offending allocation statement is in the BGSINIT CLIST. If the error is in the CLIST allocations, most likely the offending allocation statement is in the BGSPROC CLIST.

User response: To obtain more information on the location and nature of the error, run the CACHEC CLIST in DEBUG mode. See Special parameters for product invocation CLISTs for information regarding the DEBUG option.

Make sure that the data set name associated with the allocation error has been specified correctly and that the data set has the appropriate attributes. 


Problem Unknown B1MVSGP fails with no messages

Explanation: If, for any reason, B1MVSGP fails, and there are no informative messages, run it again with the debug parameter DRIVER. All of the TSO lists and messages will be displayed at your terminal, and in all probability, the difficulty will become apparent. The most likely possibilities are:

  • An error in one of the concatenation lists failure in a dynamic allocation
  • Failure to allocate the errors file
  • Deletion of a continuation character

User response: Run B1MVSGP with the DEBUG(DRIVER) parameter. Note and correct all errors.


New variable values not initialized

Explanation: You have changed the values for parameters in Customization Section 1, but in the BMC AMI Capacity Management menu, those values are not initialized. For example, you are pointing to a previous version, even though the current version is installed.

User response: Try the following:

  • Check values in Customization Section 1.
  • If you are using ISR@PRIM, make sure that it contains the correct syntax for this release; see Choosing an invocation method for the correct syntax.
  • Eliminate previous versions of the BMC AMI Capacity Management menu from the current concatenation lists.


FILE filename NOT FREED, DATASET IS OPEN

Explanation: If a data set is open, z/OS will not allow it to be freed. This might be confusing because the message can arise before the product is even invoked. The probable area of concern is LIBDEFs. The effect of the LIBDEF function is that new ISPF libraries can be dynamically associated with an already allocated ISPF DDName. Once the link is made, even before the product is called, the new (temporary) DDName cannot be freed.

User response: A LIBDEF must be issued first to break the link between the ISPF DDName and the corresponding temporary DDName associated with BMC AMI Capacity Management. Then, issue a FREE statement and the temporary DDName will be freed. Verify the area of CLIST code that handles the LIBDEFs has not been altered. 


FILE filename NOT UNALLOCATED, DATA SET IS OPEN

Explanation: When running the MVUIE CLIST, this message could occur if an ISPF library has been allocated using the LIBDEF utility, and has not been freed before this attempt.

User response: ALIBDEF must be issued first to break the link between the ISPF DDname and the corresponding temporary DDname associated with BMC AMI Capacity Management. Then, issue a FREE statement and the temporary DDname will be freed. Verify that the area of CLIST code that handles the LIBDEFs has not been altered.


Concatenation problems for SYSPROC

Explanation: Some of the allocation problems that could occur with SYSPROC (CLIST libraries) are:

  • TSO displays the following message –
    'DATA SETS NOT CONCATENATED, COMBINING UNLIKE DATA SET ORGANIZATIONS IS INVALID.'
  • B1 member not found.

User response: When allocating CLISTs, there are two critical rules to follow:

  • Never try to mix record formats, such as trying to concatenate VB and FB data sets.
  • If the data sets have different block sizes, you must concatenate them with the largest block size first. Since BMC recommends that a BMC CLIST be placed first in the concatenation list, be sure that its block size is at least equal to the largest block size in the list.

 

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