Mdisk to SFS
search cancel

Mdisk to SFS


Article ID: 42959


Updated On:


Mainframe VM Product Manager VM:Manager Suite for Linux on Mainframe VM:Manager Suite for z/VM VM SUITE



Is there an easy or automated or documented way to move from having all the VM:Manager Suite product disks on minidisks to having them in SFS instead ?

Preferably a method other than reinstalling everything from scratch, plus reinstalling all the service. 


Our recommendation is that you rename the current product install user id and reinstall using the SFS version of component. If using CASYS filepool, you can use our provided 'SFS' ppf override, for instance, specifying component VMSECURESFS will use our supplied override for sfs. If using a different filepool, you would need to create your own override PPF. 

Please review the following steps, using VM:Secure as an example. . 

1. Keep in mind that with our VMSES install, the installed code and what the product is running from is now separate so unless you do a VMDEPLOY, you will NOT impact the running server. 
Only VMDEPLOY will move the logic to the server runtime disks/directories. 

2. Rename the current ZVMX030A user ID to something else. 
This will allow you to hang on to that install until you have the SFS install going. 

3. Re-install VM:Secure using component VMSECURESFS per the installation guide 
a. If you want to create a filepool CASYS for all the CA product software, then you can use our defaults that come with the VMSECURESFS component. 
b. If you want to use a different filepool name, then you will need to create an override PPF file for the VMSECURESFS component when prompted to do that in the VMFINS install.
Our install documentation contains the information to do this. 
c. You can then put the directories you want to use in that override PPF file for the VMSECURESFS component. 

4. Install the code but don't (of course) create the server user ID or VMDEPLOY the code. 
Just do the install up to the point the install has loaded the product material down to the disk. 

5. You then use that new PPF file going forward for everything where you would specify a PPF. 

6. Change the VMSERVER NAMES for VMSECURE. The PPF entry needs to have your override PPF is used and VMSECURESFS component. 

7. Re-apply any maintenance applied to the previous installation set.
If you only apply the maintenance that was applied to the mdisk version, there is no need to do VMDEPLOY at this time unless you want to test that the new set up is working. Otherwise, just VMDEPLOY with the next maintenance you apply. 

Something also to keep in mind that though in this case you are re-installing the ZVMX030A (VMSECURE) software, the VMSECURE server is still running so can be used for the user id definition and directory allocations for the new ZVMX030A user ID with SFS directories. 


Component: VMNG