DPR: Disguise existing extract

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

Use this screen to specify information required for the disguise operation using BMC Compuware File-AID Data Privacy Dynamic Privacy Rules, then enter GO to submit the batch job for disguise.

Before you submit the disguise job, make sure that the Disguise Control File or the Dynamic Privacy Rules Project includes the desired disguise criteria for the objects included in the extract file.

DPR: Disguise Existing Extract

Enter the requested file information before viewing the JCL or submitting the disguise job with the GO command directly:

Extract File

Specify the name of the Extract File that is to be disguised. The extract file can also be a compressed extract file (see Compress).

If the Extract File is on tape, specify the name of the Extract Summary File instead of the name of the Extract File on tape. The Extract Summary File was created when the generated extract was saved to tape (see Specify Extract “TO” File Information). If your extract file on tape was created with an earlier release of File-AID/RDX than 4.8, create a summary file as described in Extract File Specification of Request-File-Member-List-panel-in-the-Load-function.

Only extract files created with File-AID/RDX Release 4.8 or higher can be disguised using Dynamic Privacy Rules.

An Extract File cannot be disguised more than once.

When you had requested an extract with disguise and the disguise step of that extract failed, or you had also set the option to save the pre-disguise records to a file in a masked format, you can enter the name of the pre-disguise Extract File here as the extract file to be disguised. You find the name of the pre-disguise file in the output of the extract job.

The name assigned to the pre-disguise extract file will use the standard File-AID/RDX routine to generate a "temporary" name. The name will be the user prefix, the mid-level qualifier from the Profile, the word "EXTRACT" and finally the current date and time fields (i.e. D120128.T055709).

Member

If the file you specified in Extract File is partitioned, you can enter a member name. If you leave this field blank or specify a pattern, File-AID/RDX displays a Member List pop-up containing a list of members that match the specified pattern. The only valid pattern character is an asterisk (*).

Disguised Extract File

Specify the name where the disguised extracted data is to be written. Make sure the size allocation is at least the same as the size of the extract file to be disguised. See also Size Allocation of Disguise Extract File.

When the specified disguised extract output is to tape or cartridge, File-AID/RDX automatically creates a summary file on DASD. The name of the summary file is the one specified in your profile or, if none is specified there, it is the name of the extract file with SUMMARY replacing the last node of the extract file name or a truncated form of SUMMARY as to not exceed 44 characters. If the summary file exists, File-AID/RDX will update (overwrite) its content. For more information, see Extract Summary File.

Member

If the file you specified in Disguised Extract File is partitioned, you can enter a member name. If you leave this field blank or specify a pattern, File-AID/RDX displays a Member List pop-up containing a list of members that match the specified pattern. The only valid pattern character is an asterisk (*). You can create new members by entering the name of the new member.

VOLSER

If the file specified in Disguised Extract File is non-cataloged or new, specify the volume serial number of the file. For non-cataloged files, a volume serial number is required. For new files, a volume serial number is optional.

Disposition

Specify the disposition of the disguise "to" file. You can extract to existing files with a disposition of OLD. Existing files must conform to the format outlined for the extract file in File-AID/RDX Extract File. Specify a disposition of NEW to create a new file.

If you specify NEW in the Disposition field, you must specify the following allocation parameters in the Create New File screen.

DPR: Repository Name

Specify the name of the Privacy Rules Repository to be used for this extract.

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

This field is prefilled with your current profile’s value (see DPR: Repository Name) or global default value (see Option G—Global User Defaults).

Project Name

Specify the name of the Dynamic Privacy Rules Project to be used for this extract. Dynamic Privacy Rules are created with the BMC Compuware File-AID Data Privacy component of the BMC Compuware Topaz Workbench. The Dynamic Privacy Rules Project keeps track of how to apply the privacy rules to which extracted data element.

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).

This field is prefilled with your current profile’s value (see DPR: Project Name).

Create Audit Trail

Specify whether an Audit Trail is to be created for each object being disguised. The Audit Trail will contain the before and after images of each record that was disguised.

N

No. Audit Trail datasets will not be created.

Y

Yes. File-AID/RDX creates a separate Audit Trail dataset for each disguised object. The naming convention for each Audit Trail dataset (Audit Trail File) is

prefix.RDXA.DnnnBnnn.Dyymmdd.Thhmmss.Msss

Audit Trail file prefix

Specify the prefix to be assigned to the Audit Trail dataset names. Prefix plus USERID can be up to 14 positions, the remainder of the data set name will follow the above mentioned naming convention. If prefix is blank, only the USERID will be used. Any value specified will be appended to the USERID. Precede the prefix value with a single quote (‘) to use the value without the USERID.

Primary Commands

The following primary commands are valid:

