Enabling and Disabling COPYWRITE

When a COPY statement is compiled, WFL selects an MCP procedure to handle the COPY. If a remote host transfer is indicated by a non local HOSTNAME, then the MCP procedure invokes MAGUS to examine the WFL COPY statement, and decide whether the request should be handled by COPYWRITE, or by NFT.
If MAGUS is not installed, then COPYWRITE cannot be called.
If the COPY process has SW4 set, then MAGUS unconditionally forwards the request to NFT. This provides a way of disabling an instance of a COPY from being handled by COPYWRITE.
If COPYWRITE must be completely disabled, then the DISABLE utility function can be used. COPYWRITE will remain disabled until an ENABLE function is performed.
When MAGUS is to be changed, COPYWRITE should be DISABLED, otherwise a subsequent COPY will call the old MAGUS, and the FILE/TRANSFER/SERVICES will attempt to link to the new MAGUS through the SL. When the old MAGUS has gone, and if the new MAGUS has already FROZEN, and failed to notify the MCP, because the previous version was still running, COPYWRITE can be reinstalled using the REINSTALL utility function.
The REINSTALL function can be used at any time, COPYWRITE will report that it is already installed, or the reason why it cannot be reinstalled. See the Installation instructions for more information.