HP 3000 Manuals HP 3000 Manuals
RESIZE
{GLOBAL } [YES ]
RESIZE {APPLICATION} [DAYS=maxdays] [EMPTY=days] [NO ]
{PROCESS } [SIZE=maxMB ] [SPACE=MB ] [MAYBE]
{DISC }
Use the RESIZE command to resize raw log files. This is the only program
you should use to resize the log files in order to preserve coordination
between the files and their internal control structures. If you use
other tools, such as FCOPY, you might remove or destroy the validity of
these control structures.
Caution UTILITY cannot be used to RESIZE extracted files. If you want
to resize an extracted file, you should use EXTRACT with
appropriate file equations to create a new extracted log file.
The RESIZE command requires a log file be opened. In order to resize raw
log files, the files cannot be opened by any other process. You must
shut down SCOPE(XL) before resizing log files.
Open the raw log files with the LOGFILE command before issuing the RESIZE
command. The RESIZE command allows you to specify log file space in
units of megabytes or days. The translation of days to megabytes is more
accurate if you do a SCAN command before entering the RESIZE command.
The RESIZE function creates the new file before deleting the original
file. Make sure there is sufficient disc space on the system to hold the
original and the resized log file before doing the resizing procedure.
The default resizing parameters are shown in table 4-2.
Table 4-2. Default Resizing Parameters
------------------------------------------------------------------
| | | |
| Parameter | If Executed | If Executed in Batch |
| | Interactively | |
| | | |
------------------------------------------------------------------
| | | |
| Log file | You are prompted for | No default. This is |
| type | each available log file | a required |
| | type. | parameter. |
| | | |
------------------------------------------------------------------
| | | |
| DAYS | The current file size. | The current file |
| | | size. |
| | | |
| SIZE | | |
| | | |
------------------------------------------------------------------
| | | |
| EMPTY | The current amount of | The current amount |
| | empty space or enough | of empty space or |
| | empty space to retain | enough empty space |
| | all data currently in | to retain all data |
| | the file, whichever is | currently in the |
| | smaller. | file, whichever is |
| | | smaller. |
| | | |
| SPACE | | |
| | | |
------------------------------------------------------------------
| | | |
| YES | You are prompted | Yes. Resizing will |
| | following the reported | occur. |
| | disc space results. | |
| | | |
| NO | | |
| | | |
| MAYBE | | |
| | | |
------------------------------------------------------------------
Log File Type Parameter
The log file type parameter specifies the type of data you want to
resize. The following raw log files correspond to the current data
types:
Data Type Raw Log File
LOGGLOB Global Data Type.
LOGAPPL Application Data Type.
LOGPROC Process Data Type.
LOGDISC Disc Data Type.
If you do not specify a data type, the batch job terminates (in batch
mode), or you are prompted to supply the data type based on those log
files that currently exist (in interactive mode).
Size Parameters
Specify two sizes when you resize a log file:
* Maximum size of the file (specify DAYS or SIZE).
* Current amount of empty space required (specify EMPTY or SPACE).
DAYS, SIZE, EMPTY, and SPACE parameters can be entered in units of
days or megabytes. Days are converted to megabytes by using an
average-megabytes-per-day value for the log file. This conversion factor
varies depending on the type of data being logged and the particular
characteristics of your system.
Usually more accurate average-megabytes-per-day conversion factors can be
obtained if you perform a SCAN command on the existing log file before
you do the RESIZE command. A SCAN measures the accumulation rates for
your system.
If no SCAN is done or if the measured conversion factor seems
unreasonable, the RESIZE command will use a default conversion factor for
each type of data.
The DAYS and SIZE parameters specify the maximum size of the log file.
The actual size depends on the amount of data in the file. MPE usually
allocates disc space in units called extents, with a new extent being
allocated when the current one is filled. The default log files are
built with a maximum of 32 extents so that the minimum size of a log file
is one-thirty-second of its maximum size.
The EMPTY and SPACE parameters specify the minimum amount of room
required in the file after the resizing operation is complete. This
value is used to determine if any of the data currently in the log file
must be removed in the resizing process. You might reasonably expect
that a log file would not fill up until the specified number of days
after a resizing operation. You might want to use this feature of the
RESIZE command to minimize the number of times a log file must be resized
by SCOPE(XL) since resizing can occur any time the file is filled. Using
UTILITY to force a certain amount of empty space in a log file will cause
a log file to be resized when you want it to be.
After resizing, a log file consists of data plus empty space. The data
retained is calculated as the maximum file size minus the required empty
space. Any data removed during the resizing operation is lost. To save
log file data for longer periods of time, use EXTRACT to copy this data
to an extracted file before doing the RESIZE function.
Action Parameter
The last parameter on the RESIZE command specifies the action to be
performed.
* YES specifies resizing should be unconditionally performed. This
parameter is the default action if UTILITY is not run
interactively. If no action is specified when UTILITY is running
interactively, you are prompted to supply the action after the
resizing report is displayed.
* NO specifies resizing should not be performed. This parameter can
be specified as an action if you want to see the resizing report
but do not want to perform the resizing at this time.
* MAYBE specifies that UTILITY should decide whether or not to
resize the file. This parameter forces UTILITY to make this
decision based on the current amount of empty space in the log
file (before any resizing) and the amount of empty space specified
in the RESIZE command. If the current log file contains at least
as much empty space as specified, resizing is not carried out. If
the current log file contains less than the specified empty space,
resizing occurs.
The MAYBE action is intended primarily for use by periodic batch
jobs. For example, if you want to ensure that the log files do
not fill up during the upcoming week (forcing SCOPE(XL) to resize
them during prime-time processing), you could run a batch job that
specified a minimum amount of space such as 7 days--or maybe even
10 days, just to be safe.
The following batch job would accomplish this:
:JOB WEEKLY,SCOPE.SYS,SCOPE
:RUN UTILITY
LOG LOGGLOB.SCOPE.SYS
DETAIL OFF
SCAN
RESIZE GLOBAL EMPTY=10 MAYBE
RESIZE APPLICATION EMPTY=10 MAYBE
RESIZE PROCESS EMPTY=10 MAYBE
RESIZE DISC EMPTY=10 MAYBE
EXIT
:EOJ
Specifying MAYBE instead of YES avoids any resizing operations if 10 or
more days of empty space currently exist in any log files.
Note that the maximum file size defaults to the current maximum file size
for each file. This allows the files to be resized to new maximum sizes
without affecting this weekly batch job.
RESIZE Command Reports
One standard report is produced when you resize a raw log file. It shows
the three interrelated disc space categories of maximum file size, data
records, and empty space, before and after resizing.
RESIZE GLOBAL DAYS=120;EMPTY=10
EMPTY SPACE RAISED TO MATCH FILE SIZE AND DATA RECORDS
FINAL RESIZING PARAMETERS:
FILE: LOGGLOB.SCOPE.SYS MEGABYTES / DAY: 0.101199
-----CURRENTLY----- --AFTER RESIZING---
MAXIMUM SIZE: 65 DAYS ( 6.6 MB) 120 DAYS ( 12.1 MB) 83% INCREASE
DATA RECORDS: 61 DAYS ( 6.2 MB) 61 DAYS ( 6.2 MB) NO DATA REMOVED
EMPTY SPACE: 4 DAYS ( 0.5 MB) 59 DAYS ( 6.0 MB) 1225% INCREASE
The megabytes/day value is used to convert between days and megabytes.
It is either the value obtained during the SCAN function or a default for
the type of data being resized.
The far right-hand column is a summary of the net change in each category
of log-file space. Maximum size and empty space can increase, decrease,
or remain unchanged. Data records have either no data removed or a
specified amount of data removed during resizing.
If the RESIZE is done interactively and one or more parameters are
defaults, you can get a preliminary resizing report. This report
summarizes the current log file contents and any parameters that were
provided. The report is provided to aid in answering questions on the
unspecified parameters.
RESIZE GLOBAL DAYS=20
FILE RESIZING PARAMETERS (BASED ON AVERAGE DAILY
SPACE ESTIMATES AND USER RESIZING PARAMETERS)
FILE: LOGGLOB.SCOPE.SYS MEGABYTES / DAY: 0.101199
-----CURRENTLY----- --AFTER RESIZING---
MAXIMUM SIZE: 65 DAYS ( 6.6 MB) 20 DAYS ( 2.0 MB)
DATA RECORDS: 61 DAYS ( 6.2 MB) ??
EMPTY SPACE: 4 DAYS ( 0.5 MB) ??
In this example you would be prompted to supply the amount of empty space
for the file before the final resizing report is given. If no action
parameter is given for interactive resizing, you are prompted for whether
or not to resize the log file immediately following the final resizing
report.
Sample RESIZE Task
The following resizing task resizes the raw PROCESS log file:
LOGFILE (The name of the log file to be
LOGGLOB.SCOPE.SYS resized.) The default log file,
LOGGLOB.SCOPE.SYS, is specified in
this case.
DETAIL=OFF (The scan report will not give full
detail.)
SCAN (LOGGLOB.SCOPE.SYS will be read and
a summary report on its contents
will be produced.) The scan is
performed before the resize to
increase the accuracy of the
number-of-days calculations.
RESIZE PROCESS DAYS=60 EMPTY=30 YES
DAYS=60 (Specifies holding a maximum of 60
days of data.)
EMPTY=30 (Specifies that 30 days of this file
are currently empty.) That is, the
file is resized with no more than 30
days of data in the file to leave
room for 30 more days out of a total
of 60 days of space.