How to Install CA CSM › Perform Post-Installation Tasks › Set Up CCIDSCSV and CCISPNSV on Each Target System

Set Up CCIDSCSV and CCISPNSV on Each Target System

The load modules and sample procedures for the SDS are delivered as a contributed CA Common Services for z/OS function CETN500. CETN500 is available for all supported CA Common Services for z/OS.

Installing CETN500 creates the address space CCIDSCSV or CCISPNSV as needed on the target system. Do not start the CCIDSCSV or CCISPNSV address space manually. CCIDSCSV is started for every Validate action that users trigger in the CA CSM System Registry. CCISPNSV is started for each Deployment action users trigger in the Software Deployment Service (SDS). CCIDSCSV and CCISPNSV end after the completion of their associated tasks. The system discovery module resides in the CA Common Services for z/OS base FMID and its associated non-PDSE load library.

Follow these steps:

1. Verify that the following CA Common Services for z/OS maintenance and functions are installed:

   CA Common Services for z/OS r12

   • CETN500
   • RO17488
   • RO19624

   CA Common Services for z/OS Version 14

   • CETN500

   In addition, install any additional maintenance that is associated with any of these versions when it becomes available.

   CETN500 installs modules into one of the following locations:

   • CAIPLD for CA Common Services for z/OS r12
   • CAW0PLD for CA Common Services for z/OS Version 14.0 and above
2. Create an independent file system (HFS or zFS) to house the SMPWKDIR directory and the SDS FTP landing directory.

   ETNI0100 provides a sample job that creates a zFS file system.

3. Mount the file system that you created. Create the SMP/E SMPWKDIR directory and the SDS FTP landing directory under the file system mount point.

   ETNI0200 provides a sample job that creates the mount point, mounts the zFS file system, and creates the SMP/E SMPWKDIR directory and the SDS FTP landing directory.

4. Verify that you update your BPXPRMxx member in SYS1.PARMLIB with the file system and mount point that you defined earlier.
5. Modify your CAIENF procedure to append the CAIOPTN library member MSMSPNPM, delivered by CETN500, to SPNPARMS DD statements.
6. Verify that nodes and connect statements that point to the CAICCI running on the CA CSM host exist in the target system CCIPARM statements. These nodes and connect statements ensure CAICCI network connectivity to the CA CSM host and all target systems.

   Note: CAICCI can use protocols VTAM LU0 and/or TCPIP and/or XCF for a connection path between systems. Use one or a mixture of protocols that best meet your organizational policies, procedures, and standards. Verify that the CAICCI Spawn Facility is active in both the CA CSM host system and target system CAIENF and CAICCI.

7. Copy CCISPNSV and CCIDSCSV sample procedures from the CA Common Services for z/OS target zone PROC library (CCShlq.CAIPROC for r12; and CCShlq.CAW0PROC for Version 14.0 and above) to your STC PROC library.
8. Modify CCISPNSV and CCIDSCSV procedures to meet your organizational standards.
   • Verify that SMPWKDIR is correctly set up for your installed file system and mount point as done in steps 2 and 3.

     The subdirectory should be created as a mount point directory for the shared DASD switched file system, if used, for example, /cai/ccispnsv/msmMPm.

   • Verify that the SMPJHOME and SMPCPATH point to the Java home directory and home SMP classes for your system.

   You can change the name of these procedures. However, you must change the CAICCI SPAWN parameters that reference MSMD_DSC_APPLICATION for System Discovery and MSMD-DPL_APPLICATION for the SDS in all systems. The CAICCI SPAWN parameters are defined in the CAIOPTN library member MSMSPNPM referenced by the SPNPARMS DD statement.

9. Verify that the user ID associated with the CCISPNSV procedure has the correct security access and privileges. The associated user ID should have a valid OMVS segment, and all security items that are associated with the user ID for CAIENF and CAICCI. You can use the CAIENF user ID or you can use your owned defined ID.
10. Verify that the CA Common Services for z/OS load libraries are APF-authorized.