To suppress unwanted items from a deployment analysis
report, use the FILTERDATASET parameter of the DEPLOY command to refer
to a filter file. A filter file is a sequential data set with a fixed-blocked
(FB) record format and a logical record length of 80 bytes. A filter
file contains plain text in a tabular layout: each line is a filter
statement that specifies criteria for report items you want to suppress.
For details, see the filter file supplied in member CCVX0007 of the
sample library SCCVSAMP.
If you specify the optional ddname CCVFLTEX in your report JCL, the job output includes a filter file that contains a filter statement for each item in the generated report. To suppress an item from future reports, copy and paste the corresponding filter statement from this file to your own filter file.
Filter statements in the CCVFLTEX filter file identify a specific, individual report item. Rather than copying these into your own filter file, you might want to review them, and specify generic filter statements (with patterns) instead.
For runtime resource definitions, filter statements in the CCVFLTEX filter file specify the APPLID value of the CICS® region from which the resource definition was collected. If you want these filter statements to apply in other situations, change this APPLID value to the generic pattern * (asterisk).
* Rpt Applid Code Text Name Type Group Comments
* --- -------- ---- --------- -------- ------------ -------- -------------------
DEP * **** All * * CEE LE
* Rpt Applid Code Text Name Type Group Comments
* --- -------- ---- --------- -------- ------------ -------- -------------------
DEP * 02** AI PROG * PROGRAM * Autoinstalled PROG
DEP * 0950 AI PROG * PROGRAM * Autoinstalled PROG
* Rpt Applid Code Text Name Type Group Comments
* --- -------- ---- --------- -------- ------------ -------- -------------------
DEP * 02** AI PROG * TERMINAL * Autoinstalled TERM
DEP * 0955 AI PROG * TERMINAL * Autoinstalled TERM
(In this 0955 filter statement, and in the similar 0950 filter statement for programs, above, specifying the TERMINAL or PROGRAM resource type is not strictly necessary, because the code is specific to that resource type.)