Includes conceptual and procedural information to use product reports.
CA ACF2 reports and utilities must be run on a system on which CA ACF2 is installed. Otherwise, necessary modules might not be available for the reports or utilities to complete successfully.
Required Access for Executing Report Generators
To run report generators that process data from the CA ACF2 databases that are related to logonids or UIDs, users must have the appropriate privilege levels (that is, SECURITY, ACCOUNT, AUDIT, LEADER, or CONSULT) or users must have read access through CA ACF2 access rules to all input data sets. Such data sets include live or backup SMF data sets or live or backup CA ACF2 databases. Your site should carefully select the subset of its user community to be granted access to SMF data sets. CA ACF2 SMF records contain database record images that are used in the database recovery process and might contain sensitive data about the site.
Restricting Access to Report Data
To restrict unauthorized users from viewing SMF data, you can write access rules. Some users might have to see some of the SMF records, but not all of them. For example, in a decentralized security environment without the use of program pathing facilities and the GSO OPTS record RPTSCOPE option, a user who has access to SMF data can read and manipulate SMF records for a broader range of data than is desirable. With the correct implementation of program pathing and the use of the RPTSCOPE option, only those users with specific authorizations and privileges can access the SMF data that they are authorized to see. Any SMF data that does not match a user's particular privileges and restrictions cannot be viewed. By specifying RPTSCOPE and restricting access to the SMF data through program pathing, for example, a scoped security officer can view only SMF data for which he is scoped. A scoped security officer is a logonid with the SECURITY privilege that has a scope record that is assigned in the SCPLIST field of the logonid record. The scope record is used to limit the information that the user can access. For more information, see Scope Records.
To limit the range of SMF data a privileged user can view, specify the global RPTSCOPE option in the GSO OPTS record. Depending on the report, RPTSCOPE forces different privileges and restrictions to be validated. These privileges and restrictions determine the range of records that the logonid submitting the report is authorized to view. If you specify the RPTSCOPE option, tell users who run CA ACF2 reports that the range of data they are viewing might be more limited than what they might otherwise see. The default is NORPTSCOPE, which bypasses authorization checking during report creation.
RPTSCOPE affects the output of any report or utility using SMF for input (including ACFRPTPP). The privileges and authorities of the logonid that submits the batch job limits the output. If the user processes the reports on TSO and RPTSCOPE is set, the output reflects the privileges and authorities of the logonid that is signed onto the session. If your site always requires unscoped report output, do not specify RPTSCOPE.
To implement program pathed access rules for SMF data sets, specify the report utilities as the PGM parameter value in the access rule to allow access to SMF data. The library where the report utility resides should also be specified as a value in the LIB parameter of this access rule. Access to SMF is then restricted only to an authorized user executing the report utilities and only to that SMF data that matches the user's privileges and restrictions.
Running Reports through ISPF Panels
Use the CA ACF2 ISPF panels to execute a report generator online and display the results at the terminal screen.
Contact system maintenance personnel for information about the availability and use of ISPF. Before proceeding, familiarize yourself with the execution requirements of the report programs as documented. For further instructions on entering the parameters and specifying files, press PF1 to view a tutorial.
To select a report generator for execution
  1. Type ISPF at the TSO READY mode.
  2. Type A for the ISPF Option Selection Menu displays.
  3. Select 4 for the CA ACF2 Report Program Processor Menu displays.
    If you have to run a series of reports, run the ACFRPTPP report utility first. Then run other report generators from the data collected and separated by ACFRPTPP.
  4. Type the appropriate number to select the desired report.
    A panel displays allowing you to type parameters for the report generator. For example, type 0 to choose the CA ACF2 SMF Record Preprocessor.
