IRU Files Used for All Application Groups

This subsection describes the IRU files that are used for all application groups.

File SYS$LIB$*IRU

Assigned by Exec to your run when you call IRU (@IRU) Cataloged by SOLAR installation of IRU (mode IRU) Deleted by SOLAR deinstallation of IRU (mode IRU)

Freed by Exec

Dumped by SOLAR LIBSAVE runstream once after installation

Reloaded by SOLAR LIBLOAD runstream

This file contains the IRU product object module and APPREC absolute. This file is created when you specify the IRU installation mode IRU.

Your site can maintain more than one level of IRU on a system; however, you do not have to install a separate IRU for each UDS application group; you can use one IRU to maintain all 16 UDS application groups. If your site has more than one IRU on a system, you must specify which IRU is to be accessed by the @IRU call during the SOLAR installation.

Files Used by IRU

File SYS$LIB$*FSAH

Assigned by Exec to Common Name Section of FSAH subsystem when FSAH subsystem is loaded

Cataloged by SOLAR installation of FSAH (mode FSAH) Deleted by SOLAR deinstallation of FSAH (mode FSAH)

Freed by Exec when FSAH subsystem is deactivated or deinstalled Dumped by SOLAR LIBSAVE runstream once after installation

Reloaded by SOLAR LIBLOAD function

This file contains the FSAH object module, subsystem, and copy elements required to create an FSAH program. This file is created when you specify the IRU installation mode FSAH.

File SYS$LIB$*ALTFSAH

Assigned by Exec to Common Name Section of alternate FSAH subsystem when alternate FSAH subsystem is loaded

Cataloged by SOLAR installation of FSAH (mode ALT-FSAH) Deleted by SOLAR deinstallation of FSAH (mode ALT-FSAH)

Freed by Exec when FSAH subsystem is deactivated or deinstalled Dumped by SOLAR LIBSAVE runstream once after installation

Reloaded by SOLAR LIBLOAD function

This file contains the FSAH object module, subsystem, and copy elements required to create an FSAH program. This file is created when you specify the IRU installation mode ALT-FSAH.

File SYS$*MCB

Assigned by Exec

Cataloged by SOLAR installation of MCB. Installation of IRU (mode IRU) catalogs this file if it is not present on the system.

Deleted by SOLAR deinstallation of MCB

Freed by Exec

Dumped by FURPUR or FAS to save dummy absolutes placed in this file during the installation of IRU or live absolutes placed in this file during the installation of MCB.

Files Used by IRU

This file contains live or dummy banks for MCB, which performs message staging, control, and retention. It is included here because the contents of this file affect IRU execution. The Communications Management System (CMS 1100) uses MCB as its interface to the application group for both recoverable and nonrecoverable messages.

IRU uses two predefined alternate file common banks (AFCB) for each application group to coordinate message recovery with MCB, a short message recovery bank for use during short recovery and a long message recovery bank for use during long recovery.

IRU determines whether an MCB AFCB environment is configured for an application group by finding a relocatable element CBEP$$MCBn, where n is the application group number, in the MCB/IRU AFCB communication file SYS$*MCB. Installing MCB level 5R1 creates the relocatable element, which contains the AFCB bank descriptor indexes (BDI) for the short and long message recovery banks.

File project-id*IRU$AFrun-id

where:

project-id is the project id associated with the run-id.

run-id is the generated run-id.

Assigned by IRU

Cataloged by IRU on any execution of IRU with the A option present. If a user executes IRU multiple times, IRU catalogs new F-cycles of this for each execution.

Deleted by Not automatically deleted. You must delete this file when you no longer need the contents.

Freed by IRU at the end of the IRU session.

Note: A use name of IRU$AF is attached to the filename. This use name is not freed at the end of the IRU session.

This is the IRU alternate print file. It contains a copy of all input and output generated during an IRU session. A new F-cycle of this file is automatically generated each time you call IRU with the A option.

Files Used by IRU

File project-id*FSAH$VIEW

