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. | |
Audit trail facility
File-AID for IMS/FLEX uses the existing File-AID for IMS audit trail facility. All update activity during a given execution can be captured in an audit trail dataset or SMF log file. Every change, delete, or insert performed causes the before and/or after image of the updated segments to be written to the audit trail dataset or SMF log file.
The audit trail facility is invoked by the presence of an IXPAT DD statement in the execution JCL (FLEX-JCL). The audit trail dataset can be either dynamically allocated or named by the user.
File-AID for IMS/FLEX will dynamically allocate the audit trail dataset at the beginning of the execution of the batch process if the following line of JCL is included in the batch job stream.
If your TSO-PREFIX matches your TSO-ID, the audit trail dataset name is
where... | equals... |
|---|---|
tso-id | Your TSO user ID, up to seven characters. |
yymmdd | The Gregorian date on which the audit trail is created. |
hhmmss | The hour, minute, and second the audit trail is created. |
If your TSO-PREFIX does not match your TSO-ID, the audit trail dataset name is:
where... | equals... |
|---|---|
tso-prefix | Your TSO user PREFIX, up to seven characters. |
If the audit trail dataset is specified in the JCL the data set must have the following attributes:
- RECFM=V or VB
- LRECL=a number greater than the longest segment to be written maximum concatenated key
- DSORG=PS
If DSORG=PO, a member must be included in the specification of the dataset name.
Notes on the Audit Trail Feature
The audit trail dataset that File-AID for IMS/FLEX creates is a sequential, variable blocked file. Its LRECL and BLKSIZE are dependent on the sum of the lengths of the longest segment type and the maximum fully concatenated key contained in the primary database being edited. The sum of these lengths cannot exceed 32,724.
When you use File-AID for IMS/FLEX to delete a parent segment that has dependent segments under it, File-AID for IMS issues a DL/I DLET call for the parent segment only. IMS automatically deletes all the dependent segments, in addition to the parent. Normally, File-AID for IMS/FLEX retrieves all the dependent segments and writes their images to the audit trail before the deletion of the parent actually occurs. This requires File-AID for IMS/FLEX to reestablish its current segment position in the database to the parent segment before deleting it.
When editing a database that contains nonkeyed and/or nonunique segment types, the capturing of deleted segment images by the audit trail feature can be affected. When the parent to be deleted is nonkeyed or nonunique, File-AID for IMS/FLEX is unable to reposition on the parent before deleting it. Therefore, File-AID for IMS/FLEX does not retrieve the dependents and write their images to the audit trail before deleting the parent. The dependent segments are deleted when the parent is deleted, but their images do not appear on the Audit Trail Report. A message appears on the report with the deleted parent's image to notify you that dependent segments were deleted but are not shown.
File-AID for IMS/FLEX provides your installation with the ability to force the creation of an audit trail during any user’s execution through a security exit routing. The process is especially useful if your installation wants to ensure that an audit trail is created whenever File-AID for IMS/FLEX is used to edit certain sensitive databases.
The security exit routine also has the capability to force the use of the system SMF log file to record the audit trail information.
If you require information on how your installation may be using a security exit routine to force audit trail creation and/or printing, contact the person responsible for File-AID for IMS/FLEX at your installation.
For more information on printing the Audit Trail, see File-AID for IMS/ISPF Reference.