Maintaining pool and subpool definitions
The suffix of the members is specified in the system member, SMMSYSxx. The definitions within these members become the active configuration that is used in all product components. The active configuration can be viewed in the GPCNFG view and other views on the Configuration menu.
When the VARY command is used to cause a volume to come online, the volume is immediately available in any pool or subpool in which it is included for Allocation, Reporting, and Automation activities.
The order of the pool definition SET statements in the SMPOOLxx member can make a difference. The Allocation component allows a volume to exist in only one pool. This pool will be the first pool in the SMPOOLxx member, going from top to bottom, to include the volume. For the Allocation component, the volume will not exist in any subsequent pool that attempts to include the volume. The Reporting and Automation components allow a volume to be included in up to eight pools. Again, the order can make a difference because the volume will exist only in the first eight pool definitions in the SMPOOLxx member.
You can reduce the number of times that the definitions need to be updated by using the volume selection and wildcard capabilities of the INC and EXC statements when defining a pool. When updates are necessary, BMC AMI Storage allows these updates to be made on-the-fly. Members can be viewed and edited in the BMC AMI Ops Infrastructure interface. After a member is edited, it can be refreshed, making the contents of the member the active configuration and, therefore, available to all other BMC AMI Storage components. This process can be completed from the ADMEMA view, which is accessible from the Parmlib Members menu.
The pool and subpool members can also be edited through TSO ISPF EDIT. Console commands can be used to refresh the members. See Communicating-with-BMC-AMI-Storage-components.