Long-running mirror tasks for IPIC

Normally, IPIC mirror tasks are stopped as soon as possible, in the same way as described for ISC mirrors, to keep the number of active tasks to a minimum and to avoid holding on to the session for long periods.

However, for some applications, it is more efficient to retain both the mirror task and the session until the next sync point, though this rentention is not required for data integrity. For example, a transaction that issues many READ FILE requests to a remote system might be better served by a single mirror task, rather than by a separate mirror task for each request. In this way, you can reduce the overheads of allocating sessions on the sending side and attaching mirror tasks on the receiving side.

Mirror tasks that wait for the next sync point, or beyond the next sync point, even though they logically do not need to do so, are called long-running mirrors. They are applicable to MRO and IPIC links only. For IPIC links, the lifetime of the mirror is specified on the system on which the mirror runs by using the MIRRORLIFE attribute of the IPCONN on which the request is received. A long-running mirror for an IPCONN specified with MIRRORLIFE(UOW) is stopped by the next sync point (or RETURN) on the sending side. A long-running mirror for an IPCONN specified with MIRRORLIFE(TASK) is stopped by the end of the task on the sending side.

For some applications, the performance benefits of using long-running mirrors can be significant. MIRRORLIFE(TASK) improves performance only if most applications that are initiated from the front-end region have multiple sync points and function shipping requests are issued between each sync point.

Specify MIRRORLIFE(TASK) or MIRRORLIFE(UOW) with caution, especially if distributed program link (DPL) requests with SYNCONRETURN or TRANSID are used.

Do not specify MIRRORLIFE(TASK) when long-running tasks might be used to function ship requests. The long-running tasks will retain the use of a SEND session for its entire duration and the SEND session will not be available for allocation to other tasks when it is no longer used. The MIRRORLIFE setting is not reflected in the lifetime of the mirror task until a file control, transient data queue (TDQ) or temporary storage queue (TSQ) request is function shipped.



dfht10b.html | Timestamp icon Last updated: Sunday, 4 June 2017