DCF: disguise existing extract

The following panel is displayed when you select Option 2, Disguise, from the Data Privacy Menu.

Use this screen to specify information required for the disguise operation, 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.
• It is also recommended that the relationship information in both the extract and disguise control file matches.
• 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 (including orphans) to be extracted.

DCF: 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.

Any existing Extract File can be disguised; however, a 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. D050128.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.

DCF: Control File

Specify the Disguise Control File Name. The Disguise Control File determines what disguise criteria are applied to objects included in this extract. Required for Disguise Selection option 1.

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 DCF: 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 Disguise Control file. 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

Data Studio’s 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.

Redirect File-AID/Data Solutions Report

You can choose to redirect the disguise report output produced by File-AID/Data Solutions to FADSPRNT DD by simply adding it to the JCL. The FADSPRNT DD can point at a file or at SYSOUT. When it points at a file and multiple objects are being disguised, use DISP=MOD.

Since the use of FADSPRNT splits the File-AID/Data Solutions report output away from the File-AID/RDX report output, FADSPRNT and SYSPRINT must be looked at together to get a complete picture of the job.

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.