IT13305: DECOMMISSIONED STATUS OF PENDING IS NOT DOCUMENTED.

APAR status

• Closed as documentation error.

Error description

• A node that has not been decommissioned has a "Decommissioned"
  state that is blank. Once a node has been fully decommissioned
  the "Decommissioned" field in query or select from nodes output
  shows as YES. However there is a time frame and/or situations
  where this decommission state could be PENDING. A Pending state
  can appear in both the query and select from nodes output. What
  this state means is not documented anywhere. What action to take
  if this state persists is also not documented. Both the meaning
  and action for a pending decommission need to be documented.
  Tivoli Storage Manager Versions Affected: 7.1.3 and above
  servers on all platforms
  Initial Impact: Low
  Additional Keywords: Spectrum Protect
  

Local fix

• If a decommissioned node is sitting in a pending state try
  running the decommission node command again. Look for any errors
  in the actlog associated with the decommission processing for
  the node if the state remains pending.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All Tivoli Storage Manager server users.                     *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See error description.                                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Update documentation as needed.                              *
  ****************************************************************
  

Problem conclusion

• In the Administrator's Reference, in the QUERY NODE command, the
  description of the Decommissioned field will be updated:
  
  "Decommissioned
  Specifies whether the client node is decommissioned. The
  following values are possible:
      YES
          Specifies that the node is decommissioned.
      Null
          Specifies that the node is not decommissioned.
      PENDING
          Specifies that the node is being decommissioned, or the
  decommission process failed.
  
      Tip: If you want to determine the status of a pending
  decommission process, follow the instructions in
  'Decommissioning a client node.'"
  
  In the Single-Site Disk Solution Guide and Multisite Disk
  Solution Guide, in the "Decommissioning a client node" topic,
  the following information will be added in the "What to do next"
  section:
  
  "Watch for error messages, which might be displayed in the user
  interface or in the command output, immediately after you run
  the process. You can verify that the client node is
  decommissioned:
      1. On the Operations Center Overview page, click Clients.
      2. In the Clients table, in the At risk column, review the
  state:
          - A DECOMMISSIONED state specifies that the node is
  decommissioned.
          - A null value specifies that the node is not
  decommissioned.
          - A PENDING state specifies that the node is being
  decommissioned, or the decommission process failed.
  
      Tip: If you want to determine the status of a pending
  decommission process, issue the following command:
      query process
  
      Review the command output:
          - If status is provided for the decommission process,
  the process is in progress. For example, you might see
  output that is similar to this example: NODE1: 8 objects
  deactivated.
          - If no status is provided for the decommission process,
  and you did not receive an error message, the process is
  incomplete. A process can be incomplete if files that are
  associated with the node are not yet deactivated. After the
  files are deactivated, run the decommission process again.
          - If no status is provided for the decommission process,
  and you receive an error message, the process failed. Run the
  decommission process again."
  
  Affected platforms:  AIX, HP-UX, Solaris, Linux, and Windows.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels