Previous Topic: CA CSM DownloadNext Topic: Use of Temporary File Systems


CA CSM Startup

This section describes the CA CSM startup process for both new and existing CA CSM installations.

At startup, CA CSM allocates and mounts file systems and USS directories. Before you execute MSMSetup.sh, define a mount point (for example, /u/users/msmserv/mpm) for the APLROOT file system. CA CSM allocates the file system and mounts it to this mount point.

Note: The MountPath keyword in MSMSetupOptionsFile.properties specifies the APLROOT directory. MSMSetup.sh populates the mpmPath parameter in the SAMPLIB(DBINIT) member with this value. The DBINIT member is used when CA CSM starts for the first time. On startup, the value is stored in the database. You can modify the value using the Application Root field on the Mount Point Management page on the Settings tab in the web-based interface.

Under the APLROOT file system, CA CSM creates four USS directories: sdsroot, scroot, ljroot, and tmproot. The USS directory ljwk is created under the ljroot directory.

The following list identifies the permanent file systems and their mount points:

hfs_prefix

This prefix is specified by the MVSHFSDsnPrefix keyword in MSMSetupOptionsFile.properties. MSMSetup.sh populates the mpmHlq parameter in the SAMPLIB(DBINIT) member with this value. On startup, the value is stored in the database. You can modify it using the Data Set Prefix field on the Mount Point Management page on the Settings tab in the web-based interface.

The tmproot USS directory is used for allocating and mounting temporary file systems as required during CA CSM operation.

You can define whether CA CSM mounts file systems at startup. The Mount Point Management page on the Settings tab in the web-based interface has an Automount option. If the option is enabled, CA CSM looks for and mounts all the file systems that it manages. If the option is not enabled, you manage the mount points by updating the BPXPRMxx member in SYSx.PARMLIB.