DPR - Disguise existing extract file

The DPR Disguise Existing Extract File screen shown in the following figure, is displayed when you select Option P, Privacy, from the Data Disguise Menu.

Use this screen to specify file information required for the disguise operation, then press Enter to display DPR: Data Privacy Specification where you add more Data Privacy information.

Hints

• Before you submit the disguise job, make sure that the Dynamic Privacy Rules (DPR) Project includes the desired disguise criteria for the objects included in the extract file.
• Also, when using disguise rules with complex criteria, the object that you used to define the criteria originally must be included (not excluded) in the extract file, or the disguise may not be successful.
• For related disguise rules, always define the criteria on the object that contains all of the different unique values to be extracted (including orphans).

DPR Disguise Existing Extract File

Specify Extract File Information

Enter the requested file information before viewing the JCL or submitting the disguise job:

Existing Extract File

Specify the name of the extract file that is to be disguised. This extract file cannot be a compressed file. Any existing extract file can be disguised, if it was created in the File-AID for IMSextract file format. An extract file can only be disguised once, that is, you cannot redisguise a disguised extract.

Member

If the existing extract file is a member of a partitioned dataset, specify the name of the member to be disguised. If this field is left blank or a pattern is entered, File-AID for IMS will display a member list pop-up. If a pattern is specified, only members matching the pattern are displayed. The only valid pattern character is an asterisk (*).

Volser

If the existing extract file is not catalogued, you must specify the volume serial number of the device where the file is located.

DBDLIB

Enter one or two DBD load library dataset names that contain the DBD describing the database that you want to disguise.

When two DBD libraries have been entered, File-AID for IMSsearches the first before the second to find the DBD entered. The DBD member entered must describe a Physical data base. Logical and Index DBD are not supported for the disguise function.

Segment/Layout XREF dataset

The XREF allows you to associate COBOL/PLI layouts with the various segment types in a DBD.

File-AID for IMS will display the DBD XREF Specification Panel before the Disguise Extract - JCL Specification panel.

The DBD XREF Specification Panel is where you can see which DBDs match the extracted objects to be disguised. You may add or update XREF Members as displayed.

COBOL/PLI Layout Datasets

When displaying segment data in formatted mode, File-AID for IMS uses the COBOL or PLI data field names obtained from Layouts in these data sets.

Primary Commands

The following primary commands are valid:

COBOL

Changes to display the segment data using the COBOL data field names.

PLI

Changes to display the segment data using the PLI data field names.

DPR: Data Privacy Specification

The DPR: Data Privacy Specification allows you to specify the DPR disguise information for disguising an existing Data Base Extract. As you had selected the Privacy option you need to specify the DPR repository and the name of the Dynamic Privacy Rules Project (see the following figure).

Use this screen to specify information required for the disguise operation, then press Enter to display Disguise-extract-JCL-specification to submit the batch job for disguise.

DPR: Data Privacy Specification

Specify DPR Information

DPR Repository Name

Specify the name of the repository to use for the Data Studio’s Data PrivacyDynamic Privacy Rules. The repository stores the Dynamic Privacy Rules Projects created with the Data Studio’s Data Privacycomponent of the Data Studio.

Specify the full repository name (up to 128 characters). Leave blank or enter an asterisk (*) by itself for a list of all available repositories. Then select the desired repository from the list (see Privacy Repository List Screen).

The Repository Name must be set properly, and will be used in combination with Dynamic Privacy Rules Project Name (see also Project name) throughout the rest of the product.

Project name

Specify the name of the Dynamic Privacy Rules Project to be used for this extract. Dynamic Privacy Rules are created with the Data Studio’s Data Privacycomponent of the Data Studio. The Dynamic Privacy Rules Project keeps track of how to apply the privacy rules to which extracted data element. This option requires installation of  BMC AMI DevX File-AID/Data Solutions and Data Studio’s Data Privacy.

Specify the full project name (up to 128 characters) or a pattern ending with an asterisk (*) for a list of matching projects. Asterisk (*) by itself lists all projects. Then select the desired project from the list (see Privacy Project List Screen). This is a scrollable field; position cursor on field and use LEFT, RIGHT or ZEXPAND to access field data.

Specify Disguise Information

Work File Prefix

The extract and disguise process creates various temporary or interim data files. This prefix provides an identifier for these files.

Create Audit Trail

Enter Y (for Yes) if you want an audit trail to be produced when the extracted data is disguised. Otherwise enter N (for No), and no audit trail will be produced. For more information about Audit Trails, see the section on Print Disguise Audit Trail.

Audit Trail Prefix

If you have requested that an audit trail be created, Enter a data set prefix for the batch job to use when creating the audit trail dataset name. Ordinarily your TSO userid will be added before whatever you specify for the prefix. So if you enter IXDG for the prefix, the data sets that are created will begin with USERID.IXDG. If you do not want your userid to be part of the data set names, be sure to enclose the prefix you enter in single quotes (apostrophes). Also note that if you have "tso profile noprefix" in effect, then the userid will not be used in the construction of the data set names. If you do not specify this parameter in such a way as to begin the data set names with your userid, be sure that you are authorized by your security system (e.g. RACF) to create data sets using the prefix you specify. For more information about Audit Trails, see the section on Print Disguise Audit Trail.

Use application relationships

Indicate whether application relationships are applied during the disguise process as they were applied during the extract.

Appl relationship dataset

Displays the application relationship data set concatenation that will be used during DPR disguise processing. For best results, this data set concatenation should be the same as the one used to create the extract. If this is not possible, make sure that all application relationships contained in the extract are defined in the data set concatenation specified on this panel. See also Application Relationship Data set Concatenation.

After specifying all DPR: Data Privacy Information to disguise an existing extract file, press Enter to continue with the Disguise-extract-JCL-specification.