Alan O'Neill

As a follow-up, I found that adding the suggested line had two negative outcomes. One was that ^%RSE failed with an undefined error. The other was that when multiple routines needed to be changed by ^%RCE, the O/S path in the tf variable grew continuously until the string exceeded 256 characters and an error occurred. To address these issues, I altered the line to read as follows. i %ZC,tf'["/" s tf=$zparse(r,"DIRECTORY")_tf The second test (i.e., tf'["/") may be less than ideal. It works for me...

Thanks a million! That did the trick. To answer Bhaskar's question: All of the mounted partitions are ext4 file systems. I configure my systems with one "local" partition for the O/S plus a few (the number is dependent on the system) that are replicated via DRBD to a secondary location for disaster recovery purposes. Of course, to any application running on the system, it should perceive all partitions as residing on the local machine, and strictly speaking, the data is stored on the local machine...

%RCE deletes routines

%GI fails to read %GO file