Customizing the override embed members

Override embeds provide a permanent way to support special customizations. Embed override files can be used to add user-defined parameters that might be overwritten when maintenance or upgrades are performed if they were added to the configuration profiles.

About this task

To customize override embed members, select option 4 on the Customize PARMGEN Configuration Profile Members panel. (You can also enter UTIL on the command line of any Workflow panel, then select option 7 to access the WCONFIG library.)

Table 1 lists some override embeds, the library in which the affected members are located, and the purpose of the embed member.
You can find a complete list of override embeds by reviewing the $JOBINDX README. The $JOBINDX is available in the RTE's WCONFIG dataset which is refreshed each time when one of the following maintenance scenarios is performed:
  • SMPE02
  • SMPE03
  • SMPE04
  • SMPE05
  • SMPE06
For more information about the maintenance scenarios, see SMP/E maintenance and upgrade scenarios.
Table 1. Override embeds
Embed member Library Purpose
Kpp$CSTR xKANCMDU Product-specific override embed in Tivoli® Enterprise Monitoring Server xKANCMDU(KDSSTRT1), Agent xKANCMDU(KppAGST) and CUA-specific startup runtime members. (CUA names vary by OMEGAMON® product.) (where x = I, W, R)
KMQ$CSTn* xKANCMDU OMEGAMON for Messaging (MQ Monitoring component only) override embed for xKANCMDU(KMQSTART) startup runtime member. *(where n = 1–5)
KMQ$CUSR xKANCMDU OMEGAMON for Messaging (MQ Monitoring component only) override embed for xKANCMDU(KMQUSER) startup runtime member.
KAG$PENV xKANPARU Common Agent override embed in all standalone Agents’ xKANPARU(KppENV) runtime member.
Kpp$PENV xKANPARU Product-specific override embed in Tivoli Enterprise Monitoring Server xKANPARU(KDSENV), Agent xKANPARU(KppENV) and applicable CUA xKANPARU(KppENV) runtime members.
Kpp$PSYS xKANPARU Product-specific override embed in Tivoli Enterprise Monitoring Server's and Agents’ xKANPARU(KppSYSIN) and CUA-specific runtime members. (CUA names vary by OMEGAMON product)
KDS$PTEC xKANPARU Tivoli Enterprise Monitoring Server override embed in xKANPARU(KMSOMTEC) Event Integration Facility (EIF) runtime member.
KD2$POMD xKD2PAR OMEGAMON for Db2 override embed for xKD2PAR(OMPE&dbid) OMEGAMON Server private parameter file.
KD2$POMP xKD2PAR OMEGAMON for Db2 override embed for xKD2PAR(OMPE00) OMPE subsystem initialization runtime member.
KD2$POPT xKD2PAR OMEGAMON for Db2 override embed for xKD2PAR(OMPEOPTS) OMPE Collector Realtime Customer Options runtime member (1 of 2).
KD2$POP1 xKD2PAR OMEGAMON for Db2 override embed for xKD2PAR(OMPEOPTS) OMPE Collector Realtime Customer Options runtime member (2 of 2).
KEP$PEDS xKANPARU OMEGAMON for z/OS override embed for xKANPARU(KEPEDS) Epilog runtime member.
KEP$POPT xKANPARU OMEGAMON for z/OS override embed for xKANPARU(KEPOPTN) Epilog runtime member.
KI2$PTRF xKANPARU OMEGAMON for IMS override embed for xKANPARU(KI2ATFmp) TRF runtime member (where mp = MPREFIX; one per IMS subsystem configured in the RTE).
KOI$PJLF xKANPARU OMEGAMON for IMS override embed for xKANPARU(KOIJLF00) Journal Logging Facility (JLF) runtime member.
KM5$PDEV xKANPARU OMEGAMON for z/OS override embed for xKANPARU(KOSDEVIN) DASD Device runtime member.
KDF$PDEV xKANPARU OMEGAMON for Storage override embed for xKANPARU(KDFDEVIN) DASD Device runtime member.
KDF$PDVS xKANPARU OMEGAMON for Storage override embed for xKANPARU(KDFDEVSU) DASD Device runtime member.
KDF$PHSN xKANPARU OMEGAMON for Storage override embed for xKANPARU(KDFDHSIN) HSM monitoring and log analysis (LOGY) options runtime member.
KAG$SST1 xKANSAMU Common Agent STEPLIB DD override in all Agents’ started tasks.
KAG$SST2 xKANSAMU Common Agent RKANMODL DD override in all Agents' started tasks.
KAG$SST3 xKANSAMU Common Agent additional DD override in all Agents' started tasks (for example, add SYSMDUMP DD, etc. in each of the Agent started tasks [default xKANSAMU(IBMpp)]).
Kpp$SST1 xKANSAMU Product-specific STEPLIB DD override in the product started task.
Kpp$SST2 xKANSAMU Product-specific RKANMODL DD override in product started task.
Kpp$SST3 xKANSAMU Product-specific additional DD override in product started tasks (for example, add SYSMDUMP DD, etc. in the product started task [default xKANSAMU(IBMpp)]).
Kpp$SDLn xKANSAMU

