Setting up the work environment

The Set up the PARMGEN Work Environment option on the Workflow primary options menu presents a series of panels in which you provide or review information about the specified runtime environment (RTE), such as the type of RTE, the properties of the RTE, the products configured in it, and certain values common to all the products. The configuration software uses this information to set up the work environment by updating the interim libraries, creating or updating the configuration profiles, and running any additional required jobs (clone, convert, merge).

1. From the Workflow - Primary Option Menu, select Set up PARMGEN work environment for an RTE.
   The Set up PARMGEN Work Environment for an RTE (1 of 3) panel (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.)    
   

2. 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. The following options are available:

   • If you are creating a brand new RTE, leave this field blank. In this case, the configuration software sets up the RTE using only values that you provide.
   • If you want to create an RTE based on an IBM-provided model RTE, enter a question mark ("?") and select the model that matches your needs.
   • If you want 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.

   Jobcard data

   If a customized job card is already available, it is retrieved from the ISPF user profile pool. If it is not available and if you did not specify a JOBGEN output library, the job card is harvested from 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 that location. 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. On this panel, specify the parameter values appropriate for your environment. In most cases, the PARMGEN configuration parameters on this panel are required.

   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.       

3. The values on this panel are read from the profile library and runtime member name you specified on the preceding panel. Review the values on the panel and override them as necessary, then press Enter to proceed to the next panel.

   GBL_TARGET_HILEV

   Specifies the SMP/E high-level qualifier of the SMP/E target (TK*) libraries.

   GBL_SYSDA_UNIT

   Specifies the non-VSAM disk UNIT for global work data sets.

   GBL_REGION

   Specifies the JCL REGION value override if other than the REGION=0M value. This is the required storage value in Kilobytes or in Megabytes for PARMGEN batch jobs and product started tasks. The jobs contain the REGION= parameter on the EXEC statement. The syntax of the JCL REGION parameter is either &valueK or &valueM. Change this value as required by your installation. Specify K/M suffix (ex.: 4096K, 0M). The default is 0M.

   The Set up PARMGEN Work Environment for an RTE (3 of 3) panel (KCIPQPG3) is displayed. The values that are already specified on this panel are determined by the information you provided on previous panels, especially the RTE model profile. If you did not specify a model RTE profile, these values are the IBM® defaults. If you specified a model profile, the values are taken from that profile. The values on this panel are inherited by the corresponding parameters in the configuration profile for the new RTE.

   KCIP@PG3  SET UP/REFRESH PARMGEN WORK ENVIRONMENT FOR AN RTE (3 OF 3) ---------
   Command ===>                                                  Scroll ===> PAGE 
                                                                                  
   Enter parameter values appropriate for the LPAR RTE=DEMO.                     
   Press F1=Help for more information.                                            
                                                                      More:     + 
   RTE_DESCRIPTION:     DEMO description_______________________________          
                                                                                  
   RTE_TYPE:            FULL____       (Full, Sharing)                            
   RTE_HILEV:           TDITN.IDTST_____________________________ (ex.: TDITN.IDTST
                        (&hlq  portion of Non-VSAM RK* HLQ=&hlq.&rte_name)        
   RTE_VSAM_HILEV:      TDITN.IDTST_____________________________ (ex.: TDITN.IDTST
                        (&hlq  portion of VSAM RK* HLQ=&hlq.&rte_name)            
                                                                                  
   If any RTE dataset HLQ-related parameter values are NONSMS-managed:            
     RTE_SMS_UNIT:          ________   (Non-VSAM disk UNIT type)                  
     RTE_SMS_VOLUME:        ________   (Non-VSAM disk VOLSER)                     
     RTE_SMS_MGMTCLAS:      ________   (Non-VSAM disk MGMTCLAS)                   
     RTE_SMS_STORCLAS:      ________   (Non-VSAM disk STORCLAS)                   
     RTE_SMS_VSAM_VOLUME:   ________   (VSAM disk VOLSER)                         
     RTE_SMS_VSAM_MGMTCLAS: ________   (VSAM disk MGMTCLAS)                       
     RTE_SMS_VSAM_STORCLAS: ________   (VSAM disk STORCLAS)                       
                                                                                  
   RTE_SMS_PDSE_FLAG:       Y    (Y, N)   (Allocate Non-VSAM PDSE libraries)      
                                                                                  
   If RTE_TYPE is SHARING:                                                        
     RTE_X_HILEV_SHARING:   ___________________________________ (ex.: TDITN.IDTST)
                            (&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/User variables 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:   TDITN.IDTST.DEMO.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: DEMO:CMS__________________________ (e.g.,DEMO: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: CTD___________________ (1-4 char.VTAM APPLID prefix) 
     RTE_STC_PREFIX:         IBM___________________ (1-4 char.started task prefix)
   Note: Type BACK to go back one panel.  Type UTIL to access utility menu.       

   Depending upon your screen resolution, you might have to scroll down (PF8) to see all the parameters. (Look for the More: + that indicates that there is more content on the panel.)
4. Customize the following parameters as appropriate.

   RTE_DESCRIPTION

   A brief description that characterizes the RTE. This description is useful when you are choosing an RTE to clone and you want to select for certain features.

   SMS parameters

   If you are using a SMS-managed high-level qualifier index, volume, unit, storage class, and management class parameters for the global RTE_* parameters and the Kpp_* product-specific parameters are not required. If you are using non-SMS-managed RTE_HILEV and RTE_VSAM_HILEV high-level qualifiers, the RTE_SMS_VOLUME, RTE_SMS_VSAM_VOLUME, and RTE_SMS_UNIT values are required, as well as the product-specific Kpp_* VOLUME, UNIT, STORCLAS, and MGMGTCLAS equivalent parameters. (Certain products allow for product-specific Kpp_* VOLUME, UNIT, STORCLAS, and MGMGTCLAS parameters for their specific data set needs.) Review all *_VOLUME and other SMS and non-SMS parameters in the WCONFIG(rte_name) RTE configuration profile.

   RTE_SMS_PDSE_FLAG

   Specifies whether (Y or N) partitioned data sets are to be allocated as PDSE. The default is Y.

   RTE_SMS_UNIT

   Specifies the non-VSAM disk UNIT type to be used for data set allocation.

   RTE_SMS_VOLUME

   Specifies the non-VSAM disk VOLSER to be used for data set allocation.

   RTE_SMS_MGMTCLAS

   Specifies the non-VSAM disk MGMTCLAS to be used for data set allocation.

   RTE_SMS_STORCLAS

   Specifies the non-VSAM disk STORCLAS to be used for data set allocation.

   RTE_SMS_VSAM_VOLUME

   Specifies the VSAM disk VOLSER to be used for data set allocation.

   RTE_SMS_VSAM_MGMTCLAS

   Specify the VSAM disk VOLSER to be used for data set allocation. Specify the VSAM disk MGMTCLAS to be used for data set allocation.

   RTE_SMS_VSAM_STORCLAS

   Specifies the VSAM disk STORCLAS to be used for data set allocation.

   RTE parameters

   RTE_TYPE

   Specifies the type of RTE being created. The following types are valid:

   Full

   Allocates both private and base libraries. Use this type if you have only one RTE or if you have an RTE for an unique set of products.

   Sharing

   Allocates private libraries only. This type can either share base libraries with a base or full RTE, or use target libraries that were installed by SMP/E for its base libraries. Define one sharing RTE for each z/OS® image.

   Note: In PARMGEN, base libraries are created as part of creating the first RTE that shares the base. RTEs created after this one can point to the existing base using the RTE_SHARE parameter.

   RTE_HILEV

   Specifies the non-VSAM high-level qualifier that you want to use for the allocation of the non-VSAM production runtime (RK*) libraries. By default, the initial value for a brand new RTE is the RTE_PLIB_HILEV value that you specified on the Parameter Generator (PARMGEN) Workflow - Welcome panel.

   RTE_VSAM_HILEV

   Specifies the VSAM high-level qualifier that you want to use for the allocation of the VSAM production runtime (RK*) libraries. By default, the initial value for a brand new RTE is the RTE_PLIB_HILEV value you specified on the Parameter Generator (PARMGEN) Worfklow - Welcome panel.

   Sharing RTE parameters

   RTE_X_HILEV_SHARING

   Specifies the value of the non-VSAM high level qualifier of the RTE being shared to.

   RTE_SHARE

   Specifies the name of the Base or Full RTE from which the sharing RTE obtains its base library information. Required for a sharing RTE.

   RTE_LOAD_SHARED_LIBS

   Determines whether to include the shared libraries in the Load job of a sharing-with-base or sharing-with-full RTE. Accept the default value (Y) to ensure that all maintenance is loaded properly into the RTE.

   Tip: If you have multiple RTEs that share read-only data sets, configure only one of the environments to load the common shared base libraries (RTE_LOAD_SHARED_LIBS=Y). Set all the other sharing environments set to N. This configuration prevents the same libraries from being loaded every time that you run the KCIJPLOD load job for each sharing environment.

   • To create a sharing-with-base environment, specify a name for the shared (base) RTE using RTE_SHARE and the high-level qualifier for the shared RTE using RTE_X_HILEV_SHARING.
   • To create a sharing RTE that shares target libraries that were installed by SMP/E, provide the value SMP for RTE_SHARE.
   • To create a sharing-with-full environment, provide the name and high-level qualifier of the full RTE. If the RTE you specify has not yet been created, the configuration software creates the libraries for the full environment you have yet to create. If the RTE you are creating will have variables enabled, you can use symbolics to specify these values so that you will not have to replace started tasks across RTEs.

   Variables (symbolics) parameters

   RTE_SYSV_SYSVAR_FLAG

   Indicates whether to enable use of variables. Using variables allows systems to share PARMGEN definitions while using unique values in those definitions.

   If you are going to use variables, set any occurrence of the system name here or in the configuration profile to &SYSNAME.. (For example, set RTE_TEMS_NAME_NODEID to PLB3&SYSNAME.:CMS.)

   Security parameters

   RTE_SECURITY_USER_LOGON

   Security system to be used for the RTE. If you specify a security system, verify that it is installed and configured correctly for your site. Specify one of the following values: RACF®, ACF2, TSS, NAM, SAF, or None. If you specify ACF2, you must also provide the name of the ACF2 macro library as the value of the GBL_DSN_ACF2_MACLIB parameter. The System Authorization Facility (SAF) provides a generic API to interface to z/OS security software.

   Specifying a security system here indicates which system is used for security validation of users who sign on to the Tivoli® Enterprise Portal, but it does not enable validation. Security validation of users is enabled by the KDS_TEMS_SECURITY_KDS_VALIDATE parameter.

   RTE_SECURITY_FOLD_PASSWORD_FLAG

   Determines whether mixed case passwords are supported and being used. Required for full and sharing RTEs.

   By default, logon passwords are folded to uppercase. However, IBM RACF V1.7 and later supports mixed-case passwords. If you want to implement mixed-case passwords and if all your monitoring agents support them, set this field to N. If any of your monitoring agents do not support mixed-case passwords, do not activate the SETROPTS PASSWORD(MIXEDCASE) option in RACF and do not enable mixed-case passwords in your RTEs. Accept the default value of Y for this parameter.

   RTE_SECURITY_CLASS

   Specifies a common System Authorization Facility (SAF) security class name for OMEGAMON® Enhanced 3270 user interface security controls. The individual products have SAF security settings that are specific to them (for example, to secure product-specific Take Action requests). For more information , see the product-specific documentation.

   RTE_X_SECURITY_EXIT_LIB

   Specifies the name of the global library that houses all the OMEGAMON and Tivoli Management Services related product security exits (such as KOBSUPDT OMEGAMON KppSUPDI exits, TMS:Engine security exits, external security exits). This value overrides the SYSIN DD statement where the user exits may have been customized (if other than the default RKANSAM location). The KppJPSC3 input members to the composite KCIJPSEC security job point the SYSIN DD statement to RKANSAMU by default. If you must make further changes to the sample exit, copy the user exit to the xKANSAMU library, and make your changes accordingly. Then, modify the RTE_X_SECURITY_EXIT_LIB parameter and change the value to RKANSAMU instead.

   GBL_DSN_ACF2_MACLIBn

   Specifies the name of an ACF2 macro library. This parameter is required if the value specified for the RTE_SECURITY_USER_LOGON environment variable is ACF2. To include more than one ACF2 macro library, define more than one GBL_DSN_ACF2_MACLIBn parameter, with a unique number substituted for n at the end of each parameter name (example: GBL_DSN_ACF2_MACLIB1, GBL_DSN_ACF2_MACLIB2).

   Monitoring server settings

   RTE_TEMS_CONFIGURED_FLAG

   Specifies whether a Tivoli Enterprise Monitoring Server is to be configured in this RTE. Required for a full or sharing RTE that contains a monitoring server. If you are creating an RTE for stand-alone monitoring agents without a monitoring server, specify N. Otherwise, specify Y (the default) to allocate libraries for the monitoring server.

   RTE_TEMS_NAME_NODEID

   Specifies the unique name that identifies the monitoring server for internal processing. Required for a full or sharing RTE that contains a monitoring server.

   KDS_TEMS_TYPE

   Specifies whether to configure a hub monitoring server or a remote monitoring server.

   KDS_TEMS_HA_TYPE

   Specify whether to configure the Tivoli Enterprise Monitoring Server as a high-availability hub. This configuration requires a sysplex environment with dynamic virtual IP addressing (DVIPA) and shared DASD. A high-availability hub is configured in its own RTE, without monitoring agents, and can be configured on the same LPAR with a remote monitoring server.

   Communications and started task settings

   RTE_TCP_PORT_NUM

   Number of the well-known port to be used for IP communications. For detailed information about assigning port numbers, see Port number assignments in the Planning topics.

   RTE_VTAM_APPLID_PREFIX

   This parameter specifies the prefix to be used when building the VTAM applids for products in this RTE. If variables are enabled in this RTE, you can use a symbolic for this value (for example, k&SYSCLONE.). The resolved prefix can have a maximum of 4 characters. Be sure to place a period (.) after the last symbolic in the specification. If none of the products or components you intend to configure require SNA communications, delete the default value and leave this parameter value blank.

   RTE_STC_PREFIX

   For full and sharing RTEs, specify a prefix to be used when generating started task procedures for products that are configured in the RTE. The default value of IBM is provided, but specifying your own prefix prevents confusion with jobs generated by other RTEs on the same system.

   • If required by your site conventions, use RTE_STC_PREFIX to specify a prefix of up to 4 characters to replace the default IBM prefix for the names of started tasks that are created by the configuration software. If you choose to use symbolics, you can use up to 18 characters that resolve to 4 characters. For example, &SYSCLONE..
   • If required by your site conventions, use RTE_VTAM_APPLID_PREFIX to specify a prefix of up to 4 characters (or a symbolic of up to 18 characters that resolve to 4) for all VTAM® major nodes and applids. For example, TS&SYSCLONE..

5. After you specify all required parameters, press Enter.

   The Include Products in this PARMGEN RTE panel (KCIP@PGI) is displayed. This panel lists the products that are installed in the CSI target zone and are therefore available for configuration. By default, all of the products in the target zone are selected. If you specified an existing PARMGEN WCONFIG profile as the model, only the products that are configured within that member are selected. If the list exceeds screen size, you can scroll down using F8.

   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

6. To exclude any of the products from the runtime environment that you are configuring, delete the / before the product code. To add products, place a slash (/) before the product name.
7. After you review the product set and customize it as required, changeConfirm ==> N to Y and press Enter.

   The %GBL_USER_JCL%(KCIJPCFG) job is generated, tailored with the values you supplied.

8. Review this job and submit it.
   After you return to the main Workflow panel, you will note a > before option 1 to indicate that this is the last step you performed. The status and date fields for that option are updated.

   The KCIJPCFG job submits the KCIJPPRF job, which updates the work libraries and merges the values from the existing RTE. You see a status of SUBMITTED until both jobs complete. Do not proceed to the next step until you see a successful return code.