GO

Submit the batch job for disguise.

JCL

View the JCL generated for the disguise job prior to submitting the job with the SUBMIT command (see also View JCL).

View JCL

The ISPF/PDF Edit screen shown in the following figure is displayed when you enter the JCL command in the DPR: Disguise Existing Extract panel.

View File-AID/RDX generated JCL

Use this screen to view or edit the JCL generated by File-AID/RDX to disguise an existing extract file with predefined disguise criteria as specified in the Dynamic Privacy Rules Project. Use the SUBMIT command to submit the extract request for execution. If you want to save this JCL, use the ISPF/PDF CREATE or REPLACE command before you exit the panel.

XVJPRINT Execution Log Output

BMC Compuware File-AID Data Privacy jobs now write execution information to XVJPRINT DD (instead of SYSPRINT DD). If XVJPRINT DD does not exist in your JCL, File-AID will dynamically allocate XVJPRINT.

If you want the execution log output sent to a file, point XVJPRINT DD at a file (instead of SYSOUT=*). This file must be allocated with RECFM=FBA, LRECL=133.

Optional Data Privacy Report Output Written to a File

If you want the Data Privacy Report information written to a fixed layout sequential file and/or to a CSV (Comma Separated Values) file, manually add the appropriate DD statement to the BMC Compuware File-AID Data Privacy job.

DPRSTAT1 DD (Fixed Layout Sequential File)

When you add a DPRSTAT1 DD to a BMC Compuware File-AID Data Privacy job and it points at a file defined as RECFM=FB,LRECL=2737, at end of job, the file will have the report information for each column written out as a single record containing all the same report information but in a formatted fixed layout sequential file.

Example:

//DPRSTAT1 DD DSN=fixed_layout_sequential_file,
//            DISP=MOD

or for a new file:

//DPRSTAT1 DD DSN=fixed_layout_sequential_file,
//            DCB=(RECFM=FB,LRECL=2737,DSORG=PS),
//            SPACE=(TRK,(1,2),RLSE),
//            UNIT=SYSDA,
//            DISP=(NEW,CATLG,CATLG)

Record Layout for Output File

To view the output file in formatted mode you can use BMC Compuware File-AID/MVS Browse or Edit with the following COBOL record layout describing a record in the output file:

DPRSTAT2 DD (CSV)

When you add a DPRSTAT2 DD to a BMC Compuware File-AID Data Privacy job and it points at a CSV (Comma Separated Values) file defined as RECFM=VB,LRECL=2751, at end of job, the file will have the report information for each column written out as a single record containing all the same report information but they will be Comma Separated Value (CSV) records.

Example:

//DPRSTAT2 DD DSN=CSV_file,
//            DISP=MOD

or for a new file:

//DPRSTAT2 DD DSN=CSV_file,
//            DCB=(RECFM=VB,LRECL=2751,DSORG=PS),
//            SPACE=(TRK,(1,2),RLSE),
//            UNIT=SYSDA,
//            DISP=(NEW,CATLG,CATLG)

Optional Source Data Identifiers (SDIs) Override During Execution

File-AID/RDX now allows you to replace, during execution of a DPR project, Source Data Identifiers (SDIs) defined in the BMC Compuware File-AID Data Privacy project.

To override SDIs, manually add the following DD statement to the JCL:

//DPRSDI  DD    DISP=SHR,DSN=u.data.mysdis

where the existing data set u.data.mysdis contains the definitions of SDIs that will be used for this execution.

If the DPRSDI DD is defined in JCL, all SDIs defined in the project will be ignored and replaced with definitions provided in the override data set.

Override File Format

Replacement SDIs can be defined either in XML or in JSON format. The tags in XML and names in name/value pairs in JSON correspond to SDI properties that can be defined through the Compuware Workbench User Interface. Refer to the Source Data Identifier Overrides topic in the Compuware Workbench File-AID Data Privacy User Guide for more information.

Override Data Privacy Environment Parameters

