FLAM Issue Tracker - FL5
View Issue Details
0000826FL51.2 FLCCpublic2016-10-11 10:402016-10-11 10:49
Falk Reichbott 
Rolf-Dieter Euler 
normalminoralways
resolvedfixed 
System zz/OSV2R20
5.1.13 
5.1.135.1.13 
0000826: Prevent RACF and LOGR messages if no log stream for usage logging defined
Currently FLAM try to connect to log stream FLAM.USAGE if no system variable (&FLOGQLx) defined. This results in a lot of messages from RACF and LOGR is this log stream not defined or the corresponding RACF settings not done.

The customers request to prevent these messages.
No tags attached.
Issue History
2016-10-11 10:40Falk ReichbottNew Issue
2016-10-11 10:40Falk ReichbottStatusnew => assigned
2016-10-11 10:40Falk ReichbottAssigned To => Rolf-Dieter Euler
2016-10-11 10:45Falk ReichbottNote Added: 0001028
2016-10-11 10:45Falk ReichbottStatusassigned => resolved
2016-10-11 10:45Falk ReichbottFixed in Version => 5.1.13
2016-10-11 10:45Falk ReichbottResolutionopen => fixed
2016-10-11 10:49Falk ReichbottNote Edited: 0001028bug_revision_view_page.php?bugnote_id=1028#r319

Notes
(0001028)
Falk Reichbott   
2016-10-11 10:45   
(edited on: 2016-10-11 10:49)
The connect to a log stream will now (>5.1.13-15352) only be done if the corresponding system variables defined.

e.g. SYS1.PARMLIB(IEASYM00)
   SYMDEF(&FLOGQL1='FLAM')
   SYMDEF(&FLOGQL2='USAGE')

Additonal the SRB time is now called offload time, which is more platform indepentend.