By: TomLiotta

TomLiotta — Wed, 28 Nov 2012 01:30:49 +0000

In general, an operator handles day to day needs of the system. That might involve tracking printer supplies, backup tape cartridges and other common physical elements.

The system will often send messages to an operator to inform of printer problems or backup process problems for examples, and the operator is responsible for knowing how to handle the request and usually for taking any action. Messages also commonly include logical rather than physical problems. Automated processes can report problems to an operator, and the operator is responsible for knowing whatever the appropriate problem resolution procedures are for the site.

An administrator is more concerned with general configuration items. That might involve creating user profiles and authorizing users to different parts of the system. An administrator should know what business functions (applications) are performed by the system and which users should have access to those functions.

An administrator often also needs to know how the applications make use of system functions such as networking. That can put some responsibility on the administrator for ensuring that networking functions are working well and that the applications can access networking well.

That can also mean that an administrator might monitor memory, disk, CPU and other resource usage by applications. If applications show that bottlenecks are slowing throughput down to unacceptable levels, changes to system configurations might be done to help shift resource usage to increase performance. It might be necessary to document requirements for purchase of additional system resources (more memory, more DASD, etc.)

For either operator or administrator, tasks can overlap. The responsibilities might be handled by a single person in smaller systems (or in larger systems that have system management software installed). Different sites have different needs.

An operator operates. An administrator administrates. Consider a heavy-equipment contractor who has a collection of construction machines. There will be an operator (or many) who actually runs the machines. There will also be an administrator who determines which machines (which resources, including people) should be available for a given job, who should be using them, what maintenance schedules are, when to replace them, etc.

Computer systems can be thought of similarly. Operation and administration are areas that need to work together, but require different skill sets.

Either way, operation and administration of AS/400s is generally the same as it is on any multi-user business computer system as far as tasks go. But like all different types of systems, the commands and interfaces for those tasks are specific to AS/400s. And for any particular AS/400, it’s up to the site to determine what tasks need to be done and who will do them. An AS/400 at a manufacturing site is likely to do different work than one at a LasVegas casino. It will always be site itself that sets the requirements.

Tom

By: MayurRastogi

MayurRastogi — Tue, 27 Nov 2012 15:51:20 +0000

Many Thanks Todd.. This is the answer that describes or clear all the doubts.

By: ToddN2000

ToddN2000 — Tue, 27 Nov 2012 15:38:44 +0000

the main difference is system authority. That would be set by company policy so it varies greatly. Operator should have less authority than the Administrator.

By: MayurRastogi

MayurRastogi — Tue, 27 Nov 2012 15:35:45 +0000

I came here after searching over several sites. but didnt get the satisfactory docs or answers there!Looking for your kind support on it!

Comments on: Operator & Administrator

By: TomLiotta

By: MayurRastogi

By: ToddN2000

By: MayurRastogi