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. When should I use a space announcement banner? Use the space organization announcement after you change the content from a book-like organization (such as User Manual, Configuration Manual, and Administration Guide) to the product model. Use the latest version announcement to push traffic to later versions. You do not need to add this to every previous version, but if you have a specific reason that you want users to be aware—for example, Google searches show content for an obsolete version—use the banner to help users find a relevant version. When an announcement is no longer needed, remove the BMC Space Banner macro.

Maintaining File-AID for IMS/CICS

Control Database DBD Changes

A database reorganization must be done whenever the DBDs used by the control databases change after the initial installation. This need can be caused by space requirement, randomizer, maximum segment size, data set organization, device type, or IMS version changes. The following steps must be taken to reorganize a changed database:

Unload the database that uses the existing DBD. Use the JCL available at your installation or the JCL in sample member hlq.SXVJSAMP(XIXNULOD).
Incorporate the changes into the DBD.
Regenerate the DBD control block (For more information, see Generate DBD Control Blocks in Customizing-File-AID-for-IMS-CICS).
Regenerate the ACB (For more information, see Generate ACB Control Blocks in Customizing-File-AID-for-IMS-CICS).
Delete and reallocate the data set, if necessary, by using the JCL in sample member hlq.SXVJSAMP(XIXNDDFO) for OSAM databases or sample member hlq.SXVJSAMP(XIXNDDFV) for VSAM databases.
Reload the database with the new DBD. Use the JCL available at your installation or the JCL in sample member hlq.SXVJSAMP(XIXNRELD).

Control Database Segment Size Changes

If the segment size requirements of a control database need to be changed to support your database, it is indicated by message D609. Within this message is a value that is the minimum required control database segment size needed to support the DBD in question.

When changing the DBD to reflect this new control database segment length, use the appropriate table provided in DBD Tailoring. In that table, the Segm Bytes column displays the recommended values for the segment length. Choose the next highest value greater than the size displayed in the message to ensure that your DBD will be supported by File-AID. Use the other values in that row in the table for the remaining control database DBD values. Remember that the LTM and CLT control databases must use the same maximum segment length (SEGM BYTES) and root addressable area size (RMNAME BYTES).

Aside from the above mentioned requirements, the procedure to change the size of the control database segments is the same as described in Control Database DBD Changes above.

Security Exit Added or Changed

If your installation is adding a new security exit program or changing an existing one, it must be linked again into File-AID’s main load module.

For more information, see Security Exit (Optional) in Customizing-File-AID-for-IMS-CICS.

Control Segment Missing or Invalid

A segment on the CLT control database stores various counts and fields used to verify the database’s integrity. If this segment is inadvertently updated or deleted, it must be rebuilt to ensure accurate processing of your databases. The Rebuild Control Segment program (XIXREBLD) reads the File-AID database, calculates and accumulates control field information for each segment, and inserts or replaces the new control segment.

You need to run XIXREBLD when any of the following conditions occur:

An abend screen is displayed with message number D204:
File-AID IS MISSING ITS CONTROL SEGMENT

An abend screen is displayed with message number D205:
File-AID’s CONTROL SEGMENT CONTAINS INVALID DBD DATA

The Batch XREF Update program terminates with a return code of 8. The summary report prints the message:
ONLINE CONTROL INFORMATION SEGMENT NOT FOUND. IF DBD UPDATE FACILITY HAS NEVER BEEN RUN, RUN IT FIRST. OTHERWISE, RUN MAINTENANCE UTILITY TO REBUILD CONTROL INFORMATION SEGMENT

The Rebuild Control Segment program can be run as a batch or shared database program.

Parameters

The parameters on the PROC statement assign default values to symbolic parameters on the procedure statement. To override a default parameter value on the PROC statement, code the same parameter on the EXEC statement that calls the procedure.

The parameters in sample members hlq.SXVJSAMP(XIXNRBLD) and hlq.SXVJSAMP(XIXNRBLB) specify the sysout class, load libraries, and data set names used when the program executes. These are described in DD Statements.

Change the default LE Runtime library from CEE.SCEERUN to your LE370 Runtime library.

The DFSRRC00 parameters are the batch IMS execution time parameters.

DD Statements

The following table contains the DD statements that define the primary processing files required to run the Rebuild Control Segment program.

Rebuild Control Segment Program DD Statements

DD Statement	Description
STEPLIB	Designates the IMS system data set that contains the IMS nucleus, required action modules (&RESLIB), and the library where File-AID for IMS/ISPF load modules are stored (&CXVJLOAD and &SXVJLOAD).
DFSRESLB	XIXNRBLD PROC only. Designates the IMS system data set that contains the IMS nucleus and required action modules (&RESLIB).
DFHLIB	XIXNRBLB PROC only. Designates the CICS system data set that contains the batch region controller modules.
IMS	XIXNRBLD PROC only. Designates the IMS system data sets that contain the database description blocks (&DBDLIB) and the program specification blocks (&PSBLIB).
DFSVSAMP	XIXNRBLD PROC only. Designates the data set (&PROCLIB) and member (&DFVSAM) that contain the control statements that describe the size and structure of the VSAM shared resource pool for File-AID’ CLT database. The buffers must be large enough to accept the largest segment size in the CLT database.
SYSUDUMP	A dump of user areas if the program abends. The dump is formatted so that it can be printed directly.
IEFRDER	XIXNRBLD PROC only. Designates the log data set when update intent is declared.
IXCCLTDD	XIXNRBLD PROC only. Designates the File-AID’ control database (&IXPDB) that is updated with DBD information.
IXPD1	Designates the DBD load library that contains the DBD load modules that define the databases used to update the CLT database. Multiple DBD load libraries can be concatenated.
IXPMLIB	Designates the library that contains File-AID for IMS messages.
SYSOUT	Designates the output class for the Online Control Information Update Summary Report.

XIXREBLD Return Codes

An execution return code (RC) for hlq.SXVJSAMP(XIXREBLD) appears in the output listing. A message appears on the Online Control Information Update Summary Report for return code 16 (system error).

The message listed on the Online Control Information Update Summary Report indicates the program’s execution status.

Online Control Information Update Summary Report

Back-up and Restore Control Databases

The JCL sample members referred to, are found in hlq.SXVJSAMP.

A back-up and recovery plan should be developed at your installation to allow recovery from physical damage to the control databases. The CLT control database contains a large amount of information that is difficult to recreate in the event the database becomes unusable. The LTM control database, which contains temporary data used only for the duration of a terminal session, is easier to reestablish. The AUD control database may contain Audit Trail activity that has not yet been extracted by running the XIXATEXT program. Therefore, your installation could lose valuable Audit Trail information.

A job is provided in sample JCL member XIXNICPY to create image copies of the CLT and AUD databases. You can use it or other JCL available at your installation for periodic back-ups. To restore the CLT and AUD databases from the image copies, use the job in installation JCL member XIXNRSTR or other JCL available at your installation.

If your CLT and AUD control databases are VSAM files, they must be deleted and redefined before beginning the restore process. Use the job in installation JCL member XIXNDDFV for this purpose.

No back-up or restore JCL is provided for the LTM database. To repair a damaged LTM control database that is a VSAM file, delete and redefine it with the job in installation JCL member XIXNDDFV. For OSAM files this step can be skipped. Then, initialize the database with the job in JCL member XIXNLTMI.

For more information, see Batch-update-facility-in-File-AID-for-IMS-CICS-or-File-AID-for-IMS-DC.