Cloning an existing runtime environment

You can clone an existing PARMGEN runtime environment to create a new environment that runs on a different LPAR but uses the same values and has the same products configured. In this scenario, nothing changes, except LPAR-specific values.

Before you begin

This scenario uses the PARMGEN Workflow user interface to set up the work environment, customize profiles, and create and submit the jobs that create the runtime environment RTE). For instructions on launching the interface, see Accessing the Workflow menu.

About this task

In this scenario, you use the configuration values from one PARMGEN runtime environment to create another on a different LPAR. There are 8 main steps involved in the scenario:
  1. Set up the PARMGEN work environment for the new runtime environment.
  2. Clone customized WCONFIG library members from the model runtime environment to the WCONFIG library for the new runtime environment.
  3. Update the interim libraries and create the PARMGEN configuration profiles.
  4. Merge the configuration profile parameter values from the model runtime environment into the new one.
  5. Customize the configuration profiles for the new environment.
  6. Validate the profile parameter values.
  7. Create the runtime members and jobs.
  8. Submit the jobs to complete create the runtime environment.
If the LPAR on which the new runtime environment is being configured does not share DASD with the LPAR on which the runtime environment will run, the PARMGEN libraries must be copied to the target LPAR. (See PARMGEN transport scenarios for more information.) Where each of these steps is performed depends on the transport method being used to deploy the new environment.
Note: In this scenario, system variables are not enabled. If you intend to clone an environment which uses system variables, see Cloning an existing environment with system variables enabled.

Procedure

  1. Set up the PARMGEN work environment for the new RTE.
    1. On the PARAMETER GENERATOR (PARMGEN) WORKFLOW MENU (KCIPQPGA) panel, specify the parameters to identify the new RTE and press Enter.
      Note that if you did not invoke the R (RESET) option, the values for GBL_USER_JCL, RTE_PLIB_HILEV, and RTE_NAME are carried forward from the last environment you created. If the values for the GBL_USER_JCL library and the high-level qualifier for the work libraries are correct, change the RTE_NAME to the name you want to use for the new environment.
      GBL_USER_JCL
      Specify the dataset name of the PARMGEN global user JCL library for the new runtime environment. If the dataset does not exist, you are prompted to correct the name or allocate the data set.
      RTE_PLIB_HILEV
      Specify the non-VSAM high-level qualifier you want to use for the PARMGEN work libraries for the new runtime environment.
      RTE_NAME
      Unique name for the runtime environment you are configuring. The name you specify is appended to the RTE_PLIB_HILEV values to make each set of PARMGEN and runtime libraries unique.
      The PARAMETER GENERATOR (PARMGEN) WORKFLOW - PRIMARY OPTION MENU (KCIPQPGB) panel is displayed.
    2. Select option 1 from the menu.

      The Set up PARMGEN Work Environment for an RTE (1 of 1) (KCIPQPG1) is displayed.

      KCIPQPG1  SET UP/REFRESH PARMGEN WORK ENVIRONMENT FOR AN RTE (1 OF 3) --------
Command ===>                                                                  
                        Quick Configuration Mode                              
                                                                   More:     +
Specify the RTE model profile to use:                                         
 ==> ______________________________________________________                   
                                                                              
   - To create a new RTE based on a predefined IBM model, type a ? in         
     the field and press Enter, then select the appropriate template.         
   - To create a new RTE that is a clone of an existing PARMGEN RTE,          
     specify the WCONFIG profile library and RTE member name to clone;        
     for example:  (&hlq.&rte.WCONFIG(&clone_from))                           
   - To create a new RTE that is a clone of an ICAT-created RTE,              
     specify the ICAT RTE Batch member location and RTE member;               
     for example:  (&hlq.ICAT.INSTJOBS(SYSA))                                 
   - To create a new RTE from scratch, leave this field blank.                
   - To reconfigure or upgrade this existing PARMGEN RTE, specify its values; 
     for example:  (TDITNT.IDTST.SYSA.WCONFIG(SYSA))                           
                                                                              
