IBM OS/390 User Manual
•
Scheduling - occurs during the planning process, and aids in identifying
conflicts and impacts, and determines target dates for changes.
conflicts and impacts, and determines target dates for changes.
•
Distributing - this depends on the type of change, for example rolling out new
levels of software across several systems.
levels of software across several systems.
•
Installing - the actual installation of changes. Installation should be able to
be scheduled for a particular date and time of day.
be scheduled for a particular date and time of day.
•
Backout - reversing a change if it does not meet the installation or test
criteria. The process to do this should be understood and planned for before
the change is implemented.
criteria. The process to do this should be understood and planned for before
the change is implemented.
•
Tracking - transmitting the state of the change to the change management
system. This provides a common view to everyone involved in the process.
system. This provides a common view to everyone involved in the process.
•
Post-installation analysis - reviewing completed changes to ensure they met
the desired objectives, and to identify improvements that could be made to
the change process.
the desired objectives, and to identify improvements that could be made to
the change process.
30.2.3 Methodology
Change management is effectively implemented in several simple steps. First, a
log of system changes should be kept. The simplest method is simply recording
the information in a data set or PDS member. This can be improved by using a
table (as provided by TSO/ISPF) or database management system (such as DB2)
where change information can be formatted into fields for easier querying,
searching, and updating. Ultimately one should investigate a change
management product, which will also add the ability to support the more formal
process activities, such as assessment, planning, and tracking, in an efficient,
automated fashion. IBM
log of system changes should be kept. The simplest method is simply recording
the information in a data set or PDS member. This can be improved by using a
table (as provided by TSO/ISPF) or database management system (such as DB2)
where change information can be formatted into fields for easier querying,
searching, and updating. Ultimately one should investigate a change
management product, which will also add the ability to support the more formal
process activities, such as assessment, planning, and tracking, in an efficient,
automated fashion. IBM
′
s TME 10 Information Management includes such
functions, and allows change information to be updated and reviewed from a
wide choices of platforms besides TSO - even via an automation product such as
TME 10 NetView for OS/390.
wide choices of platforms besides TSO - even via an automation product such as
TME 10 NetView for OS/390.
One clear recommendation is that every system change, from system hardware
to application software, be recorded and retained for a reasonable period of time
-- at least a year. This will allow analysis of changes and discovery of any trends
that are occurring (for example, are their certain changes that always lead to
problems? If so, perhaps a better way to introduce those changes should be
investigated). In addition, peer review of planned changes to the system should
include review of the change control entries that document the change(s).
to application software, be recorded and retained for a reasonable period of time
-- at least a year. This will allow analysis of changes and discovery of any trends
that are occurring (for example, are their certain changes that always lead to
problems? If so, perhaps a better way to introduce those changes should be
investigated). In addition, peer review of planned changes to the system should
include review of the change control entries that document the change(s).
30.3 Problem Management
30.3.1 Overview
The Problem Management discipline is very closely related to Change
Management. When problems occur, either a change may be needed to fix the
problem and keep it from re-occurring, or a change was what caused the
problem in the first place. Managing problems is critical to achieve high levels of
application availability (which depends upon system and component availability).
Management. When problems occur, either a change may be needed to fix the
problem and keep it from re-occurring, or a change was what caused the
problem in the first place. Managing problems is critical to achieve high levels of
application availability (which depends upon system and component availability).
Problem resolution is often assisted because of the existence of change
management and problem management databases, showing previous instances
of the same or similar problems in one case, and changes that took place in the
system just before the problem occurred.
management and problem management databases, showing previous instances
of the same or similar problems in one case, and changes that took place in the
system just before the problem occurred.
Chapter 30. Systems Management Philosophy and Methodology
461