When the SMF logstream recording was first introduced, the logstream dumping utility only copied the data from the logstream and did not delete the data. The logstream could be set up with a retention period in the defining policy, allowing the System Logger to remove older data when it had expired. This method is still the preferred way for managing SMF logstreams, and we recommend using this method.
When z/OS 1.11 was released, there was a new option added to IFASMFDL, called ARCHIVE. ARCHIVE is used to dump data from an SMF logstream and then delete it once it has been dumped successfully. This product can be set up to do this procedure as well, but there are some restrictions when using ARCHIVE with the product:
When ARCHIVE is used, CA SMF Director begins accepting records from the logstream and processes every record that is passed to it by the IFASMFDL. IFASMFDL is the IBM dumping utility. Records are processed until the utility stops sending records. When records are in the logstream from a prior, non-ARCHIVE dump, they are processed by this product. However these records are not added to the history files, since they were added through a previous dump, but they are deleted from the logstream. Other records that are deleted with this procedure are all of the other records that were dumped and added to the history files.
While this produce provides the capability to delete the SMF records after dumping by offering the ARCHIVE control statement, it is not the recommended method for dumping SMF logstreams. The additional overhead of writing the records to the SMFDOUT DD increases both CPU consumption as well as the duration of the dump process. Additionally, by writing all the records to the SMFDOUT dataset, there is the possibility of failure when writing the dataset.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|