Customize jobcard data:                                                       
 ==> //TDITNT  JOB (ACCT),'%SYSMEMBER% - NAME',CLASS=A,______________________
 ==> //  MSGCLASS=X,MSGLEVEL=(1,1),NOTIFY=&SYSUID.,REGION=0M__________________
 ==> //**  0 0  RTE_NAME=%RTE_NAME% SYSMEMBER=%SYSMEMBER%_____________________
 ==> //** \_~_/ SYSJOBNAME=%SYSJOBNAME% JOBPARM SYSAFF=%SYSNAME%______________

Specify the Install Job Generator (JOBGEN) output library if you want   
PARMGEN to reuse CALLLIBS parameters from the JOBGEN repository:        
 ==> ____________________________________________                       
     (Type ? for last referenced JOBGEN library discovered, if any.)
    3. Complete the fields as appropriate, then press Enter to continue.
      RTE model profile
      The information you provide in the RTE model profile field determines what jobs the configuration software will run after the work environment is set up. To create (clone) an RTE based on an already configured PARMGEN RTE, provide the WCONFIG profile library and member name for that RTE (for example: hilev.rte.WCONFIG(rte_name), where rte_name is the member you want to clone from).

      If a value is supplied, PARMGEN queries the member to determine what products or components are already configured within the RTE to tailor the configuration parameters set. If the specified data set or member does not exist, you are prompted to correct the name.

      Install Job Generator (JOBGEN) output library
      Specify the Install Job Generator (JOBGEN) output library if you want PARMGEN to reuse parameter values from the JOBGEN output library repository. These are values such as the jobcard, CALLLIBS override data, and other CSI values such as:

      If the specified dataset does not exist, you are prompted to correct the name.

      Note: For more information about the JOBGEN output library, refer to the Installation Job Generator Utility section in the product's Program Directory.
      Jobcard data
      If a customized job card is already available, it is retrieved from the ISPF user profile pool. If a job card is not available and if you did not specify a JOBGEN output library, the job card is harvested from the &gbl_target_hilev.TKANSAM SMP/E target library where the initial PARMGEN sample job card default is supplied. If you specified a JOBGEN output library, the job card information is harvested from there. You can modify the retrieved data as needed. The customized job card is saved in the ISPF user profile pool and persists across ISPF sessions.
       KCIPQPG1  SET UP/REFRESH PARMGEN WORK ENVIRONMENT FOR AN RTE (1 OF 3) ---------
Command ===>                                                                   
                        Quick Configuration Mode                               
                                                                   More:     + 
Specify the RTE model profile to use:                                                                                
 ==> &hlq.&rte.WCONFIG(&clone_from)________________________                    
                                                                               
   - To create an RTE from scratch, leave this field blank.           
   - To create an RTE based on a predefined IBM model, type a ? in    
     the field and press Enter, then select the appropriate template. 
   - To create an RTE that is a clone of an existing PARMGEN RTE,     
     specify the WCONFIG profile library and RTE member name to clone;
     for example:  (&hlq.&rte.WCONFIG(&clone_from))                   
   - To create an RTE that is a clone of an ICAT-created RTE,         
     specify the ICAT RTE Batch member location and RTE member;       
     for example:  (&hlq.ICAT.INSTJOBS(&rte_name))                                
   - To reconfigure or upgrade this existing PARMGEN RTE, specify its values;  
     for example:  (TDITN.IDTST.DEMO.WCONFIG(&rte_name))                       
                                                                               
Customize jobcard data:                                                        
 ==> //KCIJPPGN JOB (ACCT),'%SYSMEMBER% - NAME',CLASS=A,________________________ 
 ==> //  MSGCLASS=X,MSGLEVEL=(1,1),NOTIFY=&SYSUID.,REGION=0M__________________ 
 ==> //**  0 0  RTE_NAME=%RTE_NAME% SYSMEMBER=%SYSMEMBER%_____________________ 
 ==> //** \_~_/ SYSJOBNAME=%SYSJOBNAME% JOBPARM SYSAFF=%SYSNAME%______________ 
                                                                                
