Page tree
Skip to end of metadata
Go to start of metadata

JES2 Performance issues

Activating Trace 17 for JES2 Checkpoint Performance analysis:

Trace 17 have  statistics associated with checkpoint performance. Trace records include values for each phase of the checkpoint cycle.

Activating the traces using MVS JES2 Commands:

There are various ways to start TRACE(17) for JES2 Performance analaysis, this section only details activating Trace 17 using commands, for more information regarding this and other methods for Jes z/OS 2.2  see: {+}
Information extracted from: {+}
Turn on $TRACE(17) records for ten to fifteen minutes during your most active time of the day from a JES2 perspective. This may be during peak TSO activity, when many jobs are submitted, when JES2 queues are longest, or during a JES2 restart. 

  • Sample JES2 operator commands to start Trace 17 under Class A:  

    $S TRACE(17)

  • To deactivate Traces after collection:   

    $P TRACE(17)

  • Write the Traces to disk from Class A:   


  • Analyse Traces using the sample program  JES2T17A provided with JES2

JES2 v2r2 Self Tuning Commands

  • New Function - automatic checkpoint cycle management 
    • Adjust HOLD= and DORMANCY based on workload
    • Users can display whether Cycle Management is automatic or manual, without setting any values
  • SDSF MAS display shows what members are using
    • Adjusts as members join and leave MAS
    • Command to display MAS definitions: 

  • To enable automatic checkpoint cycle management:  

    • This setting gas MAS scope and persists until it is explicitly disabled.

  • The function can also be enabled via MASDEF initialisation statement
  • To disable automatic cycle management, i.e. traditional manual cycle management:  


    All members will revert to the setting previously active (before automatic cycle management was turned on)