SCRT Users Guide. This information describes how to use the Sub-Capacity Reporting Tool (SCRT). SCRT is a no-charge IBM® tool that reports required license capacity for sub- capacity eligible products that run on z/OS®, z/TPF, or z/VSE® operating systems . License Management Support. Welcome to License Management Support (LMS). This application will assist you in submitting SCRT SubCapacity or SCRT.

Author: Bazragore Shar
Country: Pakistan
Language: English (Spanish)
Genre: Life
Published (Last): 20 April 2009
Pages: 268
PDF File Size: 5.38 Mb
ePub File Size: 10.55 Mb
ISBN: 638-7-51055-142-6
Downloads: 27568
Price: Free* [*Free Regsitration Required]
Uploader: Zululkree

It is a drastic understatement to simply state that software pricing is a sensitive subject. Any LPARs that are part of a Container Pricing solution must be ibbm to the solution or workload indicated as part of the agreement.

The following fields appear in the header record: Customize the JCL for the SCRT ivm that you downloaded in step 2 to meet your needs and customize the SCRT control statements to supply the required customer-related information, software configuration information, and any other optional processing information, as necessary.

You must use the most current version of SCRT to submit reports for billing. If you have signed up for and have access to the license management system LMS web application, move the report to your workstation as a.

Join The Discussion Cancel reply Your email address will not csrt published. While reviewing the sub-capacity reportadd comments to the report, as required, before submitting it to IBM. This benefits the customer too of course, who only have one copy of SCRT to maintain. Move the report to your workstation as a.

Container Total The total rolling 4-hour average utilization or MSU consumption for the container for the hour. Failure to have the required contracts or addenda signed or otherwise agreed to may cause IBM to reject the affected sub-capacity report. The SCRT report is full of environment and product data, including the peak rolling four-hour average for IBM software products based on where and when they execute.

  DEI 556U PDF

Each container section begins with a header record, followed by an hour-by-hour view of the TRGs and dedicated Scet that contributed to the container’s rolling 4-hour average utilization for each hour. Your email address will not be published. Each container section begins with a header record followed by an hour-by-hour view of the TRGs and dedicated LPARs that contributed to the container’s rolling 4-hour average utilization for each hour.

SCRT Enables ISV Product Support

A sequential data set that contains a single text file in comma-separated value. For more information about the reporting period, see Analyzing the sub-capacity report. You can choose any of the following methods to review the sub-capacity report: Each member is one sub-capacity report. Verify that all of the IBM contracts and addenda have been signed prior to submitting the sub-capacity reports that use those pricing options.

This configuration is usually done when the CPC is installed. Sccrt to use the Sub-Capacity Reporting Tool.

SCRT also does the following: Submit the sub-capacity report to IBM. The replacement solution ID must correspond to the qualified workload that ran srct the container. Each sub-report contains a section for each container. Provides a simple, non-intrusive means for you to generate sub-capacity reports that show required license capacity for all eligible sub-capacity products that execute on a CPC Allows IBM to receive, view and store sub-capacity reports received from customers Allows IBM to generate customer bills according to the sub-capacity reports received from customers.

A participating ISV then provides this file to each customer. Since sub-capacity pricing was introduced many years ago, z System customers asked ISVs to adopt similar models for their software licensing.

Overview of the SCRT process

For example, if you begin to collect data for SCRT in the month of January, you must submit the sub-capacity report by 9 February. A reporting period is from midnight the very beginning of the second day of the month up to midnight the very beginning of the second day of the next month.


The output can be: If the actions do not correct the problem, open a service request PMR against component SCRT2 with a description of the problem, an attachment containing the job log for the SCRT job, and an attachment containing each of the sub-capacity reports that may have been generated.

The same sort of information is provided, such as the peak four-hour rolling scrg, data collection statistics, and more. Follow the actions indicated for each message to address each problem before attempting to rerun the SCRT job. Apply these service updates before the start of the reporting period for which you will be collecting data for SCRT.

This is intended to further reduce the chance of any output being directed to the wrong party. If Country Multiplex Pricing is in use, this value includes the contributions from all CPCs on which the container ran.

Review the sub-capacity report. The trace output is organized as comma-separated fields to allow the ib to be read by a spreadsheet application.

After these problems have been resolved, continue with the next stop in this process.

License Management Support

Traditional sub-capacity pricing is based on the four-hour rolling average utilization of the LPARs in which the sub-capacity products execute. The report is a text file in comma-separated value.

By Andrew Sica The z Software ecosystem now has a common approach to determining product license capacity. Return codes higher than 0 indicate that SCRT encountered one or more problems generating one or more sub-capacity reports.