Unified Install Process › Customize Members

Customize Members

The RUNCONF job executes a customization program that edits the members in the staging libraries. This program must be executed twice. The first run allocates a data set and copies all the variables that are required to customize the members. The second run substitutes the values specified for the variables into the members. To customize the members for your environment, complete the following steps.

Follow these steps:

1. Edit the RUNCONF job in the <stagelib_HLQ>.CHRSEC30.STAGE.JOBLIB staging library created in the previous step:
   • Edit the JOB statement to conform to your site standards.
   • Change "<yourUSSinstalldirectory>" to the complete USS path for the LDAP directory that was created during the UNZIPJCL job. Do not specify the trailing slash.
   • Change "<your_javalib>" to the fully qualified name of the data set containing your IBM Java modules.
   • Change "<your_tcpdata>" to the fully qualified data set name of the z/OS TCP/IP .DATA file.
   • Change "<yourjavahome>" to the complete USS path for the java JDK.
   • Change "<stagelib_hlq>" to the value that was specified for stagelib_hlq in the stag4xxx job.
   • Change "<config_hlq>" to the high level qualifier you wish to use for the data set that is allocated to hold your customization variables. It is acceptable to use the same value for all of the high level qualifiers.
   • Change "<custlib_hlq>" to the high level qualifier you wish to use for the customized libraries. It is acceptable to use the same value for all of the high level qualifiers.

   Note: Additional values can optionally be changed. See the notes in RUNCONF for more information.

2. Run the RUNCONF job.

   The first run allocates the <config_hlq>.CHRSEC30.CONFIG.DATA data set. All required variables are copied into this data set.

3. Review and edit the <config_hlq>.CHRSEC30.CONFIG.DATA (referred to as CONFIG.DATA later) data set. Several variables require changes and more variables can be changed, if necessary, to conform to site standards. See the documentation in this member to determine which variables require modification, which can optionally be changed, and which should not be modified.

   You must review or update the variables in the CONFIG.DATA data set prior to running the RUNCONF job for the second time. If a default value is provided, ensure that it is correct for your site. Variables with a value of 'changeme' must be modified.

4. Run the RUNCONF job again. The second run copies all members from the staging libraries into the customized libraries and applies all customizations to the members.
5. Review the customized jobs in the <custlib_hlq>.CHRSEC30.CUST.JOBLIB, procedures, parameter members, and configuration members in the customized libraries.

   Note: If any values require changes, it is recommended that you edit the value in the CONFIG.DATA data set and rerun the RUNCONF job. Doing so ensures that the change is propagated to all members that need the value.

6. Print and review the AREADME member in the customization JOBLIB data set for more instructions and notes regarding the customized members. To ensure this process is successful, you must follow the additional instructions contained within the AREADME.

   Important! We recommend printing the AREADME member for reference while editing and running the customized jobs.

7. Run the customized jobs that now reside in the customization <custlib_hlq>.CHRSEC30.CUST.JOBLIB. The jobs use the following naming conventions:
   • The first character of the job is J.
   • The second through sixth characters indicate the sequence number for the member. The jobs must be run in this order.

   The jobs must be run in the correct order using the sequence number.

   Most jobs are expected to get a return code of 0. See the AREADME file for exceptions. If a job does not have a return code of 0, review the job output.

   Note: The jobs ending in "SA" are security administration jobs. Some of these jobs require manual intervention in order to match your site standards and run successfully. Detailed instructions for these steps are provided in the AREADME member and in the comment boxes inside the jobs. Please review these jobs with the appropriate security administrator for correctness.

8. Some members created by this process are started task procedures and parameter files. Several customized jobs copy these members into PROCLIB and PARMLIB libraries. See the AREADME file for the data set names for these libraries. You are required to copy the procedures into a system proclib before you can start any of the started tasks. The parameter and config libraries are specified in several of these procedures. If you move the parameter members, you must also edit the procedures to specify the new libraries and ensure that the tasks have access to the new libraries.
9. Start the started tasks in the order described in the AREADME file. Ensure each started task starts successfully.

Note: After successfully starting the started tasks described in the AREADME file, you are ready to start the installation of the CA Chorus Security Discipline. The SECROLE member that is housed in the <custlib_hlq>.CHRSEC30.CUST.JOBLIB data set contains the variables you specified as part of the unified install process which you will need for the CA Chorus Security Discipline installation process. For more information on installing the Security Discipline, see the CA Chorus Installation Guide.