Submit CA Chorus and Discipline Jobs (Auto Config)

How to Promote a Test System › Promote a Test System without CA CSM › Configure Your Product for Promotion (Auto Config) › Submit CA Chorus and Discipline Jobs (Auto Config)

Submit CA Chorus and Discipline Jobs (Auto Config)

Use this procedure to submit the jobs that the automated configuration process edited. In the following steps, use the jobs that include custom in the high-level qualifier (HLQ).

Important! If your site does not include a discipline, skip the step. Additionally, if you are installing CA Chorus to use only the Software Development Kit, skip all discipline steps.

Follow these steps:

Note: For each of the following steps, review the output to confirm that your submissions succeeded. If a submission fails, use the return code to resolve any issues.

CA Chorus Job Submission

Submit the following CA Chorus jobs:
1. ETJI0100 from custom_hlq.CETJJCL (Changes zFS ownership)
2. ETJI0101 member from custom_hlq.CETJJCL (Mounts user file systems)
3. ETJUDCDF and ETJUDCMT from custom_hlq.CETJJCL (Configures the Knowledge Center zFS)
4. APF-authorize the following data sets:
  - custom_hlq.CC2DLOAD (Includes the Time Series Facility (TSF) library)
  - custom_hlq.CETJLOAD (Includes the CA Chorus library)
  - custom_hlq.CETJPLD (Includes the CA Chorus library)
  Note: As part of the CA Datacom/AD prerequisite, the following libraries should be APF-authorized: datacomad_adthlq.CAAXLOAD (CA Datacom/AD load library) and datacomad_adchlq.CUSLIB (CA Datacom/AD customization library).
5. CPYAXDAT from custom_hlq.CETJJCL to copy AXDATIN1 and AXDATIN2 settings from CETJOPTN to &ADCHLQ.CUSMAC.
6. Start the CA Datacom/AD MUF for CA Chorus (/S your_muf_name). You established the name of this MUF during the prerequisite setup as noted in the software requirements of the Site Preparation Guide.
7. CHDB004 from custom_hlq.CETJJCL (Initializes the tables and defines the data sources)
  Note: To clean up and restart the initialization, execute the CHDB101 member in custom_hlq.CETJJCL, execute the CHDB102 member in custom_hlq.CETJJCL, and repeat 1g.
8. TSDB002 from custom_hlq.CETJJCL (Allocates and defines the TSF database to the CA Datacom/AD MUF)
  Note: If a step fails, the remaining steps do not execute. To clean up and restart the initialization, execute the TSDB102 member in custom_hlq.CETJJCL, execute the CHTSDBDL member in custom_hlq.CETJJCL, and repeat step 1h.
  
  Important! The TSF metric database uses large amounts of disk space. We strongly recommend that you set up automation to reclaim free space and monitor your database space usage. For information about setting up this automation, see the Administration Guide.
9. TSF#ALOC from custom_hlq.CETJJCL (Allocates the TSF VSAM data sets)
10. TSF#PPL8 from custom_hlq.CETJJCL (Populates the TSF VSAM data sets)
11. Copy customized CHORTSF from CETJJCL to PROCLIB
12. If you have a CHORTSF instance, which resides on same the LPAR as the original, it must use a different SUFFIX.
  1. Add the TSFSUFFIX=c|n parameter to the TSFPARMS member in CETJOPTN, using a one-character alphabetic (c) or numeric (n) identifier for the TSF region. The valid values are A to Z, or 0 through 9.
  2. Add the export TSFII='c|n' parameter to the ENVETJ member in chorus_2.5_runtime_hlq.CETJOPTN. This statement specifies a one-character alphabetic (c) or numeric (n) identifier for the TSF region in the JBoss environment settings. This value must match the value that is specified for TSFSUFFIX. The value must be in single quotes.
13. Start TSF (/S CHORTSF).
  Note: As part of the startup process, this job dynamically determines the associated ports (such as TSF query).
14. ETJI0145 from custom_hlq.CETJJCL. (Configures the JDBC driver for CA Datacom/AD)
15. (Optional) ETJI0110 member in custom_hlq.CETJJCL (Enables or disables HTTPS)
16. (Optional) If your TSF configuration includes a remote system, copy the customized CHORTSFR to a remote system PROCLIB and then start the CHORTSFR (/S CHORTSFR).
17. (Optional) If you are using an SMTP server to send notification emails, submit ETJI0135 from custom_hlq.CETJJCL.
18. (Optional) If you want to add a CA Chorus™ Software Manager link to the Quick Links module, submit ETJI0140 from custom_hlq.CETJJCL. If you are using an APPL name that differs from the default value for CA CSM (CSMAPPLM), modify the msmApplid in ENVETJ of custom_hlq.CETJOPTN.
19. (Optional) To set up High Availability, see the Administration Guide to review all HA implications, and then submit ETJARMP from custom_hlq.CETJJCL.
Important! Steps 2 through 5 detail the jobs to submit for each discipline. Complete the applicable steps and then go to step 6.

