To prevent spool problems when running while DNR tracing is activated, DNR can be configured to spin off the log at specified intervals.
Depending on your environment, you may need to leave DNR tracing active in order to capture all necessary documentation as a problem occurs. This has been problematic in the past as the DNR trace information can accumulate, causing potential problems with the JES spool, especially when the stack remains active for long periods of time
To prevent this problem while still allowing tracing to capture problems that cannot be recreated at will, we have added the ability to spin off the DNR log in a manner similar to the SPIN parameter in the LOGGING statement for the T01LOG. The below steps outline how to implement this on your stack.
LOG [ CLASS( class ) ] [ DEST( destination ) } [ FORM( form ) ] [ WRITER( writer ) ] [ SPIN( [ LINES( lines) ] [ MINUTES( minutes ) ] [ SYNC ] | NOSPINIf you are not sure where to place this within your DNRCFG, a logical location is just below the POOLDEF statement and before the DNR startup statements.
//DNRLOG DD SYSOUT=&SOUT,FREE=CLOSEwill allow the output from the DD statement to be spun off for processing of some sort; archive, deletion from JES, etc.
LOG SPIN(MINUTES (120) SYNC)
LOG CLASS(J) DEST(RMT32) SPIN(LINES(50000) MINUTES(7200) )NOTE: Once you have defined and implemented the DNRLOG statement, changes can also be made dynamically without cycling the stack.