Some more useful information from Mark Ritter, DirMaint development:
A "region" is a subset of a "volume". A region may consist of the entire
volume, or any part of a volume. A volume may contain one or many
regions. A "group" is a collection of regions. These regions may be on
one volume or multiple volumes.
This structure can be used to budget DASD usage. For example, all
MDISKs for employees in one department could be allocated within a region
or group dedicated for that department, or all MDISKs for students in a
class could be allocated within a region or group allocated for that
course.
This structure also allows delegation of administrative authority. The
manager of a department or instructor for a course can be given authority
to allocate space within their assigned regions, volumes, or groups,
without giving authority to allocate space elsewhere.
This structure can alternatively be used to minimize DASD usage and
fragmentation. All 1 cylinder MDISKs can be allocated in a group/region
reserved for 1 cylinder MDISKs, all MDISKs that are a multiple of 5 cyls
can be allocated in areas reserved for 5 cylinder disks, etc. Thus, when
an MDISK is deleted, the space is available for reuse by another disk of
similar size.
The DIRM DASD ADD command can be used to define new regions, "volumes",
or groups. A volume definition is simply a region with the same name as
the volume id starting at cylinder 1 to the END of the physical volume.
You need to supply all (or most) of the information needed for the
:REGIONS section of the EXTENT CONTROL file. From DIRM ? DASD -
>>--DIRMaint--DASD-- ..
..Add--.-Group-- ... ... -.---|
|-Region--region_name--volid--devtype--| Options |----|
'-Volume--volid--devtype--| Options |-----------------'
Options:
|--.-------------------------------.----
'-size--.---------------------.-'
'-start--.----------.-'
'-comments-'
To define a region, you must include the region name, the volid, the
device type (with model capacity suffix), and optionally the size of
the region (default is END of volume), the starting location of the
region (default is 1), and any optional comments such as the owning
department or class or the MDISK "slot size". To define a volume,
the parameters are the same except for the omission of the region name
which is the same as the volid.
About that "model capacity suffix". It must match one of the definitions
in the DEFAULTS section of the EXTENT CONTROL file, or one of the IBM
supplied defaults in the DEFAULTS DATADVH file. For 3390s, the suffixes
include -03 for 3339 cylinders. A 3390 with unrecognized suffix
(your -3 for example) uses the generic 3390 definition which is the same
capacity as a 3390-01 (1113 cylinders). If you wish, you may define a
3390-3 in the DEFAULTS section of your EXTENT CONTROL file.
Reminder: After making changes to the EXTENT CONTROL file, make sure you
issue a DIRM RLDE command to put the changes into effect.
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
