Correcting a rank-related configuration error

Complete this task to correct a rank-related configuration error.

There might be occasions when you are using the mkrank command to create ranks, but the transaction fails. You might not be aware of the failure until you run the lsrank or showrank command to check the status of the ranks that you have created.

The lsrank or the showrank commands display reports that includes a state category. The state category reports on the current state of the rank. One of the state codes is configuration error.

A state of configuration error specifies that a rank configuration process has not completed successfully. This state reflects an internal error condition and is not an indication that there was a user input error.

You might want to gather additional information about what caused the error, which can help you determine how to correct it. Generally, to correct this error state, you must delete the designated rank configuration and submit a new transaction request.

Perform the following steps to obtain additional information about the configuration error and to correct this error condition.

  1. Obtain additional information about the transaction by implementing one of the following methods:
    • Add the -v (verbose) command flag to your mkrank command and reissue the command for the transactions that show the configuration error designation.
      Note: You can also turn on the verbose mode in your profile file and reissue the command.

      Designating the verbose mode allows the display of extra output that includes the error code that is generated when the create rank transaction fails.

    • Add the -extpool parameter to your mkrank command and reissue the command for the transactions that show the configuration error.

      You might consider using this parameter if you have not yet assigned your ranks to the extent pools. If the transaction fails, a message states the reason for a failure.

  2. Issue the rmrank command to delete the designated rank configurations if you do not want to obtain additional information about what caused the configuration error.
    Note: In the majority of instances, this is the only method for correcting a configuration error.
Library | Support | Terms of use | Feedback
© Copyright IBM Corporation 2004, 2007. All Rights Reserved.