User Report List File Management

The following User Report List files are contained in the Control‑D repository:

Active User Report List file
History User Report List file
Migrated User Report List file (Control‑V only)
Permanent User Report List file

These files are managed by the IOA Access Method. Each file consists of two separate sequential datasets:

the Data component, where the actual record information resides
the Index component, which provides keyed access to records in the Data component

Both Data and Index components can extend beyond one physical dataset (depending on whether automatic extension was specified for the file during allocation). Initially, a component is allocated as a single physical dataset called the primary extent.

For more information, see IOA Administration.

The file naming convention is

prefix.dbname.Ennn

Table 178 File Naming Convention

Field	Description
prefix	Set to Control‑D installation parameter DBPREFD.
dbname	Set to file identifier name, as follows: HST—Control‑D History User Report list Data component. ACT—Control‑D Active User Report list Data component. ACTI—Control‑D Active User Report list Index component. HSTI—Control‑D History User Report list Index component. PRM—Control‑D Permanent User Report list Data component. MIG—Control‑V Migrated User Report list Data component. MIGI—Control‑V Migrated User Report list Index component. PRMI—Control‑D Permanent User Report list Index component.
Ennn	Extent sequence number suffix. The suffix consists of the letter E followed by nnn, a number from 000 to 255, indicating the extent sequence number.

Field

Description

prefix

Set to Control‑D installation parameter DBPREFD.

dbname

Set to file identifier name, as follows:

HST—Control‑D History User Report list Data component.
ACT—Control‑D Active User Report list Data component.
ACTI—Control‑D Active User Report list Index component.
HSTI—Control‑D History User Report list Index component.
PRM—Control‑D Permanent User Report list Data component.
MIG—Control‑V Migrated User Report list Data component.
MIGI—Control‑V Migrated User Report list Index component.
PRMI—Control‑D Permanent User Report list Index component.

Ennn

Extent sequence number suffix. The suffix consists of the letter E followed by nnn, a number from 000 to 255, indicating the extent sequence number.

Example

If Control‑D installation parameter DBPREFD contains the value CTD, the following file names are assigned for the Active User Report List file:

CTD.ACT.E000 for the Data component.
CTD.ACTI.E000 for the Index component.

Each component uses its own file definition member that resides in the IOA PARM library. The member includes the file’s physical and logical attributes. The member name is DEFxxx for a Data component, or DEFxxxI for an Index component, where xxx is the dbname as described in the above table. The member is used by the IOADBF utility. Additional utilities are provided to maintain these IOA Access Method files. For more information about these utilities, see the INCONTROL for z/OS Utilities Guide.

The files can be activated with dual (mirror image) file support. The dual file name is similar to the main file name, except for the suffix (Dnnn instead of Ennn). Dual file support can be defined for both the Data component and Index component. It is recommended that this feature be activated only for the Data component to reduce overhead, since the Index component can be built from the Data component.

For details about maintaining these files, see Repository Maintenance.

Parent Topic

Control-D and Control-V