Guardian User's Guide

Monitoring Hardware Components
Guardian User’s Guide—425266-001
19-27
Checking the Size of Database Files
Checking the Size of Database Files
This subsection explains how to check the size of critical database files in order to
prevent a “file full” error (error 45) from occurring. For summary information relating to
problems you might encounter with files, see Solving Common System Process
Problems on page 4-11.
To check the size of any file on your system, enter:
> FUP INFO filename, DETAIL
A report similar to the following is sent to your home terminal:
This report shows that FILEA is 58.2 percent full. When database files become 90
percent full or more, you can modify the file extents dynamically with FUP or perform
other procedures as determined by your local system policies.
Example
To check the size of the file DATA1.MEMOS, enter:
> FUP INFO DATA1.MEMOS, DETAIL
A report such as this is sent to your home terminal:
$DATA.FILES.FILEA 10 Jul 1993, 14:05
ENSCRIBE
TYPE U
CODE 100
EXT ( 224 PAGES, 14 PAGES )
ODDUNSTR
MAXEXTENTS 370
BUFFERSIZE 4096
OWNER 8,255
SECURITY (RWEP): NUNU, LICENSED
DATA MODIF: 10 Jul 1994, 14:04
CREATION DATE: 10 Jan 1994, 14:04
LAST OPEN: 10 Jul 1994, 14:04
EOF 267022 (58.2% USED)
FILE LABEL: 822 (20.2% USED)
EXTENTS ALLOCATED: 10
$DATA.DATA1.MEMOS 12 Jul 1994, 14:05
ENSCRIBE
TYPE U
CODE 101
EXT ( 2 PAGES, 2 PAGES )
ODDUNSTR
MAXEXTENTS 16
BUFFERSIZE 4096
OWNER 8,255
SECURITY (RWEP): NUNU
DATA MODIF: 12 Jul 1994, 14:04
CREATION DATE: 12 Jan 1994, 14:04
LAST OPEN: 12 Jul 1994, 14:04
EOF 567022 (88.2% USED)
FILE LABEL: 775 (31.6% USED)
EXTENTS ALLOCATED: 10