content_image/989282.jpg content_image/989283.jpg
You now must re-create the all of the JES2-depended exits with the correct version and reload the exit under JES2. Also, strong dependency exists between TM and JES2 control blocks. Therefore, after any JES2 maintenance that affects JES2 control blocks, you must recompile the following Thruput manager modules (z/OS version and maintenance level depended exist): 

GLYPH<SM590000> DTMJ2DB7 

GLYPH<SM590000> DTMJ2GO7 

GLYPH<SM590000> DTMJ2MV7 

GLYPH<SM590000> DTMJ2SV7 

Consider moving these z/OS level-dependent modules to a separate library and concatenate them in front of the Thruput manager base load library DTMLINK. 

Thruput Manager must work correctly to separate job classes. Some examples from a customer’s installation are shown in Figure 6-6. The Jobclass names can vary in other installations. 

<img src='content_image/989282.jpg'>

After restarting JES2 with the new exits and jobclass definitions, you must complete the initial configuration. The Thruput manager initial commands that are used to configure the basic jobclass selection are shown in Example 6-6. 

$MJ,TM,CLASS,SET,Analyze(TMA) $MJ,TM,CLASS,SET,General_Services(TMG) $MJ,TM,CLASS,SET,On_Demand(TMO) $MJ,TM,CLASS,DELETE(ALL) 

The response of Thruput manager after defining all jobclasses is shown in Figure 6-7. The jobclasses can vary in your environment. 

<img src='content_image/989283.jpg'>

After these steps are completed, you now can start Thruput Manager in your system. 

