Function shipping examples
These examples illustrate the lifetime of the mirror transaction and the information that flows between the application and its mirror.
The examples contrast the action of the mirror transaction when accessing protected and
unprotected resources on behalf of the application program, over MRO, ISC, or IPIC
links, with and without MRO long-running mirror tasks.
Figure 1. ISC function
shipping: simple inquiry. In this example, no resource is changed; the session is freed and the mirror
task is stopped immediately.

Figure 2. MRO or IPIC function shipping: simple
inquiry. In this example, no resource is changed. Because
long-running mirror tasks are not specified, the session is freed by System B
and the mirror task is therefore stopped immediately.

Figure 3. MRO or IPIC function shipping: simple inquiry. In
this example, no resource is changed. However, because long-running mirror tasks
are specified, the session is held by System B, and the mirror task waits for
the next request.

Figure 4. ISC, MRO, or IPIC function shipping:
update. Because the mirror must wait for the REWRITE, it becomes
long-running and is not terminated until SYNCPOINT is received. The enqueue on
the updated record is not held beyond the REWRITE command if the file is not
recoverable.

Figure 5. ISC, MRO, or IPIC function shipping: update with ABEND.

Figure 5 is like Figure 4, except that an abend occurs during sync point processing.
Figure 6. MRO or IPIC function shipping: update using MROFSE or IPCONN MIRRORLIFE(TASK) to
extend the life of the mirror transactions. Because the mirror must wait for the REWRITE, it becomes long-running. On an MRO
connection, setting MROFSE=YES on System A prevents the mirror task on System B from
being terminated after sync point. The mirror task on System B terminates only when
the task on System A terminates. To extend the life of mirror transactions using
IPIC connections, use the MIRRORLIFE(TASK) option on the IPCONN resource definition
on System B.
