Can two Hercules instances share a base DASD file in a shadow configuration?

This is a question out of curiosity, not out of any actual present need to use it.

 

 I see nothing in the docs that would prevent this scenario from working, but I'm asking here in case there is anything that would cause corruption in the base DASD file.
 

 The idea is that the base DASD is to be strictly read-only, never updated.  All DASD updates are to be stored in the shadow file only.  Both Hercules instances could and would be active at the same time.  Both Hercules instances could and would be both reading and writing to the DASD via their own separate shadow file at the same time.

 

 Note that this is NOT in pursuit of a "shared DASD" setup at the OS level.  The sharing would be strictly at the Hercules DASD I/O level to be able to share large "virgin" DASD files that shouldn't be changed.

 

 I do understand that if the shadow file for either instance needs to be merged with the base file for any reason, such a setup means that the previously "shared" base DASD file has to be cloned to another separate directory and the shadow file merged to the base file in the new directory only, and the config file using that shadow file updated to match the new base file location.

 

 Are there any caveats or gotchas that could corrupt the base DASD file in this scenario?

 

 Is the answer different for different versions of Hercules?

 

 Is the answer different if the host environment is Win64 vs Linux?

 

 Peter