Scenario PGN04: Cloning an existing environment and converting its hub monitoring server to a remote server

In this scenario, you clone an existing runtime environment to create a new environment that has the same parameter values and product set. The new runtime environment inherits the parameter values and product set of the model runtime environment, but you convert the new environment from a full to a sharing-with-SMP/E type and convert the static hub monitoring server inherited from the model environment into a remote server.

Before you begin

Launch the PARMGEN Workflow interface as described in Starting the Workflow user interface.

About this task

In this scenario, you clone the sample PLB1SP22 runtime environment created in scenario PGN01 to create a runtime environment named PLB2SP23, which runs on a different LPAR. This scenario assumes that both environments share DASD, so no jobs or members have to be copied (transported) to the new LPAR.

The PLB1SP22 runtime environment is a full runtime environment that comprises a hub monitoring server and several monitoring agents. As you configure this environment, you convert the environment from a full environment to a sharing-with-SMPE environment. You also convert the hub monitoring server to a remote server and configure the server to connect to the high-availability hub Tivoli Enterprise Monitoring Server set up for the PLBHAHUB runtime environment (see the PGN03 scenario). The agents in the new environment automatically point to the local remote monitoring server.

This task involves eight steps:

  1. Setting up the PARMGEN work environment
  2. Cloning the WCONFIG members from the model runtime environment
  3. Updating the interim libraries and create the configuration profiles for the new environment
  4. Merging the values from the model LPAR configuration profile
  5. Customizing the profile parameter values
  6. Validating the configuration parameters
  7. Creating the runtime members and jobs
  8. Submitting the jobs to create the runtime environment

Procedure

  1. Set up the PARMGEN work environment as follows:
    1. On the PARMGEN Workflow main panel, specify the GBL_USER_JCL, RTE_PLIB_HILEV, and RTE_NAME values for the new runtime environment.

      If you do not use the reset command, the values for GBL_USER_JCL, RTE_PLIB_HILEV, and RTE_NAME are carried forward from any previous session. In this case, change the RTE_NAME to PLB2SP23.

      Note: Due to frequent product updates, the example below may not accurately reflect the options or fields you see on the screen. It is provided as a sample only.
      KCIP@PG2  SET UP/REFRESH PARMGEN WORK ENVIRONMENT FOR AN RTE (2 OF 3) -------
 Command ===>                                                                 
                         Quick Configuration Mode                             
 GBL_USER_JCL:     TSTEST.IDTST.PARMGEN.JCL                                     
 RTE_PLIB_HILEV:   TSTEST.userid         
 RTE_NAME:         PLB2SP23                                                        
                                                                              
 Enter parameter values appropriate for your environment:                     
                                                        UNIT     / STORCLAS / 
                                                        VOLSER     MGMTCLAS   
 GBL_TARGET_HILEV: TDCI.ZSMSDB2.SMPE__________________  ________ / ________ / 
                   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 U or UTIL to access utility menu.
    2. Select option 1.

      Because the runtime environment you specified is a new one, you are asked if you want to reset the definition and status values before you proceed:

      KCIP@MSG ---------------- PARMGEN MESSAGES --------------------------
COMMAND ===>                                                         
                                                                     
You have asked to configure a new RTE profile.                       
This action is recommended to be preceeded by selecting              
Option "R" to reset RTE, status and date fields                      
for a new RTE.                                                       
                                                                     
Press ENTER to perform the reset for a new RTE.                      
Press F3 to abort.
    3. Press Enter.
      A verification screen is displayed:
      KCIP@PGP ---------------- PARMGEN MESSAGES --------------------------
COMMAND ===>                                                         
                                                                     
This will clear the GBL_USER_JCL, RTE_PLIB_HILEV and                 
RTE_NAME fields and all Status and Date fields.                      
                                                                     
