Start CA CSM

How to Upgrade CA CSM › Install CA CSM › Start CA CSM

Start CA CSM

The JCL members to start CA CSM are either in your JCL data set (RunTimeMVSHLQPrefix.JCL) or in your PROCLIB data set (RunTimeMVSHLQPrefix.PROCLIB). The member location is indicated in the summary report of the CA CSM installation and setup process. You can submit or start one of these members to run it as batch jobs or started tasks.

CA CSM allocates files on startup and during operation. If your site has products interfering with file allocation, verify that DD statements to exclude such processing are included in the MSMTCSRV JCL member that starts the CA CSM application server.

Note: The CA CSM application server uses a default region size of 768 MB. If you want to change this value, update the REGSIZE parameter in the MSMTCSRV JCL member. Also, update the Xmx value in the following statement in the SAMPLIB(MSMLIB) member:

IJO="-Xms128m -Xmx768m -Xss768m"

Follow these steps:

Verify that your address spaces from the previous version of CA CSM are down.
Unmount the APLROOT, SCROOT, and LJWK mount points from your previous version.
(Optional) Back up your previous version CA CSM start procedures and copy the latest version procedures to your production library.
Submit the MSMMUFS JCL member or start the MSMMUF PROCLIB member.
The CA Datacom/MSM Multi-User Facility (MUF) address space starts.

Note: All data sets in STEPLIB must be APF-authorized.

If the MUF starts up successfully, messages similar to the following example appear:
```
DB00226I - MULTI-USER ACTIVATED XCF SUPPORT
DB00222I - MULTI-USER ACTIVATED CCI SUPPORT
DB00201I - MULTI-USER ENABLED, CXX=cxx_name  MUFNAME=muf_name   AD
```
Submit the MSMDBSVS JCL member or start the MSMDBSRV PROCLIB member.
The CA Datacom/MSM server address space starts.

If the server starts up successfully, messages similar to the following example appear:
```
DSV00049I-CA Datacom Server Version 14.0 INITIALIZED -server_name
```
Submit the MSMTCSRV JCL member or start the MSMTC PROCLIB member.
The CA CSM application server address space starts.

If the server starts up successfully, the following message appears in STDOUT:
```
MSM0009I - CA CSM startup complete.
```
If the startup fails, the following message appears in STDOUT:
```
MSM0010E - CA CSM startup failed.
```
In addition, depending on the outcome of the startup, one of the following messages appears in the system console:
```
MSM0009I CA CSM STARTUP COMPLETE 
MSM0010E CA CSM STARTUP FAILED
```
Note: The startup JCL for the CA CSM application server region has a SYSMDUMP DD statement that is commented out. If your site standards and system support the capture of this dump to the spool system, you can uncomment the DD statement to provide for dump captures in the case of failures.

After the successful startup of the CA CSM application server address space, users can log in to CA CSM through a web browser.
After you successfully bring up CA CSM for the first time, comment out the DBUPDATE DD card in the MSMTCSRV JCL member or MSMTC PROCLIB.

Notes:

Do not start the MSMTCSRV job (manually or with automation) until the MSMDBSRV job initialization completes and the BPXM023I message appears.
After you successfully start up the CA CSM application server, if the following message appears, ignore it:
```
INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java library.path:
```
CA CSM does not require the installation of this library.
Do not change any CA CSM application server startup JCL parameters unless CA Support requested it. Doing so could make CA CSM inoperable.
If you restart the CA Datacom/MSM server, restart the CA CSM application server.