This subsection describes the UDS Control files.
File application-group-qualifier*ABS$
Assigned by Exec during first access to an AFCB in this file
Cataloged by UDS security utility or SOLAR installation of UDS Control depending on first need
Deleted by SOLAR deinstallation of UDS Control
Freed by Exec
Dumped by SOLAR LIBSAVE runstream once after installation
Reloaded by SOLAR LIBLOAD runstream
This file contains the UDS Control I-bank absolutes and the UDS Control utility programs, SUDS and TRCCTL.
This file is the alternate file for the UDS common banks and is used during the loading of UDS common banks as well as during the execution of SUDS and TRCCTL.
Files Used Exclusively by Each Application Group
File application-group-qualifier*UDSC$PFGSDEF
Assigned by Exec during first access to the UDS Control subsystem in this file Cataloged by SOLAR installation of UDS Contro
Deleted by SOLAR deinstallation of UDS Control
Freed by Exec
Dumped by SOLAR LIBSAVE runstream once after installation
Reloaded by SOLAR LIBLOAD runstream
This file contains the gate definitions object module for the UDS Control protected fixed-gate subsystem.
File application-group-qualifier*UDSC$PFGSCOD
Assigned by Exec during first access to the UDS Control subsystem in this file Cataloged by UDS security utility or SOLAR installation of UDS Control depending on
first need
Deleted by SOLAR deinstallation of UDS Control
Freed by Exec
Dumped by SOLAR LIBSAVE runstream once after installation
Reloaded by SOLAR LIBLOAD runstream
This file contains the code object module for the UDS Control protected fixed-gate subsystem.
File application-group-qualifier*UDSC$CFGSDEF
Assigned by Exec during first access to the UDS Control subsystem in this file Cataloged by UDS security utility or SOLAR installation of UDS Control depending on
first need
Deleted by SOLAR deinstallation of UDS Control
Freed by Exec
Dumped by SOLAR LIBSAVE runstream once after installation
Reloaded by SOLAR LIBLOAD runstream
This file contains the gate definitions object module for the UDS Control chameleon fixed-gate subsystem.
Files Used Exclusively by Each Application Group
File application-group-qualifier*UDSC$CFGSCOD
Assigned by Exec during first access to the UDS Control subsystem in this file Cataloged by UDS security utility or SOLAR installation of UDS Control depending on
first need
Deleted by SOLAR deinstallation of UDS Control
Freed by Exec
Dumped by SOLAR LIBSAVE runstream once after installation
Reloaded by SOLAR LIBLOAD runstream
This file contains the code object module for the UDS Control chameleon fixed-gate subsystem.
File application-group-qualifier*ABSLIB$
Assigned by Exec during first access to an AFCB in this file
Cataloged by UDS security utility or SOLAR installation of UDS Control depending on first need
Deleted by SOLAR deinstallation of UDS Control
Freed by Exec
Dumped by SOLAR LIBSAVE runstream once after installation
Reloaded by SOLAR LIBLOAD runstream
This is the alternate file for the UDS Control thread control intercept and connect routine (ICR) common bank.
This file is used during the loading of UDS common banks.
Files application-group-qualifier*DUMPn(cycle) application-group-qualifier*DUMPnPnn(cycle)
Assigned by UDS Control
Cataloged by UDS Control dump facility
Deleted by User (left cataloged by UDS Control for future analysis)
Freed by UDS Control
The UDS Control dump routine writes dumps to a mass storage file. The dump file names for the default application group are in UDSSRC*DUMPn(cycle) format, where n is a number from 0 to 9 and cycle is the file cycle. If the dump does not fit in one file, additional files with names in the UDSSRC*DUMPnPnn(cycle) format are created, where nn is a 2-digit integer. File numbering starts with 01.
Files Used Exclusively by Each Application Group
When UDS Control writes a dump, the dump routine takes n as 0 and tries to catalog a file cycle with that name. If cataloging is unsuccessful, n increases by 1 and the dump routine tries to catalog the new file name. The dump routine continues increasing the number by 1 and retrying until it catalogs a file or tries all 10 dump file names. You can use UDS Control dump analysis functions to examine this file.
This file is cataloged at 262K tracks with an initial reserve equal to the number of tracks needed in the dump file. The initial reserve calculatation depends directly on the number and size of UDS D-banks expected to be written to the dump file.
If you migrate to a Security Option 3 environment, delete all file cycles of the dump file. This ensures that UDS Control catalogs all future cycles as private.
If a dump file cataloged public already exists on the system, all future dump files are cataloged public rather than private.
File application-group-qualifier*ROLLBACKnnnn
Assigned by UDS Control
Cataloged by UDS Control
Deleted Never
Freed by UDS Control
UDS Control assigns a set of retention files, depending on the configuration. A retention file contains quick-before-looks and paged deferred updates for a thread. These files can be composed of TIP, Exec, or both file types. UDS Control installation catalogs and initializes retention files. UDS Control also writes to and reads from retention files.
The contents of the retention file are used when a step is rolled back or committed. Retention files are empty before the step begins and after the step ends. After a rollback or commit, the file returns to its initial size if it expanded during step execution.
During short recovery, UDS uses the contents of the retention file to recover partially completed steps.
The UREP configuration attributes used to specify the name, TIP code, prep factor, initial size, maximum size, and qualifier of a retention file are as follows:
RETENTION-FILENAME RETENTION-FILE-TIP-CODE RETENTION-FILE-PREP-FACTOR RETENTION-INITIAL-POSITIONS RETENTION-MAXIMUM-POSITIONS RETENTION-QUALIFIER
Files Used Exclusively by Each Application Group
Additional UREP configuration attributes used to describe the structure and handling of retention files are as follows:
RETENTION-FILE-ALGORITHM RETENTION-FILE-FIXED-SEG-SIZE RETENTION-FILE-WARNING-LEVEL-TRACKS NUMBER-RETENTION-FILE-DEVICES
For information about modifying UREP configuration attributes, see the Repository for
ClearPath OS 2200 Administration Guide.
The UREP configuration attribute NUMBER-RETENTION-FILE-DEVICES is used by UDS Control to determine who is responsible for cataloging the retention files. If the
attribute value is 1, UDS Control catalogs and assigns the retention files. If the attribute value is greater than 1, UDS Control assumes that the user has cataloged the retention files and UDS Control only needs to assign the retention files. UDS Control catalogs retention files with position granularity.
The UREP configuration attributes RETENTION-INITIAL-POSITIONS and
RETENTION-MAXIMUM-POSITIONS pertain to the single-file retention file algorithm. The RETENTION-INITIAL-POSITIONS attribute determines the initial reserve for single-file retention files.
For the retention file pool algorithm, UREP determines the total number of tracks necessary for each retention file, using the RETENTION-MAXIMUM-POSITIONS attribute to determine the initial reserve. When UDS Control catalogs retention files, the number of tracks for each retention file is rounded to the next multiple of positions and the retention file is cataloged with position granularity. For example, a retention file specified as less than 64 tracks is cataloged as 1 position (64 tracks); a retention file specified as 65 tracks is cataloged as 2 positions (128 tracks).
File application-group-qualifier*SYS-FILE
Assigned by First user accessing the application group after installation assigns the file. It is also assigned during the UREP dynamic system
reconfiguration (DSR) process and by UDS Control.
Cataloged by Initial SOLAR installation of UDS Control, or UDS security utility prior to initial SOLAR installation if a Security Option 3 system, for the default application group.
The UREP PROCESS CONFIGURATION command, or UDS security utility if a Security Option 3 system, prior to SOLAR installation of UDS Control for an alternate application group.
Deleted Reinitialized by any UDS Control installation
Freed by UDS Control and dynamic system reconfiguration (DSR)
Dumped by User
Files Used Exclusively by Each Application Group
This file contains information based on the UDS applications configuration. In addition to current configuration information, this file also includes transparent configuration information, and is a backup for important UDS Control and DMS main storage tables.
This file is used during the UREP DSR process and whenever an application group is initialized. It must be dumped after every installation of an application group or after dynamically reconfiguring the system through the UREP DSR process.
Each application group has its own system file. The DSR writes to it; UDS Control reads and updates it.
File application-group-qualifier*TRACEFILE
Assigned by TRCCTL (the trace control program)
Cataloged by TRCCTL
Deleted by User
Freed by User
The trace file is created when the trace control program (TRCCTL) is used. You can change the size (initially 128 tracks) and name of the trace file during the trace session, which starts when you turn on trace. For more information about how to use TRCCTL, see Section 7.
This file contains diagnostic and statistical information collected during the execution of TRCCTL.
This file is treated as a circular buffer with fixed-size blocks.
File application-group-qualifier*UTIL$
Assigned by User through DUMPER for dump processing Cataloged by SOLAR installation of UDS Control
Deleted by SOLAR deinstallation of UDS Control Freed by User after UDS dump files are processed
Dumped by SOLAR LIBSAVE runstream once after installation
Reloaded by SOLAR LIBLOAD runstream
This UDS Control utilities file contains dump analysis routines, COMUS build routines, SOLAR installation routines, and other miscellaneous elements used during UDS dump processing.
Files Used Exclusively by Each Application Group