You can define up to 100 object storage groups to OAM (in SMS and DB2). If 100 object storage groups are not necessary, you can save space by defining only the number of storage groups you need, and defining the rest of the groups as VIEWS of the defined storage groups. For example, if you need 60 groups, you can define those 60 storage groups and then define the remaining 40 as VIEWs of the 60.

Note: Although the OAM PISA (Planning, Installation, and Storage Administration) Guide for object support states that you can skip the steps for defining groups you do not need, you must define them at least as VIEWs so that the OAM DB2 plans are bindable.

In the SMS ACS routines, you must define the STORCLAS, MGMTCLAS and STORGRP attributes for objects. You can then assign objects to appropriate storage groups based on their values for these attributes.

Control‑V objects can best be identified using the following:

• &envir parameter (= ‘STORE’)
• &hlq parameter (= MIGRATED prefix defined in Control‑V)
• &dsn parameter (= collection name)

For example, you can derive the job name from the collection name and direct the collections to storage groups according to their job name prefix.