Initialize the CA CSM 5.1 database

Products

• Mainframe Software Manager (Chorus Software Manager)

Issue/Introduction

Is it possible to initialize the CA CSM 5.1 database to get a fresh restart that cleans up the file systems created by CA CSM?

Environment

Release: MSMNGR00200-5.1-Chorus Software Manager
Component:

Resolution

This is the procedure to initialize the database and restart. Note that this procedure is only valid for sites that did a new install of CA CSM without upgrading from a previous release. Look in the /MSMSetup/MSMSetupOptionsFile.properties file for parm  PreviousRelease.MSMPATH=

If this is assigned a /msm path DO NOT attempt this procedure.

Before shutting down MSMTC, go to the settings tab, system settings and get a screen print of all that is under it. Especially software acquisition. This is where you will have HTTP and FTP proxies defined, You may not be using any but just in case. You may need to re-enter these.

Under mount point management check off Unmount at Shutdown and click apply to save the change. It may already be checked off. 

You may also want to go to the SMP/E environment and note all your current CSI's because these will have to be re-migrated back into CA CSM. 

Shutdown MSMMUF, MSMDBSRV and MSMTC. 

Look in your SAMPLIB(DBINIT) member and note the HLQ assigned to parm mpmHlq. 

Delete all these file systems created by CSM with HLQ assigned to mpmHlq.

Next run CSMN5106 in the .JCL PDS for CA CSM to recreate the database. Before running this verify that you have these datasets 

hlq.ADCXX.BKP 

hlq.DB002.BKP 

hlq.DB015.BKP 

hlq.PCY4000.BKP 

hlq.JNL4000.BKP 

hlq.SRG4000.BKP 

If these have been deleted/missing DO NOT attempt this procedure.

Run CSMN5108  to startup MSMMUF. 

Run CSMN5109 to execute constraint confirmations. 

Run CSMN5110 to shutdown MSMMUF. 

 

At this point you will have a new database but no file systems. Some of these will be recreated on the restart of MSMTC such as APLROOT and the others when an update product release is done. 

 

Review your SAMPLIB(DBINIT) member to verify that these parm are updated and not commented out. Here is an example:

mpmPath=/u/users/idmsdev/level-1/userid/r61/mpm 

mpmHlq=USERID.OMVSUSR.CAMSM 

mpmAllocation=SMS 

mpmStorclas=TSO 

mpmMgmtclas=TSO 

#mpmDataclas= 

#mpmUnit= 

#mpmVolser= 

mpmFilesystemType=ZFS 

mpmAutomount=true 

#mpmPrefix= 

If you are using SMS then unit and volser are not needed 

scDatasetPrefix=CASC 

scRoot=/u/users/idmsdev/level-1/XXX/r61/mpm/scroot <<< make sure this is not a comment 

#scStorageClass=comment 

scPrimBig=80 

scSecBig=80 

 

dsiHost=localhost 

 

dsiPort=7173 

dsiConf=/u/users/idmsdev/level-1/userid/csm61/msmruntime/dsi/dsi.conf 

#dsiKdb=/RunTimePath/dsi/cert/CA_SelfSigned_Server.kdb 

#dsiSth=/RunTimePath/dsi/cert/CA_SelfSigned_Server.sth 

#dsiLabel=Cert for SelfSigned Server 

#dsiVerPeer=false 

sisGimunzipTempPrefix=XXXXXX 

sisExecutorServerDsnPrefix=PUBLIC 

sisGimunzipTempVolser= 

sisExecutorOutputStorclas= 

#sisExecutorOutputUnit= 

#sisExecutorOutputVolser= 

#sisServerUnpaxTempDir= 

# 

# |** Product Acquisition Service **| 

# 

# |** PAS component keys **| 

PASAdvancedSettingsPDS=XXXX.CSM61.RT.SAMPLIB 

PASAdvancedSettingsMember=PASADVOP 

# 

# |** Task deletion **| 

# 

# When SAF Security is disabled, the below parameter is set 

sysTaskDeleteOverrideEnabled=true 

 

Restart MSMMUF, MSMDBSRV and MSMTC. As soon as you login check off Ignore Common Products During Discovery and click apply to save the change.