Failure to apply all of the required service may prevent SCRT from creating a sub-capacity report that will be acceptable to IBM for sub-capacity pricing. Check the SCRT maintenance web site at www. Apply these service updates before the start of the reporting period for which you will be collecting data for SCRT. Download the SCRT deliverable from the web site at www.

Author:Zukasa Faujora
Language:English (Spanish)
Published (Last):7 April 2017
PDF File Size:19.77 Mb
ePub File Size:18.43 Mb
Price:Free* [*Free Regsitration Required]

Manage Learn to apply best practices and optimize your operations. Share this item with your network: By Robert Crawford Published: 24 Mar IBM z Systems software pricing includes an overwhelming amount of options, arcane formulae and odd deductions.

This leads some companies to hire outside experts to negotiate their IBM contracts and reduce costs. However, there are ways to navigate IBM's sub-capacity software pricing and cut mainframe costs without a third party.

Sub-capacity pricing allows users to rent IBM z Systems software based how much CPU time they consume instead of total processor capacity. The billing month stretches from the second day of the month to the first of the next. Remember two important things about SCRT reports.

Ten tips to manage IBM z Systems software costs Here are some options to control and reduce your mainframe costs: IBM recently introduced Mobile Workload pricing, a discount for transactions that originate from tablets and phones. Segregate expensive software or nonproduction work to smaller LPARs to save money. Conversely, keep discretionary work off of LPARs with expensive software.

IBM's new processor architectures run most efficiently when data and instructions are in cache. Busy machines, however, do a lot of context switching, which puts pressure on cache and leaves the CPU waiting for data. Therefore, the same workload will consume fewer CPUs on processors that run at lower utilization. In some cases, you can buy more engines that run at a slower speed to save money.

Database tuning is important for a relational database management system such as DB2. Identify inefficient SQL statements and work closely with application teams on the cheapest way to get to the data. Prioritize application tuning to eliminate low-hanging fruit, such as a number of database queries, inefficient call chains or unnecessary transactions.

While only system-level code and Java can exploit this specialty processor, it may be worthwhile to update system software or look for other options that use zIIPs.

Synchronous coupling facility calls essentially spin on a processor until they complete -- the greater the distance from the processor, the longer the spin.

Try to keep CFs close to the processor that will use them, and try to minimize the amount of CF structure duplexing. If timed correctly, some software and hardware will be essentially free.

Look at the type 89 records to know when, where and which products were active. Look at usage sections in type 30 SMF records to pinpoint exactly which products an address space used. Offload to other platforms where possible to reduce IBM z Systems software costs. For example, some processing like geocoding may be more efficient on a UNIX platform. Next Steps.


FAQ: Container Pricing for IBM Z



Adding the NO89 command in SCRT


Related Articles