Miscellaneous data privacy topics (using DCF)

See the BMC AMI DevX Workbench Data Privacy User Guide documentation for information on the corresponding topics for using BMC AMI DevX Data Studio's Data Privacy.

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.

VSAM PATH support for disguise

A relationship cannot be established to a VSAM AIX or PATH. An extract that specifies an AIX as the driving object will process the AIX as a single, standalone object; it will not extract the base object or the objects related to the base object. Extracting via a PATH is not supported. Defining disguise criteria on an AIX or PATH is not supported. If disguise criteria is defined on the base object, that criteria is not applied.

Size allocation of disguise extract file

Early in the disguise processing File-AID/RDX 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.

Unlike column/field data types and disguise criteria

File-AID/RDX 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 Consideration for Numeric to Character Conversion

If the data at the origin is in numeric format (SMALLINT, INTEGER, DEC, or FIXPIC) and the character field is in a non-normalized format, the resulting disguised value in the character field will be normalized (see Normalized Format). If it is desired that the character field remain non-normalized, use the character field when creating your disguise criteria.

If the number of digits in the character field is greater than the number of digits that can fit into the non-origin, related numeric field (SMALLINT, INTEGER, DEC, or FIXPIC), then you need to use a partial column relationship to identify the digits in the character field that do fit. For more information on how to create a partial column relationship, see Extended Column Relationship Definition.

Normalized Format

Numeric data will be right justified and zero filled on the left when converted to character. If the origin has a non-zero scale, i.e. digits to the right of the decimal point, the decimal point will be explicitly filled in with the appropriate number of positions to its right. A minus sign, if needed, will be in the left-most character position.

Data privacy JCL

The data privacy JCL shown in the following figure performs the batch portion of the disguise process and generates the appropriate reports. File-AID/RDX automatically generates the JCL through the online screens for disguise existing extract file and extracts with disguise.

Data Privacy JCL

XFREXEC is the File-AID/RDX 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:

EXEC Statement PARM Field—Disguise Extract Step (EXDISG)

The following DD statements are required for data disguise:

DD Statements—Data Disguise

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/RDX to use as a model for the disguise split files (see the following figure). If no SMSMODEL DD is present, File-AID/RDX 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 XFRJDISG in the File-AID SXVJSENU library.

SMSMODEL DD statement

File-AID/RDX 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

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: