Pete,

I don't know why SNA & Mail relay would make the IPL longer, but
have you tried to do a STRMSF *CLEAR? Instead of the regular STRMSF.

It's a shot in the dark.

Pete

Pete Massiello
iTech Solutions
http://www.itechsol.com

Add iTech Solutions on Facebook:
http://www.facebook.com/group.php?gid=126431824120
Add iTech Solutions on LinkedIn: http://www.linkedin.com/groups?gid=2206093


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Pete Helgren
Sent: Tuesday, August 31, 2010 6:48 PM
To: Midrange Systems Technical Discussion
Subject: Lengthy SNA Distribution Recovery step in IPL

A few weeks back I dealt with an open relay issue on a 520 that I
eventually got sorted out. At least I *thought* I got it sorted out.
The biggest fallout was that there were a jillion spool files generated
in the process and it took a dltsplf and a rclsplstg to get back some
critical space. But I still have my suspicions that there are still
files lurking. What raised my suspicions was that last night when I
IPL'd the SNA Distribution Recovery step took over an hour. When I had
IPL'd the system after the rclsplstg a few weeks ago the SNA
Distribution Recovery step also took equally as long. Seems like SNA is
"recovering" but recovering what?

So the questions are: Why is the IPL taking so long at that step
(instead of minutes, like it used to)? Where should I look for
"leftovers" after the open relay? Could there be undelivered messages
queued up somewhere? WRKDSTQ shows nothing in any of the queues.

Thanks


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.