Product-specific imbeds to the xKANSAMU(KppDFINL) post-configuration README steps for autodiscovered subsystems by the PARMGEN KCIJPDLA z/OS DLA job (for example, KJJ$SDLn imbeds for KJJDFINL for autodiscovered JVMs directories where the OMEGAMON for JVM agent options are added for detailed monitoring).

KI2$SSCn** xKANSAMU OMEGAMON for IMS KOICTXX module statement input to the KCIJPSEC/KOISUPD Classic command table security jobs for OMEGAMON for IMS

**where n = 1–2.

KCI$SST1 xKANSAMU Common accounting imbed for adding information about the started tasks, such as owner, type of task, type of LPAR. This embed is originally populated with job card information.
KJT$PPRP xKANPARU KJTCOLL override in Agent's xKANPARU(KJTPRP00) common collector property file of the OMEGAMON for JVM Agent.

Placeholder parameters are provided in the embed files. You can uncomment and customize the values for these parameters or add your own.

For example, you might want to change the refresh rate of the OMEGAMON Enhanced 3270 user interface local registry. This registry stores information about OMEGAMON agent data sources. By default, the registry information is refreshed every 5 minutes. You can change the refresh rate temporarily by using the MVS MODIFY command, or you can change it permanently by using the REGREF parameter in the KOB$PENV embed.

In the KDS$PENV file, one set of place holder parameters points to user variable symbols that are already defined in the variables configuration profile in the %GBL_USER_JCL%(%RTE_NAME%) PARMGEN global library: KDS_HEAP_SIZE=&KDS_HEAP_SIZE., KGL_GMMSTORE=&KGL_GMMSTORE., and KDS_NCSLISTEN=&KDS_NCSLISTEN. If you use these parameters, edit the variables profile to set the appropriate resolution values.

Figure 1. KDS$PENV override file. This figure show the user section of the KDS$PENV override file.
 000049 ** ******************************************************************   
 000050 KDS_HEAP_SIZE=1024                                                      
 000051 *KDS_HEAP_SIZE=&KDS_HEAP_SIZE.                                          
 000052 KGL_GMMSTORE=1024                                                       
 000053 *KGL_GMMSTORE=&KGL_GMMSTORE.                                            
 000054 KDS_NCSLISTEN=256                                                       
 000055 *KDS_NCSLISTEN=&KDS_NCSLISTEN.                                          
 000056 ** ******************************************************************   
 000057 ** Additional common Agent parameters:                                  
 000058 ** ******************************************************************   
 000059 *CTIRA_HEARTBEAT=5                                                      
 000060 *CTIRA_RECONNECT_WAIT=600                                               
 000061 *CTIRA_PRIMARY_FALLBACK_INTERVAL=1500                                   
 000062 *CTIRA_HOSTNAME="%RTE_NAME%:CMS"                                        
 000063 *CTIRA_SUBSYSTEM_ID=&subsystem                                          
 000064 *TEMA_SDA_ACK_WAIT=300                                                  
 000065 *TEMA_SDA_RETRY_WAIT=300                                                
 000066 *TEMA_SDA_MAX_ATTEMPT=1                                                 
 000067 *KDEB_INTERFACELIST_IPV6=-                                              
 000068 * ----------------- END   - USER SECTION: OVERRIDE ---------------- *

What to do next

The next step is to create the RTE members and jobs.