Specify the Install Job Generator (JOBGEN) output library if you want           
PARMGEN to reuse CALLLIBS parameters from the JOBGEN repository:                
  ==> ____________________________________________                              
      (Type ? for last referenced JOBGEN library discovered, if any.)
    4. Press Enter to proceed to the next panel.
      The Set Up PARMGEN Work Environment for an RTE (2 OF 3) panel (KCIP@PG2) is displayed.
      
 KCIP@PG2  SET UP/REFRESH PARMGEN WORK ENVIRONMENT FOR AN RTE (2 OF 3) ---------
Command ===>                                                                   
                        Quick Configuration Mode                               
GBL_USER_JCL:   TDITN.IDTST.PARMGEN.JCL                                       
RTE_PLIB_HILEV: TDITM.IDTST                                                   
RTE_NAME:       SYSA                                                         
                                                                               
Enter parameter values appropriate for your environment:                       
                                                       UNIT     / STORCLAS /   
                                                       VOLSER     MGMTCLAS     
GBL_TARGET_HILEV: IBM.TARGET.ITM63055________________  ________ / ________ /   
                  HLQ of SMP/E target (TK*) datasets   ______     ________     
                                                                               
GBL_SYSDA_UNIT:   SYSDA___                                                     
                  Work datasets UNIT name                                      
                                                                               
GBL_REGION:       0M______                                                     
                  JCL REGION (specify K/M suffix)                              

                                                                               
