Mark A Hocraffer wrote (in part):
>>Date:    Tue, 14 Oct 1997 14:54:18 -0500
>>From:    Mark A Hocraffer <[log in to unmask]>
>>Subject: Transcient Space
>>
>>Is there an easy way to tell how much transcient space a session is
>>consuming??  Last week we had disc space problems because one of our
>>programmers logged on to our Production machine before 7:30 in the morning
>>and ran a multiple pass Quiz program with large subfiles.  He did not
>>logoff to get those temp files purged...

It might be worthwhile to migrate the developers to their own volume set,
where they will get the chance to learn more intimately about the
consequences
of filling up available disk space.  You also have the option of neglecting
to
mount that volume if you really need control.  Let the punishment fit the
crime.
Or perhaps they can be punished by being isolated to a development system
where they can crash'n'burn without wrecking the production environment.
>>...The first thing I checked was for anyone running Quiz (which
>>they are not supposed to do during the day).
And luckily for you the developer had not exited Quiz, but if developers are
banished from the production system except when chaperoned you will have far
fewer incidents like this.

Of course, when I do any development work I am convinced that all resources
are infinite, instantly available and are free of charge.  When I do system
management I am convinced that all resources are nearly exhausted or
non-existent, take forever to acquire and will bankrupt the company and
plunge
the stock market into a death-dive when used.  I can usually find
like-minded
people in both camps.

<nit-pick alert>
TEMP files (files in the temporary domain) are built in "Permanent space",
the
same as permanent disk files, and can reside on non-system volume sets.
Transient space is for objects such as swapped memory pages; it can only be
configured on the system volume set.  Transient objects are cleaned up when
ISL> start norecovery
is performed.  Temporary files are cleaned up as well, because the processes
that own them no longer exist, just as when the owning user logs off.
</nit-pick alert>

Thanks,
Scott (often lurking in the HP3000-L digest) Burdman
Midrange Team - Americas
Oracle Worldwide Customer Support Services
{insert standard disclaimer here}