I wrote this script a while ago. If those files do not have an IMAGE or OMNIDEX file code
They probably do not qualify. Try this!
Mpex.S140VIRT<SYS,LEGAULT> print LISTPERC.LISTF.VESOFT
MPEXHEADER1:="FILENAME CODE RECORD TYP EOF LIMIT "+
" % CREATOR MOD-DATE ";
MPEXHEADER2:="";
MPEXHEADER3:="";
FOR RFILE IN MPEXFILESETTOTAL
DO
WRITELN (FILE:9,
CODE:6,
(IF ISASCII THEN RECSIZE ELSE RECSIZE/2):7, 'WB'[ASCII],
' ', FMTTYPE:4,
EOF:10, ' ',
FLIMIT:9,
(IF EOF//FLIMIT<=.0005 THEN 0
ELSE EOF//FLIMIT)*100:6:1, ' ',
CREATOR:9,
MODDATE:'%0D %1M %0Y '
);
listf LISTPERC.LISTF.VESOFT ,listperc
MPEX %LISTF LISTPERC.LISTF.VESOFT PAGE 1
SYSTEM S140VIRT B0005392,MANAGER.SYS,LEGAULT THU, SEP 14, 2017, 7:49 AM
ACCOUNT= VESOFT GROUP= LISTF
FILENAME CODE RECORD TYP EOF LIMIT % CREATOR MOD-DATE
LISTPERC 132B FA 17 17 100.0 MANAGER 07 SEP 17
mpex.S140VIRT<SYS,LEGAULT>
-----Original Message-----
From: Stanfield, Randy (Carrollton, TX) [mailto:[log in to unmask]]
Sent: Wednesday, September 13, 2017 6:57 AM
Subject: MPEX using DBADGALT and Jumbo sets
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<mailto:[log in to unmask](dbsetentries//dbsetmaxcapacity>.80),db>
MPEX %LISTF [log in to unmask](dbsetentries//dbsetmaxcapacity>.80)<mailto:[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<mailto:[log in to unmask](dbsetentries//dbsetmaxcapacity>.80),db>
MPEX %LISTF [log in to unmask](dbsetentries//dbsetmaxcapacity>.80)<mailto:[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 *
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