Note: Type BACK to go back one panel.  Type UTIL to access utility menu.
    5. Review the values for GBL_TARGET_HILEV and GBL_SYSDA_UNIT and correct them if necessary.

      These values for the parameters on this panel are read from the RTE you are cloning from. You might want, for example, the new RTE to point to a different set of target libraries which has newer versions of the products installed.

    6. Press Enter to proceed to the next panel.
      The third setup panel (KCIP@PG3) is displayed. Depending on your screen resolution, you may have to scroll down (PF8) to see all the parameters. (Note the More: + indicator.)
       KCIP@PG3 ---- SET UP PARMGEN WORK ENVIRONMENT FOR AN RTE (3 OF 3) -------------
 Command ===>                                                  Scroll ===> PAGE 
                                                                                
 Enter parameter values appropriate for the LPAR RTE=&rte_name.                 
 Press F1=Help for more information.                                            
                                                                    More:     + 
 RTE_DESCRIPTION:     &rte_name____________________________________          
 RTE_SMS_PDSE_FLAG:     N               (Y, N)  (Allocate Non-VSAM PDSE libs)   
 RTE_SMS_UNIT:          __________      (Non-VSAM disk UNIT type)               
 RTE_SMS_VOLUME:        __________      (Non-VSAM disk VOLSER)                  
 RTE_SMS_MGMTCLAS:      MCSTD_____      (Non-VSAM disk MGMTCLAS)                
 RTE_SMS_STORCLAS:      SCTSTEST__      (Non-VSAM disk STORCLAS)                
 RTE_SMS_VSAM_VOLUME:   MCSTD_____      (VSAM disk VOLSER)                      
 RTE_SMS_VSAM_MGMTCLAS: __________      (VSAM disk MGMTCLAS)                    
 RTE_SMS_VSAM_STORCLAS: SCTSTEST__      (VSAM disk STORCLAS)                    
                                                                                
 RTE_TYPE:              FULL____        (FULL, SHARING)                         
 RTE_HILEV:      TDITN.IDTST_______________                                     
                 (&hlq  portion of Non-VSAM RK* HLQ=&hlq.&rte_name)             
 RTE_VSAM_HILEV: TDITN.IDTST_______________                                     
                 (&hlq  portion of VSAM RK* HLQ=&hlq.&rte_name)                 
                                                                                
 If RTE_TYPE is SHARING:                                                        
   RTE_X_HILEV_SHARING: __________________________                              
                        (&hlq  portion of shared RTE's HLQ=&hlq.&rte_share)     
   RTE_SHARE: ______________________________ ("SMP" value or *&rte_share)       
              (*&rte_share  portion of shared RTE's HLQ=&hlq.&rte_share)        
   RTE_LOAD_SHARED_LIBS:        Y    (Y, N)  (Is RTE updater of RO shared libs) 
                                                                                
 If symbolics (system variables or user-defined variables) will be used:        
   RTE_SYSV_SYSVAR_FLAG:        N    (Y, N)  (System variable flag)             
                                                                                
 Security settings:                                                             
   RTE_SECURITY_USER_LOGON:   NONE______  (RACF, ACF2, TSS, NAM, None)          
   RTE_SECURITY_FOLD_PASSWORD_FLAG: Y     (Y, N)  (Fold password to upper case) 
   RTE_SECURITY_CLASS:        ________________________________________________  
   RTE_X_SECURITY_EXIT_LIB:   TSTEST.&userid.&clone_from.RKANSAMU_____________  
   GBL_DSN_ACF2_MACLIB:       ________________________________________________  
   GBL_DSN_ACF2_MACLIB1:      ________________________________________________  
                                                                                
 Local Tivoli Enterprise Monitoring Server (TEMS) settings in this LPAR RTE:    
   RTE_TEMS_CONFIGURED_FLAG:  Y           (Y, N)  (Configure TEMS in this RTE)  
   RTE_TEMS_NAME_NODEID: &clone_from:CMS ________________ (e.g.,CLONETST:cms)   
   KDS_TEMS_TYPE:             HUB___      (Hub, Remote)                         
   KDS_TEMS_HA_TYPE:          __          (HA=High Availability Hub TEMS type)  
                                                                                
 ITM components' communication-related and started tasks settings:              
   RTE_TCP_PORT_NUM:       1918__________________ (1-65535 port number)         
   RTE_VTAM_APPLID_PREFIX: TS1___________________ (1-4 char.VTAM APPLID prefix) 
   RTE_STC_PREFIX:         TSS1__________________ (1-4 char.started task prefix)
 Note: Type BACK to go back one panel.
      Any changes made on this panel are preserved when the existing RTE is cloned, but not all changes are inherited by the corresponding component and product-specific parameters in the RTE profile of the new RTE. If you change any of the following parameters, you must edit the corresponding product and component parameters in the RTE profile to the same values as you specify here.
      • Started task prefix
      • VTAM applid prefix
      • Port number
      • RTE high-level qualifier
      • VSAM high-level qualifier
      At a minimum, make the following changes to convert the new RTE to a sharing RTE with a remote monitoring server that connects to the hub in the cloned-from RTE:
      1. Change the type of runtime environment to Sharing-with-SMPE by setting RTE_TYPE to SHARING and RTE_SHARE to SMP.
      2. Change RTE_TEMS_NAME_NODEID to &rte_name:CMS.
      3. (Optionally) Change RTE_X_SECURITY_EXIT_LIB to TSTEST.userid.&rte_name.RKANSAMU. If you are sharing the same security settings and permission as the model runtime environment, you can use the same library.
      4. Convert the hub to a remote by setting KDS_TEMS_TYPE to REMOTE.
    7. Press Enter to proceed to the next panel.

      The Include Products in this PARMGEN RTE panel (KCIP@PGI) is displayed. 

      KCIP@PGI - INCLUDE (CONFIGURE) INSTALLED PRODUCT(S) IN THIS LPAR R Row 1 of 26 
Command ===>                                                  Scroll ===> PAGE 
                                                                               
Select ("S" or "/") products to CONFIGURE those product(s) in DEMO RTE.      
Select or deselect products to include or exclude from configuration.          
Products configured in the model or current RTE (reconfiguring) are preselected
                                                                               
When finished, change N to Y to confirm selections.  Confirm ==> N  (Y, N)     
                                                                               
  Kpp  Component or Product Name and Version                                   
  ---- ----------------------------------------------------------------------  
/ KAH  System Automation Monitoring Agent V350                 
/ KC5  OMEGAMON for CICS V550                                  
/ KDO  Tivoli Decision Support for z/OS Agent V181             
/ KDS  Tivoli Enterprise Monitoring Server V630                
/ KD4  ITCAM for SOA Agent V711                                
/ KD5  OMEGAMON for DB2 PE/PM V540                             
/ KGW  OMEGAMON for CICS TG V550                               
/ KI5  OMEGAMON for IMS V550                                   
/ KJJ  OMEGAMON for JVM V540                                   
/ KMQ  OMEGAMON for Messaging - MQ V750                         
/ KM5  OMEGAMON for z/OS V550                                           
/ KNA  NetView for z/OS Agent V621                                      
/ KN3  OMEGAMON for Networks V550                                       
/ KOB  OMEGAMON Enhanced 3270 User Interface V750                       
/ KQI  OMEGAMON for Messaging - Integration Bus V750                    
/ KRG  Advanced Audit for DFSMShsm Agent V260                           
/ KRH  Advanced Reporting and Management for DFSMShsm Agent V260        
/ KRJ  Advanced Allocation Management Agent V330                        
/ KRK  Automated Tape Allocation Manager for z/OS Agent V330            
/ KRN  Advanced Catalog Management Agent V260                           
/ KRV  Advanced Backup and Recovery for z/OS Agent V240                 
/ KRW  Tape Optimizer for z/OS Agent V220              
/ KS3  OMEGAMON for Storage V540                       
/ KYN  ITCAM for Application Diagnostics, TEMA V710.03              
End of data

      This panel lists the products installed in the runtime environment and therefore available for configuration.

      This panel lists all the installed products that are available for configuration by product code (Kpp) and product name and version. The products marked with a slash (/) are the ones already configured in the RTE being cloned, but the version represents the latest version available. If you include these products, they will be upgraded to the version in the target libraries. In this example, a monitoring server, OMEGAMON for z/OS, OMEGAMON for CICS, and the OMEGAMON enhanced 3270 user interface are already configured.

    8. If you want to install additional products, select them by typing a slash next to the product code. Deselect any products you do not want to include in the new RTE. Then, change Confirm ==> N to Confirm ==> Y and press Enter.

      The KCIJPCFG job is displayed, tailored with the values you have configured.

    9. Review the notes and values and submit the job, then return to the Workflow main panel.
  2. (Optional) Clone customized members from the model runtime environment (&clone_from).
    1. Type U or UTIL from the Workflow main menu.
      The UTILITIES (KCIPQPGU) panel is displayed.
    2. Type the option number for the KCIJPCCF job that clones customized members (Kpp$C*, Kpp$P*/Kpp@P*, Kpp$S*), $JOBCARD, and the $GBL$USR global profile) from an existing WCONFIG library to a new one.
    3. Review the job to determine if you need to modify the library concatenated in the OLDWCNFG DDNAME.

      By default, this DDNAME already points to the WCONFIG library that you specified in the RTE profile library field of the first work environment setup panel. If necessary, modify the job to point to an existing WCONFIG library that contains the customized members you want cloned over to the WCONFIG library for the new runtime environment.

    4. Submit the job and return to the main Workflow panel.
    The specified members are copied to the WCONFIG library for the new runtime environment.
  3. Merge the configuration profile parameter values from the model runtime environment into the new one.
    1. Type U or UTIL from the Workflow main menu.
      The UTILITIES (KCIPQPGU) panel is displayed.
    2. Type the option number for the KCIJPMCF job.
    3. Review the job and make any required changes.

      By default, the OLDMEM(&value) parameter is already set to the runtime environment you specified in the first setup panel (in this example, TSTEST.&userid.&clone_from.WCONFIG(&clone_from).

      ===============================================================================
EDIT TSTEST.&userid.&rte_name.WCONFIG(KCIJPMCF) 
Command ===>                                                  Scroll ===> CSR  
000068 //* MERGECHG Step:                                                      
000069 //* Merge the changes in %OLDMEM% into %NEWMEM% member.                 
000070 //* ******************************************************************* 
000071 //MERGECHG  EXEC  PGM=IKJEFT01,DYNAMNBR=99,REGION=4M                    
000072 //SYSEXEC   DD DISP=SHR,                                                
000073 //          DSN=TSTEST.ITM62351.TKANCUS                                 
000074 //SYSTSPRT  DD SYSOUT=*                                                 
000075 //SYSPRINT  DD SYSOUT=*                                                 
000076 //SYSTSIN   DD *                                                        
000077   KCIRPLBX +                                                            
000078   BATCH +                                                               
000079   SKIPVAR(TSTEST.ITM62351.TKANCUS(KCIDPGNX)) +                          
000080   OLDMEM(TSTEST.&userid.&clone_from.WCONFIG(&clone_from)) +                     
000081   NEWMEM(TSTEST.&userid.&rte_name.WCONFIG(&rte_name))                       
000082 /*                                                                      
===============================================================================
    4. Review and submit the job and return to the Workflow main menu.
  4. Customize the configuration profiles for the new environment.
    1. From the Workflow menu, select option 2.

      The Customize PARMGEN Configuration Profile Members panel is displayed.

       KCIP@PG6 ------ CUSTOMIZE PARMGEN CONFIGURATION PROFILE MEMBERS ---------------
 Option ===>                                                                    
                         Quick Configuration Mode                               
  (Required) Customize the RTE profile and the $GBL$USR user profiles:       
  (Tip) Review KCIJPDLA autodiscovery job in Utility menu or type DLAJOB cmd.               
    *1. SYSA  RTE LPAR-specific CONFIG profile in WCONFIG (User copy)        
    *2. $GBL$USR Global parameters CONFIG profile in WCONFIG (User copy)        
                                                                                
  (Required)     Customize the Variables profile if RTE_SYSV_SYSVAR_FLAG=Y:     
    *3. SYSA  Variables (system, user) CONFIG profile in GBL_USER_JCL PARMGEN
                 global library (TDITN.IDTST.PARMGEN.JCL).                      
                 Add/Modify system/user-defined symbols and their               
                 resolution values, for override variables used as parameter    
                 values in the $DOCRTE RTE and $GBL$USR global profiles.        
                                                                                
  (Tip) Review/Customize WCONFIG Kpp$C*/Kpp$P*/Kpp$S* user imbeds:         
  (Cloning Tip) Review KCIJPCCF job in Utility menu prior to customization.          
     4. WCONFIG  TDITN.IDTST.$DOCRTE.WCONFIG                                    
                                                                                
  (Tip) Review if you want to compare with IBM-supplied default profile values:        
     5. $CFG$IBM RTE LPAR-specific CONFIG profile in WCONFIG (IBM copy)         
     6. $GBL$IBM Global parameters CONFIG profile in WCONFIG (IBM copy) 

  (Optional) Override SYSIN member to supply additional (User) profiles:        
     7. $SYSIN   $PARSE/$PARSESV SYSIN controls (CONFIG/SELECT MEMBER)    
                
 Press F1=Help for more information.  Type UTIL to access utility menu.
    2. Select option 1 to customize the LPAR configuration for the new runtime environment.
      Change any instances of &clone_from inherited from the model environment to &rte_name, and change any LPAR-specific values, such as host name.
    3. After you complete any necessary changes, press F3 to return to the Customize PARMGEN Configuration Profile Members panel.
    4. If necessary, edit the $GBL$USR and &rte_name system variables configuration files, then return to the Customize PARMGEN Configuration Profile Members panel.
    5. Run the DLAJOB to auto-discover other RTE-specific parameters by typing DLAJOB in the command line and pressing Enter.
    6. Submit the DLAJOB and return to the main Workflow panel.
  5. Validate the configuration profile values that you supplied:
    1. Type U or UTIL from the Workflow main menu.
      The UTILITIES (KCIPQPGU) panel is displayed.
    2. Type the option number for the KCIJPVAL job.
    3. Review the notes and submit the job.
      The parameter validation report is written to &hilev.&rte.WCONFIG($VALRPT). Enter option number + s, for example 23s, in the UTILITIES menu to view the report.
    4. If the job gets a condition code greater than 4 (COND CODE 0004), review the $VALRPT. Return to the previous step and correct the parameter values, then resubmit the validation job.
  6. Create the WK* runtime members and the WKANSAMU jobs:
    1. Select option 3.

      The CREATE THE RTE MEMBERS AND JOBS (KCIP@PR1) panel is displayed.

    2. Select option 1 to submit the generated $PARSE composite job.
    3. Review the job, then submit the job.
      Return to the main Workflow panel.
  7. Submit the batch jobs to complete the setup of the runtime environment:
    1. Select option 4 from the Workflow main menu.
      The Submit Batch Jobs to Complete PARMGEN Setup (KCIP@SUB) panel is displayed.
    2. Select option 1 if you want to submit the KCIJPSUB composite SUBMIT job, or select the other options to submit each job individually. If you select option 1, review the KCIJPSUB job first, and edit the job according to which of the conditional jobs need be submitted automatically and which need to be submitted manually (for example, for reasons of authorization). 
      KCIP@SUB -------- SUBMIT BATCH JOBS TO COMPLETE PARMGEN SETUP -----------------
Option ===>                                                                    
                                                                               
Select option 1 to SUBMIT the composite jobs in WKANSAMU for SYSA RTE.       
Tip: Review the SUBMIT commands in the KCIJPSUB composite job.                 
                                                                               
Alternatively, select other options (2-12) to submit each job individually.    
Enter ns (1s-12s) for detailed job/task status.                                
                                                                               
                   Description               REQ  Job Name   Status     Date   
    --------------------------------------- ----- -------- --------- ----------
                                                                   More:     + 
1.  Composite SUBMIT job (See JCL comments)       KCIJPSUB 
    ** or **                                                                   
2.  Allocate runtime RO and RW datasets     (Yes) KCIJPALO 
3.  Copy SMP/E mbrs from TK*->RK* RO libs   (Yes) KCIJPLOD 
4.  Run product security steps              (Yes) KCIJPSEC 
5.  Update variable-named runtime mbrs      (No ) KCIJPUPV                     
6.  (Re)Create USS runtime mbrs in RKANDATV (Yes) KCIJPUSP 
7.  Create USS dirs./ (Re)Copy USS files    (Yes) KCIJPUSS 
8.  Copy runtime mbrs to SYS1-type libs (Caution) KCIJPSYS                     
9.  Run post-SMP/E RKANMODU ASM/LINK steps  (Yes) KCIJPLNK 
10. Verify the configuration jobs           (Tip) KCIJPIVP                     
11. Back-up RK* product execution user libs (Tip) KCIJPCPR 
12. Copy runtime mbrs from WK*->RK* RW libs (Yes) Enter 12 for details. 
                                                                                
Press F1=Help for more information.  Type UTIL to access utility menu.
    3. Submit the job.

Results

You have created a customized copy of an existing runtme environment.

What to do next

If necessary, copy the PARMGEN libraries to the target LPAR. Complete any of the configuration required outside of the configuration software and start the products.