In the multinode area, you can make an optional node dedicated to archive journals. Each OpenTP1 node sends system journals to that node in order to archive the journals. A node from which journals are sent to be archived is called an archive-journal source node. The node on which the journals are archived is called the archive-journal target node.

The archive-journal target node is different from other OpenTP1 nodes (archive-journal source node or a node which does not use the Global Archive Journal facility) in the following points:

• user servers cannot be activated on an archive-journal target node
• the archive-journal target node must be first started before any other OpenTP1 node in the multinode area

The following figure illustrates the global archive journal service.

Figure 6-6 Overview of Global Archive Journal facility

You can make from 1 to 16 resource groups in an archive-journal target node. A resource group is a set of archive journal files classified for the same purpose. For example, you can specify a resource group A that collects journals from one part of the multinode area, and you can specify another resource group B that collects journals from another part of the multinode area.

The global archive journal service uses resource group names to manage archive journal files.

Up to 20 archive journal source nodes can belong to one resource group.

A resource group name is defined in the archive journal service definition as a file name. In the global archive journal service definition, you can specify the number of resource groups to be used in a node on which a journal is archived.

To connect the global archive journal service to a journal service in each node, the following definitions must be specified in nodes that use the Global Archive Journal facility:

• Archive-journal target node
  Create the global archive journal service definition and the archive journal service definition.
  
• Archive-journal source node
  In the jnl_arc_name operand of the system journal service definition, specify the node identifier of the archive-journal target node and resource group names of archive journal files.
  

You must unload every OpenTP1 node which does not use the Global Archive Journal facility.

The following figure shows the relationship between the global archive journal service and resource groups.

Figure 6-7 Relation between the global archive journal service and resource groups

A filegroup that is waiting to be unloaded needs to be copied (unloaded) to a regular file, using an OpenTP1 command. An unloaded archive journal file is called a global archive unloaded-journals file.

When one or more archive journal filegroups are not yet unloaded, but no swap destinations are available, the global archive journal service terminates abnormally.

(a) Journal maintenance of a global archive unloaded-journals file

As with a system journal file, an unloaded ordinary file can be used for recovering DAM files and editing uptime statistics. Also a user journal can be inherited by an offline program.

A global archive unloaded-journals file contains system journal information about OpenTP1 nodes. You can edit this journal: for example, by editing merged uptime statistics or sorting OpenTP1 node journals by time.

In an OpenTP1 archive-journal source node, the following statuses of system journal files are added:

• archived/not archived
  Indicate whether or not the filegroup has already been sent to and stored in an archive journal file.
  

If a standby system journal filegroup has been sent to an archive journal file and the filegroup has overwrite-permitted status, the standby system journal filegroup can be swapped in to become the current system journal filegroup regardless of whether or not the archive journal file has been unloaded.