System Event Manager

Reasons to buy

Performance monitoring checks the total number of jobs in the system, total ASP used, total amount of CPU currently being used, the number of batch jobs held, pool size, number of database pages or non-database faults, users or jobs exceeding time slice, job priority, CPU percentage, jobs that have been running for longer than expected etc.

Job Queue Monitoring checks the status of any job queue, if the number of jobs in any job queue exceeds your pre-defined threshold or if a job has been waiting too long on a job queue without being processed.

Device Monitoring checks the status of any device such as communications lines, controllers, printers, tape drives etc.

Object Monitoring checks for the existence or non-existence of any object, values of data areas, the size of any object (including data queues), whether there are records in a file or if a file has more records than expected. Files can be deleted or cleared automatically after calling a program, triggered by data appearing in a file - great for EDI.

Output Queue Monitoring checks the status of any output queue, the number of spool file entries on output queues, whether the number of pages exceeds a threshold for any spool file etc.

Distribution Queue Monitoring checks the depth of any distribution queue and whether it is in an error status.

User Profile Monitoring checks the status of user profiles (e.g. disabled users) or whether users have exceeded a pre-defined threshold for storage used.

Screen Monitoring checks any screen text, including error messages sent to the screen during long-running interactive jobs.

Inactivity Monitoring checks to see if screens have been inactive for a pre-defined period of time (from 1 minute upwards). Different monitoring intervals can be applied to different groups of jobs, users or subsystems. Actions can vary depending upon the program being run, job status (e.g. DSPW), user, time of day etc and critical applications can be ignored. Signed-on sessions can be automatically disconnected or ended and automatic screensavers can be activated if there is a period of inactivity. Screensavers include optional password protection to prevent unauthorised use of the screen. Exceptions can be made so that certain users, jobs or screens can be exempt from action.