Installation Procedures › Define the CA-Activator Machine

Define the CA-Activator Machine

If this is the initial installation of CA Top Secret at your site, you must designate a CA product maintenance virtual machine from which the product is installed and maintained. For information, see the CA‑CIS CA-Activator Reference Guide.

You may already have installed other products using Common Infrastructure Services, at which time you defined a common CA‑CIS product maintenance ID (such as CAIMAINT). Use this virtual machine to maintain this product. Sensitive files and non‑public object code are migrated to a separate Production Generation disk when the product is moved to Production.

The Production System disk can safely be made available to decentralized administrative personnel and users of other CA products installed on the same disk. However, these non‑public files is present on the Test System minidisk. For this reason, you may wish to install CA Top Secret on a separate maintenance user ID, particularly if many users have access to the Test system minidisk for administration and use of other products.

If you have already defined a CA product maintenance virtual machine for this product (or want to share an existing one), the only required steps are to increase the minidisks by the recommended sizes and to define a Production Generation minidisk (322).

These tasks are described in the CA‑CIS CA-Activator Reference Guide:

• Define the CA-Activator product maintenance virtual machine.
• For CAIMAINT, CA Top Secret for VM installation requires a virtual machine storage size of at least 32 MB (32M).
  • CA-Activator requires additional permanent disk space as detailed in the following chart. Approximate allocations are shown for disks formatted with a blocksize of 4 KB.

             work  disk    test desk   production disk production Generation disk
            	(191)          (291)       (391)           (322)
    Blocks   2000           8800        3000            1800
    

  • You should over-allocate all CMS-formatted disks by 30% to accommodate future maintenance.
  • The 191 disk (A‑disk) holds the CA-Activator files.
  • The 291 disk holds all files loaded for the Test System.
  • The 391 disk holds Production System copies of administrative applications, tools, and public files.
  • The 322 disk holds the Production System copies of sensitive object code and system generation tools.

  As an additional safeguard, CA-Activator checks to be sure enough disk space is available before installing a new product.

• Load the CA-Activator files from the CA‑CIS for z/VM tape to the A‑disk.
• Customize CA-Activator’s profile.

CA recommends that you define a new CA-Activator CAIMAINT machine for the r12 installation. This allows you to preserve your current CA-Activator environment during the conversion process.