gtps4m0k | System Generation |
Once the new system is operational, it must be maintained, whether it is a
test system or a production system. APAR fixes (normally distributed
via PTF tapes) need to be applied on a continual basis and application
programs and database records may require updating on the same basis.
System modifications are normally done in 1052 state. It is highly
recommended that all changes be first validated in a test system prior to
putting them in an operational system. The following facilities may be
used to aid in this effort:
- Alter file and alter core operator commands.
- New pilot system records may be loaded at any time in 1052 state.
- The general file loader enables the loading of new versions of the
resident control program, start-up program segments, keypoints, and/or E-type
(real-time) programs. It utilizes both offline and online segments plus
a loader general file. Figure 8 describes the entire program maintenance process when it is
utilized.
- The E-type loader enables loading of new programs or new versions of
existing programs in any system state.
- The auxiliary loader enables the loading of the same types of programs as
does the system loader described above but operates in 1052 state or above and
does not require the use of a loader general file and its associated
IPL. The new programs are passed to the online system via tape
input.
- Multiple TPF image support allows user's to perform system loads in
NORM state without destroying the existing program base, and to immediately
switch a processor to a previous program base without requiring a loader
general file IPL.
For more information about these facilities, see TPF
System Installation Support Reference.
Figure 8. Program Maintenance Overview