Filter
Top Products
Starting and Setting Up RTR
2.3 Creating a Recovery Journal
• The operator should move any duplicate copies of journal files to a
location other than the
rtrjnl/groupname
directory so that RTR will
see only the one it created.
• Track duplicate copies of journal files in the log file to prevent RTR
seeing more than the one it created and issuing the SPUJOUFIL
error message.
• If it is determined that a journal is SPURIOUS by means other than
improper copying, then a backup copy followed by a destruction of the
transactions contained in a journal can be performed by the
CREATE
JOURNAL/SUPERCEDE
command.
2.4 Changing a Facility
RTR facilities can be altered either by deleting and re-creating them using the
delete facility create facility
commands. Alternatively, you can use the
extend facility
and
trim facility
commands.
With sufficient redundancy in a system, facility modification can be carried out
with minimal interruption to the application.
Note
The RTR facility defines the nodes used by an application, and the roles
(frontend, router, backend) they may assume. You do not need to change
facility definitions in the event of node or link failures.
In the example in Figure 2–1, assume that the FE3 node is being removed from
the FUNDS_TRANSFER facility. Since FE3 is a frontend for this facility, only
the routers (TR1 and TR2) need be reconfigured. The routers can be reconfigured
one after another, so that the service provided to the remaining frontends (FE1
and FE2) is not interrupted.
Example 2–3 shows the
delete facility
and
create facility
commands that
are issued from node BE1 (for example), in order to achieve this reconfiguration.
2–4 Starting and Setting Up RTR