IC42064: MAXNUMMP DESCRIPTION IN THE TSM 5.2 ADMIN REFERENCES IS INACCURATE

APAR status

• Closed as program error.

Error description

• In third edition of the Administrator's References we read for
  the maxnummp option of the register node and update node
  command:
  "MAXNUMMP
  Specifies the maximum number of mount points a node is allowed
  to use on the server or storage agent. The parameter is
  optional. The default value is 1. You can specify an integer
  from 0-999. A value of 0 specifies that a node cannot acquire
  any mount point for a backup or archive operation. The server,
  however, will still allow the node a mount point for a restore
  or retrieve operation. .."
  This is inaccurate since users do not get information about
  1. how many mount points a node can use simultaneously for
  restore or retrieve and
  2. how many mount points a node can use simultaneously for hsm
  migrate or recall operations
  We should improve the documentation
  by modifying this paragraph e.g. like follows: "MAXNUMMP
  Specifies the maximum number of mount points a node is allowed
  to use on the server or storage agent for backup and archive
  operations only. The parameter is optional. The default value
  is 1. You can specify an integer from 0-999. A value of 0
  specifies that a node cannot acquire any mount point for a
  backup or archive operation. However the node will still get
  one or more points for a restore or retrieve operation. Also a
  node's HSM migrate or recall operations are not affected by the
  maxnummp setting .."
  additional keywords: tsm itsm
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Tivoli Storage Manager users of          *
  *                 Version 5.2 and subsequent releases.         *
  ****************************************************************
  * PROBLEM DESCRIPTION: The MAXNUMMP parameter in the           *
  *                      REGISTER NODE, UPDATE NODE, and QUERY   *
  *                      NODE commands should be updated.        *
  *                      The description should explain that     *
  *                      the parameter is only for client data   *
  *                      store                                   *
  *                      operations such as backup, archive,     *
  *                      and HSM migration. Updated text         *
  *                      should also include                     *
  *                      that the number of mount points a       *
  *                      node can use concurrently for           *
  *                      restore, retrieve, and                  *
  *                      HSM recall operations are not affected. *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The MAXNUMMP parameter in the REGISTER NODE, UPDATE NODE, and
  QUERY NODE
  commands of the Administrator's Reference and associated
  command line help
  was updated.
  The updated documentation will be available in the next
  release. The associated online help will be
  available in level 5.2.5. Note that this is subject to change
  at the discretion of IBM.
  

Problem conclusion

• Updated text follows for the MAXNUMMP parameter:
  
  Specifies the maximum number of mount points a node is allowed
  to use on
  the server or storage agent only for operations such as
  backup, archive, and
  HSM migration. The parameter is optional. The default value is
  1. You can
  specify an integer from 0-999. A value of 0 specifies that a
  node cannot acquire
  any mount point for a client data store operation. The
  MAXNUMMP value is not
  evaluated or enforced during client data read operations such
  as restore, retrieve,
  and HSM recall. However, mount points in use for data read
  operations are evaluated
  against attempted concurrent data store operations for the
  same client node and
  may prevent the data store operations from being able to
  acquire mount points.
  

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

• R52A PSY

     UP

• R52H PSY

     UP

• R52L PSY

     UP

• R52P PSY

     UP

• R52S PSY

     UP

• R52W PSY

     UP

• R52Z PSY

     UP