Using Sample JCL to Execute Reports
CA ACF2 provides a prototype JCL procedure. This JCL is stored in the REPORTS member of the CAI.ACF2.CAIJCL data set at your site. Modify this JCL or create your own JCL for regular use. Each individual report generator, provides information for modifying or creating the REPORTS JCL and executing the report generators.
If you are using the CA Earl facility for CA ACF2 reports, sample JCL is found in the EARLRUN member of the CAI.ACF2.CAIJCL data set.
Functions of the REPORTS JCL
The sample REPORTS JCL, or a user-written substitute for that job stream, performs the following functions:
Separates each subtype of SMF record into its own intermediate file. The ACFRPTPP utility performs this operation. Afterwards, each report generator can access the appropriate intermediate file that is created by ACFRPTPP. The parameters that you select, such as SDATE, STIME, or JOBMASK, can further refine which SMF records are contained in the intermediate file.
Sorts each intermediate file of SMF records. Your site's SORT utility program performs this operation. Each intermediate file can be sorted according to intended use.
Runs the report generators. All CA ACF2 report generators are reentrant and run in a 128K region. However, some report generators require a slightly larger region size, depending upon the number of SMF records processed. Requirements are highlighted in the individual descriptions of the report generators.
You are not required to run the ACFRPTPP (the SMF preprocessor utility). All report generators can run as stand-alone programs using SMF data that has not been preprocessed.
If you must sort the SMF data, we recommend using ACFRPTPP to move those records of the subtype to be sorted into an intermediate file. In addition, the preprocessor improves the efficiency of report generation. After you run the ACFRPTPP utility, the report generators read only the records that are processed instead of all the records in the SMF file.
The following report generators do not depend on SMF data because they use the CA ACF2 databases as input. These generators are not affected by the use of the ACFRPTPP utility:
  • ACFRPTSL (unless the ACFRPTSL report parameter SMF is specified)
Input and Output Files for Report Generators
The ddname and description of the input and output files common to most CA ACF2 report generators follows.
Input files contain SMF records that your site collects and maintains. The CA ACF2 report generators use these files for input. These files must have ddnames beginning with the characters
as in the following example:
In the supplied JCL, these files provide input for the ACFRPTPP utility program, which creates intermediate files for input to each of the report generators. The REC
files are either VSAM or non-VSAM. REC
files cannot be concatenated.
When Running z/OS 1.9 and higher, SMF data may alternatively be sent to the LOGGER services which is controlling the write of the SMF data in LOGSTREAM structures. The SMF data is no longer recorded in the usual SYS1.MANx data sets.
The CA ACF2 utilities is able to read data under the following conditions:
  • The LOGR services needs to be active on the system with the definitions that contain the SMF data.
  • A LOGR subsystem needs to be active on the system and an IEFSSNxx member needs to be defined and activated at IPL time with the following definition:
    The RECxxxxx DD used to read the data has the following format :
    //RECxxxxx DD DSN=IFASMF.DATA.LOGSTRM,DISP=SHR, // SUBSYS=(LOGR,IFASEXIT, // 'subsys-options1','subsys-options2')
    Description of SUBSYS options-1 includes the following:
    [FROM={({[yyyy/ddd][,hh:mm[:ss]] }) | OLDEST}] [TO={({[yyyy/ddd][,hh:mm[:ss]] }) | YOUNGEST}] [,DURATION=(nnnn,HOURS)] [,VIEW={ACTIVE|ALL|INACTIVE}] [,GMT|LOCAL]
    The subsys-options1 parameters used by the IBM IFASEXIT are the same as those used by the IFBSEXIT. A complete explanation of parameters for IFBSEXIT can be found in the z/OS 1.9 and higher IBM documentation
    MVS Diagnosis: Tools and Service Aids.
    Description of SUBSYS options-2 includes the following:
    A specific SMFID can be provided to limit the records retrieved to a cpuid when the LOGSTREAM is defined to gather SMF data from multiple CPU's. SUBSYS options1 and options2 are positional. During the batch process if you pass subsys-options1, two commas must be coded between IFASEXIT and subsys-options2.
SYSIN is a file that lets you specify parameters to CA ACF2 report generators using the PARM field on a JCL EXEC statement. The SYSIN file lets you specify a set of parameters that exceeds 100 characters.
The SYSIN file is defined in one of the following formats:
  • F
    -the last eight characters of each record are assumed to be a sequence number and are ignored.
  • VB
    -the first eight characters are assumed to be the sequence field and are ignored.
