The usual suspects are the LOG####.PUB.SYS and NMLG####.PUB.SYS (where
the #s are digits 0-9).  These can be purged by PURGE LOG####.PUB.SYS
and PURGE NMLG####.PUB.SYS. 

Also, you may have a number of old/large spool files; the files in the
group OUT.HPSPOOL. I don't recommend just purging these as there is
linkage to a table known as the ODD (output device directory); if you
have MPEX, I believe it has the proper logic to correctly delete
spoolfles.  Otherwise, you could use SPIFF or the SPF commands to clean
up these files.

Check in the DAT.TELESUP group for @MEM and @VAR files; these are memory
dump files, which, if they aren't current, should be deleted.

There may well be files may be created by your application, such as
transaction logs (not IMAGE logs) or similar audit/intermediate files.
One would have to know the application's operation to make any
recommendations in that arena.

HPTH...
Jack 

-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On
Behalf Of Tom Hula
Sent: Friday, October 03, 2008 10:43 AM
To: [log in to unmask]
Subject: [HP3000-L] Store Taking Too Long

Seems like I read something about this in the past, but can't find it in
the archives.

Seems like my nightly store to dat3 has been taking longer and longer
over time. Partially, it is due to some datasets and tables being
expanded, but I'm wondering if there isn't some sort of extra files
somewhere that could be purged or erased to cut down the job time. I
periodically delete log files in pub.sys. Just wondering if there is
somewhere else to look for unneeded files. I have a Series A400.

Tom

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *