Your HDB environment is
controlled by the Repository. The Repository is a VSAM KSDS that acts
as a repository for all definitions associated with your HDB environment:
- Templates (Performance HDBs only)
- HDB Definitions
- Selection Criteria (Performance HDBs only)
- Container data set information
- Audit information about Load requests
The Repository is also a repository for the following
definitions that are not associated with HDBs:
- Shared System Definitions
- Application Groups
- Statistics Alert Definitions
- Resource Lists
Performance Alert Definitions
On the Historical Database Menu, specify the Repository data
set name. If the Repository data set is not cataloged, the dialog
will prompt you to define it when you select an option from the menu.
Figure 1. Define Repository Define Repository
Command ===> ___________________________________________________________
Enter "/" to select option
_ Edit IDCAMS command
_ Browse errors only
Repository Name . . . 'CICSPROD.CICSPA.XYX.REPOSTRY'_______________
Cluster Level Information:
Space Units . . . . . 1 1. Cylinders Primary Quantity . . . 1_______
2. Tracks Secondary Quantity . . 1_______
3. Records
4. Kilobytes
5. Megabytes
Volume . . . . . . . . ______
Data Class . . . . . . ________
Management Class . . . ________
Storage Class . . . . ________
F1=Help F3=Exit F6=Resize F12=Cancel
Specify the required allocation settings and then press Enter to
define the Repository data set.
The allocation settings are:
- Edit IDCAMS command
- Select this option to edit the IDCAMS command that CICS PA generates
to define the Repository. If this option is not selected, the IDCAMS
command is issued immediately.
- Browse errors only
- Select this option to browse the output from IDCAMS only when
a non-zero return code is returned by IDCAMS. If this option is not
selected, the output from IDCAMS will always be presented.
- Repository Name
- Specify the name of the Repository data set to be defined.
Normal
ISPF data set conventions apply. Enclose a fully qualified data set
name in quotes, otherwise the TSO prefix is used as a high level qualifier.
- Cluster Level Information
-
- Space Units
- Select one of the following in which to express the data set size:
- cylinders
- tracks
- records
- kilobytes
- megabytes
- Space Quantities
- Specify the Primary and Secondary allocation quantities in cylinders,
tracks, records, kilobytes or megabytes as indicated in the Space
Units field. Express all quantities in decimal, not hexadecimal.
Typically
a space allocation of 1 primary and 1 secondary cylinder is sufficient.
- Volume
- The volume serial name of the DASD volume to contain the data
set.
- Data Class
- Specify the name of the data class for the data set. The data
class provides the allocation attributes for the data set. The storage
administrator at your installation defines the data class. However,
you can override the parameters defined for a data class by explicitly
specifying other attributes.
- Management Class
- For an SMS-managed data set, specify the name of the management
class for a new data set. The storage administrator at your installation
defines the names of the management classes you can specify.
If
management class is not specified, but storage class is specified
or defaulted, management class is derived from automatic class selection
(ACS).
If management class is specified and storage class is
not specified or derived, the DEFINE will fail. Note that if SMS is
inactive and management class is specified, the DEFINE will fail.
- Storage Class
- For an SMS-managed data set, specify the name of the storage class.
The storage class replaces the storage attributes that are specified
on the UNIT and VOLUME operand for non-SMS-managed data set. Use the
storage class to specify the storage service level to be used by SMS
for storage of the data set. The storage administrator at your installation
defines the names of the storage classes you can specify. A storage
class is assigned when either you specify a storage class, or an ACS
routine selects a storage class for the new data set. Note that if
SMS is inactive and storage class is specified, the DEFINE will fail.
When the repository is defined, you are ready to start using HDB.