Setting up logspin for DNR
search cancel

Setting up logspin for DNR


Article ID: 50792


Updated On:





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.

  1. Ensure that PTFs TP10395 (QO59679), TP10396 (QO59696) and TP10405 (QO59694) are applied.

    These are included on maintenance levels of SP3 and higher.

  2. Add the LOG statement with desired parameters to the DNRCFGxx member. Here is an overview of the statement with available parameters:
    LOG [ CLASS( class ) ]     [ DEST( destination ) }    [ FORM( form ) ]    [ WRITER( writer ) ]    [ SPIN( [ LINES( lines) ] [ MINUTES( minutes ) ]    [ SYNC ] | NOSPIN
    If 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.

  3. If you are adding the ability to spin off the log in order to prevent spool problems, it is vital that you also modify the TCPaccess stack STC JCL as well.

    The logspin applies to the DNRLOG statement. Changing the JCL as follows
    will allow the output from the DD statement to be spun off for processing of some sort; archive, deletion from JES, etc.

    If you do not include FREE=CLOSE, the log will spin, but will remain attached to the STC and cannot be removed without cycling the stack.


  1. The log will spin off every 2 hours on the hour, synchronized to the previous midnight.
  2. The log will spin of either every 12 hours on the hour or when the log contains 50000 records, whichever occurs first.
    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.

    For complete information regarding implementation, including any messages that may appear, please refer to APAR QI57960, which contains the combined information that would normally appear in the various TCPaccess manuals.


Component: NTCPAC