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.

Miscellaneous Data Disguise Topics

This section provides information about the following topics:

Db2 Alias, Synonym, and View Support
Size Allocation of Disguise Extract File
Unlike Column/Field Data Types and Disguise Criteria
Data Disguise JCL

Db2 Alias, Synonym, and View Support

Disguise criteria can be defined for tables and views but not for alias and synonyms. Relationships cannot be created to an alias or a synonym but they can be used as the driving object in the extract and will be resolved to the base table. If disguise criteria are defined on a table and the table is extracted via an alias or a synonym, the disguise criteria defined on the table will be applied.

Views are treated as independent objects, just like tables. If disguise criteria are defined on a view, it will be applied only when the extract uses that view. If disguise criteria are defined on a table, they are applied when the extract uses that table name. If an extract uses a view on the table that has disguise criteria defined, it will not be applied; the criteria must be defined on the view for it to be applied. If a single table is extracted using different views, the disguise criteria will have to be defined on each view. There will not be any validation that the same column is disguised the same way in each view; it will be your responsibility to define criteria that will disguise the same data in the same way for each view and the base table.

Size Allocation of Disguise Extract File

Early in the disguise processing File-AID for Db2 compares the amount of space used in the undisguised extract file with the amount of space allocated to the output disguised extract file. If the disguised extract file is smaller than the amount of space used in the undisguised extract file, then the disguised extract file is reallocated before the disguise processing starts. Be aware that your site may limit this allocation request and issue a warning in that case.

Important

This reallocation is only available for sequential files (DSORG=PS) and does not occur for a PDS disguise extract file.

Unlike Column/Field Data Types and Disguise Criteria

File-AID for Db2 supports relationships between unlike columns/fields in application relationships (see also Column/Field Types Mapping). When a disguise rule is applied to a data column/field that is related to another column/field in a different format, then data conversion is required for the disguised value.

When complex disguise criteria are applied (and unlike column conversions are by definition complex disguise criteria), then the column of origin is disguised and both values are stored in a lookup table. When the data value from an unlike column is required to have the same value replaced, then that value is converted to the format of the origin, it is looked up in the disguise value table, the replacement value is retrieved, and the replacement value is then converted to the format of the current (non-origin) column.

Special Requirement for Numeric to Character Conversion

If the data at the origin is in character format, File-AID for Db2 will convert it in normalized format (see Normalized Format). So, in order for a match to occur, the original undisguised character data must be well-behaved and adhere to the same set of formatting rules used when File-AID for Db2 converts a number format to a character format. However, if the data at the origin is NOT in the Normalized Format, a match might not occur, resulting in a disguised extract file with broken relationships.

Hint

If possible, create your origin disguise criteria on the numeric field.

Normalized Format

Numeric data will be right justified and zero filled on the left. If it is related to decimal data, the decimal point must be explicitly filled in with the exact number of positions to the right of the decimal point. A minus sign, if needed, would be in the left-most character position. Note that character columns are subject to partial column use, so the above rules are relaxed to the extent that partial column definitions apply.

Data Disguise JCL

Depending on how you created the Extract File to be disguised File-AID for Db2 automatically generates the appropriate JCL through the online screens for disguise existing extract file and extracts with disguise.

The data disguise JCL shown in the following figure is generated for an Extract File created with Option 3.7.1 (RDX format, without Control Card Dataset).

Data Disguise JCL for an Extract File created with Option 3.7.1

XFREXEC is the File-AID program name. EXDISG is the name of Data Disguise EXEC statement. The parameter information in the PARM field in the EXEC statement must have the following format:

Table 25.EXEC Statement PARM Field—Disguise Extract Step (EXDISG)

Parameter	Default Value	Length	Description
Product	FD	2	File-AID for Db2
Option	F	1	File-AID option number: F - Data Disguise
Operating Mode	B	1	B - Batch

The following DD statements are required for data disguise:

DD Statements—Data Disguise

DD Statement	Description
STEPLIB	File-AID load libraries (SXVJLOAD and CXVJLOAD).
XVJPRINT	Output for data disguise report.
RDXMLIB	Library containing File-AID messages.
MSGLIB	Library containing File-AID/Data Solutions messages.
DISGEXT	File name of the disguised extract file.
EXTRACT	Pre-disguised extract file to be disguised.
DISGCTL	File name of the Disguise Control File (DCF).
DD01BR	File name of File-AID/Data Solutions business rules data set.
FARULES	Privacy Rules Repository name and Dynamic Privacy Rules Project ID.
AUDIT	Prefix for the File-AID/Data Solutions data disguise audit trail dataset name(s).
F2RPRINT	Dummy DD.

If your site requires special SMS information for the disguise split files, you can insert an SMSMODEL DD statement with a file name you want File-AID for Db2 to use as a model for the disguise split files (see the following figure). If no SMSMODEL DD is present, File-AID models SMS information on the file pointed to by the EXTRACT DD in the JCL.

If you want the SMSMODEL DD statement in all of your disguise jobs, you can edit skeleton member XFDJDISG in the File-AID SXVJSENU library.

SMSMODEL DD statement

File-AID will verify that the disguise extract data set referred to by the DISGEXT DD is at least the same size as the extract data set referred to by the EXTRACT DD. If the DISGEXT data set is smaller, messages DISG0030, DISG0070, and DISG0080 will print and the DISGEXT data set will be re-allocated automatically. If your site does not want the re-allocation to be attempted, add a X37DEACT DD statement to the EXDISG step as shown in the following figure to deactivate this feature.

If you want the X37DEACT DD statement in all of your disguise jobs, you can edit skeleton member XFRJDISG in the File-AID SXVJSENU library.

X37DEACT DD statement

The data disguise JCL shown in the following figure is generated for a legacy Extract File created with Option 3.7.3 (with Control Card Dataset).

Data Disguise JCL for a legacy Extract File created with Option 3.7.3

