Re[2]: My token ring network croaked

[ericadelong@xxxxxxxx]

You know, I don't really remember just what we did. I was not directly involved 
with this..... 

I'm not certain if a CHGCMDDFT applied to ENDJOB would affect job abends. For 
that matter, that could be a horrible fix if a job abends and you need the 
joblog to identify the problem. 

Perhaps you could write a simple CL program to issue an ENDJOB with LOGLMT(1).
Identify the message issued for your communications failure and 

CHGMSGD MSGID(xxxnnnn) MSGF(msgfile) DFTPGM(yourENDJOBPGM)

hth. Just one idea....
Eric A DeLong
ericadelong@pmsc.com    

______________________________ Reply Separator _________________________________
Subject: Re: My token ring network croaked 
Author:  <MIDRANGE-L@midrange.com > at INTERNET
Date:    5/6/98 4:45 PM


Eric !
     
Where/how do you use this ? I see that the ENDJOB command has a field for this 
information, but if the system is ending these jobs due to a communications 
failure,
how do you handle this ?
     
We have had the same thing happen. We have had a NIC start beaconing or have had
a
frame realy failure OR the one of the NIC cards in our AS/400 has "burped" and 
all
of a sudden we have 400+ Client Access devices in the US and Canada 
failing/writing
MASSIVE job logs...
     
Thanks !
     
Chuck
     
ericadelong@pmsc.com wrote:
     
> Be aware that if a line failure occurs and terminates a large number of active
> sessions, the system may seem like it's locked up. This happened to to me 
years
> ago, so IBM may have fixed it now. The problem had to do with writing joblogs 
> for all of the terminating jobs. The workaround was to limit the ENDJOB
> LOGLMT(1).
>
> Eric A DeLong
> ericadelong@pmsc.com
> ______________________________ Reply Separator 
_________________________________
> Subject: Re: My token ring network croaked
> Author:  <MIDRANGE-L@midrange.com > at INTERNET 
> Date:    4/30/98 10:26 PM
>
> Your TRN adapter type?
>
> We are at v4r1, use a 2619, and had a failed line.  Once line/IOP was reset 
> the majority of SNA sessions could not re-connect.  An IPL was the only
> circumvention available.  Happened twice to us.  IBM had a PTF that fixed a 
> number of many problems re: 2619.  I'm out of office so I'm short my
> documentation.  I'd recommend that PTF if you are on V4R1.  We and IBM were 
> never able to determine the exact cause.  The failures occured within 7 days 
> of one another.  Since the PTF we have had almost three months with no
> problems.....
>
>
>
>
> Help!
>
> We have an AS400 S-10 as a database server for a token ring network of 14 
> PCs, some of which are Windows 95 and some are WFW 3.11.  The Windows 95 
> machines run CA95; the WFW 3.11 machines are on CA Enhanced for DOS with
> Rumba; all machines also run Microsoft Network.  I have a variety of token 
> ring cards.
>
> Tuesday afternoon, one of our PC users reported to me that her PC had
> frozen in an AS400 session.  Rebooting it (using the reset button - the
> keyboard buffer was full, so the three finger salute wouldn't work) would 
> not load LAN support and when it went looking for the router, it began
> beaconing.  Within five minutes, everyone who was in an AS400 session
> reported their systems down, and no one could log back on to the network. 
>
> IBM said it was a cabling network.  When we called the cabling contractor, 
> they came in and found that the AS400 had de-inserted itself from the ring. 
>  I did a PWRDWNSYS and IPL, which has gotten the system back.  My network
> is now running again, but I'm no further ahead as to what the problem could 
> have been or, more importantly, how to fix it.  As near as I can figure out 
> from the log, a PC upstream from the AS400 disconnected improperly, causing 
> the AS400 token ring line to fail.
>
> Any assistance/insight (in non-technical terms, please) would be greatly 
> appreciated.
>
> TIA
> David Petrie
> Taylor Enterprises - Your First Choice in Association Management 
>
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com. 
> | To unsubscribe from this list send email to
> MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator: 
> david@midrange.com
> +---
>
>
>
>
>
>
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. 
> | Questions should be directed to the list owner/operator: david@midrange.com 
> +---
>
>
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. 
> | Questions should be directed to the list owner/operator: david@midrange.com 
> +---
     
     
     
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. 
| Questions should be directed to the list owner/operator: david@midrange.com 
+---
     


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---