| Title: | -={ H A C K E R S }=- |
| Notice: | Write locked - see NOTED::HACKERS |
| Moderator: | DIEHRD::MORRIS |
| Created: | Thu Feb 20 1986 |
| Last Modified: | Mon Aug 03 1992 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 680 |
| Total number of notes: | 5456 |
I have a DCL command procedure which runs a program in batch which in
turn spends all day processing data and writing numbers to the log
file (the reference of the processed data).
The log file thus grows from 3 blocks to more than 500 blocks, causing
a lot of file extensions.
Is there any way to pre-allocate the log file?. I could always
change the way the program records it's processing (output to a
file), but this way is handy. Any ideas?
I have tried pre-allocating a file but the created log file always
replaces any existing file, even if an explicit file version is specified.
I have also tried SET RMS/SEQ/EXTEND=500 but the log file
still extends itself in fragments.
Can it be done ?. Perhaps VMS always overrides any environmental
settings. (Also asked in RDGENG::COMMAND_PROCEDURES)
Cheers, Martin
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 485.1 | FDL's worth a try ? | SIBYL::JONES | Have wetsuit will ski (in summer) ! | Tue Jun 02 1987 10:16 | 6 |
Try creating the log file with an FDL that sets the appropriate
characteristics, e.g. the extend size, best try contiguous etc.
then use OPEN /APPEND (Just tried it for an extend size of 100,
and lo and behold it did... )
Steve J.
| |||||
| 485.2 | Is it worth it??? | ALBANY::KOZAKIEWICZ | You can call me Al... | Tue Jun 02 1987 14:57 | 7 |
Does it really matter? 500 blocks over the course of an eight hour day seems like nothing. If you are looking for _measurable_ (in terms of % of execution time) performance increases, you are barking up the wrong tree. If it's that big a deal, why not let the application program open up a data file (pre-allocated) and write the data out to it? | |||||