FLAM Issue Tracker - FL5
View Issue Details
0000935FL54. Element, Byte, Record or other APIpublic2018-08-07 14:012018-08-09 17:32
Falk Reichbott 
Ulrich Schwab 
normalfeatureN/A
resolvedfixed 
GeneralGeneralGeneral
5.1.17 
5.1.185.1.18 
0000935: Add trace capability to MF-EDZ stubs of record interface
To analyze errors in MF-EDZ environments a trace facility must be implemented. There is no possibility to debug the FLCRECMF stubs and to find errors a trace is required.

An environment variable or a DD name would be useful to activate the trace.

  
No tags attached.
Issue History
2018-08-07 14:01Falk ReichbottNew Issue
2018-08-07 14:01Falk ReichbottStatusnew => assigned
2018-08-07 14:01Falk ReichbottAssigned To => Ulrich Schwab
2018-08-09 16:59Ulrich SchwabDescription Updatedbug_revision_view_page.php?rev_id=420#r420
2018-08-09 16:59Ulrich SchwabStatusassigned => resolved
2018-08-09 16:59Ulrich SchwabFixed in Version => 5.1.18
2018-08-09 16:59Ulrich SchwabResolutionopen => fixed
2018-08-09 17:30Falk ReichbottNote Added: 0001169
2018-08-09 17:32Ulrich SchwabSummaryAdd trace cabebility to MF-EDZ stups of record interface => Add trace capability to MF-EDZ stubs of record interface

Notes
(0001169)
Falk Reichbott   
2018-08-09 17:30   
The environment variable FLAM4MF_TRACEFILE can now be used to activate the trace.