Jump to content

Recommended Posts

Posted

You could report off of the edprint.log files:

FILEDEF edaprint DISK c:ibisrv82wfsedaprint.log

FILEDEF master DISK edaprint.mas

-RUN

-WRITE master FILENAME=edaprint, SUFFIX=FIX, $

-WRITE master SEGMENT=SEG01, SEGTYPE=S0, $

-WRITE master FIELDNAME=DATETIME, USAGE=A24, ACTUAL=A24, $

-WRITE master FIELDNAME=ITEM, USAGE=A2, ACTUAL=A2, $

-WRITE master FIELDNAME=ACTION, USAGE=A11, ACTUAL=A11, $

-WRITE master FIELDNAME=CODE, USAGE=A13, ACTUAL=A13, $

-WRITE master FIELDNAME=DESCRIPT, USAGE=A70, ACTUAL=A70, $

 

TABLE FILE edaprint

PRINT DATETIME ITEM ACTION CODE DESCRIPT

WHERE ACTION EQ 'processing'

END

 

 

image.png987375 81.9 KB

Posted

What we have done is add a logger to the monitor logs and written them to a table.

Its a bit difficult to read, but has CPU, response times, concurrency and much more.

Its frustrating that an old monitor report has been removed in later releases that (I think) worked off this data.

You could drill down to a period of time and get stats on what was going on.

Posted
I tried creating log viewer it is not helpful because the log files will be renamed and new file will be created everyday and the log files will be deleted after 30 days. Resource Governance and Resource Analyzer will do the job. or you may need to write program to load the log file to DB then you can create a report.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
  • Create New...