Press ENTER to proceed. Press F3 to abort.
    4. Press Enter to perform the reset.
      You are returned to the main Workflow panel.
    5. Select 1 again to begin setting up the work environment.
      The first Set up PARMGEN work environment for an RTE panel (KCIP@PG1) is displayed.
    6. In the first field, specify the data set and member name of the LPAR configuration profile whose values and product set you want to clone. In this example, you are cloning the PLB1SP22 profile. If appropriate, specify the Install Job Generator output library. 
       KCIP@PG1 ---- SET UP PARMGEN WORK ENVIRONMENT FOR AN RTE (1 OF 3) -------------
 Command ===>                                                                   
                                                                                
 Specify the RTE profile library and member name that fits your scenario:       
  ==> TSTEST.&userid.PLB1SP22.WCONFIG(PLB1SP22)__________ (ex:&dset(&rte))      
  - If creating a brand new RTE, leave this field blank.                **or**    
  - If creating another new RTE and you want to clone a PARMGEN-created           
    RTE's configured product set, specify the WCONFIG profile library and         
    RTE member name to clone (ex.: &hlq.&rte.WCONFIG(&clone_from)).     **or**    
  - If reconfiguring or upgrading this existing PLB2SP23 RTE, specify its         
    values (TSTEST.&userid.PLB2SP23.WCONFIG(PLB2SP23))                    **or**  
  - If converting an ICAT-created RTE to PARMGEN mode, specify the ICAT           
    RTE Batch member location and RTE member (ex.: &hlq.INSTJOBS(PLB2SP23))       
                                                      
 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.)           
 Enter Jobcard data: 
  ==> //&userid.J JOB (ACCT),’%SYSMEMBER% ,,&username’,CLASS=A,____________________ 
  ==> // MSGCLASS=X,MSGLEVEL=(1,1),NOTIFY=&SYSUID.,REGION=0M_________________ 
  ==> //** RTE_NAME=%RTE_NAME%________________________________________________ 
  ==> //** SYSJOBNAME=%SYSJOBNAME% SYSMEMBER=%SYSMEMBER%______________________
    7. Press Enter to proceed to the next panel.
      If the GBL_USER_JCL data set does not exist, the following verification screen is displayed:
      KCIPPLBP ------------ USER JCL LIB PROCESSING ----------------------
COMMAND ===>                                                        
                                                                    
The specified User JCL library does not exist.                      
- Press ENTER to ALLOCATE NEW like TKANCUS.                         
- Correct dsname and press ENTER to use an existing dataset.        
- Press F3 to abort processing.                                     
  GBL_USER_JCL:                                                     
  TSTEST.SYSPLEX.PARMGEN.JCL____________________________            
                                                                    
