22.12.2012 Views

z/TPF Program Management - IBM

z/TPF Program Management - IBM

z/TPF Program Management - IBM

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Alternate FCTB loader benefits<br />

Use the alternate FACE table (FCTB) loader to perform the following tasks:<br />

v Modify your database without a scheduled outage. This includes:<br />

– Removing deactivated pool extents<br />

– Expanding the number of tracks and cylinders<br />

– Removing or reduce the number of ordinals in fixed file records<br />

– Changing the physical location of records types<br />

– Changing the file address reference format (FARF) address for fixed-file<br />

records.<br />

Attention: Do not use the alternate FCTB loader to modify records that are<br />

critical to the z/<strong>TPF</strong> system or unexpected results can occur.<br />

See “Alternate FCTB compatibility checking” on page 31 and Table 2 on page 31<br />

for more information about using an alternate FCTB.<br />

v Activate an alternate FCTB on all processors or any specific processor.<br />

v Use the ufct.c user exit to customize compatibility checking for the alternate<br />

FCTB and the existing database. See “Alternate FCTB compatibility checking” on<br />

page 31 for more information about how to ensure that a valid alternate FCTB is<br />

loaded.<br />

v Use the uftz.c user exit to maintain a log of alternate FCTB activity.<br />

Alternate FCTB loader programming considerations<br />

The following lists the programming considerations for the alternate FACE table<br />

(FCTB) loader:<br />

30 z/<strong>TPF</strong> <strong>Program</strong> <strong>Management</strong><br />

v A maximum of one alternate FCTB and one base FCTB can be loaded for each<br />

z/<strong>TPF</strong> image.<br />

v If you use the ZFCTB ACCEPT command to accept an alternate FCTB that is<br />

active, that alternate FCTB becomes the base FCTB; no other FCTB exists.<br />

v You must delete or accept the existing alternate FCTB to load another alternate<br />

FCTB.<br />

v The FCTBCLEAR parameter on the @DEFINE control statement specifies if an<br />

existing alternate FCTB on a z/<strong>TPF</strong> image is cleared or left intact when an initial<br />

program load (IPL) is performed on the z/<strong>TPF</strong> image. See z/<strong>TPF</strong> <strong>Program</strong><br />

<strong>Management</strong> for more information about the FCTBCLEAR parameter on the<br />

@DEFINE control statement.<br />

v You can display the status of an alternate FCTB by using the ZIMAG DISPLAY<br />

IMAGE command. See z/<strong>TPF</strong> Operations for more information about the ZIMAG<br />

DISPLAY IMAGE command and displaying the status of an alternate FCTB.<br />

v If you perform a hard IPL and an active alternate FCTB exists, you will be<br />

prompted in the IPLB program to specify the base FCTB or the alternate FCTB.<br />

If the base FCTB is specified, the alternate FCTB is deactivated. This allows you<br />

to prevent looping errors that result from an alternate FCTB that is not valid.<br />

When a soft IPL is performed, this option is not available.<br />

v The offline loader (<strong>TPF</strong>LDR) creates the input medium that contains the alternate<br />

FCTB used by the ZFCTB LOAD command. If there are items on the input<br />

medium other than an FCTB, the ZFCTB LOAD command is rejected.<br />

v The alternate FCTB loader is not supported from image 1 to prevent interference<br />

with the general file loader. See z/<strong>TPF</strong> <strong>Program</strong> <strong>Management</strong> for more<br />

information about the general file loader.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!