Files Used in the UDS Environment
4 UDS$$FOR 5 UDS$$F
2.3.2. IRU Files Dependent on Application Groups
This subsection describes IRU files associated with application groups. Most systems have one of these files for each application group configured.
Files application-group-name*dhf-exec-filename
(The default dhf-exec-filename is IRU$DH.)
dhf-tip-file-number
Assigned Whenever an IRU command that accesses it executes
Cataloged Exec files must be cataloged, and TIP files must be registered and reserved with TIP before any IRU commands that access them are executed.
Deleted Never
Freed by IRU
Dumped by User: Back up Exec history files with FURPUR or FAS, if available. Use the TIP TFCIO utility to copy TIP history files to tape in @COPY,G format. Reloaded by Same processor used to save (that is, FAS, FURPUR, TFCIO)
IRU records information about each database DUMP, DUMP CHANGES, and RELOAD command into the dump history file. Dump information includes tape numbers, files dumped, associated audit trail identifiers and dates. These history file records can be used later for automated or history-directed long recovery.
Each application group has its own dump history file. During the COMUS build of IRU, COMUS asks whether the history files are configured as Exec or TIP files. The IRU release tape specifies Exec as the default type for history files for all application groups.
You can use the IRU ASSUME command to change the name or type of the IRU dump history file for an IRU session. For more information about the IRU ASSUME command, see the Integrated Recovery Utility Operations Guide.
The following IRU commands access the dump history file:
CLEAR DELETE DISABLE DUMP DUMP CHANGES ENABLE
RECOVER (long recovery) RELOAD
REPORT UP
Files Used by IRU
Files qualifier*mhf-exec-filename
(The default mhf-exec-filename is IRU$MH.)
mhf-tip-file-number
where qualifier is the application group name for step control audit trails or the audit trail file name for non-step-control audit trails and moves using an alternate audit trail file name.
Assigned Whenever an IRU command or FSAH request that accesses it executes. Cataloged Exec files must be cataloged, and TIP files must be registered and
reserved with TIP before any IRU commands that access them are executed.
Deleted Never
Freed by IRU
Dumped by User: Back up Exec history files with FURPUR or FAS, if available. Use the TIP TFCIO utility to copy TIP history files to tape in @COPY,G format. Reloaded by Same processor used to save (that is, FAS, FURPUR, TFCIO)
If you execute a history file MOVE command, IRU records information about the mass storage audit trail F-cycles and the tapes where IRU moved these F-cycles in the move history file. IRU uses this information to assist in recovery automation. The IRU audit handler also accesses the move history file through the freestanding audit handler (FSAH) interface.
Each application group can have its own move history file. During the COMUS build of IRU, COMUS asks whether the history files are configured as Exec or TIP files. The IRU release tape specifies Exec as the default type for history files for all application groups. TPM, COD, and ALAT audit trails cannot use TIP move history files.
The following IRU commands access the move history file:
COLLECT MOVE
RECOVER (long recovery) MEDIUM RECOVER REPORT AUDIT VERIFY
You can use the IRU ASSUME command to change the name or type of the IRU move history file for an IRU session. For more information about the IRU ASSUME command, see the Integrated Recovery Utility Operations Guide.
Files Used by IRU
File directory-idIRU$nn*filenm$MxxHh
where:
directory-id is SHARED# for concurrent application groups and STD# for local
and switchable application groups with multi-host file sharing. This value does not apply for other application groups.
nn is a unique number related to both the MHF set and leg being locked. Numbers 1 to 9 include a leading zero.
filenm is the first 6 characters of the move history file name (Exec) or
number (TIP) $-filled to 6 characters (both Exec and TIP).
xx is the application group number. Application groups 1 to 9 include a leading zero.
h is the host-id. Hh applies only for concurrent application groups.
Assigned Whenever IRU executes a history file MOVE or REPLICATE command. Cataloged Whenever IRU executes a history file MOVE or REPLICATE command. Deleted At the end of a MOVE or REPLICATE command execution.
Freed by IRU
Dumped by Not applicable
Reloaded by Not applicable
The MOVE and REPLICATE commands are the only IRU commands that access this file.
This file prevents multiple history file moves at the same time using the same move history file set, leg, and host combination, thus preventing move history file
inconsistencies.
Files directory-idfilenm*IRU$nnnnxxHh directory-idIRU$tipnum*IRU$nnnnxxHh
where:
directory-id is SHARED# for concurrent application groups and STD# for local
and switchable application groups with multi-host file sharing. This value does not apply for other application groups.
filenm is the DHF-EXEC-FILENAME (Exec dump history file).
tipnum is the DHF-TIP-NUMBER (TIP dump history file) zero-filled on the
left.
nnnn is a unique number (range 1 - 9999) associated with the current
Files Used by IRU
xx is the application group number. Application groups 1 to 9 include a leading zero.
h is the host-id. Hh applies only for concurrent application groups.
Assigned Whenever IRU executes a DUMP command for a base dump.
Cataloged Whenever IRU executes a DUMP command for a base dump.
Deleted At the end of a DUMP command execution.
Freed by IRU
Dumped by Not applicable
Reloaded by Not applicable
This file prevents execution of simultaneous DUMP commands for a file using the same dump history file. The DUMP command is the only IRU command that accesses this file.
Files application-group-name*kf-exec-filename
(The default kf-exec-filename is IRU$KF.)
kf-tip-file-number
Assigned Whenever an IRU command that accesses it executes.
Cataloged If it is an Exec file, you must catalog it before executing a COLLECT command. If it is a TIP file, you must register and reserve it with TIP before executing a COLLECT command.
Deleted Never
Freed by IRU
Dumped by User: Back up an Exec key file with FURPUR or FAS, if available, or use the TIP TFCIO utility to copy a TIP key file to tape in @COPY,G format. Reloaded by Same processor used to save
The following IRU commands access the key file:
COLLECT
DUMP CHANGES DUMP
REPORT KEY FILE
The COLLECT command reads the audit trail and collects a list of each page or record that has changed since the last base dump of a file and stores the list in a key file. The key file contains information about the specific page or record updated. Each
application group has a key file; each updated page or record within each file has an entry in the key file.
Files Used by IRU
The DUMP CHANGES command dumps the pages or records identified in the key file as having changed since the last base dump.
The DUMP command deletes keys stored in the key file for the files being dumped. The key file is not required for the DUMP command, and is only accessed if it is present.
During the COMUS build of IRU, COMUS asks whether the key files are configured as Exec or TIP files. The default values for key file configuration variables on the IRU release tape specify the file type as Exec for all application groups.
You can use the IRU ASSUME command to change the key file name or type for an IRU session. For more information about the IRU ASSUME command, see the
Integrated Recovery Utility Operations Guide.
File dir-idIRU$*MED$REC$nnHh
where:
dir-id is SHARED# for concurrent applications, STD# for local and
switchable applications in a Multi-Host Sharing File (MHFS) environment, and blank otherwise.
nn is the application group number (a leading zero is added for application groups 1 to 9).
h is the host identifier (A,B, C, or D). The Hh is present only for a concurrent application group.
Assigned by IRU
Cataloged by IRU
Deleted by IRU
Freed by IRU
This is the recovery lockout file for medium recovery.
This file is used to prevent concurrent medium recoveries for a single application group/host, to delay a short recovery until medium recovery is complete, and to prevent simultaneous conflicting long recoveries.
Files Used by IRU
File IRU$*SHRT$$RECYnn
where nn is the application group number (a leading zero appears for application groups 1 to 9).
Assigned by IRU
Cataloged by IRU
Deleted by IRU
Freed by IRU
This is the recovery lockout file for short recovery.
This file is used to prevent multiple concurrent short recoveries as well as to prevent other simultaneous conflicting recoveries.
File application-group-name*IRU$KFTIP$LK
Assigned by IRU
Cataloged by User or IRU. You might want to catalog this file before executing IRU if you have a TIP key file. If you do not catalog the file, IRU catalogs it during the execution of a DUMP, DUMP CHANGES, or COLLECT command.
Deleted Never
Freed by IRU
Files Shared by All Application Groups
2.4.
Files Shared by All Application Groups
This subsection describes the files that are shared by all application groups.
File UDS$$SRC*ADT-FILE
Assigned by Application definition table (ADT) code, when necessary for read or write access. Write accesses are caused by the UREP DSR process only.
Cataloged by SOLAR installation of UDS Control or UDS security utility prior to initial SOLAR installation if a Security Option 3 system. The V option is used to prevent it from being rolled out.
Deleted Never. Overwritten by subsequent installation of UDS Control for the default application.
Freed by ADT code as soon as the read or write access is complete. (This can be subverted by console X keyins). The SUDS FF command can be used to free this file; however, use it only under exceptional conditions.
See “Free File from UDS Domain (FF)” in Section 8 for more information.
Dumped by FURPUR or FAS
Reloaded by Same procedure used to dump
The ADT, a common data bank, maintains and uses file ADT-FILE (also called the ADT backup file) on mass storage. ADT-FILE is the only UDS file that affects all UDS application groups. The version of file ADT-FILE on the standard release tape contains a single entry for UDS Control, namely, the standard application group (named
UDSSRC for application group 3).
UDS$ADTCDB is the common data bank that contains the ADT and access routines that reference it. The UREP PROCESS command and UDS Control reference the ADT bank during configuration and initialization. The intercept and connect routines (ICR) also reference the ADT bank. For more information about how to install the ADT bank when Security Option 3 is configured, see the Universal Data System Configuration
Guide.
File ADT-FILE contains an active entry for each application group in use, a list of alias names for each application group, and transparent entries for application groups recently configured but not yet activated.
This file is closely associated with the ADT bank that controls access to UDS. During initialization, UDS Control reads the current ADT from the file. During the UREP dynamic system reconfiguration (DSR) process, a copy of the updated ADT bank is written to this file.
You must protect this file; if it becomes corrupted, access to UDS is lost for all application groups.
Files Shared by All Application Groups
You must dump this file after every installation of an application group or after dynamically reconfiguring your system through the UREP dynamic system reconfiguration (DSR) process.
The UDS Control utility file contains two Dump Analysis Procedure (DAP) functions, ADTAPPL and ADTALIAS, with which to look at the contents of file ADT-FILE.
ADTAPPL displays information relating to the active and transparent entries in the file. ADTALIAS lists the alias names associated with each application group.
Use the following sequence of commands to execute ADTAPPL and ADTALIAS:
@asg,t temp*adt-file. @copy uds$$src*adt-file.,temp*adt-file. @dap temp*adt-file. *restore uds$$src*util$. adtappl adtalias @eof
Caution
Always copy ADT-FILE to a temporary file, as in the preceding example. Do not use DAP functions to look at the permanent version of file ADT-FILE. This could cause errors, or it could cause the application group to hang because DAP assigns the file. The ADT must assign file ADT-FILE exclusively whenever it updates it. See also the caution note in 6.3.5.
File UDS$$SRC*ABSADT$
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 absolutes for the ADT AFCB, which are used when UDS common banks are loaded.
This is the alternate file for the UDS Control application definition table (ADT) common bank.
Files Shared by All Application Groups
File UDS$$SRC*SECURE-FILE
Assigned by ADT, DSR, and SUDS
Cataloged by SOLAR installation of UDS Control on a system that has Security Option 3 configured. You must save the file.
Freed by DSR or SUDS following their execution
Dump/Reload Not required because the file contains no information.
If your system has Security Option 3 configured, the security file must be on the system at all times.
If this file is not on the system and Security Option 3 is configured, users receive an error whenever they attempt the following SUDS and DSR commands:
SUDS DA DSR
ADD ALIAS
PROCESS CONFIGURATION... INSTALL PROCESS CONFIGURATION... DELETE File UDS$$SRC*UREP$BDI
Assigned by UREP, Universal Compiling System (UCS), Display Processing System (DPS), IPF SQL Interface, and Structured Query Language (SQL*) products
Cataloged by SOLAR installation of UREP
Freed by UREP, UCS, DPS, IPF SQL Interface, or SQL* products
Reload FURPUR or FAS
This file contains BDIs of the UREP ICR and the RDMS SQL banks called by users.
This file is used by UREP to determine the correct UREP common banks to use for an application group.
This file is used by UCS to identify which application groups have UREP and the RSA component of RDMS available, and to determine how to access their respective common banks.
This file is used by IPF SQL as well to retrieve the BDI for the RSA SQL BDI for bank C$RDMRPLB4.
Files Shared by All Application Groups
File STD#UDS$$SRC*INTERFACESEC
Assigned by Not applicable
Cataloged by UDS security utility prior to initial SOLAR installation if a Security Option 3 system
Deleted by Never
Freed by Not applicable
Reload Not necessary
The UDS interface security file applies only to Security Option 3 systems.
Users with write access to this file have all UDS Control command privileges. See 9.3.5.
File STD#UDS$$SRC*RUBSECURITY
Assigned by Not applicable
Cataloged by UDS security utility prior to initial SOLAR installation if a Security Option 3 system
Deleted by Never
Freed by Not applicable
Dump/Reload Not necessary
The RUB security file applies to the XTC system and Security Option 3 systems and ensures that only the RUB run performs RUB-only thread control commands.
The RUB run user ID must be the only nonprivileged user ID with write access to this file.
Files Used Exclusively by Each Application Group
2.5.
Files Used Exclusively by Each Application
Group
This subsection discusses the files that are duplicated for each application group. Each application group has its own copy of UDS Control.
The files are presented by product. In general, each file falls into one of three categories:
• Product files refer to the product itself: the product source, relocatable, and absolute code. Also, utility programs required to generate, install, and run a product are found in product files.
• UDS source files contain definitions to define the data in your databases. For example, you use UREP commands to create the symbolic form of the data definition, Data Definition Language (DDL) clauses to create a DMS source
schema, and Subschema Data Definition Language (SDDL) clauses to create a DMS source subschema. You can use UREP commands to update and report your source definitions. For example, you can produce formatted reports of UREP storage area definitions, your UDS system configuration, RDMS table definitions, or DMS schema and subschema definitions.
• UDS object files are derived from the encoded form of your source definition files. Use the UREP PROCESS command with the INSTALL option to create the object files. The file description table (FDT) is an example of a UDS object file. For information about how to use the PROCESS command, see the Repository for
ClearPath OS 2200 Administration Guide.