IBM Tivoli OMEGAMON XE e IBM Tivoli Management Services en z

Transcripción

Version 6.2.3 Fix Pack 1
IBM Tivoli OMEGAMON XE and IBM
Tivoli Management Services on z/OS
Common Parameter Reference
SC14-7280-01
IBM Tivoli OMEGAMON XE and IBM
Tivoli Management Services on z/OS
SC14-7280-01
Notices
This edition applies to version 4, release 2 of the IBM Tivoli OMEGAMON XE products and to version 6, release 2,
modification 2 of IBM Tivoli Management Services on z/OS (product number 5698-A79) and to all subsequent
releases and modifications until otherwise indicated in new editions.
© Copyright IBM Corporation 2010, 2012.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
About this information . . . . . . . . vii
Chapter 1. Overview . . . . . . . . . 1
Where configured parameters are stored .
How parameter values are set . . . .
PARMGEN method . . . . . . .
Configuration Tool (ICAT) method . .
Default values . . . . . . . . . .
Parameter names . . . . . . . . .
Determining what products are configured
runtime environment . . . . . . .
Parameters covered in this guide . . .
.
.
.
.
.
.
in
.
.
. .
. .
. .
. .
. .
. .
each
. .
. .
.
.
.
.
.
.
1
1
2
2
2
3
. 4
. 5
Chapter 2. Common agent (KPP)
parameters . . . . . . . . . . . . . 7
KPP_AGT_AUDIT_ITM_DOMAIN . . . .
KPP_AGT_AUDIT_MAX_HIST . . . . .
KPP_AGT_AUDIT_TRACE . . . . . .
KPP_AGT_CONFIGURATION_MODE . .
KPP_AGT_COMM_PROTOCOLn . . . .
KPP_AGT_FLUSH_LSR_BUFR_INT_HR . .
KPP_AGT_FLUSH_LSR_BUFR_INT_MIN .
KPP_AGT_ICU_LANGUAGE_LOCALE . .
KPP_AGT_KGL_WTO . . . . . . . .
KPP_AGT_KLX_TCP_TOLERATERECYCLE
KPP_AGT_NSNEWn_VALUE . . . . .
KPP_AGT_NONSTDn_DSN . . . . . .
KPP_AGT_NONSTDn_MBR . . . . . .
KPP_AGT_NONSTDn_PARM . . . . .
KPP_AGT_NSOLDn_VALUE . . . . .
KPP_AGT_PARTITION_NAME. . . . .
KPP_AGT_PPI_RECEIVER . . . . . .
KPP_AGT_PPI_SENDER . . . . . . .
KPP_AGT_STC . . . . . . . . . .
KPP_AGT_STORAGE_DETAIL_INT_HR .
KPP_AGT_STORAGE_DETAIL_INT_MIN .
KPP_AGT_STORAGE_MINIMUM_EXTEND
KPP_AGT_TCP_HOST . . . . . . .
KPP_AGT_TCP_KDEB_INTERFACELIST .
KPP_AGT_TCP_STC . . . . . . . .
KPP_AGT_TEMA_SDA . . . . . . .
KPP_AGT_TEMS_NAME_NODEID . . .
KPP_AGT_VIRTUAL_IP_ADDRESS . . .
KPP_AGT_VTAM_APPL_AA . . . . .
KPP_AGT_VTAM_APPL_KPPINVPO. . .
KPP_AGT_VTAM_APPL_NCS . . . . .
KPP_AGT_VTAM_APPL_OPERATOR . .
KPP_AGT_VTAM_APPL_PREFIX . . . .
KPP_AGT_VTAM_NODE . . . . . .
KPP_AGT_WTO_MSG. . . . . . . .
KPP_PD . . . . . . . . . . . .
KPP_PD_CYL . . . . . . . . . .
KPP_PD_GRP . . . . . . . . . .
KPP_PD_HISTCOLL_DATA_IN_AGT_STC .
KPP_PD_HISTCOLL_DATA_IN_TEMS_STC
© Copyright IBM Corp. 2010, 2012
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 7
. 8
. 9
. 10
. 11
. 13
. 14
. 14
. 16
. 17
. 18
. 19
. 20
. 21
. 22
. 22
. 24
. 25
. 26
. 27
. 28
. 29
. 30
. 31
. 32
. 33
. 34
. 35
. 36
. 37
. 38
. 38
. 39
. 40
. 41
. 42
. 43
. 44
. 45
. 46
KPP_PD_ROW . . . . . . . . . . .
KPP_SECURITY_ACTION_CLASS. . . . .
KPP_TEMS_BKUP1_NAME_NODEID . . .
KPP_TEMS_BKUP1_TCP_HOST . . . . .
KPP_TEMS_BKUP1_VTAM_APPL_LLB_BKR .
KPP_TEMS_BKUP1_VTAM_LU62_DLOGMOD
KPP_TEMS_BKUP1_VTAM_NETID . . . .
KPP_TEMS_HUB_TCP_HOST . . . . . .
KPP_TEMS_LOCAL_CONNECT_FLAG . . .
KPP_TEMS_NAME_NODEID . . . . . .
KPP_TEMS_TCP_HOST . . . . . . . .
KPP_TEMS_TCP_PIPE_PORT_NUM . . . .
KPP_TEMS_TCP_PIPES_PORT_NUM . . .
KPP_TEMS_TCP_PIPE6_PORT_NUM. . . .
KPP_TEMS_TCP_PIPE6S_PORT_NUM . . .
KPP_TEMS_TCP_UDP_PORT_NUM . . . .
KPP_TEMS_TCP_UDP6_PORT_NUM. . . .
KPP_TEMS_VTAM_APPL_LLB_BROKER . .
KPP_TEMS_VTAM_LU62_DLOGMOD . . .
KPP_TEMS_VTAM_LU62_MODETAB . . .
KPP_TEMS_VTAM_NETID . . . . . . .
KPP_X_AGT_CONFIRM_SHUTDOWN . . .
KPP_X_AGT_DEBUG_TRACE . . . . . .
KPP_X_AGT_KDC_DEBUG . . . . . . .
KPP_X_AGT_LGSA_VERIFY . . . . . .
KPP_X_AGT_LSRPOOL_BUFFER_NUM. . .
KPP_X_AGT_LSRPOOL_BUFSIZE . . . . .
KPP_X_AGT_SDUMP_SVC_SYS1_DUMP . .
KPP_X_AGT_STORAGE_LIMIT_EXTEND . .
KPP_X_AGT_STORAGE_LIMIT_PRIMARY . .
KPP_X_AGT_STORAGE_RESERVE_EXT. . .
KPP_X_AGT_STORAGE_RESERVE_PRI . . .
KPP_X_AGT_STORAGE_STGDEBUG . . .
KPP_X_AGT_TASKS_ATTACHED_NUM . .
KPP_X_HUB_BKUP1_TCP_HOST . . . . .
KPP_X_HUB_BKUP1_TEMS_VTAM_NETID .
KPP_X_HUB_BKUP1_VTAM_APPL_GLBBKR .
KPP_X_HUB_TCP_HOST. . . . . . . .
KPP_X_HUB_TEMS_VTAM_NETID . . . .
KPP_X_HUB_VTAM_APPL_GLBBKR. . . .
KPP_X_PD_HISTCOLL_DATA_AGT_STC . .
KPP_X_PD_HISTCOLL_DATA_TEMS_STC . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
47
48
49
50
51
52
53
54
54
55
57
58
59
60
61
61
62
63
64
65
66
67
68
68
69
70
71
71
72
73
73
74
75
75
76
76
77
77
78
78
79
79
Chapter 3. Global (GBL) parameters . . 81
GBL_DSN_ACF2_MACLIB .
GBL_DSN_CBC_SCCNOBJ .
GBL_DSN_CBC_SCLBSID .
GBL_DSN_CEE_SCEEBIND .
GBL_DSN_CEE_SCEEBND2 .
GBL_DSN_CEE_SCEECPP .
GBL_DSN_CEE_SCEELIB. .
GBL_DSN_CEE_SCEELKED .
GBL_DSN_CEE_SCEELKEX .
GBL_DSN_CEE_SCEEMSGP.
GBL_DSN_CEE_SCEERUN .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
81
81
82
82
82
83
83
83
84
84
85
iii
GBL_DSN_CEE_SCEESPC . . . . . .
GBL_DSN_CICS_CTG_DLL . . . . . .
GBL_DSN_CICS_SCTGSID . . . . . .
GBL_DSN_CICS_SDFHC370 . . . . . .
GBL_DSN_CICS_SDFHLOAD . . . . .
GBL_DSN_CSF_SCSFMOD0 . . . . . .
GBL_DSN_DB2_DSNEXIT . . . . . .
GBL_DSN_DB2_LOADLIB_Vn . . . . .
GBL_DSN_DB2_RUNLIB_Vn . . . . .
GBL_DSN_DB2_SDSNLOAD . . . . .
GBL_DSN_HZSPROC_LOADLIB . . . .
GBL_DSN_IMS_RESLIB . . . . . . .
GBL_DSN_IMS_SCEXLINK . . . . . .
GBL_DSN_IMS_SFUNLINK . . . . . .
GBL_DSN_ISP_SISPLOAD . . . . . .
GBL_DSN_NETVIEW_CNMLINK . . . .
GBL_DSN_SYS1_BRODCAST . . . . .
GBL_DSN_SYS1_CSSLIB . . . . . . .
GBL_DSN_SYS1_HSMLOGY . . . . .
GBL_DSN_SYS1_LINKLIB . . . . . .
GBL_DSN_SYS1_MACLIB . . . . . .
GBL_DSN_SYS1_MODGEN . . . . . .
GBL_DSN_SYS1_PARMLIB . . . . . .
GBL_DSN_SYS1_PROCLIB . . . . . .
GBL_DSN_SYS1_SAXREXEC . . . . .
GBL_DSN_SYS1_SBLSCLI0 . . . . . .
GBL_DSN_SYS1_SBPXEXEC. . . . . .
GBL_DSN_SYS1_SISTMAC1 . . . . . .
GBL_DSN_SYS1_VTAMLIB . . . . . .
GBL_DSN_SYS1_VTAMLST . . . . . .
GBL_DSN_TCP_ETC_SERVICES . . . .
GBL_DSN_TCP_SEZACMTX . . . . .
GBL_DSN_TCP_SEZARNT1 . . . . .
GBL_DSN_TCP_SEZATCP . . . . . .
GBL_DSN_TCP_SYSTCPD_TCPDATA . .
GBL_DSN_TCP_SYSTCPD_TCPDATA_MFN
GBL_DSN_WMQ_SCSQANLE. . . . .
GBL_DSN_WMQ_SCSQAUTH . . . .
GBL_DSN_WMQ_SCSQLOAD . . . .
GBL_HFS_JAVA_DIRn . . . . . . .
GBL_INST_HILEV. . . . . . . . .
GBL_TARGET_HILEV . . . . . . .
GBL_USER_JCL . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 85
. 85
. 86
. 86
. 87
. 87
. 87
. 88
. 89
. 89
. 90
. 90
. 91
. 91
. 92
. 92
. 93
. 93
. 94
. 94
. 94
. 95
. 95
. 96
. 96
. 96
. 97
. 98
. 98
. 99
. 99
. 99
. 100
. 100
. 101
. 101
. 102
. 102
. 103
. 103
. 104
. 104
. 105
Chapter 4. Runtime environment
(RTE) parameters. . . . . . . . . . 107
RTE_BASE_NAME . . . . . .
RTE_CANSCN_STC . . . . . .
RTE_CANSETE_STC . . . . . .
RTE_DEBUG_SYSOUT . . . . .
RTE_DESCRIPTION . . . . . .
RTE_HCK_STC_INTERVAL . . .
RTE_HILEV . . . . . . . . .
RTE_JCL_SUFFIX . . . . . . .
RTE_KCNDLSSI_IEFSSN00_FORMAT
RTE_KCNSTR00_SSID . . . . .
RTE_KCNSTR00_WTO . . . . .
RTE_KCNSTR00_XCFGROUP . . .
RTE_LOAD_OPTIMIZE . . . . .
RTE_LOAD_SHARED_LIBS . . .
RTE_LOG_SYSOUT . . . . . .
iv
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
107
107
108
109
109
110
110
111
112
113
113
114
115
116
116
RTE_NAME . . . . . . . . . . .
RTE_PDS_BATCHINIT_FLAG . . . . .
RTE_PDS_BACKUP_FLAG . . . . . .
RTE_PDS_EXPORT_FLAG . . . . . .
RTE_PDS_EXTRACT_FLAG . . . . .
RTE_PDS_FILE_COUNT . . . . . .
RTE_PDS_HILEV . . . . . . . . .
RTE_PDS_KPDPROC_PREFIX . . . . .
RTE_PDS_SMS_MGMTCLAS . . . . .
RTE_PDS_SMS_STORCLAS . . . . .
RTE_PDS_SMS_UNIT . . . . . . .
RTE_PDS_SMS_VOLUME . . . . . .
RTE_REMOTE_LPAR_FLAG . . . . .
RTE_SECURITY_CLASS . . . . . . .
RTE_SECURITY_FOLD_PASSWORD_FLAG
RTE_SECURITY_USER_LOGON . . . .
RTE_SHARE . . . . . . . . . .
RTE_SMS_MGMTCLAS . . . . . . .
RTE_SMS_PDSE_FLAG . . . . . . .
RTE_SMS_STORCLAS . . . . . . .
RTE_SMS_UNIT . . . . . . . . .
RTE_SMS_VOLUME . . . . . . . .
RTE_SMS_VSAM_MGMTCLAS . . . .
RTE_SMS_VSAM_STORCLAS . . . . .
RTE_SMS_VSAM_VOLUME . . . . .
RTE_STC_PREFIX . . . . . . . . .
RTE_SYSV_BASE_ALIAS . . . . . .
RTE_SYSV_NAME . . . . . . . .
RTE_SYSV_SYSVAR_FLAG . . . . . .
RTE_SYSV_TEMS_NAME_NODEID . . .
RTE_SYSV_VTAM_APPLID_MODEL . .
RTE_SYSV_VTAM_APPLID_PREFIX . .
RTE_SYSV_VTAM_NETID . . . . . .
RTE_TCP_HOST . . . . . . . . .
RTE_TCP_PORT_NUM . . . . . . .
RTE_TCP_STC . . . . . . . . . .
RTE_TEMS_CONFIGURED_FLAG . . .
RTE_TEMS_NAME_NODEID . . . . .
RTE_TN3270_DXL_HOSTADDRESS . . .
RTE_TN3270_DXL_LUGROUP . . . .
RTE_TN3270_DXL_TN3270PORT . . . .
RTE_TYPE . . . . . . . . . . .
RTE_USERMODS_FLAG . . . . . .
RTE_USS_RTEDIR . . . . . . . . .
RTE_VSAM_HILEV . . . . . . . .
RTE_VTAM_APPLID_PREFIX . . . . .
RTE_VTAM_GBL_MAJOR_NODE . . .
RTE_VTAM_LU62_DLOGMOD . . . .
RTE_VTAM_LU62_MODETAB . . . .
RTE_VTAM_NETID . . . . . . . .
RTE_X_KCNDLSSI_INITPARM_FLAG . .
RTE_X_KCNSTR00_PLEXCOLLECT . . .
RTE_X_KCNSTR00_REFRESH . . . . .
RTE_X_SECURITY_DATA_ABOVE . . .
RTE_X_SECURITY_EXIT_LIB . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
117
117
118
119
120
120
121
122
122
123
123
124
125
125
126
127
128
129
129
130
131
131
132
133
133
134
134
135
136
137
137
138
139
139
140
140
141
142
143
144
144
145
146
146
148
148
149
150
150
151
151
152
153
154
154
Chapter 5. Tivoli Enterprise
Monitoring Server (KDS) parameters . 157
KDS_AUDIT_ITM_DOMAIN .
KDS_AUDIT_MAX_HIST . .
KDS_AUDIT_TRACE. . . .
.
.
.
.
.
.
IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS Common Parameter Reference
.
.
.
.
.
.
.
.
.
.
.
.
. 157
. 157
. 158
KDS_HUB_TCP_HOST . . . . . . . .
KDS_HUB_TCP_PIPE_PORT_NUM . . . .
KDS_HUB_TCP_PIPE6_PORT_NUM . . .
KDS_HUB_TCP_PIPE6S_PORT_NUM . . .
KDS_HUB_TCP_PIPES_PORT_NUM . . .
KDS_HUB_TCP_UDP_PORT_NUM . . . .
KDS_HUB_TCP_UDP6_PORT_NUM . . .
KDS_HUB_TEMS_HA_TYPE . . . . . .
KDS_HUB_VTAM_APPL_GLB_BROKER . .
KDS_HUB_VTAM_NETID . . . . . . .
KDS_KMS_SDA . . . . . . . . . .
KDS_MIG_TAPE_HILEV . . . . . . .
KDS_MIG_TAPE_UNIT . . . . . . . .
KDS_MIG_TAPE_VOL . . . . . . . .
KDS_MIG_VER. . . . . . . . . . .
KDS_MIG_VSAM_HILEV . . . . . . .
KDS_NONSTDnn_DSN . . . . . . . .
KDS_NONSTDnn_MBR . . . . . . . .
KDS_NONSTDnn_PARM . . . . . . .
KDS_NSNEWnn_VALUE . . . . . . .
KDS_NSOLDnn_VALUE. . . . . . . .
KDS_PA . . . . . . . . . . . . .
KDS_PA_PARTITION_ADDRESS . . . . .
KDS_PA_PARTITION_NAME . . . . . .
KDS_PA_ROW . . . . . . . . . . .
KDS_PD . . . . . . . . . . . . .
KDS_PD_CYL . . . . . . . . . . .
KDS_PD_GRP . . . . . . . . . . .
KDS_PD_ROW . . . . . . . . . . .
KDS_PH . . . . . . . . . . . . .
KDS_PH_ROW . . . . . . . . . . .
KDS_PH_TEMS_ALIAS_NAME . . . . .
KDS_PH_TEMS_COMM_PROTOCOL1 . . .
KDS_PH_TEMS_KSH_SECURE . . . . .
KDS_PH_TEMS_NAME_NODEID . . . .
KDS_PH_TEMS_RTE . . . . . . . . .
KDS_PH_TEMS_SYSV_FLAG . . . . . .
KDS_PH_TEMS_TCP_HOST . . . . . .
KDS_PH_TEMS_TCP_HOST_LEN . . . .
KDS_PH_TEMS_TCP_PORT_NUM . . . .
KDS_PH_TEMS_USER_QUERY . . . . .
KDS_PH_TEMS_USER_UPDATE . . . . .
KDS_PH_TEMS_VTAM_APPL_GLB_BROKER
KDS_PH_TEMS_VTAM_LU62_DLOGMOD .
KDS_PH_TEMS_VTAM_NETID . . . . .
KDS_PPI_RECEIVER . . . . . . . . .
KDS_PPI_SENDER . . . . . . . . .
KDS_PU . . . . . . . . . . . . .
KDS_PU_ROW . . . . . . . . . . .
KDS_PU_TEMS_NAME_NODEID . . . .
KDS_PU_TEMS_RTE . . . . . . . . .
KDS_PU_TEMS_USER_ID . . . . . . .
KDS_PU_TEMS_USER_QUERY . . . . .
KDS_PU_TEMS_USER_UPDATE . . . . .
KDS_TEMA_SDA . . . . . . . . . .
KDS_TEMS_COMM_ADDRESS_XLAT . . .
KDS_TEMS_COMM_PROTOCOLn . . . .
KDS_TEMS_DRA_FLAG . . . . . . .
KDS_TEMS_EIF_BUFFER_EVENT_MAXSZE .
KDS_TEMS_EIF_DISABLE_TEC_EMITTER .
KDS_TEMS_EIF_EVENT_LISTENER. . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
159
159
160
161
162
163
164
165
166
166
167
168
168
169
170
170
171
172
173
174
174
175
176
177
177
178
178
179
180
180
181
181
182
182
183
184
184
185
186
186
187
187
188
188
189
190
191
192
192
192
193
194
194
195
196
196
197
198
199
200
201
KDS_TEMS_EIF_FLAG . . . . . . . .
KDS_TEMS_EIF_HOST . . . . . . . .
KDS_TEMS_EIF_PORT_NUM . . . . . .
KDS_TEMS_FLUSH_LSR_BUFR_INT_HR . .
KDS_TEMS_FLUSH_LSR_BUFR_INT_MIN .
KDS_TEMS_HA_EXCL_LIST . . . . . .
KDS_TEMS_HA_TYPE . . . . . . . .
KDS_TEMS_HTTP_PORT_NUM . . . . .
KDS_TEMS_ICU_LANGUAGE_LOCALE . .
KDS_TEMS_KDC_DEBUG . . . . . . .
KDS_TEMS_KGL_WTO . . . . . . . .
KDS_TEMS_KLX_TCP_TOLERATERECYCLE
KDS_TEMS_PARTITION_NAME . . . . .
KDS_TEMS_SECURITY_KAES256_ENCKEY .
KDS_TEMS_SECURITY_KDS_VALIDATE . .
KDS_TEMS_SOAP_SERVER_FLAG . . . .
KDS_TEMS_STC . . . . . . . . . .
KDS_TEMS_STORAGE_DETAIL_INT_HR . .
KDS_TEMS_STORAGE_DETAIL_INT_MIN .
KDS_TEMS_STORAGE_DETAIL_LOG_FLAG
KDS_TEMS_STORAGE_LIMIT_EXTEND . .
KDS_TEMS_STORAGE_LIMIT_PRIMARY . .
KDS_TEMS_STORAGE_MINIMUM_EXTEND
KDS_TEMS_TCP_HOST . . . . . . . .
KDS_TEMS_TCP_KDEB_INTERFACELIST .
KDS_TEMS_TCP_PIPE_PORT_NUM . . .
KDS_TEMS_TCP_PIPE6_PORT_NUM . . .
KDS_TEMS_TCP_PIPE6S_PORT_NUM . . .
KDS_TEMS_TCP_PIPES_PORT_NUM . . .
KDS_TEMS_TCP_STC . . . . . . . .
KDS_TEMS_TCP_UDP_PORT_NUM . . .
KDS_TEMS_TCP_UDP6_PORT_NUM . . .
KDS_TEMS_TYPE . . . . . . . . . .
KDS_TEMS_VIRTUAL_IP_ADDRESS . . .
KDS_TEMS_VTAM_APPL_CUA_OPER. . .
KDS_TEMS_VTAM_APPL_GLB_BROKER . .
KDS_TEMS_VTAM_APPL_KDS_VTAMID . .
KDS_TEMS_VTAM_APPL_KDSINVPO . . .
KDS_TEMS_VTAM_APPL_LLB_BROKER . .
KDS_TEMS_VTAM_APPL_OPERATOR. . .
KDS_TEMS_VTAM_APPL_PREFIX . . . .
KDS_TEMS_VTAM_LU62_DLOGMOD . . .
KDS_TEMS_VTAM_LU62_MODETAB . . .
KDS_TEMS_VTAM_NETID. . . . . . .
KDS_TEMS_VTAM_NODE . . . . . . .
KDS_X_HUB_BKUP1_TCP_HOST . . . .
KDS_X_HUB_BKUP1_TEMS_VTAM_NETID .
KDS_X_HUB_BKUP1_VTAM_APPL_GLBBKR
KDS_X_KDCFC_RXLIMIT . . . . . . .
KDS_X_KDE_TRANSPORT_HTTP_OPTIONS
KDS_X_KDE_TRANSPORT_OPTIONS . . .
KDS_X_KDE_TRANSPORT_POOL_OPTIONS
KDS_X_SECURITY_RESOURCE_CLASS . .
KDS_X_SECURITY_USER_EXIT . . . . .
KDS_X_STC_SYSTCPD_INCLUDE_FLAG . .
KDS_X_TEMS_CONFIRM_SHUTDOWN . .
KDS_X_TEMS_DEBUG_TRACE . . . . .
KDS_X_TEMS_EIF_BFR_EVT . . . . . .
KDS_X_TEMS_EIF_BFR_EVT_PATH. . . .
KDS_X_TEMS_EIF_FLT_ATTR1 . . . . .
KDS_X_TEMS_EIF_FLT_CLASS1 . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
202
203
203
204
205
206
206
207
208
210
211
212
213
214
214
215
216
216
217
218
219
220
221
222
222
224
225
226
227
228
229
230
232
233
233
234
234
235
236
237
237
238
238
239
240
240
241
241
242
242
243
244
244
245
245
246
247
247
248
249
249
Contents
v
KDS_X_TEMS_EIF_FLT_MODE . . . . .
KDS_X_TEMS_FRAME_STACK_SIZE . . .
KDS_X_TEMS_LGSA_VERIFY . . . . . .
KDS_X_TEMS_LOGBLOCK_RKLVLOG_SIZE
KDS_X_TEMS_LOGBUFS_RKLVLOG_BUFSZ
KDS_X_TEMS_LSRPOOL_BUFFER_NUMn .
KDS_X_TEMS_LSRPOOL_BUFSIZEn . . .
KDS_X_TEMS_LSRSTRNO_CONCURRENT .
KDS_X_TEMS_SDUMP_SVC_SYS1_DUMP .
KDS_X_TEMS_STORAGE_RESERVE_PRI . .
KDS_X_TEMS_STORAGE_STGDEBUG . . .
KDS_X_TEMS_TASKS_ATTACHED_NUM .
KDS_X_TEMS_WTO . . . . . . . . .
Parameters for the high-availability hub
monitoring server . . . . . . . . . .
KDS_TEMS_HA_TYPE . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
250
250
251
251
252
252
253
254
254
255
256
257
257
.
.
. 258
. 258
KOB_TOM_STC . . . . . . .
KOB_TOM_VTAM_APPL_LOGON .
KOB_TOM_VTAM_NODE . . . .
Documentation library
.
.
.
.
.
.
.
.
.
.
.
.
. 259
. 260
. 261
. . . . . . . 263
IBM Tivoli Monitoring library . .
Documentation for the base agents
Related publications . . . . .
Other sources of documentation .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
263
264
265
265
Support information . . . . . . . . 267
Notices . . . . . . . . . . . . . . 269
Trademarks .
.
.
.
.
.
.
.
.
.
.
.
.
. 270
Glossary . . . . . . . . . . . . . 271
Chapter 6. Enhanced 3270 user
interface (KOB) parameters . . . . . 259
vi
Index . . . . . . . . . . . . . . . 287
About this information
IBM® Tivoli® OMEGAMON® and IBM Tivoli Management Services on z/OS®: Common Parameter Reference
Version 6 Release 2 Modification Level 0 (Version 6.2.0) provides reference information on parameters
used for setting up runtime environments and configuring hub and remote Tivoli Enterprise Monitoring
Servers on z/OS.
This information is for the z/OS systems programmer or analyst who is responsible for installing
applications, automating tasks on the system, monitoring new applications, and providing solutions for
operators when they have problems.
Users of this information should be familiar with the z/OS operating system and its associated concepts,
UNIX System Services, TCP/IP, and performance monitoring concepts.
This edition applies to version 4, release 2 and version 5, release 1 of the IBM Tivoli OMEGAMON XE
products and to version 6, release 2, modification 2 of IBM Tivoli Management Services on z/OS (product
number 5698-A79) and to all subsequent releases and modifications until otherwise indicated in new
editions.
Before using this information and the product it supports, read the information in “Notices” on page 269.
New in this release
The following updates apply to the IBM Tivoli Monitoring Version 6.2.3 Fix Pack 1 update of this book:
v A new $GBL* configuration profile is now available. This addition profile provides a clearer
categorization of GBL-like candidate parmeters and differentiates them from LPAR-candidate
parameters. The content of this configuration file varies, depending on customer deployment practices.
The profiles are called in this order. The LPAR-specific one ($CFG$IBM or the &rte_name) member
takes precedence over the $GBL* configuration profile:
rhilev.midlev.WCONFIG($SYSIN)
v A number of the existing GBL_* parameters that were previously found in the $CFG* configuration file
have been moved to $GBL$IBM/$GBL$USR. The latest version of this file is in
rhilev.midlev.WCONFIG($GBL$IBM).
v IBM Tivoli Monitoring v6.2.3 includes a new auditing facility that provides detailed messages for
certain major state changes or events that occur within the environment (in Tivoli Enterprise Portal
Server, the Tivoli Enterprise Monitoring Server, and the monitoring agents). Audit Events in the system
reflect major and minor state changes, such as authorization and authentication failures, and do not
reflect minor service messages stored in the RAS logs. These audit parameters can be customized for
inclusion in the KDSENV member of the KDCSSITE member of the rhilev.midlev.RKANPARU library
for the monitoring server for monitoring agents on z/OS or by editing the KDSENV values for the
distributed monitoring agents. The following new parameters were added:
– Kpp_AGT_AUDIT_ITM_DOMAIN
– Kpp_AGT_AUDIT_MAX_HIST
– Kpp_AGT_AUDIT_TRACE
– Kpp_AGT_TEMA_SDA
– Kpp_SECURITY_ACTION_CLASS
– KDS_AUDIT_ITM_DOMAIN
– KDS_AUDIT_MAX_HIST
– KDS_AUDIT_TRACE
– KDS_KMS_SDA
– KDS_TEMA_SDA
– KDS_TEMS_DRA_FLAG
vii
– GBL_HFS_JAVA_DIRn
– GBL_DSN_SYS1_SBPXEXEC
– RTE_SECURITY_CLASS
– RTE_USS_RTEDIR
– KOB_TOM_STC
– KOB_TOM_VTAM_APPL_LOGON
– KOB_TOM_VTAM_NODE
v The list of parameters that describe a high-availability hub monitoring server has been enhanced
considerably; the new parameters are:
KDS_KCF_EXT_SECURITY
KDS_KCF_MAX_ERROR
KDS_KCF_SAFCLASS
KDS_KMC_MQ_MAXROWS
KDS_TEMS_HA_INCLUDE_Kpp
KDS_TEMS_HA_TYPE
KDS_TEMS_TCP_KDEB_INTERFACELIST
KDS_TEMS_TYPE
KMC_CFG_AUDIT_FLAG
KMC_CFG_DATABASE_TYPE
KMC_CFG_DB_DB2_DATABASE
KMC_CFG_DB_DB2_NAME
KMC_DEFAULT_RCACFG_NODENAME
KMC_I_CFG_AUDIT_SETTING
KMC_I_KCF_DB2_NAME
KMC_NODENAME
KMC_X_KCF_MAX_ERROR
KMC_X_KMC_MQ_MAXROWS
KMC_X_SECURITY_KCF_SAFCLASS
KMC_X_SECURITY_KCF_EXT_SECURITY
Kpp_AGT_TCP_KDEB_INTERFACELIST
v The OMEGAMON enhanced 3270 user interface has its own set of common configuration parameters,
each of which begins with "KOB". The new KOB parameters are:
– KOB_TOM_STC
– KOB_TOM_VTAM_APPL_LOGON
– KOB_TOM_VTAM_NODE
These parameters are described in a new chapter, Chapter 6, “Enhanced 3270 user interface (KOB)
parameters,” on page 259.
viii
Chapter 1. Overview
This guide provides reference information about the parameters that are used for setting and storing
configuration values for the common components of IBM Tivoli Management Services on z/OS and for
the runtime environments in which the IBM Tivoli OMEGAMON XE monitoring agents are configured.
For agent parameter information, see the documentation for each product.
Changes to this guide since the initial release of Tivoli Management Services on z/OS version 6.2.2, Fix
Pack 2, are marked with revision bars (|) in the left margin of pages in the PDF book.
Where configured parameters are stored
Most configuration parameters and their configured values are stored in the KppENV or KppSYSIN
members of the rhilev.rte.RKANPARU data set for each runtime environment.
Where:
pp
is the 2-character product or component code
rhilev
is the high-level qualifier for the runtime environment data sets
rte
is the runtime environment name, which is used as the mid-level qualifier for the runtime
environment data sets
For information about runtime environments, see the "Planning your deployment" chapter of IBM Tivoli
OMEGAMON XE and Tivoli Management Services on z/OS: Common Planning and Configuration Guide.
The parameters stored in the KppENV member are environment variables, which determine the operating
characteristics of the runtime environment in which products and components are configured. The
parameters stored in the KppSYSIN member are startup parameters, which determine the default startup
values for each product or component.
Some environment variables and startup parameters are stored in members other than KppENV and
KppSYSIN, or in data sets other than RKANPARU. In addition, some parameters that are neither
environment variables nor startup parameters must be included in the runtime libraries for the products
and components.
How parameter values are set
Most parameters are provided with default values that you can accept or change.
Some parameters are included in the runtime libraries by default, and others are excluded by default. You
can set parameter values by either of two basic methods:
v “PARMGEN method” on page 2
v “Configuration Tool (ICAT) method” on page 2
For instructions on using both configuration methods, see IBM Tivoli OMEGAMON XE and Tivoli
Management Services on z/OS: Common Planning and Configuration Guide. If you decide to use the
PARMGEN tool to create or update your site’s runtime environments, you might want to take advantage
of the detailed scenarios in the IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS:
PARMGEN Reference.
1
PARMGEN method
With the PARMGEN configuration method, you edit a comprehensive list of parameters for configuring
all installed products and components. You then submit a series of jobs to create a complete runtime
environment with the parameter values you specified.
The PARMGEN method can be used for creating new runtime environments and for upgrading existing
ones that were created from product versions for which the PARMGEN configuration method was
enabled. To upgrade from a product version lower than the first PARMGEN-enabled version, you must
use the Configuration Tool (ICAT). To determine the lowest PARMGEN-enabled version of each of your
products, see the PARMGEN Technote at http://www.ibm.com/support/docview.wss?uid=swg21417935.
If you have runtime environments that are already configured by the Configuration Tool (ICAT) method,
a conversion tool (the KCIJPCNV job) is provided for using the existing parameter values in those
runtime environments to set up initial values for new runtime environments to be configured by the
PARMGEN method. After you use the PARMGEN method to configure new runtime environments, you
cannot use the Configuration Tool to edit or maintain them.
Configuration Tool (ICAT) method
The Configuration Tool (also called the Installation and Configuration Assistance Tool, or ICAT) is
software provided for configuring the Tivoli Enterprise Monitoring Server and monitoring agents on
z/OS systems.
The Configuration Tool operates in two modes:
v Interactive mode, where an ISPF panel-driven facility assists you in specifying parameters and
tailoring jobs for configuring new products and new versions of products.
v Batch mode, where you create a single batch job that you can use to build, configure, and load a
runtime environment for the Tivoli Enterprise Monitoring Server, monitoring agents, or both. The batch
job performs the same processing as the interactive Configuration Tool. Batch mode is a quick way to
configure your runtime environments and is particularly useful for replicating a configured runtime
environment to other z/OS systems. For details, see the "Batch mode" chapter of IBM Tivoli
OMEGAMON XE and Tivoli Management Services on z/OS: Common Planning and Configuration Guide.
In most cases, you use interactive mode to set parameter values for a runtime environment and for the
products and components in the runtime environment, and then you use batch mode to propagate the
parameter values to other LPARs. (See Part 4, “Replicating configured environments,” and Part 5,
“Configuration and deployment scenarios,” in IBM Tivoli OMEGAMON XE and Tivoli Management Services
on z/OS: Common Planning and Configuration Guide.)
Default values
Some parameters have only one default value, and some have more than one.
For example, TMS:Engine sets this global default value for the “KDS_TEMS_STORAGE_LIMIT_EXTEND”
on page 219 parameter:
LIMIT(16,X)
However, the Configuration Tool panels and PARMGEN files override the TMS:Engine default and show
a different default value for the Tivoli Enterprise Monitoring Server:
LIMIT(23,X)
When you edit a default value on a Configuration Tool panel or in a PARMGEN file, your edited value
overrides the Configuration Tool or PARMGEN default value, which has already overridden the
TMS:Engine default value (if a TMS:Engine default value exists).
2
The default values provided by an individual monitoring agent product often differ from the TMS:Engine
default values, the Tivoli Enterprise Monitoring Server default values, and the default values of other
monitoring agents. Default values for monitoring agents are shown in the Configuration Tool panels,
batch mode data dictionaries, parameter maps (described in IBM Tivoli OMEGAMON XE and Tivoli
Management Services on z/OS: Common Planning and Configuration Guide), and PARMGEN configuration
profiles (also described in IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: Common
Planning and Configuration Guide). These values are also included in the documentation for each
monitoring agent product.
This guide includes information about the default values for runtime environment and Tivoli Enterprise
Monitoring Server parameters.
Parameter names
Most parameters have several different names in the Configuration Tool, in Batch mode, and in
PARMGEN.
Stored parameter name
Name of the parameter as stored in a runtime library. Example: LIMIT
Configuration Tool field name
Name of the field that identifies the parameter on an interactive panel. Example: Maximum storage
request size (extended)
Batch parameter name
Name of the parameter in the batch parameter member. Example: KDS_CMS_EXT_LIM
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.
Certain groups of parameters cannot be set using the Configuration Tool and cannot be updated in your
environment using Batch. Examples include the KN3_X and KON_X parameters, most of which are
stored in either the KN3SYSIN or KONSYSIN member in the rhilev.midlev.rtename.RKANPARU library.
You can set these values using PARMGEN because they are part of the configuration profile. If you
configure your monitoring agent using the Configuration Tool and the default values provided for this
product do no meet your needs, you must modify these values using the Non-Standard Parameter panels
Chapter 1. Overview
3
in the Configuration Tool. Refer to the common configuration guide for information about nonstandard
parameters. If you do not use this method to modify these values, then the values will revert to the
default values when the Configuration Tool is updated.
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
KN3_TCP_SAMP_INTERVAL
KN3_TCP_STACK
KN3_TCP_CON
.
.
** Define TCP monitoring
KN3_TCPX
KN3_TCPX_ROW
KN3_TCPX_SYS_NAME
KN3_TCPX_ADDR_SPACE
KN3_TCPX_PROF_DATASET
KN3_TCPX_OGBL
KN3_TCPX_OSTACK
KN3_TCPX_OTCPC
.
.
**KN3_TCPX_PROF_MEMBER
KN3_TCPX_ROW
KN3_TCPX_SYS_NAME
KN3_TCPX_ADDR_SPACE
KN3_TCPX_PROF_DATASET
KN3_TCPX_OGBL
KN3_TCPX_OSTACK
KN3_TCPX_OTCPC
.
.
KN3_TCPX_PROF_MEMBER
.
.
KN3_TCPX
SYS1.TCPPARMS(TCPDATA)
1
Y
Y
<-- global default
systems member:
BEGIN
* Table begin
$$$$
$$$$$$$$
TCPIP.PROFILE.TCPIP
N
Y
Y
<-- stack specific-default (this is also global)
$$$$
SAMPLESTACK
USER.PARMLIB
Y
Y
Y
<-- stack specific for SAMPLESTACK
SAMPLESTACK
END
<-- End of SAMPLESTACK parameters
<--End of all overrides for all stacks
Therefore, parameters such as KN3_TCPX or KON_TCPX can be set using the Non-Standard Parameters panels
in the Configuration Tool, but do not have Batch names (they are designated "N/A" in this guide). The
Configuration Tool sets these parameters internally unless you set them using the Non-Standard
Parameter panels. You can override the system-defined defaults by editing the stack-specific instance of
the KPPSYSIN file or by using the Non-Standard Parameter Panels, which persist after Configuration
Tool maintenance has been applied.
Determining what products are configured in each runtime
environment
One of the first sections in the configuration profile is the set of flags that define the set of monitoring
agents running in this runtime environment.
These configuration flag statements are in the following format:
4
* Tivoli Enterprise Monitoring Server: KDS flag
CONFIGURE_TEMS_KDS
"Y"
Where the first line, which is commented out, identifies the product or component to be configured and
the second statement is the PARMGEN command to configure the specified product. Specify Y if the
product-specific configuration flag if the product is to be configured in this runtime environment. Specify
N if you do not plan to configure the specified product in this runtime environment. The full set of
configuration flags are found in the table that follows.
Table 1. Master Flags from CONFIGURE_PRODUCTS USER SECTION
Product
Configuration statement (Y or N)
Tivoli Enterprise Monitoring Server
CONFIGURE_TEMS_KDS
IBM Tivoli OMEGAMON XE for CICS on z/OS
CONFIGURE_CICS_KC5
IBM Tivoli OMEGAMON XE for CICS TG on z/OS:
CONFIGURE_CICS_TG_KGW
IBM Tivoli OMEGAMON XE for DB2 PE/PM
CONFIGURE_DB2_AGENT_KD5
IBM Tivoli OMEGAMON XE for IMS on z/OS
CONFIGURE_IMS_KI5
IBM Tivoli OMEGAMON XE on z/OS
CONFIGURE_ZOS_KM5
IBM Tivoli System Automation for z/OS
CONFIGURE_SA_KAH
IBM OMEGAMON z/OS Management Console
CONFIGURE_ZMC_KHL
IBM Tivoli OMEGAMON XE for Messaging - WebSphere MQ
Configuration
CONFIGURE_MESSAGING_KMC
IBM Tivoli OMEGAMON XE for Messaging - WebSphere MQ Monitoring: CONFIGURE_MESSAGING_KMQ
IBM Tivoli OMEGAMON XE for Messaging - WebSphere Message Broker
CONFIGURE_MESSAGING_KQI
IBM Tivoli NetView for z/OS Agent
CONFIGURE_NETVIEW_KNA
IBM Tivoli OMEGAMON XE for Mainframe Networks
CONFIGURE_MFN_KN3
IBM Tivoli OMEGAMON XE for Storage on z/OS
CONFIGURE_STORAGE_KS3
IBM Tivoli OMEGAMON DE on z/OS - OMEGAVIEW and
OMEGAVIEW II
CONFIGURE_OMEGAVIEW_KWO
IBM Tivoli Decision Support for z/OS
CONFIGURE_TDS_KDO
IBM Tivoli Composite Application Manager for SOA
CONFIGURE_SOA_KD4
IBM Tivoli Advanced Audit for DFSMShsm
CONFIGURE_AAD_KRG
IBM Tivoli Advanced Reporting for DFSMShsm
CONFIGURE_ARD_KRH
IBM Tivoli Advanced Allocation Management for z/OS
CONFIGURE_AAM_KRJ
IBM Tivoli Automated Tape Allocation Manager for z/OS
CONFIGURE_ATAM_KRK
IBM Tivoli Advanced Catalog Management for z/OS
CONFIGURE_ACM_KRN
IBM Tivoli Advanced Backup and Recovery for z/OS
CONFIGURE_ABR_KRV
IBM Tivoli Tape Optimizer for z/OS
CONFIGURE_TOZ_KRW
ITCAM for Application Diagnostics on z/OS
CONFIGURE_ITCAMAD_KYN
Parameters covered in this guide
This guide documents several types of parameters:
v Chapter 2, “Common agent (KPP) parameters,” on page 7
The parameters common to all agents had been documented in the OMEGAMON XE for Mainframe
Networks parameter reference guide. The definitions of these parameters have been broadened and
moved to this common location since the parameters are common to all agents configured with
PARMGEN.
Chapter 1. Overview
5
v Chapter 3, “Global (GBL) parameters,” on page 81
The global parameters provide default settings for installation and common system library names.
v Chapter 4, “Runtime environment (RTE) parameters,” on page 107
The runtime environment parameters provide configuration settings for an individual runtime
environment and default settings for the components and products configured in the runtime
environment.
v Chapter 5, “Tivoli Enterprise Monitoring Server (KDS) parameters,” on page 157
The Tivoli Enterprise Monitoring Server parameters provide configuration settings for hub and remote
monitoring servers on z/OS. In addition, the “Parameters for the high-availability hub monitoring
server” on page 258 section of this chapter describes parameters specific to a HA hub TEMS.
v Chapter 6, “Enhanced 3270 user interface (KOB) parameters,” on page 259
The OMEGAMON enhanced 3270 user interface has its own set of common configuration parameters,
each of which begins with "KOB". The KOB parameters are:
– “KOB_TOM_STC” on page 259
– “KOB_TOM_VTAM_APPL_LOGON” on page 260
– “KOB_TOM_VTAM_NODE” on page 261
6
Chapter 2. Common agent (KPP) parameters
The KPP common agent configuration parameters in this section. The definitions for the PP variable are
found in the table that follows. The following The three-letter agent prefixes for the agents are supported
by the PARMGEN configuration method:
Table 2. Common agent parameter prefixes
Agent name
Agent prefixes
IBM Tivoli System Automation for z/OS
KAH
IBM Tivoli OMEGAMON enhanced 3270 user interface
KOB
IBM Tivoli OMEGAMON XE for CICS on z/OS
KOC, KC2, KC5
IBM Tivoli OMEGAMON XE for CICS TG on z/OS
KGW
IBM Tivoli Decision Support for z/OS
KDO
IBM Tivoli Composite Application Manager for SOA
KD4
IBM Tivoli OMEGAMON XE for DB2 PE/PM
KO2, KD2, KD5
IBM OMEGAMON z/OS Management Console
KHL
IBM Tivoli OMEGAMON XE for Messaging - WebSphere KMC
MQ Configuration
IBM Tivoli OMEGAMON XE for Messaging - WebSphere KMQ
MQ Monitoring
IBM Tivoli OMEGAMON XE for Messaging - WebSphere KQI
Message Broker
OMEGAVIEW and OMEGAVIEW II
KMV, KWO
IBM Tivoli OMEGAMON XE on z/OS
KOM, KM2, KM5
IBM Tivoli NetView for z/OS Agent
KNA
IBM Tivoli OMEGAMON XE for Mainframe Networks
KON, KN3
IBM Tivoli Advanced Audit for DFSMShsm
KRG
IBM Tivoli Advanced Reporting for DFSMShsm
KRH
IBM Tivoli Advanced Allocation Management for z/OS
KRJ
IBM Tivoli Automated Tape Allocation Manager for
z/OS
KRK
IBM Tivoli Advanced Catalog Management for z/OS
KRN
IBM Tivoli Advanced Backup and Recovery for z/OS
KRV
IBM Tivoli Tape Optimizer for z/OS
KRW
ITCAM for Application Diagnostics on z/OS
KYN
KPP_AGT_AUDIT_ITM_DOMAIN
This parameter is the audit domain name.
Required or optional
Optional
Location where the parameter value is stored
KppENV member of the rhilev.rte.RKANPARU library for the agent’s runtime environment
7
Parameter name and syntax
ITM_DOMAIN=%Kpp_AGT_AUDIT_ITM_DOMAIN%
Default value
None
Permissible values
Character string, maximum length 32.
In the Configuration Tool (ICAT)
Panel name
Specify Advanced Agent Configuration Values
Panel ID
KAG62P5
Field
z/OS Audit collection values: Domain
Default value
None
Permissible values
Kpp_AGT_AUDIT_ITM_DOMAIN
PARMGEN name
Kpp_AGT_AUDIT_ITM_DOMAIN
Description
This field specifies an identifier that may be used to associate audit records. It is suited for
commonly identifying agents that are associated with each other. An example use may be for
sorting records by a particular customer. This field will also be used to create unique namespaces
for RBAC.
Related parameters
v “KPP_AGT_AUDIT_TRACE” on page 9
v “KPP_AGT_AUDIT_MAX_HIST”
v “KDS_AUDIT_TRACE” on page 158
v “KDS_AUDIT_MAX_HIST” on page 157
v “KDS_AUDIT_ITM_DOMAIN” on page 157
KPP_AGT_AUDIT_MAX_HIST
This parameter specifies the maximum in-memory cache entries; it is the maximum number of records
kept in short-term memory for direct queries.
Optional
The AUDIT_MAX_HIST parameter in the RKANPARU data set, member KPPENV for the agent’s
runtime environment.
AUDIT_MAX_HIST=%Kpp_AGT_AUDIT_MAX_HIST%
Default value
None
8
Permissible values
10–1000
Panel name
Panel ID
KAG62P5
Field
z/OS Audit collection values: Maximum in-memory cache entries
Default value
None
Permissible values
10–1000
Kpp_AGT_AUDIT_MAX_HIST
PARMGEN name
Kpp_AGT_AUDIT_MAX_HIST
Description
The maximum number of records kept in short-term memory for direct queries.
Related parameters
v “KPP_AGT_AUDIT_TRACE”
v “KPP_AGT_AUDIT_ITM_DOMAIN” on page 7
KPP_AGT_AUDIT_TRACE
This parameter indicates the trace level to pass messages.
Optional
KppENV member of the rhilev.rte.RKANPARU library for the agent’s runtime environment.
AUDIT_TRACE=%Kpp_AGT_AUDIT_TRACE%
Default value
None
Permissible values
M, B, D, X
Panel name
Panel ID
KAG62P5
Field
z/OS Audit collection values: Enable/Disable z/OS audit collection
9
Default value
None
Permissible values
M, B, D, X
Kpp_AGT_AUDIT_TRACE
PARMGEN name
Kpp_AGT_AUDIT_TRACE
Description
This indicates the trace level to pass messages. Message trace levels, from low to high, are:
X
disabled
M
minimum
B
basic
D
detail
Higher levels imply all lower levels.
Related parameters
v “KPP_AGT_AUDIT_MAX_HIST” on page 8
v “KPP_AGT_AUDIT_ITM_DOMAIN” on page 7
KPP_AGT_CONFIGURATION_MODE
Use the KPP_AGT_CONFIGURATION_MODE parameter to specify how you want to run the monitoring
agent you are defining, in the agent address space or the server address space.
Required
Location where parameter value is stored
The parameter value is not stored, but is used for internal processing.
Parameter name
N/A
Default value
STANDALONE
Permissible values
One of the following:
v STANDALONE
v CMS
Panel name
CONFIGURE monitoring_agent
Panel ID
KppVVMCU, where VV is the agent-specific panel ID.
Field
10
Configure monitoring_agent
This value is set when you select Option 3 on this panel and complete the resulting set of
panels. If you choose Option 3 then the value for this parameter is set to AGTCMS,
which is strongly recommended for more monitoring agents, (meaning that the agent
runs in its own address space). If you choose PF5 Advanced on Panel KppvvvMCU, then
the value for this parameter will be set to CMS, which means that the agent runs in the
run in the Tivoli Enterprise Monitoring Server (CMS) address space. This value must be
selected for the IBM Tivoli OMEGAMON XE on z/OS monitoring agent and the IBM
Tivoli OMEGAMON XE for Storage on z/OS monitoring agent since these agents run
only in the monitoring server address space.
Default value
No default
Permissible values
One of the following:
v STANDALONE
v CMS
v AGTCMS
KPP_AGT_CONFIG
PARMGEN name
KPP_AGT_CONFIGURATION_MODE
PARMGEN classification
Values that describe the address space
Description
Agent configuration option
This parameter specifies how you want to run the monitoring agent you are defining.
When defining an agent, you have the option to run the agent in an agent address space or in the
server address space. For performance reasons, you should run the agent in an agent address
space. If you plan to run the agent in the server address space, the runtime environment must
contain a server.
To run the agent in an agent address space, choose Option 3 (AGTCMS) in the Configuration
Tool, which is the preferred configuration or specify STANDALONE in PARMGEN. Otherwise,
by choosing PF5 Advanced from the KPPVVMCU panel (the monitoring_agent’s main menu
panel), you specify CMS in the Configuration Tool or TEMS in PARMGEN to run the agent in the
server. The procedures outlined in the product-specific planning and configuration guide assumes
that you are running the recommended configuration for this agent, which is running in the
agent address space.
Related parameters
None
KPP_AGT_COMM_PROTOCOLn
Use the KPP_AGT_COMM_PROTOCOLn parameter to specify the communication protocol for the TEMS
connection. Valid values are IPPIPE, IP, SNA, IP6PIPE, IP6, IPSPIPE, and IP6SPIPE. When communication
with the TEMS is initiated, the agent first tries protocol 1, then goes to protocol 2, and so on, in case of
failure.
Note: Update the corresponding Kpp_TEMS_TCP_*_PORT_NUM parameter for each
Kpp_AGT_COMM_PROTOCOLx parameter enabled. For example, if Kpp_AGT_COMM_PROTOCOL1="IPPIPE",
set the corresponding Kpp_TEMS_TCP_PIPE_PORT_NUM parameter. If Kpp_TEMS_COMM_PROTOCOL2="IP"
(for IP.UDP), set the corresponding Kpp_TEMS_TCP_UDP_PORT_NUM parameter.
11
Required
In the KPPENV member of the rhilev.rtename.RKANPARU library
Parameter name
N/A
Default value
None
Permissible values
IP.PIPE, IP.UDP, IP6.PIPE, IP6.UDP, IP.SPIPE, IP6.SPIPE, and SNA.PIPE
Panel name
SPECIFY AGENT ADDRESS SPACE PARAMETERS
Panel ID
KAG62P2
Field
Specify the communication protocols in priority sequence.
v IP.PIPE
v IP.UDP
v IP6.PIPE
v IP6.UDP
v IP.SPIPE
v IP6.SPIPE
v SNA.PIPE
Example:
KDE_TRANSPORT=\
HTTP:1920\
IP6.PIPE PORT:1918 USE:N\
IP6.UDP PORT:1918 USE:N\
IP.SPIPE PORT:3660 USE:N\
IP6.SPIPE PORT:3660 USE:N\
IP.PIPE PORT:1918\
IP.UDP PORT:1918\
SNA.PIPE PORT:135
Default value
None
Permissible values
1-7
KPP_AGT_COMM_PROn
PARMGEN name
KPP_AGT_COMM_PROTOCOLn
Specify communication protocols preference for TEMS connection
Description
Agent Communication protocol n
This parameter specifies the communication protocol to be supported by the monitoring agent,
where n corresponds to a number between 1 and 7 to indicate the priority sequence for the
communication protocols.
12
In the Configuration Tool (ICAT), the seven fields corresponding to the communication protocols
that can be supported are shown, and you can set the priority sequence for these protocols by
assigning each field a value from 1 to 7, with 1 as the highest priority and 7 as the lowest. Leave
blank any fields that represent unsupported communication protocols.
The protocols, both supported and unsupported, are listed along with assigned port numbers in
the KPPENV member, as shown in the Example section. Unused protocols are indicated by USE:N.
Supported protocols are listed in priority order.
Related parameters
None
KPP_AGT_FLUSH_LSR_BUFR_INT_HR
Use the KPP_AGT_FLUSH_LSR_BUFR_INT_HR parameter to specify the interval to force all deferred
VSAM writes to DASD.
Required
In the KPPAGST member in the rhilev.midlev.rtename.RKANCMDU library
Parameter name
EVERY HH:MM:SS FLUSH (Flush VSAM buffers interval - hours)
Default value
0 hours, 30 minutes
Permissible values
0 - 24
Panel name
Panel ID
KAG62P5
Field
Flush VSAM buffers: Hours
Default value
0 hours, 30 minutes, 0 seconds (seconds is not configurable)
Permissible values
0 - 24
KPP_AGT_FLUSH_INT_HR
PARMGEN name
KPP_AGT_FLUSH_LSR_BUFR_INT_HR
Advanced Agent configuration values
Description
Flush VSAM buffers interval - hours
This parameter specifies the interval to force all deferred VSAM writes to DASD. The interval
values are written as part of the third EVERY command in the KPPAGST member in the
rhilev.midlev.rtename.RKANCMDU library. The default is 0 hours (hh) and 30 minutes (mm).
13
Related parameters
None
KPP_AGT_FLUSH_LSR_BUFR_INT_MIN
Use the KPP_AGT_FLUSH_LSR_BUFR_INT_MIN parameter to specify the interval to force all deferred
VSAM writes to DASD.
Required
In the KPPAGST member in the rhilev.midlev.rtename.RKANCMDU library
Parameter name
EVERY HH:MM:SS FLUSH (Flush VSAM buffers interval - mins)
Default value
0 hours 30 minutes
Permissible values
0 - 60
Panel name
Panel ID
KAG62P5
Field
Flush VSAM buffers: Minutes
Default value
0 hours 30 minutes 0 seconds (seconds is not configurable)
Permissible values
0 - 60
KPP_AGT_FLUSH_INT_MIN
PARMGEN name
KPP_AGT_FLUSH_LSR_BUFR_INT_MIN
Description
Flush VSAM buffers interval - mins
This parameter specifies the interval to force all deferred VSAM writes to DASD. The interval
values are written as part of the third EVERY command in:
rhilev.midlev.rtename.RKANCMDU(KPPAGST) The default is 0 hours (hh) and 30 minutes (mm).
Related parameters
None
KPP_AGT_ICU_LANGUAGE_LOCALE
Use the KPP_AGT_ICU_LANGUAGE_LOCALE parameter to specify the language and codeset (system's
locale) that you want the monitoring agent to use.
Required
14
Generated in the KPPENV member in the rhilev.midlev.rtename.RKANPARU library
Parameter name
LANG= (Language locale of z/OS system)
Panel name
Panel ID
KAG62P5
Field
Language locale
Default value
1 (English - United States)
Permissible values
v 1 (English - United States)
v 2 (English - United Kingdom)
v 3 (German - Germany)
v 4 (German - Switzerland)
v 5 (French - Belgium)
v 6 (French - France)
v 7 (French - Switzerland)
v 8 (Spanish - Spain)
v 9 (Italian - Italy)
v 10 (Portuguese - Portugal)
v 11 (Portuguese - Brazil)
v 12 (Norwegian - Norway)
v 13 (Swedish - Sweden)
v 14 (Danish - Denmark)
v 15 (Finnish - Finland)
v 16 (Japanese - Japan)
v 17 (French - Canada)
v 18 (Traditional Chinese - Taiwan)
v 19 (Simplified Chinese - China)
v 20 (Albanian - Albania)
v 21 (Bulgarian - Bulgaria)
v 22 (Czech - Slovenia)
v 23 (Dutch - Belgium)
v 24 (Dutch - Netherlands)
v 25 (Greek - Greece)
v 26 (Hebrew - Israel)
v 27 (Korean - Korea)
v 28 (Lithuanian - Lithuania)
v 29 (Macedonian - Macedonia)
v 30 (Romanian - Romania)
v 31 (Russian - Russia)
v 32 (Serbian - Serbia)
v 33 (Slovak - Slovakia)
v 34 (Slovenian - Slovenia)
v 35 (Thai - Thailand)
v 36 (Turkish - Turkey)
KPP_AGT_ICU_LANG
15
PARMGEN name
Description
Language and region for the z/OS system.
This parameter specifies the language and codeset (system's locale) that you want the monitoring
agent to use. The language locale value is used for National Language support. This field requires
the numeric value (1-36) representing the Language and Region in the table below. As an
example, specify 1 for "English - United States". The country and character set that this language
represents (for example, country is en_US and character set is ibm-037) make up the LANG=
environmental variable value generated in the KPPENV member in the
rhilev.midlev.rtename.RKANPARU library. For English - United States, LANG=en_US.ibm-037 is
generated in KPPENV.
From the Configuration Tool panel, press F1 (Help) and select Language locale for a list of the
possible values. If you accept the default value of 1 (English - United States), the
Configuration Tool generates this environment variable in KPPENV:
LANG=en_US.ibm-037
If the z/OS UNIX System Services (USS) codepage (en_US.ibm-1047) is required, you can specify
either en_US.ibm-1047 or 1A in the Language locale field on the Configuration Tool panel. In batch
mode, you can specify either of these values:
KPP_AGT_ICU_LANG
KPP_AGT_ICU_LANG
en_US.ibm-1047
1
In PARMGEN mode, you can specify either of these values for the USS codepage:
en_US.ibm-1047
The USS codepage (en_US.ibm-1047) is required for agent autonomy and for private situation
XML files.
Related parameters
None
KPP_AGT_KGL_WTO
Use the KPP_AGT_KGL_WTO parameter to activate write-to-operator messages for a particular agent.
Required
In the KPPENV member of the rhilev.midlev.rtename.RKANPARU library
Parameter name
KGL_WTO= (Enable agent WTO messages)
Default value
YES
Permissible values
YES or NO
Panel name
Specify Agent Advanced Configuration Values
16
Panel ID
KAG62P5
Field
Enable startup console messages
Default value
N
Permissible values
Y, N
KPP_AGT_KGL_WTO
PARMGEN name
KPP_AGT_KGL_WTO
Description
Enable agent WTO messages
Specify Y to this parameter if you want a SYSLOG message on the console to indicate when the
monitoring agent finishes initializing. You can use this message in an automation script. See the
automation package for your site for further instructions on how to capture the monitoring agent
startup automation message IDs. If you specify Y, the KGL_WTO=YES parameter is added to the
rhilev.midlev.rtename.RKANPARU(KPPENV) member. The default is N for the Configuration Tool
and YES for PARMGEN.
Note: The existence of the KGL_WTO= parameter triggers the startup console messages.
Therefore this parameter must not be present in the KPPENV member if you do not want this
feature enabled. When it is enabled after configuration, the parameter is added to the KPPENV
member. If you want to turn it off again, you must regenerate the Configuration Tool PP#3xxx job
created in the monitoring agent "Create runtime members" step to refresh PP3ENV, where xxx is
the JCL suffix. If you configured using PARMGEN, you can edit the configuration profile and
recycle the monitoring agent.
Related parameters
None
Use the KPP_AGT_KLX_TCP_TOLERATERECYCLE parameter to determine whether the monitoring
agent address space reconnects to its TCP/IP stack without being recycled after the stack is recycled.
Optional
In the KPPINTCP member of the rhilev.midlev.rtename.RKANPARU library
Parameter name
TCP/IP_USERID=’&tcpip_stc’ TOLERATERECYCLE
Default value
N
Permissible values
Y, N
17
Panel name
Panel ID
KAG62P5
Field
Reconnect after TCP/IP recycle
KPP_AGT_KLX_TCP_RECYCLE
PARMGEN name
Description
The parameter determines whether the monitoring agent address space reconnects to its TCP/IP
stack without being recycled after the stack is recycled. Set this parameter to Y to allow the
monitoring agent address space to reconnect to the z/OS Communications Server without having
to subsequently recycle the address space. When this parameter is set to Y, the
"TOLERATERECYCLE" keyword is added in the KPPINTCP member of the RKANPARU library.
The parameter line is generated as: TCP/IP_USERID=&tcp_userid TOLERATERECYCLE.
If this parameter is set to N, when the z/OS Communications Server is recycled,
the monitoring agent address space must also be recycled to establish connectivity to TCP/IP. The
default is N for the Configuration Tool and TOLERATERECYCLE (meaning yes) for PARMGEN.
Note: This parameter may be specified only when the monitoring agent is reporting to Tivoli
Enterprise Monitoring Server V6.2.0 and later versions.
Related parameters
None
KPP_AGT_NSNEWn_VALUE
The KPP_AGT_NSNEWn_VALUE parameter specifies the value for a nonstandard parameter (a
parameter that is not presented in a Configuration Tool interactive panel).
Optional
Attention: Use extreme caution in specifying nonstandard parameters. No error-checking is
provided at present. Syntax is not validated. The presence of the data set and member specified is
not validated. If faulty syntax or other errors cause your edits to fail, no warning or error
message is issued. Use this facility only under the guidance of IBM Software Support.
Data set, member, and parameter specified in the “KPP_AGT_NONSTDn_MBR” on page 20,
“KPP_AGT_NONSTDn_DSN” on page 19, and “KPP_AGT_NONSTDn_PARM” on page 21
parameters, respectively.
Panel name
Specify Nonstandard Parameters
Panel ID
KAGPNSTn
18
Field
New Value
Default value
None
Permissible values
Character string, maximum length 50
KPP_NSNEWn_VALUE
Description
Value for a nonstandard parameter (a parameter that is not presented in a Configuration Tool
interactive panel). In specifying the value, be sure to include format characters. For example, if
the format in the runtime member is parameter=value, precede the value with an equal sign; or if
the format is parameter(value), surround the value with parentheses. If you want to delete an
existing parameter that is specified in “KPP_AGT_NONSTDn_PARM” on page 21, leave the value
of the corresponding KPP_NSNEWnn_VALUE parameter blank.
Each KPP_NSNEWnn_VALUE parameter has a unique name, in which nn represents a number
between 1 and 6, corresponding to the number set for “KPP_AGT_NONSTDn_PARM” on page
21.
For more information about specifying nonstandard parameters, see the "Parameters" section of
the IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: Common Planning and
Configuration Guide.
Related parameters
v “KPP_AGT_NONSTDn_DSN”
v “KPP_AGT_NONSTDn_MBR” on page 20
v “KPP_AGT_NONSTDn_PARM” on page 21
KPP_AGT_NONSTDn_DSN
The KPP_AGT_NONSTDn_DSN parameter specifies the low-level qualifier of the data set containing the
member with the parameter to be added, replaced, or deleted by specifying a nonstandard parameter (a
parameter that is not presented in a Configuration Tool interactive panel).
Optional
Member specified in the “KPP_AGT_NONSTDn_MBR” on page 20 parameter
Panel name
Panel ID
KAGPNSTn
Field
Low-level dataset qualifier
Default value
None
19
Permissible values
KPP_AGT_NONSTDn_DSN
Description
This parameter specifies the low-level qualifier of the data set containing the member with the
parameter to be added, replaced, or deleted by specifying a nonstandard parameter (a parameter
that is not presented in a Configuration Tool interactive panel). Each
“KPP_AGT_NONSTDn_DSN” on page 19 parameter has a unique name, in which n represents a
number between 1 and 6, corresponding to the number set for “KPP_AGT_NONSTDn_PARM”
on page 21.
Related parameters
None
KPP_AGT_NONSTDn_MBR
The KPP_AGT_NONSTDn_MBR parameter specifies the name of the name of the
KPP_AGT_NONSTDn_DSN data set member that contains the parameter to be added, replaced, or
deleted by specifying a nonstandard parameter (a parameter that is not presented in a Configuration Tool
interactive panel).
Optional
Member specified in this parameter, in the data set specified in the “KPP_AGT_NONSTDn_DSN”
on page 19 parameter
Panel name
Panel ID
KAGPNSTn
Field
Member
Default value
None
Permissible values
KPP_NONSTDnn_MBR
Description
Name of the “KPP_AGT_NONSTDn_DSN” on page 19 data set member that contains the
20
parameter to be added, replaced, or deleted by specifying a nonstandard parameter (a parameter
that is not presented in a Configuration Tool interactive panel). The asterisk (*) wildcard character
can be used as a suffix in column 4, 5, 6, 7, or 8 of the member name (provided that column is
the final one in the name).
Each KPP_NONSTDnn_MBR parameter has a unique name, in which nn represents a number
between 1 and 6, corresponding to the number set for “KPP_AGT_NONSTDn_PARM.”
Related parameters
None
KPP_AGT_NONSTDn_PARM
The KPP_AGT_NONSTDn_PARM parameter specifies the name of the configuration parameter to be
added, replaced, or deleted.
Optional
Data set and member specified in the “KPP_AGT_NONSTDn_MBR” on page 20 and
“KPP_AGT_NONSTDn_DSN” on page 19 parameters, respectively
Panel name
Panel ID
KAGPNSTn
Field
Parameter
Default value
None
Permissible values
KPP_AGT_NONSTDn_PARM
Description
Name of the configuration parameter to be added, replaced, or deleted. You can specify up to 6
nonstandard parameters (parameters that are not presented in the Configuration Tool interactive
panels). Each nonstandard parameter has a unique name in which nn represents a number
between 1 and 6.
21
Related parameters
None
KPP_AGT_NSOLDn_VALUE
The KPP_AGT_NSOLDn_VALUE parameter specifies the existing value to be replaced or deleted in the
parameter definition corresponding to KPP_AGT_NONSTDN_PARM.
Optional
Replaced in the data set, member, and parameter specified in the “KPP_AGT_NONSTDn_MBR”
on page 20, “KPP_AGT_NONSTDn_DSN” on page 19, and “KPP_AGT_NONSTDn_PARM” on
page 21 parameters, respectively.
Panel name
Panel ID
KAGPNSTn
Field
Old Value (if replacing)
Default value
None
Permissible values
KPP_AGT_NSOLDn_VALUE
Description
Existing value to be replaced or deleted in the parameter definition corresponding to
“KPP_AGT_NONSTDn_PARM” on page 21. The character string that you specify must match
exactly the existing value for the parameter in the runtime member, or the value is not replaced.
For example, if the format in the runtime member is parameter=value, precede the value with an
equal sign; or if the format is parameter(value), surround the value with parentheses.
Each KPP_NSOLDnn_VALUE parameter has a unique name, in which nn represents a number
between 1 and 6, corresponding to the number set for “KPP_AGT_NONSTDn_PARM” on page
21.
Related parameters
“KPP_AGT_NONSTDn_PARM” on page 21
KPP_AGT_PARTITION_NAME
The KPP_AGT_PARTITION_NAME parameter specifies the partition name that identifies the location of
this monitoring server (TEMS namespace) relative to the firewalls used for address translation.
22
Optional
Parameter name
KDC_PARTITION= (Agent IP.PIPE partition name)
Default value
None
Permissible values
Panel name
SPECIFY AGENT IP.PIPE CONFIGURATION VALUES
Panel ID
KAG62P2C
Field
Partition name
Default value
None
Permissible values
KPP_AGT_PIPE_NAME
PARMGEN name
KPP_AGT_PARTITION_NAME
If the Agent requires address translation support
Description
Agent IP.PIPE partition name
This parameter specifies the partition name that identifies the location of this monitoring server
(TEMS namespace) relative to the firewalls used for address translation.
Note: The Tivoli Enterprise Monitoring Server that this monitoring agent connects to must have a
corresponding partition reference entry.
This parameter is put into the partition table that contains labels and associated socket addresses
that are provided by the firewall administrator.
The labels in the partition table are configured into and used by IBM products on an external
network, outside a firewall, during the Tivoli Enterprise Monitoring Server (TEMS) connection
establishment phase. The first part of this connection establishment is the lb lookup, which
requires that the location brokers return the socket address of the monitoring agent.
The partition table is used by the brokers, matching a partition name for a client to the labels in
the partition table. On a match, the associated socket address in the partition table is returned to
the client outside the firewall. This socket address is used by the IBM products to traverse the
firewall and connect to the monitoring server.
Each entry consists of a label or partition name, a protocol (IP for UDP or IP.PIPE for TCP), and a
host name or dotted-decimal IP address. The well-known port (Hub port) must be authorized by
the firewall administrator.
23
v If UDP is the protocol configured in the partition table, then a range of (UDP) ports must be
authorized by the firewall administrator (in addition to the well-known port).
v If TCP is the protocol, no additional ports other than the well-known TEMS port need be
authorized.
Related parameters
None
KPP_AGT_PPI_RECEIVER
The KPP_AGT_PPI_RECEIVER parameter specifies the Program-to-Program Interface (PPI) values that
enable the monitoring agent to forward Take Action commands to IBM Tivoli NetView® for z/OS V5.2, or
later.
Required if the monitoring agent will be forwarding Take Action commands to the IBM Tivoli
NetView for z/OS Program-to-Program Interface (PPI).
Parameter name
KGLHC_PPI_RECEIVER= (NetView for z/OS PPI receiver)
Default value
This value defaults to the IBM Tivoli NetView for z/OS PPI receiver used by the server if
one is configured in this RTE. Otherwise, specify the default of CNMPCMDR.
Permissible values
Panel name
Panel ID
KAG62P5
Field
NetView PPI receiver
Default value
This value defaults to the IBM Tivoli NetView for z/OS PPI receiver used by the server if
one is configured in this RTE. Otherwise, specify the default of CNMPCMDR.
Permissible values
PARMGEN name
Take Action commands security settings
Description
NetView for z/OS PPI receiver
The parameter specifies the Program to Program Interface (PPI) values that enable the monitoring
agent to forward Take Action commands to IBM Tivoli NetView for z/OS V5.2, or later. The
Tivoli Enterprise Portal user ID is passed to Tivoli NetView for z/OS.
24
Specify the name of the PPI receiver on IBM Tivoli NetView for z/OS that will receive Take
Action commands. If the specified name is invalid or the receiver is not active on Tivoli NetView
for z/OS, default (MGCR) command routing is performed. The value should be a 1-8 character,
unique identifier for the receiver program. It can contain alphabetic characters A-Z or a-z,
numeric characters 0-9, and the following special characters:
v dollar sign ($)
v percent sign (%)
v ampersand (&)
v number sign (#)
This value must match the xyz value coded on statement AUTOTASK.?APSERV.InitCmd = APSERV
xyz" in the Tivoli NetView DSIPARM initialization member, CNMSTYLE. The Configuration Tool
generates the KGLHC_PPI_RECEIVER parameter in the KPPENV member of the
rhilev.midlev.rtename.RKANPARU library. This value defaults to the Tivoli NetView for z/OS PPI
receiver used by the Server if one is configured in this RTE. Otherwise, specify the default of
CNMPCMDR. See the Tivoli NetView for z/OS online help for command APSERV for more
details.
To enable this function, specify a value on the KPP_AGT_PPI_RECEIVER parameter. Ensure that
the parameter is not commented out and the value is enclosed in double quotation marks (""). To
disable this function, simply comment out the parameter with asterisks ('**').
For complete instructions, see the "Configuring NetView authorization of z/OS commands"
section of IBM Tivoli Monitoring: Configured Tivoli Enterprise Monitoring Server on z/OS.
Related parameters
None
KPP_AGT_PPI_SENDER
The KPP_AGT_PPI_SENDER parameter specifies the Program-to-Program Interface (PPI) values that
enable the monitoring agent to forward Take Action commands to IBM Tivoli NetView for z/OS V5.2, or
later.
Required if the monitoring agent will be forwarding Take Action commands to the IBM Tivoli
NetView for z/OS Program-to-Program Interface (PPI).
Parameter name
KGLHC_PPI_SENDER (Agent PPI sender)
Default value
None
Permissible values
Panel name
Panel ID
KAG62P5
Field
Agent PPI sender
Default value
None
25
Permissible values
KPP_AGT_PPI_SENDER
PARMGEN name
KPP_AGT_PPI_SENDER
Description
Agent PPI sender
The parameter specifies the Program to Program Interface (PPI) values that enable the monitoring
agent to forward Take Action commands to IBM Tivoli NetView for z/OS V5.2, or later. The
Tivoli Enterprise Portal user ID gets passed to IBM Tivoli NetView for z/OS.
Specify the optional name of the PPI sender. The value should be a 1-8 character, unique
identifier for the sender program. It can contain alphabetic characters A-Z or a-z, numeric
characters 0-9, and the following special characters: dollar sign ('$'), percent sign ('%'), ampersand
('&'), at sign ('@'), and number sign ('#'). This name should not conflict with any NetView for
z/OS domain name, as it is used in logging the command and command response in the
NetView for z/OS log. If a value is specified on this field, the Configuration Tool generates the
KGLHC_PPI_SENDER parameter in the KPPENV member of the
rhilev.midlev.rtename.RKANPARU library. If a value is not specified on this field, the default is the
current monitoring agent jobname that is the source of the command.
section of IBM Tivoli Monitoring: Configured Tivoli Enterprise Monitoring Server on z/OS.
Related parameters
None
KPP_AGT_STC
Use the KPP_AGT_STC parameter to specify the started task name for the agent.
Required if you configure the monitoring agent in its own address space
Value becomes the name of the monitoring agent started task procedure member in the
rhilev.midlev.rtename.RKANSAMU library for stand-alone agents.
Parameter name
N/A
Default value
CANSPP
Permissible values
Panel name
Panel ID
KAG62P2
Field
26
Agent started task
Default value
CANSPP
Permissible values
KPP_AGT_STC
PARMGEN name
KPP_AGT_STC
Description
Agent started task name
This parameter specifies the started task name for the agent. This started task must be copied to
your system procedure library. The default is CANSPP.
The Configuration Tool created started task procedures in rhilev.midlev.rtename.RKANSAMU that
you must copy to your started task library. If you have configured an agent address space, copy
the monitoring agent started task (the default name is CANSPP) from
rhilev.midlev.rtename.RKANSAMU to your started task library (PROCLIB). If you have configured
the agent in the TEMS address space, then the TEMS started task procedure will be updated in
rhilev.midlev.rtename.RKANSAMU (the default name is CANSDSST) and this started task must be
copied to your started task library (PROCLIB).
Note: You might also use the sample system copy JCL to copy the system procedures and the
VTAM major node members from the rhilev.midlev.rtename.RKANSAMU library to the system
libraries (if applicable). The sample JCL can be generated from the RTE Utility option using the
Configuration Tool.
See the "Copy the started task procedures to your procedure library" task in the agent-specific
planning and configuration guide for more information.
Related parameters
None
KPP_AGT_STORAGE_DETAIL_INT_HR
Use the KPP_AGT_STORAGE_DETAIL_INT_HR parameter to set the interval to monitor storage.
Required
Part of the second EVERY command in the KPPAGST member of the
rhilev.midlev.rtename.RKANCMDU library
Parameter name
EVERY HH:MM:SS STORAGE D (Storage detail logging interval - hours)
Default value
0
Permissible values
0 - 24
27
Panel name
Panel ID
KAG62P5
Field
Storage detail logging: Hours
Default value
0
Permissible values
0 - 24
KPP_AGT_STOR_DTL_INT_HR
PARMGEN name
KPP_AGT_STORAGE_DETAIL_INT_HR
Description
Storage detail logging interval - hours
This parameters sets the interval to monitor storage. The interval values are written as part of the
second EVERY command in: rhilev.midlev.rtename.RKANCMDU(KPPAGST) The default is 0 hours
(hh) and 60 minutes (mm).
Related parameters
None
KPP_AGT_STORAGE_DETAIL_INT_MIN
Use the KPP_AGT_STORAGE_DETAIL_INT_MIN parameter to set the interval to monitor storage.
Required
Part of the second EVERY command in the KPPAGST member of the
rhilev.midlev.rtename.RKANCMDU library
Parameter name
EVERY HH:MM:SS STORAGE D (Storage detail logging interval - minutes)
Default value
60
Permissible values
0 - 60
Panel name
Panel ID
KAG62P5
Field
Storage detail logging: Minutes
Default value
60
28
Permissible values
0 - 60
KPP_AGT_STOR_DTL_INT_MIN
PARMGEN name
KPP_AGT_STORAGE_DETAIL_INT_MIN
Description
Storage detail logging interval - minutes
This parameters sets the interval to monitor storage. The interval values are written as part of the
second EVERY command in: rhilev.midlev.rtename.RKANCMDU(KPPAGST) The default is 0 hours
(hh) and 60 minutes (mm).
Related parameters
None
Use the KPP_AGT_STORAGE_MINIMUM_EXTEND parameter to specify the amount of virtual storage
the monitoring agent must acquire to run at your site.
Required
In the KPPSYSIN member of the rhilev.midlev.rtename.RKANPARU library
Parameter name
MINIMUM (256000,X) (Minimum extended storage)
Default value
256000
Permissible values
0 - 9999999
Panel name
Panel ID
KAG62P5
Field
Minimum extended storage
Default value
256000
Permissible values
0 - 9999999
KPP_AGT_STOR_MIN_EXT
PARMGEN name
29
Description
This parameter specifies the amount of virtual storage the monitoring agent must acquire to run
at your site. The default is 256000.
Related parameters
None
KPP_AGT_TCP_HOST
Use the KPP_AGT_TCP_HOST parameter to specify the hostname of the system that the agent is running
on.
Optional. This field is required if you plan to have this agent communicate with Tivoli Enterprise
Monitoring Server using TCP/IP.
KDCSSITE member of the rhilev.midlev.rtename.RKANPARU library
Parameter name
N/A
Default value
Value set for the RTE_TCP_HOST parameter for the runtime environment
Permissible values
Panel name
v SPECIFY AGENT IP.UDP CONFIGURATION VALUES (KAG62P2B)
v SPECIFY AGENT IP.PIPE CONFIGURATION VALUES (KAG62P2C)
Panel ID
v KAG62P2B (IP.UDP)
v KAG62P2C (IP.PIPE)
Field
Network address (Hostname):
Default value
Permissible values
KPP_AGT_TCP_HOST
PARMGEN name
KPP_AGT_TCP_HOST
Agent's local TCP/IP information
Description
Agent TCP/IP hostname
30
This parameter specifies the hostname of the system that the agent is running on. This value is
the TCP/IP host name or dotted decimal IP address of the z/OS system where the hub
monitoring server is installed.
To obtain the host name or IP address, enter TSO HOMETEST at the command line. If the z/OS
domain name resolver configuration specifies a search path that includes the target domain suffix,
specify only the first qualifier of the host name. (Example: sys is the first qualifier of the fully
qualified host name sys.ibm.com.) Otherwise, specify the fully qualified host name.
This field is required if you plan to have this agent communicate with the server using TCP/IP.
Related parameters
None
KPP_AGT_TCP_KDEB_INTERFACELIST
Use the KPP_AGT_TCP_KDEB_INTERFACELIST parameter to specify a list of network interfaces you
want the monitoring agent to use. If the agent requires network interface list support and your site runs
more than one TCP/IP interface or network adapter on the same z/OS image, you can specify network
interfaces to be used by monitoring servers and monitoring agents running on a z/OS system. You
specify the network interfaces in the IP communication protocol parameters for each component.
Note: Specify !* as the value if this agent runs on the same candidate z/OS image where a High
Availability (HA) Hub TEMS is running.
Optional
KDEB_INTERFACELIST=%KPP_AGT_TCP_KDEB_INTERFACELIST
Default value
None
Permissible values
Panel name
Panel ID
v KAG62P2B (for IP.UDP)
v KAG62P2C (for IP.PIPE)
Field
Network interface list
Default value
None
Permissible values
KPP_AGT_TCP_KDEBLST
PARMGEN name
KPP_AGT_TCP_KDEB_INTERFACELIST
31
If the Agent requires network interface list support
Description
TCP/IP network interface list
This parameter specifies a list of network interfaces you want the monitoring agent to use. This
parameter is required for sites that are running multiple TCP/IP interfaces or network adapters
on the same z/OS image.
Setting this parameter allows you to direct the monitoring agent to connect to a specific TCP/IP
local interface. Specify the network adapters as one or more of the following values:
v A fully-qualified hostname, for example sys.ibm.com
v The first qualifier of the fully-qualified hostname, for example sys from sys.ibm.com
v An IPv4 address in dotted decimal notation, for example 9.67.1.100
If your site supports DNS, you can enter the short hostname or an IP address. If your site does
not support DNS, you must enter the fully qualified hostname. This field is only applicable for
networks with multiple interface cards for which a specific output network interface list is
required.
If an interface address or a list of interface addresses is specified, the Configuration Tool
generates the KDEB_INTERFACELIST parameter in the KPPENV member of the
rhilev.midlev.rtename.RKANPARU library.
Note: This value defaults to the IPv4 network interface list setting used by the Tivoli Enterprise
Monitoring Server if one is configured in this IPL16 RTE. Also, separate the entries using a blank
space between interface addresses. For example:
==> 129.0.131.214 SYS1 SYS.IBM.COM
In addition, special considerations apply when specifying !<&value> or * for this field. Type
README COM on the command line when you are in the Configuration Tool to see more information
about network interface list considerations and usage.
Related parameters
v “KDS_TEMS_TYPE” on page 232
v “KDS_TEMS_HA_TYPE” on page 206
v “KDS_TEMS_TCP_KDEB_INTERFACELIST” on page 222
KPP_AGT_TCP_STC
Use the KPP_AGT_TCP_STC parameter to specify the name of the TCP/IP started task running on the
monitoring agent host.
Optional. Required if you plan to have this agent communicate with Tivoli Enterprise Monitoring
Server using TCP/IP.
In the KPPINTCP member of the rhilev.midlev.rtename.RKANPARU library
Parameter name
TCP/IP_USERID=’*’ (TCP/IP started task)
Default value
*
Permissible values
32
Panel name
Panel ID
v KAG62P2B (IP.UDP)
v KAG62P2C (IP.PIPE)
Field
Started task
Default value
*
Permissible values
KPP_AGT_TCP_STC
PARMGEN name
KPP_AGT_TCP_STC
Description
TCP/IP started task
This parameter specifies the name of the TCP/IP started task running on the monitoring agent
host. This a required field if you plan to have this agent communicate with the server using
TCP/IP.
This parameter identifies the TCP/IP stack to be used. If the LPAR contains a single TCP/IP
stack, accept the default value of an asterisk (*), which uses the first TCP/IP stack that was
started. If the LPAR contains more than one TCP/IP stack, specify the started task name of the
TCP/IP stack you want to use.
Alternatively, you can specify the number sign (#), which is translated to a blank and allows the
TCP/IP environment to choose the stack to use, either through TCP/IP definitions or through the
use of the SYSTCPD DD statement.
Whichever method is used to select a TCP/IP stack in a multi-stack environment, the Tivoli
Management Services components continue to use that stack, even if a different stack becomes
the primary stack. Therefore, in a multi-stack environment, it is best to specify the started task
name of the TCP/IP stack to be used, rather than specifying a wildcard or a blank.
Related PARMGEN CONFIG profile parameters
v “GBL_DSN_TCP_SYSTCPD_TCPDATA” on page 101
v “KDS_X_STC_SYSTCPD_INCLUDE_FLAG” on page 245
KPP_AGT_TEMA_SDA
This parameter indicates whether the agent has enabled the self-describing agent (SDA) function in the
Required
KppENV member of the rhilev.rte.RKANPARU library for the agent’s runtime environment.
33
TEMA_SDA=%Kpp_AGT_TEMA_SDA%
Default value
Y
Permissible values
Y, N
Panel name
Panel ID
KAG62P5
Field
Enable Self-Describing Agent processing
Default value
Y
Permissible values
Y, N
Kpp_AGT_TEMA_SDA
PARMGEN name
Kpp_AGT_TEMA_SDA
Description
This parameter indicates whether the agent has enabled the self-describing agent (SDA) function
in the agent address space.
Related parameters
v “GBL_HFS_JAVA_DIRn” on page 103
v “GBL_DSN_SYS1_SBPXEXEC” on page 97
v “RTE_USS_RTEDIR” on page 146
v “KDS_KMS_SDA” on page 167
v “KDS_TEMA_SDA” on page 196
KPP_AGT_TEMS_NAME_NODEID
Use the KPP_AGT_TEMS_NAME_NODEID parameter to specify the primary Tivoli Enterprise
Monitoring Server values for configuring an agent in its own address space.
Optional
In the KPPENV member in the rhilev.midlev.rtename.RKANPARU library
CT_CMSLIST=%KPP_AGT_TEMS_NAME_NODEID
Default value
&rtename:CMS
Permissible values
A string of up to 8 case-sensitive characters defining the node ID of the Tivoli Enterprise
Monitoring Server to which you are connecting the agent.
34
Panel name
Specify Agent Primary TEMS Values
Panel ID
KAG62P1
Field
TEMS Name
This value is created if you specify use of a local Tivoli Enterprise Monitoring Server
(TEMS) on the same system where you created the runtime environment (RTE). This field
is prefilled if you specified a local monitoring server on z/OS and cannot be changed.
Default value
No default
Permissible values
A string of up to 8 case-sensitive characters defining the node ID of the Tivoli Enterprise
Monitoring Server to which you are connecting the agent.
PARMGEN name
Values that describe the primary TEMS this agent will connect to: specify the primary TEMS
(Kpp_TEMS_TCP_* and Kpp_TEMS_VTAM_*) parameter values that the agent will connect to.
Related parameters
v “KPP_TEMS_NAME_NODEID” on page 55
Related PARMGEN CONFIG profile parameters
Kpp_TEMS_BKUP1_*
Agent's backup TEMS parameter values. The agent's primary and backup TEMS
parameter values are used in the CT_CMSLIST parameter in the agent's
xKANPARU(KppENV) member.
KPP_AGT_VIRTUAL_IP_ADDRESS
Use the KPP_AGT_VIRTUAL_IP_ADDRESS parameter to set this parameter to the type of VIPA defined
for this z/OS system.
Required
Parameter name
AGVIPA (VIPA type for the z/OS system)
Default value
N
Permissible values
S (static), D (dynamic), or N (none)
Panel name
35
Panel ID
KAG62P5
Field
Virtual IP Address (VIPA) type
Default value
N
Permissible values
S (static), D (dynamic), or N (none)
KPP_AGT_VIPA
PARMGEN name
KPP_AGT_VIRTUAL_IP_ADDRESS
Description
VIPA type for the z/OS system
Set this parameter to the type of VIPA defined for this z/OS system. If the monitoring agent
address space is a VIPA-defined application, specify if the VIPA definition is Static or Dynamic. If
VIPA is in use, the VIPA name is resolvable through the Domain Name Server (DNS).
Note: The IP.PIPE protocol is required when dynamic VIPA is in use.
Related parameters
None
KPP_AGT_VTAM_APPL_AA
Use the KPP_AGT_VTAM_APPL_AA parameter to specify the Alert Adapter application identifier for the
Required
In the VTAM® major node (CTDPPN is the default) member of the of the
rhilev.midlev.rtename.RKANSAMU library
Parameter name
N/A
Default value
CTDPPAA
Permissible values
A valid applid name no longer than 8 characters in length
Panel name
SPECIFY VTAM APPLID VALUES
Panel ID
KAG62P6
Field
VTAM applid for Alert Adapter
Default value
CTDPPAA
36
Permissible values
KPP_AGT_VTM_APPL_AA
PARMGEN name
KPP_AGT_VTAM_APPL_AA
Description
VTAM applid for Alert Adapter
This parameter specifies the Alert Adapter application identifier for the agent address space. This
value is normally specified in “KPP_AGT_VTAM_APPL_PREFIX” on page 39, with the characters
AA appended to it.
Related parameters
None
KPP_AGT_VTAM_APPL_KPPINVPO
Use the KPP_AGT_VTAM_APPL_KPPINVPO parameter to specify the VPO VTAM application identifier
for the agent address space.
Required
In the CTDPPN member of the of the rhilev.midlev.rtename.RKANSAMU library
Parameter name
N/A
Default value
CTDPPVP
Permissible values
Panel name
Panel ID
KAG62P6
Field
TMS:Engine VTAM program operator
Default value
CTDPPVP
KPP_AGT_VTM_APPL_VPO
PARMGEN name
KPP_AGT_VTAM_APPL_KPPINVPO
Agent applids
Description
VTAM applid for VPO interface
37
This parameter specifies the VPO VTAM application identifier for the agent address space. This
value is normally specified in “KPP_AGT_VTAM_APPL_PREFIX” on page 39, with the characters
VP appended to it.
Related parameters
None
KPP_AGT_VTAM_APPL_NCS
Use the KPP_AGT_VTAM_APPL_NCS parameter to specify the Network Computing System (NCS)
application identifier for the agent address space.
Required
Parameter name
N/A
Default value
CTDPPNC
Permissible values
A valid node name no more than 8 characters in length
Panel name
Panel ID
KAG62P6
Field
Agent to TEMS connection
Default value
CTDPPNC
KPP_AGT_VTM_APPL_NCS
PARMGEN name
KPP_AGT_VTAM_APPL_NCS
Agent applids
Description
Agent to server connection applid
This parameter specifies the Network Computing System (NCS) application identifier for the
agent address space. This value is normally specified in “KPP_AGT_VTAM_APPL_PREFIX” on
page 39, with the characters NC appended to it.
Related parameters
v “KPP_AGT_VTAM_APPL_PREFIX” on page 39
KPP_AGT_VTAM_APPL_OPERATOR
Use the KPP_AGT_VTAM_APPL_OPERATOR parameter to specify the operator VTAM application
identifier for the agent address space.
38
Required
Parameter name
N/A
Default value
CTDPPOR
Permissible values
Panel name
Panel ID
KAG62P6
Field
TMS:Engine (non-CUA)
Default value
CTDPPOR
KPP_AGT_VTM_APPL_OPR
PARMGEN name
KPP_AGT_VTAM_APPL_OPERATOR
Agent applids
Description
VTAM applid for non-CUA operator
This parameter specifies the operator VTAM application identifier for the agent address space.
This is normally the value specified in “KPP_AGT_VTAM_APPL_PREFIX,” with the characters
OR appended to it.
Related parameters
None
KPP_AGT_VTAM_APPL_PREFIX
Use the KPP_AGT_VTAM_APPL_PREFIX parameter to build the VTAM applids for the agent.
Required for SNA communications
The VTAMLST definition is created in the rhilev.midlev.rtename.RKANSAMU library. Copy this
definition to your SYS1.VTAMLST library.
Parameter name
VTAMLST
Default value
CTDPP
39
Permissible values
A character string of up to 6 characters
Panel name
Specify Configuration Values/ RTE: rtename
Panel ID
KAG62P2A
Field
Applid prefix
Default value
CTDPP
Permissible values
KPP_AGT_VTM_APPL_PREF
PARMGEN name
KPP_AGT_VTAM_APPL_PREFIX
Agent applids
Description
Agent Applid prefix
This parameter is a prefix that is used to build the VTAM applids for the agent. This is a required
field if you plan to have the monitoring agent communicate with the server using VTAM.
This parameter specifies the applid prefix to establish the VTAM node and applid list. The
product creates a customized VTAMLST definition in the rhilev.midlev.rtename.RKANSAMU
library, which you then copy to your SYS1.VTAMLST library after the Configuration Tool work is
complete. The default is CTDPP.
Note:
1. Each product requires its own set of IDs. Make sure that the product identifiers are unique.
Type README APP on the command line from the Configuration Tool to get more information
about how the Configuration Tool processes VTAM applids. Use the F6=Applids key to
specify the VTAM major node and applid values.
2. If System Variable support is enabled, type README SYS on the command line from the
Configuration Tool to get more information on how the Configuration Tool processes VTAM
applids using MVS™ system symbols.
3. Do not confuse this value with “KPP_AGT_VTAM_NODE,” the value for specifying the
VTAM major node.
Related parameters
None
KPP_AGT_VTAM_NODE
Use the KPP_AGT_VTAM_NODE parameter to specify the name that will be used to build the VTAM
node entry for the agent.
In the CTDPPN member of the rhilev.midlev.rtename.RKANSAMU library
40
Parameter name
XPPAPLN
Default value
CTDPPN
Permissible values
Panel name
Specify VTAM Applid Values
Panel ID
KPP41P6
Field
Major Node
Default value
CTDPPN
Permissible values
KPP_AGT_VTM_NODE
PARMGEN name
KPP_AGT_VTAM_NODE
Agent's local VTAM and logon information
Description
Agent node name
This parameter specifies the name that will be used to build the VTAM node entry for the agent.
This is a required field if you plan to have the agent communicate with the server using VTAM.
Specify the name of the VTAM major node name that contains all the VTAM APPLID definitions
for OMEGAMON XE for Mainframe Networks. This member must be moved to your VTAMLST
concatenation. The name of this major node is also the name used to activate the VTAM
APPLIDs. The default is CTDPPN.
Related parameters
v “RTE_VTAM_GBL_MAJOR_NODE” on page 149
KPP_AGT_WTO_MSG
Use the KPP_AGT_WTO_MSG parameter to specify whether you want the monitoring agent address
space to issue Write To Operator (WTO) messages.
Required
Parameter name
WTO(N) (Enable WTO messages)
Default value
N
41
Permissible values
Y, N
Panel name
SPECIFY CONFIGURATION VALUES / RTE: rtename
Panel ID
KAG62P5
Field
Enable WTO messages
Default value
N
Permissible values
Y, N
KPP_AGT_WTO_MSG
PARMGEN name
KPP_AGT_WTO_MSG
Description
Enable WTO messages
Specify Y as the value for this parameter if you want the monitoring agent address space to issue
Write To Operator (WTO) messages. WTOs write information and exception condition messages
to the operator consoles. Alert messages are always written to the consoles. The default is N.
Related parameters
None
KPP_PD
The KPP_PD parameter specifies the beginning and ending syntax markers for the KPP_PD_* group of
parameters.
Required
The KPPAL member of the rhilev.midlev.rtename.RKANPARU library
Parameter name
N/A
Default value
BEGIN
Permissible values
BEGIN, END
This value cannot be updated using the Configuration Tool.
KPP_PD
PARMGEN name
KPP_PD
42
Persistent datastore table space allocation overrides
Description
Specifies the beginning and ending syntax markers for the KPP_PD_* group of parameters.
Related parameters
v “RTE_PDS_HILEV” on page 121
v “RTE_PDS_KPDPROC_PREFIX” on page 122
v “RTE_PDS_BACKUP_FLAG” on page 118
v “RTE_PDS_BATCHINIT_FLAG” on page 117
v “RTE_PDS_EXPORT_FLAG” on page 119
v “RTE_PDS_EXTRACT_FLAG” on page 120
v “RTE_PDS_FILE_COUNT” on page 120
v “RTE_PDS_SMS_VOLUME” on page 124
v “RTE_PDS_SMS_UNIT” on page 123
v “RTE_PDS_SMS_STORCLAS” on page 123
v “RTE_PDS_SMS_MGMTCLAS” on page 122
v “KPP_PD_CYL”
v “KPP_PD_GRP” on page 44
v “KPP_PD_ROW” on page 47
v “KPP_PD_HISTCOLL_DATA_IN_AGT_STC” on page 45
v “KPP_PD_HISTCOLL_DATA_IN_TEMS_STC” on page 46
KPP_PD_CYL
Use the KPP_PD_CYL parameter to specify the space allocation for the persistent data store libraries and
for overhead information such as the product dictionary, table records, index records, and buffers to hold
overflow data when the libraries are full.
Optional
The KPPAL member of the rhilev.midlev.rtename.RKANPARU library
Parameter name
DSG3390 (Datastore group space)
Default value
The Configuration Tool computes this value using a formula using the SIZE, WINDOW,
and UNIT TYPE values. The default in batch mode is 290. The default in interactive
mode is 261.
Permissible values
1 - 9999
Panel name
Modify and Review Datastore Specifications
Panel ID
KPD62PP3
Field
Est Cyl Space
Default value
The Configuration Tool computes this value using a formula using the SIZE, WINDOW,
and UNIT TYPE values. The default in batch mode is 290. The default in interactive
mode is 261.
43
Permissible values
1 - 9999
KPP_PD_CYL
PARMGEN name
KPP_PD_CYL
Description
Datastore group space
The parameter specifies the space allocation for the persistent data store libraries and for
overhead information such as the product dictionary, table records, index records, and buffers to
hold overflow data when the libraries are full. Allocate enough storage so that maintenance
procedures are run only once a day. For more information about maintaining the persistent data
store, see the IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: Common
Planning and Configuration Guide.
Related parameters
v “KPP_PD” on page 42
v “KPP_PD_GRP”
KPP_PD_GRP
Use the KPP_PD_GRP parameter to specify the name of a single persistent data store group.
Optional
The KPPPG member of the rhilev.midlev.rtename.RKANPARU library
Parameter name
PDV1GRP (Datastore group name)
Default value
KPP
Permissible values
44
Panel name
Panel ID
KPD62PP3
Field
Datastore group name
Default value
PP
Permissible values
KPP_PD_GRP
PARMGEN name
KPP_PD_GRP
Description
Datastore group name
This parameter specifies the name of a single persistent data store group. KPP is the name of the
default group. Each group contains the number of data sets specified in the Group Count field.
The default for the Group Count field is 3, the minimum.
Related parameters
v “KPP_PD_CYL” on page 43
v “KPP_PD_HISTCOLL_DATA_IN_AGT_STC”
KPP_PD_HISTCOLL_DATA_IN_AGT_STC
Use the KPP_PD_HISTCOLL_DATA_IN_AGT_STC parameter to specify that historical collection is being
performed by the monitoring agent address space.
Optional
KppAL, KppPG, KppDEFIN, and KppPCTL members of the rhilev.rte.RKANPARU library for the
runtime environment of the Agent
Parameter name
N/A
45
Default value
Y
Permissible values
Y, N
In the Configuration Tool
This flag is set upon selecting the "Configure persistent datastore" option on the Agent menu.
Panel name
Configure persistent datastore (in Agent)
Panel ID
KPD62PP0
Field
N/A
Default value
Y
Permissible values
Y, N
Kpp_PDS_IRA
PARMGEN name
Kpp_PD_HISTCOLL_DATA_IN_AGT_STC
Related parameters
v “KPP_PD_HISTCOLL_DATA_IN_TEMS_STC”
KPP_PD_HISTCOLL_DATA_IN_TEMS_STC
Use the KPP_PD_HISTCOLL_DATA_IN_TEMS_STC parameter to specify whether historical collection is
being performed by the Tivoli Enterprise Monitoring Server address space.
Required
KPDAL/KppAL, KPDPG/KppAL, KPDDEFIN, and KPDPCTL members of the
rhilev.rte.RKANPARU library for the runtime environment of the TEMS.
Parameter name
N/A
46
Default value
Y
Permissible values
Y, N
This flag is set upon selecting the "Configure persistent datastore" option on the Agent main
menu.
Panel name
Configure persistent datastore (in TEMS)
Panel ID
KPD62PP0
Field
N/A
Default value
Y
Permissible values
Y, N
Kpp_PDS_CMS
PARMGEN name
Kpp_PD_HISTCOLL_DATA_IN_TEMS_STC
Related parameters
v “KPP_PD_ROW”
KPP_PD_ROW
Use the KPP_PD_ROW parameter to specify the beginning or end of a single persistent datastore group
for the server product.
Optional
The KPPPG member of the rhilev.midlev.rtename.RKANPARU library
Parameter name
PDV1ROW (Row begin group end indicator)
47
Default value
BEGIN
Permissible values
BEGIN, END
This value cannot be updated using the Configuration Tool.
KPP_PD_ROW
PARMGEN name
KPP_PD_ROW
Description
Row begin group end indicator
This parameter indicates the beginning or end of a single persistent datastore group for the server
product. If the value is BEGIN, then the variables up to either the next BEGIN or the next END
contain all the information required to construct the group information for a single group. If no
value is specified, the default is BEGIN.
Related parameters
KPP_SECURITY_ACTION_CLASS
This parameter lists security options for Take Action commands.
Specify the System Authorization Facility (SAF) security class name override that will be used to validate
the agent's Take Action commands. If the specified class is invalid or is not active in the security
manager, the command will not be executed. The value should conform to the definition rules dictated by
the security manager.
The value is used in the Kpp_SECURITY_ACTION_CLASS parameter in the:
v xKANPARU(KppENV) member, if the agent runs in its own agent address space (that is,
Kpp_AGT_CONFIGURATION_MODE="STANDALONE")
or
48
v xKANPARU(KDSENV) member, if the agent runs in the TEMS address space (that is,
Kpp_AGT_CONFIGURATION_MODE="CMS")
Note:
1. If using ACF2 as your external security resource manager, specify a maximum of three characters.
2. Parameter RTE_SECURITY_CLASS applies to the Tivoli Enterprise Portal’s and the OMEGAMON
enhanced 3270 user interface’s Take Action security.
Related PARMGEN CONFIG profile parameter
v “RTE_SECURITY_CLASS” on page 125
KPP_TEMS_BKUP1_NAME_NODEID
Use the KPP_TEMS_BKUP1_NAME_NODEID parameter to specify the backup monitoring server values
for configuring an agent for your site.
Optional
In the KPPENV member in the rhilev.midlev.rtename.RKANPARU library to communicate with the
backup Tivoli Enterprise Monitoring Server
Parameter name
N/A
Default value
No default
Permissible values
A string of up to 32 case-sensitive characters
Panel name
SPECIFY AGENT SECONDARY TEMS VALUES
Panel ID
KAG62P8
Field
Backup TEMS name
Default value
No default
Permissible values
A string of up to 32 case-sensitive characters
KPP_CMSB_NAME
PARMGEN name
KPP_TEMS_BKUP1_NAME_NODEID
Secondary TEMS VTAM information
Description
Server that the monitoring agent will connect to if the primary Tivoli Enterprise Monitoring
Server (monitoring server) fails.
This parameter specifies backup monitoring server values for configuring an agent for your site.
This name must match the name of a non-z/OS monitoring server, or the CMS_NODEID
49
parameter value, in the KPPENV member of the rhilev.midlev.rtename.RKANPARU library for a
z/OS TEMS. If the parameter value contains the SMFID, you must enter the z/OS system's
SMFID in place of this literal.
Note: The value of this field is case-sensitive for both z/OS and non-z/OS monitoring server
names.
Related parameters
None
KPP_TEMS_BKUP1_TCP_HOST
Use the KPP_TEMS_BKUP1_TCP_HOST to specify the TCP/IP hostname identifier for the backup Tivoli
Enterprise Monitoring Server that this agent should try to connect to if the primary server is unavailable.
Optional. Required field if you plan to have this monitoring agent communicate with the backup
server using TCP/IP.
Parameter name
CT_CMSLIST=\ (Agent backup Server TCP/IP hostname)
Default value
No default
Permissible values
A string of up to 32 characters
Panel name
SPECIFY AGENT SECONDARY TEMS VALUES
Panel ID
KAG62P8
Field
Network address (Hostname of Secondary TEMS)
Default value
No default
Permissible values
KPP_CMSB_TCP_HOST
PARMGEN name
KPP_TEMS_BKUP1_TCP_HOST
Secondary TEMS TCP/IP information
Description
Agent backup Server TCP/IP hostname
This parameter specifies the TCP/IP hostname identifier for the backup Tivoli Enterprise
Monitoring Server that this agent should try to connect to if the primary server is unavailable.
This is a required field if you plan to have this agent communicate with the backup server using
TCP/IP.
50
Specify the network address of the system on which the secondary monitoring server that this
monitoring agent connects to is running. A network address may be specified as one of the
following values:
1. A fully-qualified hostname (for example: sys.ibm.com)
2. The first qualifier of the fully-qualified hostname (for example: sys for sys.ibm.com)
3. An IPv4 address in dotted decimal notation (for example: 9.67.1.100)
If the secondary monitoring server is running on a z/OS platform, you can find this value by
issuing the TSO HOMETEST command from the system where the secondary monitoring server is
running. If you will specify the hostname value for network address, use the first qualifier of the
fully qualified hostname if the z/OS domain name resolver configuration specifies a search path
that would include the target domain suffix. Otherwise, specify the fully-qualified hostname
when using a Domain Name Server (DNS). If you will specify the IP address value for network
address, use the assigned IPv4 address written in dotted decimal notation. This scheme is
numeric and consists of four groups separated by a period (.).
Related parameters
None
KPP_TEMS_BKUP1_VTAM_APPL_LLB_BKR
Optional. This is a required field if this monitoring agent needs to communicate with the backup
server using VTAM protocol.
In the KPPENV member in the rhilev.midlev.rtename.RKANPARU library if you use SNA to
communicate with the backup Tivoli Enterprise Monitoring Server
Parameter name
N/A
Default value
No default
Permissible values
Panel name
Specify Agent Secondary TEMS Values
Panel ID
KAG62P8
Field
Local location broker applid
Default value
No default
Default value
No default
Permissible values
KPP_CMSB_VTM_APPL_LLB
PARMGEN name
KPP_TEMS_BKUP1_VTAM_APPL_LLB_BKR
51
Description
Backup Server Location Broker applid
This parameter identifies the Local Location Broker that is to be used for VTAM-type
communication to the backup server. Enter the Local Location Broker applid of the secondary
Tivoli Enterprise Monitoring Server that this agent communicates with. This is a required field if
this agent needs to communicate with the backup server using SNA protocol. This field is not
required if you use TCP/IP for communication with the backup monitoring server.
Related parameters
None
Use the KPP_TEMS_BKUP1_VTAM_LU62_DLOGMOD parameter to specify the name of the LU6.2
LOGMODE that was defined for the backup server.
Optional. This is a required field if you plan to have the backup server communicate with
monitoring agents using VTAM.
Parameter name
N/A
Default value
CANCTDCS
Permissible values
Panel name
Specify Agent Secondary TEMS Values
Panel ID
KAG62P8
Field
LU6.2 logmode
Default value
CANCTDCS
Permissible values
KPP_CMSB_VTM_LU62_LOG
PARMGEN name
Description
Agent backup Server LU6.2 logmode
52
This parameter specifies the name of the LU6.2 LOGMODE that was defined for the backup
server. The default is CANCTDCS. This is a required field if you plan to have the backup server
communicate with agents using SNA. This field is not needed if you use TCP/IP for
communication with the backup monitoring server.
Related parameters
None
KPP_TEMS_BKUP1_VTAM_NETID
Use the KPP_TEMS_BKUP1_VTAM_NETID parameter to identify your SNA network.
Optional. This is a required field if you plan to have the backup server communicate with
monitoring agents using VTAM.
In the PP3ENV member in the rhilev.midlev.rtename.RKANPARU library if you use SNA to
Parameter name
N/A
Default value
No default
Permissible values
Panel name
Specify Agent Secondard TEMS Values
Panel ID
KAG62P8
Field
Network ID
Default value
No default
Permissible values
KPP_CMSB_VTM_NETID
PARMGEN name
KPP_TEMS_BKUP1_VTAM_NETID
Description
Agent backup Sever Network ID
This parameter identifies your SNA network. You can locate this value on the NETID parameter
within the VTAMLST startup member, ATCSTRnn. This is a required field if you plan to have the
backup server communicate with monitoring agents using SNA. This field is not needed if you
use TCP/IP for communication with the backup monitoring server.
Related parameters
None
53
KPP_TEMS_HUB_TCP_HOST
Use the KPP_TEMS_HUB_TCP_HOST parameter to specify the hostname or IP address of the system
where the primary Tivoli Enterprise Monitoring Server (local or remote) is running.
Optional. Required for remote Tivoli Enterprise Monitoring Servers that use TCP/IP for
communications with the hub monitoring server
In the KDCSSITE member in the rhilev.midlev.rtename.RKANPARU library
Parameter name
AGLOCCN (Connect agent to local TEMS)
Default value
None
Permissible values
Panel name
Panel ID
KAG62P1
Field
Network Address (Hostname of the primary TEMS)
Default value
None
Permissible values
KPP_CMS_HUB_TCP_HOST
PARMGEN name
KPP_TEMS_HUB_TCP_HOST
Values that describe the Primary TEMS the Agent will connect to
Description
Hostname of the primary TEMS
This parameter specifies the hostname or IP address of the system where the primary Tivoli
Enterprise Monitoring Server (local or remote) is running. The value specified for this parameter
must match the value set for the KDS_TEMS_TCP_HOST parameter in the runtime environment
where the hub is configured, or the value set for an equivalent parameter of a distributed hub.
Related parameters
None
KPP_TEMS_LOCAL_CONNECT_FLAG
Use the KPP_TEMS_LOCAL_CONNECT_FLAG parameter to specify values that describe the primary
TEMS the agent will connect to.
Note: Specify the Kpp_TEMS_TCP_* or Kpp_TEMS_VTAM_* parameter values for the primary TEMS that
the agent will connect to.
54
Optional
Parameter name
AGLOCCN (Connect agent to local TEMS)
Default value
Y
Permissible values
Y, N
Panel name
Panel ID
KAG62P2
Field
Connect to TEMS in this RTE
Default value
Y
Permissible values
Y, N
KPP_CMS_LOCAL_CONNECT
PARMGEN name
KPP_TEMS_LOCAL_CONNECT_FLAG
Description
Connect agent to local TEMS
This parameter specifies how you want to connect the agent you are defining. When defining an
agent, you have the option to connect the agent to a local server or a remote server. When
connecting to a local server you are connecting the agent to the server in this runtime
environment.
Specify Y to connect the agent to the server in this RTE. Otherwise, specify N to have the agent
connect to a remote server.
Related PARMGEN CONFIG profile parameter
Kpp_TEMS_BKUP1_*
Agent's backup TEMS parameter values
The agent's primary and backup TEMS parameter values are used in the CT_CMSLIST
parameter in the agent's xKANPARU(KppENV) member.
KPP_TEMS_NAME_NODEID
Use the KPP_TEMS_NAME_NODEID parameter to specify the primary Tivoli Enterprise Monitoring
Server values for configuring an agent for your site.
55
Optional
Parameter name
CT_CMSLIST=%KPP_TEMS_NAME_NODEID
(TEMS name)
Default value
No default
Permissible values
A string of up to 8 case-sensitive characters defining the nodeid of the server to which
you are connecting the agent
Panel name
Panel ID
KAG62P1
Field
TEMS Name
This value is created if you specify use of a local Tivoli Enterprise Monitoring Server
(TEMS) on the same system where you created the runtime environment (RTE). This field
is prefilled if you specified a local monitoring server on z/OS and cannot be changed.
Default value
No default
Permissible values
A string of up to 8 case-sensitive characters defining the nodeid of the server to which
you are connecting the agent
KPP_CMS_NAME
PARMGEN name
KPP_TEMS_NAME_NODEID
Description
Primary monitoring server that this monitoring agent connects to
This parameter specifies the primary Tivoli Enterprise Monitoring Server values for configuring
an agent for your site. This name must match the name of a non-z/OS monitoring server, or the
CMS_NODEID parameter value, in the KDSENV member of the rhilev.midlev.rtename.RKANPARU
library for a z/OS TEMS. If the parameter value contains the SMFID, you must enter the z/OS
system's SMFID in place of this literal.
Note: The value of this field is case-sensitive for both z/OS and non-z/OS monitoring server
names.
Related parameters
None
56
KPP_TEMS_TCP_HOST
Use the KPP_TEMS_TCP_HOST parameter to specify the agent's primary TEMS TCP/IP information.
Note: Kpp_TEMS_TCP_HOST and Kpp_AGT_TCP_HOST must specify the same value if
Kpp_TEMS_LOCAL_CONNECT_FLAG=Y ("Agent connects to local TEMS").
This is a required field if you plan to have this agent communicate with Tivoli Enterprise
Monitoring Server using TCP/IP.
CT_CMSLIST=%KPP_TEMS_TCP_HOST
Default value
Permissible values
Panel name
Panel ID
KAG62P1
Field
Network Address
Default value
Permissible values
KPP_CMS_TCP_HOST
PARMGEN name
KPP_TEMS_TCP_HOST
Agent's Primary TEMS TCP/IP information
Description
Server hostname
This parameter specifies the server hostname. To obtain the host name or IP address, enter TSO
HOMETEST at the command line. If the z/OS domain name resolver configuration specifies a search
path that includes the target domain suffix, specify only the first qualifier of the host name.
(Example: sys is the first qualifier of the fully qualified host name sys.ibm.com.) Otherwise,
specify the fully qualified host name.
This is a required field if you plan to have this server communicate with agents using TCP/IP.
Attention: “KPP_TEMS_TCP_HOST” and “KPP_AGT_TCP_HOST” on page 30 must be the
same value if “KPP_TEMS_LOCAL_CONNECT_FLAG” on page 54=Y (that is, if the agent
connects to local monitoring server).
Related parameters
57
v “KPP_AGT_TCP_HOST” on page 30
v “KPP_TEMS_TCP_HOST” on page 57
KPP_TEMS_TCP_PIPE_PORT_NUM
Use the KPP_TEMS_TCP_PIPE_PORT_NUM parameter to specify the IP.PIPE port number that you want
to use.
Required if you specified a value of IPPIPE as one of the “KPP_AGT_COMM_PROTOCOLn” on
page 11 protocol parameters
The KPPENV member of the rhilev.rte.RKANPARU library
Parameter name
IP.PIPE PORT: (Agent IP.PIPE port number)
Default value
1918
Permissible values
1 - 65535
Panel name
v Specify Agent Primary TEMS Values (KAG62P1 for a non-local TEMS)
v Specify IP.PIPE Communication Protocol (KDS62PPD for a local TEMS)
Panel ID
v KAG62P1 for a non-local TEMS
v KDS62PPD for a local TEMS
Field
Port number (IP.PIPE)
Default value
1918
Permissible values
1 - 65535
KPP_CMS_TCP_PIPE_PORT
PARMGEN name
KPP_TEMS_TCP_PIPE_PORT_NUM
Protocol port numbers for Agent connection to TEMS
Description
Agent IP.PIPE port number
This parameter specifies the IP.PIPE port number that you want to use. This port number is used
by the non-secure Network Computing System (NCS) IP.PIPE protocol. The default is 1918.
Note: Port numbers for non-secure IP.PIPE protocol and IP.UDP protocol must match.
Related parameters
v “KPP_AGT_COMM_PROTOCOLn” on page 11
58
KPP_TEMS_TCP_PIPES_PORT_NUM
Use the KPP_TEMS_TCP_PIPES_PORT_NUM parameter to specify the IP.SPIPE port number that you
want to use.
Required if you specified a value of IPSPIPE in one of the “KPP_AGT_COMM_PROTOCOLn” on
page 11 protocol parameters.
The KDSENV member of the rhilev.rte.RKANPARU library
Parameter name
IP.SPIPE PORT: (Agent IP.SPIPE port number)
Default value
3660
Permissible values
1 - 65535
Panel name
Panel ID
Field
Port number (Secure IP.PIPE)
Default value
3660
Permissible values
1 - 65535
KPP_CMS_TCP_PIPES_PORT
PARMGEN name
KPP_TEMS_TCP_PIPES_PORT_NUM
Description
Agent IP.SPIPE port number
This parameter specifies the IP.SPIPE port number that you want to use. This port number is
used by the secure Network Computing System (NCS) IP.PIPE protocol. The default is 3660.
Note: Port numbers for non-secure IP.SPIPE protocols must match
This parameter is required if you specified a value of IPSPIPE in one of the
KPP_AGT_COMM_PROn protocol parameters.
Related parameters
59
KPP_TEMS_TCP_PIPE6_PORT_NUM
Use the KPP_TEMS_TCP_PIPE6_PORT_NUM parameter to specify the IP6.PIPE port number that you
want to use.
Required if you specified a value of IP6PIPE in one of the “KPP_AGT_COMM_PROTOCOLn” on
page 11 protocol parameters.
The KPPENV member of the rhilev.midlev.rtename.RKANPARU library
Parameter name
PORT: IP6.PIPE PORT: (Agent IP6.PIPE port number)
Default value
No default
Permissible values
1 - 65535
Panel name
Panel ID
Field
Port number (IP.PIPE for IPV6)
Default value
No default
Permissible values
1 - 65535
KPP_CMS_TCP_PIPE6_PORT
PARMGEN name
KPP_TEMS_TCP_PIPE6_PORT_NUM
Description
Agent IP6.PIPE port number
This parameter specifies the IP6.PIPE port number that you want to use. This port number is
used by the non-secure Network Computing System (NCS) IP.PIPE protocol. The default is 1918.
Note: Port numbers for non-secure IP6.PIPE and IP.UDP protocols must match.
This parameter is required if you specified a value of IP6PIPE in one of the
Related parameters
60
KPP_TEMS_TCP_PIPE6S_PORT_NUM
Use the KPP_TEMS_TCP_PIPE6S_PORT_NUM parameter to specify the IP6.SPIPE port number that you
want to use.
Required if you specified a value of IP6SPIPE in one of the “KPP_AGT_COMM_PROTOCOLn”
on page 11 protocol parameters.
Parameter name
IP6.SPIPE: PORT: (Agent IP.PIPE port number)
Default value
3660
Permissible values
1 - 65535
Panel name
v Specify Agent Primary TEMS Values (KAG62PI1 for a non-local TEMS)
Panel ID
Field
Port number (Secure IP.PIPE for IPV6)
Default value
3660
Permissible values
1 - 65535
KPP_CMS_TCP_PIPE6S_PORT
PARMGEN name
KPP_TEMS_TCP_PIPE6S_PORT_NUM
Description
Agent IP6.SPIPE port number
This parameter specifies the IP6.SPIPE port number that you want to use. This port number is
used by the secure Network Computing System (NCS) IP.PIPE protocol. The default is 3660.
Note: Port numbers for non-secure IP.PIPE and IP.UDP protocols must match.
This parameter is required if you specified a value of IP6.SPIPE in one of the
Related parameters
KPP_TEMS_TCP_UDP_PORT_NUM
Use the KPP_TEMS_TCP_UDP_PORT_NUM parameter to specify the IP.UDP port number that you want
to use.
61
Use the KPP_TEMS_TCP_UDP_PORT_NUM parameter to specify the IP.UDP port number that you want
to use.
Required if you specified a value of IP in one of the “KPP_AGT_COMM_PROTOCOLn” on page
11 protocol parameters.
Parameter name
IP.UDP PORT: (Agent IP.UDP port number)
Default value
1918
Permissible values
1 - 65535
Panel name
Panel ID
Field
Port number (IP.UDP)
Default value
1918
Permissible values
1 - 65535
KPP_CMS_TCP_UDP_PORT
PARMGEN name
KPP_TEMS_TCP_UDP_PORT_NUM
Description
Agent IP.UDP port number
This parameter specifies the IP.UDP port number that you want to use. This port number is used
by the non-secure Network Computing System (NCS) IP (UDP) protocol. The default is 1918.
Note: Port numbers for non-secure IP.PIPE protocol and IP.UDP protocol must match.
This parameter is required if you specified a value of IP in one of the KPP_AGT_COMM_PROn
protocol parameters.
Related parameters
KPP_TEMS_TCP_UDP6_PORT_NUM
Use the KPP_TEMS_TCP_UDP6_PORT_NUM parameter to specify the IP6.UDP port number that you
want to use.
62
Required if you specified a value of IP6 in one of the “KPP_AGT_COMM_PROTOCOLn” on page
11 protocol parameters.
Parameter name
IP6.UDP PORT: (Agent IP.UDP port number)
Default value
No default
Permissible values
1 - 65535
Panel name
Panel ID
Field
Port number (IP6.UDP)
Default value
No default
Permissible values
1 - 65535
KPP_CMS_TCP_UDP6_PORT
PARMGEN name
KPP_TEMS_TCP_UDP6_PORT_NUM
Description
Agent IP6.UDP port number for IPv6
This parameter specifies the IP6.UDP port number that you want to use. This port number is
used by the non-secure Network Computing System (NCS) IP (UDP) protocol. The default is
1918.
Note: Port numbers for non-secure IP.PIPE protocols must match.
This parameter is required if you specified a value of IP6 in one of the KPP_AGT_COMM_PROn
protocol parameters.
Related parameters
KPP_TEMS_VTAM_APPL_LLB_BROKER
Use the KPP_TEMS_VTAM_APPL_LLB_BROKER parameter to identify which Local Location Broker is to
be used for VTAM-type communication.
Required if you use SNA to communicate with the Tivoli Enterprise Monitoring Server
63
CT_CMSLIST=%KPP_TEMS_VTAM_APPL_LLB_BROKER
Default value
CTDDSLB
Permissible values
In the Configuration Tool
Panel name
Panel ID
KAG62P1
Field
Local Location Broker applid
Default value
CTDDSLB
Permissible values
KPP_CMS_VTM_APPL_LLB
PARMGEN name
KPP_TEMS_VTAM_APPL_LLB_BROKER
Agent's Primary TEMS VTAM information
Description
Local Location Broker applid
This parameter identifies which Local Location Broker is to be used for VTAM-type
communication.
This is a required field if you use SNA to communicate with the Tivoli Enterprise Monitoring
Server.
Related parameters
None
KPP_TEMS_VTAM_LU62_DLOGMOD
Use the KPP_TEMS_VTAM_LU62_DLOGMOD parameter to specify the name of the LU6.2 LOGMODE
that was defined for the server.
The CTDPPN member of the rhilev.midlev.rtename.RKANSAMU library
CT_CMSLIST=%KPP_TEMS_VTAM_LU62_DLOGMOD
Default value
CANCTDCS
64
Permissible values
Panel name
Panel ID
KAG62P1
Field
LU6.2 logmode
Default value
CANCTDCS
Permissible values
KPP_CMS_VTM_LU62_LOG
PARMGEN name
KPP_TEMS_VTAM_LU62_DLOGMOD
Description
LU6.2 LOGMODE
This parameter specifies the name of the LU6.2 LOGMODE that was defined for the server. This
is a required field if you plan to have the server communicate with agents using VTAM. The IBM
default is CANCTDCS.
Related parameters
None
KPP_TEMS_VTAM_LU62_MODETAB
Use the KPP_TEMS_VTAM_LU62_MODETAB parameter to specify the name of the LOGMODE table
containing the LU6.2 LOGMODE definition.
The CTDPPN member of the rhilev.midlev.rtename.RKANSAMU library
CT_CMSLIST=%KPP_TEMS_VTAM_LU62_MODETAB
Default value
KDSMTAB1
Permissible values
Panel name
Panel ID
KAG62P1
65
Field
LOGMODE table name
Default value
KDSMTAB1
Permissible values
KPP_CMS_VTM_LU62_LOGTAB
PARMGEN name
KPP_TEMS_VTAM_LU62_MODETAB
Description
LOGMODE table name
This parameter specifies the name of the LOGMODE table containing the LU6.2 LOGMODE
definition. This is a required field if you plan to have the server communicate with agents using
SNA.
Related parameters
None
KPP_TEMS_VTAM_NETID
Use the KPP_TEMS_VTAM_NETID parameter to specify the identifier of your VTAM network.
CT_CMSLIST=%KPP_TEMS_VTAM_NETID
Default value
Value set for the RTE_VTAM_NETID or RTE_SYSV_VTAM_NETID parameter
Permissible values
Panel name
Panel ID
KAG62P1
Field
Network ID
Default value
Value set for the RTE_VTAM_NETID or RTE_SYSV_VTAM_NETID parameter
Permissible values
KPP_CMS_VTM_NETID
66
PARMGEN name
KPP_TEMS_VTAM_NETID
Description
Network ID
This parameter specifies the identifier of your VTAM network. You can locate this value on the
NETID parameter within the VTAMLST startup member (ATCSTRnn). This is a required field if
you plan to have this server communicate to agents using VTAM.
Related parameters
None
KPP_X_AGT_CONFIRM_SHUTDOWN
Use the KPP_X_AGT_CONFIRM_SHUTDOWN PARMGEN-only parameter to specify the maximum
number of seconds between two successive SHUTDOWN commands or MVS STOP (P) commands to terminate
the monitoring agent address space.
Required
Parameter name
CONFIRM(&XPPFIRM) (Confirm shutdown option)
Default value
0
Permissible values
0 to 15
PARMGEN name
KPP_X_AGT_CONFIRM_SHUTDOWN
Additional agent settings
Description
Confirm shutdown option
This parameter sets the maximum number of seconds between two successive SHUTDOWN
commands or MVS STOP (P) commands to terminate the monitoring agent address space.
CONFIRM(0) allows TMS:Engine shutdown to begin immediately without an additional,
confirming SHUTDOWN command.
CONFIRM(n) prevents accidental shutdowns by requiring you to confirm the command by
entering it a second time within the specified number of seconds.
For example, CONFIRM(15) requires you enter SHUTDOWN twice within 15 seconds to
terminate the address space.
The default for the monitoring agent CONFIRM is 0, which is also the Tivoli Enterprise
Monitoring Server default.
Related parameters
None
67
KPP_X_AGT_DEBUG_TRACE
Use the KPP_X_AGT_DEBUG_TRACE PARMGEN-only parameter to specify whether TMS:Engine
debugging services are to be activated.
Optional
Parameter name
DEBUG(&XPPDEBG) (TMS:Engine Debugging Services)
Default value
N
Permissible values
Y, N
PARMGEN name
KPP_X_AGT_DEBUG_TRACE
Description
TMS:Engine Debugging Services
Attention:
Do not modify this parameter except under the guidance of IBM Software Support.
This parameter specifies whether TMS:Engine debugging services are to be activated.
N means that basic debugging information will not be recorded.
Y means that basic debugging information will be recorded.
DEBUG and STGDEBUG may affect each other. If DEBUG(Y) is specified and STGDEBUG is
omitted, basic storage debugging is turned on, causing an increase in storage use.
STGDEBUG must also be specified after DEBUG in the initialization deck for proper functioning
of these turned on, causing an increase in storage use. DEBUG will override STGDEBUG if it
follows STGDEBUG.
The default for the monitoring agent DEBUG is N.
Related parameters
None
KPP_X_AGT_KDC_DEBUG
Use the KPP_X_AGT_KDC_DEBUG PARMGEN-only parameter to instruct the data communications
layer to report communications problems using a minimal, summary format.
Optional
Parameter name
KDC_DEBUG=(&XPPDBUG) (TCP/IP communication trace debug)
Default value
N
68
Permissible values
Y, N, D, M, A
PARMGEN name
KPP_X_AGT_KDC_DEBUG
Description
TCP/IP communication trace debug
Attention:
TCP/IP communication trace debug
Set this parameter to Y if you want KDC_DEBUG=Y as the override setting in
RKANPARU(KPPENV) member. Otherwise, the default setting of KDC_DEBUG=N is used. This
default parameter instructs the data communications layer to report communications problems
using a minimal, summary format. This parameter is intended for stable applications in
production.
Note that the default KDC_DEBUG=N generates standard RAS1 trace data in the Agent
RKLVLOG, in addition to the summary information diagnosing possible timeout conditions.
The following settings report on data communications problems:
v KDC_DEBUG=N: minimal tracing (default)
v KDC_DEBUG=Y: full-packet tracing
v KDC_DEBUG=D: KDC_DEBUG=Y plus STATE & FLOW tracing
v KDC_DEBUG=M: KDC_DEBUG=D plus INPUT & OUTPUT HELPs tracing
v KDC_DEBUG=A: KDC_DEBUG=M plus all format tracing
Note: Do not set KDC_DEBUG=A unless directed to by IBM Software Support.
Related parameters
None
KPP_X_AGT_LGSA_VERIFY
Use the KPP_X_AGT_LGSA_VERIFY PARMGEN-only parameter to specify whether TMS:Engine checks
that the $GSA address is available.
Required
In the KPPSYSIN member of the rhilev.midlev.rtename.RKANPAU library
Parameter name
LGSA(&XPPLGSA) (Verify $GSA address availability)
Default value
Y
Permissible values
Y, N
PARMGEN name
KPP_X_AGT_LGSA_VERIFY
69
Description
Verify $GSA address availability
Attention:
This parameter determines whether TMS:Engine checks that the $GSA address is available. Y, N
are the only options.
Y means you want to check if available.
N means you do not want to check if available.
The default for the monitoring agent LGSA is Y, which is also the Tivoli Enterprise Monitoring
Server default value.
Related parameters
None
KPP_X_AGT_LSRPOOL_BUFFER_NUM
Use the KPP_X_AGT_LSRPOOL_BUFFER_NUM PARMGEN-only parameter to specify the number of
virtual storage buffers to be allocated for the specified buffer pool in the VSAM resource pool.
Required
Parameter name
LSRPOOL(&XPPBNUM,number) (Number of buffers)
Default value
32
Permissible values
3 - 65535 (to the maximum amount of available virtual storage in the monitoring agent
address space)
PARMGEN name
KPP_X_AGT_LSRPOOL_BUFFER_NUM
Description
Number of buffers
This parameter specifies the number of virtual storage buffers to be allocated for buffer pool "n"
in the VSAM resource pool. You must specify a size for each buffer pool individually. You cannot
string the definitions because they must be specified individually.
Permissible values: 3-65535.
This parameter has size of buffers and number of buffer and is specified as LSRPOOL(32768,32).
The default for the monitoring agent LSRPOOL buffer number is 32.
Related parameters
None
70
KPP_X_AGT_LSRPOOL_BUFSIZE
Use the KPP_X_AGT_LSRPOOL_BUFSIZE PARMGEN-only parameter to specify the size in bytes of each
virtual storage buffer in the specified buffer pool in the VSAM resource pool.
Required
Parameter name
LSRPOOL(&XPPBSIZ,number) (Size of virtual storage buffer in pool)
Default value
32768
Permissible values
512, 1024, 2048, 8192, 12288, 16384, 20480, 24576, 28672, or 32768
PARMGEN name
KPP_X_AGT_LSRPOOL_BUFSIZE
Description
Size of virtual storage buffer in pool
This parameter specifies the size in bytes of each virtual storage buffer in buffer pool "n" in the
VSAM resource pool. You must specify a size for each buffer pool individually. You cannot string
the definitions because they must be specified individually.
Permissible values are one of the following: 512, 1024, 2048, 8192, 12288, 16384, 20480, 24576,
28672, or 32768.
This parameter has size of buffers and number of buffer and specified as LSRPOOL(32768,32).
The default for the monitoring agent LSRPOOL buffer size is 32768.
Related parameters
None
KPP_X_AGT_SDUMP_SVC_SYS1_DUMP
Use the KPP_X_AGT_SDUMP_SVC_SYS1_DUMP PARMGEN-only parameter to specify whether SVC
dumps are generated.
Required
Parameter name
SDUMP(&XPPDSVC) (Generate SVC dump)
Default value
Y
Permissible values
Y, N, S ,M
PARMGEN name
KPP_X_AGT_SDUMP_SVC_SYS1_DUMP
71
Description
Generate SVC dump
This parameter determines whether SVC dumps are generated.
Y directs the SVC dump to a system dump data set (SYS1.DUMPxx). Before you specify Y as the
value of this parameter, ensure that the TMS:Engine job step is APF-authorized and that the
SYS1.DUMPxx data sets are large enough to hold the contents of the TMS:Engine address space.
N directs formatted dumps to the RKLVSNAP data set. Avoid formatted dumps if possible
because they disable the TMS:Engine address space for a longer time than either SVC dumps or
SYSMDUMPs, and are more difficult to analyze.
S directs summary dumps to the RKLVSNAP data set. A summary dump consistes of an ABEND
summary and dispatcher summary and does not provide enough information for reliable problem
analysis. Use this setting for specific testing purposes only.
M directs ABEND dumps to the data set with the SYSMDUMP DD name. This type of dump is
not formatted by the operating system and must be analyzed with IPCS. Only the first dump
taken is captured in the SYSMDUMP data set unless JCL specifies DISP=MOD. TMS:Engine
automatically initializes the SYSMDUMP data set with an end-of-file mark.
The default for the monitoring agent SDUMP is Y.
Related parameters
None
KPP_X_AGT_STORAGE_LIMIT_EXTEND
The KPP_X_AGT_STORAGE_LIMIT_EXTEND PARMGEN-only parameter specifies the maximum size for
TMS:Engine primary storage (above-the-line) requests.
Required
In the KPPSYSIN data set of the rhilev.midlev.rtename.RKANPARU library
Parameter name
LIMIT(&XPPELIM,X)
Default value
22
Permissible values
A power of 2 between 16 and 25.
PARMGEN name
KPP_X_AGT_STORAGE_LIMIT_EXTEND
Description
Extended maximum storage request
This parameter specifies the maximum size for the TMS:Engine primary storage (above-the-line)
request. The maximum extended storage request size is specified as a power of 2. The minimum
extended storage size is 16, which specifies a limit of 64K. The maximum is 25, which specifies a
limit of 32 MB.
72
The default for the monitoring agent extended storage is 22, which specifies a limit of 4 MB.
Related parameters
None
KPP_X_AGT_STORAGE_LIMIT_PRIMARY
Use the KPP_X_AGT_STORAGE_LIMIT_PRIMARY PARMGEN-only parameter to specify the maximum
size for the TMS:Engine primary storage request.
Required
Parameter name
LIMIT(&XPPPLIM,P) (Primary maximum storage request)
Default value
20
Permissible values
A power of two between 16 and 25
PARMGEN name
KPP_X_AGT_STORAGE_LIMIT_PRIMARY
Description
Primary maximum storage request
This parameter specifies the maximum size for the TMS:Engine primary storage request. The
maximum primary storage request size is specified as a power of 2. The minimum primary
storage size is 16, which specifies a limit of 64K. The maximum is 25, which specifies a limit of 32
MB
The default for the monitoring agent primary storage is 20, which specifies a limit of 1 MB.
Related parameters
None
KPP_X_AGT_STORAGE_RESERVE_EXT
Use the KPP_X_AGT_STORAGE_RESERVE_EXT PARMGEN-only parameter to specify the number of
kilobytes of extended (above-the-line) storage to set aside for other routines that might perform their own
GETMAINs in this address space.
Required
Parameter name
RESERVE(&XAGERES,X) (Extended 31-bit region reserve)
Default value
2048
Permissible values
0 to 9999
73
PARMGEN name
KPP_X_AGT_STORAGE_RESERVE_EXT
Description
Extended 31-bit region reserve
This parameter specifies the number of kilobytes of extended (above-the-line) storage to set aside
for other routines that might perform their own GETMAINs in this address space. If your
RESERVE value is too small, you might encounter IST566I messages from VTAM or S80A, S878,
S066, S40D, or S0F9 abends.
The default for the monitoring agent primary storage reserve is 2048 KB.
Related parameters
None
KPP_X_AGT_STORAGE_RESERVE_PRI
Use the KPP_X_AGT_STORAGE_RESERVE_PRI PARMGEN-only parameter to specify the number of KB
of primary (below-the-line) storage to set aside for other routines (for example, ACF2 and RACF®) that
might perform their own GETMAINs in this address space.
Required
Parameter name
RESERVE(&XPPPRES,P) (Primary 24-bit region reserve)
Default value
2048
Permissible values
0 to 9999
PARMGEN name
KPP_X_AGT_STORAGE_RESERVE_PRI
Description
Primary 24-bit region reserve
This parameter specifies the number of KB of primary (below-the-line) storage to set aside for
other routines (for example, ACF2 and RACF) that might perform their own GETMAINs in this
address space. ACF2 and RACF use approximately 1 KB of primary storage per logged-on user. If
your RESERVE value is too small, you might encounter IST566I messages from VTAM or S80A,
S878, S066, S40D, or S0F9 abends.
The default for the monitoring agent primary storage reserve is 2048 KB.
Related parameters
None
74
KPP_X_AGT_STORAGE_STGDEBUG
Use the KPP_X_AGT_STORAGE_STGDEBUG PARMGEN-only parameter to specify whether TMS:Engine
storage debugging services are to be activated.
Optional
The KPPSYSIN member of the rhilev.midlev.rtename.RKANPARU library
Parameter name
STGDEBUG(&XPPSTDB) (Storage Debugging Services)
Default value
N
Permissible values
Y, N, X
PARMGEN name
KPP_X_AGT_STORAGE_STGDEBUG
Description
Storage Debugging Services
This parameter specifies whether TMS:Engine storage debugging services are to be activated.
N means that storage debugging information will not be recorded.
Y means that basic storage debugging information will be recorded.
X means that extended storage debugging information will be recorded.
DEBUG and STGDEBUG can affect each other. If DEBUG(Y) is specified and STGDEBUG is
omitted, basic storage debugging is turned on, causing an increase in storage use.
STGDEBUG must also be specified after DEBUG in the initialization deck for proper functioning
of these turned on, causing an increase in storage use. DEBUG will override STGDEBUG if it
follows STGDEBUG.
The default for the monitoring agent STGDEBUG is N. This parameter is usually omitted from
the KPPSYSIN member.
Related parameters
None
KPP_X_AGT_TASKS_ATTACHED_NUM
Use the KPP_X_AGT_TASKS_ATTACHED_NUM PARMGEN-only parameter to specify the number of
general-purpose subtasks to be attached in the TMS:Engine address space.
Required
Parameter name
TASKS(&XPPTASK) (Default number of available processors)
75
Default value
1
Permissible values
PARMGEN name
KPP_X_AGT_TASKS_ATTACHED_NUM
Description
Default number of available processors
Attention:
This parameter specifies the number of general-purpose subtasks to be attached in the
TMS:Engine address space. If TMS:Engine is running on a multiprocessor, the TASKS default
increases both throughput and CPU usage. Reducing the number of tasks decreases both
throughput and CPU usage.
The default for the monitoring agent TASKS is 1.
Related parameters
None
KPP_X_HUB_BKUP1_TCP_HOST
Use the KPP_X_HUB_BKUP1_TCP_HOST PARMGEN-only parameter to specify the TCP/IP hostname
identifier for the hub Tivoli Enterprise Monitoring Server that this agent should try to connect to if the
primary server is unavailable.
Required field if you plan to have this monitoring agent communicate with the backup server
using TCP/IP.
Permissible values
KPP_X_HUB_BKUP1_TCP_HOST
Related parameters
None
KPP_X_HUB_BKUP1_TEMS_VTAM_NETID
Use the KPP_X_HUB_BKUP1_TEMS_VTAM_NETID PARMGEN-only parameter to identify the SNA.PIPE
protocol for communications with the secondary hub Tivoli Enterprise Monitoring Server.
Required, if you plan to have the backup server communicate with monitoring agents using
VTAM.
communicate with the backup Tivoli Enterprise Monitoring Server.
76
Permissible values
A string of up to eight characters
KPP_X_HUB_BKUP1_TEMS_VTAM_NETID
Related parameters
None
KPP_X_HUB_BKUP1_VTAM_APPL_GLBBKR
Use the KPP_X_HUB_BKUP1_VTAM_APPL_GLBBKR PARMGEN-only parameter to identify the global
hub backup server location broker APPLID.
Enter the Global Location Broker APPLID of the hub Tivoli Enterprise Monitoring Server that this agent
uses for communication. This is a required field, if this agent needs to communicate with the backup
server using SNA protocol. This field is not required, if you use TCP/IP for communication with the
backup monitoring server.
Required if this monitoring agent needs to communicate with the backup server using VTAM
protocol.
Field
Global location broker applid
Default value
No default
Default value
No default
Permissible values
A string of up to eight characters
KPP_X_HUB_BKUP1_VTAM_APPL_GLBBKR
Related parameters
None
KPP_X_HUB_TCP_HOST
Use the KPP_X_HUB_TCP_HOST PARMGEN-only parameter to specify the hub server hostname.
This is a required field if you plan to have this hub server communicate with agents using TCP/IP.
Required if you plan to have this agent communicate with the hub Tivoli Enterprise Monitoring
Server using TCP/IP.
Permissible values
77
Permissible values
Character string, maximum length of 32
KPP_X_HUB_TCP_HOST
Related parameters
None
KPP_X_HUB_TEMS_VTAM_NETID
Use the KPP_X_HUB_TEMS_VTAM_NETID PARMGEN-only parameter to specify the VTAM identifier
associated with the hub monitoring server.
Required if you use SNA to communicate with the hub Tivoli Enterprise Monitoring Server.
Permissible values
Character string, maximum length of eight
Permissible values
Character string, maximum length of eight.
KPP_X_HUB_TEMS_VTAM_NETID
Related parameters
None
KPP_X_HUB_VTAM_APPL_GLBBKR
Use the KPP_X_HUB_VTAM_APPL_GLBBKR PARMGEN-only parameter to identify the global hub
server location broker APPLID.
Enter the Global Location Broker APPLID of the hub Tivoli Enterprise Monitoring Server that this agent
uses for communication. This is a required field, if this agent needs to communicate with the backup
server using SNA protocol. This field is not required, if you use TCP/IP for communication with the
Required if this monitoring agent needs to communicate with the hub monitoring server using
the VTAM applid for the global location broker.
communicate with the hub Tivoli Enterprise Monitoring Server.
Default value
No default
Permissible values
Field
78
Global location broker applid
Default value
No default
Permissible values
KPP_X_HUB_VTAM_APPL_GLBBKR
Related parameters
None
KPP_X_PD_HISTCOLL_DATA_AGT_STC
Use the KPP_X_PD_HISTCOLL_DATA_AGT_STC PARMGEN-only parameter to specify historical
collection is being performed by the Tivoli Enterprise Monitoring Server address space.
Optional
This parameter is used for internal processing to enable a flag to be set if persistent datastore
configuration is being set for the product. When this flag is set, the KPPPG, KPPAL, KPPPCTL,
KPPPCTL2 and KPPDEFIN members are created in rhilev.midlev.rtename.RKANPARU library.
Parameter name
N/A
Default value
Y
Permissible values
Y, N
PARMGEN name
KPP_X_PD_HISTCOLL_DATA_AGT_STC
Persistent datastore
Description
This parameter indicates whether historical collection is being performed by the Tivoli Enterprise
Monitoring Server address space. Y means that the monitoring server address space is collecting
historical data. N means that the monitoring server address space is not collecting historical data.
The default in N
This parameter defines the started task name for historical data collection when this collection
takes place on the Tivoli Enterprise Monitoring Server and the monitoring agent is running in the
monitoring server address space (which is the recommended configuration for this monitoring
agent). Y means that the monitoring server is collecting historical data. The KPDPG, KP3AL,
KPPPCTL, KPDPCTL2, and KPDDEFIN members of the rhilev.midlev.rtename.RKANPARU library
are created when this flag is set.
Related parameters
None
KPP_X_PD_HISTCOLL_DATA_TEMS_STC
Use the KPP_X_PD_HISTCOLL_DATA_TEMS_STC PARMGEN-only parameter to specify whether
historical collection is being performed by the monitoring agent address space.
79
Optional
Parameter name
N/A
Default value
N
Permissible values
Y, N
PARMGEN name
KPP_X_PD_HISTCOLL_DATA_TEMS_STC
Persistent datastore
Description
This parameter indicates whether historical collection is being performed by the monitoring agent
address space. Y means that this agent address space is collecting historical data. N means that
the agent address space is not collecting historical data. The default in N.
This parameter determines whether historical data collection takes place on the Tivoli Enterprise
Monitoring Server or on the monitoring agents where the monitoring agent is running in the
monitoring server address space (which is the recommended configuration for this monitoring
agent). The KPDPG, KPDPCTL, KPDPCTL2, and KPDDEFIN members of the
rhilev.midlev.rtename.RKANPARU library are updated with KPP*-specific parameters when this
flag is set.
Related parameters
None
80
Chapter 3. Global (GBL) parameters
The global parameters are explained in this chapter.
GBL_DSN_ACF2_MACLIB
This parameter contains the name of an ACF2 macro library.
Optional
Panel name
Add Runtime Environment (2 of 3)
Panel ID
KCIPRTA1
Field
ACF2 macro library
Default value
SYS1.ACF2.MACLIB
Permissible values
RTE_ACF2_MACLIB
PARMGEN name
GBL_DSN_ACF2_MACLIB
Description
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, and so on).
Related parameters
v “RTE_SECURITY_USER_LOGON” on page 127
GBL_DSN_CBC_SCCNOBJ
This PARMGEN-only parameter contains the name of the XL C Compiler object library
Optional
Default value
CBC.SCCNOBJ
Permissible values
PARMGEN name
GBL_DSN_CBC_SCCNOBJ
Description
This is the name of the XL C Compiler object library.
81
Related parameters
None
GBL_DSN_CBC_SCLBSID
This PARMGEN-only parameter contains the name of the XL C/C++ side-deck library.
Optional
Default value
CBC.SCCNOBJ
Permissible values
PARMGEN name
GBL_DSN_CBC_SCLBSID
Description
This is the name of the XL C/C++ side-deck library.
Related parameters
None
GBL_DSN_CEE_SCEEBIND
This PARMGEN-only parameter contains the location of the LE/370 C XPLINK resident routines.
Optional
Default value
CEE.SCEEBIND
Permissible values
PARMGEN name
GBL_DSN_CEE_SCEEBIND
Description
This is the name of the library containing LE/370 C XPLINK resident routines.
Related parameters
None
GBL_DSN_CEE_SCEEBND2
This PARMGEN-only parameter contains the location of the LE/370 C XPLINK LP64 library.
Optiional
Default value
CEE.SCEEBND2
Permissible values
CEE.SCEEBND2
PARMGEN name
GBL_DSN_CEE_SCEEBND2
82
Description
This is the name of the LE/370 C XPLINK LP64 library.
Related parameters
None
GBL_DSN_CEE_SCEECPP
This PARMGEN-only parameter contains the name of the LE/370 C++ class library.
Optional
Default value
CEE.SCEECPP
Permissible values
PARMGEN name
GBL_DSN_CEE_SCEECPP
Description
This is the name of the LE/370 C++ class library.
Related parameters
None
GBL_DSN_CEE_SCEELIB
This PARMGEN-only parameter contains the name of the LE/370 C side-deck library.
Optional
Default value
CEE.SCEELIB
Permissible values
PARMGEN name
GBL_DSN_CEE_SCEELIB
Description
This is the name of the LE/370 C side-deck library.
Related parameters
None
GBL_DSN_CEE_SCEELKED
This parameter contains the name of the LE/370 C link-edit library.
Required
Default value
CEE.SCEELKED
Permissible values
83
Panel name
Specify Linkedit Libraries
Panel ID
KQI70PLE
Field
LE/370 C support libraries (Required)
KQI_CEE_LE370_LKED
PARMGEN name
GBL_DSN_CEE_SCEELKED
Description
This is the LE/370 C link-edit library that contains the link-edit stubs for C/C++, PL/I, COBOL,
and Fortran languages and Language Environment-provided routines.
Related parameters
None
GBL_DSN_CEE_SCEELKEX
This PARMGEN-only parameter contains the location of the LE/370 C non-XPLINK long names.
Optional
Default value
CEE.SCEELKEX
Permissible values
PARMGEN name
GBL_DSN_CEE_SCEELKEX
Description
This is the location of the LE/370 C non-XPLINK long names.
Related parameters
None
GBL_DSN_CEE_SCEEMSGP
This PARMGEN-only parameter contains the name of the library containing the LE/370 C prelinker
messages.
Optional
Default value
CEE.SCEEMSGP
Permissible values
PARMGEN name
GBL_DSN_CEE_SCEEMSGP
Description
This is the name of the library containing the LE/370 C prelinker messages.
Related parameters
None
84
GBL_DSN_CEE_SCEERUN
This parameter contains the name of the LE/370 C Runtime Library.
Required
Panel name
Panel ID
KQI70PLE
Field
LE/370 C support libraries (Required)
Default value
CEE.SCEERUN
Permissible values
KQI_CEE_LE370_RUN
PARMGEN name
GBL_DSN_CEE_SCEERUN
Description
This is the LE/370 C runtime library that contains the routines needed during execution of
applications written in C/C++, PL/I, COBOL and Fortran.
Related parameters
None
GBL_DSN_CEE_SCEESPC
This PARMGEN-only parameter contains the name of the LE/370 system programmer’s C facility.
Optional
Default value
CEE.SCEESPC
Permissible values
PARMGEN name
GBL_DSN_CEE_SCEESPC
Description
This is the name of the LE/370 system programmer’s C facility.
Related parameters
None
GBL_DSN_CICS_CTG_DLL
This parameter is the name of the CICS TG Dynamic Link Library.
85
Required
Panel name
Specify Configuration Parameters
Panel ID
KGW41P1
Field
CICS TG DLL DSN
Default value
SYS1.SCTGDLL
Permissible values
KGW_CTG_DLL_DSN
PARMGEN name
GBL_DSN_CICS_CTG_DLL
Description
This is the name of the CICS TG Dynamic Link Library.
Related parameters
None
GBL_DSN_CICS_SCTGSID
This PARMGEN-only parameter contains the name of the CICS TG side-deck library.
Optional
Default value
CTG.V8R0M0.SCTGSID
Permissible values
PARMGEN name
GBL_DSN_CICS_SCTGSID
Description
This is the name of the CICS TG side-deck library.
Related parameters
None
GBL_DSN_CICS_SDFHC370
This PARMGEN-only parameter contains the name of the CICS load libraries for C support.
Optional
Default value
DFH.V4R2M5P.SDFHC370
Permissible values
86
PARMGEN name
GBL_DSN_CICS_SDFHC370
Description
This is the name of the CICS load libraries for C support.
Related parameters
None
GBL_DSN_CICS_SDFHLOAD
This parameter contains the name of the CICS load libraries.
Optional
Default value
DFH.V4R2M5P.SDFHLOAD
Permissible values
PARMGEN name
GBL_DSN_CICS_SDFHLOAD
Description
This is the CICS load library, as described by the SDFHLOAD low-level qualifier in the IBM CICS
documentation.
Related parameters
None
GBL_DSN_CSF_SCSFMOD0
This PARMGEN-only parameter contains the ICSF load library that contains the CSNB* modules used for
password encryption (if ICSF is installed and configured on the z/OS system).
Required if password encryption is to be enabled
KDS_CMS_SEC_ICSF_LOADLIB
PARMGEN name
GBL_DSN_CSF_SCSFMOD0
Description
ICSF load library that contains the CSNB* modules used for password encryption (if ICSF is
installed and configured on the z/OS system).
Related parameters
v “KDS_TEMS_SECURITY_KAES256_ENCKEY” on page 214
GBL_DSN_DB2_DSNEXIT
This parameter contains the name of the DB2 exit library.
Optional
87
Panel name
OMEGAMON XE for DB2 PE - DB2 libraries
Panel ID
KD261P0
Field
Specify a DB2 exit library
Default value
DSN.V9R1M0.DSNEXIT
Permissible values
KD2_OMPE_DB2EXIT
PARMGEN name
GBL_DSN_DB2_DSNEXIT
Description
The name of the data set in which the DB2 exit load modules reside that should be used by the
OMEGAMON collector.
Related parameters
v “GBL_DSN_DB2_LOADLIB_Vn”
v “GBL_DSN_DB2_RUNLIB_Vn” on page 89
GBL_DSN_DB2_LOADLIB_Vn
This parameter contains the name of the load library for the version of DB2 your site is running.
Required
Panel name
Panel ID
KD261P0
Field
Specify DB2 load libraries
Default value
DSN.Vn.SDSNLOAD
Permissible values
KD2_OMPE_DB2LOADLIB_Vn
PARMGEN name
GBL_DSN_DB2_LOADLIB_Vn
Description
The name of the dataset in which the DB2 load modules reside. Specify one DB2 load library for
each DB2 subsystem version that you want to monitor.
Related parameters
v “GBL_DSN_DB2_DSNEXIT” on page 87
v “GBL_DSN_DB2_RUNLIB_Vn” on page 89
88
GBL_DSN_DB2_RUNLIB_Vn
This parameter contains the name of the run library for the version of DB2 your site is running.
Required
Panel name
Panel ID
KD261P0
Field
Specify DB2 run libraries
Default value
DSN.Vn.RUNLIB
Permissible values
KD2_OMPE_DB2RUNLIB_Vn
PARMGEN name
GBL_DSN_DB2_RUNLIB_Vn
Description
The name of the dataset in which the DB2 RUNLIB load modules reside. Specify one DB2 run
library for each DB2 subsystem version that you want to monitor. This library should contain the
modules DSNTIAD and DSNTIAUL to be used to run in batch. The run library is used to
generate GRANT and BIND jobs that prepare the DB2 subsystems for monitoring.
Related parameters
v “GBL_DSN_DB2_DSNEXIT” on page 87
v “GBL_DSN_DB2_LOADLIB_Vn” on page 88
GBL_DSN_DB2_SDSNLOAD
This parameter contains the name of the DB2 load library.
N/A
Panel name
Specify Configuration Values
Panel ID
KDO18P2
Field
Load library: DB2 (DSNLOAD)
Default value
DSN.Vn.SDSNLOAD
Permissible values
KDO_DB2_LOADLIB
KMC_CFG_MCDB2_LIB
89
PARMGEN name
GBL_DSN_DB2_SDSNLOAD
Description
The name of the data set in which the DB2 load modules reside.
GBL_DSN_HZSPROC_LOADLIB
This parameter contains the name of a load library that is usable by the Health Checker started task
HZSPROC for assembling and linking health check modules.
Optional
Panel name
Generate Health Check Configuration Parameters
Panel ID
KCIPHCK1
Field
DSNAME
Default value
USER.LOADLIB
Permissible values
RTE_HCK_LOADLIB
PARMGEN name
GBL_DSN_HZSPROC_LOADLIB
Description
Name of a load library that is usable by the Health Checker started task HZSPROC for
assembling and linking health check modules. This library can be in the HZSPROC STEPLIB or it
can be a library in LNKLIST.
Related parameters
v “GBL_DSN_SYS1_SAXREXEC” on page 96
v “RTE_HCK_STC_INTERVAL” on page 110
GBL_DSN_IMS_RESLIB
This parameter contains the name of the IMS RESLIB BMP interface.
Optional
Panel name
IMS Subsystems Monitored
Panel ID
KI541P2
Field
Specify the IMS.RESLIB
Default value
DFS.V12R0M0.SDFSRESL
90
Permissible values
Batch parameter names
KI5_IMS_RESLIB
KI2_CLA_BMP_RESLIB
KI2_I1_CLA_IMS_RESLIB
PARMGEN name
GBL_DSN_IMS_RESLIB
Description
The IMS.RESLIB library contains the CQSREG00 action module required to enable the Common
Queue Server. The CQS and shared queues allow users to take advantage of the Parallel Sysplex
environment.
Related parameters
None
GBL_DSN_IMS_SCEXLINK
This parameter contains the name of the IMS Connect product load library.
Optional
Panel name
Job Names of Monitored IMS Connects
Panel ID
KI541PO4
Field
IMS.SCEXLINK
Default value
IMS.SCEXLINK
Permissible values
KI5_ICT_SCEXLINK
KI5_X_ICT_IMS_CONNECT_FLAG
PARMGEN name
GBL_DSN_IMS_SCEXLINK
Description
This specifies the IMS.SCEXLINK library. OMEGAMON XE for IMS on z/OS uses the IMS
Connect Extensions Publisher API. The IMS Connect Extensions product and functional support
libraries are required for the OMEGAMON XE for IMS agent to connect to and collect
performance and statistics data from the IMS Connect address space.
Related parameters
None
GBL_DSN_IMS_SFUNLINK
This parameter contains the name of the IMS Connect functional load library.
91
Optional
Panel name
Job Names of Monitored IMS Connects
Panel ID
KI541PO4
Field
IMS.SFUNLINK
Default value
IMS.SFUNLINK
Permissible values
KI5_ICT_SFUNLINK
KI5_X_ICT_IMS_CONNECT_FLAG
PARMGEN name
GBL_DSN_IMS_SFUNLINK
Description
OMEGAMON XE for IMS on z/OS uses the IMS Connect Extensions Publisher API. The IMS
Connect Extensions product and functional support libraries are required for the OMEGAMON
XE for IMS agent to connect to and collect performance and statistics data from the IMS Connect
address space.
Related parameters
None
GBL_DSN_ISP_SISPLOAD
This PARMGEN-only parameter contains the name of the library that contains ISPLINK (SISPLOAD for
ISPF Version 4 and above, or ISPLOAD for ISPF version 3 and below).
Optional
Default value
ISP.SISPLOAD
Permissible values
PARMGEN name
GBL_DSN_ISP_SISPLOAD
Description
This gives the name of the ISPF load library.
Related parameters
None
GBL_DSN_NETVIEW_CNMLINK
This parameter contains the name of the IBM Tivoli NetView CNMLINK load library, required for
NetView authorization of Take Action commands.
92
Optional
KNA_NETV_LNKLIB
PARMGEN name
GBL_DSN_NETVIEW_CNMLINK
Default value
NETVIEW.VnRnMn.CNMLINK
Description
Name of the IBM Tivoli NetView CNMLINK load library, required for NetView authorization of
Take Action commands. Contact your NetView or z/OS system programmer for the CNMLINK
link library name, if necessary. The CNMLINK library must be APF-authorized.
Related parameters
v “KDS_PPI_RECEIVER” on page 190
v “KDS_PPI_SENDER” on page 191
GBL_DSN_SYS1_BRODCAST
This PARMGEN-only parameter contains the name of the TSO broadcast data set name.
Optional
Default value
SYS1.BRODCAST
Permissible values
PARMGEN name
GBL_DSN_SYS1_BRODCAST
Description
SEND stores messages in the broadcast data set, and LISTBC retrieves them from the broadcast
data set.
GBL_DSN_SYS1_CSSLIB
This PARMGEN-only parameter contains the name of the Unix System Services library.
Optional
Default value
SYS1.CSSLIB
Permissible values
PARMGEN name
GBL_DSN_SYS1_CSSLIB
Description
This library contains Assembler Callable Services.
Related parameters
None
93
GBL_DSN_SYS1_HSMLOGY
This parameter contains the name of the HSM LOGY dataset.
Optional
Panel name
HSM Log Analysis Options
Panel ID
KDF55PO
Field
HSM LOGY dataset
Default value
SYS1.HSMLOGY
Permissible values
KDF_HSM_LOG_DSN
PARMGEN name
GBL_DSN_SYS1_HSMLOGY
Description
HSM log analysis periodically scans the HSM LOGY data set for new messages.
Related parameters
None
GBL_DSN_SYS1_LINKLIB
This PARMGEN-only parameter contains the name of the SYSLIB link library.
Optional
Default value
SYS1.LINKLIB
Permissible values
PARMGEN name
GBL_DSN_SYS1_LINKLIB
Description
This is typically the SYS1.LINKLIB library in the OMEGAMON Classic security jobs.
Related parameters
None
GBL_DSN_SYS1_MACLIB
This PARMGEN-only parameter contains the name of a system macro library for installed components
and products.
Optional
94
Kpp_SYS1_MACLIB
PARMGEN name
GBL_DSN_SYS1_MACLIB
Default value
SYS1.MACLIB
Description
Name of a system macro library for installed components and products. To include more than
one system macro library, define more than one GBL_DSN_SYS1_MACLIBn parameter, with a
unique number substituted for n at the end of each parameter name (example:
GBL_DSN_SYS1_MACLIB1, GBL_DSN_SYS1_MACLIB2, and so on).
Related parameters
None
GBL_DSN_SYS1_MODGEN
This PARMGEN-only parameter contains the name of the System Macro Library.
Optional
Default value
SYS1.MODGEN
Permissible values
PARMGEN name
GBL_DSN_SYS1_MODGEN
Description
This is the name of the system macro library.
Related parameters
None
GBL_DSN_SYS1_PARMLIB
This PARMGEN-only parameter contains the name of the system parameter library for installed
components and products.
Required
KPP_ICS_DATASET
PARMGEN name
GBL_DSN_SYS1_PARMLIB
Default value
SYS1.PARMLIB
Description
Name of the system parameter library for installed components and products.
Related parameters
None
95
GBL_DSN_SYS1_PROCLIB
This parameter contains the name of the system library that is to contain the started tasks and
procedures.
Panel name
Generate Sample System Copy JCL
Panel ID
KCIPSYSP
Field
System procedure
Default value
SYS1.PROCLIB
Permissible values
RTE_SYS_PROCLIB
PARMGEN name
GBL_DSN_SYS1_PROCLIB
Description
Name of the system library that is to contain the started tasks and procedures. You can specify
any system library if you do not want to update your PROCLIB library directly.
Related parameters
None
GBL_DSN_SYS1_SAXREXEC
This PARMGEN-only parameter contains the name of the system library where the Health Checker REXX
code is stored.
Optional
PARMGEN name
GBL_DSN_SYS1_SAXREXEC
Default value
SYS1.SAXREXEC
Description
Name of the system library where the Health Checker REXX code is stored.
Related parameters
v “GBL_DSN_HZSPROC_LOADLIB” on page 90
v “RTE_HCK_STC_INTERVAL” on page 110
GBL_DSN_SYS1_SBLSCLI0
This PARMGEN-only parameter contains the name of the system library that contains interactive problem
control system (IPCS) CLISTs and REXX execs.
Optional
96
PARMGEN name
GBL_DSN_SYS1_SBLSCLI0
Default value
SYS1.SBLSCLI0
Description
Name of the system library that contains interactive problem control system (IPCS) CLISTs and
REXX execs.
Related parameters
None
GBL_DSN_SYS1_SBPXEXEC
This parameter is the z/OS UNIX System Services (USS) CLIST/EXEC library name.
Required
N/A
Panel name
TEMS: Specify TEMS Self-Describing Agent Values
Agents: Specify Linkedit Libraries
Panel ID
KDS62PP4
KD471PPM
KQI70PLE
Field
USS CLIST library
Default value
SYS1.SBPXEXEC
Permissible values
TEMS: KDS_USS_EXEC
Agents: Kpp_USS_EXEC
PARMGEN name
GBL_DSN_SYS1_SBPXEXEC
Description
This is the z/OS USS CLIST/EXEC library that contains the oshell command to perform the
symbolic link. These are described by the SBPXEXEC low-level qualifier in the IBM z/OS UNIX
System Services documentation.
Related parameters
v
v
v
v
“KDS_KMS_SDA” on page 167
“KDS_TEMA_SDA” on page 196
“KPP_AGT_TEMA_SDA” on page 33
“GBL_HFS_JAVA_DIRn” on page 103
97
GBL_DSN_SYS1_SISTMAC1
This parameter contains the name of the system library that contains the VTAM macros.
Optional
Panel name
Create LU6.2 Logmode
Panel ID
KDS62PLU
Field
IBM VTAM macro library
Default value
SYS1.SISTMAC1
Permissible values
KDS_CMS_VTM_MACLIB
PARMGEN name
GBL_DSN_SYS1_SISTMAC1
Description
Name of the system library that contains the VTAM macros. The default is SYS1_SISTMAC1.
Related parameters
None
GBL_DSN_SYS1_VTAMLIB
This parameter contains the name of the system library that contains the VTAM logmode tables.
Optional
Panel name
Panel ID
KDS62PLU
Field
VTAM load library
Default value
SYS1.VTAMLIB
Permissible values
KDS_CMS_VTM_LOADLIB
PARMGEN name
GBL_DSN_SYS1_VTAMLIB
Description
Name of the system library that contains the VTAM logmode tables.
98
Related parameters
v “RTE_VTAM_LU62_MODETAB” on page 150
GBL_DSN_SYS1_VTAMLST
This parameter contains the name of the system VTAMLST library.
Required
Panel name
Generate Sample System Copy JCL
Panel ID
KCIPSYSP
Field
System VTAMLST
Default value
SYS1.VTAMLST
Permissible values
RTE_SYS_VTAMLST
PARMGEN name
GBL_DSN_SYS1_VTAMLST
Description
Name of the system VTAMLST library.
Related parameters
v “RTE_VTAM_NETID” on page 151
GBL_DSN_TCP_ETC_SERVICES
This PARMGEN-only parameter contains the name of the TCP/IP network services.
Optional
Default value
TCPIP.ETC.SERVICES
Permissible values
PARMGEN name
GBL_DSN_TCP_ETC_SERVICES
Description
TCP/IP network services such as NIS, DNS, and the /etc/hosts file.
Related parameters
None
GBL_DSN_TCP_SEZACMTX
This PARMGEN-only parameter contains the name of the TCP/IP load libraries.
99
Optional
Default value
EZA.SEZACMTX
Permissible values
PARMGEN name
GBL_DSN_TCP_SEZACMTX
Description
This is the TCP/IP load library for linking user modules and programs, as described for the
SEZACMTX low-level qualifier in the IBM TCP/IP for z/OS documentation. This is a required
field if any of the directory services use TCP/IP communications, such as a directory service that
has been configured as a directory server.
Related parameters
None
GBL_DSN_TCP_SEZARNT1
This PARMGEN-only parameter contains the name of the TCP/IP Reentrant Object Module Library.
Optional
Default value
EZA.SEZARNT1
Permissible values
PARMGEN name
GBL_DSN_TCP_SEZARNT1
Description
This is the TCP/IP Reentrant object module library for linking user modules and programs, as
described for the SEZARNT1 low-level qualifier in the IBM TCP/IP for MVS documentation. This
is a required field if any of the directory services use TCP/IP communications, such as a
directory service that has been configured as a directory server.
Related parameters
None
GBL_DSN_TCP_SEZATCP
This PARMGEN-only parameter contains the name of the TCP/IP executable libraries.
Optional
Default value
EZA.SEZATCP
Permissible values
PARMGEN name
GBL_DSN_TCP_SEZATCP
Description
This is the TCP/IP executable load library used for STEPLIB or LINKLIB concatenation, as
100
described for the SEZATCP low-level qualifier in the IBM TCP/IP for MVS documentation. This
is a required field if any of the directory services use TCP/IP communications, such as a
directory service that has been configured as a directory server.
Related parameters
None
GBL_DSN_TCP_SYSTCPD_TCPDATA
This parameter contains the name of the system library to use in obtaining the parameters defined by
TCPIP.DATA when no GLOBALTCPIPDATA statement is configured.
Optional
Default value
TCPIP.SEZAINST
Kpp_TCP_DATA
PARMGEN name
GBL_DSN_TCP_SYSTCPD_TCPDATA
Description
Name of the system library to use in obtaining the parameters defined by TCPIP.DATA when no
GLOBALTCPIPDATA statement is configured. If IP domain name resolution is not fully
configured on the z/OS system, SYSTCPD must be supported by the monitoring server and
monitoring agents on z/OS.
Related parameters
None
This parameter contains the name of the TCP/IP data file.
Required
Panel name
SPECIFY COMPONENT CONFIGURATION (Page 1)
Panel ID
KN341P2
Field
TCP/IP data file
Default value
TCPIP.SEZAINST(TCPDATA)
Permissible values
Character string, maximum length 54 (with the member name).
Kpp_TCP_DATA
PARMGEN name
Description
This specifies the data set name of the library described in the z/OS Communications Server IP
101
Configuration Reference", section "Configuration Datasets", which provides parameters for TCP/IP
client programs. Specify this dsname if your site is running z/OS V1R4 or above.
Related parameters
None
GBL_DSN_WMQ_SCSQANLE
This parameter contains the name of the IBM WebSphere MQ language library.
Optional
Panel name
Panel ID
KMC70PPM
KMQ70PPM
Field
IBM-supplied WebSphere MQ language library
Default value
IBM.WMQ.SCSQANLE
Permissible values
Kpp_MQS_LANGLIB
PARMGEN name
GBL_DSN_WMQ_SCSQANLE
Description
This is the IBM-supplied library that provides national language support.
Related parameters
None
GBL_DSN_WMQ_SCSQAUTH
This parameter contains the name of the IBM WebSphere MQ authorized load library.
Required
Panel name
Panel ID
KMC70PPM
KMQ70PPM
KQI70PLE
Field
IBM-supplied WebSphere MQ authorized load library
Default value
IBM.WMQ.SCSQAUTH
102
Permissible values
Kpp_MQS_AUTHLIB
PARMGEN name
GBL_DSN_WMQ_SCSQAUTH
Description
This is the IBM-supplied library that contains the WebSphere MQ API modules required to
execute OMEGAMON XE for WebSphere MQ. The data set name you specify here will be added
to the started task JCL.
Related parameters
v “GBL_DSN_WMQ_SCSQANLE” on page 102
v “GBL_DSN_WMQ_SCSQLOAD”
GBL_DSN_WMQ_SCSQLOAD
This parameter contains the name of the WebSphere MQ load library.
Required
Panel name
Panel ID
KQI70PLE
Field
Load library (SCSQLOAD)
Default value
IBM.WMQ.SCSQLOAD
Permissible values
KQI_MQS_LOADLIB
PARMGEN name
GBL_DSN_WMQ_SCSQLOAD
Description
This is the WebSphere MQ load library that contains load modules for non-APF code, user exits,
utilities, samples, installation verification programs, and adapter stubs.
Related parameters
v “GBL_DSN_WMQ_SCSQAUTH” on page 102
GBL_HFS_JAVA_DIRn
This parameter contains the name of the Java home directory.
Required
The TEMS_JAVA_BINPATH parameter in the RKANDATV data set, member KDSDPROF.
103
Panel name
Specify TEMS Self-Describing Agent Values
Panel ID
KDS62PP4
Field
JavaRoot home directory for TEMS_JAVA_BINPATH
Default value
/usr/lpp/java/IBM/J6.0
Permissible values
KDS_HFS_JAVA_DIRn
PARMGEN name
GBL_HFS_JAVA_DIRn
Description
The name of the Java home directory. The default is /usr/lpp/java/IBM/J6.0. This directory must
begin with a "/".
Related parameters
v “KPP_AGT_TEMA_SDA” on page 33
GBL_INST_HILEV
This PARMGEN-only parameter contains the high-level qualifier (shilev) of the installation libraries
(INSTJOBS, INSTDATA, and so on).
Required
PARMGEN name
GBL_INST_HILEV
Description
High-level qualifier (shilev) of the installation libraries (INSTJOBS, INSTDATA, and so on).
Related parameters
v “GBL_TARGET_HILEV”
GBL_TARGET_HILEV
This PARMGEN-only parameter contains the high-level qualifier (thilev) of the target libraries that were
installed by SMP/E (for example, TKANDATV and TKANMOD).
Required
PARMGEN name
GBL_TARGET_HILEV
104
Description
High-level qualifier (thilev) of the target libraries that were installed by SMP/E (for example,
TKANDATV and TKANMOD).
Related parameters
v “GBL_INST_HILEV” on page 104
GBL_USER_JCL
This PARMGEN-only parameter contains the user JCL library where the KCIJPCFG PARMGEN
configuration job is to be customized.
Required
PARMGEN name
GBL_USER_JCL
Description
User JCL library where the KCIJPCFG PARMGEN configuration job is to be customized.
Related parameters
None
105
106
Chapter 4. Runtime environment (RTE) parameters
The runtime environment parameters provide configuration settings for an individual runtime
environment and default settings for the OMEGAMON components and products configured in that
runtime environment, including the end-to-end response-time analysis feature.
The runtime environment parameters are explained in this section.
RTE_BASE_NAME
This parameter contains the mid-level qualifier for base runtime library allocations.
Optional
Panel name
Add Runtime Environment
Panel ID
KCIPRTAB
Field
Mid-level qualifier
Default value
Base runtime environment name
Permissible values
RTE_BASE_MIDLEV
PARMGEN name
RTE_BASE_NAME
Description
Mid-level qualifier for base runtime library allocations. Accept the default value (the base runtime
environment name), even though this parameter is modifiable for base runtime environments. For
full and sharing runtime environments, the mid-level qualifier is set to the runtime environment
name (RTE_NAME parameter value) and cannot be changed.
Related parameters
v “RTE_NAME” on page 117
v “RTE_TYPE” on page 145
v “RTE_HILEV” on page 110
v “RTE_VSAM_HILEV” on page 148
RTE_CANSCN_STC
This parameter gives the name of the Candle subsystem started task.
Optional
107
Panel name
Panel ID
KCNPPR1
Field
Started task
Default value
CANSCN
Permissible values
RTE_CAN_SS_STC
PARMGEN name
RTE_CANSCN_STC
Description
This is the name of the started task that will be constructed for the Candle subsystem.
Related parameters
v “RTE_KCNSTR00_SSID” on page 113
v “RTE_KCNSTR00_XCFGROUP” on page 114
v “RTE_KCNSTR00_WTO” on page 113
v “RTE_KCNDLSSI_IEFSSN00_FORMAT” on page 112
v “RTE_X_KCNSTR00_REFRESH” on page 153
v “RTE_X_KCNSTR00_PLEXCOLLECT” on page 152
v “RTE_X_KCNDLSSI_INITPARM_FLAG” on page 151
RTE_CANSETE_STC
This parameter contains the name of the started task that measures end-to-end response-time
performance.
Optional
Panel name
Specify Configuration values
Panel ID
KC256PR
KI256PP
KM255P1
Field
End-to-End (ETE)
Default value
CANSETE
Permissible values
RTE_ETE_STC
PARMGEN name
RTE_CANSETE_STC
108
Description
The started task name for the end-to-end server.
Related parameters
None
RTE_DEBUG_SYSOUT
This parameter contains the SYSOUT class for diagnostic output DDNAMEs, such as SYSUDUMP and
SYSABEND, in generated JCL.
Required
Panel name
v (For a base runtime environment) Add Runtime Environment
v (For a full or sharing runtime environment) Add Runtime Environment (1 of 3)
Panel ID
v (For a base runtime environment) KCIPRTAB
v (For a full or sharing runtime environment) KCIPRTEA
Field
Diagnostic SYSOUT class
Default value
X
Permissible values
1 character
RTE_DEBUG_SYSOUT
PARMGEN name
RTE_DEBUG_SYSOUT
Description
SYSOUT class for diagnostic output DDNAMEs, such as SYSUDUMP and SYSABEND, in
generated JCL.
Related parameters
v “RTE_LOG_SYSOUT” on page 116
RTE_DESCRIPTION
This parameter contains the description of the runtime environment.
Optional
Panel name
Runtime Environments (RTEs)
Panel ID
KCIPRTE
Field
Description
Default value
None
109
Permissible values
RTE_DESC
PARMGEN name
RTE_DESCRIPTION
Description
Description of the runtime environment.
Related parameters
v “RTE_SHARE” on page 128
RTE_HCK_STC_INTERVAL
This parameter contains the Interval (in minutes) for running a health check to verify that all started
tasks configured for a runtime environment are running.
Optional
Panel name
Generate Health Check Configuration Parameters
Panel ID
KCIPHCK1
Field
Interval
Default value
30
Permissible values
10 - 1440
RTE_HCK_INTERVAL
PARMGEN name
RTE_HCK_STC_INTERVAL
Description
Interval (in minutes) for running a health check to verify that all started tasks configured for a
runtime environment are running.
Related parameters
v “GBL_DSN_HZSPROC_LOADLIB” on page 90
v “GBL_DSN_SYS1_SAXREXEC” on page 96
RTE_HILEV
This parameters contains the non-VSAM high-level qualifier to be used for allocating the runtime data
sets.
Required
110
Panel name
Panel ID
Field
High-level Qualifier (Non-VSAM)
Default value
None
Permissible values
RTE_HILEV
PARMGEN name
RTE_HILEV
Description
Non-VSAM high-level qualifier to be used for allocating the runtime data sets. If you plan to
allocate SMS-managed data sets for the runtime environment, the high-level qualifier that you
specify must be eligible for SMS-managed volumes.
For PARMGEN configuration, the value of this parameter for a sharing runtime environment
must be the same as the value for the shared runtime environment. For detailed information
about sharing and shared runtime environments, see the "Planning your deployment" chapter of
IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: Common Planning and
Related parameters
v “RTE_BASE_NAME” on page 107
RTE_JCL_SUFFIX
This parameter contains the unique JCL suffix to identify the batch job members created by the
Configuration Tool for this runtime environment in the shilev.INSTJOBS data set.
Required
Panel name
Panel ID
Field
JCL suffix
111
Default value
None
Permissible values
RTE_JCL_SUFF
PARMGEN name
RTE_JCL_SUFFIX
Description
Unique JCL suffix to identify the batch job members created by the Configuration Tool for this
runtime environment in the shilev.INSTJOBS data set.
If possible, specify the runtime environment name (or an abbreviated version of the runtime
environment name) as the JCL suffix. This setup makes it easy to identify the runtime
environment associated with each job generated by the Configuration Tool and stored in the
INSTJOBS data set.
Related parameters
None
This parameter contains the IEFSSN00 format.
Optional
Panel name
Specify Configuration values
Panel ID
KCNPPR1
Field
IEFSSN00 format
Default value
K
Permissible values
P, K
RTE_CAN_SS_IEFSSN_FMT
PARMGEN name
Description
This field specifies the format found in the IEFSSN00 member in the PARMLIB dataset. This
member can have one of two formats:
Keyword
format allows for dynamic subsystem processing. This is the preferred format for this
member when your version of z/OS allows it. Specify K for this field if the member is in
Keyword format.
Positional
format is for compatibility. Specify P for this field if the member appears as follows:
CNDL,KCNDLINT,’SSPROC=CANSCN’
112
Although both formats can be used, z/OS requires that all the commands in a single
concatenation member follow the same format.
Related parameters
v “RTE_KCNSTR00_SSID”
v “RTE_KCNSTR00_WTO”
RTE_KCNSTR00_SSID
This parameter contains the Candle subsystem ID.
Optional
Panel name
Panel ID
KCNPPR1
Field
Subsystem ID
Default value
CNDL
Permissible values
RTE_CAN_SSID
PARMGEN name
RTE_KCNSTR00_SSID
Description
This field specifies the four-character identifier of the Candle subsystem. The Candle subsystem is
shipped with a predefined ID set to CNDL. If you change this value, be sure that all references to
the subsystem ID in other products configured in this runtime environment are consistent with
this value.
Related parameters
v “RTE_CANSCN_STC” on page 107
v “RTE_KCNSTR00_WTO”
RTE_KCNSTR00_WTO
This parameter writes the IXCQUERY message to the z/OS console.
Optional
Panel name
113
Panel ID
KCNPPR1
Field
IXCQUERY WTO message
Default value
ERROR
Permissible values
NO, ALL, ERROR
RTE_CAN_SS_WTO
PARMGEN name
RTE_KCNSTR00_WTO
Description
This field specifies the IXCQUERY WTO messaging mode to determine if warning and error
messages will be written to the z/OS operator console. It allows error, warnings, and key
informational messages from the Candle subsystem that are associated with the Coupling Facility
Collection enhancement. It also allows automation to take action for problem conditions. All
Candle subsystems within a sysplex must have the same value for this parameter.
Error
is the default.
All
allows warning, error, and full diagnostic processing messages that are associated with
the Coupling Facility Collection enhancement.
No
prevents all messages from the Candle subsystem that are associated with the Coupling
Facility Collection enhancement from being written to the z/OS operator console.
Related parameters
v “RTE_KCNSTR00_XCFGROUP”
RTE_KCNSTR00_XCFGROUP
This parameter contains the Candle subsystem XCF group name.
Optional
Panel name
Panel ID
KCNPPR1
Field
XCF group name
Default value
KCNXCFCF
Permissible values
RTE_CAN_SS_XCF_GRP
114
PARMGEN name
RTE_KCNSTR00_XCFGROUP
Description
This is the XCF group name to be used by the Candle subsystems to share collected data within a
sysplex. This value must be a unique name for this sysplex conforming to the naming rules for
XCF groups (characters comprising alphabetics, numerals, and national characters). Every Candle
subsystem configured within a sysplex must use the same value.
Related parameters
RTE_LOAD_OPTIMIZE
The parameter determines whether to optimize the loading of the runtime environment after maintenance
is applied or products are reconfigured.
Required
Panel name
Panel ID
Field
Load optimization
Default value
N
Permissible values
Y or N
RTE_LOAD_OPTIMIZE
PARMGEN name
RTE_LOAD_OPTIMIZE
Description
Determines whether to optimize the loading of the runtime environment after maintenance is
applied or products are reconfigured. (Load optimization takes effect on the second and
subsequent load operations but not on the initial loading.)
If
v
v
v
v
you specify Y, the load job has the following characteristics:
Copies only modified modules from target to runtime libraries.
Requires access to IBM's SuperC (ISRSUPC) utility.
Uses less DASD space.
Performs additional analysis, which uses more CPU processing and file I/O.
If you specify N (the default), the load job has the following characteristics:
v Copies all members from target to runtime libraries, whether or not they were modified.
v Requires more DASD space.
115
v Uses less CPU time.
Related parameters
None
RTE_LOAD_SHARED_LIBS
This parameter determines whether to include the shared libraries of a base or full runtime environment
in the Load job of a sharing-with-base or sharing-with-full runtime environment.
Required
Panel name
Confirmation - Load Shared RTE Datasets
Panel ID
KCIPSHLD
Field
Do you want to include these datasets in the RTE Load?
Default value
Y
Permissible values
Y or N
PARMGEN name
Description
Determines whether to include the shared libraries of a base or full runtime environment in the
Load job of a sharing-with-base or sharing-with-full runtime environment. Accept the default
value (Y) to ensure that all maintenance is loaded properly into the runtime environment.
Related parameters
RTE_LOG_SYSOUT
This parameter contains the SYSOUT class for non-diagnostic output DDNAMEs, such as RKPDLOG, in
generated JCL.
Required
Panel name
Panel ID
Field
116
SYSOUT class
Default value
X
Permissible values
1 character
RTE_LOG_SYSOUT
PARMGEN name
RTE_LOG_SYSOUT
Description
SYSOUT class for non-diagnostic output DDNAMEs, such as RKPDLOG, in generated JCL.
Related parameters
v “RTE_DEBUG_SYSOUT” on page 109
RTE_NAME
This parameter contains the unique name that identifies the runtime environment.
Required
Panel name
Panel ID
KCIPRTE
Field
Name
Default value
None
Permissible values
RTE_NAME
PARMGEN name
RTE_NAME
Description
Unique name that identifies the runtime environment. This name is appended to the high-level
qualifiers specified in the “RTE_HILEV” on page 110 and “RTE_VSAM_HILEV” on page 148
parameters, to make each set of runtime libraries unique.
Related parameters
RTE_PDS_BATCHINIT_FLAG
This PARMGEN-only parameter determines if the BATCHINIT parameter is generated in the
&rhilev.&rte.RKANSAMU(KppPCTL) Persistent Datastore RKPDIN DD command EXEC startup member.
rte_pds_batchinit_flag
117
Optional
Value determines if the BATCHINIT parameter is generated in the &rhilev.
&rte.RKANSAMU(KppPCTL) Persistent Datastore RKPDIN DD command EXEC startup member.
BATCHINIT if the flag is Y. Syntax is: MAINTPRC PROC=KPDPROC1 GENPROC BATCHINIT
Default value
N
Permissible values
Y, N
PARMGEN name
RTE_PDS_BATCHINIT_FLAG
Description
This parameter determines if the BATCHINIT parameter is generated in the &rhilev.
&rte.RKANSAMU(KppPCTL) Persistent Datastore RKPDIN DD command EXEC startup member.
Determines the Persistent Datastore (PDS) settings for xKANPARU(KppPCTL),
xKANPARU(KppPG), xKANPARU(KppDEFIN) and xKANPARU(KppAL) Persistent Datastore
control member options.
Related parameters
v “KPP_X_PD_HISTCOLL_DATA_AGT_STC” on page 79
v “KPP_X_PD_HISTCOLL_DATA_TEMS_STC” on page 79
v “RTE_PDS_BACKUP_FLAG”
v
v
v
v
v
“RTE_PDS_BATCHINIT_FLAG” on page 117
“RTE_PDS_EXPORT_FLAG” on page 119
“RTE_PDS_EXTRACT_FLAG” on page 120
“RTE_PDS_FILE_COUNT” on page 120
“RTE_PDS_HILEV” on page 121
RTE_PDS_BACKUP_FLAG
This parameter determines whether to perform backup operations on data sets used by the persistent
data store.
Optional
118
Panel name
Panel ID
KPD62PP3
Field
Backup
Default value
N
Permissible values
Y or N
RTE_PDS_BU
PARMGEN name
RTE_PDS_BACKUP_FLAG
Description
Determines whether to perform backup operations on data sets used by the persistent data store.
Backups enable you to keep a copy of the data sets on either tape or DASD. You can then make
the data available to the persistent data store again whenever you want.
For detailed information on maintaining the persistent data store, see IBM Tivoli OMEGAMON
XE and Tivoli Management Services on z/OS: Common Planning and Configuration Guide.
Related parameters
v “RTE_PDS_EXPORT_FLAG”
RTE_PDS_EXPORT_FLAG
This parameter determines whether to export data sets used by the persistent data store.
Optional
Panel name
Panel ID
KPD62PP3
Field
Export
Default value
N
Permissible values
Y or N
RTE_PDS_EXP
PARMGEN name
RTE_PDS_EXPORT_FLAG
Description
Determines whether to export data sets used by the persistent data store. The Export option
converts the data sets to flat (ASCII) files in an internal format that can be used by other
119
applications. The exported data can also be used for recovery when the persistent data store
detects potential problems with its data. To make the exported file available to the persistent data
store program again requires the restore program, KPDREST, to be run against the exported data.
Related parameters
v “RTE_PDS_EXTRACT_FLAG”
RTE_PDS_EXTRACT_FLAG
This parameters determines whether to write the data to a flat file in human-readable form, which is
suitable for loading into other database management systems.
Optional
Panel name
Panel ID
KPD62PP3
Field
Extract
Default value
N
Permissible values
Y or N
RTE_PDS_EXT
PARMGEN name
RTE_PDS_EXTRACT_FLAG
Description
Determines whether to write the data to a flat file in human-readable form, which is suitable for
loading into other database management systems. The data is extracted from a full data set in
EBCDIC form, but the extraction does not empty the data set. The data set is not initialized until
it becomes a candidate for being emptied, so the most current data becomes available in an
extracted form without that data being lost.
Related parameters
RTE_PDS_FILE_COUNT
This parameter contains the number of historical data sets in the group defined by the Kpp_PD_GRP
parameter.
120
Optional
Panel name
Panel ID
KPD62PP3
Field
Count
Default value
3
Permissible values
See Description.
RTE_PDS_CNT
PARMGEN name
RTE_PDS_FILE_COUNT
Description
Number of historical data sets in the group defined by the Kpp_PD_GRP parameter.
The value specified for this parameter is applied to every product configured in the runtime
environment. The default value is 3, but the best value for the following products is 7:
v IBM Tivoli OMEGAMON XE for CICS® on z/OS
v IBM Tivoli OMEGAMON XE for Mainframe Networks
v IBM Tivoli OMEGAMON XE on z/OS
Therefore, set a value of 7 if OMEGAMON XE for CICS on z/OS, OMEGAMON XE for
Mainframe Networks, or OMEGAMON XE on z/OS is to be configured in the runtime
environment.
Related parameters
v “KDS_PD_GRP” on page 179
v Product-specific Kpp_PD_GRP parameters
RTE_PDS_HILEV
This parameter contains the high-level qualifier for the persistent data store libraries.
Required
Panel name
Specify Persistent Datastore Values
Panel ID
KCIPIR4 or KDSPP3
Field
Datastore high-level prefix
Default value
rhilev.rte
Permissible values
121
RTE_PDS_HILEV
PARMGEN name
RTE_PDS_HILEV
Description
High-level qualifier for the persistent data store libraries.
Related parameters
None
RTE_PDS_KPDPROC_PREFIX
This parameter contains the prefix of the started task name that will be used to perform maintenance on
the data sets written by the persistent data store.
Required
Panel name
Panel ID
KCIPIR4 or KDSPP3
Field
Maintenance procedure prefix
Default value
KPDPROC
Permissible values
RTE_PDS_PROC_PREF
PARMGEN name
RTE_PDS_KPDPROC_PREFIX
Description
Prefix of the started task name that will be used to perform maintenance on the data sets written
by the persistent data store. For detailed information on maintaining the persistent data store, see
Related parameters
RTE_PDS_SMS_MGMTCLAS
This parameter contains the SMS management class to be used for data set allocation for the persistent
data store.
Optional
122
Panel name
Panel ID
KCIPIR4 or KDSPP3
Field
Allocation MGMTCLAS
Default value
None
Permissible values
RTE_PDS_SMS_MGMT_CLAS
PARMGEN name
RTE_PDS_SMS_MGMTCLAS
Description
SMS management class to be used for data set allocation for the persistent data store.
Related parameters
v “RTE_PDS_SMS_STORCLAS”
RTE_PDS_SMS_STORCLAS
This parameters contains the SMS storage class to be used for data set allocation for the persistent data
store.
Optional
Panel name
Panel ID
KCIPIR4 or KDSPP3
Field
Allocation STORCLAS
Default value
None
Permissible values
RTE_PDS_SMS_STOR_CLAS
PARMGEN name
RTE_PDS_SMS_STORCLAS
Description
SMS storage class to be used for data set allocation for the persistent data store.
Related parameters
RTE_PDS_SMS_UNIT
This parameter contains the default unit for non-SMS data set allocation for the persistent data store.
123
Required if the runtime data sets are not to be managed by SMS; optional otherwise.
Panel name
Panel ID
KCIPIR4 or KDSPP3
Field
Allocation unit
Default value
None
Permissible values
RTE_PDS_UNIT
PARMGEN name
RTE_PDS_SMS_UNIT
Description
Default unit for non-SMS data set allocation for the persistent data store.
Related parameters
v “RTE_PDS_SMS_VOLUME”
RTE_PDS_SMS_VOLUME
This parameter contains the default volume serial number for non-SMS data set allocation for the
persistent data store.
Panel name
Panel ID
KCIPIR4 or KDSPP3
Field
Allocation volume
Default value
None
Permissible values
RTE_PDS_VOL
PARMGEN name
RTE_PDS_SMS_VOLUME
Description
Default volume serial number for non-SMS data set allocation for the persistent data store.
Related parameters
124
RTE_REMOTE_LPAR_FLAG
This parameter determines whether this runtime environment will be run on the local system (N, the
default) or transported to other systems (Y).
Required
Panel name
Panel ID
Field
Remote RTE for transport
Default value
N
Permissible values
Y or N
RTE_REMOTE
PARMGEN name
RTE_REMOTE_LPAR_FLAG
Description
Determines whether this runtime environment will be run on the local system (N, the default) or
transported to other systems (Y). If the value of this parameter is Y, the value of the
“RTE_USERMODS_FLAG” on page 146 parameter must be N, and vice versa.
Related parameters
v “RTE_USERMODS_FLAG” on page 146
RTE_SECURITY_CLASS
This parameter specifies a common System Authorization Facility (SAF) security class name for
OMEGAMON enhanced 3270 user interface security controls.
Optional
The RTE_SECURITY_CLASS parameter in the KPPENV member of the xKANPARU library.
Panel name
Add Runtime Environment
Panel ID
KCIPRTA1
Field
Global SAF class name
125
Default value
None. If this field is not specified, the RTE_SECURITY_CLASS parameter is generated as
a placeholder comment in the xKANPARU(KPPENV) member for components exploiting
this parameter.
Permissible values
A valid SAF class name, comprising a character string, maximum length 8. If using ACF2
as your external security resource manager, specify a maximum of 3 characters.
RTE_SECURITY_CLASS
PARMGEN name
RTE_SECURITY_CLASS
Description
Security validation processing by the OMEGAMON enhanced user interface: which validates the
user identity using the SAF interface. The existence of the SAF user and its validity (that is, not
suspended) are always checked.
Note:
1. Applies only to the OMEGAMON enhanced 3270 user interface and OMEGAMON XE/IBM
Tivoli Monitoring-based components that take advantage of the enhanced 3270 user interface.
2. The individual products have additional SAF security settings that are specific to them (for
example, how to secure product-specific Take Action requests); see the product-specific
documentation for information.
Related parameters
v “KDS_TEMS_DRA_FLAG” on page 198
v “KOB_TOM_STC” on page 259
v “KOB_TOM_VTAM_APPL_LOGON” on page 260
v “KOB_TOM_VTAM_NODE” on page 261
v “KPP_SECURITY_ACTION_CLASS” on page 48
This parameter determines whether mixed case passwords are supported and being used.
Required for full and sharing runtime environments; does not apply to base runtime
environments.
Panel name
Panel ID
KCIPRTA1
Field
Fold password to upper case
Default value
Y
Permissible values
Y or N
RTE_FOLD_PWD
126
PARMGEN name
Description
By default, TMS:Engine folds logon passwords 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 runtime environments. Accept the default value of Y for this parameter
For more information about the MIXEDCASE option in RACF, see the z/OS V1R8.0 Security Server
RACF Security Administrator's Guide.
Related parameters
v “RTE_SECURITY_USER_LOGON”
RTE_SECURITY_USER_LOGON
This parameters contains the security system to be used for the runtime environment.
Required
N/A
Various
Default value
None
Permissible values
RACF, ACF2, TSS, NAM, SAF, or None
Panel name
Panel ID
KCIPRTA1
Field
Security system
Default value
None
Permissible values
RACF, ACF2, TSS, NAM, or None
RTE_CUA_SECURITY
PARMGEN name
RTE_SECURITY_USER_LOGON
Description
Security system to be used for the runtime environment. If you specify a security system, verify
that it is installed and configured correctly for your site. 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.
127
The PARMGEN configuration method supports one additional permissible value: SAF. The System
Authorization Facility (SAF) provides a generic API to interface to z/OS security software.
Specifying a security system here indicates which system will be used for security validation of
users signing 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.
In addition, the security-related parameters are used in the PARMGEN WKANSAMU(KCIJPSEC)
composite security job and product-specific, stand-alone versions of these security jobs. They are
also used in several xKANPARU runtime members such as:
xKANPARU(KppINNAM)
for the TMS:Engine security member
xKANPARU(KDSENV)
for the KDS_TEMS_SECURITY_KDS_VALIDATE parameter
xKANPARU(KppENV)
for the RTE_SECURITY_CLASS parameter
xKANMODU(&module)
for product-specific security exits
Related parameters
v
v
v
v
v
“RTE_SECURITY_FOLD_PASSWORD_FLAG” on page 126
“RTE_X_SECURITY_EXIT_LIB” on page 154
“RTE_X_SECURITY_DATA_ABOVE” on page 154
“GBL_DSN_ACF2_MACLIB” on page 81
“RTE_SECURITY_CLASS” on page 125
v “KDS_TEMS_SECURITY_KDS_VALIDATE” on page 214
RTE_SHARE
This parameters contains the name of the base or full runtime environment from which the sharing
runtime environment obtains its base library information.
Required for a sharing runtime environment definition
Panel name
Panel ID
KCIPRTE
Field
Sharing
Default value
None
Permissible values
RTE_SHARE
PARMGEN name
RTE_SHARE
Description
Name of the base or full runtime environment from which the sharing runtime environment
obtains its base library information. If target libraries that were installed by SMP/E are to be
shared, provide the value SMP. This parameter applies to sharing runtime environments only.
128
Related parameters
RTE_SMS_MGMTCLAS
This parameter specifies whether the runtime data sets are to be managed by SMS.
Optional
Panel name
Panel ID
Field
Mgmtclas
Default value
None
Permissible values
RTE_SMS_MGMT_CLAS
PARMGEN name
RTE_SMS_MGMTCLAS
Description
If the runtime data sets are to be managed by SMS, specify the SMS management class to be used
for the allocation of non-VSAM data sets. If your site does not require the SMS MGMTCLAS
parameter, you can leave this field blank.
Related parameters
v “RTE_SMS_VSAM_MGMTCLAS” on page 132
v “RTE_SMS_STORCLAS” on page 130
RTE_SMS_PDSE_FLAG
This parameter specifies whether the non-VSAM data sets are to be managed by SMS, and therefore you
want to allocate PDSE data sets instead of PDS data set
Required
Panel name
Panel ID
129
Field
PDSE
Default value
N
Permissible values
Y or N
RTE_PDSE
PARMGEN name
RTE_SMS_PDSE_FLAG
Description
If the non-VSAM data sets are to be managed by SMS, you can specify Y to allocate PDSE data
sets instead of PDS data sets. PDSE data sets do not require compression and are not limited by a
predefined number of directory entries.
Even if you specify Y, most load module libraries (RKANMOD, RKANMODL, RKANMODR, and
RKANMODU) are not allocated as PDSE data sets. The main exception is RKANMODP, a load
module library used for the SMP/E CALLLIBS facility.
Related parameters
None
RTE_SMS_STORCLAS
This parameter specifies whether the runtime data sets are to be managed by SMS and therefore it is
necessary to specify the SMS storage class to be used for the allocation of non-VSAM data sets.
Optional
Panel name
Panel ID
Field
Storclas
Default value
None
Permissible values
RTE_SMS_STOR_CLAS
PARMGEN name
RTE_SMS_STORCLAS
Description
If the runtime data sets are to be managed by SMS, specify the SMS storage class to be used for
the allocation of non-VSAM data sets. If your site does not require the SMS STORCLAS
parameter, you can leave this parameter value blank.
Related parameters
130
v “RTE_SMS_VSAM_STORCLAS” on page 133
v “RTE_SMS_MGMTCLAS” on page 129
RTE_SMS_UNIT
This parameter specifies the unit name to be used for allocating the non-VSAM runtime data sets, if the
data sets are not managed by SMS.
Panel name
Panel ID
Field
Unit
Default value
None
Permissible values
RTE_UNIT
PARMGEN name
RTE_SMS_UNIT
Description
If the runtime data sets are not to be managed by SMS, specify the unit name to be used for
allocating the non-VSAM runtime data sets. Otherwise, leave the parameter value blank.
Related parameters
v “RTE_SMS_VOLUME”
RTE_SMS_VOLUME
This parameter specifies the volume serial numbers to be used for allocating the non-VSAM runtime data
sets if the runtime data sets are not to be managed by SMS.
Panel name
Panel ID
Field
Volser
131
Default value
None
Permissible values
RTE_VOL
PARMGEN name
RTE_SMS_VOLUME
Description
If the runtime data sets are not to be managed by SMS, specify the volume serial numbers to be
used for allocating the non-VSAM runtime data sets. Otherwise, leave the parameter value blank.
Related parameters
v “RTE_SMS_UNIT” on page 131
v “RTE_SMS_VSAM_VOLUME” on page 133
RTE_SMS_VSAM_MGMTCLAS
This parameter specifies the SMS management class to be used for the allocation of VSAM data sets, if
the runtime data sets are to be managed by SMS.
Optional
Panel name
Panel ID
Field
Mgmtclas
Default value
None
Permissible values
RTE_SMS_VSAM_MGMT_CLAS
PARMGEN name
RTE_SMS_VSAM_MGMTCLAS
Description
If the runtime data sets are to be managed by SMS, specify the SMS management class to be used
for the allocation of VSAM data sets. If your site does not require the SMS MGMTCLAS
parameter, you can leave this field blank.
Related parameters
v “RTE_SMS_MGMTCLAS” on page 129
v “RTE_SMS_VSAM_STORCLAS” on page 133
132
RTE_SMS_VSAM_STORCLAS
This parameter specifies the SMS storage class to be used for the allocation of VSAM data sets if the
runtime data sets are to be managed by SMS.
Optional
Panel name
Panel ID
Field
Storclas
Default value
None
Permissible values
RTE_SMS_VSAM_STOR_CLAS
PARMGEN name
RTE_SMS_VSAM_STORCLAS
Description
If the runtime data sets are to be managed by SMS, specify the SMS storage class to be used for
the allocation of VSAM data sets. If your site does not require the SMS STORCLAS parameter,
you can leave this field blank.
Related parameters
v “RTE_SMS_STORCLAS” on page 130
v “RTE_SMS_VSAM_MGMTCLAS” on page 132
RTE_SMS_VSAM_VOLUME
This parameter specifies the volume serial numbers to be used for allocating the VSAM runtime data sets,
if the runtime data sets are not managed by SMS.
Panel name
Panel ID
Field
Volser
133
Default value
None
Permissible values
RTE_VSAM_VOL
PARMGEN name
RTE_SMS_VSAM_VOLUME
Description
Volume serial numbers to be used for allocating the VSAM runtime data sets. This value is
required if the runtime data sets are not to be managed by SMS. Otherwise, leave this parameter
value blank.
Related parameters
v “RTE_SMS_VOLUME” on page 131
RTE_STC_PREFIX
This parameter specifies a prefix to be used when generating started task procedures for products
configured in the runtime environment.
environments.
Panel name
Panel ID
KCIPRTEA
Field
STC prefix
Default value
CANS
Permissible values
RTE_STC_PREFIX
PARMGEN name
RTE_STC_PREFIX
Description
For full and sharing runtime environments, specify a prefix to be used when generating started
task procedures for products configured in the runtime environment. The default value of CANS is
provided, but specifying your own prefix prevents confusion with jobs generated by other
runtime environments on the same system.
Related parameters
None
RTE_SYSV_BASE_ALIAS
This parameter specifies a system variable for the base runtime environment for a sharing-with-base
runtime environments with system variables enabled.
134
Required for full and sharing runtime environments with system variables enabled; does not
apply to base runtime environments
Panel name
Panel ID
KCIPRTA1
Field
RTE base alias specification
Default value
None
Permissible values
RTE_SYSV_BASE_ALIAS
PARMGEN name
RTE_SYSV_BASE_ALIAS
Description
For a sharing-with-base runtime environment with system variables enabled
(RTE_SYSV_SYSVAR_FLAG = Y), specify a system variable for the base runtime environment. This
value is then inserted into the base runtime environment data set references in all started tasks.
The resolved name must be a valid data set name qualifier.
For other types of runtime environments, the label n/a is displayed beside this field.
Related parameters
v “RTE_SYSV_SYSVAR_FLAG” on page 136
RTE_SYSV_NAME
This parameter contains the system variable for the name of the runtime environment.
Panel name
Panel ID
KCIPRTA1
Field
RTE name specification
Default value
SYSNAME
Permissible values
RTE_SYSV_NAME
135
PARMGEN name
RTE_SYSV_NAME
Description
System variable for the name of the runtime environment. The resolved name must be a single
valid JCL symbol, as defined in the z/OS MVS JCL Reference. This field becomes the value of the
SYS= parameter (for example, SYS=’SYSNAME’) in all started task members. This field can contain
both literals and symbolics. For example, if you specify a value of OMXSYSNAME, the value resolves
to a runtime environment name of OMXSYSA when SYSNAME = SYSA.
Related parameters
v “RTE_SYSV_SYSVAR_FLAG”
RTE_SYSV_SYSVAR_FLAG
This parameter determines whether to enable z/OS system variables, which are elements that allow
systems to share PARMGEN definitions while retaining unique values in those definitions.
environments.
Panel name
Panel ID
KCIPRTA1
Field
Use z/OS system variables?
Default value
N
Permissible values
Y or N
RTE_SYSV
PARMGEN name
RTE_SYSV_SYSVAR_FLAG
Description
Determines whether to enable z/OS system variables, which are elements that allow systems to
share PARMGEN definitions while retaining unique values in those definitions. Each system that
shares a definition replaces the system variable with a unique value during initialization.
If you use system variables, the components inherit the system values for the system on which
they are started (the host z/OS system). These system-specific values are then automatically
loaded into dynamic in-memory parameter members that exist only while the component runs.
The result is that the software runs correctly by using the system-specific parameter values for
the host z/OS system.
Note: You cannot use system variables in the runtime environment of a high-availability hub.
For complete information about using system variables, see the chapter "Enabling system variable
support" in IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: Common Planning
and Configuration Guide.
Related parameters
136
v
v
v
v
“RTE_SYSV_NAME” on page 135
“RTE_SYSV_BASE_ALIAS” on page 134
“RTE_SYSV_VTAM_APPLID_PREFIX” on page 138
“RTE_SYSV_VTAM_APPLID_MODEL”
RTE_SYSV_TEMS_NAME_NODEID
The parameters specifies the system variable for the name that identifies the monitoring server for
internal processing.
Required for runtime environments with system variables enabled
Panel name
Runtime Environment (1 of 3)
Panel ID
KCIPRTEA
Field
TEMS name
Default value
None
Permissible values
RTE_SYSV_CMS_NAME
PARMGEN name
RTE_SYSV_TEMS_NAME_NODEID
Description
System variable for the name that identifies the monitoring server for internal processing. The
resolved name must follow the rules for the RTE_TEMS_NAME_NODEID parameter.
Related parameters
v “RTE_TEMS_NAME_NODEID” on page 142
RTE_SYSV_VTAM_APPLID_MODEL
This parameter determines whether the runtime environment will use VTAM model applids; that is,
applids with wildcard suffixes such as ? or *.
Panel name
Panel ID
KCIPRTA1
Field
Use VTAM model applids?
137
Default value
N
Permissible values
Y or N
RTE_SYSV_VTM_APPL_MODEL
PARMGEN name
RTE_SYSV_VTAM_APPLID_MODEL
Description
Determines whether the runtime environment will use VTAM model applids; that is, applids with
wildcard suffixes such as ? or *. These model applids allow the use of any applids that match the
pattern in the VTAM node.
Related parameters
v “RTE_SYSV_VTAM_APPLID_PREFIX”
RTE_SYSV_VTAM_APPLID_PREFIX
This parameter specifies the a VTAM applid prefix that contains system variables, if system variables are
enabled and you intend to use SNA communications.
Optional for runtime environments with system variables enabled
Panel name
Panel ID
KCIPRTA1
Field
Applid prefix
Default value
KSYSCLONE.
Permissible values
RTE_SYSV_VTM_APPL_PREF
PARMGEN name
RTE_SYSV_VTAM_APPLID_PREFIX
Description
If system variables are enabled (RTE_SYSV_SYSVAR_FLAG = Y) and if you intend to use SNA
communications, supply a VTAM applid prefix that contains system variables. 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.
Related parameters
v “RTE_VTAM_APPLID_PREFIX” on page 148
138
RTE_SYSV_VTAM_NETID
This parameter specifies a system variable for the VTAM network identifier, if system variables are
enabled and you intend to use SNA communications.
Required for SNA communications if system variables are enabled
Panel name
Panel ID
KCIPRTA1
Field
Network ID
Default value
None
Permissible values
RTE_SYSV_VTM_NETID
PARMGEN name
RTE_SYSV_VTAM_NETID
Description
If system variables are enabled (RTE_SYSV_SYSVAR_FLAG = Y) and if you intend to use SNA
communications, supply a system variable for the VTAM network identifier, as defined in the
NETID parameter of the VTAMLST startup member ATCSTRnn. The resolved value can have a
maximum of 8 characters. This value is required for SNA communications. If none of the
products or components you intend to configure in this runtime environment require SNA
communications, leave this parameter value blank.
Related parameters
RTE_TCP_HOST
This parameter contains the TCP/IP host name or dotted decimal IPV4 address of the z/OS system
where the runtime environment is being defined.
Required
Panel name
Panel ID
KCIPRTA1
Field
Hostname
Default value
None
139
Permissible values
RTE_TCP_HOST
PARMGEN name
RTE_TCP_HOST
Description
TCP/IP host name or dotted decimal IPV4 address of the z/OS system where the runtime
environment is being defined. The value you specify becomes the default host name for the
products and components configured in the runtime environment. To obtain the host name and
IP address, enter TSO HOMETEST at a command line.
Related parameters
v “RTE_TCP_PORT_NUM”
v “KDS_TEMS_TCP_HOST” on page 222
v “KDS_HUB_TCP_HOST” on page 159
RTE_TCP_PORT_NUM
This parameter contains the number of the well-known port to be used for IP communications.
Required
Panel name
Panel ID
KCIPRTA1
Field
Port number
Default value
1918
Permissible values
1 - 65535
RTE_TCP_PORT
PARMGEN name
RTE_TCP_PORT_NUM
Description
Number of the well-known port to be used for IP communications. For detailed information
about assigning port numbers, see "Port number assignments" in IBM Tivoli OMEGAMON XE and
Tivoli Management Services on z/OS: Common Planning and Configuration Guide.
Related parameters
v “RTE_TCP_HOST” on page 139
v “KDS_TEMS_TCP_PIPE_PORT_NUM” on page 224
RTE_TCP_STC
This parameter identifies the TCP/IP stack to be used.
140
Required
Panel name
Panel ID
KCIPRTA1
Field
Started task
Default value
*
Permissible values
RTE_TCP_STC
PARMGEN name
RTE_TCP_STC
Description
Identifies the TCP/IP stack to be used. If the LPAR contains a single TCP/IP stack, accept the
default value (the wildcard character *) to select the first TCP/IP stack that was started.
If the LPAR contains more than one TCP/IP stack, you can specify the started task name of the
TCP/IP stack you want to use; or you can specify the number sign (#), which is translated to a
blank and allows the TCP/IP environment to choose the stack to use, either through TCP/IP
definitions or through the use of the SYSTCPD DD statement.
Related parameters
v “KDS_TEMS_TCP_STC” on page 228
RTE_TEMS_CONFIGURED_FLAG
This parameter specifies whether a Tivoli Enterprise Monitoring Server is to be configured in this runtime
environment.
environments.
Panel name
Runtime Environment (1 of 3)
Panel ID
KCIPRTEA
Field
Will this RTE have a Tivoli Enterprise Monitoring Server?
Default value
Y
141
Permissible values
Y or N
RTE_CMS
PARMGEN name
RTE_TEMS_CONFIGURED_FLAG
Description
Determines whether a Tivoli Enterprise Monitoring Server is to be configured in this runtime
environment. If you are creating a runtime environment for stand-alone monitoring agents
without a monitoring server, specify N. Otherwise, specify Y (the default) to allocate libraries for
the monitoring server.
Related parameters
v “RTE_TEMS_NAME_NODEID”
RTE_TEMS_NAME_NODEID
This parameter specifies the unique name that identifies the monitoring server for internal processing.
Required for a full or sharing runtime environment that contains a Tivoli Enterprise Monitoring
Server; does not apply to base runtime environments.
In KDSENV
Parameter name
CMS_NODEID
Default value
rtename:CMS
Permissible values
Panel name
Panel ID
KCIPRTEA
Field
TEMS name
Default value
rtename:CMS
Permissible values
RTE_CMS_NAME
PARMGEN name
RTE_TEMS_NAME_NODEID
Description
Unique name that identifies the monitoring server for internal processing. In general, it is best to
accept the default TEMS name (the runtime environment name followed by :CMS). If you want to
specify a different name, follow these guidelines:
v The TEMS name must be unique.
142
v The name is alphanumeric and must begin with an alphabetic character.
v The length of the name must be at least 2 characters and no more than 32 characters.
v The name cannot contain blanks or special characters ($#@). An underscore (_) is permitted and
conforms to ISO 9660 standards. A period (.) is also valid.
v The TEMS name is case-sensitive on all platforms. If you use a mixed-case name, you must
supply the same mixed-case name when you configure all components and monitoring agents
that will connect to the monitoring server.
Be sure to make a note of the TEMS name. You will have to specify it when you configure
components and products in the runtime environment, and when you set up communications
with the distributed components of Tivoli Management Services (IBM Tivoli Monitoring).
Related parameters
v “RTE_TEMS_CONFIGURED_FLAG” on page 141
v “RTE_SYSV_TEMS_NAME_NODEID” on page 137
RTE_TN3270_DXL_HOSTADDRESS
This parameter specifies the network address of an LPAR that does have an active Telnet listener, if you
are configuring products that support the Dynamic XE to 3270 (Classic) linking feature and if the LPAR
in which you are defining a runtime environment does not have an active Telnet listener.
Optional
Panel name
Panel ID
KCIPRTA2
Field
Hostname
Default value
None
Permissible values
RTE_TN3270_TCP_HOST
PARMGEN name
RTE_TN3270_DXL_HOSTADDRESS
Description
If you are configuring products that support the Dynamic XE to 3270 (Classic) linking feature and
if the LPAR in which you are defining a runtime environment does not have an active Telnet
listener, specify the network address of an LPAR that does have an active Telnet listener. A
network address can be specified as one of the following values:
v Fully qualified hostname (for example, sys.ibm.com)
v First qualifier of the fully qualified hostname (for example, sys for sys.ibm.com)
v 32-bit IPV4 address in dotted decimal notation (for example, 9.67.1.100)
To get this value, issue the TSO HOMETEST command on the LPAR of the Telnet listener.
The values you specify on this panel are displayed during TN3270 logon and can be modified
then for an individual TN3270 session.
143
Related parameters
v “RTE_TN3270_DXL_TN3270PORT”
RTE_TN3270_DXL_LUGROUP
This parameter specifies the name of a Logical Unit (LU) group if the default Telnet USS screen does not
accept the requires the LOGON APPLID() DATA() command required by the Dynamic XE to 3270 (Classic)
linking feature.
Required
Panel name
Panel ID
KCIPRTA2
Field
LUGROUP
Default value
None
Permissible values
RTE_TN3270_LUGROUP
PARMGEN name
RTE_TN3270_DXL_LUGROUP
Description
The Dynamic XE to 3270 (Classic) linking feature requires the VTAM Unformatted System
Services (USS) screen to accept a LOGON APPLID() DATA() command. If the default Telnet USS
screen does not accept this command, supply the name of a Logical Unit (LU) group that does
accept it. The TN3270 session will be joined to that LU group.
Related parameters
None
RTE_TN3270_DXL_TN3270PORT
This parameter contains the port number on which the TN3270 server is listening.
Optional
Panel name
Panel ID
KCIPRTA2
Field
Port number
Default value
23
Permissible values
1 - 65535
144
RTE_TN3270_TCP_PORT
PARMGEN name
RTE_TN3270_DXL_TN3270PORT
Description
Port number on which the TN3270 server is listening.
Related parameters
v “RTE_TN3270_DXL_HOSTADDRESS” on page 143
RTE_TYPE
This parameter specifies the type of runtime environment being created.
Required
Panel name
Panel ID
KCIPRTE
Field
Type
Default value
None
Permissible values
FULL, BASE, or SHARING
RTE_TYP
PARMGEN name
RTE_TYPE
Description
Type of runtime environment being created. If you intend to create any sharing environments,
start by creating the base or full runtime environment that they will share, so that you can then
add the sharing runtime environment later. The following types are valid:
Full
Allocates both private and base libraries. Use this if you only one runtime environment
or if you a runtime environment for a unique set of products. This is the default if no
value is provided in the Configuration Tool.
Base
Allocates read-only base libraries and does not execute alone. Use this only in conjunction
with sharing runtime environments. Create the base runtime environment first.
Note: You cannot configure products in base runtime environments, which contain
shared, read-only libraries exclusively.
Sharing
Allocates private libraries only. This type can either share base libraries with a base or full
runtime environment, or use target libraries that were installed by SMP/E for its base
libraries. Define one sharing runtime environment for each z/OS image.
For detailed information about types of runtime environments, see IBM Tivoli OMEGAMON XE
and Tivoli Management Services on z/OS: Common Planning and Configuration Guide.
145
Related parameters
RTE_USERMODS_FLAG
This parameter determines whether the Configuration Tool will identify user-modified data set members
that each configuration batch job will affect.
Required
Panel name
Panel ID
Field
Runtime members analysis
Default value
Y
Permissible values
Y or N
RTE_USERMODS
PARMGEN name
RTE_USERMODS_FLAG
Description
Determines whether the Configuration Tool will identify user-modified data set members that
each configuration batch job will affect. If runtime members analysis is enabled, a report of
user-modified members is displayed. If the value of this parameter is Y, the value of the
“RTE_REMOTE_LPAR_FLAG” on page 125 parameter must be N, and vice versa.
Related parameters
v “RTE_REMOTE_LPAR_FLAG” on page 125
RTE_USS_RTEDIR
This parameter specifies the main Hierarchical File System/zSeries File System (HFS/zFS) directory name
for the runtime environment, if a product to be configured in the runtime environment requires that
UNIX System Services (USS) directories be created.
Optional
The KDSENV member of the rhilev.midlev.rtename.RKANPARU library
TEMS_MANIFEST_PATH=#rtedir/%RTE_NAME%/kds/support/TEMS
Default value
/rtehome
146
Permissible values
See description.
Panel name
Panel ID
KCIPRTA2
Field
RTE directory
RTE_USS_RTEDIR
PARMGEN name
RTE_USS_RTEDIR
Description
(Conditional) If any products in this runtime environment require that Unix System Services
(USS) directories be created, specify the RTE HFS/zFS home directory (#rtedir).
Note:
1. Specify the main RTE HFS/zFS home directory name if you are enabling the self-describing
agents (SDA) function in the z/OS TEMS and agents. SDA applies to Tivoli Management
Services V6.2.3 and higher versions.
2. The RTE_USS_RTEDIR value (#rtedir) is used in this TEMS parameter in the xKANPARU
library:
TEMS_MANIFEST_PATH=\
#rtedir/%RTE_NAME%/kds/support/TEMS
3.
4.
5.
6.
The TEMS_MANIFEST_PATH parameter is the name of the USS home directory where
agent-uploaded jar files and other application support files will be stored by the TEMS. The
#rtedir value is also used in the KDS* members in RKANDATV; these members contain the
commands that create the USS directories and send files to the USS subdirectories.
Product configuration USS jobs (KCIJ%USP/KCIJ%USS) that use the RTE_USS_RTEDIR home
directory parameter must be invoked by a user ID wither either superuser authority (UID=0)
or read access to resource BPX.SUPERUSER under the FACILITY profile (in which case,
superuser authority must be activated).
The user ID must have read access to the BPX.FILEATTR.APF resource profile in the RACF
FACILITY class.
If you plan to create a new file system for products that use the RTE_USS_RTEDIR home
directory parameter, ensure it is created before submitting the product USS jobs to define file
system paths. See the KCIUSSJB sample job in the %GBL_TARGET_HILEV%.TKANSAM
SMP/E target library.
When issuing the MOUNT FILESYSTEM command, the MOUNTPOINT() parameter equates
to the value you are supplying for the RTE_USS_RTEDIR. A sample MOUNT FILESYSTEM
command is shown below:
MOUNT FILESYSTEM(’&hlq_rte_home’) TYPE(ZFS) MODE(RDWR) MOUNTPOINT(’/rtehome’) AGGRGROW
7. The file system must be in read/write mode when the product USS jobs are run.
Related parameters
147
RTE_VSAM_HILEV
This parameter specifies the VSAM high-level qualifier to be used for allocating the runtime data sets
Required
Panel name
Panel ID
Field
High-level Qualifier (VSAM)
Default value
None
Permissible values
RTE_VSAM_HILEV
PARMGEN name
RTE_VSAM_HILEV
Description
VSAM high-level qualifier to be used for allocating the runtime data sets. If you plan to allocate
SMS-managed data sets for the runtime environment, the high-level qualifier that you specify
must be eligible for SMS-managed volumes.
For PARMGEN configuration, the value of this parameter for a sharing runtime environment
must be the same as the value for the shared runtime environment. For detailed information
about sharing and shared runtime environments, see the "Planning your deployment" chapter of
Related parameters
RTE_VTAM_APPLID_PREFIX
This parameter specifies the global VTAM applid prefix to be used when building the VTAM applids for
products in this runtime environment.
Optional
Panel name
148
Panel ID
KCIPRTA1
Field
Applid prefix
Default value
CTD
Permissible values
RTE_VTM_APPL_PREF
PARMGEN name
RTE_VTAM_APPLID_PREFIX
Description
Global VTAM applid prefix to be used when building the VTAM applids for products in this
runtime environment. If none of the products or components you intend to configure in this
runtime environment require SNA communications, delete the default value and leave this
parameter value blank.
If system variables are enabled, the value supplied for the RTE_SYSV_VTAM_APPLID_PREFIX
parameter is used.
Related parameters
v “RTE_SYSV_VTAM_APPLID_PREFIX” on page 138
RTE_VTAM_GBL_MAJOR_NODE
This parameter specifies the name of the global VTAM major node in the RKANSAMU member with the
same name.
Required
Panel name
Create VTAM Major Node
Panel ID
KCIPSVU2
Field
VTAM major node name
Default value
KCANDLE1
Permissible values
RTE_VTM_CANDLE_NODE
PARMGEN name
RTE_VTAM_GBL_MAJOR_NODE
Description
Name of the global VTAM major node in the RKANSAMU member with the same name. This
major node contains all applid definitions required for the runtime environment.
149
Related parameters
None
RTE_VTAM_LU62_DLOGMOD
This parameter specifies the LU6.2 logmode for this runtime environment.
Panel name
Panel ID
KCIPRTA1
Field
LU6.2 logmode
Default value
CANCTDCS
Permissible values
RTE_VTM_LU62_LOG
PARMGEN name
RTE_VTAM_LU62_DLOGMOD
Description
LU6.2 logmode for this runtime environment. The default is CANCTDCS. If none of the products or
components you intend to configure in this runtime environment require SNA communications,
delete the default value and leave this parameter value blank.
Related parameters
v “RTE_VTAM_LU62_MODETAB”
RTE_VTAM_LU62_MODETAB
This parameter specifies the logmode table name for LU6.2 logmode entries
Optional
Panel name
Panel ID
KCIPRTA1
Field
Logmode table
Default value
KDSMTAB1
Permissible values
RTE_VTM_LU62_LOGTAB
150
PARMGEN name
RTE_VTAM_LU62_MODETAB
Description
Logmode table name for LU6.2 logmode entries. The default is KDSMTAB1. If none of the products
or components you intend to configure in this runtime environment require SNA
communications, delete the default value and leave this parameter value blank.
This table is assembled into the system library (usually SYS1.VTAMLIB) that contains VTAM
logmode tables.
Related parameters
v “RTE_VTAM_LU62_DLOGMOD” on page 150
v “GBL_DSN_SYS1_VTAMLIB” on page 98
RTE_VTAM_NETID
This parameter specifies the VTAM network identifier, as defined in the NETID parameter of the
VTAMLST startup member.
Panel name
Panel ID
KCIPRTA1
Field
Network ID
Default value
None
Permissible values
RTE_VTM_NETID
PARMGEN name
RTE_VTAM_NETID
Description
VTAM network identifier, as defined in the NETID parameter of the VTAMLST startup member
(ATCSTRnn). If none of the products or components you intend to configure in this runtime
environment require SNA communications, leave this parameter value blank.
If system variables are enabled, the value supplied for “RTE_SYSV_VTAM_NETID” on page 139
is used.
Related parameters
v “RTE_SYSV_VTAM_NETID” on page 139
v “GBL_DSN_SYS1_VTAMLST” on page 99
RTE_X_KCNDLSSI_INITPARM_FLAG
This PARMGEN-only parameter determines if the INITPARM(’SSPROC=%RTE_CANSCN_STC%’) parameter is
generated in the &rhilev.&rte.RKANSAMU(KCNDLSSI) OMEGAMON subsystem member.
151
Optional
Value determines if the INITPARM(’SSPROC=%RTE_CANSCN_STC%’) parameter should be generated in
the &rhilev.&rte.RKANSAMU(KCNDLSSI) member.
N/A
Default value
Y
Permissible values
Y, N
PARMGEN name
RTE_X_KCNDLSSI_INITPARM_FLAG
Description
This is the flag that generates the INITPARM(’SSPROC=%RTE_CANSCN_STC%’) parameter in the
KCNDLSSI member in RKANSAMU. A value of Y generates the INITPARM(). Member
KCNDLSSI contains a sample IEFSSNcc update. In addition to identifying the subsystem to
z/OS, this sample causes an automatic start of the subsystem address space.
Related parameters
v
v
v
v
“RTE_KCNSTR00_SSID” on page 113
“RTE_KCNSTR00_XCFGROUP” on page 114
“RTE_KCNSTR00_WTO” on page 113
“RTE_X_KCNSTR00_REFRESH” on page 153
v “RTE_X_KCNSTR00_PLEXCOLLECT”
RTE_X_KCNSTR00_PLEXCOLLECT
This PARMGEN-only parameter specifies whether or not the OMEGAMON subsystem address space
may become the collector for this sysplex.
Optional
KCNSTR00 OMEGAMON subsystem startup member in the &rhilev.&rte.RKANPARU library.
PLEXCOLLECT=%RTE_X_KCNSTR00_PLEXCOLLECT%
Default value
YES
Permissible values
YES, NO
PARMGEN name
RTE_X_KCNSTR00_PLEXCOLLECT
Description
This parameter specifies whether or not the OMEGAMON subsystem address space may become
the collector for this Sysplex. There are two values:
YES
152
This OMEGAMON subsystem may become the Coupling Facility data collector for this
sysplex. Only one OMEGAMON subsystem at a time is the collector, but OMEGAMON
subsystems with this value may take over collection should the current collector fail or be
terminated. YES is the default.
NO
This OMEGAMON subsystem may not become the collector for this sysplex. This
OMEGAMON subsystem may initiate local collection if the sysplex collector cannot be
located.
Related parameters
v “RTE_X_KCNSTR00_REFRESH”
RTE_X_KCNSTR00_REFRESH
This PARMGEN-only parameter specifies the interval at which the OMEGAMON subsystem refreshes
Coupling Facility data in the address space.
Optional
KCNSTR00 OMEGAMON subsystem startup member in the &rhilev.&rte.RKANPARU library.
REFRESH=%RTE_X_KCNSTR00_REFRESH%
Default value
60 (in seconds)
Permissible values
Numeric range 1–300
PARMGEN name
RTE_X_KCNSTR00_REFRESH
Description
This parameter shows the refresh interval in effect. The value is in seconds. This interval
determines how frequently Coupling Facility data gets refreshed in this address space. All
OMEGAMON subsystems that are part of the same XCF group should have the same refresh
interval. The smaller this number, the higher the overhead incurred.
Related parameters
v “RTE_X_KCNSTR00_PLEXCOLLECT” on page 152
153
RTE_X_SECURITY_DATA_ABOVE
This PARMGEN-only parameter determines if the DATA=ABOVE parameter or the DATA=BELOW
parameter is generated in the &rhilev.&rte.RKANPARU(KppINNAM) security member for TMS:Engine to
control the allocation of security control blocks.
Optional
v KppINNAM member in &rhilev.&rte.RKANPARU for the TEMS, the agents, and most of the
agent CUA interfaces
v KC2NAMnn in &rhilev.&rte.RKANPARU for OMEGAMON II for CICS/OMEGAMON XE for
CICS on z/OS, where nn=00..15 (one pair per Classic 3270 or CUA started tasks)
v KD2INNAM in &rhilev.&rte.RKD2PAR for OMEGAMON XE for DB2 on z/OS (Classic 3270
started task)
DATA=ABOVE|BELOW
Default value
Y
Permissible values
Y, N
PARMGEN name
RTE_X_SECURITY_DATA_ABOVE
Description
Controls where the security control blocks are allocated by the TMS/Engine NAM routines, as
follows:
BELOW
Control blocks are allocated in 24-bit storage (RMODE 24).
ABOVE
Control blocks are allocated in 31-bit storage (RMODE 31).
If RTE_X_SECURITY_DATA_ABOVE is set to Y, then a DATA=ABOVE parameter is written to
the KppINNAM member in the RKANPARU library. If RTE_X_SECURITY_DATA_ABOVE is set
to N, then a DATA=BELOW parameter is written out to the KppINNAM member in the
RKANPARU library.
Related parameters
v “RTE_SECURITY_FOLD_PASSWORD_FLAG” on page 126
RTE_X_SECURITY_EXIT_LIB
This parameter specifies the name of the global RTE library that houses all the OMEGAMON/ITMrelated product security exits (KOBSUPDT OMEGAMON KppSUPDI exits, TMS:Engine security exits,
external security exits, etc.).
Required
N/A
154
N/A
Default value
&rhilev.&rte.RKANSAM
Permissible values
PARMGEN name
RTE_X_SECURITY_EXIT_LIB
Description
Library where user security exits are located. 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
RKANSAM by default. If you need to 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.
ICAT-to-PARMGEN conversion considerations: If you are converting an ICAT-built runtime
environment, the security exit source library varies for each product. Refer to the
application-specific security jobs for more information. See the master PARMGEN Technote's FAQ
Security category for more information.
Related parameters
v
v
v
v
v
v
“RTE_SECURITY_FOLD_PASSWORD_FLAG” on page 126
“RTE_X_SECURITY_EXIT_LIB” on page 154
“RTE_X_SECURITY_DATA_ABOVE” on page 154
“GBL_DSN_ACF2_MACLIB” on page 81
“RTE_SECURITY_CLASS” on page 125
“KDS_TEMS_SECURITY_KDS_VALIDATE” on page 214
155
156
Chapter 5. Tivoli Enterprise Monitoring Server (KDS)
parameters
The Tivoli Enterprise Monitoring Server parameters provide configuration settings for hub and remote
monitoring servers on z/OS.
The Tivoli Enterprise Monitoring Server parameters are explained in this section.
KDS_AUDIT_ITM_DOMAIN
This parameter specifies an identifier that may be used to associate audit records.
Optional
The value you specify on the KDS_AUDIT_ITM_DOMAIN parameter generates an
ITM_DOMAIN parameter in KDSENV.
Configuration Tool (ICAT) information
Panel name
Specify Advanced Configuration Values
Panel ID
KDS62PP3
Field
Domain
Default value
None
Permissible values
PARMGEN name
Description
Audit domain name
This field is used to specify an identifier that may be used to associate audit records. It is suited
for commonly identifying agents that are associated with each other. An example use may be for
sorting records by a particular customer.
This field will also be used to create unique namespaces for RBAC. The value you specify
generates an ITM_DOMAIN parameter in KDSENV.
Related parameters
None
KDS_AUDIT_MAX_HIST
This parameter specifies an identifier that may be used to associate audit records
Optional
157
AUDIT_MAX_HIST parameter in the RKANPARU data set, member KDSENV.
Panel name
Panel ID
KDS62PP3
Field
Maximum in-memory cache entries
Default value
None
Permissible values
10-1000
KDS_AUDIT_MAX_HIST
PARMGEN name
KDS_AUDIT_MAX_HIST
Description
The maximum number of records kept in short term memory for direct queries.
Related parameters
None
KDS_AUDIT_TRACE
Optional
AUDIT_TRACE parameter in the RKANPARU data set, member KDSENV.
Panel name
Panel ID
KDS62PP3
Field
Enable/Disable z/OS audit collection
Default value
None
Permissible values
M, B, D, X
KDS_AUDIT_TRACE
PARMGEN name
KDS_AUDIT_TRACE
Description
This indicates the trace level to pass messages. Message trace levels (from low to high) are X
(Disabled), M (Minimum), B (Basic), and D(Detail). Higher levels imply all lower levels.
158
Related parameters
None
KDS_HUB_TCP_HOST
This parameter specifies the TCP/IP host name or the dotted decimal IPV4 address of the system where
the hub monitoring server is installed.
Required for remote Tivoli Enterprise Monitoring Servers that use TCP/IP for communications
with the hub
KDCSSITE member of the rhilev.rte.RKANPARU library for the runtime environment of the
remote monitoring server
Panel name
Specify Configuration - Hub Values for Remote TEMS
Panel ID
KDS62PP2
Field
Network address (Hostname of Hub)
Default value
None
Permissible values
KDS_HUB_TCP_HOST
PARMGEN name
KDS_HUB_TCP_HOST
Description
The TCP/IP host name or the dotted decimal IPV4 address of the system where the hub
monitoring server is installed. This parameter applies only to a remote monitoring server that
uses TCP/IP for communications. The value specified for this parameter must match the value
set for the “KDS_TEMS_TCP_HOST” on page 222 parameter in the runtime environment where
the hub is configured, or the value set for an equivalent parameter of a distributed hub.
Related parameters
KDS_HUB_TCP_PIPE_PORT_NUM
This parameter contains the well-known port for the hub monitoring server for the IP.PIPE
communication protocol (the TCP/IP protocol that supports IPV4), specified during configuration of a
remote monitoring server.
Required for remote Tivoli Enterprise Monitoring Servers that use the IP.PIPE protocol for
communications with the hub
KDSENV member of the rhilev.rte.RKANPARU library for the runtime environment of the remote
monitoring server
Chapter 5. Tivoli Enterprise Monitoring Server (KDS) parameters
159
Parameter name
KDE_TRANSPORT (IP.PIPE PORT option)
Example:
KDE_TRANSPORT=\
IP.PIPE PORT:1918
Default value
1918
Permissible values
1 - 65535
Panel name
Panel ID
KDS62PP2
Field
IP.PIPE port number
Default value
1918 or the value set for the “KDS_TEMS_TCP_PIPE_PORT_NUM” on page 224
parameter for the hub
Permissible values
1 - 65535
KDS_HUB_TCP_PIPE_PORT
PARMGEN name
KDS_HUB_TCP_PIPE_PORT_NUM
Description
Well-known port for the hub monitoring server for the IP.PIPE communication protocol (the
TCP/IP protocol that supports IPV4), specified during configuration of a remote monitoring
server. The value specified for this parameter must match the value set for the
“KDS_TEMS_TCP_PIPE_PORT_NUM” on page 224 parameter in the runtime environment where
the hub is configured, or the value set for an equivalent parameter of a distributed hub.
Related parameters
v “KDS_TEMS_TCP_PIPE_PORT_NUM” on page 224
KDS_HUB_TCP_PIPE6_PORT_NUM
This parameter contains the well-known port for the hub monitoring server for the IP6.PIPE
communication protocol (the TCP/IP protocol that supports IPV6), specified during configuration of a
remote monitoring server.
Required for remote Tivoli Enterprise Monitoring Servers that use the IP6.PIPE protocol for
monitoring server
Parameter name
KDE_TRANSPORT (IP6.PIPE PORT option)
Example:
160
KDE_TRANSPORT=\
IP6.PIPE PORT:1918
Default value
1918
Permissible values
1 - 65535
Panel name
Panel ID
KDS62PP2
Field
IP6.PIPE port number
Default value
1918
Permissible values
1 - 65535
KDS_HUB_TCP_PIPE6_PORT
PARMGEN name
KDS_HUB_TCP_PIPE6_PORT_NUM
Description
Well-known port for the hub monitoring server for the IP6.PIPE communication protocol (the
TCP/IP protocol that supports IPV6), specified during configuration of a remote monitoring
server. This protocol is available for a monitoring server on a z/OS system at release level V1R7
or higher, with IPV6 installed and operational.
The value specified for this parameter must match the value set for the
“KDS_TEMS_TCP_PIPE6_PORT_NUM” on page 225 parameter in the runtime environment
Related parameters
v “KDS_TEMS_TCP_PIPE6_PORT_NUM” on page 225
KDS_HUB_TCP_PIPE6S_PORT_NUM
This parameter contains the well-known port for the hub monitoring server for the IP6.SPIPE
communication protocol (the TCP/IP protocol that supports Secure Sockets Layer communications over
IPV6), specified during configuration of a remote monitoring server.
Required for remote Tivoli Enterprise Monitoring Servers that use the IP6.SPIPE protocol for
monitoring server
Parameter name
KDE_TRANSPORT (IP6.SPIPE PORT option)
Example:
KDE_TRANSPORT=\
IP6.SPIPE PORT:3660
161
Default value
3660
Permissible values
1 - 65535
Panel name
Panel ID
KDS62PP2
Field
IP6.SPIPE port number
Default value
3660 or the value set for the “KDS_TEMS_TCP_PIPE6S_PORT_NUM” on page 226
Permissible values
1 - 65535
KDS_HUB_TCP_PIPE6S_PORT
PARMGEN name
KDS_HUB_TCP_PIPE6S_PORT_NUM
Description
Well-known port for the hub monitoring server for the IP6.SPIPE communication protocol (the
TCP/IP protocol that supports Secure Sockets Layer communications over IPV6), specified during
configuration of a remote monitoring server. This protocol is available for a monitoring server on
a z/OS system at release level V1R7 or higher, with IPV6 installed and operational.
“KDS_TEMS_TCP_PIPE6S_PORT_NUM” on page 226 parameter in the runtime environment
Related parameters
v
“KDS_TEMS_TCP_PIPE6S_PORT_NUM” on page 226
KDS_HUB_TCP_PIPES_PORT_NUM
This parameter contains the well-known port for the hub monitoring server for the IP.SPIPE
communication protocol (the TCP/IP protocol that supports Secure Sockets Layer communications over
IPV4), specified during configuration of a remote monitoring server
Required for remote Tivoli Enterprise Monitoring Servers that use the IP.SPIPE protocol for
monitoring server
Parameter name
KDE_TRANSPORT (IP.SPIPE PORT option)
Example:
KDE_TRANSPORT=\
IP.SPIPE PORT:3660
162
Default value
3660
Permissible values
1 - 65535
Panel name
Panel ID
KDS62PP2
Field
IP.SPIPE port number
Default value
3660 or the value set for the “KDS_TEMS_TCP_PIPES_PORT_NUM” on page 227
Permissible values
1 - 65535
KDS_HUB_TCP_PIPES_PORT
PARMGEN name
KDS_HUB_TCP_PIPES_PORT_NUM
Description
Well-known port for the hub monitoring server for the IP.SPIPE communication protocol (the
TCP/IP protocol that supports Secure Sockets Layer communications over IPV4), specified during
a z/OS system at release level V1R7 or higher.
“KDS_TEMS_TCP_PIPES_PORT_NUM” on page 227 parameter in the runtime environment
Related parameters
v “KDS_TEMS_TCP_PIPES_PORT_NUM” on page 227
KDS_HUB_TCP_UDP_PORT_NUM
This parameter contains the well-known port for the hub monitoring server for the IP.UDP
communication protocol (the TCP/IP protocol that uses the packet-based, connectionless User Datagram
Protocol under IPV4), specified during configuration of a remote monitoring server.
Required for remote Tivoli Enterprise Monitoring Servers that use the IP.UDP protocol for
monitoring server
Parameter name
KDE_TRANSPORT (IP.UDP PORT option)
Example:
KDE_TRANSPORT=\
IP.UDP PORT:1918
163
Default value
1918
Permissible values
1 - 65535
Panel name
Panel ID
KDS62PP2
Field
IP.UDP port number
Default value
1918 or the value set for the “KDS_TEMS_TCP_UDP_PORT_NUM” on page 229
Permissible values
1 - 65535
KDS_HUB_TCP_UDP_PORT
PARMGEN name
KDS_HUB_TCP_UDP_PORT_NUM
Description
Well-known port for the hub monitoring server for the IP.UDP communication protocol (the
TCP/IP protocol that uses the packet-based, connectionless User Datagram Protocol under IPV4),
specified during configuration of a remote monitoring server. The value specified for this
parameter must match the value set for the “KDS_TEMS_TCP_UDP_PORT_NUM” on page 229
parameter in the runtime environment where the hub is configured, or the value set for an
equivalent parameter of a distributed hub.
Related parameters
v “KDS_TEMS_TCP_UDP_PORT_NUM” on page 229
KDS_HUB_TCP_UDP6_PORT_NUM
This parameter specifies the well-known port for the hub monitoring server for the IP6.UDP
communication protocol (the packet-based, connectionless User Datagram Protocol that supports IPV6),
specified during configuration of a remote monitoring server.
Required for remote Tivoli Enterprise Monitoring Servers that use the IP6.UDP protocol for
monitoring server
Parameter name
KDE_TRANSPORT (IP6.UDP PORT option)
Example:
KDE_TRANSPORT=\
IP6.UDP PORT:1918
Default value
1918
164
Permissible values
1 - 65535
Panel name
Panel ID
KDS62PP2
Field
IP6.UDP port number
Default value
1918 or the value set for the “KDS_TEMS_TCP_UDP6_PORT_NUM” on page 230
Permissible values
1 - 65535
KDS_HUB_TCP_UDP6_PORT
PARMGEN name
KDS_HUB_TCP_UDP6_PORT_NUM
Description
Well-known port for the hub monitoring server for the IP6.UDP communication protocol (the
packet-based, connectionless User Datagram Protocol that supports IPV6), specified during
a z/OS system at release level V1R7 or higher, with IPV6 installed and operational.
“KDS_TEMS_TCP_UDP6_PORT_NUM” on page 230 parameter in the runtime environment
Related parameters
v “KDS_TEMS_TCP_UDP6_PORT_NUM” on page 230
KDS_HUB_TEMS_HA_TYPE
This parameter specifies whether the hub with which a remote Tivoli Enterprise Monitoring Server
communicates is a high-availability hub.
Required for remote Tivoli Enterprise Monitoring Servers
Panel name
Panel ID
KDS62PP1
Field
Hub TEMS type
Default value
None
Permissible values
HA or none
165
KDS_HUB_HA_TYP
PARMGEN name
KDS_HUB_TEMS_HA_TYPE
Description
Specifies whether the hub with which a remote Tivoli Enterprise Monitoring Server
communicates is a high-availability hub.
Related parameters
KDS_HUB_VTAM_APPL_GLB_BROKER
This parameter specifies the VTAM applid for the global location broker of the hub monitoring server.
Required for remote Tivoli Enterprise Monitoring Servers that use the SNA.PIPE protocol for
v KDCSSITE member of the rhilev.rte.RKANPARU library for the runtime environment of the
v XCF_PLEXGROUP parameter in the KDSENV member of the rhilev.rte.RKANPARU library for
the runtime environment of the remote monitoring server
Panel name
Panel ID
KDS62PP2
Field
Global location broker applid of Hub
Default value
None
Permissible values
KDS_HUB_GLB_APPL
PARMGEN name
KDS_HUB_VTAM_APPL_GLB_BROKER
Description
VTAM applid for the global location broker of the hub monitoring server. You can find this
applid in the VTAM major node definition in SYS1.VTAMLST for the hub.
Related parameters
v “KDS_TEMS_VTAM_APPL_GLB_BROKER” on page 234
KDS_HUB_VTAM_NETID
This parameter specifies the VTAM network identifier associated with the hub monitoring server.
Required for remote Tivoli Enterprise Monitoring Servers that use the SNA.PIPE protocol for
166
KDCSSITE member of the rhilev.rte.RKANPARU library for the runtime environment of the
Panel name
Panel ID
KDS62PP2
Field
Network ID of hub
Default value
None
Permissible values
KDS_HUB_VTM_NETID
PARMGEN name
KDS_HUB_VTAM_NETID
Description
VTAM network identifier associated with the hub monitoring server.
Related parameters
v “KDS_TEMS_VTAM_NETID” on page 239
KDS_KMS_SDA
This parameter indicates whether the server supports self-describing agents.
Required
The KMS_SDA parameter in the RKANPARU data set, member KDSENV.
Panel name
TEMS Self-Describing Agent Values
Panel ID
KDS62PP4
Field
Enable TEMS Self-Description processing (KMS_SDA)
Default value
Y
for a remote TEMS
N
for a hub TEMS
Permissible values
Y, N
KDS_KMS_SDA
PARMGEN name
KDS_KMS_SDA
167
Description
This field indicates whether the server supports and runs the self-description feature.
Related parameters
KDS_MIG_TAPE_HILEV
This parameter specifies the high-level qualifier (with DISP=NEW) for the backup VSAM clusters on tape.
Required for migrating customized objects (for example, modified situations, templates, and
managed objects) from a previous version to a later version of the Tivoli Enterprise Monitoring
Server
KDSDMG4B member of the rhilev.rte.RKANSAMU library for the runtime environment of the
monitoring server
Panel name
Generate Sample Migration JCL
Panel ID
KDS62PMG
Field
Tape high-level qualifier
Default value
None
Permissible values
KDS_MIG_TAPE_HILEV
PARMGEN name
KDS_MIG_TAPE_HILEV
Description
High-level qualifier (with DISP=NEW) for the backup VSAM clusters on tape. For complete upgrade
instructions, see IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: Upgrade
Guide.
Related parameters
v “KDS_MIG_TAPE_UNIT”
v “KDS_MIG_TAPE_VOL” on page 169
v “KDS_MIG_VSAM_HILEV” on page 170
KDS_MIG_TAPE_UNIT
This parameter specifies the unit device name for the backup VSAM clusters on tape.
Optional
168
monitoring server
Panel name
Panel ID
KDS62PMG
Field
Tape unit type
Default value
None
Permissible values
KDS_MIG_TAPE_UNIT
PARMGEN name
KDS_MIG_TAPE_UNIT
Description
Unit device name for the backup VSAM clusters on tape. Leave this field blank if your
environment does not require the unit name. For complete upgrade instructions, see IBM Tivoli
OMEGAMON XE and Tivoli Management Services on z/OS: Upgrade Guide.
Related parameters
v “KDS_MIG_TAPE_VOL”
KDS_MIG_TAPE_VOL
This parameter specifies the volume serial for the backup VSAM clusters on tape.
Optional
monitoring server
Panel name
Panel ID
KDS62PMG
Field
Tape volser
Default value
None
Permissible values
KDS_MIG_TAPE_VOL
PARMGEN name
KDS_MIG_TAPE_VOL
169
Description
Volume serial for the backup VSAM clusters on tape. Leave this field blank if your environment
does not require the volume serial number. For complete upgrade instructions, see IBM Tivoli
OMEGAMON XE and Tivoli Management Services on z/OS: Upgrade Guide.
Related parameters
v “KDS_MIG_TAPE_UNIT” on page 168
KDS_MIG_VER
This parameter specifies the version number of the Tivoli Enterprise Monitoring Server whose customized
objects you want to migrate.
Server
monitoring server
Panel name
Panel ID
KDS62PMG
Field
TEMS version
Default value
None
Permissible values
Version number, in nnn format
KDS_MIG_VER
PARMGEN name
KDS_MIG_VER
Description
Version number of the Tivoli Enterprise Monitoring Server whose customized objects you want to
migrate. For complete upgrade instructions, see IBM Tivoli OMEGAMON XE and Tivoli
Management Services on z/OS: Upgrade Guide.
Related parameters
v “KDS_MIG_VSAM_HILEV”
v “KDS_MIG_TAPE_HILEV” on page 168
KDS_MIG_VSAM_HILEV
This parameter specifies complete high-level qualifier (rvhilev.rte) of the VSAM runtime libraries from
which you want to migrate customized objects.
Server
170
monitoring server
Panel name
Panel ID
KDS62PMG
Field
VSAM high-level qualifier
Default value
None
Permissible values
KDS_MIG_VSAM_HILEV
PARMGEN name
KDS_MIG_VSAM_HILEV
Description
Complete high-level qualifier (rvhilev.rte) of the VSAM runtime libraries from which you want to
migrate customized objects. For complete upgrade instructions, see IBM Tivoli OMEGAMON XE
and Tivoli Management Services on z/OS: Upgrade Guide.
Related parameters
v “KDS_MIG_TAPE_HILEV” on page 168
KDS_NONSTDnn_DSN
This parameter specifies the low-level qualifier of the data set containing the member with the parameter
to be added, replaced, or deleted by specifying a nonstandard parameter (a parameter that is not
presented in a Configuration Tool interactive panel).
Optional in the Configuration Tool interactive and batch modes; does not apply to PARMGEN
configuration
Member specified in the “KDS_NONSTDnn_MBR” on page 172 parameter
Panel name
Panel ID
KDSPNSTn
Field
Default value
None
Permissible values
KDS_NONSTDnn_DSN
171
PARMGEN name
KDS_NONSTDnn_DSN
Description
The low-level qualifier of the data set containing the member with the parameter to be added,
replaced, or deleted by specifying a nonstandard parameter (a parameter that is not presented in
a Configuration Tool interactive panel). Each KDS_NONSTDnn_DSN parameter has a unique
name, in which nn represents a number between 1 and 18, corresponding to the number set for
“KDS_NONSTDnn_PARM” on page 173.
Configuration Guide. For examples of commonly specified nonstandard parameters, see the
"Configuration, and Deployment: Highlights of Common z/OS Configuration Tool
Enhancements" Technote at http://www.ibm.com/support/docview.wss?uid=swg21338430.
Related parameters
v “KDS_NONSTDnn_PARM” on page 173
v “KDS_NONSTDnn_MBR”
KDS_NONSTDnn_MBR
This parameter specifies the name of the KDS_NONSTDnn_DSN data set member that contains the
parameter to be added, replaced, or deleted by specifying a nonstandard parameter (a parameter that is
not presented in a Configuration Tool interactive panel).
configuration
Member specified in this parameter, in the data set specified in the “KDS_NONSTDnn_DSN” on
page 171 parameter
Panel name
Panel ID
KDSPNSTn
Field
Member
Default value
None
Permissible values
KDS_NONSTDnn_MBR
PARMGEN name
KDS_NONSTDnn_MBR
Description
Name of the “KDS_NONSTDnn_DSN” on page 171 data set member that contains the parameter
to be added, replaced, or deleted by specifying a nonstandard parameter (a parameter that is not
presented in a Configuration Tool interactive panel). The asterisk (*) wildcard character can be
used as a suffix in column 4, 5, 6, 7, or 8 of the member name (provided that column is the final
one in the name).
172
Each KDS_NONSTDnn_MBR parameter has a unique name, in which nn represents a number
between 1 and 18, corresponding to the number set for “KDS_NONSTDnn_PARM.”
Related parameters
v “KDS_NONSTDnn_PARM”
v “KDS_NONSTDnn_DSN” on page 171
KDS_NONSTDnn_PARM
This parameter specifies the name of the configuration parameter to be added, replaced, or deleted.
configuration
Data set and member specified in the “KDS_NONSTDnn_MBR” on page 172 and
“KDS_NONSTDnn_DSN” on page 171 parameters, respectively
Panel name
Panel ID
KDSPNSTn
Field
Parameter
Default value
None
Permissible values
KDS_NONSTDnn_PARM
PARMGEN name
KDS_NONSTDnn_PARM
Description
Name of the configuration parameter to be added, replaced, or deleted. You can specify up to 18
nonstandard parameters (parameters that are not presented in the Configuration Tool interactive
panels). Each nonstandard parameter has a unique name in which nn represents a number
between 1 and 18.
Related parameters
v “KDS_NSNEWnn_VALUE” on page 174
v “KDS_NSOLDnn_VALUE” on page 174
173
KDS_NSNEWnn_VALUE
This parameter specifies the value for a nonstandard parameter (a parameter that is not presented in a
Configuration Tool interactive panel).
configuration
Data set, member, and parameter specified in the “KDS_NONSTDnn_MBR” on page 172,
“KDS_NONSTDnn_DSN” on page 171, and “KDS_NONSTDnn_PARM” on page 173 parameters,
respectively.
Panel name
Panel ID
KDSPNSTn
Field
New Value
Default value
None
Permissible values
KDS_NSNEWnn_VALUE
PARMGEN name
KDS_NSNEWnn_VALUE
Description
Value for a nonstandard parameter (a parameter that is not presented in a Configuration Tool
interactive panel). In specifying the value, be sure to include format characters. For example, if
the format in the runtime member is parameter=value, precede the value with an equal sign; or if
the format is parameter(value), surround the value with parentheses. If you want to delete an
existing parameter that is specified in “KDS_NONSTDnn_PARM” on page 173, leave the value of
the corresponding KDS_NSNEWnn_VALUE parameter blank.
Each KDS_NSNEWnn_VALUE parameter has a unique name, in which nn represents a number
between 1 and 18, corresponding to the number set for “KDS_NONSTDnn_PARM” on page 173.
Related parameters
v “KDS_NSOLDnn_VALUE”
KDS_NSOLDnn_VALUE
This parameter specifies the existing value to be replaced or deleted in the parameter definition
corresponding to KDS_NONSTDnn_PARM.
174
configuration
Replaced in the data set, member, and parameter specified in the “KDS_NONSTDnn_MBR” on
page 172, “KDS_NONSTDnn_DSN” on page 171, and “KDS_NONSTDnn_PARM” on page 173
parameters, respectively.
Panel name
Panel ID
KDSPNSTn
Field
Old Value (if replacing)
Default value
None
Permissible values
KDS_NSOLDnn_VALUE
PARMGEN name
KDS_NSOLDnn_VALUE
Description
Existing value to be replaced or deleted in the parameter definition corresponding to
“KDS_NONSTDnn_PARM” on page 173. The character string that you specify must match exactly
the existing value for the parameter in the runtime member, or the value is not replaced. For
example, if the format in the runtime member is parameter=value, precede the value with an
equal sign; or if the format is parameter(value), surround the value with parentheses.
Each KDS_NSOLDnn_VALUE parameter has a unique name, in which nn represents a number
between 1 and 18, corresponding to the number set for “KDS_NONSTDnn_PARM” on page 173.
Related parameters
v “KDS_NSNEWnn_VALUE” on page 174
KDS_PA
This parameter indicates the beginning or end of the partition reference table for address translation.
Required for broker partitioning
KDCPART member of the rhilev.rte.RKANPARU library for the runtime environment of the Tivoli
Enterprise Monitoring Server
175
KDS_PA
PARMGEN name
KDS_PA
Description
Indicates the beginning or end of the partition reference table for address translation. The
partition table contains labels and associated socket addresses provided by the firewall
administrator. This parameter is for IBM internal use only.
Related parameters
v “KDS_TEMS_COMM_ADDRESS_XLAT” on page 196
v “KDS_PA_PARTITION_ADDRESS”
v “KDS_PA_PARTITION_NAME” on page 177
v “KDS_TEMS_PARTITION_NAME” on page 213
KDS_PA_PARTITION_ADDRESS
This parameter contains the IP address or SNA reference assigned to the Tivoli Enterprise Monitoring
Server from a location on the other side of the firewall.
Panel name
Specify IP.PIPE Partition References
Panel ID
KDS62PPE
Field
Partition address
Default value
None
Permissible values
KDS_PA_ADDR
PARMGEN name
KDS_PA_PARTITION_ADDRESS
Description
IP address or SNA reference assigned to the Tivoli Enterprise Monitoring Server from a location
on the other side of the firewall. The partition address that you supply is added to the partition
table identified by the “KDS_PA” on page 175 parameter. The partition table contains labels and
associated socket addresses provided by the firewall administrator.
If the value of the “KDS_TEMS_COMM_ADDRESS_XLAT” on page 196 parameter is Y, this
parameter must have a value assigned to it, or the Tivoli Enterprise Monitoring Server and its
communications will fail.
Related parameters
176
v “KDS_PA” on page 175
v “KDS_PA_PARTITION_NAME”
KDS_PA_PARTITION_NAME
This parameter contains the partition name (label) that identifies the location of the Tivoli Enterprise
Monitoring Server relative to the firewall or firewalls used for address translation.
Panel name
Specify IP.PIPE Communication Protocol
Panel ID
KDS62PPD
Field
Partition name
Default value
None
Permissible values
KDS_PA_NAME
PARMGEN name
KDS_PA_PARTITION_NAME
Description
Partition name (label) that identifies the location of the Tivoli Enterprise Monitoring Server
relative to the firewall or firewalls used for address translation. The partition name that you
supply is added to the partition table identified by the “KDS_PA” on page 175 parameter. The
partition table contains labels and associated socket addresses provided by the firewall
administrator. The label is used outside the firewall to establish monitoring server connections.
The well-known port for the hub monitoring server must be authorized by the firewall
administrator. For the IP*.*PIPE protocols, no additional ports be authorized.
If the value of the “KDS_TEMS_COMM_ADDRESS_XLAT” on page 196 parameter is Y, this
parameter must have a value assigned to it, or the Tivoli Enterprise Monitoring Server and its
communications will fail.
Related parameters
v “KDS_PA_PARTITION_ADDRESS” on page 176
KDS_PA_ROW
This parameter indicates the beginning or end of a row in the partition reference table for address
translation.
177
KDS_PA_ROW
PARMGEN name
KDS_PA_ROW
Description
Indicates the beginning or end of a row in the partition reference table for address translation.
This parameter is for IBM internal use only.
Related parameters
KDS_PD
This parameter indicates the beginning or end of the persistent data store specifications table.
Optional
KPDPG member of the rhilev.rte.RKANPARU library for the runtime environment of the Tivoli
KDS_PD
PARMGEN name
KDS_PD
Description
Indicates the beginning or end of the persistent data store specifications table. The persistent data
store is the repository for short-term historical data. This parameter is for IBM internal use only.
Related parameters
v “KDS_PD_ROW” on page 180
KDS_PD_CYL
This parameter contains the space allocation for the persistent data store libraries and for overhead
information such as the product dictionary, table records, index records, and buffers to hold overflow
data when the libraries are full.
Optional
KPDAL member of the rhilev.rte.RKANPARU library for the runtime environment of the Tivoli
Panel name
178
Panel ID
KPD62PP3
Field
Est Cyl Space
Default value
None
Permissible values
1 - 9999
KDS_PD_CYL
PARMGEN name
KDS_PD_CYL
Description
Space allocation for the persistent data store libraries and for overhead information such as the
product dictionary, table records, index records, and buffers to hold overflow data when the
libraries are full.
By default, the Tivoli Enterprise Portal Server retrieves historical data for reports once every 24
hours. Unless the Tivoli Enterprise Portal Server KFW_REPORT_TERM_BREAK_POINT
parameter is set to a value other than the default, allocate enough space (n data sets) for the
persistent data store to permit n-1 data sets to hold 24 hours of data.
For more information about maintaining the persistent data store, see IBM Tivoli OMEGAMON
XE and Tivoli Management Services on z/OS: Common Planning and Configuration Guide. For
information about historical data collection and reporting, see IBM Tivoli Monitoring:
Administrator's Guide.
Related parameters
None
KDS_PD_GRP
This parameter contains the name of a single persistent data store group.
Optional
Parameter name
GROUP
Default value
None
Permissible values
Panel name
Panel ID
KPD62PP3
Field
Group Name
179
Default value
None
Permissible values
KDS_PD_GRP
PARMGEN name
KDS_PD_GRP
Description
Name of a single persistent data store group.
Related parameters
v “KDS_PD_ROW”
v “KDS_PD” on page 178
KDS_PD_ROW
This parameter indicates the beginning or end of a single persistent datastore group for the monitoring
server.
Optional
KDS_PD_ROW
PARMGEN name
KDS_PD_ROW
Description
Indicates the beginning or end of a single persistent datastore group for the monitoring server.
Related parameters
v “KDS_PD” on page 178
KDS_PH
This parameter indicates the beginning or end of the table that lists the hub monitoring servers that are
eligible for SOAP server access.
Required for a hub Tivoli Enterprise Monitoring Server
KSHXHUBS member of the rhilev.rte.RKANPARU library for the runtime environment of the hub
KDS_PH
PARMGEN name
KDS_PH
180
Description
Indicates the beginning or end of the table that lists the hub monitoring servers that are eligible
for SOAP server access. This parameter is for IBM internal use only.
Related parameters
v “KDS_TEMS_SOAP_SERVER_FLAG” on page 215
v “KDS_PH_ROW”
KDS_PH_ROW
This parameter indicates the beginning or end of a single hub monitoring server entry in the SOAP
server list.
KDS_PH_ROW
PARMGEN name
KDS_PH_ROW
Description
Indicates the beginning or end of a single hub monitoring server entry in the SOAP server list.
Related parameters
“KDS_TEMS_SOAP_SERVER_FLAG” on page 215
“KDS_PH” on page 180
KDS_PH_TEMS_ALIAS_NAME
This parameter contains the TEMS name (node ID) that identifies a non-local hub monitoring server to
the SOAP server. For best results, accept the default name.
Required for a non-local hub Tivoli Enterprise Monitoring Server
KSHXHUBS member of the rhilev.rte.RKANPARU library for the runtime environment of the local
monitoring server
Example:
Aliasrte_name:CMS/Alias
Panel name
Specify TEMS KSHXHUBS Values
Panel ID
KDS62PPG
Field
Alias name
Default value
Value set for “RTE_TEMS_NAME_NODEID” on page 142 in the runtime environment of
the hub
181
Permissible values
KDS_PH_CMS_ALIAS_NAME
PARMGEN name
KDS_PH_TEMS_ALIAS_NAME
Description
TEMS name (node ID) that identifies a non-local hub monitoring server to the SOAP server. For
best results, accept the default name.
Related parameters
KDS_PH_TEMS_COMM_PROTOCOL1
This parameter contains the communication protocol to be used by the SOAP server.
Example:
CMS_NameIP.PIPE:SYS1[1918]/CMS_Name
Panel name
Panel ID
KDS62PPG
Field
Protocol 1
Default value
Value set for the KDS_TEMS_COMM_PROTOCOL1 parameter for the hub
Permissible values
IPPIPE, IP, IP6PIPE, IP6, IPSPIPE, IP6SPIPE, or SNA
KDS_PH_CMS_COMM_PRO1
PARMGEN name
KDS_PH_TEMS_COMM_PROTOCOL1
Description
Communication protocol to be used by the SOAP server. The value of this parameter is included
in the entry for this hub in the KSHXHUBS member of the rhilev.rte.RKANPARU library.
Related parameters
v “KDS_TEMS_COMM_PROTOCOLn” on page 197
KDS_PH_TEMS_KSH_SECURE
This parameter defines the security status of the SOAP server.
182
Panel name
SOAP Server KSHXHUBS List
Panel ID
KDS62PPF
Field
TEMS secured
Default value
N
Permissible values
Y or N
KDS_PH_CMS_KSH_SECURE
PARMGEN name
KDS_PH_TEMS_KSH_SECURE
Description
Security status of the SOAP server.If no user access list is defined, the value of this parameter is
set to N and the SOAP server honors requests from any user ID that passes logon validation. If
user IDs with query or update access are listed, the parameter value is set to Y. If user IDs are
listed and given global security access, the parameter value is reset to N.
For more information about SOAP server security, see the "Planning for the SOAP server on
z/OS" section of IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: Common
Planning and Configuration Guide. For SOAP server configuration instructions, see IBM Tivoli
Management Services on z/OS: Configuring the Tivoli Enterprise Monitoring Server on z/OS.
Related parameters
v “KDS_PU_TEMS_USER_QUERY” on page 194
v “KDS_PU_TEMS_USER_UPDATE” on page 195
KDS_PH_TEMS_NAME_NODEID
This parameter defines the TEMS name (node ID) of the hub monitoring server.
Example:
Service_Namerte_name:CMS/Service_Name
Panel name
Panel ID
KDS62PPG
Field
TEMS name
183
Default value
Value of the “RTE_TEMS_NAME_NODEID” on page 142 parameter
Permissible values
KDS_PH_CMS_NAME
PARMGEN name
KDS_PH_TEMS_NAME_NODEID
Description
TEMS name (node ID) of the hub monitoring server. For best results, accept the default name.
Related parameters
KDS_PH_TEMS_RTE
This parameter contains the name of the runtime environment where the hub is configured.
Required for the hub Tivoli Enterprise Monitoring Server SOAP server
Example:
Service_Namerte_name:CMS/Service_Name
Panel name
Panel ID
KDS62PPG
Field
Hub TEMS SOAP Server values for rtename
Default value
Value of the “RTE_NAME” on page 117 parameter
Permissible values
KDS_PH_CMS_RTE
PARMGEN name
KDS_PH_TEMS_RTE
Description
Name of the runtime environment where the hub is configured. Accept the default value.
Related parameters
KDS_PH_TEMS_SYSV_FLAG
This parameter determines whether system variables are to be enabled for the SOAP server.
Required
184
KDS_PH_CMS_SYSV
PARMGEN name
KDS_PH_TEMS_SYSV_FLAG
Description
Determines whether system variables are to be enabled for the SOAP server. The value of this
parameter is always set to match the value of the “RTE_SYSV_SYSVAR_FLAG” on page 136
parameter. If system variables are enabled for the runtime environment, the server list that is
maintained in the KSHXHUBS member of the rhilev.rte.RKANPARU library is restricted to hub
monitoring servers that support z/OS system symbols.
Related parameters
KDS_PH_TEMS_TCP_HOST
This parameter contains the host name of the SOAP server.
Required for a hub Tivoli Enterprise Monitoring Server if Protocol 1 (the highest-priority
protocol) for the SOAP server is one of the TCP/IP protocols
Example:
Panel name
Panel ID
KDS62PPG
Field
TCP hostname
Default value
Value of the “KDS_TEMS_TCP_HOST” on page 222 parameter
Permissible values
KDS_PH_CMS_TCP_HOST
PARMGEN name
KDS_PH_TEMS_TCP_HOST
Description
Host name of the SOAP server. For best results, accept the default value.
Related parameters
v “KDS_PH_TEMS_COMM_PROTOCOL1” on page 182
185
KDS_PH_TEMS_TCP_HOST_LEN
This parameter defines the number of characters (up to 255) to be used internally in preparing for TCP
host name expansion.
KDS_PH_CMS_TCP_HOST_LEN
PARMGEN name
KDS_PH_TEMS_TCP_HOST_LEN
Description
Number of characters (up to 255) to be used internally in preparing for TCP host name
expansion.
Related parameters
v “KDS_PH_TEMS_TCP_HOST” on page 185
KDS_PH_TEMS_TCP_PORT_NUM
This parameter defines the TCP port number of the SOAP server.
Example:
Panel name
Panel ID
KDS62PPG
Field
TCP port number
Default value
Value set for the highest-priority TCP/IP protocol for the hub Tivoli Enterprise
Monitoring Server
Permissible values
1 - 65535
KDS_PH_CMS_TCP_PORT
PARMGEN name
KDS_PH_TEMS_TCP_PORT_NUM
Description
TCP port number of the SOAP server. For best results, accept the default value.
186
Related parameters
v “KDS_TEMS_COMM_PROTOCOLn” on page 197
KDS_PH_TEMS_USER_QUERY
This parameter defines the user ID with query access to the SOAP server.
Optional
Panel name
Panel ID
KDS62PPG
Field
Query access
Default value
None
Permissible values
KDS_PH_CMS_USER_QUERY
PARMGEN name
KDS_PH_TEMS_USER_QUERY
Description
User ID with query access to the SOAP server. To add more users, use the
KDS_PU_TEMS_USER_* parameters.
Related parameters
v “KDS_PU_TEMS_USER_ID” on page 194
KDS_PH_TEMS_USER_UPDATE
This parameter defines the user ID with update access to the SOAP server.
Optional
Panel name
Panel ID
KDS62PPG
Field
Update access
187
Default value
None
Permissible values
KDS_PH_CMS_USER_UPDATE
PARMGEN name
KDS_PH_TEMS_USER_UPDATE
Description
User ID with update access to the SOAP server. To add more users, use the
KDS_PU_TEMS_USER_* parameters.
Related parameters
This parameter defines the VTAM applid for the global location broker of the SOAP server.
protocol) for the SOAP server is SNA
Panel name
Panel ID
KDS62PPG
Field
SNA global location broker applid
Default value
Value set for “KDS_TEMS_VTAM_APPL_GLB_BROKER” on page 234
Permissible values
KDS_PH_CMS_VTM_APPL_GLB
PARMGEN name
Description
VTAM applid for the global location broker of the SOAP server.
Related parameters
v “KDS_TEMS_VTAM_APPL_GLB_BROKER” on page 234
KDS_PH_TEMS_VTAM_LU62_DLOGMOD
This parameter defines the LU6.2 logmode entry required by the SOAP server for SNA communications.
188
Panel name
Panel ID
KDS62PPG
Field
SNA LU6.2 logmode
Default value
Value set for the “KDS_TEMS_VTAM_LU62_DLOGMOD” on page 238 parameter
Permissible values
KDS_PH_CMS_VTM_LU62_LOG
PARMGEN name
KDS_PH_TEMS_VTAM_LU62_DLOGMOD
Description
LU6.2 logmode entry required by the SOAP server for SNA communications.
Related parameters
v “KDS_TEMS_VTAM_LU62_DLOGMOD” on page 238
KDS_PH_TEMS_VTAM_NETID
This parameter defines the VTAM network identifier for the SOAP server.
Panel name
Panel ID
KDS62PPG
Field
SNA network ID
Default value
Value set for “KDS_TEMS_VTAM_NETID” on page 239
Permissible values
KDS_PH_CMS_VTM_NETID
189
PARMGEN name
KDS_PH_TEMS_VTAM_NETID
Description
VTAM network identifier for the SOAP server.
Related parameters
v “KDS_TEMS_VTAM_NETID” on page 239
KDS_PPI_RECEIVER
This parameter specifies the name of the NetView PPI receiver that is to receive Take Action commands.
Optional
KDSENV member of the rhilev.rte.RKANPARU library for the runtime environment of the Tivoli
Parameter name
KGLHC_PPI_RECEIVER
Default value
CNMPCMDR
Permissible values
Panel name
Panel ID
KDS62PP1
Field
NetView PPI receiver
Default value
CNMPCMDR
Permissible values
KDS_PPI_RECEIVER
PARMGEN name
KDS_PPI_RECEIVER
Description
Name of the NetView PPI receiver that is to receive Take Action commands. This name must
match the receiver name specified on the NetView APSERV command.
The value must be a 1- through 8-character unique identifier for the receiver program. It can
contain alphabetic characters A-Z and a-z, numeric characters 0-9, and the following special
characters: dollar sign ($), percent sign (%), ampersand (), at sign (@), and number sign (#). This
value must match the value specified in the NetView DSIPARM initialization member,
CNMSTYLE
190
If a value is specified for this parameter and either the specified name is incorrect or the receiver
is not active on NetView for z/OS, the command fails. If no value is specified, default (MGCR)
command routing is performed.
section of IBM Tivoli Management Services on z/OS: Configuring the Tivoli Enterprise Monitoring
Server on z/OS.
Related parameters
v “GBL_DSN_NETVIEW_CNMLINK” on page 92
v “KDS_PPI_SENDER”
KDS_PPI_SENDER
This parameter specifies the name of the NetView PPI sender.
Optional
Parameter name
KGLHC_PPI_SENDER
Default value
None
Permissible values
Panel name
Panel ID
KDS62PP1
Field
TEMS PPI sender
Default value
None
Permissible values
KDS_PPI_SENDER
PARMGEN name
KDS_PPI_SENDER
Description
Name of the NetView PPI sender. This name is used in logging the command and command
response in the NetView log and therefore must not conflict with any NetView for z/OS domain
name.
This parameter has no default value in the KDSENV member, but the internal default is the value
of the “KDS_PPI_RECEIVER” on page 190 parameter.
191
section of IBM Tivoli Management Services on z/OS: Configuring the Tivoli Enterprise Monitoring
Server on z/OS.
Related parameters
v “GBL_DSN_NETVIEW_CNMLINK” on page 92
v “KDS_PPI_RECEIVER” on page 190
KDS_PU
This parameter indicates the beginning or end of the SOAP server user access table.
Optional
KDS_PU
PARMGEN name
KDS_PU
Description
Indicates the beginning or end of the SOAP server user access table. This parameter is for IBM
internal use only.
Related parameters
v “KDS_PH_TEMS_KSH_SECURE” on page 182
KDS_PU_ROW
This parameter indicates the beginning or end of a single user access record in the SOAP server user
access table.
Optional
KDS_PU_ROW
PARMGEN name
KDS_PU_ROW
Description
Indicates the beginning or end of a single user access record in the SOAP server user access table.
Related parameters
v “KDS_PU”
KDS_PU_TEMS_NAME_NODEID
This parameter contains the TEMS name (node ID) of the hub monitoring server.
192
Optional
Panel name
Specify TEMS KSHXHUBS User Access List
Panel ID
KDS62PPI
Field
Monitored Hub TEMS
Default value
Value of the “KDS_PH_TEMS_NAME_NODEID” on page 183 parameter
Permissible values
KDS_PU_CMS_NAME
PARMGEN name
KDS_PU_TEMS_NAME_NODEID
Description
TEMS name (node ID) of the hub monitoring server. For best results, accept the default name.
Related parameters
v “KDS_PH_TEMS_NAME_NODEID” on page 183
KDS_PU_TEMS_RTE
This parameter contains the name of the runtime environment where the hub is configured.
Optional
Panel name
Panel ID
KDS62PPI
Field
Monitored RTE
Default value
Value of the “KDS_PH_TEMS_RTE” on page 184 parameter
Permissible values
KDS_PU_CMS_RTE
PARMGEN name
KDS_PU_TEMS_RTE
193
Description
Name of the runtime environment where the hub is configured. Accept the default value.
Related parameters
v “KDS_PH_TEMS_RTE” on page 184
KDS_PU_TEMS_USER_ID
This parameter contains the user ID defined to have access to the SOAP server.
Optional
Panel name
Panel ID
KDS62PPI
Field
User ID
Default value
None
Permissible values
KDS_PU_CMS_USER_ID
PARMGEN name
KDS_PU_TEMS_USER_ID
Description
User ID defined to have access to the SOAP server. A user ID can have both query and update
access.
Related parameters
v “KDS_PU_TEMS_USER_QUERY”
KDS_PU_TEMS_USER_QUERY
This parameter determines query access of a user ID to the SOAP server.
Optional
Panel name
Panel ID
KDS62PPI
Field
194
Grant query access?
Default value
Y
Permissible values
Y or N
KDS_PU_CMS_USER_QUERY
PARMGEN name
KDS_PU_TEMS_USER_QUERY
Description
Determines query access of a user ID to the SOAP server. A user ID can have both query and
update access.
Related parameters
v “KDS_PU_TEMS_USER_UPDATE”
KDS_PU_TEMS_USER_UPDATE
This parameter determines update access of a user ID to the SOAP server.
Optional
Panel name
Panel ID
KDS62PPI
Field
Grant update access?
Default value
N
Permissible values
Y or N
KDS_PU_CMS_USER_UPDATE
PARMGEN name
KDS_PU_TEMS_USER_UPDATE
Description
Determines update access of a user ID to the SOAP server. A user ID can have both update and
query access.
Related parameters
195
KDS_TEMA_SDA
This parameter indicates whether the agent uses the self-description feature.
Required
The TEMA_SDA parameter in the RKANPARU data set, member KDSENV.
Panel name
Specify TEMS Self-Describing Agent Values
Panel ID
KDS62PP4
Field
Agent Self-Description processing in TEMS (TEMA_SDA)
Default value
Y
Permissible values
Y, N
KDS_TEMA_SDA
PARMGEN name
KDS_TEMA_SDA
Description
This field indicates whether one or more agents will use the self-description feature in the TEMS
address space.
Related parameters
KDS_TEMS_COMM_ADDRESS_XLAT
This parameter points to the file that enables broker partitioning.
Required
Parameter name
KDC_PARTITIONFILE
Default value
None
Permissible values
KDCPART or none
196
Panel name
Panel ID
KDS62PPD
Field
Address translation
Default value
N
Permissible values
Y or N
KDS_CMS_COMM_XLAT
PARMGEN name
KDS_TEMS_COMM_ADDRESS_XLAT
Description
Points to the file that enables broker partitioning. For more information about broker partitioning,
see "Implementation of firewall support" in IBM Tivoli OMEGAMON XE and Tivoli Management
Services on z/OS: Common Planning and Configuration Guide.
Related parameters
v “KDS_TEMS_PARTITION_NAME” on page 213
KDS_TEMS_COMM_PROTOCOLn
This parameter specifies the Communication protocol to be supported by the Tivoli Enterprise Monitoring
Server, with n corresponding to a number between 1 and 7 to indicate the priority sequence for the
Required
Parameter name
KDE_TRANSPORT
Example:
KDE_TRANSPORT=\
HTTP:1920\
IP6.PIPE PORT:1918 USE:N\
IP6.UDP PORT:1918 USE:N\
IP.SPIPE PORT:3660 USE:N\
IP6.SPIPE PORT:3660 USE:N\
IP.PIPE PORT:1918\
IP.UDP PORT:1918\
SNA.PIPE PORT:135
Default value
None
Permissible values
IP.PIPE, IP.UDP, IP6.PIPE, IP6.UDP, IP.SPIPE, IP6.SPIPE, and SNA.PIPE
197
Panel name
Specify Communication Protocols
Panel ID
KDS62PP3
Field
v
v
v
v
v
v
v
IP.PIPE
IP.UDP
IP6.PIPE
IP6.UDP
IP.SPIPE
IP6.SPIPE
SNA.PIPE
Default value
None
Permissible values
1-7
KDS_CMS_COMM_PROn
Default value
None
Permissible values
IPPIPE, IP, IP6PIPE, IP6, IPSPIPE, IP6SPIPE, and SNA
PARMGEN name
KDS_TEMS_COMM_PROTOCOLn
Description
Communication protocol to be supported by the Tivoli Enterprise Monitoring Server, with n
corresponding to a number between 1 and 7 to indicate the priority sequence for the
In the Configuration Tool, the seven fields corresponding to the communication protocols that can
be supported are shown. You set the priority sequence for the communication protocols by
assigning each field a value from 1 to 7, with 1 as the highest priority and 7 as the lowest. Leave
blank any fields that represent unsupported communication protocols.
The protocols, both supported and unsupported, are listed along with assigned port numbers in
the KDSENV member, as shown in the Example section. Unsupported protocols are indicated by
USE:N. Supported protocols are listed in priority order.
Related parameters
None
KDS_TEMS_DRA_FLAG
The KDS_TEMS_DRA_FLAG parameter controls the generation of the KOBAGENT startup command in
xKANCMDU(KDSSTRT1). KOBAGENT is the OMEGAMON enhanced 3270 user interface’s data-retrieval
agent (DRA) (if installed in this SMP/E environment). If not installed in this CSI, then KOBAGENT
startup is simply ignored at TEMS startup.
Required if you configure the OMEGAMON enhanced 3270 user interface component.
If the flag is set to Y, the AT ADD ID=KOB DELAY=00:00:10 CMD=’IRAMAN KOBAGENT START’ startup
parameter is added to the KDSSTRT1 member of the rhilev.rtename.RKANCMDU library.
198
AT ADD ID=KOB DELAY=00:00:10 CMD=’IRAMAN KOBAGENT START’
Default value
Y
Permissible values
Y, N
Panel name
SPECIFY ADVANCED CONFIGURATION VALUES
Panel ID
KDS62PP3
Field
Enable Data Retrieval Agent
Default value
Y
Permissible values
Y, N
KDS_TEMS_DRA_FLAG
PARMGEN name
KDS_TEMS_DRA_FLAG
Description
The KDS_TEMS_DRA_FLAG parameter controls the generation of the KOBAGENT startup
command in xKANCMDU(KDSSTRT1). KOBAGENT is the OMEGAMON enhanced 3270 user
interface’s data retrieval agent (DRA) (if installed in the SMP/E environment). If not installed in
this CSI, then KOBAGENT startup is ignored when the TEMS starts up.
Related parameters
KDS_TEMS_EIF_BUFFER_EVENT_MAXSZE
This parameter specifies the maximum size, in KB, of the adapter cache file.
Required for the hub Tivoli Enterprise Monitoring Server if event forwarding is enabled; does not
apply to remote monitoring servers
KMSOMTEC member of the rhilev.rte.RKANPARU library for the runtime environment of the hub
monitoring server
Parameter name
BufEvtMaxSize
Default value
4096
Permissible values
1 - 9999999
199
Panel name
Specify Values for Event Destination
Panel ID
KDSPEIF
Field
Buffer events maximum size
Default value
4096
Permissible values
1 - 9999999
KDS_CMS_EIF_BFR_EVT_MAX
PARMGEN name
KDS_TEMS_EIF_BUFFER_EVENT_MAXSZE
Description
Maximum size, in KB, of the adapter cache file. The cache file stores events on disk when they
cannot be sent to the event server.
Related parameters
v “KDS_TEMS_EIF_EVENT_LISTENER” on page 201
v “KDS_TEMS_EIF_FLAG” on page 202
KDS_TEMS_EIF_DISABLE_TEC_EMITTER
This parameter specifies whether to deactivate the EIF emitter activities in your policies to prevent
workflow policies containing emitter activities that send events to the Tivoli Enterprise Console® from
generating duplicate events.
Optional for the hub Tivoli Enterprise Monitoring Server if event forwarding is enabled and if the
IBM Tivoli Enterprise Console is defined as the event server; does not apply to remote
monitoring servers
monitoring server
Parameter name
KMS_DISABLE_TEC_EMITTER
Default value
None
Permissible values
Y or none
Panel name
Panel ID
KDSPEIF
Field
200
Disable Workflow Policy/Emitter Agent event forwarding
Default value
N
Permissible values
Y or N
KDS_CMS_EIF_DISABLE_EMT
PARMGEN name
KDS_TEMS_EIF_DISABLE_TEC_EMITTER
Description
If you already have workflow policies containing emitter activities that send events to the Tivoli
Enterprise Console, turning on EIF event-forwarding causes duplicate events. You can specify Y in
this field to deactivate the emitter activities in your policies.
Policies give you more control over which events are sent, and you might want to keep some
policies active. Moreover, policies that contain the Tivoli Enterprise Console emitter activities
generally do little else. If you deactivate these activities, there is no point in running the policies.
Therefore, you might want to delete the policies that are no longer required, instead of disabling
them.
Related parameters
v “KDS_TEMS_EIF_EVENT_LISTENER”
KDS_TEMS_EIF_EVENT_LISTENER
This parameter specifies the type of event server.
monitoring server
Parameter name
EventListenerType
Default value
T
Permissible values
T or M
Panel name
Panel ID
KDSPEIF
Field
Event server type
Default value
T
Permissible values
T or M
201
KDS_CMS_EIF_EVT_LISTENER
PARMGEN name
KDS_TEMS_EIF_EVENT_LISTENER
Description
Type of event server: T (the default) for Tivoli Enterprise Console, or M for OMNIbus.
Related parameters
v “KDS_TEMS_EIF_FLAG”
v “KDS_TEMS_EIF_DISABLE_TEC_EMITTER” on page 200
KDS_TEMS_EIF_FLAG
This parameter determines whether to enable event forwarding from the hub.
Optional for the hub Tivoli Enterprise Monitoring Server; does not apply to remote monitoring
servers
KDSENV member of the rhilev.rte.RKANPARU library for the runtime environment of the hub
monitoring server
Parameter name
KMS_OMTEC_INTEGRATION
Default value
None
Permissible values
YES or none
Panel name
Panel ID
KDS62PP3
Field
Enable Tivoli Event Integration Facility (EIF)
Default value
N
Permissible values
Y or N
KDS_CMS_EIF
PARMGEN name
KDS_TEMS_EIF_FLAG
Description
Determines whether to enable event forwarding from the hub. If the value of this parameter is Y,
the KMS_OMTEC_INTEGRATION parameter is created in the KDSENV member. For further
instructions, see IBM Tivoli Management Services on z/OS: Configuring the Tivoli Enterprise
Monitoring Server on z/OS.
Related parameters
None
202
KDS_TEMS_EIF_HOST
This parameter contains the fully qualified host name or dotted decimal IPV4 address of the primary
event server and of up to seven backup event servers.
monitoring server
Parameter name
ServerLocation
Default value
None
Permissible values
Panel name
Panel ID
KDSPEIF
Field
Event server location
Default value
None
Permissible values
Example:
Event server location ==> primary_server,backup_server1,backup_server2
KDS_CMS_EIF_HOST
PARMGEN name
KDS_TEMS_EIF_HOST
Description
Fully qualified host name or dotted decimal IPV4 address of the primary event server and of up
to seven backup event servers. If you specify more than one event server, use commas to separate
the host names or IP addresses. If an event cannot be sent to the first server on the list, the next
one is tried, and so on.
Related parameters
v “KDS_TEMS_EIF_PORT_NUM”
KDS_TEMS_EIF_PORT_NUM
This parameter contains the port number on which the Tivoli Enterprise Console event server or
OMNIbus EIF probe listens for events.
203
monitoring server
Parameter name
ServerPort
Default value
5529
Permissible values
Panel name
Panel ID
KDSPEIF
Field
Event server port
Default value
5529
Permissible values
Example:
Event server port ==> primary_port,backup_port1,backup_port2
KDS_CMS_EIF_PORT
PARMGEN name
KDS_TEMS_EIF_PORT_NUM
Description
Port number on which the Tivoli Enterprise Console event server or OMNIbus EIF probe listens
for events. If you specify more than one event server, use commas to separate the port numbers.
List the port numbers in an order corresponding to the list of event server locations specified in
the “KDS_TEMS_EIF_HOST” on page 203 parameter.
Related parameters
v “KDS_TEMS_EIF_HOST” on page 203
KDS_TEMS_FLUSH_LSR_BUFR_INT_HR
This parameter specifies in hours how often you want to force all deferred VSAM writes to DASD.
Optional
Part of the third EVERY command in the KDSSTART member of the rhilev.rte.RKANCMDU data
set
Example:
204
EVERY 00:30:00 FLUSH
Default value
00
Permissible values
00 - 24
Panel name
Panel ID
KDS62PP3
Field
Flush VSAM buffers: Hours
Default value
0
Permissible values
0 - 24
KDS_CMS_FLUSH_INT_HR
PARMGEN name
KDS_TEMS_FLUSH_LSR_BUFR_INT_HR
Description
Specifies in hours how often you want to force all deferred VSAM writes to DASD.
Related parameters
v “KDS_TEMS_STORAGE_DETAIL_LOG_FLAG” on page 218
v “KDS_TEMS_FLUSH_LSR_BUFR_INT_MIN”
KDS_TEMS_FLUSH_LSR_BUFR_INT_MIN
This parameter specifies in minutes how often you want to force all deferred VSAM writes to DASD.
Optional
Part of the third EVERY command in the KDSSTART member of the rhilev.rte.RKANCMDU data
set
Example:
EVERY 00:30:00 FLUSH
Default value
30
Permissible values
00 - 60
Panel name
Panel ID
KDS62PP3
Field
Flush VSAM buffers: Minutes
205
Default value
30
Permissible values
0 - 60
KDS_CMS_FLUSH_INT_MIN
PARMGEN name
KDS_TEMS_FLUSH_LSR_BUFR_INT_MIN
Description
Specifies in minutes how often you want to force all deferred VSAM writes to DASD.
Related parameters
v “KDS_TEMS_FLUSH_LSR_BUFR_INT_HR” on page 204
KDS_TEMS_HA_EXCL_LIST
This parameter specifies an eligible product or products to be excluded from reporting to the
high-availability hub.
Optional
Panel name
Exclusion Verification for HA Hub TEMS
Panel ID
KDSPHUBV
KDS_CMS_HA_EXCL_LIST
PARMGEN name
KDS_TEMS_HA_EXCL_LIST
Description
Specifies an eligible product or products to be excluded from reporting to the high-availability
hub. You can exclude products by specifying the 2-character product code of each product that
you want to exclude. Use a single blank space to separate product codes. The list can have a
maximum length of 50 characters. To exclude more products than can be accommodated by the
KDS_CMS_HA_EXCL_LIST or KDS_TEMS_HA_EXCL_LIST parameter, specify more than one
KDS_CMS_HA_EXCL_LISTn or KDS_TEMS_HA_EXCL_LISTn parameter, where n is a number
from 1 to 5.
Related parameters
v “KDS_TEMS_HA_TYPE”
KDS_TEMS_HA_TYPE
This parameter determines whether to configure the Tivoli Enterprise Monitoring Server as a
Required
206
Panel name
Panel ID
KDS62PP1
Field
Hub TEMS type
Default value
None
Permissible values
HA or none
KDS_CMS_HA_TYP
PARMGEN name
KDS_TEMS_HA_TYPE
Description
Determines 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 runtime
environment, without monitoring agents, and can be configured on the same LPAR with a remote
monitoring server. This configuration allows the hub to be relocated to any suitable LPAR in the
sysplex with no changes, and with minimal disruption to the components connecting to the hub.
Related parameters
v “KDS_HUB_TEMS_HA_TYPE” on page 165
v “KDS_TEMS_HA_EXCL_LIST” on page 206
v “KDS_TEMS_VIRTUAL_IP_ADDRESS” on page 233
KDS_TEMS_HTTP_PORT_NUM
This parameter contains the HTTP port number for communications with the SOAP server.
monitoring server
Parameter name
KDE_TRANSPORT (HTTP option)
Example:
KDE_TRANSPORT=\
HTTP:1920\
IP.PIPE PORT:1918\
Default value
1920
Permissible values
1 - 65535
207
Panel name
Panel ID
KDS62PPD
Field
HTTP server port number
Default value
1920
Permissible values
1 - 65535
KDS_CMS_HTTP_PORT
PARMGEN name
KDS_TEMS_HTTP_PORT_NUM
Description
HTTP port number for communications with the SOAP server. If the specified port is in use
when the hub monitoring server is started, another port is assigned. For detailed information
about assigning port numbers, see "Port number assignments" in IBM Tivoli OMEGAMON XE and
Tivoli Management Services on z/OS: Common Planning and Configuration Guide.
Related parameters
KDS_TEMS_ICU_LANGUAGE_LOCALE
This parameter contains the language and region for the z/OS system.
Required
Parameter name
LANG
Default value
en_US.ibm-037
Permissible values
lang.ibm-nnn
Panel name
Panel ID
KDSnnPP3
Field
Language locale
Default value
1 (English - United States)
Permissible values
Any language locale or codepage listed in Table 3 on page 209.
208
Table 3. Language locales and corresponding codepages
Language locale
Codepage
National language and region
1a or 1A
en_US.ibm-1047
English - United States (USS)
1
en_US.ibm-037
English - United States
2
en_UK.ibm-285
English - United Kingdom
3
de_DE.ibm-273
German - Germany
4
de_CH.ibm-500
German - Switzerland
5
fr_BE.ibm-500
French - Belgium
6
fr_FR.ibm-297
French - France
7
fr_CH.ibm-500
French - Switzerland
8
es_ES.ibm-284
Spanish - Spain
9
it_IT.ibm-280
Italian - Italy
10
pt_PT.ibm-037
Portuguese - Portugal
11
pt_BR.ibm-037
Portuguese - Brazil
12
no_NO.ibm-277
Norwegian - Norway)
13
sv_SE.ibm-278
Swedish - Sweden
14
da_DK.ibm-277
Danish - Denmark
15
fi_FI.ibm-278
Finnish - Finland
16
ja_JP.ibm-290
Japanese - Japan
17
fr_CA.ibm-500
French - Canada
18
zh_TW.ibm-937
Traditional Chinese - Taiwan
19
zh_CN.ibm-935
Simplified Chinese - China
20
sq_AL.ibm-500
Albanian - Albania
21
bg_BG.ibm-500
Bulgarian - Bulgaria
22
cs_CZ.ibm-870
Czech - Slovenia
23
nl_BE.ibm-500
Dutch - Belgium
24
nl_NL.ibm-037
Dutch - Netherlands
25
el_GR.ibm-87
Greek - Greece
26
iw_IL.ibm-424
Hebrew - Israel
27
ko_KR.ibm-933
Korean - Korea
28
lt_LT.ibm-1112
Lithuanian - Lithuania
29
mk_MK.ibm-1025
Macedonian - Macedonia
30
ro_RO.ibm-870
Romanian - Romania
31
ru_RU.ibm-1025
Russian - Russia
32
sr_SP.ibm-1025
Serbian - Serbia
33
sr_SP.ibm-870
Slovak - Slovakia
34
sk_SK.ibm-870
Slovenian - Slovenia
35
th_TH.ibm-838
Thai - Thailand
36
tr_TR.ibm-1026
Turkish - Turkey
KDS_CMS_ICU_LANG
209
PARMGEN name
Description
Language and region for the z/OS system. From the Configuration Tool panel, press F1 (Help)
and select Language locale for a list of the possible values. If you accept the default value of 1
(English - United States), the Configuration Tool generates this environment variable in
KDSENV:
LANG=en_US.ibm-037
If the z/OS UNIX System Services (USS) codepage (en_US.ibm-1047) is required, you can specify
either en_US.ibm-1047 or 1A in the Language locale field on the Configuration Tool panel. In batch
mode, you can specify either of these values:
KDS_CMS_ICU_LANG
KDS_CMS_ICU_LANG
en_US.ibm-1047
1A
For PARMGEN configuration, you can specify either of these values for the USS codepage:
en_US.ibm-1047
1A
The USS codepage (en_US.ibm-1047) is required for agent autonomy and for private situation
XML files.
Related parameters
None
KDS_TEMS_KDC_DEBUG
This parameter determines the trace option.
Optional
Parameter name
KDC_DEBUG
Default value
N
Permissible values
N, Y, D, M, or A
Panel name
Panel ID
KDS62PP3
Field
Enable communications trace
Default value
N
Permissible values
N, Y, D, M, or A
210
KDS_CMS_KDC_DEBUG
PARMGEN name
KDS_TEMS_KDC_DEBUG
Description
Determines the trace option. The default setting of N instructs the data communications layer to
summarize communications problems, and is intended for stable applications in production. The
default setting generates standard RAS1 trace data in the RKLVLOG, in addition to the summary
information diagnosing possible timeout conditions. The following settings report on data
communications problems:
N
Minimal tracing (the default)
Y
Full-packet tracing
Note: The Y setting causes a great many records to be written to the log files. Use this
setting only for testing or problem diagnosis.
D
Y, plus state and flow tracing
M
D, plus input and output help tracing
A
M, plus all-format tracing
Note: Do not use the A setting unless directed by IBM Software Support personnel.
Related parameters
None
KDS_TEMS_KGL_WTO
This parameter determines whether a SYSLOG message is written to the console to indicate that the
monitoring server has completed initialization.
Required
Parameter name
KGL_WTO
Default value
YES
Permissible values
YES or none
Panel name
Panel ID
KDS62PP3
Field
Enable startup console messages
Default value
Y
211
Permissible values
Y or N
KDS_CMS_KGL_WTO
PARMGEN name
KDS_TEMS_KGL_WTO
Description
Determines whether a SYSLOG message is written to the console to indicate that the monitoring
server has completed initialization. You can use this message as an UP status message in your
automation package (for example, IBM Tivoli System Automation for z/OS). See the
documentation for your automation package for instructions on capturing the monitoring server
automation message IDs (KO4SRV032 and KDSMA001).
Related parameters
None
This parameter determines whether the monitoring server address space reconnects to its TCP/IP stack
without being recycled after the stack is recycled.
Required
KLXINTCP member of the rhilev.rte.RKANPARU library for the runtime environment of the Tivoli
Parameter name
TCP/IP_USERID (TOLERATERECYCLE option)
Example:
TCP/IP_USERID=’*’ TOLERATERECYCLE
Default value
None
Permissible values
TOLERATERECYCLE or None
Panel name
Panel ID
KDS62PP3
Field
Default value
N
Permissible values
Y or N
KDS_CMS_KLX_TCP_RECYCLE
PARMGEN name
212
Description
Determines whether the monitoring server address space reconnects to its TCP/IP stack without
being recycled after the stack is recycled. If this parameter is set to N (the default), then if the
TCP/IP stack used by the monitoring server is recycled, the monitoring server address space
must also be recycled to re-establish TCP/IP connectivity. If this parameter is set to Y, the
TOLERATERECYCLE option is added to the TCP/IP_USERID parameter in KLXINTCP.
Related parameters
None
KDS_TEMS_PARTITION_NAME
This parameter contains the partition name (label) that identifies the location of the monitoring server
relative to the firewall or firewalls used for address translation.
Required if you specified Y for the “KDS_TEMS_COMM_ADDRESS_XLAT” on page 196
parameter
Panel name
v Specify IP.PIPE Communication Protocol
v Specify IP.PIPE Partition References
Panel ID
v KDS62PPD (for Communication Protocol panel)
v KDS62PPE (for Partition References panel)
Field
Partition name
Default value
None
Permissible values
KDS_CMS_PART_NAME
PARMGEN name
KDS_TEMS_PARTITION_NAME
Description
Partition name (label) that identifies the location of the monitoring server relative to the firewall
or firewalls used for address translation. The partition name that you supply is added to the
partition table, which contains labels and associated socket addresses provided by the firewall
administrator. The label is used outside the firewall to establish monitoring server connections.
The well-known port for the hub monitoring server must be authorized by the firewall
administrator. For the IP*.*PIPE protocols, no additional ports require authorization.
Related parameters
v “KDS_PA_PARTITION_NAME” on page 177
213
KDS_TEMS_SECURITY_KAES256_ENCKEY
This parameter contains unique 32-byte password encryption key.
Required if ICSF is installed and configured on the z/OS system
KAES256 member of the rhilev.rte.RKANPARU library for the runtime environment of the Tivoli
Enterprise Monitoring Server. The stored value is encrypted.
Default value
IBMTivoliMonitoringEncryptionKey
Permissible values
Character string, maximum length 32, no ampersand () character
Panel name
Panel ID
KDS62PP1
Field
TMS encryption key
Default value
IBMTivoliMonitoringEncryptionKey
Permissible values
KDS_CMS_SEC_ENC_KEY
PARMGEN name
KDS_TEMS_SECURITY_KAES256_ENCKEY
Description
Unique 32-byte password encryption key. The value is case-sensitive. You must use the same key
during the installation of any components that communicate with the monitoring server. For
further information, see the "Configuring security on a monitoring server on z/OS" chapter of
IBM Tivoli Management Services on z/OS: Configuring the Tivoli Enterprise Monitoring Server on z/OS.
Related parameters
v “GBL_DSN_CSF_SCSFMOD0” on page 87
KDS_TEMS_SECURITY_KDS_VALIDATE
This parameter determines whether the hub monitoring server validates the user IDs and passwords of
users signing on to the Tivoli Enterprise Portal.
Required for a hub Tivoli Enterprise Monitoring Server.
monitoring server
Parameter name
KDS_VALIDATE
Default value
NO
214
Permissible values
YES or NO
Panel name
Panel ID
KDS62PP1
Field
Validate security
Default value
N
Permissible values
Y or N
KDS_CMS_SEC_VALIDATE
PARMGEN name
KDS_TEMS_SECURITY_KDS_VALIDATE
Description
Determines whether the hub monitoring server validates the user IDs and passwords of users
signing on to the Tivoli Enterprise Portal. If this parameter is set to Y, validation of users is
handled by the security system specified for the runtime environment.
Related parameters
KDS_TEMS_SOAP_SERVER_FLAG
This parameter determines whether to enable the Web Services Simple Object Access Protocol (SOAP)
server.
Panel name
Panel ID
KDS62PP3
Field
Enable Web Services SOAP Server
Default value
Y
Permissible values
Y or N
KDS_CMS_CTSOAP
PARMGEN name
KDS_TEMS_SOAP_SERVER_FLAG
215
Description
Determines whether to enable the Web Services Simple Object Access Protocol (SOAP) server. The
SOAP server is an application server plug-in that receives and sends XML data, and provides
XML SOAP interfaces into the Tivoli Management Services components and the monitoring
agents. This feature requires a TCP communication protocol.
For more information about the SOAP server, see the "Planning for the SOAP server on z/OS"
section of IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: Common Planning
and Configuration Guide. For SOAP server configuration instructions, see IBM Tivoli Management
Services on z/OS: Configuring the Tivoli Enterprise Monitoring Server on z/OS.
Related parameters
None
KDS_TEMS_STC
This parameter contains the unique name of the started task JCL procedure for the monitoring server.
Required
Value becomes the name of the Tivoli Enterprise Monitoring Server started task procedure
member in the rhilev.rte.RKANSAMU library
Panel name
Panel ID
KDS62PP1
Field
STC prefix
Default value
CANSDSST
Permissible values
KDS_CMS_STC
PARMGEN name
KDS_TEMS_STC
Description
Unique name of the started task JCL procedure for the monitoring server. Make a note of the
name, because you will to copy this started task procedure to your system procedure library. The
default started task name for a monitoring server is ccccDSST, where cccc is the 4-character STC
prefix specified when you defined the runtime environment.
Related parameters
v “RTE_STC_PREFIX” on page 134
KDS_TEMS_STORAGE_DETAIL_INT_HR
This parameter specifies in hours how often you want storage allocation detail to be logged.
Required if the value of the “KDS_TEMS_STORAGE_DETAIL_LOG_FLAG” on page 218
parameter is Y
216
Part of the second EVERY command in the KDSSTART member of the rhilev.rte.RKANCMDU
library
Example:
EVERY 00:60:00 STORAGE D
Default value
00
Permissible values
00 - 24
Panel name
Panel ID
KDS62PP3
Field
Storage detail logging: Hours
Default value
0
Permissible values
0 - 24
KDS_CMS_STOR_DTL_INT_HR
PARMGEN name
KDS_TEMS_STORAGE_DETAIL_INT_HR
Description
Specifies in hours how often you want storage allocation detail to be logged.
Related parameters
v “KDS_TEMS_STORAGE_DETAIL_INT_MIN”
KDS_TEMS_STORAGE_DETAIL_INT_MIN
This parameter specifies in minutes how often you want storage allocation detail to be logged.
Required if the value of the “KDS_TEMS_STORAGE_DETAIL_LOG_FLAG” on page 218
parameter is Y
Part of the second EVERY command in the KDSSTART member of the rhilev.rte.RKANCMDU
library
Example:
EVERY 00:60:00 STORAGE D
Default value
60
Permissible values
00 - 60
217
Panel name
Panel ID
KDS62PP3
Field
Storage detail logging: Minutes
Default value
60
Permissible values
0 - 60
KDS_CMS_STOR_DTL_INT_MIN
PARMGEN name
KDS_TEMS_STORAGE_DETAIL_INT_MIN
Description
Specifies in minutes how often you want storage allocation detail to be logged.
Related parameters
v “KDS_TEMS_STORAGE_DETAIL_INT_HR” on page 216
v “KDS_TEMS_STORAGE_DETAIL_LOG_FLAG”
This parameter determines whether to enable storage allocation detail logging.
Optional
Generates the second EVERY command in the KDSSTART member of the rhilev.rte.RKANCMDU
library
Panel name
Panel ID
KDS62PP3
Field
Enable storage detail logging
Default value
Y
Permissible values
Y or N
KDS_CMS_STOR_DTL_LOG
PARMGEN name
Description
Determines whether to enable storage allocation detail logging. You can use the storage detail
command output to analyze storage allocated by the monitoring server address space.
218
To disable storage detail logging, set this parameter to N. The second EVERY command is then
written as a comment in rhilev.rte.RKANCMDU(KDSSTART).
If you disable storage logging and then want to activate it after the monitoring server is
configured and running, you can issue the following modify command to the monitoring server
started task:
/F started_task,EVERY hh:mm:ss STORAGE D
Issuing this modify command activates storage detail logging without a requirement to recycle
the monitoring server.
Related parameters
v “KDS_TEMS_STORAGE_DETAIL_INT_HR” on page 216
v “KDS_TEMS_STORAGE_DETAIL_INT_MIN” on page 217
This parameter contains the maximum extended (above-the-line) storage request size, as a power of 2.
Required
KDSSYSIN member of the rhilev.rte.RKANPARU library for the runtime environment of the
monitoring server
LIMIT(n,X)
Default value
v Default for the Configuration Tool and PARMGEN: LIMIT(23,X)
v Default in TMS:Engine: LIMIT(16,X)
Permissible values
No higher than 25 (see Description)
Panel name
Panel ID
KDS62PP3
Field
Maximum storage request size (extended)
Default value
23
Permissible values
KDS_CMS_EXT_LIM
PARMGEN name
Description
Maximum extended (above-the-line) storage request size, as a power of 2. The value can be no
higher than 25 (32768 KB).
219
This value is used in building storage access tables to speed memory allocation. If a process in
TMS:Engine attempts to allocate a block of storage larger than the value set, program interruption
U0100 or U0200 results. Too small a value causes components to fail. Too large a value wastes
storage and increases processing overhead. You might to specify a large value if any monitoring
agent reporting to the monitoring server builds large VTAM request/response units (RUs) and
data streams.
Related parameters
v “KDS_TEMS_STORAGE_LIMIT_PRIMARY”
v “KDS_TEMS_STORAGE_MINIMUM_EXTEND” on page 221
KDS_TEMS_STORAGE_LIMIT_PRIMARY
This parameter contains the maximum primary (below-the-line) storage request size, as a power of 2.
Required
monitoring server
LIMIT(n,P)
Default value
LIMIT(16,P)
Permissible values
Panel name
Panel ID
KDS62PP3
Field
Maximum storage request size (primary)
Default value
16
Permissible values
KDS_CMS_PRI_LIM
PARMGEN name
KDS_TEMS_STORAGE_LIMIT_PRIMARY
Description
Maximum primary (below-the-line) storage request size, as a power of 2. The value can be no
higher than 25 (32768 KB). The default maximum for primary storage is 16 (64 KB). However,
some monitoring agents configured to run in the monitoring server address space require a
maximum primary storage request size of 20 (1 MB).
This value is used in building storage access tables to speed memory allocation. If a process in
TMS:Engine attempts to allocate a block of storage larger than the value set, program interruption
U0100 or U0200 results. Too small a value causes components to fail. Too large a value wastes
220
storage and increases processing overhead. You might to specify a large value if any monitoring
agent reporting to the monitoring server builds large VTAM request/response units (RUs) and
data streams.
Related parameters
v “KDS_TEMS_STORAGE_LIMIT_EXTEND” on page 219
v “KDS_TEMS_STORAGE_MINIMUM_EXTEND”
This parameter specifies the minimum number of kilobytes of extended (above-the-line) storage to be
made available to the monitoring agents and other components that are communicating with the
monitoring server.
Required
monitoring server
MINIMUM(n,X)
Default value
MINIMUM(768000,X)
Permissible values
1 - 9999999
Panel name
Panel ID
KDS62PP3
Field
Default value
768000
Permissible values
A non-zero value
KDS_CMS_STOR_MIN_EXT
PARMGEN name
Description
Minimum number of kilobytes of extended (above-the-line) storage to be made available to the
monitoring agents and other components that are communicating with the monitoring server. The
default value is 768000 KB. If you do not have many IBM components reporting to the
monitoring server and you want to conserve storage, you can lower the value.
Related parameters
v “KDS_TEMS_STORAGE_LIMIT_EXTEND” on page 219
v “KDS_TEMS_STORAGE_LIMIT_PRIMARY” on page 220
221
KDS_TEMS_TCP_HOST
This parameter specifies the TCP/IP host name or dotted decimal IPV4 address of the z/OS system
where the monitoring server is installed.
Required
KDCSSITE and KDSENV members of the rhilev.rte.RKANPARU library for the runtime
environment of the Tivoli Enterprise Monitoring Server
Default value
Value set for the “RTE_TCP_HOST” on page 139 parameter for the runtime environment
Permissible values
Panel name
Panel ID
KDS62PPD
Field
TCP hostname
Default value
Value set for the “RTE_TCP_HOST” on page 139 parameter for the runtime environment
Permissible values
KDS_CMS_TCP_HOST
PARMGEN name
KDS_TEMS_TCP_HOST
Description
TCP/IP host name or dotted decimal IPV4 address of the z/OS system where the monitoring
server is installed.
To obtain the host name or IP address, enter TSO HOMETEST at the command line. If the z/OS
domain name resolver configuration specifies a search path that includes the target domain suffix,
specify only the first qualifier of the host name. (Example: sys is the first qualifier of the fully
qualified host name sys.ibm.com.) Otherwise, specify the fully qualified host name.
For a high-availability hub, the host name is the application-instance-specific (private) dynamic
virtual IP address you have defined to the Domain Name Server (DNS).
Related parameters
v “KDS_PH_TEMS_TCP_HOST” on page 185
v “KDS_HUB_TCP_HOST” on page 159
v “KDS_TEMS_TCP_KDEB_INTERFACELIST”
This parameter specifies one or more network interfaces for the monitoring server to use.
222
Optional
Parameter name
KDEB_INTERFACELIST
Default value
None
Permissible values
Panel name
v Specify IP.UDP Communication Protocol
Panel ID
v KDS62PPD (for IP.PIPE)
v KDS62PPC (for IP.UDP)
Field
Network interface list
Default value
None
Permissible values
KDS_CMS_TCP_KDEBLST
PARMGEN name
Description
One or more network interfaces for the monitoring server to use. If the z/OS image has more
than one TCP/IP interface or network adapter, you can use this parameter to direct the
monitoring server to connect to a specific TCP/IP local interface.
To set a network interface list, supply one of the following values:
v The host name or IP address of the preferred interface.
v A list of host names or IP addresses, in descending order of preference. Use a blank space to
separate the entries.
v An asterisk (*) to prefer the interface associated with the default host name for the z/OS
image. To display this value, enter TSO HOMETEST at the command line.
v An exclamation point followed by an asterisk (!*) to use only the interface associated with the
default host name for the z/OS image.
v An exclamation point followed by a host name or IP address (!hostname) to use only the
interface associated with hostname.
Note:
– If you set the value of this parameter to !* or !hostname, you must specify the same value
for every component and product configured in all runtime environments on the same z/OS
image.
223
– In the default character set (LANG=en_US.ibm-037), the code for an exclamation point is x’5A’.
If you are using a character set other than the default, a different character might map to
that code. To require a specific network interface, use the character that maps to x’5A’ in
your character set.
For a high-availability hub, specify the value of this parameter as !dvipa_hostname, where
dvipa_hostname is the private DVIPA name set for the “KDS_TEMS_TCP_HOST” on page 222
parameter.
Related parameters
KDS_TEMS_TCP_PIPE_PORT_NUM
This parameter specifies the well-known port for the monitoring server for the IP.PIPE communication
protocol (the TCP/IP protocol that supports IPV4). Tivoli Management Services reserves a default
well-known port for the first process started on a system (normally, the monitoring server).
Required if you specified IP.PIPE as a communication protocol for the Tivoli Enterprise
Monitoring Server
KDSENV member of the rhilev.rte.RKANPARU library for the runtime environment of the
monitoring server
Parameter name
KDE_TRANSPORT (IP.PIPE PORT option)
Example:
KDE_TRANSPORT=\
HTTP:1920\
IP.PIPE PORT:1918
Default value
1918 or the value set for the “RTE_TCP_PORT_NUM” on page 140 parameter
Permissible values
1 - 65535
Panel name
Panel ID
KDS62PPD
Field
Port number (IP.PIPE)
Default value
Permissible values
1 - 65535
KDS_CMS_TCP_PIPE_PORT
PARMGEN name
KDS_TEMS_TCP_PIPE_PORT_NUM
Description
Well-known port for the monitoring server for the IP.PIPE communication protocol (the TCP/IP
224
protocol that supports IPV4). Tivoli Management Services reserves a default well-known port for
the first process started on a system (normally, the monitoring server). For monitoring agents and
other components, an algorithm based on the port number assigned to the monitoring server
calculates the listening port to reserve. A port number cannot be assigned to a component if it is
already reserved for another component or application.
The default listening port number for the monitoring server for IP.PIPE is 1918 or the value set
for the “RTE_TCP_PORT_NUM” on page 140 parameter. You might find it necessary to change
the setting under some conditions; for example, when the port assigned to a component by the
algorithm is already reserved by another application or component. For a remote Tivoli
Enterprise Monitoring Server, the port number must be the same as that of the hub.
For detailed information about assigning port numbers, see "Port number assignments" in IBM
Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: Common Planning and Configuration
Guide.
Related parameters
v “RTE_TCP_PORT_NUM” on page 140
KDS_TEMS_TCP_PIPE6_PORT_NUM
This parameter specifies the well-known port for the monitoring server for the IP6.PIPE communication
protocol (the TCP/IP protocol that supports IPV6).
Required if you specified IP6.PIPE as a communication protocol for the Tivoli Enterprise
Monitoring Server
Parameter name
KDE_TRANSPORT (IP6.PIPE PORT option)
Example:
KDE_TRANSPORT=\
HTTP:1920\
IP6.PIPE PORT:1918
Default value
Permissible values
1 - 65535
Panel name
Panel ID
KDS62PPD
Field
Port number (IP.PIPE for IPV6)
Default value
Permissible values
1 - 65535
KDS_CMS_TCP_PIPE6_PORT
225
PARMGEN name
KDS_TEMS_TCP_PIPE6_PORT_NUM
Description
Well-known port for the monitoring server for the IP6.PIPE communication protocol (the TCP/IP
protocol that supports IPV6). This protocol is available for a monitoring server on a z/OS system
at release level V1R7 or higher, with IPV6 installed and operational.
Tivoli Management Services reserves a default well-known port for the first process started on a
system (normally, the monitoring server). For monitoring agents and other components, an
algorithm based on the port number assigned to the monitoring server calculates the listening
port to reserve. A port number cannot be assigned to a component if it is already reserved for
another component or application.
The default listening port number for the monitoring server for IP6.PIPE is 1918 or the value set
Guide.
Related parameters
KDS_TEMS_TCP_PIPE6S_PORT_NUM
This parameter specifies the well-known port for the monitoring server for the IP6S.PIPE communication
protocol (the TCP/IP protocol that supports Secure Sockets Layer communications over IPV6).
Required if you specified IP6.SPIPE as a communication protocol for the Tivoli Enterprise
Monitoring Server
monitoring server
Parameter name
KDE_TRANSPORT (IP6.SPIPE PORT option)
Example:
KDE_TRANSPORT=\
HTTP:1920\
IP6.SPIPE PORT:3660
Default value
Permissible values
1 - 65535
Panel name
Panel ID
KDS62PPD
Field
226
Port number (Secure IP.PIPE for IPV6)
Default value
Permissible values
1 - 65535
KDS_CMS_TCP_PIPE6S_PORT
PARMGEN name
KDS_TEMS_TCP_PIPE6S_PORT_NUM
Description
Well-known port for the monitoring server for the IP6S.PIPE communication protocol (the
TCP/IP protocol that supports Secure Sockets Layer communications over IPV6). This protocol is
available for a monitoring server on a z/OS system at release level V1R7 or higher, with IPV6
installed and operational.
The default listening port number for the monitoring server for IP6.SPIPE is 3660 or the value set
Guide.
Related parameters
KDS_TEMS_TCP_PIPES_PORT_NUM
This parameter specifies the well-known port for the monitoring server for the IP.SPIPE communication
protocol (the TCP/IP protocol that supports Secure Sockets Layer communications over IPV4).
Required if you specified IP.SPIPE as a communication protocol for the Tivoli Enterprise
Monitoring Server
monitoring server
Parameter name
KDE_TRANSPORT (IP.SPIPE PORT option)
Example:
KDE_TRANSPORT=\
HTTP:1920\
IP.SPIPE PORT:3660\
Default value
Permissible values
1 - 65535
227
Panel name
Panel ID
KDS62PPD
Field
Port number (Secure IP.PIPE)
Default value
Permissible values
1 - 65535
KDS_CMS_TCP_PIPES_PORT
PARMGEN name
KDS_TEMS_TCP_PIPES_PORT_NUM
Description
Well-known port for the monitoring server for the IP.SPIPE communication protocol (the TCP/IP
protocol that supports Secure Sockets Layer communications over IPV4). This protocol is
available for a monitoring server on a z/OS system at release level V1R7 or higher.
The default listening port number for the monitoring server for IP.SPIPE is 3660 or the value set
Guide.
Related parameters
KDS_TEMS_TCP_STC
This parameter identifies the TCP/IP stack to be used. If the LPAR contains a single TCP/IP stack, accept
the default value of an asterisk (*), which uses the first TCP/IP stack that was started.
Required
KLXINTCP member of the rhilev.rte.RKANPARU library for the runtime environment of the Tivoli
Parameter name
TCP/IP_USERID
Default value
*
228
Permissible values
Panel name
v Specify IP.UDP Communication Protocol
Panel ID
v KDS62PPD (for IP.PIPE)
v KDS62PPC (for IP.UDP)
Field
Started task
Default value
*
Permissible values
KDS_CMS_TCP_STC
PARMGEN name
KDS_TEMS_TCP_STC
Description
Identifies the TCP/IP stack to be used. If the LPAR contains a single TCP/IP stack, accept the
default value of an asterisk (*), which uses the first TCP/IP stack that was started.
If the LPAR contains more than one TCP/IP stack, specify the started task name of the TCP/IP
stack you want to use. Alternatively, you can specify the number sign (#), which is translated to a
blank and allows the TCP/IP environment to choose the stack to use, either through TCP/IP
definitions or through the use of the SYSTCPD DD statement.
Related parameters
v “RTE_TCP_STC” on page 140
KDS_TEMS_TCP_UDP_PORT_NUM
This parameter specifies the well-known port for the monitoring server for the IP.UDP communication
protocol (the TCP/IP protocol that uses the packet-based, connectionless User Datagram Protocol under
IPV4).
Required if you specified IP.UDP as a communication protocol for the Tivoli Enterprise
Monitoring Server
Parameter name
KDE_TRANSPORT (IP.UDP PORT option)
Example:
229
KDE_TRANSPORT=\
HTTP:1920\
IP.UDP PORT:1918\
Default value
Permissible values
1 - 65535
Panel name
Specify IP.UDP Communication Protocol
Panel ID
KDS62PPC
Field
Port number (IP.UDP)
Default value
Permissible values
1 - 65535
KDS_CMS_TCP_UDP_PORT
PARMGEN name
KDS_TEMS_TCP_UDP_PORT_NUM
Description
Well-known port for the monitoring server for the IP.UDP communication protocol (the TCP/IP
protocol that uses the packet-based, connectionless User Datagram Protocol under IPV4).
The default listening port number for the monitoring server for IP.UDP is 1918 or the value set
Guide.
Related parameters
KDS_TEMS_TCP_UDP6_PORT_NUM
This parameter specifies the well-known port for the monitoring server for the IP6.UDP communication
protocol (the packet-based, connectionless User Datagram Protocol that supports IPV6).
Required if you specified IP6.UDP as a communication protocol for the Tivoli Enterprise
Monitoring Server
230
monitoring server
Parameter name
KDE_TRANSPORT (IP6.UDP PORT option)
Example:
KDE_TRANSPORT=\
HTTP:1920\
IP6.UDP PORT:1918\
Default value
Permissible values
1 - 65535
Panel name
Panel ID
KDS62PPC
Field
Port number (IP6.UDP)
Default value
Permissible values
1 - 65535
KDS_CMS_TCP_UDP6_PORT
PARMGEN name
KDS_TEMS_TCP_UDP6_PORT_NUM
Description
Well-known port for the monitoring server for the IP6.UDP communication protocol (the
packet-based, connectionless User Datagram Protocol that supports IPV6). This protocol is
available for a monitoring server on a z/OS system at release level V1R7 or higher, with IPV6
installed and operational.
The default listening port number for the monitoring server for IP6.UDP is 1918 or the value set
Guide.
Related parameters
231
KDS_TEMS_TYPE
This parameter specifies whether to configure a hub monitoring server or a remote monitoring server.
Optional
Parameter name
KDS_HUB
Default value
*LOCAL
Permissible values
*LOCAL or *REMOTE
Panel name
Panel ID
KDS62PP1
Field
Type (Hub or Remote)
Default value
HUB
Permissible values
HUB or REMOTE
KDS_CMS_TYP
PARMGEN name
KDS_TEMS_TYPE
Description
Specifies whether to configure a hub monitoring server or a remote monitoring server.
The hub monitoring server is the focal point for the entire monitoring environment. This server is
under a significant load. Work on the hub includes communicating with remote monitoring
servers, with the Tivoli Enterprise Portal Server, and with local monitoring agents; authenticating
users; consolidating and distributing data; storing and tracking situations and policies; and
initiating and tracking all generated Take Action commands.
Remote monitoring servers communicate only with the monitoring agents that report to them and
with the hub monitoring server to which they report. Note that a remote monitoring server is
remote with respect to the hub monitoring server, not necessarily with respect to the monitoring
agents. If monitoring agents are installed on the same system as a remote monitoring server, that
monitoring server is local to the monitoring agents but remote to the hub.
The load on remote monitoring servers is typically low. Load is driven higher if historical data
collection is performed on the monitoring servers instead of on the monitoring agents.
Related parameters
None
232
KDS_TEMS_VIRTUAL_IP_ADDRESS
This parameter contains the type of virtual IP addressing (VIPA) defined for the z/OS system.
Optional
Panel name
Panel ID
KDS62PP3
Field
Virtual IP Address (VIPA) type
Default value
N
Permissible values
S, D, or N
KDS_CMS_VIPA
PARMGEN name
KDS_TEMS_VIRTUAL_IP_ADDRESS
Description
Type of virtual IP addressing (VIPA) defined for the z/OS system. The default is N (None). If
VIPA is in use, specify either S (Static) or D (Dynamic). The VIPA name of the monitoring server
must be resolvable through the Domain Name Server (DNS). Dynamic VIPA (DVIPA, which is
required for a high-availability hub) requires one of the following communication protocols:
IP.PIPE, IP.SPIPE, IP6.PIPE, or IP6.SPIPE.
Related parameters
KDS_TEMS_VTAM_APPL_CUA_OPER
This parameter contains the Common User Access (CUA) operator applid for the Tivoli Enterprise
Monitoring Server.
KDSSTART member of the rhilev.rte.RKANCMDU library for the runtime environment of the
Panel name
Specify VTAM APPLID Values
Panel ID
KDS62PP6
Field
233
Default value
CTDDSVP
Permissible values
KDS_CMS_VTM_APPL_CUA
PARMGEN name
KDS_TEMS_VTAM_APPL_CUA_OPER
Description
Common User Access (CUA) operator applid for the Tivoli Enterprise Monitoring Server.
Related parameters
None
KDS_TEMS_VTAM_APPL_GLB_BROKER
This parameter contains the VTAM applid for the global location broker.
Required for the hub if SNA is one of the selected communication protocols
CTDDSN member of the rhilev.rte.RKANSAMU library for the runtime environment of the hub
Panel name
Panel ID
KDS62PP6
Field
Global location broker
Default value
CTDDSLB
Permissible values
KDS_CMS_VTM_APPL_GLB
PARMGEN name
KDS_TEMS_VTAM_APPL_GLB_BROKER
Description
VTAM applid for the global location broker. The value is recorded in the VTAM major node
created for the hub.
Related parameters
v “KDS_HUB_VTAM_APPL_GLB_BROKER” on page 166
v “KDS_PH_TEMS_VTAM_APPL_GLB_BROKER” on page 188
KDS_TEMS_VTAM_APPL_KDS_VTAMID
This parameter contains the primary VTAM applid for the Tivoli Enterprise Monitoring Server.
234
Parameter name
KDS_VTAMID
Default value
CTDDSDS
Permissible values
Panel name
Panel ID
KDS62PP6
Field
TEMS application ID
Default value
CTDDSDS
Permissible values
KDS_CMS_VTM_APPL_DS
PARMGEN name
KDS_TEMS_VTAM_APPL_KDS_VTAMID
Description
Primary VTAM applid for the Tivoli Enterprise Monitoring Server.
Related parameters
None
KDS_TEMS_VTAM_APPL_KDSINVPO
This parameter contains the VTAM Primary Operator (VPO) applid for the Tivoli Enterprise Monitoring
Server.
KDSINVPO member of the rhilev.rte.RKANPARU library for the runtime environment of the
Panel name
Panel ID
KDS62PP6
Field
Default value
CTDDSVP
235
Permissible values
KDS_CMS_VTM_APPL_VPO
PARMGEN name
KDS_TEMS_VTAM_APPL_KDSINVPO
Description
VTAM Primary Operator (VPO) applid for the Tivoli Enterprise Monitoring Server.
Related parameters
None
KDS_TEMS_VTAM_APPL_LLB_BROKER
This parameter contains the VTAM applid for the local location broker.
Parameter name
KDCFC_ALIAS
Default value
CTDDSLB
Permissible values
Panel name
Panel ID
KDS62PP6
Field
Local location broker
Default value
CTDDSLB
Permissible values
KDS_CMS_VTM_APPL_LLB
PARMGEN name
KDS_TEMS_VTAM_APPL_LLB_BROKER
Description
VTAM applid for the local location broker.
Related parameters
v “KDS_TEMS_VTAM_APPL_PREFIX” on page 237
236
KDS_TEMS_VTAM_APPL_OPERATOR
This parameter contains theNon-CUA operator applid for the Tivoli Enterprise Monitoring Server.
KDSSTART member of the rhilev.rte.RKANCMDU library for the runtime environment of the
Panel name
Panel ID
KDS62PP6
Field
TMS:Engine operator (non-CUA)
Default value
CTDDSOR
Permissible values
KDS_CMS_VTM_APPL_OPR
PARMGEN name
KDS_TEMS_VTAM_APPL_OPERATOR
Description
Non-CUA operator applid for the Tivoli Enterprise Monitoring Server.
Related parameters
None
KDS_TEMS_VTAM_APPL_PREFIX
This parameter defines a prefix for VTAM application names that are used for communication with the
monitoring server.
Panel name
Specify SNA Communication Protocol
Panel ID
KDS62PPB
Field
Applid prefix
Default value
Value set for the “RTE_VTAM_APPLID_PREFIX” on page 148 parameter
Permissible values
237
KDS_CMS_VTM_APPL_PREF
PARMGEN name
KDS_TEMS_VTAM_APPL_PREFIX
Description
This value defines a prefix for VTAM application names that are used for communication with
the monitoring server. These application names begin with the prefix, and end with a specific
value that makes each applid unique. The names (applids) are contained in the VTAM major
node.
Related parameters
KDS_TEMS_VTAM_LU62_DLOGMOD
This parameter defines LU6.2 logmode for the Tivoli Enterprise Monitoring Server.
CTDDSN member of the rhilev.rte.RKANSAMU library for the runtime environment of the Tivoli
Panel name
Panel ID
KDS62PLU
Field
LU6.2 logmode
Default value
CANCTDCS or the value set for the “RTE_VTAM_LU62_DLOGMOD” on page 150
parameter
Permissible values
KDS_CMS_VTM_LU62_LOG
PARMGEN name
KDS_TEMS_VTAM_LU62_DLOGMOD
Description
LU6.2 logmode for the Tivoli Enterprise Monitoring Server.
Related parameters
v “RTE_VTAM_LU62_DLOGMOD” on page 150
v “KDS_PH_TEMS_VTAM_LU62_DLOGMOD” on page 188
KDS_TEMS_VTAM_LU62_MODETAB
This parameter contains the name of the logmode table containing the LU6.2 logmode entry for the Tivoli
Enterprise Monitoring Server.
238
Panel name
Panel ID
KDS62PLU
Field
Logmode table name
Default value
KDSMTAB1 or the value set for the “RTE_VTAM_LU62_MODETAB” on page 150 parameter
Permissible values
KDS_CMS_VTM_LU62_LOGTAB
PARMGEN name
KDS_TEMS_VTAM_LU62_MODETAB
Description
Name of the logmode table containing the LU6.2 logmode entry for the Tivoli Enterprise
Monitoring Server.
Related parameters
v “RTE_VTAM_LU62_MODETAB” on page 150
KDS_TEMS_VTAM_NETID
This parameter contains the VTAM network identifier, as defined in the NETID parameter of the
VTAMLST startup member (ATCSTRnn).
Panel name
Specify SNA Communication Protocol
Panel ID
KDS62PPB
Field
Network ID
Default value
Value set for the “RTE_VTAM_NETID” on page 151 or “RTE_SYSV_VTAM_NETID” on
page 139 parameter
Permissible values
KDS_CMS_VTM_NETID
239
PARMGEN name
KDS_TEMS_VTAM_NETID
Description
VTAM network identifier, as defined in the NETID parameter of the VTAMLST startup member
(ATCSTRnn).
Related parameters
v “RTE_SYSV_VTAM_NETID” on page 139
v “KDS_PH_TEMS_VTAM_NETID” on page 189
KDS_TEMS_VTAM_NODE
This parameter contains the name of the VTAM major node for the Tivoli Enterprise Monitoring Server.
KDS_CMS_VTM_NODE
PARMGEN name
KDS_TEMS_VTAM_NODE
Description
Name of the VTAM major node for the Tivoli Enterprise Monitoring Server.
Related parameters
KDS_X_HUB_BKUP1_TCP_HOST
This parameter defines the TCP/IP hostname identifier for the backup Hub TEMS that the Remote TEMS
should try to connect to if the primary Hub TEMS is unavailable
Required only if you plan to have the Remote TEMS communicate with the backup Hub TEMS
using TCP/IP
The KDCSSITE member of the RKANPARU library
IP.PIPE:&XDSBTCPH or IP.UDP:&XDSBTCPH
Default value
No default
Permissible values
A string of up to 32 characters defining a fully qualified TCP/IP hostname identifier
PARMGEN name
KDS_X_HUB_BKUP1_TCP_HOST
Description
TEMS backup Server TCP/IP hostname
240
This parameter defines the TCP/IP hostname identifier for the backup Hub TEMS that the
Remote TEMS should try to connect to if the primary Hub TEMS is unavailable. This is a
required field if you plan to have Remote TEMS communicate with the backup Hub TEMS using
TCP/IP.
Related parameters
None
KDS_X_HUB_BKUP1_TEMS_VTAM_NETID
This parameter specifies the identifier of your VTAM network.
Required only if you plan to have the Remote TEMS communicate with the backup Hub TEMS
using VTAM
In the VTAMLST startup member, ATCSTRnn for the backup Hub monitoring server
SNA.PIPE:&XDSBNETD
Default value
No default
Permissible values
PARMGEN name
KDS_X_HUB_BKUP1_TEMS_VTAM_NETID
Description
TEMS backup Sever Network ID
This parameter specifies the identifier of your VTAM network. You can locate this value on the
NETID parameter within the VTAMLST startup member, ATCSTRnn. This is a required field if
you plan to have the Remote TEMS communicate with the backup Hub TEMS using VTAM.
Related parameters
None
This parameter identifies the global location broker that is to be used for VTAM communication to the
Required if the remote TEMS needs to communicate with the backup Hub TEMS using the
VTAM protocol
The KDCSSITE member of the RKANPARU library.
SNA.PIPE:
Default value
No default
Permissible values
PARMGEN name
241
Description
TEMS backup VTAM applid for the global location broker.
This parameter identifies the global location broker that is to be used for VTAM communication
to the backup monitoring server. This is a required field if the remote TEMS needs to
communicate with the backup Hub TEMS using the VTAM protocol.
Related parameters
None
KDS_X_KDCFC_RXLIMIT
This parameter defines the size (in KB) of the buffer used for return queries.
Required
monitoring server.
KDCFC_RXLIMIT=8192
Default value
8192
Permissible values
1024–65536
PARMGEN name
KDS_X_KDCFC_RXLIMIT
Description
RPC request size
This parameter defines the size (in KB) of the buffer used for return queries.
Related parameters
None
This parameter allows for any HTTP-related overrides in the KDE_TRANSPORT environment variable
keyword if it is determined that your site requires these special settings.
Optional
KDSENV member of the rhilev.rte.RKANPARU library for the portal server
KDE_TRANSPORT
Default value
None
Permissible values
The following special settings are supported:
HTTPS:0
Eliminates error messages when the HTTPS daemon server is active and failing to
obtain or bind to family ip.ssl (ip.ssl.https:3661).
242
HTTP:0, HTTPS:0
These settings disable port allocation and port bind errors for the HTTP (1920)
and HTTPS (3661) default ports.
HTTP_SERVER:n
This KDE_TRANSPORT environment variable keyword disables HTTP and
HTTPS daemon services. Do not specify this for a hub monitoring server or for
the portal server.
HTTP_CONSOLE:n
This KDE_TRANSPORT environment variable keyword disables the TMS/Service
Console facility of the HTTP daemon service.
HTTP_CONSOLE:N
This KDE_TRANSPORT environment variable keyword removes the process from
the published Tivoli service index; this makes the process inaccessible from the
TMS/Service Console.
PARMGEN name
Description
Allows for any HTTP-related overrides in the KDE_TRANSPORT environment variable keyword
if it is determined that your site requires these special settings.
The KDE_TRANSPORT environment variable keyword redefines the ports to be use by the HTTP
and HTTPS daemons.
A portal server on Windows, Linux, or UNIX uses port 1920 for HTTP connections and 3661 for
HTTPS connections from portal browser clients.
Default port settings should not be changed, especially on multifunction UNIX and Linux
systems, since many components might be located on the same system and some of these
components might depend on the default values being used for HTTP and HTTPS ports.
Related parameters
None
KDS_X_KDE_TRANSPORT_OPTIONS
This parameter allows for any KDE_TRANSPORT-related overrides in addition to HTTP-related and
POOL-related options.
Optional
KDE_TRANSPORT
Default value
None
Permissible values
PARMGEN name
KDS_X_KDE_TRANSPORT_OPTIONS
Description
Additional KDE_TRANSPORT overrides
243
This parameter allows for any KDE_TRANSPORT-related overrides, in addition to HTTP-related
and POOL-related options. See “KDS_X_KDE_TRANSPORT_HTTP_OPTIONS” on page 242 for
HTTP*-related overrides and
“KDS_X_KDE_TRANSPORT_POOL_OPTIONS”KDS_X_KDE_TRANSPORT_POOL_OPTIONS for
POOL-related override parameters in KDE_TRANSPORT parameter.);
Related parameters
v “KDS_X_KDE_TRANSPORT_HTTP_OPTIONS” on page 242
v “KDS_X_KDE_TRANSPORT_POOL_OPTIONS”
This parameter allows for any POOL-related overrides in the KDE_TRANSPORT environment variable
keyword if it is determined that your site requires these special settings.
Optional
KDE_TRANSPORT POOL:nnnn-nnnn
Default value
None
Permissible values
A range of ports no smaller than 2 and no larger than 1024, expressed as nnnn-nnnn
PARMGEN name
Description
Range of port numbers parameters
This parameter allows for any POOL-related overrides in the KDE_TRANSPORT environment
variable keyword if it is determined that your site requires these special settings.
After the port allocation algorithm assigns a well-known port to each process, all subsequent
ports allocated for connections between components are opaque ports; that is, any available port
can be allocated for a connection. You can limit opaque port allocations to a specific range of
ports by coding the POOL option with any protocol specified on the KDE_TRANSPORT
environment variable.
The POOL option must specify a range of ports no smaller than 2 and no larger than 1024 in the
format nnnn-nnnn. POOL:1000-2023 is valid; POOL:1000-2024 is not. If more than 1024 ports are
needed in a pool for a specific protocol, you can code more than one POOL option, as in
POOL:1000-2023 POOL:3000-4023.
Related parameters
None
KDS_X_SECURITY_RESOURCE_CLASS
This parameter specifies a member in RKANPARU that contains protected class lists information used by
external security packages to construct the correct resource validation request.
Required
244
KDSINNAM member of the rhilev.rte.RKANPARU library for the runtime environment of the
monitoring server
CLASSES=&XDSSCLA
Default value
&XDSSCLA
Permissible values
A string up to 8 characters in length
PARMGEN name
KDS_X_SECURITY_RESOURCE_CLASS
Description
External security classes
This parameter specifies a member in RKANPARU that contains protected class lists information.
This is used by external security packages to construct the correct resource validation request.
The default for Tivoli Enterprise Monitoring Server CLASSES is &XDSSCLA.
Related parameters
None
KDS_X_SECURITY_USER_EXIT
This parameter specifies the load module name of an exit routine that will be invoked to provide
validation.
Optional
KDSINNAM member of the rhilev.rte.RKANPARU library for the runtime environment of the
monitoring server
EXIT=&XDSSUEX
Default value
&XDSSUEX
Permissible values
A string of up to 8 characters.
PARMGEN name
KDS_X_SECURITY_USER_EXIT
Description
External security exit.
This parameter specifies the load module name of an exit routine that will be invoked to provide
validation. The default for Tivoli Enterprise Monitoring Server EXIT is &XDSSUEX.
Related parameters
None
KDS_X_STC_SYSTCPD_INCLUDE_FLAG
This parameter is used to identify which dataset to use to obtain the parameters defined by TCPIP.DATA
when no GLOBALTCPIPDATA statement is configured.
245
Required
N/A
N/A
Default value
N.
Permissible values
Y or N
PARMGEN name
KDS_X_STC_SYSTCPD_INCLUDE_FLAG
Description
Specifies whether to include the SYSTCPD DD statement in the TEMS started task.
This flag is for the SYSTCPD DD: TCPDATA override. Override this DD card to explicitly identify
which dataset to use to obtain the parameters defined by TCPIP.DATA when no
GLOBALTCPIPDATA statement is configured. Refer to the IBM z/OS Communications Server: IP
Configuration Guide for information on the TCPIP.DATA search order.
TCPIP.SEZAINST(TCPDATA) is the default sample file. TCPIP.TCPPARMS(TCPDATA) is another
sample and is created as part of the Installation Verification Program (IVP) for TCP/IP. To
customize this value in PARMGEN mode, override this parameter in the CONFIG profile
member in WCONFIG ($CFG$USR or the user-specified) prior to running the $PARSE job and
specify the GBL_DSN_TCP_SYSTCPD_TCPDATA library accordingly.
Related parameters
v “GBL_DSN_TCP_SYSTCPD_TCPDATA” on page 101
KDS_X_TEMS_CONFIRM_SHUTDOWN
This parameter specifies the maximum number of seconds between two successive SHUTDOWN
commands or MVS STOP (P) commands to terminate the monitoring server address space.
Required
monitoring server
CONFIRM(n)
Default value
v Default for the Configuration Tool and PARMGEN: CONFIRM(0)
v Default in TMS:Engine: CONFIRM(15)
Permissible values
0 - 2000000000
PARMGEN name
KDS_X_TEMS_CONFIRM_SHUTDOWN
Description
Maximum number of seconds between two successive SHUTDOWN commands or MVS STOP
(P) commands to terminate the monitoring server address space. CONFIRM(0) allows shutdown
to begin immediately, without an additional, confirming SHUTDOWN command. CONFIRM(n),
246
where n is a number greater than zero, prevents accidental shutdowns by requiring confirmation
of the command by entering it a second time within the specified number of seconds. For
example, the value 15 requires that the SHUTDOWN command be entered twice within 15
seconds to terminate the monitoring server address space.
Related parameters
None
KDS_X_TEMS_DEBUG_TRACE
This parameter determines whether to activate TMS:Engine debugging services.
Optional
monitoring server
DEBUG(N|Y)
Default value
DEBUG(N)
Permissible values
DEBUG(N) or DEBUG(Y)
PARMGEN name
KDS_X_TEMS_DEBUG_TRACE
Description
Determines whether to activate TMS:Engine debugging services. A setting of Y automatically
turns on the internal trace with the default number of entries (1024), resulting in an increase in
CPU use, storage use, and number of messages issued. The amount of increase depends on the
activity in the Tivoli Enterprise Monitoring Server address space.
The setting for this parameter and the setting for the “KDS_X_TEMS_STORAGE_STGDEBUG” on
page 256 parameter interact.
v If the “KDS_X_TEMS_STORAGE_STGDEBUG” on page 256 parameter is included (not
commented out and not deleted), the “KDS_X_TEMS_DEBUG_TRACE” parameter must
precede it. Otherwise, “KDS_X_TEMS_DEBUG_TRACE” overrides
“KDS_X_TEMS_STORAGE_STGDEBUG” on page 256.
v If the “KDS_X_TEMS_STORAGE_STGDEBUG” on page 256 parameter is commented out or
omitted, and the setting for “KDS_X_TEMS_DEBUG_TRACE” is Y, basic storage debugging is
turned on, causing an increase in storage use.
v If the setting for the “KDS_X_TEMS_STORAGE_STGDEBUG” on page 256 parameter is N, and
the setting for “KDS_X_TEMS_DEBUG_TRACE” is Y, no storage debugging is performed.
v If the setting for the “KDS_X_TEMS_STORAGE_STGDEBUG” on page 256 parameter is Y or X,
and the setting for “KDS_X_TEMS_DEBUG_TRACE” is N, storage debugging is performed, but
no other debugging is performed.
Related parameters
v “KDS_X_TEMS_STORAGE_STGDEBUG” on page 256
KDS_X_TEMS_EIF_BFR_EVT
This parameter determines whether event buffering is enabled.
247
Optional
KMSOMTEC member of the rhilev.rte.RKANPARU library for the runtime environment of the
Parameter name
BufferEvents
Default value
Y
Permissible values
Y or N
KDS_CMS_EIF_BFR_EVT
PARMGEN name
KDS_X_TEMS_EIF_BFR_EVT
Description
Determines whether event buffering is enabled. A value of Y stores events in the library specified
by the “KDS_X_TEMS_EIF_BFR_EVT_PATH” parameter. A value of N does not store or buffer
events.
For further information, see "Whether and how to enable event forwarding" in IBM Tivoli
Related parameters
v “KDS_X_TEMS_EIF_BFR_EVT_PATH”
KDS_X_TEMS_EIF_BFR_EVT_PATH
This parameter contains the full path name of the adapter cache file.
Required if the “KDS_X_TEMS_EIF_BFR_EVT” on page 247 parameter is set to Y.
Parameter name
BufEvtPath
Default value
./TECLIB/OM_TEC.CACHE
Permissible values
KDS_CMS_EIF_BFR_EVT_PATH
PARMGEN name
KDS_X_TEMS_EIF_BFR_EVT_PATH
Description
Full path name of the adapter cache file. The format is like that of a data set name that is limited
to 5 levels with no more than 8 characters per level, separated by periods (for example,
LEVEL001.LEVEL002.LEVEL003.LEVEL004.LEVEL005).
248
Related parameters
v “KDS_X_TEMS_EIF_BFR_EVT” on page 247
KDS_X_TEMS_EIF_FLT_ATTR1
This parameter contains the name of a filter attribute.
Optional
KDS_CMS_EIF_FLT_ATTR1
PARMGEN name
KDS_X_TEMS_EIF_FLT_ATTR1
Description
Name of a filter attribute. An event matches a Filter statement when each attribute=value pair
in the Filter statement is identical to the corresponding attribute=value pair in the event. A Filter
statement must contain the event class, and optionally can include any other attribute=value
pair that is defined for the event class.
The format of a filtering statement is:
Filter:Class=class_name;attribute=value;..;attribute=value
Each statement must be on a single line. The attribute=value pair is case-sensitive.
Related parameters
v “KDS_X_TEMS_EIF_FLT_CLASS1”
KDS_X_TEMS_EIF_FLT_CLASS1
This parameter contains the name of the event class for a filter.
Optional
KDS_CMS_EIF_FLT_CLASS1
PARMGEN name
KDS_X_TEMS_EIF_FLT_CLASS1
Description
Name of the event class for a filter. A Filter statement must contain the event class.
The format of a filtering statement is:
Filter:Class=class_name;attribute=value;..;attribute=value
249
Each statement must be on a single line.
Related parameters
v “KDS_X_TEMS_EIF_FLT_ATTR1” on page 249
KDS_X_TEMS_EIF_FLT_MODE
This parameter determines whether events that match a Filter or FilterCache statement are sent to the
event server (FilterMode=IN) or discarded (FilterMode=OUT).
Optional
Parameter name
FilterMode
Default value
OUT
Permissible values
IN or OUT
KDS_CMS_EIF_FLT_MODE
PARMGEN name
KDS_X_TEMS_EIF_FLT_MODE
Description
Determines whether events that match a Filter or FilterCache statement are sent to the event
server (FilterMode=IN) or discarded (FilterMode=OUT). If you set FilterMode=IN, you must have
one or more Filter and FilterCache statements defined.
Related parameters
None
KDS_X_TEMS_FRAME_STACK_SIZE
This parameter defines the size (in bytes) of the initial save area stack that TMS:Engine allocates for each
of its tasks.
Required
monitoring server
FRAME(n)
Default value
v Default for the Configuration Tool and PARMGEN: FRAME(1025)
250
v Default in TMS:Engine: FRAME(512)
Permissible values
Do not change the value from the default except under the guidance of IBM Software
Support.
PARMGEN name
KDS_X_TEMS_FRAME_STACK_SIZE
Description
Size (in bytes) of the initial save area stack that TMS:Engine allocates for each of its tasks.
Related parameters
None
KDS_X_TEMS_LGSA_VERIFY
This parameter determines whether TMS:Engine checks that the $GSA address is available.
Required
monitoring server
LGSA(Y|N)
Default value
LGSA(Y)
Permissible values
Support.
PARMGEN name
KDS_X_TEMS_LGSA_VERIFY
Description
Determines whether TMS:Engine checks that the $GSA address is available.
Related parameters
None
This parameter defines the block size, in bytes, of the RKLVLOG file.
Required
monitoring server
LOGBLOCK(n)
Default value
v Default for the Configuration Tool and PARMGEN: LOGBLOCK(12480)
v Default in TMS:Engine: LOGBLOCK(3120)
251
Permissible values
Support.
PARMGEN name
Description
Block size, in bytes, of the RKLVLOG file.
Related parameters
v “KDS_X_TEMS_LOGBUFS_RKLVLOG_BUFSZ”
This parameter defines the number of buffers to allocate for the RKLVLOG file.
Required
monitoring server
LOGBUFS(n)
Default value
v Default for the Configuration Tool and PARMGEN: LOGBUFS(5)
v Default in TMS:Engine: LOGBUFS(2)
Permissible values
Support.
PARMGEN name
Description
Number of buffers to allocate for the RKLVLOG file. If the value of LOGBUFS is too small and
extensive logging is performed (for example, during debugging), excessive physical I/O can
increase response time. If the value of LOGBUFS is too large, storage shortages can occur.
Related parameters
v “KDS_X_TEMS_LOGBLOCK_RKLVLOG_SIZE” on page 251
KDS_X_TEMS_LSRPOOL_BUFFER_NUMn
This parameter specifies the number of virtual storage buffers, of the size specified in the
KDS_X_TEMS_LSRPOOL_BUFSIZEn parameter, to be allocated for buffer pool n in the VSAM resource
pool.
Required
monitoring server
LSRPOOL(size,number)
252
Default value
v Default for the Configuration Tool and PARMGEN: See the example in the Description
section.
v Default in TMS:Engine: No default value, but starting TMS:Engine requires at least one
LSRPOOL parameter.
Permissible values
3 - 65535 (to the maximum amount of available virtual storage in the monitoring server
address space)
PARMGEN name
KDS_X_TEMS_LSRPOOL_BUFFER_NUMn
Description
Number of virtual storage buffers, of the size specified in the
KDS_X_TEMS_LSRPOOL_BUFSIZEn parameter, to be allocated for buffer pool n in the VSAM
resource pool. You must specify a number for each buffer pool individually; you cannot string the
definitions together.
Example:
KDS_X_TEMS_LSRPOOL_BUFSIZE1
KDS_X_TEMS_LSRPOOL_BUFFER_NUM1
32768
12
8192
21
4096
400
1024
6
If you receive KLVVS026 messages identifying buffer contention, increase the number of buffers
allocated to the data set identified in the associated KLVVS021 messages.
Related parameters
v “KDS_X_TEMS_LSRPOOL_BUFSIZEn”
KDS_X_TEMS_LSRPOOL_BUFSIZEn
This parameter specifies the size (in bytes) of each virtual storage buffer in buffer pool n in the VSAM
resource pool.
Required
monitoring server
LSRPOOL(size,number)
Default value
v Default for the Configuration Tool and PARMGEN: See the example in the Description
section.
v Default in TMS:Engine: No default value, but starting TMS:Engine requires at least one
LSRPOOL parameter.
Permissible values
512, 1024, 2048, 4096, 8192, 12288, 16384, 20480, 24576, 28672, or 32768
PARMGEN name
KDS_X_TEMS_LSRPOOL_BUFSIZEn
253
Description
Size (in bytes) of each virtual storage buffer in buffer pool n in the VSAM resource pool. You
must specify a size for each buffer pool individually; you cannot string the definitions together.
Example:
32768
12
8192
21
4096
400
1024
6
Related parameters
v “KDS_X_TEMS_LSRPOOL_BUFFER_NUMn” on page 252
KDS_X_TEMS_LSRSTRNO_CONCURRENT
This parameter specifies the maximum number of concurrent VSAM requests that TMS:Engine can
process against all the VSAM data sets allocated to it.
Required
monitoring server
LSRSTRNO(n)
Default value
v Default for the Configuration Tool and PARMGEN: LSTSTRNO(255)
v Default in TMS:Engine: LSTSTRNO(32)
Permissible values
3 - 255
PARMGEN name
KDS_X_TEMS_LSRSTRNO_CONCURRENT
Description
Maximum number of concurrent VSAM requests that TMS:Engine can process against all the
VSAM data sets allocated to it.
If you receive KLVVS026 messages identifying string contention and if the LSRSTRNO value is
lower than 255, increase the value.
Related parameters
None
KDS_X_TEMS_SDUMP_SVC_SYS1_DUMP
This parameter determines whether SVC dumps are generated.
Required
monitoring server
254
SDUMP(Y|N)
Default value
SDUMP(Y) if the TMS:Engine job step is APF-authorized; SDUMP(N) otherwise.
Permissible values
Y, N, S, or M (see Description)
PARMGEN name
KDS_X_TEMS_SDUMP_SVC_SYS1_DUMP
Description
Determines whether SVC dumps are generated.
v Y directs SVC dumps to a system dump data set (SYS1.DUMPxx). Before you specify Y as the
value of this parameter, ensure that the TMS:Engine job step is APF-authorized and that the
SYS1.DUMPxx data sets are large enough to hold the contents of the TMS/Engine address
space.
v N directs formatted dumps to the RKLVSNAP data set. Avoid formatted dumps if possible,
because they disable the TMS:Engine address space for a longer time than either SVC dumps
or SYSMDUMPs, and are more difficult to analyze.
v S directs summary dumps to the RKLVSNAP data set. A summary dump consists of an
ABEND summary and a dispatcher summary, and does not provide enough information for
reliable problem analysis. Use this setting for specific testing purposes only.
v M directs ABEND dumps to a data set with the SYSMDUMP DD name. This type of dump is
not formatted by the operating system and must be analyzed with IPCS. Only the first dump
taken is captured in the SYSMDUMP data set unless the JCL specifies DISP=MOD. TMS:Engine
automatically initializes the SYSMDUMP data set with an end-of-file mark.
Related parameters
None
KDS_X_TEMS_STORAGE_RESERVE_PRI
This parameter specifies the number of kilobytes of primary (below-the-line) storage to set aside for other
routines (for example, RACF) that might perform their own GETMAINs in the monitoring server address
space.
Required
monitoring server
Parameter name
RESERVE(n,P)
Default value
v Default for the Configuration Tool and PARMGEN:
– High-availability hub: RESERVE(4096,P)
– Other monitoring servers: RESERVE(2048,P)
v Default in TMS:Engine: RESERVE(512,P)
Permissible values
See Description.
PARMGEN name
KDS_X_TEMS_STORAGE_RESERVE_PRI
255
Description
The number of kilobytes of primary (below-the-line) storage to set aside for other routines (for
example, RACF) that might perform their own GETMAINs in the monitoring server address
space. If your RESERVE value is too small, you might encounter IST566I messages from VTAM or
S80A, S878, S066, S40D, or S0F9 abends.
Related parameters
None
KDS_X_TEMS_STORAGE_STGDEBUG
This parameter determines whether to disable (N) TMS:Engine storage debugging services, or to activate
basic (Y) or extended (X) storage debugging services.
Optional
monitoring server
STGDEBUG(N|Y|X)
Default value
STGDEBUG(N)
Permissible values
STGDEBUG(N), STGDEBUG(Y), or STGDEBUG(X)
PARMGEN name
KDS_X_TEMS_STORAGE_STGDEBUG
Description
Determines whether to disable (N) TMS:Engine storage debugging services, or to activate basic (Y)
or extended (X) storage debugging services. A setting of Y or X increases storage use; X causes a
larger increase than Y.
The setting for this parameter and the setting for the “KDS_X_TEMS_DEBUG_TRACE” on page
247 parameter interact.
v If the “KDS_X_TEMS_STORAGE_STGDEBUG” parameter is included (not commented out and
not deleted), the “KDS_X_TEMS_DEBUG_TRACE” on page 247 parameter must precede it.
Otherwise, “KDS_X_TEMS_DEBUG_TRACE” on page 247 overrides
“KDS_X_TEMS_STORAGE_STGDEBUG.”
v The default setting for the “KDS_X_TEMS_STORAGE_STGDEBUG” parameter is N if the
“KDS_X_TEMS_DEBUG_TRACE” on page 247parameter is commented out or omitted, or if the
value of the “KDS_X_TEMS_DEBUG_TRACE” on page 247 parameter is N; and Y if the value of
“KDS_X_TEMS_DEBUG_TRACE” on page 247 is Y.
v If the “KDS_X_TEMS_STORAGE_STGDEBUG” parameter is commented out or omitted, and
the setting for “KDS_X_TEMS_DEBUG_TRACE” on page 247 is Y, basic storage debugging is
turned on, causing an increase in storage use.
v If the setting for the “KDS_X_TEMS_STORAGE_STGDEBUG” parameter is N, and the setting
for “KDS_X_TEMS_DEBUG_TRACE” on page 247 is Y, no storage debugging is performed.
v If the setting for the “KDS_X_TEMS_STORAGE_STGDEBUG” parameter is Y or X, and the
setting for “KDS_X_TEMS_DEBUG_TRACE” on page 247 is N, storage debugging is performed,
but no other debugging is performed.
Related parameters
v “KDS_X_TEMS_DEBUG_TRACE” on page 247
256
KDS_X_TEMS_TASKS_ATTACHED_NUM
This parameter specifies the number of general-purpose subtasks to be attached in the monitoring server
address space.
Required
monitoring server
TASKS(n)
Default value
The number of available processors.
Permissible values
Support.
PARMGEN name
KDS_X_TEMS_TASKS_ATTACHED_NUM
Description
Number of general-purpose subtasks to be attached in the monitoring server address space. If the
monitoring server is running on a multiprocessor, the TASKS default increases both throughput
and CPU usage.
Related parameters
None
KDS_X_TEMS_WTO
This parameter determines whether the monitoring server address space issues Write To Operator (WTO)
messages.
Required
monitoring server
WTO(Y|N)
Default value
WTO(N)
Permissible values
Y or N
PARMGEN name
KDS_X_TEMS_WTO
Description
Determines whether the monitoring server address space issues Write To Operator (WTO)
messages. WTOs write information and exception condition messages to the operator consoles.
Alert messages are always written to the consoles.
Related parameters
None
257
Parameters for the high-availability hub monitoring server
The parameters for the high-availability hub monitoring server updates are explained in this section.
KDS_TEMS_HA_TYPE
This parameter determines whether to configure the Tivoli Enterprise Monitoring Server as a
Required
Panel name
Panel ID
KDS62PP1
Field
Hub TEMS type
Default value
None
Permissible values
HA or none
KDS_CMS_HA_TYP
PARMGEN name
KDS_TEMS_HA_TYPE
Description
Determines 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 runtime
environment, without monitoring agents, and can be configured on the same LPAR with a remote
monitoring server. This configuration allows the hub to be relocated to any suitable LPAR in the
sysplex with no changes, and with minimal disruption to the components connecting to the hub.
Related parameters
v “KDS_HUB_TEMS_HA_TYPE” on page 165
v “KDS_TEMS_HA_EXCL_LIST” on page 206
v “KDS_TEMS_VIRTUAL_IP_ADDRESS” on page 233
258
Chapter 6. Enhanced 3270 user interface (KOB) parameters
The parameters that control the OMEGAMON enhanced 3270 user interface are explained in this section.
The OMEGAMON enhanced 3270 user interface has its own set of common configuration parameters,
each of which begins with "KOB". The KOB parameters are related to the following parameters, described
elsewhere in this reference:
KOB_TOM_STC
This parameter is the name of the started task for the OMEGAMON enhanced 3270 user interface's Tivoli
OMEGAMON Manager (TOM).
Value becomes the name of the TOM started task procedure member in the
rhilev.rtename.RKANSAMU library.
N/A
Default value
CANSTOM
Permissible values
Panel name
SPECIFY CONFIGURATION VALUES
Panel ID
KOB70P1
Field
OMEGAMON Enhanced 3270 UI
Default value
CANSTOM
Permissible values
KOB_TOM_STC
PARMGEN name
KOB_TOM_STC
Description
This parameter is the name of the started task that starts the OMEGAMON enhanced 3270 user
interface's Tivoli OMEGAMON Manager (TOM).
Related parameters
259
v “KOB_TOM_VTAM_APPL_LOGON”
KOB_TOM_VTAM_APPL_LOGON
This parameter specifies the name that will be used to build the VTAM logon APPLID for the
OMEGAMON enhanced 3270 user interface's Tivoli OMEGAMON Manager (CTDOBN).
Value is included in the TOM VTAM major node member in the rhilev.rtename.RKANSAMU
library or in the RTE_VTAM_GBL_MAJOR_NODE member in RKANSAMU.
N/A
Default value
CTDOBAP
Permissible values
Panel name
Panel ID
KOB70P1
Field
VTAM information: Appl ID
Default value
CTDOBAP
Permissible values
PARMGEN name
Description
This parameter specifies the VTAM logon APPLID for the OMEGAMON enhanced 3270 user
interface's Tivoli OMEGAMON Manager (CTDOBN).
Note: If you use the global VTAM major node member specified on the
RTE_VTAM_GBL_MAJOR_NODE parameter, the VTAM APPLID associated with CTDOBN is
automatically included in the RTE_VTAM_GBL_MAJOR_NODE member in RKANSAMU.
Related parameters
260
KOB_TOM_VTAM_NODE
This parameter specifies the name used to build the VTAM node entry for the OMEGAMON enhanced
3270 user interface's Tivoli OMEGAMON Manager (CTDOBN).
Value specified becomes the name of the TOM VTAM major node member in the
rhilev.rtename.RKANSAMU library.
N/A
Default value
CTDOBN
Permissible values
Panel name
Panel ID
KOB70P1
Field
VTAM information: Node name
Default value
CTDOBN
Permissible values
KOB_TOM_VTAM_NODE
PARMGEN name
KOB_TOM_VTAM_NODE
Description
This parameter specifies the name used to build the VTAM node entry for the OMEGAMON
enhanced 3270 user interface's Tivoli OMEGAMON Manager (CTDOBN).
Note: If you use the global VTAM major node member specified on the
RTE_VTAM_GBL_MAJOR_NODE parameter, the VTAM APPLID associated with CTDOBN is
automatically included in the RTE_VTAM_GBL_MAJOR_NODE member in RKANSAMU.
Related parameters
Chapter 6. Enhanced 3270 user interface (KOB) parameters
261
262
This appendix contains information about the publications related to the OMEGAMON XE products and
to IBM Tivoli Monitoring and the commonly shared components of Tivoli Monitoring Server.
These publications are listed in the following categories:
v “IBM Tivoli Monitoring library”
v “Documentation for the base agents” on page 264
v “Related publications” on page 265
v “Other sources of documentation” on page 265
See IBM Tivoli Monitoring and OMEGAMON XE Products: Documentation Guide, SC23-8816, for information
about accessing and using the publications. You can find the Documentation Guide in the IBM Tivoli
Monitoring and OMEGAMON XE Information Center at http://publib.boulder.ibm.com/infocenter/
tivihelp/v15r1/index.jsp. To open the Documentation Guide in the information center, select Using the
publication in the Contents pane. To find a list of new and changed publications, click What's new on
the Welcome page of the IBM Tivoli Monitoring and OMEGAMON XE Information Center. To find
publications from the previous version of a product, click Previous information centers on the Welcome
page for the product.
IBM Tivoli Monitoring library
The following publications provide information about IBM Tivoli Monitoring and about the commonly
shared components of Tivoli Management Services:
v Quick Start Guide, GI11-8058
Introduces the components of IBM Tivoli Monitoring.
v Installation and Setup Guide, GC32-9407
Provides instructions for installing and configuring IBM Tivoli Monitoring components on Windows,
Linux, and UNIX systems.
v Program Directory for IBM Tivoli Management Services on z/OS, GI11-4105
Gives instructions for the SMP/E installation of the Tivoli Management Services components on z/OS.
v Configuring the Tivoli Enterprise Monitoring Server on z/OS, SC32-9463Gives detailed instructions for
using the Configuration Tool to configure Tivoli Enterprise Monitoring Server on z/OS systems.
Includes scenarios for using batch mode to replicate monitoring environments across the z/OS
enterprise. Also provides instructions for setting up security and for adding application support to a
Tivoli Enterprise Monitoring Server on z/OS.
v Administrator's Guide, SC32-9408
Describes the support tasks and functions required for the Tivoli Enterprise Portal Server and clients,
including Tivoli Enterprise Portal user administration.
v High-Availability Guide for Distributed Systems, SC23-9768
Gives instructions for several methods of ensuring the availability of the IBM Tivoli Monitoring
components.
v Tivoli Enterprise Portal online help
Provides context-sensitive reference information about all features and customization options of the
Tivoli Enterprise Portal. Also gives instructions for using and administering the Tivoli Enterprise
Portal.
v Tivoli Enterprise Portal User's Guide, SC32-9409
263
v
v
v
v
v
v
Complements the Tivoli Enterprise Portal online help. The guide provides hands-on lessons and
detailed instructions for all Tivoli Enterprise Portal features.
Command Reference, SC32-6045
Provides detailed syntax and parameter information, as well as examples, for the commands you can
use in IBM Tivoli Monitoring.
Troubleshooting Guide, GC32-9458
Provides information to help you troubleshoot problems with the software.
Messages, SC23-7969
Lists and explains messages generated by all IBM Tivoli Monitoring components and by z/OS-based
Tivoli Management Services components (such as Tivoli Enterprise Monitoring Server on z/OS and
TMS:Engine).
IBM Tivoli Universal Agent User's Guide, SC32-9459
Introduces you to the IBM Tivoli Universal Agent, an agent of IBM Tivoli Monitoring. The IBM Tivoli
Universal Agent enables you to use the monitoring and automation capabilities of IBM Tivoli
Monitoring to monitor any type of data you collect.
IBM Tivoli Universal Agent API and Command Programming Reference Guide. SC32-9461
Explains the procedures for implementing the IBM Tivoli Universal Agent APIs and provides
descriptions, syntax, and return status codes for the API calls and command-line interface commands.
Agent Builder User's Guide, SC32-1921
Explains how to use the Agent Builder for creating monitoring agents and their installation packages,
and for adding functions to existing agents.
Documentation for the base agents
If you purchased IBM Tivoli Monitoring as a product, you received a set of base monitoring agents as
part of the product. If you purchased a monitoring agent product (for example, an OMEGAMON XE
product) that includes the commonly shared components of Tivoli Management Services, you did not
receive the base agents.
The following publications provide information about using the base agents.
v Operating system agents:
– Windows OS Agent User's Guide, SC32-9445
– UNIX OS Agent User's Guide, SC32-9446
– Linux OS Agent User's Guide, SC32-9447
– i5/OS Agent User's Guide, SC32-9448
– UNIX Log Agent User's Guide, SC32-9471
v Agentless operating system monitors:
– Agentless Monitoring for Windows Operating Systems User's Guide, SC23-9765
– Agentless Monitoring for AIX Operating Systems User's Guide, SC23-9761
– Agentless Monitoring for HP-UX Operating Systems User's Guide, SC23-9763
– Agentless Monitoring for Solaris Operating Systems User's Guide, SC23-9764
– Agentless Monitoring for Linux Operating Systems User's Guide, SC23-9762
v Warehouse agents:
– Warehouse Summarization and Pruning Agent User's Guide, SC23-9767
– Warehouse Proxy Agent User's Guide, SC23-9766
v System P agents:
– AIX Premium Agent User's Guide, SA23-2237
– CEC Base Agent User's Guide, SC23-5239
264
– HMC Base Agent User's Guide, SA23-2239
– VIOS Premium Agent User's Guide, SA23-2238
v Other base agents:
– Monitoring Agent for IBM Tivoli Monitoring 5.x Endpoint User's Guide, SC32-9490
Related publications
You can find useful information about related products in the IBM Tivoli Monitoring and OMEGAMON
XE Information Center at http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/index.jsp.
Other sources of documentation
You can also obtain technical documentation about IBM Tivoli Monitoring and related products from the
following sources:
v IBM Tivoli Open Process Automation Library (OPAL)
http://www.ibm.com/software/tivoli/opal
OPAL is an online catalog that contains integration documentation and other downloadable product
extensions.
v Redbooks
http://www.redbooks.ibm.com/
IBM Redbooks® and Redpapers include information about products from platform and solution
perspectives.
v Technotes
Technotes provide the latest information about known product limitations and workarounds. You can
find Technotes through the IBM Software Support website at http://www.ibm.com/software/support/
probsub.html, or more directly through your product website, which contains a link to Technotes
(under Solve a problem).
v Tivoli wikis on the IBM developerWorks® website
Tivoli Wiki Central at http://www.ibm.com/developerworks/wikis/display/tivoli/Home is the home
for interactive wikis that offer best practices and scenarios for using Tivoli products. The wikis contain
white papers contributed by IBM employees, and content created by customers and business partners.
Two of these wikis are of particular relevance to IBM Tivoli Monitoring:
– Tivoli Distributed Monitoring and Application Management Wiki at http://www.ibm.com/
developerworks/wikis/display/tivolimonitoring/Home provides information about IBM Tivoli
Monitoring and related distributed products, including IBM Tivoli Composite Application
Management products.
– Tivoli System z® Monitoring and Application Management Wiki at http://www.ibm.com/
developerworks/wikis/display/tivoliomegamon/Home provides information about the
OMEGAMON XE products, NetView for z/OS, Tivoli Monitoring Agent for z/TPF, and other
System z monitoring and application management products.
265
266
Support information
If you have a problem with your IBM software, you want to resolve it quickly. IBM provides the
following ways for you to obtain support:
Online
Go to the IBM Software Support site at http://www.ibm.com/software/support/probsub.html
and follow the instructions.
IBM Support Assistant
The IBM Support Assistant (ISA) is a free local software serviceability workbench that helps you
resolve questions and problems with IBM software products. The ISA provides quick access to
support-related information and serviceability tools for problem determination. To install the ISA
software, go to http://www.ibm.com/software/support/isa.
Troubleshooting Guide
For more information about resolving problems, see the product's Troubleshooting Guide.
267
268
Notices
This information was developed for products and services offered in the U.S.A. IBM may not offer the
products, services, or features discussed in this document in other countries. Consult your local IBM
representative for information on the products and services currently available in your area. Any
reference to an IBM product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product, program, or service that
does not infringe any IBM intellectual property right may be used instead. However, it is the user's
responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in this
document. The furnishing of this document does not give you any license to these patents. You can send
license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785 U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property
Department in your country or send inquiries, in writing, to:
Intellectual Property Licensing
Legal and Intellectual Property Law
IBM Japan, Ltd.
1623-14, Shimotsuruma, Yamato-shi
Kanagawa 242-8502 Japan
The following paragraph does not apply to the United Kingdom or any other country where such
provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS"
WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR
FITNESS FOR A PARTICULAR PURPOSE.
Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore,
this statement might not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically
made to the information herein; these changes will be incorporated in new editions of the publication.
IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.
Any references in this information to non-IBM websites are provided for convenience only and do not in
any manner serve as an endorsement of those websites. The materials at those websites are not part of
the materials for this IBM product and use of those websites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes appropriate without
incurring any obligation to you.
269
Licensees of this program who wish to have information about it for the purpose of enabling: (i) the
exchange of information between independently created programs and other programs (including this
one) and (ii) the mutual use of the information which has been exchanged, should contact:
IBM Corporation
2Z4A/101
11400 Burnet Road
Austin, TX 78758 U.S.A.
Such information may be available, subject to appropriate terms and conditions, including in some cases
payment of a fee.
The licensed program described in this document and all licensed material available for it are provided
by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or
any equivalent agreement between us.
Any performance data contained herein was determined in a controlled environment. Therefore, the
results obtained in other operating environments may vary significantly. Some measurements may have
been made on development-level systems and there is no guarantee that these measurements will be the
same on generally available systems. Furthermore, some measurement may have been estimated through
extrapolation. Actual results may vary. Users of this document should verify the applicable data for their
specific environment.
Information concerning non-IBM products was obtained from the suppliers of those products, their
published announcements or other publicly available sources. IBM has not tested those products and
cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM
products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of
those products.
This information contains examples of data and reports used in daily business operations. To illustrate
them as completely as possible, the examples include the names of individuals, companies, brands, and
products. All of these names are fictitious and any similarity to the names and addresses used by an
actual business enterprise is entirely coincidental.
Trademarks
IBM, the IBM logo, and ibm.com® are trademarks or registered trademarks of International Business
Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be
trademarks of IBM or other companies. A current list of IBM trademarks is available on the web at
“Copyright and trademark information” at www.ibm.com/legal/copytrade.shtml.
Linux is a trademark of Linus Torvalds in the United States, other countries, or both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the
United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Other company, product, and service names may be trademarks or service marks of others.
270
Glossary
A
activity. One phase within a sequence of predefined steps called a policy that automate system responses to a
situation that has fired (that is, become true).
administration mode. See workspace administration mode.
Advanced Encryption Standard. An encryption algorithm for securing sensitive but unclassified material designed
by the National Institute of Standards and Technology (NIST) of the U.S. Department of Commerce. AES is intended
to be a more robust replacement for the Data Encryption Standard. The specification calls for a symmetric algorithm
(in which the same key is used for both encryption and decryption), using block encryption of 128 bits and
supporting key sizes of 128, 192 and 256 bits as a minimum. The algorithm must offer security of a sufficient level to
protect data for the next 20 to 30 years. It had to be easily implemented in hardware and software and had to offer
good defenses against various attack techniques. AES has since been published as Federal Information Processing
Standard (FIPS) 197, which specifies the encryption algorithm that all sensitive, unclassified documents must use.
AES. See Advanced Encryption Standard.
affinity. A label that classifies objects by managed system.
agent. Software installed on systems you want to monitor that collects data about an operating system, subsystem,
or application running on each such system. Because an executable gathers information about a single managed
system, there is always a one-to-one correspondence between them.
agentless monitor. An agentless monitor uses a standard API (such as SNMP or CIM) to identify and notify you of
common problems with the operating system of the computer running the API. Thus, as their name implies, the
agentless monitors can retrieve monitoring and performance data without requiring OS agents on the computers
being monitored: An agentless monitor enables you to monitor a remote, distributed node without first installing any
Tivoli Management Services code on it. The agentless monitors provide monitoring, data gathering, and event
management for Windows, Linux, AIX®, HP-UX, and Solaris systems.
agentless monitoring server. A computer with an OS agent installed that has one or more agentless monitors
running on it. Each agentless monitoring server can support up to 10 active instances of the various types of
agentless monitors, in any combination. Each instance can communicate with up to 100 remote nodes, which means a
single agentless monitoring server can support as many as 1000 monitored systems.
alert. A warning message that appears at a console to indicate that something has occurred that may require
intervention.
alert monitor. A special type of monitoring agent that collects and relays alert information to the monitoring server.
Sources of alerts include message logs, system console logs, and network and system management products.
algorithm. A set of well-defined rules for the solution of a problem in a finite number of steps. For example, a full
statement of an arithmetic procedure for evaluating sin(x) to a stated precision.
API. See Application Programming Interface.
application. A software component or collection of software components that performs specific user-oriented work
on a computer.
Application Programming Interface. A set of multiple subprograms and data structures and the rules for using
them that together enable application development using a particular language and, often, a particular operating
environment. An API is a functional interface supplied by the operating system or by a separately licensed program
that allows an application program written in a high-level language to use specific data or functions of the operating
system or the licensed program.
arithmetic expression. A statement containing any combination of values joined together by one or more arithmetic
operators in such a way that the statement can be processed as a single numeric value.
271
arithmetic operator. A symbol representing a mathematical operation (addition, subtraction, multiplication, division,
or exponentiation), such as +, -, *, /, or ^.
associate. The process of linking a situation with a Navigator item that enables a light to go on and a sound to play
for an open event. Predefined situations are associated automatically, as are situations created or edited through the
Navigator item pop-up menu. When you open the Situation editor from the toolbar, any situations you create cannot
be associated with a Navigator item during this editing session. You must close the Situation editor, then open it
again from the pop-up menu of the Navigator item with which the situation should be associated.
attribute. (1) A system or application element being monitored by the monitoring agent, such as Disk Name and
Disk Read/Writes Per Second. (2) A characteristic of a managed object; that is, a field in the data structure of a
managed object or in the workspace associated with that managed object. (3) A field in an ODBC-compliant database.
attribute group. A set of related attributes that can be combined in a data view or a situation. When you open the
view or start the situation, data samples of the selected attributes are retrieved. Each type of monitoring agent has its
own set of attribute groups.
autonomous-mode monitoring agents. These monitoring agents run without communicating directly with a Tivoli
Enterprise Monitoring Server. An autonomous agent can emit Simple Network Management Protocol (SNMP) traps
and Event Integration Facility (EIF) events directly to an OMNIbus ObjectServer for private situations (but not for
enterprise situations) that have turned true.
B
baroc files. Basic Recorder of Objects in C files define event classes for a particular Tivoli Enterprise Console event
server. Baroc files also validate event formats based on these event-class definitions.
browser client. The software installed with the Tivoli Enterprise Portal Server that is downloaded to your
computer when you start the Tivoli Enterprise Portal in browser mode. The browser client runs under the control of
the Tivoli Enterprise Portal Server's integral web server within a Web browser.
C
capacity planning. The process of determining the hardware and software configuration required to accommodate
the anticipated workload on a system.
chart. A graphical view of data returned from a monitoring agent. A data point is plotted for each attribute chosen
and, for bar and pie charts, a data series for each row. Types of charts include pie, bar, plot, and gauge.
CIM. See Common Information Model.
class file. A file containing Java™ object code for a single Java object class.
class loader. A Java component that loads Java class files.
client. An application that receives requested data from a server.
client/server architecture. An architecture in which the client (usually a personal computer or workstation) is the
machine requesting data or services and the server is the machine supplying them. Servers can be microcomputers,
minicomputers, or mainframes. The client provides the user interface and may perform application processing. In
IBM Tivoli Monitoring, the Tivoli Enterprise Portal is the client to the Tivoli Enterprise Portal Server, whereas the
Tivoli Enterprise Portal Server is the client to the Tivoli Enterprise Monitoring Server. On the other hand, in IBM
Tivoli Business Service Manager (TBSM), the Tivoli Enterprise Portal Server is the client to the Tivoli Enterprise
Monitoring Server (as before) and the server to the Tivoli Integrated Portal.
A database server maintains the databases and processes requests from the client to extract data from or to update
the database. An application server provides additional business-support processing for its clients.
Common Information Model. An XML-based standard for defining device and application characteristics so that
system administrators and management programs can monitor and control them using the same set of tools,
regardless of their differing architectures. CIM provides a more comprehensive toolkit for such management
functions than the Simple Network Management Protocol.
272
Common Object Request Broker Architecture. An industry specification for the design and standardization of
different types of object request brokers (ORBs). ORBs allow different computers to exchange object data; CORBA
enables ORBs from different software vendors (often running under dissimilar computer systems and operating
systems) to exchange object data. CORBA is an architecture and specification that facilitates communication among
program components in a network using objects. The Tivoli Enterprise Portal Server is a CORBA implementation.
condition. An expression that evaluates to either true or false. It can be expressed in natural language text, in
mathematically formal notation, or in a machine-readable language.
Configuration Tool, z/OS (ICAT). A REXX-based tool for configuring OMEGAMON XE products running on
zSeries® systems, once they have been installed using the System Modification Program/Extended (SMP/E) tool.
Configure History permission. Your user ID must have Configure History permission to open the History
Collection Configuration window for setting up history files and data rolloff. If you do not have this permission, you
will not see the menu item or tool for historical configuration.
CORBA. See Common Object Request Broker Architecture.
critical state. The indication that a situation associated with a Navigator item is in an unacceptable state and that
you must take corrective action. The critical state is represented by the color red.
Custom Navigator Views permission. Your Tivoli Enterprise Portal user ID has a Modify checkbox for the Custom
Navigator Views feature. This permission must be enabled for you to open the Navigator view editor to maintain
and update Navigator views.
D
Data Encryption Standard. A widely used method of private-key data encryption that originated at IBM in 1977
and was adopted by the U.S. Department of Defense. DES supports 72 quadrillion or more possible encryption keys;
for each message, the key is chosen at random from among this enormous number of possible keys. Like all other
private-key cryptographic methods, both the sender and the receiver must know and use the same private key.
DES applies a 56-bit key to each 64-bit block of data. Although this is considered strong encryption, many companies
use triple DES, which applies three keys in succession.
data warehouse. A central repository for the data that an organization's business systems collect. A data warehouse
usually comprises multiple databases.
The data warehouse used by IBM Tivoli Monitoring is called the Tivoli Data Warehouse.
database. A collection of both interrelated and independent data items that is stored together on a computer disk to
serve multiple applications.
datasource name (DSN). The name that is stored in the database server and that enables you to retrieve
information from the database through ODBC. The DSN includes such information as the database name, database
driver, user ID, and password.
datasources. Data pertaining to J2EE data sources, which are logical connections to database subsystems.
DB2® for the workstation. IBM's DB2 Database for Linux, UNIX, and Windows systems is a relational database
management system that runs on desktop computers. You install a DB2 database on the same system as the Tivoli
Enterprise Portal Server; it stores the portal server's queries, customized workspaces, user IDs, and custom
Navigator views. DB2 Database for Linux, UNIX, and Windows can also serve as the data repository for the Tivoli
Data Warehouse, which provides long-term storage of historical monitoring information.
default. An attribute, value, or option whose setting is assumed when none is explicitly specified.
Demilitarized Zone. The area of a Worldwide Web application that enables a company to host Internet services
without allowing unauthorized access.
Derby. An open-source, public-domain, relational database management system implemented in Java and designed
to conform to accepted database standards (such as SQL and JDBC) and yet still feature a small machine footprint.
Derby came about when IBM contributed its Cloudscape database manager to the Apache project. IBM Tivoli
Glossary
273
Monitoring implements Derby as an embedded database within its Tivoli Enterprise Portal Server; in other words,
the database is installed with the portal server, and it runs within the portal server's Java virtual machine.
DES. See Data Encryption Standard.
desktop client. Software supplied with IBM Tivoli Monitoring that you install on a workstation that you plan to
use for interacting with the Tivoli Enterprise Portal Server and the Tivoli Enterprise Monitoring Server. The
desktop Tivoli Enterprise Portal client provides the graphical user interface into the IBM Tivoli Monitoring network.
detailed attribute name. The name used in formulas, expert advice, Take Action commands, and headers and
footers when referencing a monitoring agent attribute. In the Properties and Situation editors, first click Show
Formula, then check Show detailed formula to see the detailed attribute name.
display item. An attribute designated to further qualify a situation. With a display item set for a multiple-row
attribute group, the situation continues to look at the other rows in the sample and opens more events if other rows
qualify. The value displays in the event workspace and in the message log and situation event console views. You
can select a display item when building a situation with a multiple-row attribute group.
distribution. The managed systems on which the situation is running.
DLL. See Dynamic Link Library.
DMZ. See Demilitarized Zone.
drill down. To access information by starting with a general category and moving through the hierarchy of
information, for example, in a database, to move from file to record to field.
DSN. See datasource name.
DVIPA. See Dynamic Virtual IP Addressing.
Dynamic Link Library. A composite of one or more executable objects that is bound together by a linking procedure
and loaded at run time (rather than when the application is linked). The code and data in a dynamic link library can
be shared by several applications simultaneously. DLLs apply only to Windows operating environments.
Dynamic Virtual IP Addressing. This feature of IP allows System Z to reassign IP addresses in event of a failure in
an application, TCP/IP stack, or LPAR.
E
EIB. See Enterprise Information Base.
EIF. See Event Integration Facility.
endcode. You assign endcodes in a policy as you connect one activity to another. The endcode indicates the result
of this activity that will trigger the next activity.
enhanced 3270 user interface. The OMEGAMON enhanced 3270 user interface is the latest generation of user
interfaces for the OMEGAMON Monitoring Agents. Used in conjunction with the Tivoli Enterprise Monitoring
Server, this new 3270-based user interface enables you to monitor the performance of your site’s z/OS systems,
applications, and devices and helps you identify and troubleshoot problems with those monitored resources.
The OMEGAMON Monitoring Agents that support the enhanced 3270 user interface provide predefined workspaces
that enable you to quickly and easily diagnose problems with monitored resources and then invoke the appropriate
Take Action commands to correct them. You can customize the workspaces to suit your requirements, and even
design and create your own workspaces and navigation.
Because the enhanced 3270 user interface exploits data collected by OMEGAMON Monitoring Agents, viewing data
in the interface requires at least one Tivoli Enterprise Monitoring Server running in your environment, as well as
monitoring agents that support the interface. When you navigate to a particular agent’s workspace, one or more data
queries are sent to the monitoring server; the monitoring server collects the data from the target agent or agents and
sends the data to the interface for display via the workspace.
274
Enterprise Information Base. A database used by the Tivoli Enterprise Monitoring Server that serves as a
repository of shared objects for all systems across your enterprise. The EIB stores all persistent data, including
situations, policies, user definitions, and managed-object definitions.
enterprise situation. A situation that is created for a Tivoli Enterprise Monitoring Agent that reports events to the
Tivoli Enterprise Monitoring Server it connects to. Enterprise situations are centrally defined at the monitoring
server and distributed at agent startup. See also private situation.
event. An action or some occurrence, such as running out of memory or completing a transaction, that can be
detected by a situation. Events cause a change in the state of a managed object associated with a situation, thereby
making the situation true and causing an alert to be issued.
event indicator. The colored icon that displays over a Navigator item when an event opens for a situation.
Event Integration Facility. An application programming interface that external applications can invoke to create,
send, or receive Tivoli Enterprise Console events. These events are referred to as either EIF events or TEC/EIF
events.
event item. A Navigator item that shows when you open the event workspace for a true situation (by selecting it
from the event flyover list or from the situation event console pop-up menu).
event sound. The sound file that plays when an event opens. This sound file is set in the Situation editor when the
situation is associated with a Navigator item and can differ for different Navigator items.
expert advice. A description within the Situation editor of each situation provided with a monitoring agent to help
you quickly understand and interpret events that arise when situations becomes true.
Extensible Markup Language. A data-description language derived from Standard Generalized Markup Language
(SGML). A tool for encoding messages so they describe their own fields, XML allows you to format a document as a
data structure. As program objects, such documents can have their contents and data hidden within the object; this
allows you to control who can manipulate the document and how. In addition, documents can carry with them the
object-oriented procedures called methods. The XML standard aids in exchanging data between local and remote
applications and users.
F
filter criteria. These limit the amount of information returned to the data view in response to a query. You can
apply a prefilter to the query to collect only certain data, or apply a postfilter to the view properties to show only a
selected subset of the information collected.
fix pack. A tested collection of all cumulative maintenance for a product, up to the release of the fix pack. It can
also contain fixes that have not been shipped previously, but it should contain no new function.
G
georeferenced map. A special type of graphic that has built-in knowledge of latitude and longitude and can be
zoomed into and out of quickly. The Tivoli Enterprise Portal uses proprietary .IVL files generated with the
map-rendering component. These files cannot be opened or saved in a graphic editor.
GSKit. The Global Security Toolkit provides SSL (Secure Sockets Layer) processing within protocols such as SPIPE
and HTTPS. On z/OS systems, GSKit is known as the Integrated Cryptographic Service Facility, or ICSF.
H
hierarchical. Describes data that is organized on computer systems using a hierarchy of containers, often called
folders (that is, directories) and files. In this scheme, folders can contain other folders and files. The successive
creation of folders within folders defines the levels of organization, which is the hierarchy.
Glossary
275
historical collection. A definition for collecting and storing data samples for historical reporting. The historical
collection identifies the attribute group, any row filtering you have assigned, the managed system distribution,
frequency of data collection, where to store it for the short term, and whether to save data long term (usually to the
Tivoli Data Warehouse).
historical data management. The procedures applied to short-term binary history files that roll off historical data to
either the Tivoli Data Warehouse or to delimited text files (the krarloff utility on UNIX or Windows; ddname
KBDXTRA for the z/OS Persistent Datastore), and then delete entries in the short-term history files over 24 hours
old, thereby making room for new entries.
hot standby. A redundant Tivoli Enterprise Monitoring Server running on a distributed system that, if the primary
or hub monitoring server should fail, assumes the responsibilities of the failed monitoring server.
HTTP. The Hypertext Transfer Protocol is a suite of Internet protocols that transfer and display hypertext documents
within web browsers.
HTTP sessions. Data related to invocations of specific Worldwide Web sites.
HTTPS. The Secure Hypertext Transport Protocol is an implementation of the Hypertext Transport Protocol (HTTP)
that relies on either the Secure Sockets Layer (SSL) API or the Transport Layer Security (TLS) API to provide your
users with secure access to your site's web server. These APIs encrypt and then decrypt user page requests as well as
the pages returned by the web server.
hub monitoring server. (1) A central host system that collects the status of situations running on your systems. (2)
The Tivoli Enterprise Monitoring Server that your site has selected to act as the focal point to which all portal
servers and remote monitoring servers in this monitored network connect. A remote monitoring server passes its
collected data to the hub to be made available to clients, creating an enterprise-wide view.
I
IBM Tivoli Monitoring. A client/server implementation for monitoring enterprise-wide computer networks that
comprises a Tivoli Enterprise Monitoring Server, an application server known as the Tivoli Enterprise Portal
Server, one or more Tivoli Enterprise Portal clients, and multiple monitoring agents that collect and distribute data
to the monitoring server. IBM Tivoli Monitoring also provides a data warehouse, the Tivoli Data Warehouse, where
historical monitoring data can be accumulated for later trend analysis and long-term problem identification.
IIOP. See Internet Inter-ORB Protocol.
input data. Data provided to the computer for further processing. See also output data.
integral web server. A proprietary web server developed for IBM Tivoli Monitoring that is installed and
configured automatically with the Tivoli Enterprise Portal Server. You enter the URL of the integral web server to
start the Tivoli Enterprise Portal client in browser mode.
Internet Inter-ORB Protocol (IIOP). An Internet communications protocol that runs on distributed platforms. Using
this protocol, software programs written in different programming languages and running on distributed platforms
can communicate over the Internet.
IIOP, a part of the CORBA standard, is based on the client/server computing model, in which a client program
makes requests of a server program that waits to respond to client requests. With IIOP, you can write client programs
that communicate with your site's existing server programs wherever they are located without having to understand
anything about the server other than the service it performs and its address (called the Interoperable Object
Reference, IOR, which comprises the server's port number and IP address).
Interoperable Object Reference (IOR). Connects clients to the Tivoli Enterprise Portal Server. The IOR identifies a
remote object, including such information as name, capabilities, and how to contact it. The URL may include an IOR
because it goes through the web server; the portal server uses it to tell the client which IOR to fetch. Once it does
that, the portal server extracts the host and port information and tells the client where to route the request.
interval. The number of seconds that have elapsed between one sample and the next. A sample is the data that the
Tivoli Enterprise Monitoring Agent collects for the monitoring server.
IOR. See Interoperable Object Reference.
276
J
Java Database Connectivity (JDBC). A standard API that enables application developers to access and update
relational databases (RDBMSes) from within Java programs. The JDBC standard is based on the X/Open SQL Call
Level Interface (CLI) and complies with the SQL-92 Entry Level standard; it provides a DBMS-independent interface
that enables SQL-compliant database access for Java programmers.
Java Management Extensions (JMX) API . A set of Java classes for application and network management in J2EE
environments. JMX provides Java programmers a set of native Java tools called MBeans (managed beans) that
facilitate network, device, and application management. JMX provides a Java-based alternative to the Simple
Network Management Protocol.
JDBC. See Java Database Connectivity.
JMX. See Java Management Extensions API.
L
LDAP. See Lightweight Directory Access Protocol.
Lightweight Directory Access Protocol. A protocol that conforms to the International Standards Organization's
X.500 directory standard and uses TCP/IP to access directory databases where applications can store and retrieve
common naming and location data. For example, applications can use LDAP to access such directory information as
email addresses, service configuration parameters, and public keys.
location broker. The component of the Tivoli Enterprise Monitoring Server that manages connections for the hub
monitoring server, enabling it to find all other IBM Tivoli Monitoring components, including remote monitoring
servers, the Tivoli Enterprise Portal Server, and monitoring agents.
M
managed object. An icon created in the Tivoli Enterprise Portal from a managed object template that represents
resources you monitor using situations. Managed objects are converted to items in the Navigator's Logical view.
managed system. A particular operating system, subsystem, or application in your enterprise where a monitoring
agent is installed and running. This is any system that IBM Tivoli Monitoring is monitoring.
managed system group. A named, heterogeneous group of both similar and dissimilar managed systems organized
for the distribution of historical collections, situations, and policies, and for assignment to queries and items in
custom Navigator views. For example, you might create a managed system group named IT_London for a
geographic region and another named Credit_Approval for a functional area of your organization. Managed system
groups are created, modified, or deleted either by the Tivoli Enterprise Portal's Object Group editor or via the tacmd
CLI command with the createsystemlist, editsystemlist, or deletesystemlist keywords; they are maintained by the
Tivoli Enterprise Monitoring Server.
If a managed system group is updated (usually when a constituent managed system is added or deleted), then all the
historical collections, situations, and policies that use that group are redistributed to all managed systems in the
group.
MBeans. Managed beans are Java objects that represent managed resources such as devices, services, and
applications. The management functions are provided by the MBean server.
MDM. See Multidomain Management.
method. In object-oriented programming, the software that implements an object's behavior as specified by an
operation.
Microsoft Management Console. This feature of Microsoft's various Windows Server environments provides a
centralized, consistent, and extensible interface to Windows' various monitoring and management utilities. In
particular, MMC manages directory services, job scheduling, event logging, performance monitoring, and user
environments.
Glossary
277
middleware. Software that enables the exchange of information between components in a distributed computing
environment. The middleware is the data-exchange and communications channel that allows programs to cooperate
with each other without having to know details about how they are implemented or where they are deployed.
Middleware typically provides a range of related facilities such as persistence, auditing, and the ability to build a
transactional unit of work. IBM's CICS and WebSphere® MQ are examples of middleware.
migrating. Preserving your customized configuration data so that you can use it again after installing a newer
version of the product.
MMC. See Microsoft Management Console.
monitor. An entity that performs measurements to collect data pertaining to the performance, availability, reliability,
or other attributes of applications or the systems on which those applications rely. These measurements can be
compared to predefined thresholds. If a threshold is exceeded, administrators can be notified, or predefined
automated responses can be performed.
monitor interval. A specified time, scalable to seconds, minutes, hours, or days, for how often the Tivoli Enterprise
Monitoring Server checks to see if a situation has become true. The minimum monitor interval is 30 seconds; the
default is 15 minutes.
monitoring. Running a hardware or software tool to monitor the performance characteristics of a system.
Multi-domain Management (MDM). This feature gives you the ability to administer multiple IBM Tivoli
Monitoring domains from a single, central location. This type of management consolidates Tivoli Monitoring
configuration artifacts into a central database where they can be managed independently of the monitoring server.
Your hub monitoring server operations will be generalized across multiple IBM Tivoli Monitoring domains. MDM
has the following capabilities:
v Promotion of existing configuration artifacts from an editor domain into a standard store.
v Export of configuration artifacts from multiple IBM Tivoli Monitoring domains into a single relational database
under a single namespace for management and reporting purposes.
v Import of configuration artifacts into multiple IBM Tivoli Monitoring domains.
v Ease of monitoring agent migration operations, configuration changes, and compliance with configuration
standards.
v Server-side audit of all operations.
N
namespace. A namespace uniquely identifies a set of names so that there is no ambiguity when objects having
different origins but the same names are mingled. For example, within the Extensible Markup Language (XML), an
XML namespace is a collection of element type and attribute names. These element types and attribute names are
uniquely identified by the name of the unique XML namespace that contains them. In an XML document, any
element type or attribute name can thus require a two-part name consisting of the name of its namespace and then
its local (functional) name, separated by a colon (:).
It is possible (and often desirable) to create multiple namespaces; this may be essential in environments where
different sets of information are maintained in a common repository like LDAP.
NAT. See Network Address Translation.
Navigator. The upper-left pane of the Tivoli Enterprise Portal window from which individual workspaces can be
selected and displayed (that is, double-clicked). The Navigator Physical view shows your network enterprise as a
physical hierarchy of systems grouped by platform. You can also create other views to create logical hierarchies
grouped as you specify, such as by department or function.
Network Address Translation. A scheme used by local-area networks (LANs) to establish an internal and external
set of IP addresses. Internal IP addresses are kept private and must be translated to and from the external addresses
for outbound and inbound communications. NAT is often used in firewall configurations.
Network File System. A client/server file system developed by Sun Microsystems that, once mounted (that is, made
accessible), allows a user on an NFS client to view, store, and update files on a remote computer (the NFS server) as
though they were on the user's own computer. The portion of the mounted file system that each user can access and
in what ways is determined by the user's own file-access privileges and restrictions.
278
NFS. See Network File System.
node. (1) In networking, a point capable of sending and receiving data. A node can be a device (such as a printer or
workstation), a system, a storage location on a disk, or a single computer. (2) Any managed system, such as an
AIX-based pSeries® server, that IBM Tivoli Monitoring is monitoring. A node can also be a managed system of
subnodes, all of which are being managed as components of the primary node.
non-agent bundles. These custom bundles let you remotely deploy components that need not connect to a Tivoli
Enterprise Monitoring Server, such as those that support other Tivoli products like Netcool/OMNIbus.
O
object. An instance of a class, which comprises an implementation and an interface. An object reflects its original,
holding data and methods and responds to requests for services.
CORBA defines an object as a combination of state and a set of methods characterized by the behavior of relevant
requests.
ODBC. See Open Database Connectivity.
OMEGAMON Dashboard Edition (DE). The OMEGAMON implementation that includes all the features of the
Tivoli Enterprise Portal provided with OMEGAMON Extended Edition, plus application-integration components
that facilitate an enterprise-wide view of your Series z computing environment. OMEGAMON DE's workspaces
integrate the data from multiple OMEGAMON Monitoring Agents into one network-wide view.
OMEGAMON Extended Edition (XE). The IBM Tivoli Monitoring implementation of a single OMEGAMON
Monitoring Agent. OMEGAMON Extended Edition displays the monitoring data from each OMEGAMON
Monitoring Agent independently, without integrating it into the enterprise-wide workspaces provided by
OMEGAMON Dashboard Edition.
OMEGAMON Monitoring Agent. The software process that probes a managed z/OS system or subsystem (such as
CICS) for data. The monitoring agent sends that monitoring information back to the Tivoli Enterprise Monitoring
Server and then on to the Tivoli Enterprise Portal Server to be formatted into table and chart views for display on a
Tivoli Enterprise Portal client.
OMEGAMON Tivoli Event Adapter (OTEA). The OMEGAMON Tivoli Event Adapter invokes the Event
Integration Facility API to synchronize IBM Tivoli Monitoring events with the IBM Tivoli Enterprise Console
product. OTEA is a component of the Tivoli Enterprise Monitoring Server; it forwards IBM Tivoli Monitoring events
to Tivoli Enterprise Console and maps them to their corresponding Tivoli Enterprise Console event classes based on
the situation name's suffix, either _Warning or _Critical.
Integrating these products requires two parts: a Tivoli Enterprise Monitoring Server piece (included with IBM Tivoli
Monitoring version 6.1 and subsequent releases) called the OMEGAMON Tivoli Event Adapter, and a Tivoli
Enterprise Console piece called the Situation Update Forwarder (SUF) that is installed on the Tivoli Enterprise
Console server.
Open Database Connectivity (ODBC). A standard for accessing different database systems using procedural,
non-object-based languages such as C. The Query editor enables you to write custom SQL queries for creating views
that retrieve data from ODBC-compliant databases.
operator. (1) The action to be performed on one or more attributes when evaluating an expression. The types of
operators the Tivoli Enterprise Portal supports are arithmetic, comparison, Boolean, and logical. (2) The symbol
(such as +, -, or *) that represents that operation (in these examples, addition, subtraction, multiplication).
OTEA. See OMEGAMON Tivoli Event Adapter.
output data. Data resulting from computer processing. See also input data.
Glossary
279
P
parameter. A value or reference passed to a function, command, or program that serves as input or to control
actions. The value is supplied by a user or by another program or process.
PDS. See Persistent Datastore.
PerfMon. See Performance Monitor.
performance. A major factor in measuring system productivity. Performance is determined by a combination of
throughput, response time, and availability.
performance analysis. The use of one or more performance tools to investigate the reasons for performance
improvement or deterioration.
Performance Monitor (PerfMon). The Windows Performance Monitor is an SNMP-based performance-monitoring
tool for Windows environments. PerfMon monitors network elements such as computers, routers, and switches.
Persistent Datastore (PDS). A set of z/OS data sets where the Tivoli Enterprise Monitoring Server running on
z/OS stores historical monitoring data.
platform. The operating system upon which the managed system is running, such as z/OS or Linux. The Tivoli
Enterprise Portal Navigator's Physical mapping places the platform level under the Enterprise level.
policy. A set of automated system processes that can perform actions, schedule work for users, or automate manual
tasks, frequently in response to events. Policies are the IBM Tivoli Monitoring automation tool; they comprise a
series of automated steps, called activities, whose order of execution you control.
In most cases, a policy links a Take Action command to a situation that has turned true. Once begun, the policy's
workflow progresses until all activities have been completed or until the Tivoli Enterprise Portal user manually
stops the policy. You can create both policies that fully automate workflow strategies and those that require user
intervention. As with situations, policies are distributed to the managed systems you want to monitor and to which
you are sending commands.
presentation files. Two files installed with the Tivoli Enterprise Portal Server, presentation.dat and
presentation.idx, that store workspace definitions, link definitions, and terminal emulator scripts.
private situation. A situation that is defined in an XML privateconfiguration file for the local Tivoli Enterprise
Monitoring Agent or Tivoli System Monitor Agent and does not interact with a Tivoli Enterprise Monitoring
Server. Events are viewed through the Agent Service Interface or can be sent as EIF events or SNMP alerts to a
receiver. See also enterprise situation.
product code. The three-letter code used by Tivoli Management Services to identify the product component. For
example, the product code for IBM Tivoli Composite Application Manager for WebSphere Application Server is KWE.
Properties editor. A multi-tabbed window for specifying the properties of the individual views that make up a
workspace, as well as the general workspace properties.
pure event. A pure event is one that occurs automatically, such as when a paper-out condition occurs on the printer
or when a new log entry is written. Situations written to notify you of pure events remain true until they are
manually closed or automatically closed by an UNTIL clause. See also sampled event.
Q
query. A particular view of specified attributes of selected instances of a set of managed-object classes, arranged to
satisfy an end-user request. Queries are written using SQL.
query permissions. The set of Tivoli Enterprise Portal Server authorities that allow your user ID to create or update
queries.
v If you do not see the Queries tool, your user ID does not have View or Modify Query permissions.
v If you can see the tool but it is disabled, your user ID does not have Workspace Author Mode permission.
v If you can open the Query editor but the tools are disabled, your user ID does not have Modify Query permission.
280
R
remotemonitoring server. A remote Tivoli Enterprise Monitoring Server collects monitoring data from a subset of
your site's monitoring agents and passes its collected data to the hub monitoring server to be made available to one
or more Tivoli Enterprise Portal clients via the Tivoli Enterprise Portal Server, thereby creating an enterprise-wide
view.
remote deployment. IBM Tivoli Monitoring processes can deploy agents and other non-agent, Tivoli Management
Services-based components to remote nodes without your having to sign onto those nodes and perform the
installation and configuration steps yourself. Remote deployment requires two pieces on the destination node: (1) a
bundle containing the component code and the instructions for installing/configuring it, and (2) an operating-system
agent to read the bundle and perform the installation and configuration steps.
Remote Procedure Call (RPC). A protocol based on the Open Software Foundation's Distributed Computing
Environment (DCE) that allows one program to request services from a program running on another computer in a
network. RPC uses the client/server model: the requesting program is the client, and the responding program is the
server. As with a local procedure call (also known as a function call or a subroutine call), an RPC is a synchronous
operation: the requesting program is suspended until the remote procedure returns its results.
rolloff. The transfer of monitoring data to the Tivoli Data Warehouse.
RPC. See Remote Procedure Call.
RTE. See runtime environments.
runtime environment (RTE). A group of execution libraries that provide an operational environment on a z/OS
system. RTEs execute OMEGAMON products on a z/OS image.
runtime libraries. A group of z/OS libraries in the runtime environment that the product uses when it is started
and running. Runtime libraries provide an operational environment on a z/OS system.
S
sample. One block of monitoring data that a Tivoli Enterprise Monitoring Agent collects for a Tivoli Enterprise
Monitoring Server. The interval is the time between data samplings.
sampled event. Sampled events happen when a situation becomes true. Situations sample data at regular intervals.
When the situation becomes true, it opens an event, which gets closed automatically when the situation goes back to
false (or when you close it manually). See also pure event.
Secure Sockets Layer. A security protocol for communication privacy that provides secure client/server
conversations.
security-enhanced Linux (SELinux). The National Security Agency's security-enhanced Linux is a set of patches to
the Linux kernel plus utilities that together incorporate a strong, flexible mandatory access control (MAC)
architecture into the kernel's major subsystems.
SELinux enforces the separation of information based on confidentiality and integrity requirements, which allows
attempts to tamper with or bypass application security mechanisms to be recorded and confines the damage caused
by malicious or flawed applications.
seed data. The product-provided situations, templates, policies, and other sample data included with a Tivoli
Enterprise Monitoring Agent to initialize the Tivoli Enterprise Monitoring Server's Enterprise Information Base.
Before you can use a particular monitoring agent, the monitoring server to which it reports must be seeded, that is,
initialized with application data.
self-describing agent. When you invoke a self-describing Tivoli Enterprise Monitoring Agent, the seed data
necessary for the Tivoli Enterprise Monitoring Server to recognize and process data from that agent need no longer
be "seeded" at installation into the agent's local monitoring server and then replicated out to the hub monitoring
server and all other Tivoli Management Services components that require it (such as the Tivoli Enterprise Portal
Server and the Tivoli Data Warehouse). Instead, this application support data can now be automatically replicated
from the agent to its local monitoring server whenever the agent starts up. This means it is also no longer necessary
Glossary
281
that you follow each seeding step by restarting all affected Tivoli Management Services components so they can
recognize and process data generated by these newly installed or upgraded agents.
After you activate the self-describing agents capability, application support is automatically refreshed whenever a
newer version of a self-describing agent is detected. Also, components need not be recycled every time an update is
applied (similarly, its situations, policies, and activities are automatically redistributed and restarted), nor is it
necessary each time a newly updated agent connects to its monitoring server—each update is seeded once and only
once. This means you need not interrupt your enterprise monitoring whenever you add a new self-describing agent
or update an existing agent. This enhancement also means that no self-describing OMEGAMON Monitoring Agents'
application data need be stored on distributed systems.
A self-describing agent can be either a distributed agent running on Windows, UNIX, or Linux, or an OMEGAMON
Monitoring Agent running on z/OS.
server. An application that satisfies data and service requests from clients.
Simple Network Management Protocol (SNMP). A TCP/IP transport-layer protocol for exchanging network
management data and controlling the monitoring of network nodes in a TCP/IP environment. The SNMP software
protocol facilitates communications between different types of networks. IBM Tivoli Monitoring uses SNMP
messaging to discover the devices on your network and their availability.
Simple Object Access Protocol (SOAP). The Simple Object Access Protocol is an XML-based interface that vendors
use to bridge remote procedure calls between competing systems. SOAP makes it unnecessary for sites to choose
between CORBA/Java/EJB and Microsoft's COM+.
Because XML and SOAP are platform- and language-neutral, users can mix operating systems, programming
languages, and object architectures yet maintain business-component interoperability across platforms: using SOAP,
applications can converse with each other and exchange data over the Internet, regardless of the platforms on which
they run.
single sign-on. This feature lets your IBM Tivoli Monitoring users start other Tivoli web-enabled applications from
any Tivoli Enterprise Portal client (desktop, browser, or Java Web start), or to start the portal client from those
applications, without having to re-enter their user credentials (userid and password). For SSO to function, User
Authentication must be configured through the Tivoli Enterprise Portal Server for an external LDAP registry (such
as Microsoft Active Directory) that is shared by all participating Tivoli applications. All the participating applications
must be configured for SSO and must belong to the same security domain and realm.
situation. One or more monitored conditions running on a managed system. The set of conditions that, when met,
creates an event. A situation comprises an attribute, function (such as Value of expression or
Percent change in
value), a relational operator such as greater than or equal to, and a value to be compared. It can be read as “If –
system condition – compared to – value – is true”. An example of a situation is: If – value of CPU usage > 90% –
TRUE. The expression “CPU usage > 90 is the situation condition. See also enterprise situation and private
situation.
Situation Event Forwarder. This component of Tivoli Management Services maps situation events to Event
Integration Facility (EIF) events and uses the EIF interface to send the events to a Tivoli Enterprise Console Event
Server or to an OMNIbus EIF probe(the EIF receivers). The event receivers receive the forwarded events, and expand
and format them for the event servers. On the Tivoli Enterprise Console or OMNIbus console, users can view,
acknowledge, or reset situation events. The updated situation status is returned to the originating hub monitoring
server and reflected in the Tivoli Enterprise Console or OMNIbus console.
Situation Update Forwarder (SUF). The Situation Update Forwarder is a Java- and CORBA-based background
process for communication between IBM Tivoli Enterprise Console and a particular Tivoli Enterprise Monitoring
Server running under IBM Tivoli Monitoring version 6.1 and subsequent releases. Your site must install this
component on the Tivoli Enterprise Console server; for instructions, see the IBM Tivoli Enterprise Console Installation
Guide on the IBM Tivoli Enterprise Console information center.
SNMP. See Simple Network Management Protocol.
SOAP. See Simple Object Access Protocol.
sockets. Refers to the sockets method of passing data back and forth between a networked client and server or
between program layers on the same computer.
282
sound. The WAV file that plays whenever a situation becomes true for the current Navigator item. Sound is
assigned to the Navigator item for a situation in the same way a state is assigned.
SPIPE. A secure pipe is an implementation of the Internet Protocol's pipe specification that uses the Secure Sockets
Layer API. Using SPIPE, your corporate web server can securely access internal servers that are not based on the
HTTPS protocol, while retaining their ability to process HTTP requests.
SQL. See Structured Query Language.
SSL. See Secure Sockets Layer.
SSM. See System Service Monitors.
SSO. See single sign-on.
state. The severity of the situation event: critical, warning, or informational. Indicated by a colored event indicator,
state is set in the Situation editor and can be different for different Navigator items.
status. The true or false condition of a situation.
Structured Query Language. A programming language for extracting information from and updating information
within a relational database. The Query editor enables you to write SQL queries to ODBC-compliant datasources for
retrieval and display in table and chart views.
subnetwork. A configuration wherein a single IP network address is split up so it can be used on several
interconnected local networks. Subnetworking is a local configuration; outside it appears as a single IP network.
SUF. See Situation Update Forwarder.
summarization and pruning agent. One of the IBM Tivoli Monitoring base agents, the summarization and pruning
agent keeps the data warehouse from growing too large by summarizing and pruning your stored historical data at
intervals that you set. For every attribute group that has data collection configured, you specify how often to
aggregate (summarize) data in the Tivoli Data Warehouse and the length of time to pass before deleting (pruning)
data from the warehouse.
symbol. A variable that can be added to header or footer text for data views, expert-advice text, or query
specifications. The detailed attribute name is enclosed in dollar signs, such as $ORIGINNODE$, and resolves to the
attribute's value. For queries, == $NODE$ specifies the managed systems from which to retrieve data. For queries to be
used in link target workspaces, you can create symbols for attributes using the $symbolname$ format.
System Monitor Agent. These agents were introduced with IBM Tivoli Monitoring version 6.2.2 for nodes that run
the desktop operating systems (Windows, Linux, UNIX). System Monitor Agents operate only autonomously (that is,
they run without a connection to a Tivoli Enterprise Monitoring Server) and pass SNMP trap data about operating
system performance to an SNMP Event Collector such as IBM Tivoli Netcool/OMNIbus.
No other agents or other components should be installed on the same node as a System Monitor Agent. The only
exception to this rule is agents created with the Agent Builder tool (V6.2.2 or later).
System Service Monitors. The IBM Tivoli Netcool/OMNIbus product provides System Service Monitors that
support basic system-level monitoring of network components such as operating systems. In addition, OMNIbus
provides ISMs (Internet Service Monitors) and ASMs (Application Service Monitors).
IBM System Z. Umbrella family name used when referring to multiple product lines or the IBM mainframe class of
products in general.
T
Take Action. A Tivoli Enterprise Portal dialog from which you can enter a command to perform or choose from a
list of predefined commands. It also lists systems on which to effect the command, which is usually a response to an
event.
Take Action command. A Take Action command allows you to send commands to your managed systems, either
automatically, in response to a situation that has fired (that is, turned true), or manually, as the Tivoli Enterprise
Portal operator requires. With Take Action commands, you can enter a command to execute or select one of the
Glossary
283
commands predefined by your product and run it on any system in your managed network. Thus you can issue Take
Action commands either against the managed system where the situation fired or a different managed system in your
network.
target libraries. SMP/E-controlled libraries that contain the data installed from the product-distribution media.
task. A unit of work representing one of the steps in a process.
TCP/IP. See Transmission Control Protocol/Internet Protocol.
TDW. See Tivoli Data Warehouse.
telnet. A terminal-emulation program used on TCP/IP networks. You can start a telnet session with another system
and enter commands that execute on that system. A valid user ID and password for that remote system are required.
TEPS/e. See Tivoli Enterprise Portal Server extended services.
threshold. (1) A level set in the system at which a message is sent or an error-handling program is called. For
example, in a user auxiliary storage pool, the user can set the threshold level in the system values, and the system
notifies the system operator when that level is reached or exceeded. (2) A customizable value for defining the
acceptable tolerance limits (maximum, minimum, or reference limit) for an application resource or system resource.
When the measured value of the resource is greater than the maximum value, less than the minimum value, or equal
to the reference value, an exception is raised.
time-scheduling services. The Tivoli Common Reporting module uses the time-scheduling services to query and
manage report schedules and tasks.
timestamp. A data type that contains a seven-part value consisting of a date and a time expressed in years, months,
days, hours, minutes, seconds, and microseconds.
Tivoli Common Reporting. This reporting module allows a single point of access to reports generated by multiple
products. It interacts with either the Business Intelligence and Reporting Tools (BIRT) Designer or with the Cognos®
product for customizing reports and running defined reports. The time-scheduling service allows you to schedule
report extraction and creation.
Tivoli Data Warehouse (TDW). This member of the IBM Tivoli Monitoring product family stores Tivoli Monitoring
agents' monitoring data in separate relational database tables so you can analyze historical trends using that
enterprise-wide data. Reports generated from Tivoli Data Warehouse data provide information about the availability
and performance of your monitoring environment over different periods of time.
Tivoli Enterprise Monitoring Server. The host data-management component for IBM Tivoli Monitoring. It receives
and stores monitoring data from either the agents or other monitoring servers and delivers it to the Tivoli
Enterprise Portal Server, raises alerts when conditions specified in situations are met, receives Take Action
commands from the Tivoli Enterprise Portal and passes them to the appropriate monitoring agents for execution,
and (optionally) provides a repository for short-term historical data. The Tivoli Enterprise Monitoring Server can be
installed on z/OS, Windows, Linux, and UNIX operating systems.
Tivoli Enterprise Portal. The client component of a Tivoli Enterprise Portal Server. The Tivoli Enterprise Portal
provides the graphical user interface into monitoring data collected by the Tivoli Enterprise Monitoring Server and
prepared for user display by the portal server. The Tivoli Enterprise Portal comes in two versions: the desktop client
and the browser client.
Tivoli Enterprise Portal Server. The server you log onto that connects you to IBM Tivoli Monitoring via the Tivoli
Enterprise Portal client. The Tivoli Enterprise Portal Server connects to the hub Tivoli Enterprise Monitoring
Server and enables retrieval, manipulation, and analysis of data from your enterprise's monitoring servers.
Tivoli Enterprise Portal Server extended services. An embedded, colocated extension of the Tivoli Enterprise Portal
Server that provides J2EE-based Application Server integration facilities. TEPS/e supports a federated user repository
built on the Lightweight Directory Access Protocol (LDAP).
Tivoli Enterprise Services user interface extensions. A component provided as part of Tivoli Management Services
running on distributed systems that provides access to the command line interface for other Tivoli Management
Services components. This component includes the tacmd command, which is used for, among other things,
administering the self-describing agents feature. The GUI installer on distributed operating systems automatically
284
installs this component when you install the Tivoli Enterprise Portal desktop client, the Tivoli Enterprise Portal
Server, or the Tivoli Enterprise Monitoring Server. Additionally, it is an optional installable component of the Tivoli
Enterprise Monitoring Agent component. The component code is KUE.
The Tivoli Enterprise Services user interface extensions are not available on z/OS.
Tivoli Enterprise Web Services. An open standards-based interface to the Tivoli Enterprise Monitoring Server that
uses SOAP requests. Using SOAP, any monitoring agent can be dynamically queried, which means that its
performance and availability data can be processed by external applications not a part of IBM Tivoli Monitoring.
Tivoli Integrated Portal. The Tivoli Integrated Portal provides a single, task-based navigation panel for Web-based
Tivoli products; it offers a common user interface with which you can launch applications, launch from one
application to another, and share information between applications. It provides a rich, Web-based user interface with
which you can access results generated by such applications as Tivoli Application Dependency Discovery Manager
(TADDM), Tivoli Business Service Manager (TBSM), and Netcool/OMNIbus. The Tivoli Integrated Portal enables the
secure passing of data between Tivoli products via this common portal. With it, you can manage different aspects of
your enterprise from a single dashboard view.
Tivoli Management Services. An integrated, layered architecture consisting of data-access, communication, and
presentation components that enable cross-platform operation and integration of enterprise-wide data for
systems-management applications. The software foundation that supports the development and operations of the
Tivoli Enterprise Monitoring Server, the Tivoli Enterprise Portal Server and Tivoli Enterprise Portal, and their
monitoring agents.
Tivoli OMEGAMON Manager (TOM). The enhanced 3270 user interface’s address space. In any IBM Tivoli
Monitoring environment where one or more OMEGAMON Monitoring Agents will exploit the enhanced 3270 user
interface, a TOM must be configured in such a way that it shares a sysplex with at minimum one monitoring server
or agent address space that is connected to that Tivoli Monitoring network’s hub monitoring server. From this one
Tivoli Monitoring environment, a single TOM address space can manage multiple Tivoli Monitoring environments
that contain other instances of the OMEGAMON Monitoring Agents.
Each z/OS-based Tivoli Enterprise Monitoring Server or Tivoli Enterprise Monitoring Agent address space has a
process running in it called KOBAGENT, which is the enhanced 3270 user interface’s data-retrieval agent (DRA).
KOBAGENT uses Tivoli Management Services on z/OS to send your data requests to its hub monitoring server.
When the address space running the TOM starts, it discovers each KOBAGENT process in the same sysplex; thus the
TOM has access to multiple hub environments, since there may be multiple KOBAGENTs running in the sysplex that
connect to different hub monitoring servers (and therefore different Tivoli Monitoring environments). The TOM
requires only one KOBAGENT per hub, but if there are more, the TOM can determine over time which KOBAGENT
has the best data throughput; it can also try alternate KOBAGENT instances if a request fails using the first
KOBAGENT it selects.
When users log on to a session in the TOM, they pick the Tivoli Monitoring environment they wish to work with
and then start exploiting the various OMEGAMON agents running in that environment. Which agent data users can
look at is determined by the hub Tivoli Enterprise Monitoring Server running in that environment.
TOM. See Tivoli OMEGAMON Manager.
Transmission Control Protocol/Internet Protocol (TCP/IP). An open, portable communications protocol that is the
software basis for the Internet.
TSO. Time Sharing Option, the interactive interface into the z/OS operating system.
U
UDP. See User Datagram Protocol.
User Datagram Protocol. A TCP/IP communications protocol that exchanges messages ("datagrams") between
networked computers linked by the Internet Protocol (IP). UDP is an alternative to the Transmission Control Protocol
(TCP), which, like UDP, uses IP to move a message from one computer to another. Unlike TCP, however, UDP does
not divide the message into packets and reassemble them at the other end.
The Network File System uses UDP to move file contents and file updates between the NFS server and the NFS
client.
Glossary
285
V
value of expression. A function in a situation condition, query specification, or data view filter or threshold that
uses the raw value of an attribute. A value can be a number, text string, attribute, or modified attribute. Use this
function with any operator.
view. A window pane, or frame, in a Tivoli Enterprise Portal workspace. It displays agent data in a chart or table,
or it may contain a terminal session or browser, for example. A view can be split into two separate, autonomous
views.
W
warehouse proxy agent. One of the IBM Tivoli Monitoring base agents, the warehouse proxy agent passes data
from either a monitoring agent or the Tivoli Enterprise Monitoring Server to the Tivoli Data Warehouse. This
multi-threaded server process can handle concurrent requests from multiple monitoring agents to roll off data from
their short-term history files to the data warehouse.
WAV file. Waveform audio format for storing sound in files, developed jointly by Microsoft and IBM.
wildcard. An * (asterisk) used to represent any characters that may follow or precede those entered, such as Sys* to
locate System and SysTray. Used in formulas with the VALUE function or MISSING function (in the Missing Task
List). Used also with the SCAN function, but at the beginning of the text as in *Z to find markZ and typeZ.
Windows Management Instrumentation (WMI) API. Microsoft's Windows Management Instrumentation API
provides a toolkit for managing devices and applications in a network of Windows-based computers. WMI provides
both the data about the status of local or remote computer systems and the tools for controlling the data. WMI is
included with the Windows XP and Windows Server 2003 operating systems.
WMI. See Windows Management Instrumentation.
workload. A percentage that shows how much of a computer's resources a managed system is using. Workload is
calculated using a weighted combination of resource-use statistics.
workspace. The viewing area of the Tivoli Enterprise Portal window, excluding the Navigator. Each workspace
comprises one or more views. Every Navigator item has associated with it its own default workspace and perhaps
multiple workspaces.
workspace administration mode. A global parameter set in the Administer Users editor but which is available only
for user IDs with administrator authority. When enabled for a user ID, customization of workspaces, links, and
terminal-session scripts automatically becomes available to all users connected to the same Tivoli Enterprise Portal
Server.
X
XML. See Extensible Markup Language.
Z
z/OS. IBM's operating system for its line of mainframe, Series z computers that can manage large amounts of
memory, direct-access storage, and data.
286
Index
A
about this information vii
ACF2 macro library field 81
Address translation field 196
administration mode
See workspace administration mode
advanced agent configuration values
monitoring agent
KPP_AGT_ICU_LANGUAGE_LOCALE 14
KPP_AGT_WTO_MSG 41
Advanced Encryption Standard 271
AES
See Advanced Encryption Standard
Agent PPI sender field 25
Agent started task field 26
Agent to TEMS connection field 38
alert monitor 271
Alias name field 181
Allocation MGMTCLAS field 122
Allocation STORCLAS field 123
Allocation unit field 124
Allocation volume field 124
API
See Application Programming Interface
Application Programming Interface 271
application server 272
Application Service Monitors, Netcool/OMNIbus 283
Applid prefix field 39, 138, 148, 237
B
Backup field 118
Backup TEMS name field 49
baroc files 272
Basic Recorder of Objects in C files 272
batch mode 2
batch parameters
KPP_AGT_AUDIT_ITM_DOMAIN 7
KPP_AGT_AUDIT_MAX_HIST 8
KPP_AGT_AUDIT_TRACE 9
KPP_AGT_COMM_PROn 11
KPP_AGT_CONFIG 10
KPP_AGT_FLUSH_INT_HR 13
KPP_AGT_FLUSH_INT_MIN 14
KPP_AGT_ICU_LANG 14
KPP_AGT_KGL_WTO 16
KPP_AGT_KLX_TCP_RECYCLE 17
KPP_AGT_NONSTDn_DSN 19
KPP_AGT_NONSTDn_PARM 21
KPP_AGT_NSOLDn_VALUE 22
KPP_AGT_PIPE_NAME 23
KPP_AGT_PPI_RECEIVER 24
KPP_AGT_PPI_SENDER 25
KPP_AGT_STC 26
KPP_AGT_STOR_DTL_INT_HR 27
KPP_AGT_STOR_DTL_INT_MIN 28
KPP_AGT_STOR_MIN_EXT 29
KPP_AGT_TCP_HOST 30
KPP_AGT_TCP_STC 32
KPP_AGT_TEMA_SDA 33
batch parameters (continued)
KPP_AGT_TEMS_NAME_NODEID 34
KPP_AGT_VIPA 35
KPP_AGT_VTM_APPL_AA 36
KPP_AGT_VTM_APPL_NCS 38
KPP_AGT_VTM_APPL_OPR 39
KPP_AGT_VTM_APPL_PREF 39
KPP_AGT_VTM_APPL_VPO 37
KPP_AGT_VTM_NODE 40
KPP_AGT_WTO_MSG 41
KPP_CMS_HUB_TCP_HOST 54
KPP_CMS_LOCAL_CONNECT 54
KPP_CMS_NAME 56
KPP_CMS_TCP_HOST 57
KPP_CMS_TCP_PIPE_PORT 58
KPP_CMS_TCP_PIPE6_PORT 60
KPP_CMS_TCP_PIPE6S_PORT 61
KPP_CMS_TCP_PIPES_PORT 59
KPP_CMS_TCP_UDP_PORT 62
KPP_CMS_TCP_UDP6_PORT 63
KPP_CMS_VTM_APPL_LLB 63
KPP_CMS_VTM_LU62_LOG 64
KPP_CMS_VTM_LU62_LOGTAB 65
KPP_CMS_VTM_NETID 66
KPP_CMSB_NAME 49
KPP_CMSB_TCP_HOST 50
KPP_CMSB_VTM_APPL_LLB 51
KPP_CMSB_VTM_LU62_LOG 52
KPP_CMSB_VTM_NETID 53
KPP_ICS_DATASET 95
Kpp_MQS_AUTHLIB 102
Kpp_MQS_LANGLIB 102
KPP_NONSTDnn_MBR 20
KPP_NSNEWn_VALUE 18
KPP_PD 42
KPP_PD_CYL 43
KPP_PD_GRP 44
KPP_PD_ROW 47
Kpp_TCP_DATA 101
Kpp_USS_EXEC 97
KD2_OMPE_DB2EXIT 87
KD2_OMPE_DB2LOADLIB_Vn 88
KD2_OMPE_DB2RUNLIB_Vn 89
KDF_HSM_LOG_DSN 94
KDO_DB2_LOADLIB 89
KDS_AUDIT_ITM_DOMAIN 157
KDS_AUDIT_MAX_HIST 157
KDS_AUDIT_TRACE 158
KDS_CMS_COMM_PROn 197
KDS_CMS_COMM_XLAT 196
KDS_CMS_CTSOAP 215
KDS_CMS_EIF 202
KDS_CMS_EIF_BFR_EVT 248
KDS_CMS_EIF_BFR_EVT_MAX 199
KDS_CMS_EIF_BFR_EVT_PATH 248
KDS_CMS_EIF_DISABLE_EMT 200
KDS_CMS_EIF_EVT_LISTENER 201
KDS_CMS_EIF_FLT_ATTR1 249
KDS_CMS_EIF_FLT_CLASS1 249
KDS_CMS_EIF_FLT_MODE 250
KDS_CMS_EIF_HOST 203
287
KDS_CMS_EIF_PORT 204
KDS_CMS_EXT_LIM 219
KDS_CMS_FLUSH_INT_HR 204
KDS_CMS_FLUSH_INT_MIN 205
KDS_CMS_HA_EXCL_LIST 206
KDS_CMS_HA_TYP 206, 258
KDS_CMS_HTTP_PORT 207
KDS_CMS_ICU_LANG 208
KDS_CMS_KDC_DEBUG 210
KDS_CMS_KGL_WTO 211
KDS_CMS_KLX_TCP_RECYCLE 212
KDS_CMS_PART_NAME 213
KDS_CMS_SEC_ENC_KEY 214
KDS_CMS_SEC_VALIDATE 214
KDS_CMS_STC 216
KDS_CMS_STOR_DTL_INT_HR 216
KDS_CMS_STOR_DTL_INT_MIN 217
KDS_CMS_STOR_DTL_LOG 218
KDS_CMS_STOR_MIN_EXT 221
KDS_CMS_TCP_HOST 222
KDS_CMS_TCP_KDEBLST 223
KDS_CMS_TCP_PIPE_PORT 224
KDS_CMS_TCP_PIPE6_PORT 225
KDS_CMS_TCP_PIPE6S_PORT 226
KDS_CMS_TCP_PIPES_PORT 227
KDS_CMS_TCP_STC 228
KDS_CMS_TCP_UDP_PORT 229
KDS_CMS_TCP_UDP6_PORT 230
KDS_CMS_TYP 232
KDS_CMS_VIPA 233
KDS_CMS_VTM_APPL_CUA 233
KDS_CMS_VTM_APPL_DS 234
KDS_CMS_VTM_APPL_GLB 234
KDS_CMS_VTM_APPL_LLB 236
KDS_CMS_VTM_APPL_OPR 237
KDS_CMS_VTM_APPL_PREF 237
KDS_CMS_VTM_APPL_VPO 235
KDS_CMS_VTM_LOADLIB 98
KDS_CMS_VTM_LU62_LOG 238
KDS_CMS_VTM_LU62_LOGTAB 238
KDS_CMS_VTM_MACLIB 98
KDS_CMS_VTM_NETID 239
KDS_CMS_VTM_NODE 240
KDS_HFS_JAVA_DIRn 103
KDS_HUB_GLB_APPL 166
KDS_HUB_HA_TYP 165
KDS_HUB_TCP_HOST 159
KDS_HUB_TCP_PIPE_PORT 159
KDS_HUB_TCP_PIPE6_PORT 160
KDS_HUB_TCP_PIPE6S_PORT 161
KDS_HUB_TCP_PIPES_PORT 162
KDS_HUB_TCP_UDP_PORT 163
KDS_HUB_TCP_UDP6_PORT 164
KDS_HUB_VTM_NETID 166
KDS_KMS_SDA 167
KDS_MIG_TAPE_HILEV 168
KDS_MIG_TAPE_UNIT 168
KDS_MIG_TAPE_VOL 169
KDS_MIG_VER 170
KDS_MIG_VSAM_HILEV 170
KDS_NONSTDnn_DSN 171
KDS_NONSTDnn_MBR 172
KDS_NONSTDnn_PARM 173
KDS_NSNEWnn_VALUE 174
KDS_NSOLDnn_VALUE 175
KDS_PA 175
288
KDS_PA_ADDR 176
KDS_PA_NAME 177
KDS_PA_ROW 177
KDS_PD 178
KDS_PD_CYL 178
KDS_PD_GRP 179
KDS_PD_ROW 180
KDS_PH 180
KDS_PH_CMS_ALIAS_NAME 181
KDS_PH_CMS_COMM_PRO1 182
KDS_PH_CMS_KSH_SECURE 183
KDS_PH_CMS_NAME 183
KDS_PH_CMS_RTE 184
KDS_PH_CMS_SYSV 184
KDS_PH_CMS_TCP_HOST 185
KDS_PH_CMS_TCP_HOST_LEN 186
KDS_PH_CMS_TCP_PORT 186
KDS_PH_CMS_USER_QUERY 187
KDS_PH_CMS_USER_UPDATE 187
KDS_PH_CMS_VTM_APPL_GLB 188
KDS_PH_CMS_VTM_LU62_LOG 189
KDS_PH_CMS_VTM_NETID 189
KDS_PH_ROW 181
KDS_PPI_RECEIVER 190
KDS_PPI_SENDER 191
KDS_PU 192
KDS_PU_CMS_NAME 193
KDS_PU_CMS_RTE 193
KDS_PU_CMS_USER_ID 194
KDS_PU_CMS_USER_QUERY 194
KDS_PU_CMS_USER_UPDATE 195
KDS_PU_ROW 192
KDS_TEMA_SDA 196
KDS_TEMS_DRA_FLAG 198
KDS_USS_EXEC 97
KGW_CTG_DLL_DSN 86
KI2_CLA_BMP_RESLIB 90
KI2_I1_CLA_IMS_RESLIB 90
KI5_ICT_SCEXLINK 91
KI5_ICT_SFUNLINK 92
KI5_IMS_RESLIB 90
KI5_X_ICT_IMS_CONNECT_FLAG 91, 92
KMC_CFG_MCDB2_LIB 89
KNA_NETV_LNKLIB 93
KOB_TOM_STC 259
KOB_TOM_VTAM_APPL_LOGON 260
KOB_TOM_VTAM_NODE 261
KPP_AGT_TCP_KDEBLST 31
KQI_CEE_LE370_LKED 83
KQI_CEE_LE370_RUN 85
KQI_CIC_LOADLIB 87
KQI_MQS_LOADLIB 103
PARMGEN parameter names
KDS_HUB_TCP_PIPES_PORT_NUM 162
RTE_SYSV_SYSVAR_FLAG 136
RTE_ACF2_MACLIB 81
RTE_BASE_MIDLEV 107
RTE_CAN_SS_IEFSSN_FMT 112
RTE_CAN_SS_STC 107
RTE_CAN_SS_WTO 113
RTE_CAN_SSID 113
RTE_CMS 141
RTE_CMS_NAME 142
RTE_CUA_SECURITY 127
RTE_DEBUG_SYSOUT 109
221
RTE_DESC 109
RTE_ETE_STC 108
RTE_FOLD_PWD 125, 126
RTE_HCK_INTERVAL 110
RTE_HCK_LOADLIB 90
RTE_HILEV 110
RTE_JCL_SUFF 111
RTE_KCNSTR00_XCFGROUP 114
RTE_LOAD_OPTIMIZE 115
RTE_LOAD_SHARED_LIBS 116
RTE_LOG_SYSOUT 116
RTE_NAME 117
RTE_PDS_BU 118
RTE_PDS_CNT 121
RTE_PDS_EXP 119
RTE_PDS_EXT 120
RTE_PDS_HILEV 121
RTE_PDS_PROC_PREF 122
RTE_PDS_SMS_MGMT_CLAS 122
RTE_PDS_SMS_STOR_CLAS 123
RTE_PDS_UNIT 124
RTE_PDS_VOL 124
RTE_PDSE 129
RTE_REMOTE 125
RTE_SHARE 128
RTE_SMS_MGMT_CLAS 129
RTE_SMS_STOR_CLAS 130
RTE_SMS_VSAM_MGMT_CLAS 132
RTE_SMS_VSAM_STOR_CLAS 133
RTE_STC_PREF 134
RTE_SYS_PROCLIB 96
RTE_SYS_VTAMLST 99
RTE_SYSV 136
RTE_SYSV_BASE_ALIAS 135
RTE_SYSV_CMS_NAME 137
RTE_SYSV_NAME 135
RTE_SYSV_VTM_APPL_MODEL 137
RTE_SYSV_VTM_APPL_PREF 138
RTE_SYSV_VTM_NETID 139
RTE_TCP_HOST 139
RTE_TCP_PORT 140
RTE_TCP_STC 141
RTE_TN3270_LUGROUP 144
RTE_TN3270_TCP_HOST 143
RTE_TN3270_TCP_PORT 144
RTE_TYP 145
RTE_UNIT 131
RTE_USERMODS 146
RTE_USS_RTEDIR 146
RTE_VOL 131
RTE_VSAM_HILEV 148
RTE_VSAM_VOL 133
RTE_VTM_APPL_PREF 148
RTE_VTM_CANDLE_NODE 149
RTE_VTM_LU62_LOG 150
RTE_VTM_LU62_LOGTAB 150
RTE_VTM_NETID 151
SYS1_MACLIB 94
TCP_DATA 101
browser client 272
BufEvtMaxSize parameter 199
BufEvtPath parameter 248
Buffer events maximum size field 199
BufferEvents parameter 248
C
CIM
See Common Information Model
client/server architecture 272
CMS_NODEID parameter 142
CNMLINK load library 93
codepages, language locale 208
common agent parameters 7
Common Information Model 272
Common Object Request Broker Architecture 273
configuration flags 4
Configuration Tool
defined 2
modes 2
Configuration Tool, z/OS 273
configured parameters
storage 1
CONFIRM parameter 246
Connect to TEMS in this RTE field 54
CORBA
See Common Object Request Broker Architecture
Count field 121
D
Data Encryption Standard 273
database server 272
Datastore group name field 44
Datastore high-level prefix field 121
ddname KBDXTRA 276
DEBUG parameter 247, 256
default values 2
DES
See Data Encryption Standard
Description field 109
desktop client 274
Diagnostic SYSOUT class field 109
Disable Workflow Policy/Emitter Agent event forwarding
field 200
DLL
See Dynamic Link Library
DMZ
See Demilitarized Zone
DS_TEMS_VTAM_APPL_LLB_BROKER parameter 236
DSN
See datasource name
DSNAME field 90
DVIPA
See Dynamic Virtual IP Addressing
Dynamic Link Library 274
Dynamic Virtual IP Addressing 274
E
EIB
See Enterprise Information Base
EIF
See Event Integration Facility
Enable communications trace field 210
Enable startup console messages field 16, 211
Enable storage detail logging field 218
Enable Tivoli Event Integration Facility (EIF) field
Enable Web Services SOAP Server field 215
Enable WTO messages field 41
Enable/Disable z/OS audit collection field 158
encryption, password 87
202
Index
289
enhanced 3270 user interface 259
SAF security class name for 125
started task name for 259
Tivoli OMEGAMON Manager 259, 260, 261
VTAM logon APPLID for 260
VTAM node entry for 261
Enterprise Information Base 275
environment variables, defined 1
Est Cyl Space field 43, 178
event 275
Event Integration Facility 275
Event server location field 203
Event server port field 204
Event server type field 201
EventListenerType parameter 201
Export field 119
Extensible Markup Language 275
Extract field 120
F
Federal Information Processing Standard 197
FilterMode parameter 250
FIPS 197 271
Flush VSAM buffers: Hours field 13, 204
Flush VSAM buffers: Minutes field 14, 205
Fold password to upper case field 126
FRAME parameter 244, 250
271
G
GBL_DSN_ACF2_MACLIB parameter 81
GBL_DSN_CBC_SCCNOBJ parameter 81
GBL_DSN_CBC_SCLBSID parameter 82
GBL_DSN_CEE_SCEEBIND parameter 82
GBL_DSN_CEE_SCEEBND2 parameter 82
GBL_DSN_CEE_SCEECPP parameter 83
GBL_DSN_CEE_SCEELIB parameter 83
GBL_DSN_CEE_SCEELKED parameter 83
GBL_DSN_CEE_SCEELKEX parameter 84
GBL_DSN_CEE_SCEEMSGP parameter 84
GBL_DSN_CEE_SCEERUN parameter 85
GBL_DSN_CEE_SCEESPC parameter 85
GBL_DSN_CICS_CTG_DLL parameter 86
GBL_DSN_CICS_SCTGSID parameter 86
GBL_DSN_CICS_SDFHC370 parameter 86
GBL_DSN_CICS_SDFHLOAD parameter 87
GBL_DSN_CSF_SCSFMOD0 parameter 87
GBL_DSN_DB2_DSNEXIT parameter 87
GBL_DSN_DB2_LOADLIB_Vn parameter 88
GBL_DSN_DB2_RUNLIB_Vn parameter 89
GBL_DSN_DB2_SDSNLOAD parameter 89
GBL_DSN_HZSPROC_LOADLIB parameter 90
GBL_DSN_IMS_RESLIB parameter 90
GBL_DSN_IMS_SCEXLINK parameter 91
GBL_DSN_IMS_SFUNLINK parameter 92
GBL_DSN_ISP_SISPLOAD parameter 92
GBL_DSN_NETVIEW_CNMLINK parameter 93
GBL_DSN_SYS1_BRODCAST parameter 93
GBL_DSN_SYS1_CSSLIB parameter 93
GBL_DSN_SYS1_HSMLOGY parameter 94
GBL_DSN_SYS1_LINKLIB parameter 94
GBL_DSN_SYS1_MACLIB parameter 94
GBL_DSN_SYS1_MODGEN parameter 95
GBL_DSN_SYS1_PARMLIB parameter 95
GBL_DSN_SYS1_PROCLIB parameter 96
290
GBL_DSN_SYS1_SAXREXEC parameter 96
GBL_DSN_SYS1_SBLSCLI0 parameter 96
GBL_DSN_SYS1_SBPXEXEC parameter 97
GBL_DSN_SYS1_SISTMAC1 parameter 98
GBL_DSN_SYS1_VTAMLIB parameter 98
GBL_DSN_SYS1_VTAMLST parameter 99
GBL_DSN_TCP_ETC_SERVICES parameter 99
GBL_DSN_TCP_SEZACMTX parameter 100
GBL_DSN_TCP_SEZARNT1 parameter 100
GBL_DSN_TCP_SEZATCP parameter 100
GBL_DSN_TCP_SYSTCPD_TCPDATA parameter 101
GBL_DSN_TCP_SYSTCPD_TCPDATA_MFN parameter
GBL_DSN_WMQ_SCSQANLE parameter 102
GBL_DSN_WMQ_SCSQAUTH parameter 102
GBL_DSN_WMQ_SCSQLOAD parameter 103
GBL_HFS_JAVA_DIRn parameter 103
GBL_INST_HILEV parameter 104
GBL_TARGET_HILEV parameter 104
GBL_USER_JCL parameter 105
georeferenced map 275
Global location broker applid of Hub field 166
Global location broker field 234
global parameters 81
GBL_DSN_ACF2_MACLIB 81
GBL_DSN_CSF_SCSFMOD0 87
GBL_DSN_HZSPROC_LOADLIB 90
GBL_DSN_ISP_SISPLOAD 92
GBL_DSN_NETVIEW_CNMLINK 93
GBL_DSN_SYS1_MACLIB 94
GBL_DSN_SYS1_PARMLIB 95
GBL_DSN_SYS1_PROCLIB 96
GBL_DSN_SYS1_SAXREXEC 96
GBL_DSN_SYS1_SBLSCLI0 96
GBL_DSN_SYS1_SISTMAC1 98
GBL_DSN_SYS1_VTAMLIB 98
GBL_DSN_SYS1_VTAMLST 99
GBL_DSN_TCP_SYSTCPD_TCPDATA 101
GBL_INST_HILEV 104
GBL_TARGET_HILEV 104
GBL_USER_JCL 105
Global Security Toolkit 275
Grant query access? field 194
Grant update access? field 195
Group Name field 179
GSKit 275
101
H
Health Checker
load library 90
system library 96
Hierarchical File System/zSeries File System (HFS/zFS) 146
high availability hub monitoring server parameters 258
High-level Qualifier field 110, 148
high-level qualifiers
installation libraries 104
target libraries 104
Hostname field 139, 143
hot-standby monitoring server 276
how parameter values are set 1
HTTP
See Hypertext Transport Protocol
HTTP server port number field 207
HTTPS 275
See Secure Hypertext Transport Protocol
Hub TEMS type field 165, 206, 258
Hypertext Transport Protocol 276
HZSPROC started task
90
I
IBM Support Assistant 267
ICAT
See Configuration Tool, z/OS
ICSF
See Integrated Cryptographic Service Facility
ICSF load library 87
IIOP
See Internet Inter-ORB Protocol
individual agent parameters
KPP_SECURITY_ACTION_CLASS 48
integral web server 276
Integrated Cryptographic Service Facility 275
interactive mode 2
Internet Inter-ORB Protocol 276
Internet Service Monitors, Netcool/OMNIbus 283
Interoperable Object Reference 276
Interval field 110
IOR
See Interoperable Object Reference
IP domain name resolution 101
IP.PIPE field 11, 197
IP.PIPE port number field 159
IP.SPIPE field 11, 197
IP.SPIPE port number field 162
IP.UDP field 11, 197
IP.UDP port number field 163
IP6.PIPE field 11, 197
IP6.PIPE port number field 160
IP6.SPIPE field 11, 197
IP6.SPIPE port number field 161
IP6.UDP field 11, 197
IP6.UDP port number field 164
IPCS system library 96
ISA 267
J
Java Database Connectivity 277
Java Management Extensions API 277
JCL library 105
JCL suffix field 111
JDBC
See Java Database Connectivity
JMX
See Java Management Extensions API
K
KPP parameters 7
KPP_AGT_AUDIT_ITM_DOMAIN batch parameter 7
KPP_AGT_AUDIT_ITM_DOMAIN parameter 7
KPP_AGT_AUDIT_MAX_HIST batch parameter 8
KPP_AGT_AUDIT_MAX_HIST parameter 8
KPP_AGT_AUDIT_TRACE batch parameter 9
KPP_AGT_AUDIT_TRACE parameter 9
KPP_AGT_COMM_PROn batch parameter 11
KPP_AGT_COMM_PROTOCOLn parameter 11
KPP_AGT_CONFIG batch parameter 10
KPP_AGT_CONFIGURATION_MODE parameter 10, 80
KPP_AGT_FLUSH_INT_MIN batch parameter 14
KPP_AGT_FLUSH_LSR_BUFR_INT_HR parameter 13
KPP_AGT_FLUSH_LSR_BUFR_INT_MIN parameter 14
KPP_AGT_ICU_LANG batch parameter 14
KPP_AGT_ICU_LANGUAGE_LOCALE parameter 14
KPP_AGT_KGL_WTO batch parameter 16
KPP_AGT_KGL_WTO parameter 16
KPP_AGT_KLX_TCP_RECYCLE batch parameter 17
KPP_AGT_KLX_TCP_TOLERATERECYCLE parameter 17
KPP_AGT_NONSTDn_DSN batch parameter 19
KPP_AGT_NONSTDn_DSN parameter 19
KPP_AGT_NONSTDn_MBR parameter 20
KPP_AGT_NONSTDn_PARM batch parameter 21
KPP_AGT_NONSTDn_PARM parameter 21
KPP_AGT_NSNEWn_VALUE parameter 18
KPP_AGT_NSOLDn_VALUE parameter 22
KPP_AGT_NSOLDn_VALUE batch parameter 22
KPP_AGT_PARTITION_NAME parameter 23
KPP_AGT_PIPE_NAME batch parameter 23
KPP_AGT_PPI_RECEIVER batch parameter 24
KPP_AGT_PPI_RECEIVER parameter 24
KPP_AGT_PPI_SENDER batch parameter 25
KPP_AGT_PPI_SENDER parameter 25
KPP_AGT_STC batch parameter 26
KPP_AGT_STC parameter
monitoring agent 26
KPP_AGT_STOR_DTL_INT_HR batch parameter 27
KPP_AGT_STOR_DTL_INT_MIN batch parameter 28
KPP_AGT_STOR_MIN_EXT batch parameter 29
KPP_AGT_STORAGE_DETAIL_INT_HR parameter 27
KPP_AGT_STORAGE_DETAIL_INT_MIN parameter 28
KPP_AGT_STORAGE_MINIMUM_EXTEND parameter 29
KPP_AGT_TCP_HOST batch parameter 30
KPP_AGT_TCP_HOST parameter 30
KPP_AGT_TCP_KDEB_INTERFACELIST parameter 31
KPP_AGT_TCP_KDEBLST batch parameter 31
KPP_AGT_TCP_STC batch parameter 32
KPP_AGT_TCP_STC parameter 32
KPP_AGT_TEMA_SDA batch parameter 33
KPP_AGT_TEMA_SDA parameter 33
KPP_AGT_TEMS_NAME_NODEID batch parameter 34
KPP_AGT_TEMS_NAME_NODEID parameter 34
KPP_AGT_VIPA batch parameter 35
KPP_AGT_VIRTUAL_IP_ADDRESS parameter 35
KPP_AGT_VTAM_APPL_AA parameter 36
KPP_AGT_VTAM_APPL_KPPINVPO parameter 37
KPP_AGT_VTAM_APPL_NCS parameter 38
KPP_AGT_VTAM_APPL_OPERATOR parameter 39
KPP_AGT_VTAM_APPL_PREFIX parameter 39
KPP_AGT_VTAM_NODE parameter 40
KPP_AGT_VTM_APPL_AA batch parameter 36
KPP_AGT_VTM_APPL_NCS batch parameter 38
KPP_AGT_VTM_APPL_OPR batch parameter 39
KPP_AGT_VTM_APPL_PREF batch parameter 39
KPP_AGT_VTM_APPL_VPO batch parameter 37
KPP_AGT_VTM_NODE batch parameter 40
KPP_AGT_WTO_MSG parameter
monitoring agent 41
KPP_AGT_WTO_MSGL batch parameter 41
KPP_CMS_FLUSH_INT_HR batch parameter 13
KPP_CMS_HUB_TCP_HOST batch parameter 54
KPP_CMS_LOCAL_CONNECT batch parameter 54
KPP_CMS_NAME batch parameter 56
KPP_CMS_TCP_HOST batch parameter 57
KPP_CMS_TCP_PIPE_PORT batch parameter 58
KPP_CMS_TCP_PIPE6_PORT batch parameter 60
KPP_CMS_TCP_PIPE6S_PORT batch parameter 61
KPP_CMS_TCP_PIPES_PORT batch parameter 59
KPP_CMS_TCP_UDP_PORT batch parameter 62
KPP_CMS_TCP_UDP6_PORT batch parameter 63
Index
291
KPP_CMS_VTM_APPL_LLB batch parameter 63
KPP_CMS_VTM_LU62_LOG batch parameter 64
KPP_CMS_VTM_LU62_LOGTAB batch parameter 65
KPP_CMS_VTM_NETID batch parameter 66
KPP_CMSB_NAME batch parameter 49
KPP_CMSB_TCP_HOST batch parameter 50
KPP_CMSB_VTM_APPL_LLB batch parameter 51
KPP_CMSB_VTM_LU62_LOG batch parameter 52
KPP_CMSB_VTM_NETID batch parameter 53
KPP_ICS_DATASET batch parameter 95
Kpp_MQS_AUTHLIB batch parameter 102
Kpp_MQS_LANGLIB batch parameter 102
KPP_NONSTDnn_MBR batch parameter 20
KPP_NSNEWn_VALUE batch parameter 18
KPP_PD batch parameter 42
KPP_PD parameter 42
KPP_PD_CYL batch parameter 43
KPP_PD_CYL parameter 43
KPP_PD_GRP batch parameter 44
KPP_PD_GRP parameter 44
KPP_PD_HISTCOLL_DATA_IN_AGT_STC parameter 45
KPP_PD_HISTCOLL_DATA_IN_TEMS_STC parameter 46
KPP_PD_ROW batch parameter 47
KPP_PD_ROW parameter 47
KPP_SECURITY_ACTION_CLASS parameter 48
Kpp_TCP_DATA batch parameter 101
KPP_TEMS_BKUP1_NAME_NODEID parameter 49
KPP_TEMS_BKUP1_TCP_HOST parameter 50
KPP_TEMS_BKUP1_VTAM_APPL_LLB_BKR parameter 51
KPP_TEMS_BKUP1_VTAM_LU62_DLOGMOD parameter 52
KPP_TEMS_BKUP1_VTAM_NETID parameter 53
KPP_TEMS_HUB_TCP_HOST parameter 54
KPP_TEMS_LOCAL_CONNECT_FLAG parameter 54
KPP_TEMS_NAME_NODEID parameter 56
KPP_TEMS_TCP_HOST parameter 57
KPP_TEMS_TCP_PIPE_PORT_NUM parameter 58
KPP_TEMS_TCP_PIPE6_PORT_NUM parameter 60, 63
KPP_TEMS_TCP_PIPE6S_PORT_NUM parameter 61
KPP_TEMS_TCP_PIPES_PORT_NUM parameter 59
KPP_TEMS_TCP_UDP_PORT_NUM parameter 62
KPP_TEMS_VTAM_APPL_LLB_BROKER parameter 63
KPP_TEMS_VTAM_LU62_DLOGMOD parameter 64
KPP_TEMS_VTAM_LU62_MODETAB parameter 65
KPP_TEMS_VTAM_NETID parameter 66
Kpp_USS_EXEC batch parameter 97
KPP_X_AGT_CONFIRM_SHUTDOWN parameter 67
KPP_X_AGT_DEBUG_TRACEE parameter 68
KPP_X_AGT_KDC_DEBUG parameter 68
KPP_X_AGT_LGSA_VERIFY parameter 69
KPP_X_AGT_LSRPOOL_BUFFER_NUM parameter 70
KPP_X_AGT_LSRPOOL_BUFSIZEE parameter 71
KPP_X_AGT_SDUMP_SVC_SYS1_DUMP parameter 71
KPP_X_AGT_STORAGE_LIMIT_EXTEND parameter 72
KPP_X_AGT_STORAGE_LIMIT_PRIMARY parameter 73
KPP_X_AGT_STORAGE_RESERVE_EXT parameter 73
KPP_X_AGT_STORAGE_RESERVE_PRI parameter 74
KPP_X_AGT_STORAGE_STGDEBUG parameter 75
KPP_X_AGT_TASKS_ATTACHED_NUM parameter 75
KPP_X_HUB_BKUP1_TCP_HOST parameter 76
KPP_X_HUB_BKUP1_TEMS_VTAM_NETID parameter 76
KPP_X_HUB_BKUP1_VTAM_APPL_GLBBKR parameter 77
KPP_X_HUB_TCP_HOST parameter 77
KPP_X_HUB_TEMS_VTAM_NETID parameter 78
KPP_X_HUB_VTAM_APPL_GLBBKR parameter 78
KPP_X_PD_HISTCOLL_DATA_AGT_STC parameter 79
KD2_OMPE_DB2EXIT batch parameter 87
KD2_OMPE_DB2LOADLIB_Vn batch parameter 88
292
KD2_OMPE_DB2RUNLIB_Vn batch parameter 89
KDC_DEBUG parameter 210
KDC_PARTITIONFILE parameter 196
KDCFC_ALIAS parameter 236
KDE_TRANSPORT parameter 159, 160, 161, 162, 163, 164,
207, 224, 225, 226, 227, 229, 230
KDEB_INTERFACELIST parameter 223
KDO_DB2_LOADLIB batch parameter 89
KDS_AUDIT_ITM_DOMAIN batch parameter 157
KDS_AUDIT_ITM_DOMAIN parameter 157
KDS_AUDIT_MAX_HIST batch parameter 157
KDS_AUDIT_MAX_HIST parameter 157
KDS_AUDIT_TRACE batch parameter 158
KDS_AUDIT_TRACE parameter 158
KDS_CMS_COMM_PROn batch parameter 197
KDS_CMS_COMM_XLAT batch parameter 196
KDS_CMS_CTSOAP batch parameter 215
KDS_CMS_EIF batch parameter 202
KDS_CMS_EIF_BFR_EVT batch parameter 248
KDS_CMS_EIF_BFR_EVT_MAX batch parameter 199
KDS_CMS_EIF_BFR_EVT_PATH batch parameter 248
KDS_CMS_EIF_DISABLE_EMT batch parameter 200
KDS_CMS_EIF_EVT_LISTENER batch parameter 201
KDS_CMS_EIF_FLT_ATTR1 batch parameter 249
KDS_CMS_EIF_FLT_CLASS1 batch parameter 249
KDS_CMS_EIF_FLT_MODE batch parameter 250
KDS_CMS_EIF_HOST batch parameter 203
KDS_CMS_EIF_PORT batch parameter 204
KDS_CMS_EXT_LIM batch parameter 219
KDS_CMS_FLUSH_INT_HR batch parameter 204
KDS_CMS_FLUSH_INT_MIN batch parameter 205
KDS_CMS_HA_EXCL_LIST batch parameter 206
KDS_CMS_HA_TYP batch parameter 206, 258
KDS_CMS_HTTP_PORT batch parameter 207
KDS_CMS_ICU_LANG batch parameter 208
KDS_CMS_KDC_DEBUG batch parameter 210
KDS_CMS_KGL_WTO batch parameter 211
KDS_CMS_KLX_TCP_RECYCLE batch parameter 212
KDS_CMS_PART_NAME batch parameter 213
KDS_CMS_SEC_ENC_KEY batch parameter 214
KDS_CMS_SEC_VALIDATE batch parameter 214
KDS_CMS_STC batch parameter 216
KDS_CMS_STOR_DTL_INT_HR batch parameter 216
KDS_CMS_STOR_DTL_INT_MIN batch parameter 217
KDS_CMS_STOR_DTL_LOG batch parameter 218
KDS_CMS_STOR_MIN_EXT batch parameter 221
KDS_CMS_TCP_HOST batch parameter 222
KDS_CMS_TCP_KDEBLST batch parameter 223
KDS_CMS_TCP_PIPE_PORT batch parameter 224
KDS_CMS_TCP_PIPE6_PORT batch parameter 225
KDS_CMS_TCP_PIPE6S_PORT batch parameter 226
KDS_CMS_TCP_PIPES_PORT batch parameter 227
KDS_CMS_TCP_STC batch parameter 228
KDS_CMS_TCP_UDP_PORT batch parameter 229
KDS_CMS_TCP_UDP6_PORT batch parameter 230
KDS_CMS_TYP batch parameter 232
KDS_CMS_VIPA batch parameter 233
KDS_CMS_VTM_APPL_CUA batch parameter 233
KDS_CMS_VTM_APPL_DS batch parameter 234
KDS_CMS_VTM_APPL_GLB batch parameter 234
KDS_CMS_VTM_APPL_LLB batch parameter 236
KDS_CMS_VTM_APPL_OPR batch parameter 237
KDS_CMS_VTM_APPL_PREF batch parameter 237
KDS_CMS_VTM_APPL_VPO batch parameter 235
KDS_CMS_VTM_LOADLIB batch parameter 98
KDS_CMS_VTM_LU62_LOG batch parameter 238
KDS_CMS_VTM_LU62_LOGTAB batch parameter 238
KDS_CMS_VTM_MACLIB batch parameter 98
KDS_CMS_VTM_NETID batch parameter 239
KDS_CMS_VTM_NODE batch parameter 240
KDS_HFS_JAVA_DIRn batch parameter 103
KDS_HUB parameter 232
KDS_HUB_GLB_APPL batch parameter 166
KDS_HUB_HA_TYP batch parameter 165
KDS_HUB_TCP_HOST batch parameter 159
KDS_HUB_TCP_HOST parameter 159
KDS_HUB_TCP_PIPE_PORT batch parameter 159
KDS_HUB_TCP_PIPE_PORT_NUM parameter 159
KDS_HUB_TCP_PIPE6_PORT batch parameter 160
KDS_HUB_TCP_PIPE6_PORT_NUM parameter 160
KDS_HUB_TCP_PIPE6S_PORT batch parameter 161
KDS_HUB_TCP_PIPE6S_PORT_NUM parameter 161
KDS_HUB_TCP_PIPES_PORT batch parameter 162
KDS_HUB_TCP_PIPES_PORT_NUM parameter 162
KDS_HUB_TCP_UDP_PORT batch parameter 163
KDS_HUB_TCP_UDP_PORT_NUM parameter 163
KDS_HUB_TCP_UDP6_PORT batch parameter 164
KDS_HUB_TCP_UDP6_PORT_NUM parameter 164
KDS_HUB_TEMS_HA_TYPE parameter 165
KDS_HUB_VTAM_APPL_GLB_BROKER parameter 166
KDS_HUB_VTAM_NETID parameter 166
KDS_HUB_VTM_NETID batch parameter 166
KDS_KMS_SDA batch parameter 167
KDS_KMS_SDA parameter 167
KDS_MIG_TAPE_HILEV batch parameter 168
KDS_MIG_TAPE_HILEV parameter 168
KDS_MIG_TAPE_UNIT batch parameter 168
KDS_MIG_TAPE_UNIT parameter 168
KDS_MIG_TAPE_VOL batch parameter 169
KDS_MIG_TAPE_VOL parameter 169
KDS_MIG_VER batch parameter 170
KDS_MIG_VER parameter 170
KDS_MIG_VSAM_HILEV batch parameter 170
KDS_MIG_VSAM_HILEV parameter 170
KDS_NONSTDnn_DSN batch parameter 171
KDS_NONSTDnn_DSN parameter 171
KDS_NONSTDnn_MBR batch parameter 172
KDS_NONSTDnn_MBR parameter 172
KDS_NONSTDnn_PARM batch parameter 173
KDS_NONSTDnn_PARM parameter 173
KDS_NSNEWnn_VALUE batch parameter 174
KDS_NSNEWnn_VALUE parameter 174
KDS_NSOLDnn_VALUE batch parameter 175
KDS_NSOLDnn_VALUE parameter 175
KDS_PA batch parameter 175
KDS_PA parameter 175
KDS_PA_ADDR batch parameter 176
KDS_PA_NAME batch parameter 177
KDS_PA_PARTITION_ADDRESS parameter 176
KDS_PA_PARTITION_NAME parameter 177
KDS_PA_ROW batch parameter 177
KDS_PA_ROW parameter 177
KDS_PD batch parameter 178
KDS_PD parameter 178
KDS_PD_CYL batch parameter 178
KDS_PD_CYL parameter 178
KDS_PD_GRP batch parameter 179
KDS_PD_GRP parameter 179
KDS_PD_ROW batch parameter 180
KDS_PD_ROW parameter 180
KDS_PH batch parameter 180
KDS_PH parameter 180
KDS_PH_CMS_ALIAS_NAME batch parameter 181
KDS_PH_CMS_COMM_PRO1 batch parameter 182
KDS_PH_CMS_KSH_SECURE batch parameter 183
KDS_PH_CMS_NAME batch parameter 183
KDS_PH_CMS_RTE batch parameter 184
KDS_PH_CMS_SYSV batch parameter 184
KDS_PH_CMS_TCP_HOST batch parameter 185
KDS_PH_CMS_TCP_HOST_LEN batch parameter 186
KDS_PH_CMS_TCP_PORT batch parameter 186
KDS_PH_CMS_USER_QUERY batch parameter 187
KDS_PH_CMS_USER_UPDATE batch parameter 187
KDS_PH_CMS_VTM_APPL_GLB batch parameter 188
KDS_PH_CMS_VTM_LU62_LOG batch parameter 189
KDS_PH_CMS_VTM_NETID batch parameter 189
KDS_PH_ROW batch parameter 181
KDS_PH_ROW parameter 181
KDS_PH_TEMS_ALIAS_NAME parameter 181
KDS_PH_TEMS_COMM_PROTOCOL1 parameter 182
KDS_PH_TEMS_KSH_SECURE parameter 183
KDS_PH_TEMS_NAME_NODEID parameter 183
KDS_PH_TEMS_RTE parameter 184
KDS_PH_TEMS_SYSV_FLAG parameter 184
KDS_PH_TEMS_TCP_HOST parameter 185
KDS_PH_TEMS_TCP_HOST_LEN parameter 186
KDS_PH_TEMS_TCP_PORT_NUM parameter 186
KDS_PH_TEMS_USER_QUERY parameter 187
KDS_PH_TEMS_USER_UPDATE parameter 187
KDS_PH_TEMS_VTAM_APPL_GLB_BROKER parameter 188
KDS_PH_TEMS_VTAM_LU62_DLOGMOD parameter 189
KDS_PH_TEMS_VTAM_NETID parameter 189
KDS_PPI_RECEIVER batch parameter 190
KDS_PPI_RECEIVER parameter 190
KDS_PPI_SENDER batch parameter 191
KDS_PPI_SENDER parameter 191
KDS_PU batch parameter 192
KDS_PU parameter 192
KDS_PU_CMS_NAME batch parameter 193
KDS_PU_CMS_RTE batch parameter 193
KDS_PU_CMS_USER_ID batch parameter 194
KDS_PU_CMS_USER_QUERY batch parameter 194
KDS_PU_CMS_USER_UPDATE batch parameter 195
KDS_PU_ROW batch parameter 192
KDS_PU_ROW parameter 192
KDS_PU_TEMS_NAME_NODEID parameter 193
KDS_PU_TEMS_RTE parameter 193
KDS_PU_TEMS_USER_ID parameter 194
KDS_PU_TEMS_USER_QUERY parameter 194
KDS_PU_TEMS_USER_UPDATE parameter 195
KDS_TEMA_SDA batch parameter 196
KDS_TEMA_SDA parameter 196
KDS_TEMS_COMM_ADDRESS_XLAT parameter 196
KDS_TEMS_COMM_PROTOCOLn parameter 197
KDS_TEMS_DRA_FLAG batch parameter 198
KDS_TEMS_DRA_FLAG parameter 198
KDS_TEMS_EIF_BUFFER_EVENT_MAXSZE parameter 199
KDS_TEMS_EIF_DISABLE_TEC_EMITTER parameter 200
KDS_TEMS_EIF_EVENT_LISTENER parameter 201
KDS_TEMS_EIF_FLAG parameter 202
KDS_TEMS_EIF_HOST parameter 203
KDS_TEMS_EIF_PORT_NUM parameter 204
KDS_TEMS_FLUSH_LSR_BUFR_INT_HR parameter 204
KDS_TEMS_FLUSH_LSR_BUFR_INT_MIN parameter 205
KDS_TEMS_HA_EXCL_LIST parameter 206
KDS_TEMS_HA_TYPE parameter 206, 258
KDS_TEMS_HTTP_PORT_NUM parameter 207
KDS_TEMS_ICU_LANGUAGE_LOCALE parameter 208
KDS_TEMS_KDC_DEBUG parameter 210
KDS_TEMS_KGL_WTO parameter 211
KDS_TEMS_KLX_TCP_TOLERATERECYCLE parameter 212
Index
293
KDS_TEMS_PARTITION_NAME parameter 213
KDS_TEMS_SECURITY_KAES256_ENCKEY parameter 214
KDS_TEMS_SECURITY_KDS_VALIDATE parameter 214
KDS_TEMS_SOAP_SERVER_FLAG parameter 215
KDS_TEMS_STC parameter 216
KDS_TEMS_STORAGE_DETAIL_INT_HR parameter 216
KDS_TEMS_STORAGE_DETAIL_INT_MIN parameter 217
KDS_TEMS_STORAGE_DETAIL_LOG_FLAG parameter 218
KDS_TEMS_STORAGE_LIMIT_EXTEND parameter 219
KDS_TEMS_STORAGE_LIMIT_PRIMARY parameter 220
KDS_TEMS_STORAGE_MINIMUM_EXTEND parameter 221
KDS_TEMS_TCP_HOST parameter 222
KDS_TEMS_TCP_KDEB_INTERFACELIST parameter 223
KDS_TEMS_TCP_PIPE_PORT_NUM parameter 224
KDS_TEMS_TCP_PIPE6_PORT_NUM parameter 225
KDS_TEMS_TCP_PIPE6S_PORT_NUM parameter 226
KDS_TEMS_TCP_PIPES_PORT_NUM parameter 227
KDS_TEMS_TCP_STC parameter 228
KDS_TEMS_TCP_UDP_PORT_NUM parameter 229
KDS_TEMS_TCP_UDP6_PORT_NUM parameter 230
KDS_TEMS_TYPE parameter 232
KDS_TEMS_VIRTUAL_IP_ADDRESS parameter 233
KDS_TEMS_VTAM_APPL_CUA_OPER parameter 233
KDS_TEMS_VTAM_APPL_GLB_BROKER parameter 234
KDS_TEMS_VTAM_APPL_KDS_VTAMID parameter 234
KDS_TEMS_VTAM_APPL_KDSINVPO parameter 235
KDS_TEMS_VTAM_APPL_OPERATOR parameter 237
KDS_TEMS_VTAM_APPL_PREFIX parameter 237
KDS_TEMS_VTAM_LU62_DLOGMOD parameter 238
KDS_TEMS_VTAM_LU62_MODETAB parameter 238
KDS_TEMS_VTAM_NETID parameter 239
KDS_TEMS_VTAM_NODE parameter 240
KDS_USS_EXEC batch parameter 97
KDS_VALIDATE parameter 214
KDS_VTAMID parameter 234
KDS_X_HUB_BKUP1_TCP_HOST parameter 240
KDS_X_HUB_BKUP1_TEMS_VTAM_NETID parameter 241
KDS_X_HUB_BKUP1_VTAM_APPL_GLBBKR parameter 241
KDS_X_KDCFC_RXLIMIT parameter 242
KDS_X_KDE_TRANSPORT_HTTP_OPTIONS parameter 242
KDS_X_KDE_TRANSPORT_OPTIONS parameter 243
KDS_X_KDE_TRANSPORT_POOL_OPTIONS parameter 244
KDS_X_SECURITY_RESOURCE_CLASS parameter 244
KDS_X_SECURITY_USER_EXIT parameter 245
KDS_X_STC_SYSTCPD_INCLUDE_FLAG parameter 246
KDS_X_TEMS_CONFIRM_SHUTDOWN parameter 246
KDS_X_TEMS_DEBUG_TRACE parameter 247
KDS_X_TEMS_EIF_BFR_EVT parameter 248
KDS_X_TEMS_EIF_BFR_EVT_PATH parameter 248
KDS_X_TEMS_EIF_FLT_ATTR1 parameter 249
KDS_X_TEMS_EIF_FLT_CLASS1 parameter 249
KDS_X_TEMS_EIF_FLT_MODE parameter 250
KDS_X_TEMS_FRAME_STACK_SIZE parameter 250
KDS_X_TEMS_LGSA_VERIFY parameter 251
KDS_X_TEMS_LOGBLOCK_RKLVLOG_SIZE parameter 251
KDS_X_TEMS_LOGBUFS_RKLVLOG_BUFSZ parameter 252
KDS_X_TEMS_LSRPOOL_BUFFER_NUM parameter 252
KDS_X_TEMS_LSRPOOL_BUFSIZE parameter 253
KDS_X_TEMS_LSRSTRNO_CONCURRENT parameter 254
KDS_X_TEMS_SDUMP_SVC_SYS1_DUMP parameter 254
KDS_X_TEMS_STORAGE_RESERVE_PRI parameter 255
KDS_X_TEMS_STORAGE_STGDEBUG parameter 256
KDS_X_TEMS_TASKS_ATTACHED_NUM parameter 257
KDS_X_TEMS_WTO parameter 257
KGL_WTO parameter 211
KGLHC_PPI_RECEIVER parameter 190
KGLHC_PPI_SENDER parameter 191
294
KGW_CTG_DLL_DSN batch parameter 86
KI2_CLA_BMP_RESLIB batch parameter 90
KI2_I1_CLA_IMS_RESLIB batch parameter 90
KI5_ICT_SCEXLINK batch parameter 91
KI5_ICT_SFUNLINK batch parameter 92
KI5_IMS_RESLIB batch parameter 90
KI5_X_ICT_IMS_CONNECT_FLAG batch parameter 91, 92
KMC_CFG_MCDB2_LIB batch parameter 89
KMS_DISABLE_TEC_EMITTER parameter 200
KMS_OMTEC_INTEGRATION parameter 202
KNA_NETV_LNKLIB batch parameter 93
KOB_TOM_STC batch parameter 259
KOB_TOM_STC parameter 259
KOB_TOM_VTAM_APPL_LOGON batch parameter 260
KOB_TOM_VTAM_APPL_LOGON parameter 260
KOB_TOM_VTAM_NODE batch parameter 261
KOB_TOM_VTAM_NODE parameter 261
KQI_CEE_LE370_LKED batch parameter 83
KQI_CEE_LE370_RUN batch parameter 85
KQI_CIC_LOADLIB batch parameter 87
KQI_MQS_LOADLIB batch parameter 103
krarloff utility 276
L
LANG parameter 208
Language locale field 14, 208
language locales 208
LDAP
See Lightweight Directory Access Protocol
LGSA parameter 251
Lightweight Directory Access Protocol 277
LIMIT parameter 219, 220
load libraries
CNMLINK 93
Health Checker 90
ICSF 87
NetView 93
Load optimization field 115
Local location broker applid field 51
Local Location Broker applid field 63
Local location broker field 236
LOGBLOCK parameter 251
LOGBUFS parameter 252
Logmode table field 150
Logmode table name field 238
LOGMODE table name field 65
logmode tables system library 98
Low-level dataset qualifier field 19, 171
LSRPOOL parameter 252, 253
LSRSTRNO parameter 254
LU6.2 logmode field 52, 64, 150, 238
LUGROUP field 144
M
macro library 94
Maintenance procedure prefix field 122
Major Node field 40
managed Java beans 277
Maximum storage request size (extended) field 219
Maximum storage request size (primary) field 220
MBeans 277
MDM
See Multidomain Management
Member field 20, 172
Mgmtclas field 129, 132
Microsoft Management Console 277
Mid-level qualifier field 107
Minimum extended storage field 29, 221
MINIMUM parameter 221
MMC
See Microsoft Management Console
Monitored Hub TEMS field 193
Monitored RTE field 193
monitoring agent
advanced agent configuration values
KPP_AGT_WTO_MSG 41
Multidomain Management 278
14
N
Name field 117
names, parameter 3
NAT
See Network Address Translation
NetView CNMLINK load library 93
NetView PPI receiver field 24, 190
Network address (Hostname of Hub) field 157, 159
Network address (Hostname of Secondary TEMS) field 50
Network Address (Hostname of the primary TEMS) field 54
Network address (Hostname) field 30
Network Address field 57
Network Address Translation 278
Network File System 278
Network ID field 53, 66, 139, 151, 239
Network ID of hub field 166
Network interface list field 31, 223
New Value field 174
NFS
See Network File System
O
ODBC
See Open Database Connectivity
Old Value field 22, 175
OMEGAMON Tivoli Event Adapter 279
OMEGAMON XE Advanced Agent configuration values
KPP_AGT_FLUSH_LSR_BUFR_INT_HR 13
KPP_AGT_FLUSH_LSR_BUFR_INT_MIN 14
KPP_AGT_KGL_WTO 16
KPP_AGT_KLX_TCP_TOLERATERECYCLE 17
KPP_AGT_STORAGE_DETAIL_INT_HR 27
KPP_AGT_STORAGE_DETAIL_INT_MIN 28
KPP_AGT_STORAGE_MINIMUM_EXTEND 29
KPP_AGT_VIRTUAL_IP_ADDRESS 35
OMEGAMON XE Agent's Applids
KPP_AGT_VTAM_APPL_AA 36
KPP_AGT_VTAM_APPL_KPPINVPO 37
KPP_AGT_VTAM_APPL_NCS 38
KPP_AGT_VTAM_APPL_OPERATOR 39
OMEGAMON XE Agent's local TCP/IP information
KPP_AGT_TCP_HOST 30
OMEGAMON XE Agent's local VTAM and logon information
KPP_AGT_VTAM_APPL_PREFIX 39
KPP_AGT_VTAM_NODE 40
OMEGAMON XE Agent's Primary TEMS VTAM information
KPP_TEMS_VTAM_APPL_LLB_BROKER 63
KPP_TEMS_VTAM_LU62_DLOGMODE 64
KPP_TEMS_VTAM_LU62_MODETAB 65
OMEGAMON XE Agent's Primary TEMS VTAM information
(continued)
KPP_TEMS_VTAM_NETID 66
OMEGAMON XE historical collection is being performed by
the monitoring agent address space
KPP_PD_HISTCOLL_DATA_IN_AGT_STC 45
OMEGAMON XE Historical data collection by the Tivoli
Enterprise Monitoring Server address space 46
OMEGAMON XE If the Agent requires address translation
support
KPP_AGT_PARTITION_NAME 23
OMEGAMON XE If the Agent requires network interface list
support
KPP_AGT_TCP_KDEB_INTERFACELIST 31
OMEGAMON XE monitoring agent
KPP_AGT_KGL_WTO 16
Agent's Applids
KPP_AGT_TCP_HOST 30
Agent's local VTAM and logon information
KPP_TEMS_VTAM_LU62_DLOGMOD 64
historical collection is being performed by the monitoring
agent address space
KPP_PD_HISTCOLL_DATA_IN_AGT_STC 45
Historical data collection by the Tivoli Enterprise
Monitoring Server address space
KPP_PD_HISTCOLL_DATA_IN_TEMS_STC 46
If the Agent requires address translation support
If the Agent requires network interface list support
Nonstandard parameters
KPP_AGT_NONSTDn_MBR 20
KPP_AGT_NSNEWn_VALUE 18
KPP_PD 42
KPP_PD_CYL 43
KPP_PD_GRP 44
KPP_PD_ROW 47
KPP_X_PD_HISTCOLL_DATA_AGT_STC 79
KPP_TEMS_TCP_PIPE_PORT_NUM 58
KPP_TEMS_TCP_PIPE6_PORT_NUM 60, 63
KPP_TEMS_TCP_PIPE6S_PORT_NUM 61
KPP_TEMS_TCP_PIPES_PORT_NUM 59
KPP_TEMS_TCP_UDP_PORT_NUM 62
Index
295
OMEGAMON XE monitoring agent (continued)
Secondary TEMS TCP/IP information
KPP_TEMS_BKUP1_TCP_HOST 50
KPP_TEMS_BKUP1_NAME_NODEID 49
KPP_TEMS_BKUP1_VTAM_APPL_LLB_BKR 51
KPP_TEMS_BKUP1_VTAM_LU62_DLOGMOD 52
KPP_TEMS_BKUP1_VTAM_NETID 53
Specify communication protocols preference for TEMS
connection
KPP_AGT_COMM_PROTOCOLn 11
KPP_AGT_CONFIGURATION_MODE 10
KPP_AGT_STC 26
KPP_AGT_TCP_STC 32
KPP_TEMS_TCP_HOST 57
Values that describe the address space for the agent and
the TEMS
KPP_AGT_TEMS_NAME_NODEIDD 34
Values that describe the Primary TEMS the Agent will
connect to
KPP_TEMS_HUB_TCP_HOST 54
KPP_TEMS_LOCAL_CONNECT_FLAG 54
KPP_TEMS_NAME_NODEID 56
OMEGAMON XE Nonstandard parameters
KPP_AGT_NONSTDn_MBR 20
KPP_TN3270_DXL_APPLID 18
OMEGAMON XE Persistent datastore table space allocation
overrides
KPP_PD 42
KPP_PD_CYL 43
KPP_PD_GRP 44
KPP_PD_ROW 47
OMEGAMON XE Protocol port numbers for Agent connection
to TEMS
KPP_TEMS_TCP_PIPE6_PORT_NUM 60, 63
OMEGAMON XE Secondary TEMS TCP/IP information
OMEGAMON XE Secondary TEMS VTAM information
KPP_TEMS_BKUP1_VTAM_APPL_LLB_BKRG 51
OMEGAMON XE Specify communication protocols preference
for TEMS connection
OMEGAMON XE Take Action commands security settings
OMEGAMON XE Values that describe the address space
KPP_AGT_STC 26
KPP_AGT_TCP_STC 32
OMEGAMON XE Values that describe the address space for
the agent and the TEMS
296
OMEGAMON XE Values that describe the Primary TEMS the
Agent will connect to
OMNIbus 283
Open Database Connectivity 279
OTEA
See OMEGAMON Tivoli Event Adapter
overview, parameters 1
P
parameter 79
Parameter field 21, 173
parameter library 95
parameter names 3
RTE_SYSV_VTAM_APPLID_PREFIX 138
parameter values
how to set 1
parameters covered in this guide 5
parameters, overview 1
PARM_BATCH batch parameter 94
PARMGEN configuration method 2
PARMGEN parameter names
DS_TEMS_VTAM_APPL_LLB_BROKER 236
GBL_DSN_ACF2_MACLIB 81
GBL_DSN_CBC_SCCNOBJ 81
GBL_DSN_CBC_SCLBSID 82
GBL_DSN_CEE_SCEEBIND 82
GBL_DSN_CEE_SCEEBND2 82
GBL_DSN_CEE_SCEECPP 83
GBL_DSN_CEE_SCEELIB 83
GBL_DSN_CEE_SCEELKED 83
GBL_DSN_CEE_SCEELKEX 84
GBL_DSN_CEE_SCEEMSGP 84
GBL_DSN_CEE_SCEERUN 85
GBL_DSN_CEE_SCEESPC 85
GBL_DSN_CICS_CTG_DLL 86
GBL_DSN_CICS_SCTGSID 86
GBL_DSN_CICS_SDFHC370 86
GBL_DSN_CICS_SDFHLOAD 87
GBL_DSN_CSF_SCSFMOD0 87
GBL_DSN_DB2_DSNEXIT 87
GBL_DSN_DB2_LOADLIB_Vn 88
GBL_DSN_DB2_RUNLIB_Vn 89
GBL_DSN_DB2_SDSNLOAD 89
GBL_DSN_HZSPROC_LOADLIB 90
GBL_DSN_IMS_RESLIB 90
GBL_DSN_IMS_SCEXLINK 91
GBL_DSN_IMS_SFUNLINK 92
GBL_DSN_ISP_SISPLOAD 92
GBL_DSN_NETVIEW_CNMLINK 93
GBL_DSN_SYS1_BRODCAST 93
GBL_DSN_SYS1_CSSLIB 93
GBL_DSN_SYS1_HSMLOGY 94
GBL_DSN_SYS1_LINKLIB 94
GBL_DSN_SYS1_MACLIB 94
GBL_DSN_SYS1_MODGEN 95
GBL_DSN_SYS1_PARMLIB 95
GBL_DSN_SYS1_PROCLIB 96
GBL_DSN_SYS1_SAXREXEC 96
GBL_DSN_SYS1_SBLSCLI0 96
GBL_DSN_SYS1_SBPXEXEC 97
GBL_DSN_SYS1_SISTMAC1 98
GBL_DSN_SYS1_VTAMLIB 98
GBL_DSN_SYS1_VTAMLST 99
PARMGEN parameter names (continued)
GBL_DSN_TCP_ETC_SERVICES 99
GBL_DSN_TCP_SEZACMTX 100
GBL_DSN_TCP_SEZARNT1 100
GBL_DSN_TCP_SEZATCP 100
GBL_DSN_TCP_SYSTCPD_TCPDATA 101
GBL_DSN_TCP_SYSTCPD_TCPDATA_MFN 101
GBL_DSN_WMQ_SCSQANLE 102
GBL_DSN_WMQ_SCSQAUTH 102
GBL_DSN_WMQ_SCSQLOAD 103
GBL_HFS_JAVA_DIRn 103
GBL_INST_HILEV 104
GBL_TARGET_HILEV 104
GBL_USER_JCL 105
KPP_AGT_CONFIGURATION_MODE 10, 80
KPP_AGT_ICU_LANGUAGE_LOCALE 14
KPP_AGT_KGL_WTO 16
KPP_AGT_STC 26
KPP_AGT_TCP_HOST 30
KPP_AGT_TCP_STC 32
KPP_AGT_TEMA_SDA 33
KPP_AGT_WTO_MSG 41
KPP_NONSTDnn_MBR 20
KPP_NSNEWn_VALUE 18
KPP_PD 42
KPP_PD_CYL 43
KPP_PD_GRP 44
KPP_PD_ROW 47
KPP_TEMS_BKUP1_VTAM_APPL_LLB_BKR 51
KPP_TEMS_TCP_PIPE6_PORT_NUM 60
KPP_TEMS_TCP_UDP6_PORT_NUM 63
KPP_TEMS_VTAM_LU62_DLOGMOD 64
KPP_X_AGT_CONFIRM_SHUTDOWN 67
KPP_X_AGT_DEBUG_TRACE 68
KPP_X_AGT_LGSA_VERIFY 69
KPP_X_AGT_LSRPOOL_BUFFER_NUM 70
KPP_X_AGT_LSRPOOL_BUFSIZEE 71
KPP_X_AGT_SDUMP_SVC_SYS1_DUMP 71
KPP_X_AGT_STORAGE_LIMIT_EXTEND 72
KPP_X_AGT_STORAGE_LIMIT_PRIMARY 73
KPP_X_AGT_STORAGE_RESERVE_EXT 73
KPP_X_AGT_STORAGE_RESERVE_PRI 74
KPP_X_AGT_STORAGE_STGDEBUG 75
KPP_X_AGT_TASKS_ATTACHED_NUM 75
KPP_X_HUB_BKUP1_TCP_HOST 76
KPP_X_HUB_BKUP1_TEMS_VTAM_NETID 76
KPP_X_HUB_BKUP1_VTAM_APPL_GLBBKR 77
KPP_X_HUB_TCP_HOST 77
KPP_X_HUB_TEMS_VTAM_NETID 78
KPP_X_HUB_VTAM_APPL_GLBBKR 78
KDS_AUDIT_TRACE 158
KDS_HUB_TCP_PIPE_PORT_NUM 159
KDS_HUB_TCP_PIPE6_PORT_NUM 160
KDS_HUB_TCP_PIPE6S_PORT_NUM 161
KDS_HUB_TCP_UDP_PORT_NUM 163
KDS_HUB_TCP_UDP6_PORT_NUM 164
KDS_HUB_TEMS_HA_TYPE 165
KDS_HUB_VTAM_APPL_GLB_BROKER 166
KDS_HUB_VTAM_NETID 166
KDS_KMS_SDA 167
KDS_MIG_VER 170
KDS_PA 175
KDS_PA_PARTITION_ADDRESS 176
KDS_PA_PARTITION_NAME 177
KDS_PA_ROW 177
KDS_PD 178
KDS_PD_CYL 178
KDS_PD_GRP 179
KDS_PD_ROW 180
KDS_PH 180
KDS_PH_ROW 181
KDS_PH_TEMS_ALIAS_NAME 181
KDS_PH_TEMS_COMM_PROTOCOL1 182
KDS_PH_TEMS_KSH_SECURE 183
KDS_PH_TEMS_NAME_NODEID 183
KDS_PH_TEMS_RTE 184
KDS_PH_TEMS_SYSV_FLAG 184
KDS_PH_TEMS_TCP_HOST 185
KDS_PH_TEMS_TCP_HOST_LEN 186
KDS_PH_TEMS_TCP_PORT_NUM 186
Index
297
KDS_PH_TEMS_USER_QUERY 187
KDS_PH_TEMS_USER_UPDATE 187
KDS_PH_TEMS_VTAM_APPL_GLB_BROKER 188
KDS_PH_TEMS_VTAM_LU62_DLOGMOD 189
KDS_PH_TEMS_VTAM_NETID 189
KDS_PPI_SENDER 191
KDS_PU 192
KDS_PU_ROW 192
KDS_PU_TEMS_NAME_NODEID 193
KDS_PU_TEMS_RTE 193
KDS_PU_TEMS_USER_ID 194
KDS_PU_TEMS_USER_QUERY 194
KDS_PU_TEMS_USER_UPDATE 195
KDS_TEMA_SDA 196
KDS_TEMS_COMM_ADDRESS_XLAT 196
KDS_TEMS_COMM_PROTOCOLn 197
KDS_TEMS_EIF_BUFFER_EVENT_MAXSZE 199
KDS_TEMS_EIF_DISABLE_TEC_EMITTER 200
KDS_TEMS_EIF_EVENT_LISTENER 201
KDS_TEMS_EIF_FLAG 202
KDS_TEMS_EIF_HOST 203
KDS_TEMS_EIF_PORT_NUM 204
KDS_TEMS_FLUSH_LSR_BUFR_INT_HR 204
KDS_TEMS_FLUSH_LSR_BUFR_INT_MIN 205
KDS_TEMS_HA_EXCL_LIST 206
KDS_TEMS_HA_TYPE 206, 258
KDS_TEMS_HTTP_PORT_NUM 207
KDS_TEMS_ICU_LANGUAGE_LOCALE 208
KDS_TEMS_KDC_DEBUG 210
KDS_TEMS_KGL_WTO 211
KDS_TEMS_KLX_TCP_TOLERATERECYCLE 212
KDS_TEMS_PARTITION_NAME 213
KDS_TEMS_SECURITY_KAES256_ENCKEY 214
KDS_TEMS_SECURITY_KDS_VALIDATE 214
KDS_TEMS_SOAP_SERVER_FLAG 215
KDS_TEMS_STC 216
KDS_TEMS_STORAGE_DETAIL_INT_HR 216
KDS_TEMS_STORAGE_DETAIL_INT_MIN 217
KDS_TEMS_STORAGE_DETAIL_LOG_FLAG 218
KDS_TEMS_STORAGE_LIMIT_EXTEND 219
KDS_TEMS_STORAGE_LIMIT_PRIMARY 220
KDS_TEMS_TCP_HOST 222
KDS_TEMS_TCP_KDEB_INTERFACELIST 223
KDS_TEMS_TCP_PIPE_PORT_NUM 224
KDS_TEMS_TCP_PIPE6_PORT_NUM 225
KDS_TEMS_TCP_PIPE6S_PORT_NUM 226
KDS_TEMS_TCP_PIPES_PORT_NUM 227
KDS_TEMS_TCP_STC 228
KDS_TEMS_TCP_UDP_PORT_NUM 229
KDS_TEMS_TCP_UDP6_PORT_NUM 230
KDS_TEMS_TYPE 232
KDS_TEMS_VIRTUAL_IP_ADDRESS 233
KDS_TEMS_VTAM_APPL_CUA_OPER 233
KDS_TEMS_VTAM_APPL_GLB_BROKER 234
KDS_TEMS_VTAM_APPL_KDS_VTAMID 234
KDS_TEMS_VTAM_APPL_KDSINVPO 235
KDS_TEMS_VTAM_APPL_OPERATOR 237
KDS_TEMS_VTAM_APPL_PREFIX 237
KDS_TEMS_VTAM_LU62_DLOGMOD 238
KDS_TEMS_VTAM_LU62_MODETAB 238
KDS_TEMS_VTAM_NETID 239
KDS_TEMS_VTAM_NODE 240
KDS_X_HUB_BKUP1_TCP_HOST 240
KDS_X_HUB_BKUP1_TEMS_VTAM_NETID 241
298
KDS_X_HUB_BKUP1_VTAM_APPL_GLBBKR 241
KDS_X_KDCFC_RXLIMIT 242
KDS_X_KDE_TRANSPORT_HTTP_OPTIONS 242
KDS_X_KDE_TRANSPORT_OPTIONS 243
KDS_X_KDE_TRANSPORT_POOL_OPTIONS 244
KDS_X_SECURITY_RESOURCE_CLASS 244
KDS_X_SECURITY_USER_EXIT 245
KDS_X_STC_SYSTCPD_INCLUDE_FLAG 246
KDS_X_TEMS_CONFIRM_SHUTDOWN 246
KDS_X_TEMS_DEBUG_TRACE 247
KDS_X_TEMS_EIF_BFR_EVT 248
KDS_X_TEMS_EIF_BFR_EVT_PATH 248
KDS_X_TEMS_EIF_FLT_ATTR1 249
KDS_X_TEMS_EIF_FLT_CLASS1 249
KDS_X_TEMS_EIF_FLT_MODE 250
KDS_X_TEMS_FRAME_STACK_SIZE 250
KDS_X_TEMS_LGSA_VERIFY 251
KDS_X_TEMS_LOGBLOCK_RKLVLOG_SIZE 251
KDS_X_TEMS_LOGBUFS_RKLVLOG_BUFSZ 252
KDS_X_TEMS_LSRPOOL_BUFFER_NUMn 252
KDS_X_TEMS_LSRPOOL_BUFSIZEn 253
KDS_X_TEMS_LSRSTRNO_CONCURRENT 254
KDS_X_TEMS_SDUMP_SVC_SYS1_DUMP 254
KDS_X_TEMS_STORAGE_RESERVE_PRI 255
KDS_X_TEMS_STORAGE_STGDEBUG 256
KDS_X_TEMS_TASKS_ATTACHED_NUM 257
KDS_X_TEMS_WTO 257
KOB_TOM_STC 259
PKPP_X_AGT_KDC_DEBUG 68
RTE_BASE_NAME 107
RTE_CANSCN_STC 107
RTE_CANSETE_STC 108
RTE_DESCRIPTION 109
RTE_HCK_STC_INTERVAL 110
RTE_HILEV 110
RTE_JCL_SUFFIX 111
RTE_KCNDLSSI_IEFSSN00_FORMAT 112
RTE_KCNSTR00_SSID 113
RTE_KCNSTR00_WTO 113
RTE_LOG_SYSOUT 116
RTE_NAME 117
RTE_PDS_BACKUP_FLAG 118
RTE_PDS_BATCHINIT_FLAG 117
RTE_PDS_EXPORT_FLAG 119
RTE_PDS_EXTRACT_FLAG 120
RTE_PDS_FILE_COUNT 121
RTE_PDS_HILEV 121
RTE_PDS_KPDPROC_PREFIX 122
RTE_PDS_SMS_MGMTCLAS 122
RTE_PDS_SMS_STORCLAS 123
RTE_PDS_SMS_UNIT 124
RTE_PDS_SMS_VOLUME 124
RTE_REMOTE_LPAR_FLAG 125
RTE_SECURITY_CLASS 125
RTE_SECURITY_FOLD_PASSWORD_FLAG 126
RTE_SECURITY_USER_LOGON 127
RTE_SHARE 128
RTE_SMS_MGMTCLAS 129
RTE_SMS_PDSE_FLAG 129
RTE_SMS_STORCLAS 130
RTE_SMS_UNIT 131
RTE_SMS_VOLUME 131
RTE_SMS_VSAM_MGMTCLAS 132
RTE_SMS_VSAM_STORCLAS 133
RTE_SMS_VSAM_VOLUME 133
RTE_STC_PREFIX 134
RTE_SYSV_NAME 135
RTE_SYSV_TEMS_NAME_NODEID 137
RTE_SYSV_VTAM_APPLID_MODEL 137
RTE_SYSV_VTAM_NETID 139
RTE_TCP_HOST 139
RTE_TCP_PORT_NUM 140
RTE_TCP_STC 141
RTE_TEMS_CONFIGURED_FLAG 141
RTE_TEMS_NAME_NODEID 142
RTE_TN3270_DXL_HOSTADDRESS 143
RTE_TN3270_DXL_LUGROUP 144
RTE_TN3270_DXL_TN3270PORT 144
RTE_TYPE 145
RTE_USERMODS_FLAG 146
RTE_USS_RTEDIR 146
RTE_VSAM_HILEV 148
RTE_VTAM_APPLID_PREFIX 148
RTE_VTAM_GBL_MAJOR_NODE 149
RTE_VTAM_LU62_DLOGMOD 150
RTE_VTAM_LU62_MODETAB 150
RTE_VTAM_NETID 151
RTE_X_KCNDLSSI_INITPARM_FLAG 152
RTE_X_KCNSTR00_PLEXCOLLECT 152
RTE_X_KCNSTR00_REFRESH 153
RTE_X_SECURITY_DATA_ABOVE 154
RTE_X_SECURITY_EXIT_LIB 154
Partition address field 176
Partition name field 23, 177, 213
password encryption 87
PDS
See Persistent Datastore
PDSE field 129
PerfMon
See Performance Monitor
Performance Monitor, Windows 280
Persistent Datastore 280
Port number (IP.PIPE for IPV6) field 60, 225
Port number (IP.PIPE) field 58, 224
Port number (IP.UDP) field 62, 229
Port number (IP6.UDP) field 63, 230
Port number (Secure IP.PIPE for IPV6) field 61, 226
Port number (Secure IP.PIPE) field 59, 227
Port number field 140, 144
procedures library 96
Protocol 1 field 182
Q
Query access field
187
R
Reconnect after TCP/IP recycle field
Remote Procedure Call 281
Remote RTE for transport field 125
RESERVE parameter 255
RKANPARU library 1
17, 212
RPC
See Remote Procedure Call
RTE base alias specification field 135
RTE directory field 146
RTE name specification field 135
RTE parameters 107
RTE_ACF2_MACLIB batch parameter 81
RTE_BASE_MIDLEV batch parameter 107
RTE_BASE_NAME parameter 107
RTE_CAN_SS_IEFSSN_FMT batch parameter 112
RTE_CAN_SS_STC batch parameter 107
RTE_CAN_SS_WTO batch parameter 113
RTE_CAN_SSID batch parameter 113
RTE_CANSCN_STC parameter 107
RTE_CANSETE_STC parameter 108
RTE_CMS batch parameter 141
RTE_CMS_NAME batch parameter 142
RTE_CUA_SECURITY batch parameter 127
RTE_DEBUG_SYSOUT batch parameter 109
RTE_DEBUG_SYSOUT parameter 109
RTE_DESC batch parameter 109
RTE_DESCRIPTION parameter 109
RTE_ETE_STC batch parameter 108
RTE_FOLD_PWD batch parameter 125, 126
RTE_HCK_INTERVAL batch parameter 110
RTE_HCK_LOADLIB batch parameter 90
RTE_HCK_STC_INTERVAL parameter 110
RTE_HILEV batch parameter 110
RTE_HILEV parameter 110
RTE_JCL_SUFF batch parameter 111
RTE_JCL_SUFFIX parameter 111
RTE_KCNDLSSI_IEFSSN00_FORMAT parameter 112
RTE_KCNSTR00_SSID parameter 113
RTE_KCNSTR00_WTO parameter 113
RTE_KCNSTR00_XCFGROUP batch parameter 114
RTE_KCNSTR00_XCFGROUP parameter 114
RTE_LOAD_OPTIMIZE batch parameter 115
RTE_LOAD_OPTIMIZE parameter 115
RTE_LOAD_SHARED_LIBS batch parameter 116
RTE_LOAD_SHARED_LIBS parameter 116
RTE_LOG_SYSOUT batch parameter 116
RTE_LOG_SYSOUT parameter 116
RTE_NAME batch parameter 117
RTE_NAME parameter 117
RTE_PDS_BACKUP_FLAG parameter 118
RTE_PDS_BATCHINIT_FLAG parameter 117
RTE_PDS_BU batch parameter 118
RTE_PDS_CNT batch parameter 121
RTE_PDS_EXP batch parameter 119
RTE_PDS_EXPORT_FLAG parameter 119
RTE_PDS_EXT batch parameter 120
RTE_PDS_EXTRACT_FLAG parameter 120
RTE_PDS_FILE_COUNT parameter 121
RTE_PDS_HILEV batch parameter 121
RTE_PDS_HILEV parameter 121
RTE_PDS_KPDPROC_PREFIX parameter 122
RTE_PDS_PROC_PREF batch parameter 122
RTE_PDS_SMS_MGMT_CLAS batch parameter 122
RTE_PDS_SMS_MGMTCLAS parameter 122
RTE_PDS_SMS_STOR_CLAS batch parameter 123
RTE_PDS_SMS_STORCLAS parameter 123
RTE_PDS_SMS_UNIT parameter 124
RTE_PDS_SMS_VOLUME parameter 124
RTE_PDS_UNIT batch parameter 124
RTE_PDS_VOL batch parameter 124
RTE_PDSE batch parameter 129
RTE_REMOTE batch parameter 125
Index
299
RTE_REMOTE_LPAR_FLAG parameter 125
RTE_SECURITY_CLASS parameter 125
RTE_SECURITY_FOLD_PASSWORD_FLAG parameter 126
RTE_SECURITY_USER_LOGON parameter 127
RTE_SHARE batch parameter 128
RTE_SHARE parameter 128
RTE_SMS_MGMT_CLAS batch parameter 129
RTE_SMS_MGMTCLAS parameter 129
RTE_SMS_PDSE_FLAG parameter 129
RTE_SMS_STOR_CLAS batch parameter 130
RTE_SMS_STORCLAS parameter 130
RTE_SMS_UNIT parameter 131
RTE_SMS_VOLUME parameter 131
RTE_SMS_VSAM_MGMT_CLAS batch parameter 132
RTE_SMS_VSAM_MGMTCLAS parameter 132
RTE_SMS_VSAM_STOR_CLAS batch parameter 133
RTE_SMS_VSAM_STORCLAS parameter 133
RTE_SMS_VSAM_VOLUME parameter 133
RTE_STC_PREF batch parameter 134
RTE_STC_PREFIX parameter 134
RTE_SYS_PROCLIB batch parameter 96
RTE_SYS_VTAMLST batch parameter 99
RTE_SYSV batch parameter 136
RTE_SYSV_BASE_ALIAS batch parameter 135
RTE_SYSV_BASE_ALIAS parameter 135
RTE_SYSV_CMS_NAME batch parameter 137
RTE_SYSV_NAME batch parameter 135
RTE_SYSV_NAME parameter 135
RTE_SYSV_SYSVAR_FLAG parameter 136
RTE_SYSV_TEMS_NAME_NODEID parameter 137
RTE_SYSV_VTAM_APPLID_MODEL parameter 137
RTE_SYSV_VTAM_APPLID_PREFIX parameter 138
RTE_SYSV_VTAM_NETID parameter 139
RTE_SYSV_VTM_APPL_MODEL batch parameter 137
RTE_SYSV_VTM_APPL_PREF batch parameter 138
RTE_SYSV_VTM_NETID batch parameter 139
RTE_TCP_HOST batch parameter 139
RTE_TCP_HOST parameter 139
RTE_TCP_PORT batch parameter 140
RTE_TCP_PORT_NUM parameter 140
RTE_TCP_STC batch parameter 141
RTE_TCP_STC parameter 141
RTE_TEMS_CONFIGURED_FLAG parameter 141
RTE_TEMS_NAME_NODEID parameter 142
RTE_TN3270_DXL_HOSTADDRESS parameter 143
RTE_TN3270_DXL_LUGROUP parameter 144
RTE_TN3270_DXL_TN3270PORT parameter 144
RTE_TN3270_LUGROUP batch parameter 144
RTE_TN3270_TCP_HOST batch parameter 143
RTE_TN3270_TCP_PORT batch parameter 144
RTE_TYP batch parameter 145
RTE_TYPE parameter 145
RTE_UNIT batch parameter 131
RTE_USERMODS batch parameter 146
RTE_USERMODS_FLAG parameter 146
RTE_USS_RTEDIR batch parameter 146
RTE_USS_RTEDIR parameter 146
RTE_VOL batch parameter 131
RTE_VSAM_HILEV batch parameter 148
RTE_VSAM_HILEV parameter 148
RTE_VSAM_VOL batch parameter 133
RTE_VTAM_APPLID_PREFIX parameter 148
RTE_VTAM_GBL_MAJOR_NODE parameter 149
RTE_VTAM_LU62_DLOGMOD parameter 150
RTE_VTAM_LU62_MODETAB parameter 150
RTE_VTAM_NETID parameter 151
RTE_VTM_APPL_PREF batch parameter 148
300
RTE_VTM_CANDLE_NODE batch parameter 149
RTE_VTM_LU62_LOG batch parameter 150
RTE_VTM_LU62_LOGTAB batch parameter 150
RTE_VTM_NETID batch parameter 151
RTE_X_KCNDLSSI_INITPARM_FLAG parameter 152
RTE_X_KCNSTR00_PLEXCOLLECT parameter 152
RTE_X_KCNSTR00_REFRESH parameter 153
RTE_X_SECURITY_DATA_ABOVE parameter 154
RTE_X_SECURITY_EXIT_LIB parameter 154
runtime environment parameters 107
RTE_BASE_NAME 107
RTE_DESCRIPTION 109
RTE_HCK_STC_INTERVAL 110
RTE_HILEV 110
RTE_JCL_SUFFIX 111
RTE_LOG_SYSOUT 116
RTE_NAME 117
RTE_PDS_BACKUP_FLAG 118
RTE_PDS_EXPORT_FLAG 119
RTE_PDS_EXTRACT_FLAG 120
RTE_PDS_FILE_COUNT 121
RTE_PDS_HILEV 121
RTE_PDS_KPDPROC_PREFIX 122
RTE_PDS_SMS_MGMTCLAS 122
RTE_PDS_SMS_STORCLAS 123
RTE_PDS_SMS_UNIT 124
RTE_PDS_SMS_VOLUME 124
RTE_REMOTE_LPAR_FLAG 125
RTE_SECURITY_CLASS 125
RTE_SECURITY_FOLD_PASSWORD_FLAG 126
RTE_SECURITY_USER_LOGON 127
RTE_SHARE 128
RTE_SMS_MGMTCLAS 129
RTE_SMS_PDSE_FLAG 129
RTE_SMS_STORCLAS 130
RTE_SMS_UNIT 131
RTE_SMS_VOLUME 131
RTE_SMS_VSAM_MGMTCLAS 132
RTE_SMS_VSAM_STORCLAS 133
RTE_SMS_VSAM_VOLUME 133
RTE_STC_PREFIX 134
RTE_SYSV_NAME 135
RTE_SYSV_SYSVAR_FLAG 136
RTE_SYSV_TEMS_NAME_NODEID 137
RTE_SYSV_VTAM_APPLID_MODEL 137
RTE_SYSV_VTAM_APPLID_PREFIX 138
RTE_SYSV_VTAM_NETID 139
RTE_TCP_HOST 139
RTE_TCP_PORT_NUM 140
RTE_TCP_STC 141
RTE_TEMS_CONFIGURED_FLAG 141
RTE_TEMS_NAME_NODEID 142
RTE_TN3270_DXL_HOSTADDRESS 143
RTE_TN3270_DXL_LUGROUP 144
RTE_TN3270_DXL_TN3270PORT 144
RTE_TYPE 145
RTE_USERMODS_FLAG 146
RTE_USS_RTEDIR 146
RTE_VSAM_HILEV 148
RTE_VTAM_APPLID_PREFIX 148
RTE_VTAM_GBL_MAJOR_NODE 149
RTE_VTAM_LU62_DLOGMOD 150
RTE_VTAM_LU62_MODETAB 150
runtime environment parameters (continued)
RTE_VTAM_NETID 151
Runtime members analysis field 146
S
SDUMP parameter 254
Secure Hypertext Transport Protocol 276
secure pipe 283
Secure Sockets Layer API 275, 276, 281
Security system field 127
self-describing agent 281
SELinux 281
ServerLocation parameter 203
ServerPort parameter 204
Sharing field 128
Simple Network Management Protocol 282
Simple Object Access Protocol 282
single sign-on 282
Situation Event Forwarder 282
Situation Update Forwarder 282
SMP/E 104
See System Modification Program/Extended
SNA global location broker applid field 188
SNA LU6.2 logmode logmode field 189
SNA network ID field 189
SNA.PIPE field 11, 197
SNMP
See Simple Network Management Protocol
SOAP
See Simple Object Access Protocol
Software Support 267
Specify SAF security class 125
Specify the communication protocols in priority sequence
field 11
SPIPE 275, 283
SQL
See Structured Query Language
SSL
See Secure Sockets Layer
SSM
See System Service Monitors
SSO
See single sign-on
Started task field 32, 141, 228
startup parameters, defined 1
STC prefix field 134, 216
Storage detail logging: Hours field 27, 216
Storage detail logging: Minutes field 28, 217
Storclas field 130, 133
Structured Query Language 283
SUF
See Situation Update Forwarder
support assistant 267
SYS1_MACLIB batch parameter 94
SYS1.ACF2.MACLIB library 81
SYS1.MACLIB macro library 94
SYS1.PARMLIB parameter library 95
SYS1.PROCLIB procedures library 96
SYS1.SAXREXEC library 96
SYS1.SBLSCLI0 library 96
SYS1.SISTMAC1 library 98
SYS1.VTAMLIB library 98
SYS1.VTAMLST library 99
SYSIN parameters 1
SYSOUT class field 116
SYSTCPD library 101
System Authorization Facility (SAF)
security class name, specifying 125
system libraries
Health Checker 96
SYS1.ACF2.MACLIB 81
SYS1.MACLIB 94
SYS1.PARMLIB 95
SYS1.PROCLIB 96
SYS1.SBLSCLI0 96
SYS1.SISTMAC1 98
SYS1.VTAMLIB 98
SYS1.VTAMLST 99
SYSTCPD 101
System Modification Program/Extended 273, 284
System Monitor Agent 283
System procedure field 96
System Service Monitors, Netcool/OMNIbus 283
System VTAMLST field 99
T
Tape high-level qualifier field 168
Tape unit type field 168
Tape volser field 169
target libraries high-level qualifiers 104
TASKS parameter 257
TCP hostname field 185, 222
TCP port number field 186
TCP_DATA batch parameter 101
TCP/IP
See Transmission Control Protocol/Internet Protocol
TCP/IP system library 101
TCP/IP_USERID parameter 212, 228
TDW
See Tivoli Data Warehouse
telnet 284
TEMS application ID field 234
TEMS name field 137, 142, 183
TEMS Name field 34, 56
TEMS PPI sender field 191
TEMS secured field 183
TEMS version field 170
TEPS/e
See Tivoli Enterprise Portal Server extended services
Tivoli Data Warehouse 284
Tivoli Enterprise Monitoring Server parameters 157
GBL_DSN_CBC_SCCNOBJ 81
GBL_DSN_CBC_SCLBSID 82
GBL_DSN_CEE_SCEEBIND 82
GBL_DSN_CEE_SCEEBND2 82
GBL_DSN_CEE_SCEECPP 83
GBL_DSN_CEE_SCEELIB 83
GBL_DSN_CEE_SCEELKED 83
GBL_DSN_CEE_SCEELKEX 84
GBL_DSN_CEE_SCEEMSGP 84
GBL_DSN_CEE_SCEERUN 85
GBL_DSN_CEE_SCEESPC 85
GBL_DSN_CICS_CTG_DLL 86
GBL_DSN_CICS_SCTGSID 86
GBL_DSN_CICS_SDFHC370 86
GBL_DSN_CICS_SDFHLOAD 87
GBL_DSN_DB2_DSNEXIT 87
GBL_DSN_DB2_LOADLIB_Vn 88
GBL_DSN_DB2_RUNLIB_Vn 89
GBL_DSN_DB2_SDSNLOAD 89
GBL_DSN_IMS_RESLIB 90
GBL_DSN_IMS_SCEXLINK 91
Index
301
Tivoli Enterprise Monitoring Server parameters (continued)
GBL_DSN_IMS_SFUNLINK 92
GBL_DSN_SYS1_BRODCAST 93
GBL_DSN_SYS1_CSSLIB 93
GBL_DSN_SYS1_HSMLOGY 94
GBL_DSN_SYS1_LINKLIB 94
GBL_DSN_SYS1_MODGEN 95
GBL_DSN_SYS1_SBPXEXEC 97
GBL_DSN_TCP_ETC_SERVICES 99
GBL_DSN_TCP_SEZACMTX 100
GBL_DSN_TCP_SEZARNT1 100
GBL_DSN_TCP_SEZATCP 100
GBL_DSN_TCP_SYSTCPD_TCPDATA_MFN 101
GBL_DSN_WMQ_SCSQANLE 102
GBL_DSN_WMQ_SCSQAUTH 102
GBL_DSN_WMQ_SCSQLOAD 103
GBL_HFS_JAVA_DIRn 103
KPP_AGT_TEMA_SDA 33
KPP_X_AGT_CONFIRM_SHUTDOWN 67
KPP_X_AGT_DEBUG_TRACE 68
KPP_X_AGT_KDC_DEBUG 68
KPP_X_AGT_LGSA_VERIFY 69
KPP_X_AGT_LSRPOOL_BUFFER_NUM 70
KPP_X_AGT_LSRPOOL_BUFSIZEE 71
KPP_X_AGT_SDUMP_SVC_SYS1_DUMP 71
KPP_X_AGT_STORAGE_LIMIT_EXTEND 72
KPP_X_AGT_STORAGE_LIMIT_PRIMARY 73
KPP_X_AGT_STORAGE_RESERVE_EXT 73
KPP_X_AGT_STORAGE_RESERVE_PRI 74
KPP_X_AGT_STORAGE_STGDEBUG 75
KPP_X_AGT_TASKS_ATTACHED_NUM 75
KPP_X_HUB_BKUP1_TCP_HOST 76
KPP_X_HUB_BKUP1_TEMS_VTAM_NETID 76
KPP_X_HUB_BKUP1_VTAM_APPL_GLBBKR 77
KPP_X_HUB_TCP_HOST 77
KPP_X_HUB_TEMS_VTAM_NETID 78
KPP_X_HUB_VTAM_APPL_GLBBKR 78
KDE_TRANSPORT 159, 160, 161
KDS_AUDIT_TRACE 158
KDS_HUB_TCP_PIPE_PORT_NUM 159
KDS_HUB_TCP_PIPE6_PORT_NUM 160
KDS_HUB_TCP_PIPE6S_PORT_NUM 161
KDS_HUB_TCP_PIPES_PORT_NUM 162
KDS_HUB_TCP_UDP_PORT_NUM 163
KDS_HUB_TCP_UDP6_PORT_NUM 164
KDS_HUB_TEMS_HA_TYPE 165
KDS_HUB_VTAM_APPL_GLB_BROKER 166
KDS_HUB_VTAM_NETID 166
KDS_KMS_SDA 167
KDS_MIG_VER 170
302
KDS_PA 175
KDS_PA_PARTITION_ADDRESS 176
KDS_PA_PARTITION_NAME 177
KDS_PA_ROW 177
KDS_PD 178
KDS_PD_CYL 178
KDS_PD_GRP 179
KDS_PD_ROW 180
KDS_PH 180
KDS_PH_ROW 181
KDS_PH_TEMS_ALIAS_NAME 181
KDS_PH_TEMS_COMM_PROTOCOL1 182
KDS_PH_TEMS_KSH_SECURE 183
KDS_PH_TEMS_NAME_NODEID 183
KDS_PH_TEMS_RTE 184
KDS_PH_TEMS_SYSV_FLAG 184
KDS_PH_TEMS_TCP_HOST 185
KDS_PH_TEMS_TCP_HOST_LEN 186
KDS_PH_TEMS_TCP_PORT_NUM 186
KDS_PH_TEMS_USER_QUERY 187
KDS_PH_TEMS_USER_UPDATE 187
KDS_PH_TEMS_VTAM_APPL_GLB_BROKER 188
KDS_PH_TEMS_VTAM_LU62_DLOGMOD 189
KDS_PH_TEMS_VTAM_NETID 189
KDS_PPI_SENDER 191
KDS_PU 192
KDS_PU_ROW 192
KDS_PU_TEMS_NAME_NODEID 193
KDS_PU_TEMS_RTE 193
KDS_PU_TEMS_USER_ID 194
KDS_PU_TEMS_USER_QUERY 194
KDS_PU_TEMS_USER_UPDATE 195
KDS_TEMA_SDA 196
KDS_TEMS_COMM_ADDRESS_XLAT 196
KDS_TEMS_COMM_PROTOCOLn 197
KDS_TEMS_EIF_BUFFER_EVENT_MAXSZE 199
KDS_TEMS_EIF_DISABLE_TEC_EMITTER 200
KDS_TEMS_EIF_EVENT_LISTENER 201
KDS_TEMS_EIF_FLAG 202
KDS_TEMS_EIF_HOST 203
KDS_TEMS_EIF_PORT_NUM 204
KDS_TEMS_FLUSH_LSR_BUFR_INT_HR 204
KDS_TEMS_FLUSH_LSR_BUFR_INT_MIN 205
KDS_TEMS_HA_EXCL_LIST 206
KDS_TEMS_HA_TYPE 206, 258
KDS_TEMS_HTTP_PORT_NUM 207
KDS_TEMS_ICU_LANGUAGE_LOCALE 208
KDS_TEMS_KDC_DEBUG 210
KDS_TEMS_KGL_WTO 211
KDS_TEMS_KLX_TCP_TOLERATERECYCLE 212
KDS_TEMS_PARTITION_NAME 213
KDS_TEMS_SECURITY_KAES256_ENCKEY 214
KDS_TEMS_SECURITY_KDS_VALIDATE 214
KDS_TEMS_SOAP_SERVER_FLAG 215
KDS_TEMS_STC 216
KDS_TEMS_STORAGE_DETAIL_INT_HR 216
KDS_TEMS_STORAGE_DETAIL_INT_MIN 217
KDS_TEMS_STORAGE_DETAIL_LOG_FLAG 218
KDS_TEMS_STORAGE_LIMIT_EXTEND 219
KDS_TEMS_STORAGE_LIMIT_PRIMARY 220
KDS_TEMS_STORAGE_MINIMUM_EXTEND 221
KDS_TEMS_TCP_HOST 222
KDS_TEMS_TCP_KDEB_INTERFACELIST 223
KDS_TEMS_TCP_PIPE_PORT_NUM 224
KDS_TEMS_TCP_PIPE6_PORT_NUM 225
KDS_TEMS_TCP_PIPE6S_PORT_NUM 226
KDS_TEMS_TCP_PIPES_PORT_NUM 227
KDS_TEMS_TCP_STC 228
KDS_TEMS_TCP_UDP_PORT_NUM 229
KDS_TEMS_TCP_UDP6_PORT_NUM 230
KDS_TEMS_TYPE 232
KDS_TEMS_VIRTUAL_IP_ADDRESS 233
KDS_TEMS_VTAM_APPL_CUA_OPER 233
KDS_TEMS_VTAM_APPL_GLB_BROKER 234
KDS_TEMS_VTAM_APPL_KDS_VTAMID 234
KDS_TEMS_VTAM_APPL_KDSINVPO 235
KDS_TEMS_VTAM_APPL_LLB_BROKER 236
KDS_TEMS_VTAM_APPL_OPERATOR 237
KDS_TEMS_VTAM_APPL_PREFIX 237
KDS_TEMS_VTAM_LU62_DLOGMOD 238
KDS_TEMS_VTAM_LU62_MODETAB 238
KDS_TEMS_VTAM_NETID 239
KDS_TEMS_VTAM_NODE 240
KDS_X_HUB_BKUP1_TCP_HOST 240
KDS_X_HUB_BKUP1_TEMS_VTAM_NETID 241
KDS_X_HUB_BKUP1_VTAM_APPL_GLBBKR 241
KDS_X_KDCFC_RXLIMIT 242
KDS_X_KDE_TRANSPORT_HTTP_OPTIONS 242
KDS_X_KDE_TRANSPORT_OPTIONS 243
KDS_X_KDE_TRANSPORT_POOL_OPTIONS 244
KDS_X_SECURITY_RESOURCE_CLASS 244
KDS_X_SECURITY_USER_EXIT 245
KDS_X_STC_SYSTCPD_INCLUDE_FLAG 246
KDS_X_TEMS_CONFIRM_SHUTDOWN 246
KDS_X_TEMS_DEBUG_TRACE 247
KDS_X_TEMS_EIF_BFR_EVT 248
KDS_X_TEMS_EIF_BFR_EVT_PATH 248
KDS_X_TEMS_EIF_FLT_ATTR1 249
KDS_X_TEMS_EIF_FLT_CLASS1 249
KDS_X_TEMS_EIF_FLT_MODE 250
KDS_X_TEMS_FRAME_STACK_SIZE 250
KDS_X_TEMS_LGSA_VERIFY 251
KDS_X_TEMS_LOGBLOCK_RKLVLOG_SIZE 251
KDS_X_TEMS_LOGBUFS_RKLVLOG_BUFSZ 252
KDS_X_TEMS_LSRPOOL_BUFFER_NUM 252
KDS_X_TEMS_LSRPOOL_BUFSIZE 253
KDS_X_TEMS_LSRSTRNO_CONCURRENT 254
KDS_X_TEMS_SDUMP_SVC_SYS1_DUMP 254
KDS_X_TEMS_STORAGE_RESERVE_PRI 255
KDS_X_TEMS_STORAGE_STGDEBUG 256
KDS_X_TEMS_TASKS_ATTACHED_NUM 257
KDS_X_TEMS_WTO 257
KOB_TOM_STC 259
LIMIT 220
RTE_CANSCN_STC 107
RTE_CANSETE_STC 108
RTE_KCNDLSSI_IEFSSN00_FORMAT 112
RTE_KCNSTR00_SSID 113
RTE_KCNSTR00_WTO 113
RTE_PDS_BATCHINIT_FLAG 117
RTE_X_KCNDLSSI_INITPARM_FLAG 152
RTE_X_KCNSTR00_PLEXCOLLECT 152
RTE_X_KCNSTR00_REFRESH 153
RTE_X_SECURITY_DATA_ABOVE 154
RTE_X_SECURITY_EXIT_LIB 154
Tivoli Enterprise Portal Server extended services 284
Tivoli Integrated Portal 285
Tivoli OMEGAMON Manager 274, 285
TLS 276
TMS encryption key field 214
TMS:Engine (non-CUA) field 39
TMS:Engine default values 2
TMS:Engine operator (non-CUA) field 237
TMS:Engine VTAM program operator field 37, 233, 235
TOM
See Tivoli OMEGAMON Manager
Transmission Control Protocol/Internet Protocol 285
Transport Layer Security API 276
Type (Hub or Remote) field 232
Type field 145
U
UDP
See User Datagram Protocol
Unit field 131
UNIX System Services (USS) 146
Update access field 187
Use z/OS system variables? field 136
User Datagram Protocol 285
User ID field 194
V
Validate security field 214
Virtual IP Address (VIPA) type field 35, 233
Volser field 131, 133
VSAM high-level qualifier field 170
VTAM
logmode tables 98
macro library 98
VTAMLST library 99
VTAM applid for Alert Adapter field 36
VTAM load library field 98
VTAM macro library field 98
VTAM major node name field 149
W
WAV file 286
where configured parameters are stored 1
wildcard 286
Windows Dynamic Link Library 274
Windows Management Instrumentation API 286
Windows Performance Monitor 280
WMI
See Windows Management Instrumentation
WTO parameter 257
X
XML
Extensible Markup Language.
286
Z
z/OS
286
Index
303
304
Readers’ Comments — We'd Like to Hear from You
IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS
Publication No. SC14-7280-01
We appreciate your comments about this publication. Please comment on specific errors or omissions, accuracy,
organization, subject matter, or completeness of this book. The comments you send should pertain to only the
information in this manual or product and the way in which the information is presented.
For technical questions and information about products and prices, please contact your IBM branch office, your
IBM business partner, or your authorized remarketer.
When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your comments in any
way it believes appropriate without incurring any obligation to you. IBM or any other organizations will only use
the personal information that you supply to contact you about the issues that you state on this form.
Comments:
Thank you for your support.
Send your comments to the address on the reverse side of this form.
If you would like a response from IBM, please fill in the following information:
Name
Address
Company or Organization
Phone No.
Email address
SC14-7280-01
___________________________________________________________________________________________________
Readers’ Comments — We'd Like to Hear from You
Cut or Fold
Along Line
_ _ _ _ _ _ _Fold
_ _ _and
_ _ _Tape
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _Please
_ _ _ _ _do
_ _not
_ _ staple
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _Fold
_ _ _and
_ _ Tape
______
NO POSTAGE
NECESSARY
IF MAILED IN THE
UNITED STATES
BUSINESS REPLY MAIL
FIRST-CLASS MAIL
PERMIT NO. 40
ARMONK, NEW YORK
POSTAGE WILL BE PAID BY ADDRESSEE
_________________________________________________________________________________________
Fold and Tape
Please do not staple
Fold and Tape
SC14-7280-01
Cut or Fold
Along Line
Printed in USA
SC14-7280-01

IBM Tivoli OMEGAMON XE e IBM Tivoli Management Services en z

Transcripción

Documentos relacionados

FRONT PANEL DESCRIPTION SPECIFICATIONS On line

790-4E24V 790-4E12V 790-4E24V 790-4E12V

790-4A24B 790-4A12B