× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Is this a hardware problem or not ?
  • From: Chris Spirinckx <Chris3.Spirinckx@xxxxxxxxxx>
  • Date: Wed, 27 Jun 2001 20:13:58 +0200


Hi group,


Sorry for the long post, but I'm really annoyed with this problem.

Since monday morning , one of our AS/400 fails to communicate with the other 2
systems using TCP/IP & SNA over the Tokenring.
Traffic over the tokenring between these last two is working perfectly.
Ethernet between the 3 machines is working perfectly as well.
The IP-Tokenring traffic is needed by MIMIX.
The system with the problem is our HUB-system.

These are the Communication Resources from the failing system :

    Resource        Type  Status                Text
    CMB01           9164  Operational           Combined function IOP
      LIN04         2720  Operational           Comm Adapter
        LIN011      2720  Operational           V.24 Port
      LIN02         2721  Operational           Comm Adapter
        LIN012      2721  Operational           Comm Port
        CMN05       2721  Operational           Comm Port
      LIN05         2850  Operational           File Server IOA
        CMN06       2838  Operational           Ethernet Port
        CMN01       2724  Operational           Token-Ring Port    
        CMN07       6B00  Operational           Virtual Port
      LIN06         285A  Operational           LAN Adapter
    CMB02           2809  Operational           Combined function IOP
      LIN03         2838  Operational           LAN Adapter
        CMN04       2838  Operational           Ethernet Port      <== eth cmn


If I stop and restart the *NWS (LIN05), 
SNDNETMSG/STRPASTHR & PING starts to work again over the Tokenring. 
The ping response times are varying between 1ms and above 1sec.
Using an FTP-session or a SNDNETF to transfer some data, 
all communications suddenly stops in the middle of the process
with no errors whatsoever. 
(QSNADS jobs have now a status of "ICFW" , Pings don't give any result anymore)
I even tried the Windows trick ( re-IPL :-) the system ) , still no luck.

During these 4 days I've called Hardware support, Software support and again
Hardware support and yes again Software support. Well you get the idea :-(


in SST I found the following around the time that we manually IPLd the system
over the weekend :

                      Display Detail Report for Resource
                                         Serial                  Resource
 Name              Type      Model       Number                  Name
 NTASDEVL          2850      012         10-06031                LIN05
 Log ID  . . . . . . . . . :   0101C249   Sequence . . . . . . . : 73298
 Date  . . . . . . . . . . :   01/06/23   Time . . . . . . . . . : 07:16:40
 Reference code  . . . . . :   1302       Secondary code . . . . : 00000000
 Table ID  . . . . . . . . :   B006F060   IPL source/state . . . : B/3
 Class . . . . . . . . . . :   Permanent
 System Ref Code . . . . . :   B0061302
 No description is available


                    Display Hexadecimal Report for Resource
                                         Serial                  Resource
 Name              Type      Model       Number                  Name
 NTASDEVL          2850      012         10-06031                LIN05
 Offset          0 1 2 3  4 5 6 7  8 9 A B  C D E F    EBCDIC
 000240          00000000 00000000 00000000 00000000   ................
 000250          00000000 00000000 00000000 00000000   ................
 000260          00000000 00000000 00000000 00000000   ................
 000270          C1D1C4C7 D7F0F1C3 D7D7C2C1 F0F000C3   AJDGP01CPPBA00.C
 000280          C1D1C4C7 F3F0F1C3 D7D7C2C1 F0F000C3   AJDG301CPPBA00.C
 000290          F4F5C8F1 F2F2F6C3 D7D7F6F1 F4F100D5   45H1226CPP6141.N
 0002A0          C6C9F0F0 F1F3F2C3 D7D7F1F2 F1C300D5   FI00132CPP121C.N
 0002B0          00000000 00000000 00000000 00000000   ................
 0002C0          00000000 00000000 00000000 00000000   ................
 0002D0          C3D7D7C5 C1F1F1D5 C2F0F0F6 F1F3F0F2   CPPEA11NB0061302
 0002E0          F0F0F0F0 F0F0F0F0 F0F0F0F0 F0F0C6F8   00000000000000F8
 0002F0          F0F0F2F1 0000E8D5 00000000 00000000   0021..YN........

at offset 0002D0 I see "CPPEA11"


 Message ID . . . . . . . . . :   CPPEA11
 Message file . . . . . . . . :   QCPFMSG
   Library  . . . . . . . . . :     QSYS
 Message . . . . :   *Attention*  Hardware service may be required.
 Cause . . . . . :   Internal analysis of a hardware exception indicates
that the system may require the attention of your service provider.
 Recovery  . . . :   Contact your hardware service provider.  The steps
below may be performed to attempt to return to normal operations:
     1) Vary off any failed configuration descriptions.  Then vary them on.
     2) If processor &26 is still not operable and DASD is attached, IPL the
   system to start the processor. If DASD is not attached, perform "VRYCFG
   RESET(*YES)" to start the processor.
     Press F14 and report the problem.
 Technical description . . . . . . . . :   LIC Exception Analysis


Am I correct when I think that this indicates a hardware error on the 
"File Server IOA" ?


Any thoughts are really appreciated.


Many TNX in advance,



Chris

          .                        \\|//                        .
 ._O_.   . ________________________(o o)________________________ .   ._O_.
/_\o/_\ .                    -oOOO--(_)--OOOo-                    . /_\o/_\
  /H\  .          live : Chris.Spirinckx@easynet.be                .  /H\
 (=O=).           ICQ  : 14033396                                   .(=O=)
   U .            work : chris_spirinckx@pee.pioneer.be              . U
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@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
+---

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.