|
The I would suggest you do a RCLSTG. It might fix this.
There are no entries in the DSTQ on the originating system."Armand Borick" <midrangel@xxxxxxxxxxxxxxxxxx> 2007-09-05 16:17
"Denis Robitaille" <denis_robitaille@xxxxxxxxxxxx> wrote in message
news:mailman.3384.1189021970.4459.midrange-l@xxxxxxxxxxxxxxx
Try WRKDSTQ on the originating system. If there are entries on someTCP/IP.
queues, try removing them.
Have you done a WRKNETF *ALL or just WRKNETF"Pete Massiello" <pmassiello-ml@xxxxxxxxxxxx> 2007-09-05 15:55
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
to
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
SNADSwould
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
chargemailing
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
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
listmailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.