Introduction to NonStop Operations Management

Application Management
Introduction to NonStop Operations Management–125507
11-5
Check List for an Applications Review
•
Will status messages be displayed so that operators know that the application is
running properly?
•
Have the naming conventions been followed?
•
What operational procedures are required to support the application?
•
How fault-tolerant is the application? Can it handle minor problems? Does the
application have recovery procedures for each phase of processing?
•
What are the backup procedures? How often should NonStop TM/MP dumps be
performed?
•
What provisions must be made for off-site disaster recovery?
•
Are additional tools or utilities (programs, command files, TACL routines)
needed before the application can go into production? Will the operations staff
be involved in tool development?
•
What impact does the application have on production schedules and report
distribution?
•
What documentation does the operator need? Is there online help? What are the
procedures for updating the documentation? Who is responsible for updating
documentation?
•
What training does the operator need to monitor the application and run jobs?
•
What does the operator have to do to restart the job? Is this information
documented?
•
What error messages will operators have to understand? Will all problems
generate events or messages? Is this information documented?
•
What are the problem escalation procedures? Whom do operators contact when
they cannot resolve a problem?
•
How often does the application need to be run, and what is the impact of the
application on the level of service?
•
Is the application a batch program that will need to be run many times, or is the
application an online program that needs to be started only once?
•
How long does the application take to run? Can other applications run while this
application is running?
•
Does the application provide performance statistics? What type of statistics?
•
What are the security provisions?
•
Does the application require users to log on and supply passwords?
•
Who can access files, databases, terminals, systems, and so on? Can the
operations staff control access?
•
Can the operations staff audit access attempts?