Enter=Next  F3=End/Cancel
    8. Perform one of the following steps:
      • Press Enter to allocate a new data set.
      • Specify the correct data set name, then press Enter.
      The Set Up PARMGEN Work Environment for an RTE (2 OF 3) panel (KCIP@PG2) is displayed.
    9. Review the values on the example KCIP@PG2 panel and change them as necessary.
      These values are read from the LPAR profile that you specified on the first panel.
      KCIP@PG2  SET UP/REFRESH PARMGEN WORK ENVIRONMENT FOR AN RTE (2 OF 3) -------
 Command ===>                                                                 
                         Quick Configuration Mode                             
 GBL_USER_JCL:     TSTEST.SYSPLEX.PLEX.JCL                                     
 RTE_PLIB_HILEV:   TSTEST.userid .DB2                                                  
 RTE_NAME:         DB2                                                        
                                                                              
 Enter parameter values appropriate for your environment:                     
                                                        UNIT     / STORCLAS / 
                                                        VOLSER     MGMTCLAS   
 GBL_TARGET_HILEV: TDCI.ZSMSDB2.SMPE__________________  ________ / ________ / 
                   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 U or UTIL to access utility menu.
    10. Press Enter to proceed to the next panel.

      The third setup panel is displayed. Depending on your screen resolution, you might have to scroll down (PF8) to see all the parameters. (The More: + indicates that there are more parameters to be displayed.)

       KCIP@PG3 ---- SET UP PARMGEN WORK ENVIRONMENT FOR AN RTE (3 OF 3) -------------
 Command ===>                                                  Scroll ===> PAGE 
                                                                                
 Enter parameter values appropriate for the LPAR RTE=PLBHAHUB.                    
 Press F1=Help for more information.                                            
                                                                    More:     - 
 RTE_DESCRIPTION:       _____________________________                           
 RTE_SMS_PDSE_FLAG:     Y               (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:   __________      (VSAM disk VOLSER)                      
 RTE_SMS_VSAM_MGMTCLAS: MCSTD_____      (VSAM disk MGMTCLAS)                    
 RTE_SMS_VSAM_STORCLAS: SCTSTEST__      (VSAM disk STORCLAS)                    
                                                                                
 RTE_TYPE:              FULL____        (FULL, SHARING)                         
 RTE_HILEV:      TSTEST.&userid_______________                                   
                 (&hlq  portion of Non-VSAM RK* HLQ=&hlq.&rte_name)             
 RTE_VSAM_HILEV: TSTEST.&userid_______________                                   
                 (&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)             
   RTE_X_SYSV_OVERRIDE_SYMBOLS: N    (Y, N)  (Override local system symbols)    

 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.PLB1SP22.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:      PLBH1SP22:CMS ___________________ (e.g.,IDTEST: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)
      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
    11. Press Enter to proceed to the next panel.

      The Display PARMGEN Environment Analysis panel is displayed:

       KCIP@PG4 ------------ DISPLAY PARMGEN ENVIRONMENT ANALYSIS - Row 1 to 15 of 15 
 Command ===>                                                  Scroll ===> PAGE 
                                                                                
 Review message traffic before proceeding.  These Kpp components are installed  
 into the TSTEST.ITM62351.TKANCUS SMP/E target library and                      
 are available for (re)configuration and/or upgrade into the RTE=PLB2SP23.      
 Refer to the next panel ("EXCLUDE PRODUCTS FROM PARMGEN CUSTOMIZATION")        
 for a legend of the Kpp components' product names.                             

 34 Components installed in TSTEST.ITM62351.TKANCUS:                            
 KAH KC2 KC5 KDF KDO KDS KD2 KD4 KD5 KGW                                        
 KHL KI2 KI5 KMC KMQ KMV KM2 KM5 KNA KN3                                        
 KOB KON KQI KRG KRH KRJ KRK KRN KRV KRW                                        
 KS3 KT1 KWO KYN                                                                
                                                                                
 34 Components installed and configured in RTE profile PLB2SP23:                
 KAH KC2 KC5 KDF KDO KDS KD2 KD4 KD5 KGW                                        
 KHL KI2 KI5 KMC KMQ KMV KM2 KM5 KNA KN3                                        
 KOB KON KQI KRG KRH KRJ KRK KRN KRV KRW                                        
 KS3 KT1 KWO KYN                                                                
                                                                                
 1 Components installed but not configured in RTE profile PLB2SP23:            
 KT1                                                                        
 End of data
      This panel displays the list of products installed and available for configuration. The Components installed and configured in the RTE profile PLB2SP23 field lists products that will be configured.
    12. Press Enter to display the Include Products in this PARMGEN RTE panel (KCIP@PG5). 
       KCIP@PGI ------------ INCLUDE PRODUCTS IN THIS PARMGEN RTE - Row 1 to 19 of 26 
 Command ===>                                                  Scroll ===> PAGE 
                                                                                
 Select (/) product(s) to CONFIGURE those product(s) in RTE=PLB1SP23            
 All installed products have been preselected (/).                              
 Select or deselect products to include or exclude from configuration.          
                                                                                
 When finished, change "N" to "Y" to confirm selections.  Confirm ==> N (Y, N)  
                                                                                
   Kpp  Product Name/Version                                                    
   ---- ----------------------------------------------------------------------  
 _ KAH  System Automation Monitoring Agent V350                    
 / KC5  OMEGAMON for CICS on z/OS V530                              
 _ 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 on z/OS V530                         
 / KI5  OMEGAMON for IMS on z/OS V530                           
 / KJJ  OMEGAMON for JVM V540                                      
 / KMC  OMEGAMON for Messaging - WebSphere MQ Configuration V730
 / KMQ  OMEGAMON for Messaging - MQ V730   
 / KM5  OMEGAMON for z/OS V530                                  
 / KNA  NetView for z/OS Agent V621                                
 / KN3  OMEGAMON for Networks V530                  
 / KOB  OMEGAMON Enhanced 3270 User Interface V730               
 / KQI  OMEGAMON for Messaging - Integration Bus V730
 _ 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 on z/OS V540                        
 / KWO  OMEGAMON Dashboard Edition on z/OS - OMEGAVIEW V530      
 _ KYN  ITCAM for Application Diagnostics, TEMA V710.03            
 End of data

      The panel lists all the products installed in the target libraries. The products configured in the RTE being cloned are selected with a slash (/).

    13. Type a slash next to the product code for any additional products you want to configure in the new RTE. Then, change Confirm ==> N to Confirm==>Y and press Enter.
      If the versions of the selected products in the target libraries are newer than the products in the RTE being cloned, those products are upgrade.

      The GBL_USER_JCL(KCIJPCFG) file-tailored job is presented.

    14. Review the notes and values in the job to make sure that they are correct and submit the job.
      Return to the main Workflow panel.
  2. Clone the WCONFIG members for the new runtime environment from the model runtime environment's WCONFIG library:

    This step allows you to reuse any customizations to an existing PARMGEN environment for the new environment. The WCONFIG(KCIJPCCF) job clones user-customized members (such as Kpp$C*, Kpp$P*/Kpp@P*, Kpp$S*, KCI$X*, $JOBCARD, and $GBL$USR) from an existing WCONFIG library to a new one.

    1. From the Workflow main menu, select option 3, KCIJPCCF Clone customized WCONFIG members.

      The KCIJPCCF job is displayed.

    2. Review the job to determine if you need to further modify the library that is concatenated in the OLDWCNFG DDNAME. 
       000082 //* ******************************************************************* 
 000083 //CLONWCFG EXEC PGM=KCIPARSE,                                           
 000084 //         PARM='MV=32000,MAXL=32000,MI=255,LIST=YES'                   
 000085 //STEPLIB  DD DISP=SHR,                                                 
 000086 //         DSN=TDITNT.DEV.ITM62351.TKANMOD                              
 000087 //OLDWCNFG DD DISP=OLD,                                                 
 000088 //         DSN=TSTEST.&userid.PLB1SP22.WCONFIG                              
 000089 //NEWWCNFG DD DISP=SHR,                                                 
 000090 //         DSN=TSTEST.&userid.PLB2SP23.WCONFIG                              
 000091 //SYSPRINT DD SYSOUT=*                                                  
 000092 //SYSVROUT DD SYSOUT=*                                                  
 000093 //SYSINLST DD SYSOUT=*                                                  
 000094 //SYSIN    DD *

      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 that you want cloned over to the WCONFIG library for the new runtime environment.

    3. Submit the job and return to the main Workflow panel.
      Notice the jobstep indicator (>) on step 3 to denote that this is the last step you performed. Also notice the updated Status and Date on the KCIJPCCF job (option 1).
  3. Update the interim libraries and create profiles:
    1. Select option 4, KCIJPUP1 Update interim libraries and create profiles.
      The WCONFIG(KCIJPUP1) job is displayed.
    2. Review the job, then submit it.
    The work libraries are updated with the configuration values that you specified and the configuration profiles for the PLB2SP23 runtime environment are created.
  4. Merge the values from the LPAR configuration profile of the model runtime environment into the profile for the new runtime environment.
    1. From the Workflow main menu, select option 6, KCIJPMC2 Merge profile from model RTE.
      The TSTEST.&userid.PLB2SP23.WCONFIG(KCIJPMC2) member is displayed.
    2. Review the job and make any required changes. By default, the OLDMEM(&value) parameter is already set to the runtime environment that you specified in the first setup panel (in this example, TSTEST.&userid.PLB1SP22.WCONFIG(PLB1SP22). 
      ===============================================================================
EDIT TSTEST.&userid.PLB2SP23.WCONFIG(KCIJPMC2) 
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.PLB1SP22.WCONFIG(PLB1SP22)) +                     
000081   NEWMEM(TSTEST.&userid.PLB2SP23.WCONFIG(PLB2SP23))                       
000082 /*                                                                      
===============================================================================
    3. Submit the job to merge the profile values.
  5. Customize the PARMGEN configuration profiles.
    1. From the Workflow main menu, select option 8, PLB2SP23 Customize PARMGEN configuration profiles.
      The Customize PARMGEN Configuration Profile Members panel is displayed.
       KCIP@PG6 ------ CUSTOMIZE PARMGEN CONFIGURATION PROFILE MEMBERS ---------------
 Option ===>                                                                    
  Review/Customize the LPAR-specific and global configuration values:           
    *1. PLB1SP23 RTE LPAR-specific CONFIG profile in WCONFIG (User copy)        
                                                                                
    *2. $GBL$USR Global parameters CONFIG profile in WCONFIG (User copy)        
                                                                                
  Review/Customize symbolic resolution values in option (3) for applicable      
  system or user-defined variables used in option (1) PLB1SP23 LPAR-specific    
  and option (2) $GBL$USR global user profiles above:                           
    *3. PLB1SP23 System Variables CONFIG profile in GBL_USER_JCL                
                 (TDITN.IDTST.PARMGEN.JCL)                                      
                                                                                
    *Note: The PARMGEN configuration profiles above are preserved.              
                                                                                
  (Reference) IBM-supplied default profiles (refreshed by KCIJPUP1 job):        
     4. $CFG$IBM RTE LPAR-specific CONFIG profile in WCONFIG (IBM copy)         
     5. $GBL$IBM Global parameters CONFIG profile in WCONFIG (IBM copy)         
     6. $SYSIN   $PARSE/$PARSESV SYSIN controls (CONFIG/SELECT MEMBER)
      Customization of the WCONFIG(PLB2SP23) RTE profile is required. Customization of the (WCONFIG($GBL$USR) global profile is optional, but you might want to review the profile to determine if there are changes that you want to make.
    2. Select option 1 and customize the PLB2SP23 LPAR profile as follows:
      1. Change the type of runtime environment to Sharing-with-SMP/E by setting RTE_TYPE to SHARING and RTE_SHARE to SMP.
      2. Convert the hub server to a remote by setting the KDS_TEMS_TYPE parameter to REMOTE.
      3. Change all references to the RTE name PLB1SP22 (inherited from the model profile) to PLB2SP23 (the name of the new RTE).
        ISREDDE2 TSTEST.&userid.PLB2SP23.WCONFIG(PLB2SP23) 
Command ===> C PLB1SP22 PLB2SP23 ALL                          Scroll ===> CSR  
****** ***************************** Top of Data ******************************
- - -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -   354 Line(s) not Displayed 
==CHG> RTE_NAMESV                        PLB2SP23                        
- - -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  6 Line(s) not Displayed 
==CHG> RTE_NAME                          PLB2SP23                        
- - -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  1 Line(s) not Displayed 
==CHG> RTE_DESCRIPTION                   "PLB2SP23 LPAR"                 
- - -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -   110 Line(s) not Displayed 
==CHG> RTE_TEMS_NAME_NODEID              "PLB2SP23:CMS"                  
- - -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  - 20 Line(s) not Displayed 
==CHG> RTE_X_SECURITY_EXIT_LIB TSTEST.&userid.PLB2SP23.RKANSAM           
- - -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -   296 Line(s) not Displayed 
==CHG> KDS_PH01_TEMS_NAME_NODEID         "PLB2SP23:CMS"                     
==CHG> KDS_PH01_TEMS_RTE                 PLB2SP23                           
- - -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  6 Line(s) not Displayed 
==CHG> KDS_PH01_TEMS_ALIAS_NAME          "PLB2SP23:CMS"                  
- - -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  - 12 Line(s) not Displayed 
==CHG> **KDS_PU01_TEMS_NAME_NODEID       "PLB2SP23:CMS"                  
- - -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -   332 Line(s) not Displayed 
==CHG> KC5_TEMS_NAME_NODEID              "PLB2SP23:CMS"                  
- - -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -   190 Line(s) not Displayed 
==CHG> KGW_TEMS_NAME_NODEID              "PLB2SP23:CMS"                  
- - -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -   198 Line(s) not Displayed 
==CHG> KM2_HIST_DSTOR_RKM2EDS_DSN1 TSTEST.&userid.PLB2SP23.RKM2EDS1      
- - -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  3 Line(s) not Displayed 
==CHG> KM2_HIST_DSTOR_RKM2EDS_DSN2 TSTEST.&userid.PLB2SP23.RKM2EDS2      
- - -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  3 Line(s) not Displayed 
==CHG> KM2_HIST_DSTOR_RKM2EDS_DSN3 TSTEST.&userid.PLB2SP23.RKM2EDS3      
- - -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  - 24 Line(s) not Displayed 
==CHG> **KM2_HIST_WORKLOAD_PROFILE_DSN TSTEST.&userid.PLB2SP23.RKM2PROF  
- - -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  - 45 Line(s) not Displayed 
==CHG> KM5_AGT_TEMS_NAME_NODEID          "PLB2SP23:CMS"                  
- - -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  - 74 Line(s) not Displayed 
****** **************************** Bottom of Data ****************************
      4. To reconfigure the agents to point to the local remote monitoring server, perform an EXCLUDE FIND on TCP_HOST and change the parameters to SP23 (the IP host name).
      5. Change the started task name for the monitoring server (KDS_TEMS_STC).
      6. (Optional) Change all references of TS1 according to your site VTAM® naming convention for VTAM prefixes.

        This change is usually not required if the new runtime environment is a complete clone of the previous environment, differing only in the library names. For this scenario, the PLB2SP23 runtime environment is being set up for a conversion to a remote monitoring server, so the current PLB1SP22 configuration is being preserved for the PGN01 scenario.

      7. To configure the monitoring server to connect to the high-availability hub (created in the PGN03 scenario), perform an EXCLUDE FIND on all reference to KDS_HUB. Then, specify the high-availability hub monitoring server values that this remote monitoring server will connect to. In this example, these values represent the high-availability hub configured for the PLBHAHUB runtime environment.
        SP22       TSTEST.&userid.PLB2SP23.WCONFIG(PLB2SP23) 
Command ===> XF KDS_HUB                                       Scroll ===> CSR  
000829
000830 ** Note: The KDS_HUB_* values populate the xKANPARU(KDCSSITE) member    
000831 **       that Remote TEMS reads to know how to connect to its Hub.      
000832 KDS_HUB_TEMS_NAME_NODEID        "PLBHAHUB"                              
000833                                                                         
000834 ** If the TEMS is a Remote and requires VTAM SNA support:               
000835 KDS_HUB_VTAM_APPL_GLB_BROKER    ""   * Hub KDS_TEMS_VTAM_APPL_GLB_BROKER
000836 KDS_HUB_VTAM_NETID              ""   * Hub KDS_TEMS_VTAM_NETID          
000837                                                                         
000838 ** If the TEMS is a Remote and requires TCP/IP support:                 
000839 KDS_HUB_TCP_HOST                "OMEGHAHUB"                            
000840                                                                         
000841 ** If the TEMS is a Remote, specify port numbers of its Hub:            
000842 KDS_HUB_TCP_PIPE_PORT_NUM       nnnnn * Hub KDS_TEMS_TCP_PIPE_PORT_NUM  
000843 KDS_HUB_TCP_UDP_PORT_NUM        nnnnn * Hub KDS_TEMS_TCP_UDP_PORT_NUM   
000844 KDS_HUB_TCP_PIPE6_PORT_NUM      ""    * Hub KDS_TEMS_TCP_PIPE6_PORT_NUM 
000845 KDS_HUB_TCP_UDP6_PORT_NUM       ""    * Hub KDS_TEMS_TCP_UDP6_PORT_NUM  
000846 KDS_HUB_TCP_PIPES_PORT_NUM      ""    * Hub KDS_TEMS_TCP_PIPES_PORT_NUM 
000847 KDS_HUB_TCP_PIPE6S_PORT_NUM     ""    * Hub KDS_TEMS_TCP_PIPE6S_PORT_NUM
- - -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -   853 Line(s) not Displayed 
****** **************************** Bottom of Data ****************************
    3. After you finish customizing the profile, press F3 to save the changes and return to the Customize PARMGEN Configuration Profile Members panel. Press F3 again to return to the main Workflow panel.
  6. Validate the configuration profile values that you supplied:
    1. On the Workflow main panel, select option 9, KCIJPVAL Validate PARMGEN profile parameter values.
      The KCIJPVAL job is displayed.
    2. Review the notes and submit the job.
      The parameter validation report is written to the %RTE_PLIB_HILEV%.%RTE_NAME%.WCONFIG($VALRPT) member. Enter 9s to view the report.
    3. If the job gets a condition code greater than 4, review the $VALRPT report. Return to the previous step and correct the parameter values, then resubmit the validation job.
  7. Create the WK* runtime members and the WKANSAMU jobs:
    1. Select option 10, $PARSE Create the RTE members and jobs, from the Workflow main menu.
      The $PARSE/$PARSESV: Create the RTE Members and Jobs panel is displayed.
    2. Select option 1 to submit the generated $PARSE composite job. 
       KCIP@PR1 ------ $PARSE/$PARSESV: CREATE THE RTE MEMBERS AND JOBS --------------
 Option ===>                                                                    
                                                                                
 Select option 1 to SUBMIT the full $PARSE job in WCONFIG for   RTE=PLB1SP23.   
 $PARSE composite job creates product runtime members and jobs in    all the    
 PARMGEN WK* work libraries.  Alternatively, press F5 to SUBMIT the             
 library-specific $PARSE* jobs individually.                                    
                                                                                
 Enter ns (1s-2s) for detailed job/task status.                                 
                                                                                
                    Description                    Job Name   Status     Date   
    ---------------------------------------------- -------- --------- ----------
                                                                                
 1. Create runtime members/jobs in all WK* libs.   $PARSE                       
                                                                                
 2. Generate listing of symbolics       (Optional) $PARSEDV                     
                              Important                                         
 If this is a reconfiguration of an existing PARMGEN-maintained System          
 Variables-enabled RTE, then after rerunning the $PARSE job, you   must         
 rerun the WKANSAMU(KCIJVUPV) System Variables IEBUPDTE job next, to            
 refresh the variable-named runtime members.                                    
                                                                                
 Press F1=Help for more information. Press F5 for library specific $PARSE jobs.
      The $PARSE member is displayed.
    3. Review the member to make sure the values are correct, then submit the job.
      Return to the main Workflow panel.
  8. Submit the batch jobs to complete the setup of the runtime environment:
    1. Select option 11, SUBMIT, from the Workflow main menu.
      The Submit Batch Jobs to Complete PARMGEN Setup (KCIP@SUB) panel is displayed.
    2. Select option 1 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, then edit the job according to which of the conditional jobs can be submitted automatically and which have to be submitted manually (for example, for reasons of authorization). 
       KCIP@SUB -------- SUBMIT BATCH JOBS TO COMPLETE PARMGEN SETUP -----------------
 Option ===>                                                   Scroll ===> PAGE 
                                                                                
 Select option 1 to SUBMIT the composite jobs in WKANSAMU for RTE=PLB1SP23      
 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   
     --------------------------------------- ----- -------- --------- ----------
                                                                                
 1.  Composite SUBMIT job (See JCL comments)       KCIJPSUB                     
     ** or **                                                                   
 2.  Allocate runtime RO and RW (user) libs  (Yes) KCIJPALO                     
 3.  Copy SMP/E mbrs from TK*->RK* RO libs   (Yes) KCIJPLOD                     
 4.  Run product security steps              (No)  KCIJPSEC                     
 5.  Update variable-named runtime mbrs      (No ) KCIJPUPV                     
 6.  Create USS runtime mbrs in RKANDATV     (No)  KCIJPUSP                     
 7.  Execute USS commands                    (No)  KCIJPUSS                     
 8.  Copy runtime mbrs to system libs   (AUTH/Tip) KCIJPSYS                     
 9.  Run post-SMP/E RKANMODU ASM/LINK steps  (No)  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) KCIJPW2R                     
                                                                                
                                                                                
 Press F1=Help for more information.  Type UTIL to access utility menu.
    3. Submit the job.

Results

You created a copy of the PLB1SP22 runtime environment with a remote monitoring server instead of a hub and you have changed the runtime environment from full to sharing-with-SMP/E runtime environment.

What to do next

Complete any configuration steps required outside the configuration software. See the Planning and Configuration Guide for each product for details.