CREATE STOGROUP

The CREATE STOGROUP command creates an XDB Server stogroup which associates a user-specified directory path with the named stogroup. Once the SYSIBM.SYSVOLUMES catalog table has been updated to reflect this path assignment, newly created objects can be physically stored in this directory path by designating the named stogroup when creating the objects.

Restriction: This topic applies to Windows environments only.

Invocation

This statement can be embedded in an application program or issued interactively.

Authorization

The XDB Server checks to verify whether the AuthID issuing this command has either the CREATESG privilege, or SYSADM or SYSCTRL authority for the location.

Syntax

CREATE STOGROUP stogroup-name 
    VOLUMES (volume-id[,...]) 
    VCAT catalog-name [PASSWORD password]

Parameters:

`stogroup-name`	Identifies the stogroup. This 1 to 8 characters name must be unique among stogroup names created at the currently set location.
`volume-id`	Identifies one or more Volume IDs, any of which can be associated (by updating the SYSIBM.SYSVOLUMES table) with a path designated specifically for the named stogroup.
`catalog-name`	Identifies an Integrated Catalog Facility catalog existing on a DB2-mainframe system.
`password`	Furnishes a VSAM control or master level password for the ICF catalog on a DB2-mainframe system.

Description

The stogroup feature allows XDB Server users greater control in assigning objects to specific directory paths. For example, you can assign storage of individual data objects to specially created stogroup directories (such as E:\STOR1\ or D:\STOR2\).

VOLUMES

This clause assigns a series of volume-id values (limit of 133) to the named stogroup. The XDB Server stores these values in the VOLID column of the SYSIBM.SYSVOLUMES catalog table. Whenever the stogroup is specified in an object creation command, the XDB Server uses these volume-id values to physically store the new objects on the path recorded in SYSIBM.SYSVOLUMES for the named stogroup. Users must first manually update the XDBPRIMEVOLPATH and XDBVOLPATH columns in SYSIBM.SYSVOLUMES. These columns associate a physical path with the value recorded in the VOLID column.

Asterisks are recognized only by Storage Management Subsystem (SMS). Contact your site's storage administrator to determine if the SMS Guaranteed Space attribute applies. If SMS Guaranteed Space does not apply for SMS-managed data sets, it is recommended that the VOLUMES clause be specified with one asterisk, VOLUMES('*' ). If SMS Guaranteed Space does apply, contact your site storage manager and refer to DFSMS/MVS: Access Method Services for the Integrated Catalog and DFSMS/MVS: Storage Administration Reference for DFSMSdfp for information on how to specify the VOLUMES clause.

Note:

There is no specific limit on the number of volumes that can be defined for a storage group. However, the maximum number of volumes that can be managed for a storage group is 133. Thus, there is no point in creating a storage group with more than 133 volumes.

VCAT

Although this clause has no physical functionality within the XDB Server system architecture, the keyword VCAT and a catalog-name value of "xdb" must be specified when working in DB2 mode. This information is recorded in the catalog tables for the current XDB Server location. The password parameter is also mainframe-specific, and is recorded in the XDB Server catalog tables.

Example:

The following command (executed in DB2 mode) creates a stogroup named STOR1 and assigns a volume-id value of "myid" to the VOLID column of the SYSIBM.SYSVOLUMES catalog table:

CREATE STOGROUP stor1 VOLUMES (myid) VCAT xdb;

The next example updates the SYSIBM.SYSVOLUMES catalog table by associating a user-created path (D:\STOR1) with myid:

UPDATE SYSIBM.SYSVOLUMES 
    SET xdbprimevolpath = "y" 
    , xdbvolpath = "d:\stor1\"
WHERE volid = "myid";