Journal DB2® Multisystem files

When you successfully start journaling on a distributed file, the system distributes the start journal request to the other servers in the node group.

All servers are attempted even if there is a failure at any one server. Once journaling is started on a server in the node group, it stays started even if there is a failure at any of the other servers.

The journal has to exist with the same name on all servers in the node group. The journal itself is not distributed, only the Start Journal Physical File (STRJRNPF) command.

The journal and its receiver are associated only with the changes made to the file on the one server. If you have two servers in the node group and a file is updated on both servers, the update on server A is only in server A's journal and receiver and the update on system B is only in system B's journal and receiver.

The journal identifier (JID) is different on each piece of the distributed file. Each server piece has its own JID. This means that you cannot use the journal entries that are deposited on one server to apply or remove journaled changes to a different piece of the file on another server.

Related concepts
Distributed database administration
Related reference
Start Journal Physical File (STRJRNPF) command