FLAM Issue Tracker - FL5
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0000811FL54. Element, Byte, Record or other APIpublic2016-06-01 13:592016-10-10 08:29
ReporterFalk Reichbott 
Assigned ToRolf-Dieter Euler 
PrioritynormalSeverityfeatureReproducibilityN/A
StatusresolvedResolutionfixed 
PlatformSystem zOSz/OSOS VersionV2R20
Product Version5.1.11 
Target Version5.1.14Fixed in Version5.1.13 
Summary0000811: Support of SMF record type 89 for FLAM components
DescriptionCustomer using our APIs can not determine the CPU usage and other performance messurments of our components. To solve this, we plan to support SMF logging in each FLAM component. This will allow to measure compression, encryption, character conversion, encoding, formatting and I/O efforts per implementation (GZIP, BZIP2, XZ, PGP, XML, TXT, FLAM4, BLOCK-IO, Record-IO, ...).
Steps To Reproduce
Additional Informationsee http://publibfp.dhe.ibm.com/epubs/pdf/iea2g2c1.pdf [^]

Chapter 12. IFAUSAGE — Collecting Usage Data
Any product or application can measure usage. If you are a software vendor or
application owner, use the information in this topic to enable your software
product to measure its usage, perhaps to participate in measured usage pricing.
The measurement function collects data using SMF record types 30 and 89. SMF
record type 30 (Version 5 only) contains usage data for the product's address space.
System-wide usage data for each product is recorded on SMF record type 89. The
control and writing of these records is the same as for any SMF record type.
TagsNo tags attached.
Relationships
related to 0000095closed Ulrich Schwab Support of SMF logging in z/OS 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2016-06-01 13:59Falk ReichbottNew Issue
2016-06-01 13:59Falk ReichbottStatusnew => assigned
2016-06-01 13:59Falk ReichbottAssigned To => Rolf-Dieter Euler
2016-06-01 14:12Falk ReichbottRelationship addedrelated to 0000095
2016-06-01 17:37Ulrich SchwabSummarySupport of SMF record type 89 for FLAM komponents => Support of SMF record type 89 for FLAM components
2016-06-01 17:37Ulrich SchwabDescription Updatedbug_revision_view_page.php?rev_id=298#r298
2016-06-09 10:36Falk ReichbottNote Added: 0000996
2016-07-26 15:23Falk ReichbottNote Added: 0001011
2016-07-26 15:24Falk ReichbottNote Added: 0001012
2016-07-26 15:25Falk ReichbottNote Edited: 0001012bug_revision_view_page.php?bugnote_id=1012#r308
2016-08-10 09:48Falk ReichbottNote Edited: 0001011bug_revision_view_page.php?bugnote_id=1011#r310
2016-08-10 09:51Falk ReichbottNote Edited: 0001012bug_revision_view_page.php?bugnote_id=1012#r311
2016-08-10 09:51Falk ReichbottTarget Version5.1.13 => 5.1.14
2016-10-10 08:29Falk ReichbottNote Added: 0001027
2016-10-10 08:29Falk ReichbottStatusassigned => resolved
2016-10-10 08:29Falk ReichbottFixed in Version => 5.1.13
2016-10-10 08:29Falk ReichbottResolutionopen => fixed

Notes
(0000996)
Falk Reichbott   
2016-06-09 10:36   
Implemented for all FL5 components with CPU time and processed bytes
(0001011)
Falk Reichbott   
2016-07-26 15:23   
(edited on: 2016-08-10 09:48)
APF authorisation required (current solution with IFAUSAGE are not possible)
(0001012)
Falk Reichbott   
2016-07-26 15:24   
(edited on: 2016-08-10 09:51)
CPU usage (including SRB times) will be determined with TIMEUSED makro and written to the normal log. A SMF logging can later be activated if a record type given. The issue is moved to revision 14 to re-implement all these stuff.
(0001027)
Falk Reichbott   
2016-10-10 08:29   
Add usage logging and reporting feature unsing a log stream. More information can be found in install.txt for z/OS.

The TIMEUSED macro are used and the CPU, SRB (ZIIP), possible SRB and total time together with the amount of processed bytes are logged.

The feature can be used to determine cost saving for ZIIP, ZEDC and other co-processors.