HP3000-L Archives

September 2017, Week 2

HP3000-L@RAVEN.UTC.EDU
Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
MPEX using DBADGALT and Jumbo sets
From:
"Stanfield, Randy (Carrollton, TX)" <[log in to unmask]>
Reply To:
Stanfield, Randy (Carrollton, TX)
Date:
Wed, 13 Sep 2017 13:57:02 +0000
Content-Type:
text/plain
Parts/Attachments:
text/plain (1 lines) 
Have another Vesoft question for the group. We've tried staying away from Jumbo Data sets for the most part. Have a job that runs during backup quiet time we will run to check database capacity and automatically increase the size. But it having an issue with Jumbo datasets. We have DDX sets too and evaluate the DBSETDYNAMIC. Not sure if the Jumbo sets are falling under this condition too.



listf [log in to unmask](dbsetentries//dbsetmaxcapacity>.80),db

     MPEX %LISTF [log in to unmask](dbsetentries//dbsetmaxcapacity>.80)   PAGE 1     

     SYSTEM UW0H3D01   STANFR01.TESTSW,DATA   WED, SEP 13, 2017,  9:45 AM      







ACCOUNT=  TESTSW      GROUP=  DATA    



FILENAME SET NAME     TYPE LDEV  ENTRY   CAPA-  %FULL BLK SECTORS %BLOCK SECTRS

                                 COUNT    CITY        FCT         WASTED WASTED



SFDAUX95 IT-AUDIT        D  34 4354109 4989088  87.3%   4      32   0.0%   -415

 95.001                  C    

 95.002                  C    





DBADGALT @.DATA (MODDATE>TODAY-30 AND DBSETMAXCAPACITY<> 0 AND &

         DBSETDYNAMIC=FALSE  AND DBSETENTRIES//DBSETMAXCAPACITY>.80),.70



listf [log in to unmask](dbsetentries//dbsetmaxcapacity>.80),db

     MPEX %LISTF [log in to unmask](dbsetentries//dbsetmaxcapacity>.80)   PAGE 1     

     SYSTEM UW0H3D01   STANFR01.TESTSW,DATA   WED, SEP 13, 2017,  9:45 AM      







ACCOUNT=  TESTSW      GROUP=  DATA    



FILENAME SET NAME     TYPE LDEV  ENTRY   CAPA-  %FULL BLK SECTORS %BLOCK SECTRS

                                 COUNT    CITY        FCT         WASTED WASTED



SFDAUX95 IT-AUDIT        D  34 4354109 4989088  87.3%   4      32   0.0%   -415

 95.001                  C    

 95.002                  C    





The Jumbo sets aren't being included in the database capacity changes. Is there another hidden option like DBSETDYNAMIC that isn't in the help I can evaluate?



Secondary Question can the 95.001 and 95.002 be excluded in the listf's in Vesoft?





* To join/leave the list, search archives, change list settings, *

* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2