Re: Lengthy SNA Distribution Recovery step in IPL

[Pete Helgren <pete@xxxxxxxxxx>]

 Jack:  They are at V5R4M0.  Not completely current, on CUME (9321).  I 
don't know what Step Code it was, I should have written it down

Pete:  I ran the strmsf and it completed normally.  No other messages 
issued.  I am not sure why the IPL is longer but it sure hung up at the 
SNA Distribution Recovery step for quite a while (60 minutes, give or 
take).  Normally, I could bounce this thing in 20 minutes and most of 
that time was spent shutting down the IXA and IXS.

Evan: I ran the two commands you suggested.  Here is what the job log shows:

qrydst
Requested distribution complete, 0 distributions.

RCLDLO DLO(*ALL)
All document library objects are being reclaimed.
Activity related to documents and folders is now allowed.
All documents and folders are now available.
*ALL of type *N in folder path *N reclaimed.

All: I'll monitor this at the next IPL and take better notes.  I get 
zero hits when I google for "SNA Distribution Recovery" (except for 
midrange) and without the quotes I don't do much better. Nothing in the 
job log during IPL looks abnormal.

Thanks.  I'll keep you posted.

Pete Helgren
Value Added Software, Inc
www.valadd.com


On 9/1/2010 8:50 AM, Jack Kingsley wrote:
> What is the IPL step code, what version of I5/os.
>
> Current on PTF's.
> On Wed, Sep 1, 2010 at 10:25 AM, Pete Massiello
> <pmassiello-ml@xxxxxxxxxxxx>wrote:
>
> > 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
> >
> > --
> > Pete Helgren
> > Value Added Software, Inc
> > www.valadd.com
> >
> > --
> > 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.
> >
> >
> >
> > --
> > 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.