Scan CA VIEW Reports In CA DCD

To comply with data-protection regulations like the General Data Protection Regulation (GDPR), you can use CA DCD to locate reports in CA View which contain Personally Identifiable Information (PII).
view140
To comply with data-protection regulations like the General Data Protection Regulation (GDPR), you can use CA DCD to locate reports in CA View which contain Personally Identifiable Information (PII).
Follow these steps
:
  1. Use the CA View online interface to identify reports that you want to scan for PII.
    1. Use the retrieval facility to show a list of reports.
    2. Locate the SYSOUT ID for each report that you want to scan from the
      Sysout Selection List
      .
      If there are multiple versions of the report, you may also need to identify the generation (GEN), sequence number (SEQ), or both.
  2. Use the
    SARBCH
    utility to print each report to a sequential data set:
      • Example:
        Print A Single Report To A Sequential Data Set
        This example shows a sample JCL script to print a single report to a new sequential data set. The example uses the LOAD command, which generates raw text output and omits carriage-control characters.
        //EXAMPLE1 JOB ACCOUNT,PROGRAMMER //STEP1 EXEC PGM=SARBCH,PARM='VIEW.SYSTEM1' //STEPLIB DD DSN=CAI.CVDELOAD,DISP=SHR //DDNAME DD DSN=USER.REPORTS.R12345, // DISP=(NEW,CATLG,DELETE), // DCB=(RECFM=VB,LRECL=240,BLKSIZE=32670), // SPACE=(CYL,(20,10)), // UNIT=SYSDA //SYSPRINT DD SYSOUT=* //SYSIN DD * /LOAD DDNAME=DDNAME ID=R12345 /*
        where:
        • DDNAME=ddname
          specifies the DD definition of the output sequential dataset to which the report prints.
        • ID=id
          specifies the SYSOUT identifier of the report.
        You can optionally include
        SEQ=nnnnn
        , or
        GEN=nnnnn
        , or both parameters in the LOAD statement to specify further the GEN, SEQ number, or both, of the report. For the full syntax of the LOAD control statement, see Batch Processing (SARBCH).
      • Example:
        Print Multiple Reports To A Sequential Dataset
        This example shows sample a JCL script for printing multiple reports to new sequential data sets. The example uses the LOAD command, which generates raw text output and omits carriage-control characters.
        //EXAMPLE2 JOB ACCOUNT,PROGRAMMER //STEP1 EXEC PGM=SARBCH,PARM='VIEW.SYSTEM1' //STEPLIB DD DSN=CAI.CVDELOAD,DISP=SHR //DDNAME1 DD DSN=USER.REPORTS.DCDREP1, // DISP=(NEW,CATLG,DELETE), // DCB=(RECFM=VB,LRECL=240,BLKSIZE=32670), // SPACE=(CYL,(20,10)), // UNIT=SYSDA //DDNAME2 DD DSN=USER.REPORTS.DCDREP2, // DISP=(NEW,CATLG,DELETE), // DCB=(RECFM=VB,LRECL=240,BLKSIZE=32670), // SPACE=(CYL,(20,10)), // UNIT=SYSDA //DDNAME3 DD DSN=USER.REPORTS.DCDPAY, // DISP=(NEW,CATLG,DELETE), // DCB=(RECFM=VB,LRECL=240,BLKSIZE=32670), // SPACE=(CYL,(100,50)), // UNIT=SYSDA //SYSPRINT DD SYSOUT=* //SYSIN DD * /LOAD DDNAME=DDNAME1 ID=REP1 /LOAD DDNAME=DDNAME2 ID=REP2 /LOAD DDNAME=DDNAME3 ID=PAYROLL /*
        where:
        • DDNAME=ddname
          specifies the DD definition of the output sequential dataset to which the report prints.
        • ID=id
          specifies the SYSOUT identifier of the report.
        • You must specify a
          DDNAME
          for each dataset. Then, for each
          LOAD
          control statement, provide the
          DDNAME
          that matches the dataset to which the report prints.
        • Optionally, include the
          SEQ=nnnnn
          ,
          GEN=nnnnn
          , or both parameters in the
          LOAD
          statement. To review the full syntax for the
          LOAD
          control statement, see Batch Processing (SARBCH).
  3. Use CA DCD to scan the sequential data sets:
    1. Open the
      Scans
      page.
    2. Select
      Create a Scan
      .
      The Scan Wizard launches.
    3. Add all sequential data sets which contain the reports to scan on the
      Scan Includes
      page. Select
      Next
      .
    4. (Optional) Exclude data from the scan on the
      Scan Excludes
      page. Select
      Next
      .
    5. Specify what information to scan for in your reports on the
      Classifier Selection
      page. Select
      Next
      .
    6. (Optional) Refine the scan on the
      Classifier Refinement
      page. Select
      Next
      .
      • On the
        Word Boundary
        tab, specify the classifiers for which you require the word boundary check to be met.
      • On the
        Sequence Numbers
        tab, specify the classifiers for which the line sequence numbers should not be scanned. This helps to prevent false positives when the data set to which the report prints contains line numbers.
    7. (Optional) Specify whom to alert when the scan is complete on the
      Email Alerts
      page. Select
      Next
      .
    8. (Optional) Specify a name and a description for your scan on the
      Name and Description
      page.
    9. (Optional) Select
      Run scan immediately
      to run the scan immediately after a review. Select
      Next
      .
      If you do not select
      Run scan immediately
      , you can only save your scan and run it later.
    10. Verify that the scan configuration is correct on the
      Review
      page.
    11. Select
      Run Scan
      or
      Save Scan
      .
  4. Review your scan results.
    1. On the
      Scans
      page, select a scan.
    2. On the
      Scan Details
      page, select a data set under Data Source to see details for each classifier.
    3. On the
      Details for <data set>
      page, select a value under
      Rows with Matches
      for the
      Classifier
      that you want to review.
    4. On the
      Rows with Matches for <data set>
      page, review each match.
      Not every match represents a problem. For example, if you include
      birthdate
      as a classifier, and a report contains the date when it was last updated, then that occurrence registers as a match for the birthdate classifier, even though it is not an actual birth date.
  5. Remove the data sets that were created in step 2.
More information: