IBM OS/390 User Manual
•
Places a stronger emphasis on service, as it promotes keeping one
′
s
″
eye
on the ball.
″
•
Provides more effective and productive processes.
Challenges in this approach are not just to segment the activities, but also to
recognize how the disciplines interrelate and how they cross functional
boundaries. Also, all responsibilities must be assigned and understood, and
disciplines documented.
recognize how the disciplines interrelate and how they cross functional
boundaries. Also, all responsibilities must be assigned and understood, and
disciplines documented.
30.1.2 Systems Management Scope - What Needs to be Managed?
In almost all systems, hardware (at the mainframe site, anyway) is reasonably
controlled. As our systems become networks of autonomous users who can
control their own configuration and setup, it is possible for an end user to
destroy his or her own ability to interact with the host and other server systems.
In some cases, they can also impact the connections and services to other
users.
controlled. As our systems become networks of autonomous users who can
control their own configuration and setup, it is possible for an end user to
destroy his or her own ability to interact with the host and other server systems.
In some cases, they can also impact the connections and services to other
users.
Host operating system and subsystem software (0S/390, ACF/VTAM, CICS/ESA,
DB2) similarly have a relatively small group of people who control and manage
their attributes and status. In the new OS/390 environment, however, it is likely
that the number of people responsible for these components could be larger
than is typical in computer systems running VSE/ESA or VM/VSE. In addition,
problems and changes in one component may affect other components and
workloads. Because of the increase in number of people who control these
components, it is recommended to implement Systems Management in a way
that all the systems support personnel will be aware of planned and completed
management activities. In addition, this process permits the implementation of
peer review of planned activities, which both catches errors and educates other
staff members in the various Systems Management disciplines.
DB2) similarly have a relatively small group of people who control and manage
their attributes and status. In the new OS/390 environment, however, it is likely
that the number of people responsible for these components could be larger
than is typical in computer systems running VSE/ESA or VM/VSE. In addition,
problems and changes in one component may affect other components and
workloads. Because of the increase in number of people who control these
components, it is recommended to implement Systems Management in a way
that all the systems support personnel will be aware of planned and completed
management activities. In addition, this process permits the implementation of
peer review of planned activities, which both catches errors and educates other
staff members in the various Systems Management disciplines.
Application program software is likely to be impacted with higher volumes during
an 0S/390 migration in several areas. For one example, it is likely that
application source programs will be changed (from DOS/VS COBOL to COBOL
for MVS, and VSE assembler macros to OS/390 macros). Much of this will be
automated, but because of new language nuances, program maintenance and
development will require more effort, at least to begin with. Systems
Management disciplines such as change and operations management can help
reduce this extra effort by avoiding rediscovery, identifying reasons for failure,
and more. Change management will help control JCL changes, application setup
and run instructions, and more. Operations management will invoke and
monitor the applications, provide for problem bypass, and provide feedback for
any further changes to be made.
an 0S/390 migration in several areas. For one example, it is likely that
application source programs will be changed (from DOS/VS COBOL to COBOL
for MVS, and VSE assembler macros to OS/390 macros). Much of this will be
automated, but because of new language nuances, program maintenance and
development will require more effort, at least to begin with. Systems
Management disciplines such as change and operations management can help
reduce this extra effort by avoiding rediscovery, identifying reasons for failure,
and more. Change management will help control JCL changes, application setup
and run instructions, and more. Operations management will invoke and
monitor the applications, provide for problem bypass, and provide feedback for
any further changes to be made.
Overall, then, you should realize more benefits by extending the scope of your
implementation of systems management disciplines all the way from hardware
configuration and setup on one end to application programming and JCL on the
other end. Whether the discipline being applied is Change Management,
Problem Management, Performance Management, Operations Management,
Security Management, or others, the most benefit can be derived when the
scope for the discipline covers the system.
implementation of systems management disciplines all the way from hardware
configuration and setup on one end to application programming and JCL on the
other end. Whether the discipline being applied is Change Management,
Problem Management, Performance Management, Operations Management,
Security Management, or others, the most benefit can be derived when the
scope for the discipline covers the system.
The disciplines should also include the network elements (we will define network
as anything on the non-mainframe side of a communications controller); the
availability of the workloads to the users will depend upon those elements as
as anything on the non-mainframe side of a communications controller); the
availability of the workloads to the users will depend upon those elements as
Chapter 30. Systems Management Philosophy and Methodology
459