Writer instructions | ||
Purpose | Use this page to display a banner announcement on each page of the space. Create the Space announcements page in the master space, outside of the Home branch. You can version the Space announcements page to enable different banners to be published into different target spaces, however, the banner that is displayed in the versioned (master) space itself only displays the most recently-published banner. If you find errors in the banner area of your versioned space and you are sure the Space announcements page is set up correctly, try publishing the page to the same space. For more information, see Space-announcements-banners. | |
Removing | When an announcement is no longer needed, remove the BMC Space Banner macro. | |
Translation | Localized spaces using the L10n Viewport theme must change the name of this page to Space announcements l10n. See Configuring-the-Scroll-ViewPort-theme-for-translated-spaces. | |
Usage | Choose one or none of the following BMC Space Banner macros. If your space requires another kind of announcement, you can use this page in coordination with your team lead and editors. |
RECOVERY (edit only)
The RECOVERY command helps you minimize the number of database updates lost due to a system failure.
RECOVERY ON causes File-AID for IMS/ISPF to issue a DL/I checkpoint call after every n database update calls. When a checkpoint call is made, DL/I writes all its changed database buffers, which forces all updated segments to be written to the database datasets.
RECOVERY OFF prevents File-AID for IMS/ISPF from automatically issuing any checkpoint calls. Therefore, DL/I writes its buffers only when they are full.
If you enter the RECOVERY command without any operands, the default is ON and the checkpoint interval n is set to one. If you enter a checkpoint interval, it can range from 1 to 2,147,483,647.
When initially entering the Database Location screen, File-AID for IMS/ISPF sets RECOVERY OFF. RECOVERY remains off throughout the editing session unless you turn it on with the RECOVERY command.
See here for information on how the RECOVERY command is affected by nonkeyed and nonunique segments.