Manual Install Process › Migrating CA Chorus for Security and Compliance Management from CA Chorus r2.5 to r3 › Migrate CIA Real-Time Component

Migrate CIA Real-Time Component

We updated the Compliance Information Analysis (CIA) Real-Time component in CA Chorus r3 to enhance handling of user-defined fields (UDF). Enhancements include the following:

• Addition of the following CIA repository tables to support UDFs (updated data model and data dictionary):
  • ORGINFO
  • UDFCHAR
  • UDFNUM
  • UDFDATE
  • UDFTIME
• Removal of the following CIA repository tables to support UDFs (updated data model and data dictionary):
  • USERFLD
  • USERUSER
• Updated method for supporting UDFs in CIA batch unload and load processes.
• Support added for UDFs in CIA real-time processing.
• Support added for multi-valued UDFs in batch and real-time processes.
• Support added for different UDFs on multiple systems.
• Supported added for UDFs in a CIA CA Datacom/AD repository.
• The following CIA SAMPJCL jobs were updated to support the new method of processing user-defined fields:
  • CIADB2
  • CIADCOMD
  • CIADCOM
  • CIAALLOC
  • CIAUNLD
  • CIALOAD
  • CIALOADA
  • CIALOADC
• For CA ACF2:

  The control GSO Chorus record CIAGEXIT and CIAGFLD fields are obsolete and ignored during CIA real-time initialization and processing. You can supply a globalid in the CIA Unload Utility input control statements as the name of a user globalid exit module (‘GLOBALID EXIT(exitname’) or the external name of a single-valued, character type field that is in the logonid record (‘GLOBALID FIELD(fieldname)’). The globalid is used during CIA real-time initialization and processing. If a globalid input control statement is not specified in the CIA Unload Utility, CIA real-time processing uses the userid (logonid) as the globalid. For more information on the Globalid, see the CA ACF2 Compliance Information Analysis Guide.

Follow these steps:

1. Review Implementing CIA Real-Time for CA Chorus for Security and Compliance Management and follow the instructions to perform the following steps for a CA Datacom/AD or DB2 repository implementation:
   • Stop the CIA Real-Time Component
   • Implement the CIA Repository in CA Datacom/AD
     • Start the CA Datacom/AD MUF
     • Link the CIA functions with CA Datacom/AD
     • Delete the CIA repository for CA Datacom/AD
     • Define the CIA repository for CA Datacom/AD
   • Implement the CIA Repository in DB2
     • Start the DB2 subsystem
     • Link the DB2 Modules and Functions
     • Delete the CIA repository for DB2
     • Define the CIA repository for DB2
   • Estimate storage requirements for the Unload data set

     Important! The amount of space required for UDF significantly increased based on the number of users and UDF in your security database. Use the CA ACF2 Worksheet and CA Top Secret Worksheet provided to calculate the amount of space required for the Unload data set.

   • Allocate the Unload data set
   • Unload the security information
   • Load the CIA repository
   • Start the CIA Real-Time component

     Important! If you are using CA ACF2 and updated the ACFFDR, stop and restart the CIA real-time address space to refresh the in-core tables, which support UDF.