I was looking at job CSMN6007 and noticed a lot of references to deleting the user database:
//* DELETE DATACOM CONTROL DATASETS //*
//* DO NOT RUN WITHOUT VERIFYING THAT YOU WANT TO DELETE
//* YOUR CXX, LXX, AND PXX BEFORE YOU RUN
//* I M P O R T A N T
This is my first time installing MSM (the guy who did it before is no longer here). Prior to starting, I was looking (or trying to understand) the methodology of the installation. I opted to do a full new install rather than an upgrade. It looks like there is a database and stuff on the unix side that isn't supposed to contain a version number in the path name as it will be used in future upgrades. For that reason, I decided to do a full install (new) since the guy before us had put a version in the path of the MSM product. On job CSMN6007, it also references databases, etc. The dataset names (on the z/OS side) in this job have a version number. Will these z/OS files be used for a future version or will the next upgrade define its own?
It is only for the /mpm path that we recommend not using a version number for.
It will not have any impact on the functioning of CA CSM nor is it related to what is in CSMN6007..
After a new install there are no file systems for the /mpm path.
After CSM is started for the first time it allocates, formats and mounts the first file system which is APLROOT to /mpm.
It allocates and formats others like CASC1 that is mounted to /mpm/scroot/DatabaseM/cars etc.
There's no need to be concerned with this during the install of CSM. The MSMSetup.sh and the jobs in the .JCL PDS takes care of all this. Fior each file system created by CSM it stores a MOUNTPOINT row on the database that contains the name of the file system and the path name for /mpm. Each row hs a unique mount point/path under /mpm.
The CSMN6007 job is set up to delete the files if they already exist, but this is a new install so for you they
do not exist so it will be skipped.