anyone knows the (negative) implications to performance system if we
execute a scratch file. We have a long process that execute an ASM module
(equivalent to delete scratch of IDCAMS).
If your ASM module is just issuing the IBM SCRATCH macro, I would not
expect any significant performance implication.
SCRATCH must update the VTOC of the disk involved, which requires
getting a SYSVTOC RESERVE on the disk. This will stop any other system
from accessing the disk until the SCRATCH is done.
If you are converting SYSVTOC to a global ENQ in GRS or CA-MIM, then
other systems will not be inhibited from accessing the disk, but there
may be a small penalty while the ENQ is acquired across all systems.
If you have an active VTOCIX on the disk volume, the SCRATCH process is
pretty fast, only a few I/Os. If you do not have an active VTOCIX, then
more I/O may be required and the SCRATCH will take a little longer.
But in any case, I would not expect the SCRATCH to have any noticiable
impact on your system.
When you say "a long process that execute an ASM module", do you mean
that the SCRATCH seems to take a long time? How long? How do you
know it is the SCRATCH?
--
Bruce A. Black
Senior Software Developer for FDR
Innovation Data Processing 973-890-7300
personal: [EMAIL PROTECTED]
sales info: [EMAIL PROTECTED]
tech support: [EMAIL PROTECTED]
web: www.innovationdp.fdr.com
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
