After completing Production Task KVC0P001 or after system reconfiguration, the following tasks should be considered in the performance of the remaining product installation:
You may need to update this task before proceeding with additional tasks, if, for example, your target Production operating system is configured differently from your Test System (although good testing practice suggests that the same software configuration be used even if the Test System does not require all of the available features). Similarly, you may need to generate multiple target Production Systems.
Each time the Production Generation minidisk address specification is changed in this task for an enhanced service system release, you must re-execute panel KVC0-I075. The CAKVBLD command contains imbedded minidisk information required for proper system generation.
Your responses in this task influence the defaults for building and checking the CA Top Secret PARMS file in Task KVC0I070. If you need to execute that task, you should update the information here first.
See the previous two procedures.
See the first procedure in this list.
Because of the structure of the z/VM Access Control Interface, it is impossible to AUTOLOG more than one CA Top Secret server at the same time. However, you may wish to maintain a Test server and Production server for ease of testing, or to facilitate second-level testing. Remember that you may deactivate one server and activate another having a different z/VM user ID (that is, TSSVM and TSSVMB).
Note: Be careful when activating servers with different software maintenance levels. Upgrades in server software, especially new product genlevels, may require corresponding service in CP. You should not mix genlevels between the server, CP and CMS.
If you need to define a new CA Top Secret server for the Production System, or to change the definition of the Production server due to software release level requirements, execute this task.
This task must be executed if you have newly created the CA Top Secret server for Production System use.
If you have a separate Test facility, it might have its own CA Top Secret security database or share the Production data base. If necessary, specify or create the Production data base files using this task.
Each time you execute Production Task KVC0P001, the customer encryption key specified for the Test System is carried over to the Production System. If your Test System Security File encryption key differs from that of the Production System, you will need to execute this task.
The Installation Exit module, TSSINS, is copied from the Test System minidisk to the Production Generation minidisk when you copy component files to production. This is done if changes were required to the Installation Exit to support the current software, and to ensure the use of the tested version of your Installation Exit. If this is inappropriate, execute this task to retrieve the required Installation Exit module for production use.
If you have separate Test and Production servers, you will need to execute this task to generate the Production server. If, on the other hand, you have only one server and you are testing new server software maintenance, you will have regenerated the server nucleus (using the appropriate Test System generation task). Should it become necessary to fall back to the previous version, regenerate the server using this Production task to reinstate the latest validated level of service.
Use this task to create or modify the CA Top Secret PARMS file for your Production System if you have just created the Production server, have specified new options in previous tasks, or need to implement new control options for the Production z/VM facility.
Execute this task if you use a different maintenance virtual machine to generate your Production z/VM CP system, or if you have changed the Production Generation minidisk address in Task KVC0I000. The CAKVBLD command contains imbedded minidisk information and must be kept up-to-date on the 191 disk to ensure that CP and CMS are built with Production object code and tools.
Execute this task to build a new CP nucleus for Production using the newly validated level of CP modules.
This task is included to remind you that the Production System is not complete until you have IPLed CP with current software. It should be noted that, unlike generating the Test System, it is not necessary to execute this task To confirm product installation. The Production System is considered to be in place and all Test System APARs are updated to reflect this as soon as you execute Production Task KVC0P001.
Information given above for Task KVC0I079, applies to this task as well.
Execute this task if you are enabling the CA-Register interface for the first time or if maintenance has been applied to the CA Top Secret exit program for CA-Register.
|
Copyright © 2013 CA.
All rights reserved.
|
|