where:

project-id is the project id associated with the run-id.

Assigned by IRU

Cataloged by IRU (FSAH) when the caller specifies an alternate print file. Deleted by IRU during FSAH-TERM processing.

Freed by IRU during FSAH-TERM and FSAH-SETUP processing.

This file contains messages generated by IRU during an FSAH session. You can use an editor to view the contents of this file, to see messages that precede a prompt that appears on the console or demand terminal. IRU performs a breakpoint to this file at each prompt, so this file contains only messages issued since the previous prompt, or since the beginning of the FSAH session.

File project-id*DMP$PFrun-id

where:

project-id is the project id associated with the run-id.

run-id is the name of the run.

Assigned by IRU

Cataloged by IRU when a user responds “DUMP” to an error recovery query. Deleted by Not automatically deleted. You must delete this file when you no

longer need the contents. Freed by IRU at the end of the session.

This file contains the octal dump of the buffer (for example, audit block) that encountered an error.

Files Used by IRU

File project-id*PMD$PFrun-id

where:

project-id is the project id associated with the run-id.

run-id is the name of the run.

Assigned by IRU

Cataloged by IRU on encountering an IRU ERROR message if the P option is present.

Deleted by Not automatically deleted. You must delete this file when you no longer need the contents.

Freed by IRU

This file contains the IRU contingency dump and contingency information.

File project-id*DIAG$run-id

where:

project-id is the project id associated with the run-id.

run-id is the generated run-id.

Assigned by IRU

Cataloged by IRU contingency processing when the D option is present. If a user executes IRU multiple times, IRU catalogs a new F-cycle of this file for each execution.

Deleted by Not automatically deleted. You must delete this file when you no longer need the contents.

Freed Not freed

This file contains a copy of the DIAG$ file generated during IRU contingency processing. IRU generates a new F-cycle of this file each time a session ends in contingency and you specified the D option on the IRU call for that session.

Normal contingency processing creates a temporary DIAG$ file. This DIAG$ file is reused for subsequent processor executions and deleted on run termination; this means that information can be lost when additional processors are called or the run terminates. Use the D option to preserve the DIAG$ file in the next F-cycle of DIAG$run-id.

Files Used by IRU

If you specify the D option, the following ECL commands are executed after the IRU contingency handler detects a critical contingency:

@USE DIAG$PF.,DIAG$runid(+1). @ASG,UP DIAG$PF.,F/0/TRK/50000 @COPY DIAG$.,DIAG$PF.

@FREE DIAG$PF.

If the run is executing in an environment with Security Option 3 or common bank protection set, the @ASG statement does not include the P option, so the file is cataloged as a private file.

File project-id*IRU$PFrun-id

where:

project-id is the project-id associated with the run-id.

run-id is the name of the run.

Assigned by IRU

Cataloged by IRU on first execution of IRU processor if the S option is present; otherwise, it is assigned as a temporary file by IRU.

Deleted by IRU (or freed if it is assigned as a temporary file) whenever an IRU session terminates normally.

Freed by IRU

This is the execution packet file used by the IRU checkpoint-restart capability. It retains the IRU command packet on all IRU commands. During the processing of the DUMP, RELOAD, and RECOVER commands, restart information is periodically saved in the execution packet.

The S option on the IRU processor call activates the checkpoint-restart capability. If IRU was initially executed with the S option and the IRU session terminates

abnormally, a subsequent execution of IRU (with or without the S option specified) causes IRU to reexecute the original command. The reexecution commences at a subcommand level for the DUMP, RELOAD, and RECOVER commands, which allows IRU to begin execution from a checkpoint within the DUMP, RELOAD, or RECOVER processing. Other IRU commands are restarted at the command level and repeat the entire processing as specified by the original IRU command.

The file created by IRU contains your run-id. To take advantage of the IRU checkpoint- restart capability, you must either reexecute IRU under the same run-id or use a @USE statement on the packet file, project-id*IRU$PFrun-id, as follows:

Files Used by IRU