Reduce Operators Work Load - You can take care of all jobs that need to be scheduled, messages will dealt with instantly, critical conditions can be monitored for, housekeeping automated.
Improve Service to End Users - Reports will be distributed when required, jobs will be run when they should, messages not missed. You can be sure of consistency minimising the chance of errors.
Maximize Machine Efficiency - Spread the workload away from peak times or make use of the Job Control module to balance throughput. Automatically reorganize files to free up space.

To give an example of its high level of functionality, Jobs can be set up to run daily, weekly, monthly, day of month, month end date and selected days of the month. They can be attached to a calendar to define the days to run, or add a number of days to the calendar to run (normally financial month ends and days after  month ends), attach a calendar holding days the jobs have not to run on (daily jobs not to run on bank holidays). 

Naturally we cater for Dependent jobs, you can Specify the latest time a job can become active or the amount of time a job can run. Useful to stop long updates running into the morning.

Once a job has completed you can set up completion commands to run after a job has been completed. This allows for commands like sending the spool file as a database file to another machine via TCP/IP or formatting the spool file into a useable database file, to be executed.

The  Scheduler can be integrated with all of the other modules to provide an easy to use complete automation solution

Specify all or specific reports to be distributed. If specifying individual reports to be distributed, the attributes of the print can  change each time it is distributed.

For each report specified or all reports, specify a list of users to receive the report. Each user can have a different header page attached or define a  default page and use replacement values, such as name and department to speed up the set up.

Send the reports to another AS/400 using SNADS or put them on another AS/400 output queue.

Use  completion commands to format a spool file to a database file and TCP/IP or SNADS it to another AS/400 or PC.  See the Spool File Formatter.

Distribution maintenance that allows searches and  changes to be made to distribution set up at the distribution level. A use of this would be to search for all reports being distributed to a user name containing 'mark' in any case, and then use the list presented to change the user to a new user or copy the distribution so a new user gets it.

Message Manager allows any message queue to be monitored.

Copy selected message to up to 3 other queues.
Reply to a message if it meets the correct selection criteria.
Automatically receive a file sent by SNADS if it meets the correct selection criteria..
Automatically start a process running if a message received meets the correct selection criteria.
Remove specific messages from a queue.

When a message queue is being monitored, it does not allocate the message queue exclusively.

Some main reasons for using the Message Manager function are :

Filter QSYSOPR having specific messages sent to support staff, highlighting problems.
Consider what would happen if you missed a Mirrored Disk failure message, Serious Storage Condition. What is the cost of downtime per hour for your organisation ? It would justify the cost immediately.

To automatically reply to  messages. Conditioning can be applied so different replies are sent depending on the message and/or the time the message is sent.

Answering alignment messages on laser printers or sending an ignore reply when a data base file reaches it's limit of records.

Automatically receive and process files sent by another AS/400.

Start processes by sending a message to a queue that is  being  monitored. The message could be sent from another AS/400.

It is like having another pair of eyes monitoring :

Lines
Controllers
Devices
Network servers
Network interfaces
Job queues
Output queues
Sub systems
Jobs within a job queue
Prints within an output queue.
 
You decide what to monitor and when and how often to monitor it. You can schedule the commands to run and perform specific actions dependent on the object's status.

The Health Checker only has to alert you to one critical problem to pay for itself many times over.

Spool Manager has three main areas :

Allows spool files to be archived to a data base which can then be saved to tape. It can handle *IPDS files as well as standard reports.  This can be done selectively or by output queue.

Allows output queues to be defined on how to clean them up. Selection by number of days old can be applied to specific statuses of spool files and  the report automatically moved to another output queue that will be archived or just deleted.

Allow spool files including *IPDS files to be duplicated to other output queues. This allows spool files produced to be printed at multiple output queues at once.

File Manager has three main areas :

Allow you to produce a print, by library, files that have deleted records, reporting information on each file. Note : The space saving  is just on the physicals alone; There would be more savings, depending on how many logicals were based over the physical. Processing time can also be saved by removing deleted records.

Allows physicals within a library to be reorganised, thus saving disk space, and processing time. The physicals to reorganise can be selected by size of saving or by percentage of saving. Specify a list of  files to ignore. This allows the reorganisation to be set up to run overnight.

Allows you to define from which files you wish to remove members and what the removal criteria should be. It is  useful for cleaning up files that use members to backup data before processing or files used to extract information into separate members.

Process  journal receivers to help in backup situations or just to keep system storage  down. Receivers can be changed, deleted and/or saved and sent via SNADs or TCP/IP to other machines. The other side of this process is that a receiver sent to another AS/400 can be automatically unpacked and attached to a journal