Volume Clones - Procedure Clarification Request

There is a "Volume Clones" section in Release Notes V4.8, page 27.  This is the latest documentation I can find, but understand the procedure may be the same for later versions? Currently, I am running Proview Workstation version 6.1 on Debian 12 and Proview Workstation version 7.0 on Debian 13.  Both workstations work as advertised.

Following the Clone Volume procedure, a CloneVolumeConfig object named VolCloned is created with a ParentVolume = VolOK in the PwR Directory dialog.  The Global Volume list is updated with VolCloned.  A new NodeConfig object is configured as "Cloned", but the new node's RootVolumeLoad cannot select the new cloned volume name.  It does not appear in the drop-down menu.  A CloneVolumeConfig object is not recognized as a valid volume choice.  Is this an artifact, where in version 4.8 the volume name could be typed in directly?  Or, is this a procedural error on my part?  Also, when activating Functions/Clone Volume in VolOK, a temporary script is not generated in $pwrp_cnf, as mentioned.  Is the "Volume Clones" procedure still valid or does it need an update or something else?  Looking forward to your explanation.

Regards,
/Ron

 

Hi Ron,

The ClonedVolumeConfig objects should be included in the available names for the RootVolumeLoad object, that is something I’ve missed. You can still type in an arbitrary name with Ctrl+Q.

The script file on $pwrp_cnf is not generated by the clone function, it’s a file that you can create when the cloned volume should not be an exact copy of the original volume. You have the possibility make minor modification, for example change objects names, change attribute values, add or remove objects.

/Claes

Thanks Claes for your quick and informative response. Using Ctrl + Q, VolCloned was used to add VolCloned to NodeConfg-RootVolumeLoad.

From VolOK -> Functions -> More -> Clone Volume, a message occurs at the bottom of the dialog: "unable to open file".

In file: directory.wb_load, VolCloned appears twice as RootVolumeConfig and CloneVolumeConfig.

In directory $pwr_cnf, a file was created manually, called: VolCloned_clone.pwr_com with content: main(), endmain().

My understanding is changes made to VolOK + .pwr_com exceptions are compiled as VolCloned for the new cloned node?

I don't know what file is "unable to open". Any additional light you may shed on this topic is much appreciated.

Regards,
/Ron

Hi Ron,

The cloning means that a temporary copy of the source volume with the volume identity and name of the clone volume is created in memory. The script is executed for this volume and the volume is built, ie the plcpgms are compiled, cross reference files are generated and the dbs-file is created. The volume is then deleted so no modification can be made later. From the generated files a node can be built that has the cloned volume specified with a RootVolumeLoad object.

VolCloned should appear as ClonedVolumeConfig and RootVolumeLoad (not RootVolumeConfig).

Scriptfile with lower case, $pwrp_cnf/volcloned_clone.pwr_com

endmain in the script without parenthesis.

/Claes