VMTDLMUT MODULE and customized VMTDLMSC EXEC were on VMANAGER admin disk 195. After installing Required Service RS1611 plus latest PTFs and running VMDEPLOY VMANAGER PRIMARY, the VMTDLM* files were missing.
The VMTDLMUT MODULE is deployed to the VM:Tape ADMIN TAG.
The VMTDLMSC EXEC is provided as a sample EXEC. It is installed to the SAMPZ disk as VMTDLMSC XEXEC.
It's possible you have the VM:Tape ADMIN TAG (VMANAGER ADMIN) redirected to the VMANAGER ADMIN TAG. Check and see.your VMSERVER NAMES file for that.
In general, VMDEPLOY deploys specifically to the target TAG exactly the files that the BUILDLIST associated with that TAG for the products indicates should be on that disk target and ERASES anything that is not in the BUILDLIST. This is by design to manage upgrades, etc... to remove old or obsolete code from the target disk. which is why the VMTAPE files got removed.
The exceptions are the VMANAGER PUBLIC and VMANAGER HELP, that we by default for all products redirect to these targets … for these two targets, we do not erase any files.
PTF SO06467 was created that adds the deployment of the VMTDLMUT MODULE to the PUBLIC disk in addition to the VMTAPE ADMIN disk.
* This PTF requires VMTAPE RSU-1801 to be installed before it can be applied.
Although the VMTDLMUT MODULE will now be deployed to the PUBLIC disk, your "driver" EXEC (VMTDLMSC) should be placed on the LOCAL
(A-Disk) or some other disk that has local code you've modified and not a disk that belongs to an ID that VMDEPLOY manages by copying and potentially deleting files.