DCF disguise existing extract file


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

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

Hints

  • Before you submit the disguise job, make sure that the Disguise Control File (DCF) 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 should match.
  • 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).

DCF Disguise Existing Extract File

 File-AID for IMS  ----------  DCF Disguise Existing Extract File  ---------------
 OPTION ===>                                                                     
 ENV: TEST - IMS ENVIRONMENT                                                  

 Specify Extract File Information:                                               
     Existing Extract file  . . . 'TSOID01.FISAMP.UNLOAD'                        
                    Member  . . .        (Blank or pattern for member list)     
                    Volser  . . .    Password  . . . .    
                                                
        + DBDLIB Dataset 1  . . . 'CW.FISAMP.DBDLIB'        
                 Dataset 2  . . . 'IX.IMSVS.DBDLIB'                        
                 Member . . . . . PORDR   (Blank or pattern for member list)     

  + Segment/Layout XREF Dataset .         

   + COBOL Layout Dataset 1 . . . 'TSOID01.FISAMP.COBOLLIB'      
                  Dataset 2 . . . 'CW.FISAMP.COBOLLIB'

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 IMSwill 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 data set names that contain the DBD describing the database that you want to disguise.

When two DBD libraries have been entered, File-AID for IMS searches 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 Segment/Layout XREF allows you to associate COBOL/PLI layouts with the various segment types in a DBD.

COBOL/PLI layout datasets

When displaying segment data in formatted mode, File-AID for IMSuses 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.

DCF: Data Privacy Specification

The DCF: Data Privacy Specification allows you to specify disguise information for disguising an existing Data Base Extract using the Disguise Control File as shown in following image.

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.

DCF: Data Privacy Specification

File-AID for IMS --------------  DCF: Data Privacy Specification  -------------
COMMAND ===>                                                          
                                                                     
Specify DCF for Extract File:                                         
                                                                     
  DCF: Control File  . . . . .'TSOID01.DISGUISE.CONTROL'    

Specify Disguise Information:                                         
  Work File Prefix . . . . . . TSOID01.WORKFILE  
                                                                     
  Create Audit Trail . . . . . Y          (Y = Yes; N = No)    
  Audit Trail Prefix . . . . . TSOID01.IXDGF                      
                                                                     
                                                                     
Press ENTER to continue

Select DCF for Extract File

DCF: Control File

Identify the Disguise Control File (DCF) to be used to disguise the extract file specified on the previous panel.

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.

Important

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. This is also true for Audit Trail Prefix below.

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.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*