CA Chorus for DB2 Database Management Job Submission
Submit the following CA Chorus for DB2 Database Management jobs:
Important! Before finalizing DB2 subsystem connections in the following step, see the Manual Configuration Guide for a detailed explanation of DBA subsystems, confederations, and data sources.
1. E3KI0010 in custom_hlq.CE3KJCL (Defines DB2 subsystem connections)
2. E3KI0020 in custom_hlq.CE3KJCL (Defines data sources). The MUF must be active when you submit this job.
  Note: To clean up and restart the initialization, submit the CHDB101 member in custom_hlq.CETJJCL, CHDB102 member in custom_hlq.CETJJCL, CHDB004 from custom_hlq.CETJJCL, and repeat step 2b.
  
  Important! The next three substeps must be performed manually outside of CA CSM.
3. (Optional) If you are running any DB2 subsystems in Compatibility Mode (CM), override the DB2 execution mode (edit E3KMOD10 in your_chorusdba_hlq.CE3KPARM, and edit and submit E3K3I0030 in your_chorusdba_hlq.CE3KJCL).
  Note: The configuration tasks in the next two substeps are not required for an integration with CA Chorus Infrastructure Management for Networks and Systems.
4. Load CA Detector collection data for the TSF. Complete the tasks under Statistics Gathering Overview.
5. Enable DB2 object migration. Complete the steps in How to Enable DB2 Object Migration.
  Note: When you complete substeps c and d, return to this topic to complete the configuration.
CA Chorus Infrastructure Management for Networks and Systems Job Submission
Submit each of the following CA Chorus Infrastructure Management for Networks and Systems jobs:
1. FAWGSMP1 from custom_hlq.CFAWJCL (Sets the CA NetMaster NM for TCP/IP properties)
2. FAWGSMP2 from custom_hlq.CFAWJCL (Sets the CA SYSVIEW properties)
3. FAWGSMP3 from custom_hlq.CFAWJCL (Configures the sysview-module.xml file)
CA Chorus for Security and Compliance Management Job Submission
Submit the following CA Chorus for Security and Compliance Management jobs:
1. E1MI0010 member in custom_hlq.CE1MJCL (Establishes database connections)
2. E1MI0020 member in custom_hlq.CE1MJCL (Creates the CA LDAP files)
  Note: For the following two steps, run the jobs where DB2 or CA Datacom/AD is installed.
3. E1MI0011 (DB2) or E1MI0016 (CA Datacom/AD) in custom_hlq.CE1MJCL (Creates CIA database views)
4. E1MI0012 (DB2) or E1MI0017 (CA Datacom/AD) in custom_hlq.CE1MJCL (Creates CA Compliance Manager database views)
5. E1MI0014 member in custom_hlq.CE1MJCL (Defines the Security and Policy Administration nodes)
6. E1MI0015 in custom_hlq.CE1MJCL (Identifies the systems for use with the Security Command Manager module)
7. If you have CA DSI Servers running systems that are configured for use with the Security Command Manager module or the Security Simulation interface, add the following lines to the dsi.env file for each of those servers:
```
GSK_KEYRING_FILE={Path to the KEYRING FILE} 
GSK_KEYRING_STASH={Path to the KEYRING STASH file} 
GSK_KEY_LABEL=Cert for SelfSigned Server
```
CA Chorus for Storage Management Job Submission
Submit the following CA Chorus for Storage Management jobs:
1. E4HI0006 and E4HI0007 in custom_hlq.CE4HJCL (Creates the Storage Management interface database USS file system (CE4HVDB))
  Note: If you have an existing CA Chorus system and you want to use the database in a newer CA Chorus version, use the E4HDUPDT job to upgrade the newer system to use the older database.
2. (Optional) E4HI0008 and E4HI0009 in custom_hlq.CE4HJCL (Creates and mounts a USS file system to output Storage Management interface reports). Note the following points before submitting the jobs:
  - If you are using a new system for reporting, run both jobs.
  - If you are using an existing reporting system, run only E4HI0009.
3. E4HI0010 in custom_hlq.CE4HJCL (Identifies storage engine subsystems, creates a password for the Storage Management interface database, and creates an encrypted boot password for the database.)
  Note: If more storage engines are required in the future, this job can be rerun multiple times.
4. E4HI0011 in custom_hlq.CE4HJCL (Configures cost analysis, which is accessible from the Investigator.)
  Note: You can run this job with the default values and then rerun it after you see the objects in the Investigator.
5. Verify that the TSF configuration is set up. Each storage engine subsystem must be able to connect to the TSF using the loopback address of ‘127.0.0.1’ for an IPV4 stack. To determine if the stack is IPV4 enabled, enter the following command:
```
D TCPIP,stackname,NETSTAT,ROUTE,ADDRTYPE=IPV4
```
Finalize the Configuration
Submit the following jobs to activate your configuration and start CA Chorus components:
1. ETJI0105 member in custom_hlq.CETJJCL (Configures CA DSI)
2. ETJI0150 from custom_hlq.CETJJCL (Activates your configuration)
  Important! If you are completing this configuration as part of an upgrade, do not start JBoss until you have completed the upgrade procedure.
3. Copy the CHORJBOS member to a PROCLIB.
4. Start the CHORJBOS started task.
The following message appears when JBoss startup is complete:

ETJTC001I CA Chorus Startup Complete
Complete the tasks in Verify the Installation and Configuration and Post Installation Considerations.
CA Chorus and the applicable disciplines are configured.