gtpm1m36 | TPF V4R1 Migration Guide: 3.1 to 4.1 |
In the TPF 3.1 system, testing changes to a TPF system required
bringing down the system, scheduling planned downtime for system loads, and
re-IPLing the loader general file for fallback.
In the TPF 4.1 system, multiple TPF images allow you to integrate
changes in a TPF environment by:
- Performing loads in NORM state without destroying your existing program
base
- Falling back immediately to a previous program base with a single IPL
without re-IPLing your loader general file.
Multiple TPF images allow you to have up to 8 images. One primary
image is designated for use during a hard initial program load (IPL).
Each image has:
- A unique core image restart (CIMR) area
- A pointer to an IPL area (IPLA and IPLB)
- A pointer to a program base
- Its own keypoint load staging are to facilitate the pre-loading of
keypoints in NORM state.
You can define up to 8 images (CIMR and keypoint staging area), up to 8
program bases, and up to 4 IPL areas.
You can run different images on separate processors in a loosely coupled
complex as long as the system structures, including the FCTB and RIAT, are
compatible.
When you IPL the loader general file (LGF), the
online general file loader (ACPL) writes the loaded system components to image
1. The auxiliary loader (TLDR) writes loaded system components for the
other images. TLDR now supports output to general data sets
(GDSs) tape, user-defined media, and virtual reader.
- Note:
- Virtual reader refers to the IBM VM/ESA facility for supplying input to a
virtual machine. A full load must be done when you are loading to an
image using a new program base.
Keypoint X (CTKX) no longer exists as a keypoint. CTKX is the
image-unique image pointer record that contains information about keypoints
and CIMR components.
The following two CIMR components
are no longer supported:
The APTV and CGOT components are replaced by two user-defined CIMR
components:
- USR1, which is subsystem shared
- USR2, which is subsystem unique.
New Keypoint CTK5 occupies the slot vacated by Keypoint CTKX. This
keypoint is reserved for IBM use.
See TPF System Installation Support Reference for
more information about how to use multiple TPF images.
The ZIMAG command allows you to modify and display images and their
components. See Modifying and Displaying Multiple TPF Images for more information about this command. Also see
TPF Operations for a complete description of the
ZIMAG command.
The new ZIMAG command allows you to define, delete, modify, display, and
manipulate components of TPF images.
- DEFINE
- Allows you to define (or redefine) up to 8 images.
- DISPLAY IMAGE
- Displays the image name, status, associated IPL and program areas, CTKX
version code (if physically loaded), and CIMR component.
- ENABLE
- Allows you to enable an image for an IPL.
- PRIMARY
- Defines an enabled image as the primary image. The primary image is
used during a hard IPL and is valid only on the basic subsystem (BSS).
- DISABLE
- Disables an enabled image so that it cannot be IPLed.
- CLEAR
- Deletes a disabled image.
- COPY
- Allows you to copy core image restart area (CIMR) components from one
image to another by reference (logically) or physically.
New options were added to the COPY parameter that enable you to copy the
IPL and program areas between the source and target images.
- UNREF
- Deletes the logical references of CIMR components from a disabled
image.
- MAKEPHYS
- Allows you to make all of your CIMR component references physical
copies.
- DISPLAY PROG
- Displays all of the program areas defined in the TPF 4.1 system and
identifies which (if any) images they are associated with.
- DISPLAY IPL
- Displays all the IPL areas that were loaded and identifies which (if any)
images they are associated with. This option also displays IPLA and
IPLB information for each area.
- DISPLAY PROCESSOR
- Displays the image associated with each processor in the complex, as well
as the status of the processor.
You can use the keypoint staging area to store copies of keypoints
that you want to test. When you activate these keypoints (by moving
them to the working area and IPLing), a backup copy of the working keypoints
is saved for fallback purposes. Therefore, at one time, you could have
the following copies of the keypoints:
- Working keypoints, which are used by all of the processors in
a complex, regardless of which images are active
- Keypoints that were loaded to some or all of the staging areas
- Backup keypoints.
Although the staging area keypoints are image-unique, the working keypoints
and backup keypoints are not.
The following options for the ZIMAG KEYPT command let you manipulate these
keypoints.
- MOVE
- Allows you to move keypoints from the keypoint staging area of an image to
the working keypoint area.
- RESTORE
- Allows you to move the backup copy of the keypoints to the working
keypoint area (keypoint recover). All processors, other than the one
for which the command was issued, must be in STOP state.
- CONT
- Required after a KEYPT MOVE or RESTORE (to allow the MOVE or RESTORE to
continue after you have determined that the processors are in the required
states).
- ABORT
- Ends the KEYPT MOVE or RESTORE.
- DELETE
- Enables you to remove keypoints from the keypoint backup area.
Enter the command with this option before a KEYPT MOVE if there are
backup copies of the keypoints that you want to move.
- DISPLAY
- Displays working (active) storage area or backup keypoints.
se the ZTPLD command to load program data to an image from tape, general
data set (GDS), user-defined media, or virtual reader. See TPF Operations for a complete description of the ZTPLD
command.