The STEPLIB DD statement specifies the name of the IBM® load library, SYS1.SIFALIB, where the usage report program, IFAURP, resides. This library is shipped as part of z/OS. This library may contain required modules from IBM program products supporting usage pricing. All IFAURP maintenance and enhancements will be directed to this library.

If you need IFAURP to process type 89 records from multiple MVS™ releases, identify SYS1.SIFALIB for the most current release, OS/390. (As long as you specify the current SYS1.SIFALIB, you can run IFAURP under OS/390 or z/OS®.)

Vendors who want to use IFAURP to report on their own products can supply the customer with a load library containing a vendor exit for IFAURP to invoke. Each required vendor library must be explicitly provided to the customer by the vendor together with explicit instructions describing the appropriate JCL and associated IFAURP control statements. You must concatenate these vendor load libraries with SYS1.SIFALIB on the STEPLIB DD statement. Avoid accidental name collisions with IBM modules by not placing vendor exits to IFAURP in SYS1.SIFALIB. Vendors may, alternatively, place their load modules in a pre-existing vendor load library that is already included in the LNKLST concatenation. In this case no STEPLIB DD is required for vendors.

The STEPLIB DD statement is required if SYS1.SIFALIB is not included in the LNKLST or if vendors require it for their own product exits. If vendors do provide such exits, SYS1.SIFALIB must always appear as the first STEPLIB dataset even if it is already in the LNKLST. IBM recommends omitting this library from the LNKLST because maintenance to LNKLST libraries requires a REFRESH of LLA for the maintenance to take affect. This REFRESH is often not performed because the individuals applying the maintenance are not the same individuals performing the REFRESH.