Use the TSO EDIT command to create a SYSIN file like this:
All records in the SYSIN file are assumed to be an extension of the JCL EXEC statement PARM field. Any parameter value specified in a record is continued in the next record in the file. A dash (-) as the last nonblank character of a record indicates a continuation in the next record. The contents of the next record are concatenated to the preceding record at the position of the dash; the dash itself is omitted. The concatenated parameter includes all blanks preceding the dash continuation character and all blanks at the beginning of the continuation record.
SYSPRINT is a file that specifies where the report output is sent. Output is directed to a printer or to a listing data set. The record format is VBA. Specification of the BLKSIZE parameter is optional; the default is 3665.
Report generator output is generally 80 characters wide for most reports. This width permits convenient report browsing on an 80-character display screen. Some reports have a wider format for use with printer-directed output. To find out the maximum record length for each format, see the explanation of each report generator.
SYSPRINT is referred to as OUTPUT LIST NAME on the ISPF report generator panels.
SMF Input Records for Report Generators
SMF record numbers identify the input records for the various CA ACF2 report generators. One record number (default of 230) includes all CA ACF2 record types. A subtype indicator identifies the record type.
When you run combined reports for CA ACF2 for VM and CA ACF2 for z/OS on your systems, be aware that SMF records written under CA ACF2 for VM before r3.3 have a unique record number for each CA ACF2 record type. To run reports that include SMF records created before CA ACF2 for VM r3.3, specify the site-default SMF record numbers in the CA ACF2 Field Definition Record (ACFFDR) as long as your z/OS system does not use these numbers for other purposes.
If the ACFFDR module is not available through linklist, STEPLIB, or JOBLIB, specify the SMF record numbers using the report generator's SELECT parameter. If you specify a record number through the SELECT parameter of a report generator and also want to select records with the SMF record number, specify the SMF record number (default of 230) in the SELECT parameter. For example, enter the following for the ACFRPTLL report:
Report Generator Sort Sequence
The prototype JCL provided in CAI.ACF2.CAIJCL(REPORTS) sorts the records in several CA ACF2 SMF record subtypes to provide more meaningful reports. You can modify the JCL to customize the reports. The sort sequences provided with the prototype JCL are explained for each report generator.
Some reports, such as the database update journals, do not require sorting steps; the input for these utilities usually is generated in chronological sequence. Use a sort step to ensure that records are in date and time-stamp sequence, particularly if you are processing multiple SMF files.
Common Parameters and Descriptions
Specify parameters for CA ACF2 report generators using one of these methods:
  • The PARM parameter of the EXEC statement in the JCL. For example:
    // 'MASK(SYS1.-)','SDATE(091170)','EDATE(091174)')
  • A SYSIN file. Supply a SYSIN DD statement and control record file as previously explained in Input and Output Files for Report Generators.
