Parameter names

Information on parameter names and how they are used is provided in this section.

Stored parameter name
Name of the parameter as stored in a runtime library. Example: LIMIT
PARMGEN name
Name of the parameter in the PARMGEN parameter list. Example: KDS_TEMS_STORAGE_LIMIT_EXTEND
In this guide, the parameters in each chapter are documented in alphabetical order by PARMGEN name, and all other applicable names for each parameter are shown. You can use the Index to look up a parameter by one of the names other than the PARMGEN name.

Parameters with n or nn in their names

Some parameters include n or nn in their names. These are not the actual names of these commands as you will see them in the configuration profile. The n or nn means that you can have multiple instances of this parameter in your configuration profile. For example, you will most likely have multiple instances of the set of monitoring agent component override commands (for example, KN3_TCPXnn_OVRD_CONN or KN3_TCPXnn_OVRD_FTP) because you have one set of values for every instance in which you override the global (all stacks) collection values for a specific stack. Likewise, you would have multiple instances of the KN3_AGT_NONSTDn_DSN, KN3_AGT_NONSTDn_MBR, KN3_AGT_NONSTDn_PARM values if you defined several nonstandard parameters. If you cannot find a parameter by searching on its full name, try searching on a part of the name, omitting the numbers that define instance.

Parameters designated N/A

Some parameters have "N/A" (not applicable) designated in the field description. This designation means that these parameter cannot be set using the mode being described.

There is a difference in how PARMGEN designates multiple instances of sets of parameters for stack-specific configuration (as opposed to global values) in the configuration profile file and how batch mode handles these same parameters. As noted previously, override commands in PARMGEN have a two-digit number (represented as nn) appended to the middle of the parameter name (for example, KN3_TCPXnn) indicating a stack-specific override of a global value (for example, KN3_TCPX01_OVRD_CONN or KN3_TCPX02_OVRD_CONN to override the global value KN3_TCP_CON). Batch mode does not append the two-digit number to indicate a stack-specific override. Instead, Batch overrides are indicated with a KN3_TCPX BEGIN or KON_TCPX BEGIN statement and concluded with a KN3_TCPX END or KON_TCPX END statement, as shows in the following sample Batch mode file: 
 ** TCP/IP Information:                                                  
 KN3_TCP_DATA              SYS1.TCPPARMS(TCPDATA)                        
 KN3_TCP_SAMP_INTERVAL     1                                             
 KN3_TCP_STACK             Y                                             
 KN3_TCP_CON               Y                 <-- global default
 .
 .
 ** Define TCP monitoring systems member:                                
 KN3_TCPX                  BEGIN                           * Table begin 
 KN3_TCPX_ROW                                                            
 KN3_TCPX_SYS_NAME         $$$$                                          
 KN3_TCPX_ADDR_SPACE       $$$$$$$$                                      
 KN3_TCPX_PROF_DATASET     TCPIP.PROFILE.TCPIP                           
 KN3_TCPX_OGBL             N                                             
 KN3_TCPX_OSTACK           Y                                             
 KN3_TCPX_OTCPC            Y   <-- stack specific-default (this is also global)
 . 
 . 
 **KN3_TCPX_PROF_MEMBER                            
 KN3_TCPX_ROW                                      
 KN3_TCPX_SYS_NAME         $$$$                    
 KN3_TCPX_ADDR_SPACE       SAMPLESTACK             
 KN3_TCPX_PROF_DATASET     USER.PARMLIB            
 KN3_TCPX_OGBL             Y                       
 KN3_TCPX_OSTACK           Y                       
 KN3_TCPX_OTCPC            Y   <-- stack specific for SAMPLESTACK  
  . 
  . 
 KN3_TCPX_PROF_MEMBER      SAMPLESTACK   <-- End of SAMPLESTACK parameters 
  . 
  . 
 KN3_TCPX                  END   <--End of all overrides for all stacks