Try WRKDSTQ on the originating system. If there are entries on some
queues, try removing them.
"Pete Massiello" <pmassiello-ml@xxxxxxxxxxxx> 2007-09-05 15:55 >>>
Have you done a WRKNETF *ALL or just WRKNETF
Pete
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Armand Borick
Sent: Wednesday, September 05, 2007 5:40 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Space eating SNADS
We have 2 iSeries systems, connected via Ethernet and SNA over TCP/IP.
We use SNADS to back up production libraries from one to the other,
using
the SNDNETF command.
Due to lack of monitoring, the backup system got over 99% disk
utilization,
and shut down.
After restarting the system, and deleting a few libraries, the disk
util
rests at 98%, and the PRTDSKINF command reports over 40% allocated to
SNADS
and communications.
The WRKNETF display is empty, but the space used looks like the save
files
sent in the backup process.
We are considering a system restore, but would prefer something less
drastic. Of course, we are not on IBM SW maintenence, so they would
charge
many major body parts just to answer the phone.
Does anyone out there have any suggestions, besides a decent burial?
Thanks,
Armand Borick
Responsive Data Systems
midrange.com