//UTIL EXEC PGM=IKJEFT01,DYNAMNBR=80,REGION=8192K,COND=(7,LT)
//*-------------------------------------------------------------------
//* Custom JCL imbedded in skeletons F2DGEXST,F2EXTR,F2EXTLOD,F2EXTLDI
//*-------------------------------------------------------------------
//* NOTE: If the Data Solutions datasets were not specified at install
//* time you will need to supply them in this JCL. Or have the
//* installer complete the install with Data Solutions datasets.
//*-------------------------------------------------------------------
//STEPLIB DD DISP=SHR,
// DSN=hlq.CXVJLOAD
// DISP=SHR,
// DSN=hlq.SXVJLOAD
// DISP=SHR,
// DD DSN=DSNA10.DA01.SDSNEXIT,
// DISP=SHR
// DD DISP=SHR,
// DSN=DSNA10.SDSNLOAD
// DD DISP=SHR,
// DSN=hlq.SXVJLOAD
//DALLIB DD DISP=SHR,
// DSN=hlq.SXVJLOAD
//MSGLIB DD DISP=SHR,
// DSN=hlq.SXVJMENU
//*
//ISPPLIB DD DISP=SHR,
// DSN=ISP.SISPPENU
// DD DISP=SHR,
// DSN=hlq.SXVJPENU
//*
//ISPMLIB DD DISP=SHR,
// DSN=hlq.SXVJMENU
// DD DISP=SHR,
// DSN=ISP.SISPMENU
//*
//ISPSLIB DD DISP=SHR,
// DSN=ISP.SISPSENU
// DD DISP=SHR,
// DSN=hlq.SXVJSENU
//*
//ISPTLIB DD DISP=SHR,
// DSN=hlq.SXVJTENU
// DD DISP=SHR,
//*
//ISPPROF DD DSN=&BATPROF,DISP=(NEW,DELETE,DELETE),
// DCB=(BLKSIZE=3120,LRECL=80,DSORG=PO,RECFM=FB),
// SPACE=(TRK,(1,,1)),UNIT=SYSDA
//*
//SYSPRINT DD SYSOUT=(*)
//SYSTSPRT DD SYSOUT=(*)
//SYSTERM DD SYSOUT=(*)
//SYSOUT DD SYSOUT=(*)
//*
//EDSNAME DD DISP=OLD,
// DSN=TSOID01.FDSAMP.EXTRPDS5(EMP3)
//CTEDSNME DD DISP=OLD,
// DSN=TSOID01.EMP.CTRL
//*
//DGEXFILE DD DISP=OLD,
// DSN=TSOID01.FDSAMP.EXTRPDS5(EMP3)
//*
//F2DSGCTL DD DISP=OLD,
// DSN=TSOID01.FRSAMP.DISGUISE
//SYSTSIN DD *
ISPSTART PGM(F2DGEXST) NEWAPPL(FD48)
/*
//PARM DD *
F2SSID DSN
FIPLAN FDA10N25
CURSQLID FDDBA
LOCATION
C#CREAT1 DBQA
C#TABLE1 EMP
AUDROWS *
DSNQUAL EMP
/*
//AUDIT DD *
audit-file-name-prefix
/*

The following DD statements are required for data disguise:

DD Statements—Data Disguise

DD Statement	Description
ISPMLIB	ISPF Message Libraries
ISPTLIB	ISPF Table Libraries
ISPSLIB	ISPF Skeleton Libraries
ISPPLIB	ISPF Panel Libraries.
ISPLLIB	Load Libraries.
STEPLIB	File-AID load libraries (SXVJLOAD and CXVJLOAD).
DALLIB	File-AID load libraries (SXVJLOAD and CXVJLOAD).
MSGLIB	File-AID Message Library.
EDSNAME	File name of the disguised extract file.
F2DSGCTL	File name of the Disguise Control File.
DD01BR	File name of File-AID/Data Solutions business rules data set.
CTEDS	File-AID for Db2 Load Control Card dataset.
SYSIN	Select statement for the object being extracted.
AUDIT	Prefix for the File-AID/Data Solutions audit trail dataset name(s).

F2DGEXST is the File-AID for Db2 program name for the Data Disguise EXEC statement. The parameter information in the PARM DD in the EXEC statement must have the following format:

EXEC Statement PARM DD—Disguise Extract

Parameter	Length	Description
F2SSID	4	Current subsystem identification of your Db2 system.
FIPLAN	8	Current plan identification.
CURSQLID	7	Current SQL identification.
LOCATION		Location identification of your Db2 subsystem.
C#CREAT1		Table creator. Depending on the Length of the Creator name there could be a C#CREAT2 and C#CREAT3.
C#TABLE1		Table or object name. Depending on the length of the table name, there could be a C#TABLE2 and C#TABLE3.
AUDROWS		Provides the maximum number of rows being extracted to File-AID/Data Solutions. so Data Solutions can allocate the Audit Trail Report file.
DSNQUAL		Used in the Audit Trail Dataset name, if an audit trail was requested.

Return Codes

An execution return code (RC) appears in the output listing. For return codes other than 0, an error code and message indicating the specific problem also appear in the listing. In general, the return codes can be summarized as follows:

Return Code	Description
0	Job ran to completion.
4	Job ran to completion, warnings issued that criteria is not found for that object.
12	Severe error, job aborted.

Batch JCL from Previous Releases

Migrating JCL for disguising a legacy extract file created with Option 3.7.3 from File-AID for Db2 Release 6.3 to Release 21.01 requires removing the File-AID/Common Components (VJ) load libraries CXVJAUTH and SXVJAUTH. See sample JCL in View File-AID for DB2 generated JCL for a legacy extract file created with Option 3.7.3.