We did have everything working. However, we opted to go with the default message server file size of 20GB and have recently decided to scale that back to 5GB.
We recreated new mount point datasets at 5GB using a new dataset naming syntax (virtually recreating a fresh deploy of the message server).
We unmounted the original mount points and remounted using the newly allocated zfs datasets.
Upon trying to start ZMSSTART, we are receiving:
run(adapter.java:515): No OPS instances detected
I stopped the task and unmounted the new mountpoints then remounted the old ones, all is well again. It appears as if there is an OPSMVS hook into the existing mounts that is preventing it from reading the new mounts?
Release : 13.5
Component : MAINFRAME TEAM CENTER AUTOMATION
MTC-A does not use hooks.