target_mirror
Use this option if you want to copy members by the copy module also to additional libraries. Members written to mirrored datasets are not stored in a database. This option only ensures that a backup of members that are copied to target libraries is also copied to mirrored libraries. If the real target system and dataset match the ones specified by target_mirror option then copying to locations specified in the inner array is done. You can copy members to more than one library or system if you want. You can use wildcards both in and and also in and , as is shown in the sample below.
In the case of the above example this mirroring occurs:
If the target dataset is P391D.HOS.DATA.SYS on SYSH_ID system then members are mirrored to P391D.HOS.DATA2.SYS on the same SYSH_ID system.
If the target dataset is P391D.HOS.DATA.OUT on SYSH_ID system then members are mirrored to:
P391D.HOS.DATA.MIRROR1, ...MIRROR2, ...MIRROR3 on SYSH_ID system
P391D.HOS.DATA.PRE.MIRROR1,, ...MIRROR2 in SYSH2_ID system.
In the following examples mapping takes effect then any qualifier(s) appears at the place of asterisk:
Or with their variables:
It will map:
DDD.PROCMAN.TARGET.AAA.STEUKA to DDD,PROCMAN.TARGET.AAA.STEUKA.MIRROR DDD.PROCMAN.TARGET.BBB.STEUKA to DDD,PROCMAN.TARGET.BBB.STEUKA.MIRROR DDD.PROCMAN.TARGET.AAA.BBB.STEUKA to DDD,PROCMAN.TARGET.AAA.BBB.STEUKA.MIRROR
The mirroring works also when files are deleted. In this case approved members are deleted from target libraries as well as from all their mirrors.
Last updated