Case 2: Install additional products in an existing SMP/E environment with JOBGEN

Use this step-by-step guide to install additional products in an existing SMP/E environment using the Job Generator (JOBGEN) utility.

1. Invoke the JOBGEN utility, as follows:
   1. Enter the following command for the TKANCUS library from the existing SMP/E environment where you want to install additional products:
      
   2. Select option 2, Installation Workflow: SMP/E-install z/OS products with Install Job Generator (JOBGEN), from the z/OS Installation and Configuration Tool main menu:
      
2. Provide the JOBGEN output PDS where you want the jobs to be created:
   
3. Select the products that you want to install. In this example, additional products will be installed into an existing environment, so IBM Tivoli Management Services on z/OS is not selected:
   
4. Specify the required information in the panel:
   

   1 – Specify the names of the target and distribution zones and the global zone OPTIONS section, as well as the data set prefix for the SMPTLIB data sets that will be allocated for the RELFILEs. You must also supply the SMPTLIB volume serial number, which will be used for the SMPTLIB DDDEF entry.

   2 – Specify high-level qualifiers for the SMP/E data sets and the target and distribution zone data sets. In this example, qualifiers are provided for existing SMP/E data sets where the products will be installed. You must also specify at least one of the Volser, STORCLAS, or MGMTCLAS entries. If the target or distribution zone entries are left blank, they will be propagated from the prior panel row.

   3 – (Optional) Change the generated name prefix (1-5 characters) that will be used to name the generated jobs to install the selected products. You can also specify the jobcard information in the four lines that are available.

5. Provide the input location of the selected products. Only one input media type is allowed at a time. In this example, the DASD input RELFILE hilev is provided. (This is the high-level qualifier preceding IBM, which already exists on the disk):
   
6. If a z/OS UNIX System Services (z/OS UNIX) install environment is required by any of the selected products, the USS Install Path panel is presented. Provide the z/OS UNIX install root directory. It must start with a forward slash (/) and is case sensitive. This directory will be the mount point of the HFS/zFS file system that will be used for installation:
   
   In this example, the SMP/E environment did not have anything installed in z/OS UNIX, so a new install root directory will be provided, like in the Case 1 scenario. If there were any products installed already that are using z/OS UNIX, you must provide the install root directory that is already being used. Otherwise, JOBGEN will fail with RC=8 due to mismatching supplied and installed paths and you would have to rerun JOBGEN and enter the correct z/OS UNIX path in the panel. The following figure shows an example error that would occur when you provide an incorrect path:

   

   
7. Remove the asterisks and/or modify the provided model CALLLIBS data sets according to your shop standards:
   
   After you confirm your choice, JOBGEN starts generating installation jobs.
8. Wait for JOBGEN to complete the generation of the installation jobs, and monitor the return codes. A successful JOBGEN run returns RC = 0. If there are any mistakes in the setup process that JOBGEN can recognize, it will issue RC = 8 and errors will be printed in KCIJGLOG member. In this example, you can also see that the existing CSI was scanned for information:
   
9. Review the content in log member KCIJGLOG in the JOBGEN output library. It contains all the information about generated jobs and indicates the order in which they must be submitted. This member also contains a summary of the parameters that were provided in the JOBGEN panels, a list of the products selected and their FMIDs, as well as information about the data sets that will be created, DDDEFs, and so on. In this scenario, an existing SMP/E environment is being used to install additional products and qualifiers for existing SMP/E CSI, target, and distribution libraries were provided; therefore, jobs KCIJGSMA and KCIJGSMI were not created. Instead, KCIJGANL and KCIJGREA jobs were created to analyze the existing SMP/E environment for adequate space to install new products.
   
   
10. To install additional products into an existing SMP/E environment, submit the jobs in the order presented in KCIJGLOG. Every job contains a comprehensive comment section with the function of the job and additional notes. This section briefly describes all the jobs in the order that they should be submitted:
    1. KCIJGANL – This job analyzes the existing SMP/E environment (target and distribution libraries) and checks if there is enough space to install new products. If some data sets will have to be reallocated, the REALLOC member is created in the same JOBGEN PDS. When you submit this job, the JOBGEN PDS should not be in use (browsed); otherwise, it might hang in execution:
       
       When the job completes, it prints a detailed log that provides information about space requirements. If there are no data sets to reallocate, the REALLOC member will be empty and there is no need to submit next job, KCIJGREA.

       
    2. KCIJGREA – This job reallocates existing SMP/E data sets using the REALLOC control member created in the previous job, KCIJGANL. Submit this job only if there are data sets that need to be reallocated and the REALLOC member contains new space requirements:
       
       
    3. KCIJGALO – This job allocates the target and distribution libraries for the selected products that are missing and are required for the selected products. In this job you can also find the VOLUME setting that was provided in JOBGEN panels. If the data sets are SMS-managed, the VOLUME lines can be deleted from the JCL before submitting the job:
       
    4. KCIJGDDF – This job defines the SMP/E DDDEF zone entries for the newly allocated product data sets and the CALLLIBS libraries as well as for the TKANJAR path:
       
    5. KCIJGBDI – This job builds the directory structure for the selected products. Before submitting this job, you must ensure that the z/OS UNIX root directory that was provided in the JOBGEN USS Install Path panel already exists. In this example, this job was created because the SMP/E environment did not have it defined earlier. If such a path already exists and is defined to SMP/E, the KCIJGBDI job will not be created:
       
    6. KCIJGREC – This job is the RECEIVE job, which receives the components for the selected products. If any of the components that are shared by the products is already installed, it will be skipped from the job.
    7. KCIJGAPP – This job is the APPLY job, which applies the components for the selected products. If any of the components that are shared by the products is already applied, it will be excluded in the SMPCNTL statement.
    8. KCIJGACC – This job is the ACCEPT job, which accepts the components for the selected products. If any of the components that are shared by the products is already accepted, it will be excluded in the SMPCNTL statement.