IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

COFVLH02E VLF trimmed objects younger than the ALERTAGE


IBM Mainframe Forums -> All Other Mainframe Topics
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
Raleigh Naidoo

New User


Joined: 23 Jun 2015
Posts: 2
Location: Australia

PostPosted: Tue Feb 09, 2016 3:37 am
Reply with quote

We receive the following message from VLF_MAXVIRT Health Checker, COFVLH02E VLF trimmed objects younger than the ALERTAGE.'
The object trimmed in this instance was CSVLLA. It’s ALERTAGE and MAXVIRT settings were 60 and 4096(16M). I changed the MAXVIRT setting to 16384(64M) but continue to receive COFVLH02E messages for CSVLLA. Our paging rates are very low with an average 30% slots in use. I don't think increasing MAXVIRT further will have any impact to paging. I issued the 'F VLF,REPLACE,NN=xx' command to dynamically introduce the MAXVIRT changes? Is this effectively the same as restarting VLF or is there some added benefit restarting VLF?

Questions,
How can determine what the correct MAXVIRT size should be for CSVLLA? Is there any analytical process to determine this.
Any other suggestions?

Thanks
Raleigh
Back to top
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 8569
Location: Dubuque, Iowa, USA

PostPosted: Tue Feb 09, 2016 6:53 am
Reply with quote

Quote:
I issued the 'F VLF,REPLACE,NN=xx' command to dynamically introduce the MAXVIRT changes? Is this effectively the same as restarting VLF or is there some added benefit restarting VLF?
Yes, this is pretty much the same as restarting VLF. System programmers use MODIFY (F) console commands frequently to change system parameters.

Quote:
How can determine what the correct MAXVIRT size should be for CSVLLA? Is there any analytical process to determine this.
Any other suggestions?
One recommendation is to look at your SMF 41 records. If you have MXG or MICS, this is much easier than if you don't. If you don't have one of them and don't feel like fiddling with the SMF 41 records too much, you could keep increasing MAXVIRT until the trimmed objects go away. MAXVIRT can go to 512K (524288) which is 2 GB of memory, so even at 64M you have a long way before the maximum. Of course, the value to use depends upon a number of variables, but just to get rid of the HC message might be worth it.
Back to top
View user's profile Send private message
Raleigh Naidoo

New User


Joined: 23 Jun 2015
Posts: 2
Location: Australia

PostPosted: Tue Feb 09, 2016 9:04 am
Reply with quote

Thanks Robert. We dont have Mics or SAS but will see if I can extract the information from SMF Type 41.

Regards
Raleigh
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> All Other Mainframe Topics

 


Similar Topics
Topic Forum Replies
No new posts De-compile AFP objects IBM Tools 1
No new posts Updating DFSMShsm DB when objects are... JCL & VSAM 0
No new posts Understanding Program Objects All Other Mainframe Topics 5
No new posts Identify DB2 Objects that were create... DB2 1
No new posts Very high CPU consumption in SUM (Mem... DFSORT/ICETOOL 5
Search our Forums:

Back to Top