MODIFYING THE STANDARD ORDERING FOR ALERT HISTORY
Article ID: 131293
Updated On:
Products
CMDB for z/OS
NetSpy Network Performance
NetMaster Network Automation
SOLVE
NetMaster Network Management for SNA
NetMaster Network Management for TCP/IP
NetMaster File Transfer Management
Issue/Introduction
From cust:
Our question relates to the ordering of the alerts on history of the Net-
Master Alert Monitor.
When we access the history without alert filtering the order prioritizes
the exhibiting of the most recent date. But when filtering is used by
specific severity (for example) the order is modified and exhibits the
oldest date--what can generate excessive time to load the screen. We
ask if there is the possibility to alter this behavior on the alert history
so that with filtering it be ordered from the newest date--as it occurs
without filtering.
Our question relates to the ordering of the alerts on history of the Net-
Master Alert Monitor.
When we access the history without alert filtering the order prioritizes
the exhibiting of the most recent date. But when filtering is used by
specific severity (for example) the order is modified and exhibits the
oldest date--what can generate excessive time to load the screen. We
ask if there is the possibility to alter this behavior on the alert history
so that with filtering it be ordered from the newest date--as it occurs
without filtering.
Environment
OS: z/OS.
Resolution
These notes are from L2 Support:
-
The current code is working as designed--in that if on the alert history
screen--once a filter command is issued it makes the display in as-
cending sequence. There is nothing we can do about that but there
is a circumvention.
Try the following when a user wants to change a filter but continue to
be placed at the very last alerts:
From anywhere in the product do:
=/alh.b;filter
where filter is the name of the filter desired. E.g.: =/alh.b;sev1 would
bring up alert history with dates in descending sequence using filter
SEV1.
Notice that =/alh.b alone takes user to alert history without a filter. The
use of the semicolon in the command allows the filter name to be
passed to the command.
-
Also there is the SORT command. After doing the FILTER command
the user could do a SORT on the date--like:
SORT DATE D
-
-
The current code is working as designed--in that if on the alert history
screen--once a filter command is issued it makes the display in as-
cending sequence. There is nothing we can do about that but there
is a circumvention.
Try the following when a user wants to change a filter but continue to
be placed at the very last alerts:
From anywhere in the product do:
=/alh.b;filter
where filter is the name of the filter desired. E.g.: =/alh.b;sev1 would
bring up alert history with dates in descending sequence using filter
SEV1.
Notice that =/alh.b alone takes user to alert history without a filter. The
use of the semicolon in the command allows the filter name to be
passed to the command.
-
Also there is the SORT command. After doing the FILTER command
the user could do a SORT on the date--like:
SORT DATE D
-
Feedback
Yes
No
Powered by