If you need to, you can override the Data Privacy Environment parameters listed in the following table (established with your site’s BMC Compuware File-AID Data Privacy Environment parameters. For more information, see File-AID Data Privacy Environment.

 Data Privacy Environment Parameter Overrides

To do so, insert any of these FAJPATH, FAJOPTS, FAIPADDR, and FAEXPATH DD statements as needed. For example:

It is also possible to specify more than one debug parameter inline. For example:

Override Execution Parameter in a Data Privacy Project

In order to override an execution parameter (public variable or translate table) in a Data Privacy Project, add a DPRPARMS DD statement to your JCL. This DD can point to a file or a PDS member containing the override values (maximum record length is 512 bytes). The override values can also be specified inline. Specify override values in the following way:

executionParm=overrideValue

The execution parameter must have been defined in the BMC Compuware Topaz Workbench user interface for the project.

Example:

Your DPR project ‘project1’ includes:

• 2 translate tables, ‘Title table’ and ‘Titles for HR dept’ (Manage Translate Tables) 
  • The source table for ‘Title table’ is file ‘ABC.TRANS’.
• 2 public variables, ‘scramvar’ and ‘altscram‘ (Process Variables)
  • The initial value for ‘scramvar’ is string ‘123abc’.
• 2 execution parameters, ‘Parameter1’ identifies the translate table ‘Title table’ and ‘Param2Variable’ identifies variable ‘scramvar’ (Manage Execution Parameters)

At execution time, however, you want to override the defined execution parameters for translate table ‘Title table’ with the new translate table ‘ABC.NEWTRANS’ and the initial value of variable ‘altscram‘ with the new string ‘789xyz’. The new translate table must have the same characteristics as the original one.

To do so, insert the following DPRPARMS DD statement in the JCL (inline example):

Manage Translate Tables

Process Variables

Manage Execution Parameters

Execution Parameter List of Values

If the execution parameter variable type is either a String List or Numeric List, you can also override the list of values.

Specify a list of values in the following way:

executionParm=LIST(X)=overrideValueXoverrideValueXoverrideValue

The X variable inside the =LIST( )= parentheses defines the delimiter for the list of values. The delimiter can be any character. Connect each overridevalue with the defined delimiter.

For example, insert the following DPRPARMS DD statement in the JCL (inline example) to override the values of the String List named STATE (* is the defined delimiter):

Multiple Origins for a Data Privacy Rule

Normally, when a Data Privacy Rule is applied to a related field, one object¹ in the relationship thread is chosen as the “origin”. For every record in the origin, the Data Privacy Rule is applied to the related field and the BEFORE and AFTER values are saved. For every record in a “non-origin”, the Data Privacy Rule is not applied. Rather, the appropriate AFTER value is retrieved from where it was saved. This guarantees relationship integrity.

This methodology is efficient and sufficient in most scenarios, but there are some scenarios where no single origin contains all of the values required by the non-origins. When this occurs, it is possible to direct File-AID to use all objects that contain the necessary fields referenced by the Data Privacy Rule as origins. This directive is specified by adding to your JCL:

Special Instructions for Oracle Translate Table

If your Data Privacy job uses Data Translation with an Oracle Translate Table and your BMC Compuware File-AID Data Privacy Environment parameters do not include the following JAVA options (for more information, see File-AID Data Privacy Environment), insert the following FAJOPTS DD statement after the FARULES DD statement:

If the JAVA options in the BMC Compuware File-AID Data Privacy Environment parameters include other site specific JAVA options, also add them to the FAJOPTS DD statement before submitting the job.

Adding the above FAJOPTS DD statement will override the JAVA options in the BMC Compuware File-AID Data Privacy Environment parameters and make it possible to run an Oracle translation while the log will be generated in EBCDIC.

An indicator that you need to make this JCL change is when the Data Privacy job ended with the following error:

However, this general message is not conclusive. Your error log file should have something like the following:

If you see the above, then you need to insert the FAJOPTS DD statement.

Set Incomplete Disguise Continuation Indicator

When during the disguise process of an object, File-AID/RDX cannot disguise some records completely, File-AID/RDX, by default, issues a warning and removes these records from the disguised extract file. The resulting extract file might not be loadable or usable. Possible reasons for the incomplete disguise could be:

• Two related columns have unlike data types; error may be due to non-normalized data
• Error may be due to childless parents and/or orphans in your database

The disguise audit file for the object contains the before image for the offending records. Print it (see Print Disguise Audit Trail) so you can determine whether the discarded records are needed in your extract file.

The TEST parameter for the disguise (EXDISG) EXEC statement in the EXTPARMS data set (see EXTPARMS File) can be used to change the default behavior. When you set the parameter to Y, File-AID/RDX will issue a fatal error (RC=8) for this object instead of just discarding the incomplete disguise records. When set to N, File-AID/RDX will issue warning messages for incomplete disguise (RC=6) for an object, but continue disguise of object.

Control Card Cleanup

The last step, CLEANEXT, in the disguise jobs deletes the File-AID/RDX EXTPARMS parameter file. Whether step CLEANEXT is commented out or executed is determined by the global job option Delete in-stream data datasets at EOJ. If the job option is set to NO, File-AID/RDX EXTPARMS parameter files created in the extract jobs will NOT be deleted. Keeping the data sets until all steps run successfully allows for the restarting of the JCL at any step.

Periodically, you may want to manually delete the EXTPARMS parameter files that are no longer needed for saved jobs to be resubmitted.