RSP components and processing
Use the RSP components RSP SMF Capture and RSP JCL Capture to collect SMF and JCL data.
RSP SMF Capture
RSP SMF Capture (which uses the IEFU83 and IEFU84 SMF exit facilities) collects SMF record types 14, 15, 30, 61, 64, 65, and 66. These records supply data to RSP for application job cycle control job completion and data sets that are opened and closed, deleted, renamed, and allocated. RSP SMF Capture detects cycle control job completions and captures the first reference of an application data set. It does not matter if the reference is OPEN, or CLOSE, or URD (updated, renamed, or deleted).
In this situation, if CICS is started before RSP is started and the data sets are not closed before BKMAPLEN is run, RSP does not know they existed.
RSP JCL Capture
RSP JCL Capture (which uses the IEFUJI JCL exit facility) identifies all data sets in the JCL, even those data sets referenced in steps that are not processed or those data sets that are not opened— including concatenated libraries.
The database update task (ACDIUPDT)
A database update task (ACDIUPDT) runs on each image where you want to collect data.Each job submitted to the system is scanned by RSP JCL Capture to identify each data set in the JCL. As jobs run, system SMF records are created for each data set that record whether or not a data set has been read, updated, renamed, or deleted. RSP intercepts each SMF record before the record is written to the system SMF MANX and MANY data sets. These JCL and SMF records are written to the Automated Critical Data Identification Application Data Inventory database as "raw" records, or data set detail records (DSD), and can be viewed through the Automated Critical Data Identification ISPF interface.
The records intercepted by RSP SMF Capture and RSP JCL Capture are stored temporarily in buffers that are created in a data space. The database update task unloads the data space buffers and updates the Automated Critical Data Identification Application Data Inventory database. Before it unloads the data space buffers, the database update task waits until the number of loaded buffers reaches a threshold that maximizes I/O efficiency.
If the database update task slows and fills most of the buffers in the data space, due to the volume of data being processed, the task enlarges the data space. The data space can be enlarged to twice its initial size. If more room is required, the export task unloads the data space to an overflow file. When buffers are available, the import task reloads the data space buffers. The export task also unloads the data space if the database update task is not running and the buffers are full. The unloaded records are not reloaded until the database update task is processing normally again.
System configuration and RSP tasks
RSP can collect data for applications defined to Automated Critical Data Identification in single image or multi-image (SYSPLEX) environments. This capability allows you to schedule and run applications, or unique application jobs, on any processor image and still maintain continuous collection of application file usage.