My PMR to IBM Tivoli support
I’d be surprised if there wasn’t already an ER for this, but if you
don’t mind, please submit one.
Do you know if anybody else has asked or criticized this major
limitation.
Its hard to believe that there isn’t something that emulate what a
simple one line script would accomplish.
In the ER, I would expect support for perl regex pattern, where patterns
can be indexed to return the matching index as a displayable value.
match process string against /opt/IBM*\s+(\S+java*\)s+server1 pattern and return pattern matching (\S+java*\)
IBM’s Response
Yes, we already have an ER opened for this case, please note down the
request number: MR0108092213
****
ITM 6 has limitations when monitoring processes.
Customer needs to monitor processes with very long names, in this case
the WebSphere NodeAgent process with 4999 characters. The unique string
“nodeagent” is at the very end of the process name and the Unix OS agent
cannot find this process: The attribute command_name is limited to 100
characters and for command_name_U to 768 Bytes.
Cust needs a possibility to monitor such long process names using the
standard ITM 6 OS agent.
****
It is already a recognized request. You can follow up on the progress of
the request with your IBM Rep. Please let me know if you have any other
questions.
Tags: ibm, java ibm, line script, name, pattern, process, regex pattern, Rep. Please, Request, request number, server1, STRING, unix os
Posted in ITM6.x | Comments (0)
ITM 6.2 FP1 contains several new and changed T/EC class changes, ranging from new classes, new slots, and only ONE new slot (omnux_value replacing kux_value).
**I have not seen an ITM event containing kux_value nor omnux_value, but to be safe, I added the old ‘kux_value’ slot to the kux.baroc file.
TOTAL: 22 baroc files
|
Baroc
|
Difference
|
Desc
|
|
ka4.baroc
|
Changes
|
Sentry3_5_Base class changed to Omegamon_Base
14 new classes
** JDS: Replace with new baroc
|
|
khd.baroc
|
New
|
|
|
kib.baroc
|
Changes
|
Sentry3_5_Base class changed to Omegamon_Base
one new slot: link_table in ITM_Universal_Messages
** JDS: Replace with new baroc
|
|
klz.baroc
|
Changes
|
Sentry3_5_Base class changed to Omegamon_Base
3 new classes : File pattern, comparison and host availability
several new slot changes : file information file content changed and checksum
** JDS: Replace with new baroc
|
|
knt.baroc
|
Changes
|
Sentry3_5_Base class changed to Omegamon_Base
8 new classes
several slot changes
** JDS: Replaced with new baroc
|
|
koq.baroc
|
Changes
|
Sentry3_5_Base class changed to Omegamon_Base
3 new classes
** JDS: Replaced with new baroc
|
|
kor.baroc
|
Changes
|
Sentry3_5_Base class changed to Omegamon_Base
11 new classes
several new slots : including table space used/allocated, processes, session details, lock wait time
** JDS: Replaced with new baroc
|
|
koy.baroc
|
Changes
|
Sentry3_5_Base class changed to Omegamon_Base
1 new class : Sybase segment detail
several new slots : lock wait time, engine number and status, number of databases open, logon available
** JDS: Replaced with new baroc
|
|
kp5.baroc
|
New
|
|
|
kph.baroc
|
None
|
|
|
kpk.baroc
|
None
|
|
|
kpv.baroc
|
New
|
|
|
kpx.baroc
|
None
|
|
|
kqr.baroc
|
New
|
|
|
kqv.baroc
|
New
|
|
|
kqx.baroc
|
New
|
|
|
ksy.baroc
|
New
|
|
|
kud.baroc
|
Changes
|
Sentry3_5_Base class changed to Omegamon_Base
3 new classes
new slots added to existing classes
** JDS: Replace with new baroc
|
|
kul.baroc
|
Changes
|
Sentry3_5_Base class changed to Omegamon_Base
** JDS: Replace with new baroc
|
|
kux.baroc
|
Changes
|
Sentry3_5_Base class changed to Omegamon_Base
kux_value(STRING) changed to omunx_value(STRING)
8 new classes added
** JDS: Modified new kux.baroc to include kux_value slot
|
|
kva.baroc
|
None
|
|
|
om_tec.baroc
|
None
|
|
Tags: baroc, base, class, class changes, databases, ec, file, file pattern, fp1, itm, JDS, kux, New, None, number, Omegamon, omnux, Replace, Replaced, segment, Sentry, session details, slot, slots, STRING, table, table space, time, time engine, universal messages, value
Posted in Non-Tivoli | Comments (0)
Regular expression predicates were introduced as of T/EC 3.7 that make the task of string pattern matching and manipulation a clean and intuitive procedure.
In a nutshell, there are basically 7 predicates, where
- one is used to define a regular expression pattern
- two are to perform a substring subsitition
- the remaining four are for pattern matching.
Read the rest of this entry »
Tags: added emphasis, Documentation, enterprise console, expression, match, numeric string, pattern, pattern definitions, pattern matching, perl syntax, regex, regular expression, regular expression pattern, result, rules, STRING, tab space, TEC, UTILIZATION
Posted in TEC | Comments (0)
