The
iSeries Server Agent takes the load off your system operators by continuously
monitoring the operating health of your iSeries systems, day and night.
Now the IT department can concentrate on more productive work, safe in the
knowledge that no important message or event goes unnoticed.
The Server Agent running on each iSeries server forwards
messages and events to the
Visual Message Center console, so they can be managed automatically, including message replies
or system command actions.
The more tasks you automate, the more time you can save!
Our technical consultants can advise you on automation strategies.
If an event cannot be resolved automatically then an
operator can be alerted immediately with full diagnostic information,
so they can take corrective action, before your business is affected.
|
| Check iSeries system health by
monitoring |
 |
Message queues |
 |
Job activity |
 |
Job status |
 |
Job Duration |
 |
System history log (QHST) |
 |
Job queue status |
 |
Device status |
 |
Restricted State processes |
|
|
| Technical
Details
The iSeries Server Agent can be configured to monitor
any number of system message queues, as well as operating status and specific
events.
Message monitoring
OS/400 and most iSeries applications use message queues to notify operators
of important events. The iSeries Server Agent can monitor any number of
message queues, including system message queues (e.g. QSYSOPR) and specific
third-party application messages. You can even choose generic or *ALL
message queue monitoring within a specific library, useful if message
queues can be created dynamically. Resource impact is minimal.
Examples of critical messages include:
- Application errors, for example
data errors, missing objects, object locks, full files
- Configuration changes, such as disabled user profiles
or devices
- Hardware and device issues, such as printers, communication
lines, disk usage
- Third-party application operation messages, such as
licensing issues, configuration
- And many more.
Job Activity
If critical jobs do not start or finish on time, your company may not
get access to critical data. For example, nighttime batch processes must
finish before users can work in the morning. The iSeries Server Agent
can monitor the activity of specific jobs at any time, so you can get
alerted of any potential problem before it's too late.
Job Status
The iSeries Server Agent detects jobs that are in an erroneous state,
e.g. MSGW, INEL, LCKW. For example, unattended jobs will not be processed
if they are waiting for a message reply, or if they are trying to access
a locked object.
Job Duration
The new Job Duration Monitor monitors the duration of the activity
of a job, providing an easy way to monitor that batch or interactive processes
start and end within acceptable thresholds.
The user can select the job name, the job user name, the time limit, the
repeat time and the notification for status changes of these jobs. The
repeat time and the notify change status flag are two new parameters for
this monitor.
Restricted State monitoring
When the system is in Restricted State, it's not possible to monitor
it from outside, it's only possible to do it from the iSeries console.
The new Restricted State Monitor Agent for iSeries eliminates this problem.
When an error is produced, the agent opens a communication line and sends
the alert to the configured remote messenger receivers. Operators don't
need to stay in front of the server to perform processes like SAVSYS (Save
the System) or RCLSTG (Reclaim Storage).
System History Log (QHST)
The system history log contains valuable information including hardware
error warnings; security messages; IPL information; job start, end and
CPU time; PTF information; changes to system values; pool sizes; and much
more. The iSeries Server Agent simplifies the monitoring and analysis
of information logged to QHST on all your servers.
Job Queue Status
If a job queue has an overflow or it is inoperative, then jobs cannot
be processed normally. The iSeries Server Agent can provide detailed information
on critical job queues at all times, including the number of jobs in release
status, and the status of the queue itself.
Device Status
Specific devices, controllers and lines (e.g. Ethernet lines, printers,
fax servers and so on), can be monitored to detect erroneous situations.
Full error code and diagnostic information is retrieved.
|