How to Install 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 that interfere 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 512 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 -Xmx512m"

Follow these steps:

1. (CA CSM upgrade only) Verify that your address spaces from the previous version of CA CSM are down.
2. (CA CSM upgrade only) Unmount the APLROOT, SCROOT, and LJWK mount points from your previous version.
3. (CA CSM upgrade only) Optionally, back up your previous version of CA CSM start procedures and copy the latest version procedures to your production library.
4. If you are starting the latest CA Datacom/MSM MUF for the first time, verify that the following post installation jobs have previously been manually executed successfully.
   • For an upgrade (xx represents the CA MSM version you are upgrading from)
     • CSMUxx08
     • CSMUxx09
     • CSMUxx10
   • For a new installation
     • CSMN5108
     • CSMN5109
     • CSMN5110
5. 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:

   DB00215I - CA Datacom/DB r12 at service pack: SP0
   DB00212I - CA Datacom SQL r12   at service pack: SP0
   DB00226I - MULTI-USER ACTIVATED XCF SUPPORT (RIMF20,mufname)
   DB00222I - MULTI-USER ACTIVATED CCI SUPPORT (caicci_sysid,mufname)
   DB00201I - MULTI-USER ENABLED, CXX=cxx_name    MUFNAME=mufname SVC=svc_number
   

6. Important! Verify that the value of the MUF parameter in the runtime CUSMAC(DBDATIN1) member matches the value of the MUFname keyword in the options file (MSMSetupOptionsFile.properties). Otherwise, you cannot start the MUF.
7. 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:

   DB00101I - Started Job-MF2SRVR2 number-11326 CXX=CAMSM    Mufname=muf_name   Svc=svc_number
   BPXM023I (USER01) DSV00049I-CA Datacom Server r11       INITIALIZED -server_name
   

8. 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.

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.