SAS Institute provides the following examples to assist customers who want to track usage of specific SAS software products on z/OS systems. These are provided "as is." You might need to modify these programs to meet your needs. In the example based on load module usage, the list of load modules might not include all modules from all releases of SAS. The list includes at least one module that is commonly called for each SAS product.

• You can track some SAS software products by having SAS software write a System Management Facility (SMF) record at the termination of every PROC or DATA step. To enable this feature, you must have installed the SAS SVC routine and enabled the SMF and STIMER SAS system options. Note that you can choose which SMF record type SAS creates by using the SMFTYPE system option. Instructions for installing the SVC routine as well as the optional SAS SMF Exit are available in Configuration Guide for SAS^® 9.4 Foundation for z/OS. The SVC is downward-compatible with any SAS release. The optional SAS SMF Exit is needed only if you intend to customize the SMF records that SAS writes.

  The sample SMF usage job extracts the SAS SMF records and creates a simple product usage report by job and user. This code is valid for releases of SAS^® 8.2 through SAS^® 9.3.

• Some products are not always used via specific PROC statements and thus are not easily measured via SMF records. This is true for SAS/AF^® software, SAS/CONNECT^® software, SAS/SHARE^® software, SAS/ACCESS^® software, SAS/FSP^® software, and SAS^® Integration Technologies. For these products, you must look at which load modules are used. This data is not available in standard SMF records but can be created with certain third-party products. Ask your system administrator if you have a third-party product that will log module loads, such as PDSMAN. The sample load module usage job generates a sample product usage report that is based on load module usage. Instructions in the comments of that program describe how to modify the code for your specific data. This code is valid for releases of SAS 8.2 through SAS 9.3.

  Caution: SAS/AF is often used to develop applications that are compiled and then used without invoking SAS/AF modules. Thus, you might not see evidence of SAS/AF usage in the load module data during regular usage of those applications. SAS/AF shows up as being "in use" only when it is used to create an AF program or modify an existing AF application. If you cancel your SAS/AF license, you can no longer make modifications to your SAS/AF applications.

• If you do not have any data on load module usage, you might be able to use logs from some products.
  • For SAS/CONNECT, if you have implemented a SAS/CONNECT spawner, you can look at the spawner log file to see client connections. Note that this might not show all traffic, such as outbound traffic to another host.
  • For SAS/SHARE, the log for the SAS/SHARE server shows client connections to that server. Again, outbound traffic for applications that are connecting to a SAS/SHARE server on other hosts are not shown.
  • For SAS/IntrNet^® software, you might see an SMF record created each time that PROC APPSERV runs to create a new application server. The number of records might not be an accurate indicator of the actual traffic and usage of this product.

Note: Removing or renaming load modules for any product might cause loss of functionality in another product. Removing or renaming load modules is therefore not recommended.