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.

DBD tailoring in File-AID for IMS

File-AID for IMS uses three databases to store information created or used during execution. These databases are referred to as control databases. Two of the control databases are required and one is optional.

The LTM control database is required and is used to store information between transactions. It is updated as each transaction ends, before the screen is displayed. The other required control database is CLT, which contains static information about the user databases, including segment layouts. The CLT control database is updated primarily by the DBD Update and XREF Update batch programs. The use of these programs is described in the File-AID for IMS/CICS and File-AID for IMS/DC Reference manual.

The third control database is the optional AUD or Audit Trail control database. If you choose to use the Audit Trail feature of File-AID for IMS at your installation, the AUD database is used to capture the update activity processed against the databases you specify. It is not necessary to create the AUD control database if you choose not to use the Audit Trail feature at your installation.

All three control databases use the HDAM access method and IBM’s randomizing module DFSHDC40. There are two parameters that are input to this randomizing module that must be altered to your installation’s requirements—the Relative Block Number (RBN) and the Root Addressable Area size (BYTES). These parameters are specified in the RMNAME= keyword in the DBD statement for each of the three control database DBDs.

To calculate the RBN parameter for the LTM control database, multiply the estimated number of users who will be using File-AID for IMS (allow for growth) by 1.20. To calculate the RBN for the CLT control database, add the number of user databases to the number of layouts for the segments in those databases (allow for growth), and multiply this number by 1.20.

Calculate the RBN parameter for the AUD database as follows:

Decide how often you plan to extract and delete the Audit Trail database segments (by executing the XIXATEXT program as described in the File-AID for IMS/CICS and File-AID for IMS/DC Reference manual.
Estimate the typical total number of segment updates (inserts, repeats, deletes, and replaces of all database segment types) that will take place at your installation across all user databases where the Audit Trail feature will be active between the planned extraction and deletion of the Audit Trail database segments.
Divide the number of total updates by 16.

The resulting value is the RBN used for the AUD control database. For example, if you plan to extract and delete the segments from the Audit Trail database every two days and the daily segment updates total is estimated at 400, then the RBN is calculated as (2 * 400)/16 = 50.

Refer to the following table to determine the Bytes parameter. In the Maximum User DB Segment Length column, find the row that corresponds to your installation’s maximum user database segment length. Within this row, find the BYTES operand from the RMNAME Bytes column. Because the minimal SEGM bytes for the LTM and CLT databases is 8,158 bytes, use the data from row one if all your user databases have segment lengths less than 8,153 bytes. The same RMNAME bytes parameter must be used for both the CLT and LTM databases. Also, based on the row selected, use the corresponding CI/BLOCK value for the SIZE parameter in the DATASET statement in both control databases.

LTM and CLT Databases

Maximum User DB Segment Length	DBD Parameters		Data set Allocation		Buffer Used
Maximum User DB Segment Length	RMNAME Bytes	SEGM Bytes	CI/BLOCK	RECSZ
8,153 or less	8,177	8,158	8,192	8,185	8,192
12,249 or less	12,273	12,254	12,288	12,281	12,288
16,345 or less	16,369	16,350	16,384	16,377	16,384
20,441 or less	20,465	20,446	20,480	20,473	20,480
24,537 or less	24,561	24,542	24,576	24,569	24,576
28,633 or less	28,657	28,638	28,672	28,665	28,672
30,681 or less	30,705	30,688	30,720	30,713	30,720

To determine the BYTES parameter for the AUD database, you must first perform the following steps:

Determine the length of the longest user database segment whose updates will be captured by the Audit Trail feature. You can find this value specified for the BYTES= keyword on the SEGM statement that defines each user database segment type in the DBD source code for each database.
Determine the length of the longest fully concatenated key to a user database segment whose updates will be captured by the Audit Trail feature. One way to determine this value is to look for the largest KEYLEN= parameter value specified on a PCB statement within the PSBs that contain an Audit Trail database PCB.

Add the longest segment length value to the longest concatenated key value. Then, find the row that corresponds to the result in the Maximum User DB Segment Plus Concat Key Length column in the following table. Within this row, find the BYTES operand from the RMNAME Bytes column. Because the minimal SEGM bytes for the AUD database is 8,102 bytes, use the data from row one if the result you calculated is less than 8054 bytes. Also, based on the row selected, use the corresponding CI/BLOCK value for the SIZE parameter in the DATASET statement in the AUD database.

AUD Database

Maximum User DB Segment Plus Concat Key Length	DBD Parameters		Data set Allocation		Buffer Used
Maximum User DB Segment Plus Concat Key Length	RMNAME Bytes	SEGM Bytes	CI/BLOCK	RECSZ
8,054 or less	8,117	8,102	8,192	8,185	8,192
12,150 or less	12,213	12,198	12,288	12,281	12,288
16,246 or less	16,309	16,294	16,384	16,377	16,384
20,342 or less	20,405	20,390	20,480	20,473	20,480
24,438 or less	24,501	24,486	24,576	24,569	24,576
28,534 or less	28,597	28,582	28,672	28,665	28,672
30,582 or less	30,615	30,630	30,720	30,713	30,720

Further modifications to the control database DBDs are explained in Control Database DBD Changes.

Writer instructions

DBD tailoring in File-AID for IMS

On this page