Jim,

If total service units have increased, but TCB, SRB, and EXCPs haven't 
increased, that leaves the MSO component of the service units. You REALLY need 
to change MSO to 0. Even using MSO=0.0001 can result in enormous values for 
total service units. An RMF report can easily show you the relationship. 

A change in z/OS release seldom changes the amount of storage you have. So 
during the change, did you either change the MSO setting or reconfigure the 
LPAR to have more storage. If you did either of these, the service units would 
increase.

A common phenomenon when the service units increase dramatically can be seen in 
sites that use multi-period batch. The jobs drop into the next period(s) 
faster, run at a lower dispatch priority, and have a longer elapsed time.

If this is the problem, the solution is to set MSO=0.

Best regards,
Cheryl

======================
Cheryl Watson
Watson & Walker, Inc.
www.watsonwalker.com
======================


On Jul 26, 2012, at 2:41 PM, Jim Mooney wrote:

> Thanks to all for all the suggestions... very helpful.  We just noticed the 
> same thing Christopher has pointed out (longest elapsed = COBOL pgm), so we 
> are now focusing on LE and COBOL.  No changes to the COBOL source. IEFACTRT 
> was assembled for v1.13.  The sort sysouts indicate only that we have 1M less 
> of virt. stg compared to v1.11.  
> 
> 'SYS1.PARMLIB(CEEPRM00)' CEEDOPT section contains:
> STACK(128K,128K,BELOW,KEEP,512K,128K),
> STORAGE(00,NONE,00,8K),               
> TERMTHDACT(MSG,,96),                  
> 
> While 'CEE.SCEESAMP(CEEDOPT)' contains:
> STACK=((128K,128K,ANYWHERE,KEEP,512K,128K),OVR),
> 
> Is it possible BELOW vs. ANYWHERE would cause this?
> 
> -Jim
> 
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to