2. Use resize if you can get exclusive use of the file. (I don't
think "CONCURRENT" works with dynamic files. but I'm wary with
static too.)
RESIZE will allow you to set the minimum modulus, but maybe not using
the syntax as documented. And syntax differs according to acct
flavour and OS (and UV rel?)
If RESIZE does nOt recognize MINIMUM.MODULUS on the command line,
then specify the mod explicitly, like you would a static hashed file.
That will become the minimum.modulus and the file will be sized
accordingly.
RESIZE YOURFILE 30 10000 4 [SEQ.NUM] (syntax different in Pick
flavour)
will resize the file, type 30, setting MINIMUM.MODULUS TO 10000 and
reserve the disk space in DATA.30, setting the current modulus to
10000 too.
(Of course, if the file is already larger than that, the current
modulus will be larger than 10000.)
Hi Chuck,
In case you hadn't noticed, the manual is explicit about it - RESIZE
does not recognise MIMIMUM.MODULUS if the file is already dynamic. Of
course, that doesn't mean the manual is correct :-)
Cheers,
Wol
I do pretty much ignore the manual on the subject. I'm not a
postmodern, but in this case I think truth is relative, varying from
flavour to flavour , OS to OS, release to release, manual to manual.
The absolute truth is that you can use RESIZE to set the minimum modulus
parameter itself, no matter what it says about the syntax or the
corresponding parameter.
Wol, I think it would be reading too much into one of your posts to
infer that you use (&trust) CONCURRENT, but hope springs eternal. Do
you trust CONCURRENT & INPLACE?
I *think* the manual also says you can't do CONCURRENT when resizing a
file that starts out dynamic.
IBM has been promising a trustworthy CONCURRENT to move toward
competitive uptime capability.
cds
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
