Start of change
ANTX5174W
XRC VOLUME(volser/devnum) IN SESSION(sessionid) CONVERTED FROM DVCBLOCK(dvcblock1) TO DVCBLOCK(dvcblock2)

Explanation

The WorkloadWritePacing parameter in parmlib requests that workload-based write pacing be enabled for the XRC session sessionid, and during processing of an XADDPAIR or XSET command, to maintain compatibility with workload-based write pacing, the DVCBLOCK setting for the volume indicated by volser/devnum was automatically converted from dvcblock1 to dvcblock2. This typically occurs when dvcblock1 is ON and dvcblock2 is WPdiscretionary, where discretionary is the sixth level defined in WLM.

System action

The XADDPAIR or XSET command succeeds, but the volume does not use DVCBLOCK(dvcblock1). Instead, the volume participates in workload-based write pacing on z/OS systems on which it is enabled, and uses volume-level DVCBLOCK(dvcblock2) on other application systems, such as z/Linux or z/VM. Note, also, that the WrtPacingResidualCnt parameter in parmlib will be used to define the threshold instead of the DeviceBlockingThreshold parameter. This results in XRC using DVCBLOCK(dvcblock2) for the specified volser/devnum until explicitly updated using either an XSET or XADDPAIR command.

System programmer response

None.

Source

Extended remote copy (XRC).

End of change