To represent a literal string of text delimited by single quotes as part of an EXEC PARM, use two single quotes. For example:
PARM=('IF(PREFIX NE ''********'')')
Parameter Descriptions
The following parameters operate the same for most report generators.
All parameters are shown in the notation used to execute JCL. If you are using ISPF panels to execute reports, omit the brackets.
Specifies that records appearing on the report are limited to those for the job indicated by the job name mask. Use commas or spaces to separate multiple job name masks. The default is all jobs.
[TITLE(first 35 characters of PARM parameter1|string)]
Specifies a one- to 35-character string added to other title information at the top of the report. When you do not specify this parameter, the report generator uses the first 35 characters in the PARM field of the EXEC statement as the title. When this character string is longer than 35 characters, the report generator uses only the first 35 characters as the title.
The LINECNT parameter specifies the number of output lines to be printed on a page. To prevent splitting information, CA ACF2 report generators that issue multiple line reports check whether a complete report item will fit on a page. The maximum number of output lines per page is limited only by the physical constraints of the output media used, or to 99,999 lines.
Specifies the beginning Julian date from which report information is selected. The standard "0" bit is used for the 1900 century. The year must be past 69, for example, 1970-1999. If the century bit is set to "1" and the year is 69 or less, it is considered 2000 and above. Any input SMF records generated before the SDATE value are ignored.
Specifies the ending Julian date from which report information is selected. The standard "0" bit is used for the 1900 century. The year must be past 69, for example, 1970-1999. If the century bit is set to "1" and the year is 69 or less, it is considered 2000 and above.
When combined with the SDATE parameter, this parameter creates a window for report content. The defaults for SDATE and EDATE process all available records.
Specifies the beginning-of-time interval from which SMF records are selected based on a 24-hour clock. SMF records generated before this specified time of day are ignored. The selection of records begins at the STIME specified for each date in the SDATE/EDATE range and ends on each date at the ETIME given.
Specifies the end-of-time interval from which SMF records are selected based on a 24-hour clock. SMF records generated after this specified time of day are ignored.
[SELECT(number defined in @SMF macro|
nnn nnn...nnn
Defines the SMF record numbers used by CA ACF2. Generally, this parameter is not necessary because the report generators extract the proper record numbers from the ACFFDR of the running system. However, if CA ACF2 is not available in the running system, or if your site changed the SMF record numbers, you must supply the proper record numbers.
CA ACF2 processes all SMF records using a single record number. To process SMF records, specify the record number in the SELECT parameter. (This record number is defined in the CA ACF2 parameter of the @SMF macro in the ACFFDR.)
To process SMF data generated under CA ACF2 for VM with CA ACF2 SMF data, specify the SMF record numbers required by the particular report. Before CA ACF2 for VM r3.3, a different record number existed for each CA ACF2 record type. Each record number is specified by the appropriate record-type parameter in the @SMF macro of the ACFFDR that was active when the record was generated. Specify the single record number for CA ACF2 for z/OS with those record numbers used by CA ACF2 for VM.
The NOSELECT parameter specifies no selection of records based on SMF record numbers or CA ACF2 subtypes. All records satisfying the other specified parameters (SDATE, STIME, SYSID, and so forth) are processed. Specify this parameter only when your input files contain records that have been preprocessed by the ACFRPTPP utility and selected especially for the report generator you want to execute. Otherwise, use of this parameter might lead to unpredictable results, such as abends or meaningless report output.
Specifies the CA ACF2 system ID active when the SMF records in question were generated. You can specify a single system ID or a system ID mask. You cannot specify multiple masks or a series of IDs. The default is all systems.
Causes all selected SMF records to be printed in hexadecimal dump format. This parameter option is provided primarily for diagnostic purposes.
Specifies the desired format of the time stamp printed in report: the default M = HH.MM, S = HH.MM.SS, H = HH.MM.SS.TH.
Specifies the condition code the report program will return if the report is empty. This is a BATCH only parameter. The Condition code value may be any decimal value in the range 0 to 4095.
Sample Parameters
Parameters common to all ACF2 reports include:
[TITLE(first 35 characters of PARM parameter|string)]
Running Other Utilities
You can run other utilities through JCL, ISPF panels, and by executing the TSO CALL command. These are described in the following sections.
Using JCL to Execute Other Utilities
There are sample JCL job streams available for executing other CA ACF2 utility programs. Submit these job steps as individual jobs or combine them to form larger, more comprehensive jobs. See the individual description of the particular CA ACF2 utility for an explanation of all input and output files.
Using ISPF Panels to Run Other Utilities
CA ACF2 provides ISPF panels for the ACFDEL, ACFBSYNC, and ACFCLEAN utilities. Contact the appropriate systems maintenance personnel at your site for information on the availability and use of ISPF.
Before executing ACFDEL or ACFBSYNC using the ISPF panels, review their batch execution requirements as documented. For a short tutorial about ACFDEL, ACFBSYNC and ACFCLEAN, press F1 when viewing the CA ACF2 Utility Processor Menu.
To select an CA ACF2 utility for execution
  • Type ISPF at the TSO READY mode. (Check with your site for the exact command syntax.)
    The ISPF Primary Selection Menu displays.
  • Type the appropriate selection code (usually A).
    The ISPF Option Selection Menu displays.
  • Type 5 to display the CA ACF2 Utility Processor Menu.
  • Enter 1, 2, or 3 to select the desired utility.
    The appropriate panel displays.
  • Enter parameters for the batch program.
Executing the TSO CALL Command
You can execute the CA ACF2 utilities by first creating a CLIST data set containing the CALL and other necessary commands for executing the utility. In doing so, be aware of the following:
  • You can specify the parameters for the utility as CALL parameter operands.
  • You can specify parameters in a SYSIN file. Specify a dash in single quotes
    ('-') as the last nonblank character in the CALL program parameter.
  • When you specify a dash as the last nonblank character of the CALL program parameter and do not allocate a SYSIN file, CA ACF2 prompts you for input through the terminal. Each input prompt consists of the last two characters of the report generator name followed by a question mark.
Executing Reports When CA ACF2 is Inactive
All CA ACF2 report generators except ACFRPTRX and ACFRPTXR execute without CA ACF2 active on the system. If the ACFFDR module, used when CA ACF2 is active, is available through the LOAD macro, the default SMF record number is retrieved from the ACFFDR.
If the ACFFDR is not available, you must specify the SMF record number (or numbers). An authorized user can run the report generators ACFRPTCR, ACFRPTDS, ACFRPTEL, ACFRPTJL, ACFRPTLL, ACFRPTNV, ACFRPTPW, ACFRPTRL, and ACFRPTRV by specifying the SELECT report parameter with the appropriate SMF record numbers.
If CA ACF2 is not active, ACFRPTSL uses the CA ACF2 sequential logonid backup file or an SMF file as input. If an SMF file is used, specify the appropriate logonid SMF record number in the SELECT parameter. For more information, see ACFRPTSL--Selected Logonid List.
You can execute ACFRPTXR when CA ACF2 is not active. Use the ACFRECVR utility and create a set of VSAM clusters from the CA ACF2 sequential backup files. After creating the required VSAM clusters, point ACFRPTXR to these files and execute the program. For more information, see Database Recovery.
Running Online Reports Using SMF Data Extracted from LOGSTREAM Structure
To retrieve SMF data from a LOGSTREAM, type Y next to the Logstream Report field located in each report's main panel.
Panel Parameters
The following are panel parameters located on the LOGSTREAM Information Collection panel:
When specified, it will limit the data retrieved from the LOGSTREAM to a specific CPUid.
Specify the subsystem defined in the IEFSSNxx member to activate the LOGR subsystem. When not provided, a default LOGR is assumed.
Specify the subsystem exit that will be used to format the SMF records retrieved by LOGR in the SMF LOGSTREAM structure. When not provided a default IFASEXIT is assumed.
Mutually exclusive with the FDATE and FTIME fields, specify O for OLDEST to retrieve the LOGSTREAM data starting from the oldest date still recorded.
Mutually exclusive with FROM, specify a starting date (CYYDDD) to retrieve the LOGSTREAM record from.
Mutually exclusive with FROM, specify a starting time (HHMMSS) to retrieve the LOGSTREAM record from.
Mutually exclusive with the TDATE and TTIME fields, specify Y for YOUNGEST to retrieve the LOGSTREAM data up to the last written data block.
Mutually exclusive with TO, specify an ending date (CYYDDD) to retrieve the LOGSTREAM data blocks up to. The high limit of the TDATE is 142259.
Mutually exclusive with TO, specify an ending time (HHMMSS) to retrieve the LOGSTREAM data blocks up to.
Mutually exclusive with FROM, TO, FDATE, FTIME, TDATE, TTIME. Requests the data from the last nnnn hours up to the youngest block of LOGSTREAM data to be returned.
Indicate if the time provided in FDATE-FTIME TDATE-TTIME parameters in expressed in Local or GMT time.
Indicate, the complete (F), inactive (I) or active (A) portion of the LOGSTREAM records is being returned.
  • System logger maintains two types of log stream data in a log stream: active and inactive portion. The active portion of the log stream is the log data that the log stream owner has not logically deleted through an IXGDELET request. The inactive portion of the log stream is the log data that the log stream owner has logically deleted but has not yet been physically deleted from the log stream because the retention period (RETPD) specified for the log stream has not yet expired.
  • SMF is the owner of the LOGSTREAM, CA ACF2 is just a player (write/read smf data through smf services) and therefore may not issue delete requests. SMF is maintaining the logstream through standard utilities as explained in the SMF manual.
Specify the LOGSTREAM structure or dasdonly names that will be dynamically allocated as input to the ACFRPTxx reports to retrieve the SMF records.
Create a CA ACF2 Report
Use the following ddnames for the input/output files that are common to most CA ACF2 reports. See the following specific reports for additional files:
  • RECxxxxx (input files containing SMF records)
  • SYSIN (input file containing additional parameters)
  • SYSPRINT (output file)
Specify the following parameters in either or both of the following ways:
Through the PARM parameter of the EXEC statement in the JCL:
Through the SYSIN file:
Using Parameters Specific to Each Report
Optional parameters specific to each report include:
ACFRPTCR -- TSO Command Statistics Log
[BUFFER|NOBUFFER] [MASK(********|logonidmask)] [UID( |uidmask)] [UPPER|NOUPPER] [COND(4|n)] [TIME(M|S|H)]
[SUMMARY|DETAIL] [EXCLUDE(nnnnnnnn,...,nnnnnnnn|********)] [INCLUDE(nnnnnnnn,...,nnnnnnnn|********)] [COND(4|n)] [TIME(M|S|H)]
ACFRPTDS -- Data Set/Program Event Log
Optional File: HEXDUMP
[NLIDMASK(logonid mask,...,logonid mask)] [MASK( |datasetmask)] [NMASK(datasetmask)] [LIDMASK(********|logonidmask)] [NLIDMASK(logonidmask)] [UID( |uidmask)] [SIZE(2500|nnnnn)] {SHORT] [LOGGING|VIO|TRACE|PGMNAME|TAPE|INSTALL|UNKNOWN|ALL] [PRINTER|SUMMARY|TERMINAL] [EXTEND|NOEXTEND] [COND(4|n)] [TIME(M|S|H)]
ACFRTPEL -- Infostorage Update Log
[SUMMARY|DETAIL] [UID( |uidmask)] [MASK(********|logonidmask)] [TYPE{ |typemask)] [CLASS(R|class)] [COND(4|n)] [TIME(M|S|H)]
ACFRPTIX -- Data Set Index Report
Optional File: DETAIL
[DETAIL|NODETAIL] [PREFIX(********|mask)] [SELLID(ACFFDR @SMF LID|nn,...,nn)] [SELRULE(ACFFDR @SMF RULE|nn,...,nn)] [COND(4|n)] [TIME(M|S|H)]
ACFRPTJL -- Restricted Logonid Job Log or JOBFROM Job Log Report
[MASK(********|logonidmask)] [SMASK(********|submitterlogonidmask)] [JOBFROM] [COND(4|n)] [TIME(M|S|H)]
ACFRPTLL -- Logonid Modification Log
[SUMMARY|DETAIL] [MASK(********|logonidmask)] [UPDATE|NOUPDATE] [LIDFLDS(nnnnnnnn,...,nnnnnnnn | ********)] [CHANGER(changermask | ********)] [COND(4|n)] [TIME(M|S|H)]
ACFRPTNV -- The Environment Report
Optional Files: DISK, TAPE, or VSAM
[CPUID(****|cpuidmask)] [DBLSPC|NODBLSPC] [HEADER] [TRACE] [COND(4|n)] [TIME(M|S|H)]
ACFRPTOM -- Open Edition MVS Report
[SUMMARY|DETAIL] [UID(value)] [GID(value)] [USER(logonid)] [GROUP(groupname)] [SERVICE(service)|{INCLUDE(service,...,service)}{EXCLUDE(service,...,service)}]
ACFRPTPP -- The Preprocessor
[MASK(********|logonidmask)] [SMFxx(nnn,...,nnn)] [SMF$x(nnn,...,nnn)] [SMFxxxxx(nnn|x,nnn|x,"description")] [SELECT(nnn,...,nnn)]
ACFRPTPW -- Invalid Password/Authority Log
[MASK(********|logonidmask)] [COND(4|n)] [TIME(M|S|H)]
ACFRPTRL -- Rule ID Modification Log
[SUMMARY|DETAIL] [MASK(********|rulemask)] [COND(4|n)] [TIME(M|S|H)]
ACFRPTRV -- Resource Event Log
[LOG|VIO|TRACE|ALL] [MASK(********|rulemask)] [PRINTER] [TYPE(***|typemask)] [UID( |uidmask)] [SUMMARY|DETAIL] [CLASS(R|class)] [COND(4|n)] [TIME(M|S|H)]
ACFRPTRX -- The Logonid Access Report
[ACF2|NOACF2] [DSET|RSRC] [LID(********|logonidmask)] [RMASK(accessrulemask|resourcerulemask)] [TYPE(type)] [UID( |uidmask)] [CLASS(R|class)]
ACFRPTSL -- Selected Logonid List
[DTCFIELD(YES|NO)] {INPUT(SMF|BKUP|ACF2)]} [IF(fieldnameoperators)] [MASK(********|logonidmask)] {REPORT(SHORT|FULL|NONE)} [SFLDS(fieldlist)] [UPDATE|NOUPDATE]
ACFRPTST -- The Sectrace Report
ACFRPTXR -- The Cross Reference Report
[ACF2|NOACF2] [CLASS(R|class)] [DSET|RSRC] [DSN(datasetname)] [LID|NOLID] [NAME(name)] [RKEY(rulekey)] [RRSUM|NORRSUM] [TYPE(type)] [VOL(volumeserial)]